Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 7 112 | repo_url stringlengths 36 141 | action stringclasses 3 values | title stringlengths 2 665 | labels stringlengths 4 554 | body stringlengths 3 235k | index stringclasses 6 values | text_combine stringlengths 96 235k | label stringclasses 2 values | text stringlengths 96 196k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
34,176 | 28,438,655,736 | IssuesEvent | 2023-04-15 16:27:06 | sulton-max/profile.todoapp | https://api.github.com/repos/sulton-max/profile.todoapp | opened | Configure routes | infrastructure | # The Ask
Configure client app routes
# How to Complete this Task
Here's some steps to complete this deliverable.
- Create route guard
- Configure client app routes for following pages | 1.0 | Configure routes - # The Ask
Configure client app routes
# How to Complete this Task
Here's some steps to complete this deliverable.
- Create route guard
- Configure client app routes for following pages | infrastructure | configure routes the ask configure client app routes how to complete this task here s some steps to complete this deliverable create route guard configure client app routes for following pages | 1 |
73,774 | 7,354,632,169 | IssuesEvent | 2018-03-09 07:53:48 | prometheus/prometheus | https://api.github.com/repos/prometheus/prometheus | closed | PromQL tests fail to run on a system with 4gb /tmp space | component/tests kind/bug low hanging fruit priority/P3 | **What did you do?**
go test github.com/prometheus/prometheus/promql
**What did you expect to see?**
Tests to succeed.
**What did you see instead? Under which circumstances?**
```
...
--- FAIL: TestEvaluations (7.40s)
promql_test.go:33: error running test testdata/functions.test: log series: no space left on device
promql_test.go:33: error running test testdata/histograms.test: log series: no space left on device
promql_test.go:33: error running test testdata/legacy.test: log series: no space left on device
promql_test.go:33: error running test testdata/operators.test: log series: no space left on device
promql_test.go:33: error running test testdata/selectors.test: log series: no space left on device
promql_test.go:33: error running test testdata/staleness.test: log series: no space left on device
FAIL
FAIL github.com/prometheus/prometheus/promql 7.861s
```
**Environment**
* System information:
Linux 4.13.6-1-ARCH x86_64
tmpfs is 4GB: `tmpfs on /tmp type tmpfs (rw,nosuid,nodev)`
* Prometheus version:
master + updated tsdb (commit: 721050c6)
| 1.0 | PromQL tests fail to run on a system with 4gb /tmp space - **What did you do?**
go test github.com/prometheus/prometheus/promql
**What did you expect to see?**
Tests to succeed.
**What did you see instead? Under which circumstances?**
```
...
--- FAIL: TestEvaluations (7.40s)
promql_test.go:33: error running test testdata/functions.test: log series: no space left on device
promql_test.go:33: error running test testdata/histograms.test: log series: no space left on device
promql_test.go:33: error running test testdata/legacy.test: log series: no space left on device
promql_test.go:33: error running test testdata/operators.test: log series: no space left on device
promql_test.go:33: error running test testdata/selectors.test: log series: no space left on device
promql_test.go:33: error running test testdata/staleness.test: log series: no space left on device
FAIL
FAIL github.com/prometheus/prometheus/promql 7.861s
```
**Environment**
* System information:
Linux 4.13.6-1-ARCH x86_64
tmpfs is 4GB: `tmpfs on /tmp type tmpfs (rw,nosuid,nodev)`
* Prometheus version:
master + updated tsdb (commit: 721050c6)
| non_infrastructure | promql tests fail to run on a system with tmp space what did you do go test github com prometheus prometheus promql what did you expect to see tests to succeed what did you see instead under which circumstances fail testevaluations promql test go error running test testdata functions test log series no space left on device promql test go error running test testdata histograms test log series no space left on device promql test go error running test testdata legacy test log series no space left on device promql test go error running test testdata operators test log series no space left on device promql test go error running test testdata selectors test log series no space left on device promql test go error running test testdata staleness test log series no space left on device fail fail github com prometheus prometheus promql environment system information linux arch tmpfs is tmpfs on tmp type tmpfs rw nosuid nodev prometheus version master updated tsdb commit | 0 |
33,955 | 28,033,920,638 | IssuesEvent | 2023-03-28 14:01:01 | nf-core/tools | https://api.github.com/repos/nf-core/tools | closed | Don't use `System.exit(1)` | template linting good-first-issue infrastructure | We've been giving @pditommaso nightmares with our use of `System.exit`:
https://github.com/nf-core/tools/blob/bc56cdd35077e408a0a7c90ec07fcdff7c2d1f3b/nf_core/pipeline-template/lib/WorkflowPipeline.groovy#L16-L17
```console
$ nextflow run .
N E X T F L O W ~ version 22.08.2-edge
Launching `./main.nf` [crazy_swirles] DSL2 - revision: 6b60f60cc2
Genome fasta file not specified with e.g. '--fasta genome.fa' or via a detectable config file.
```
Instead, we should be using exceptions:
```nextflow
throw new Exception("Genome fasta file not specified with e.g. '--fasta genome.fa' or via a detectable config file.")
```
```console
$ nextflow run .
N E X T F L O W ~ version 22.08.2-edge
Launching `./main.nf` [cranky_roentgen] DSL2 - revision: 62f715c40c
Genome fasta file not specified with e.g. '--fasta genome.fa' or via a detectable config file.
-- Check script 'main.nf' at line: 1 or see '.nextflow.log' file for more details
```
### TODO
- [ ] Remove from the template
- [ ] Add lint tests that search all files for `System.exit` | 1.0 | Don't use `System.exit(1)` - We've been giving @pditommaso nightmares with our use of `System.exit`:
https://github.com/nf-core/tools/blob/bc56cdd35077e408a0a7c90ec07fcdff7c2d1f3b/nf_core/pipeline-template/lib/WorkflowPipeline.groovy#L16-L17
```console
$ nextflow run .
N E X T F L O W ~ version 22.08.2-edge
Launching `./main.nf` [crazy_swirles] DSL2 - revision: 6b60f60cc2
Genome fasta file not specified with e.g. '--fasta genome.fa' or via a detectable config file.
```
Instead, we should be using exceptions:
```nextflow
throw new Exception("Genome fasta file not specified with e.g. '--fasta genome.fa' or via a detectable config file.")
```
```console
$ nextflow run .
N E X T F L O W ~ version 22.08.2-edge
Launching `./main.nf` [cranky_roentgen] DSL2 - revision: 62f715c40c
Genome fasta file not specified with e.g. '--fasta genome.fa' or via a detectable config file.
-- Check script 'main.nf' at line: 1 or see '.nextflow.log' file for more details
```
### TODO
- [ ] Remove from the template
- [ ] Add lint tests that search all files for `System.exit` | infrastructure | don t use system exit we ve been giving pditommaso nightmares with our use of system exit console nextflow run n e x t f l o w version edge launching main nf revision genome fasta file not specified with e g fasta genome fa or via a detectable config file instead we should be using exceptions nextflow throw new exception genome fasta file not specified with e g fasta genome fa or via a detectable config file console nextflow run n e x t f l o w version edge launching main nf revision genome fasta file not specified with e g fasta genome fa or via a detectable config file check script main nf at line or see nextflow log file for more details todo remove from the template add lint tests that search all files for system exit | 1 |
21,160 | 14,404,828,227 | IssuesEvent | 2020-12-03 17:49:14 | sciencehistory/scihist_digicoll | https://api.github.com/repos/sciencehistory/scihist_digicoll | opened | Add poppler-utils exiftool to Ansible build. | heroku infrastructure | Just add them to the list of packages installed by apt in the Ansible code. | 1.0 | Add poppler-utils exiftool to Ansible build. - Just add them to the list of packages installed by apt in the Ansible code. | infrastructure | add poppler utils exiftool to ansible build just add them to the list of packages installed by apt in the ansible code | 1 |
14,926 | 11,244,058,968 | IssuesEvent | 2020-01-10 05:47:15 | battlecode/battlecode20 | https://api.github.com/repos/battlecode/battlecode20 | closed | Block stdout spam | critical engine infrastructure | Limit stdout spamming to something reasonable, so that we don't have to deal with transporting ridiculously large amounts of stdout jabber. Can also let us use less memory on scrim servers. | 1.0 | Block stdout spam - Limit stdout spamming to something reasonable, so that we don't have to deal with transporting ridiculously large amounts of stdout jabber. Can also let us use less memory on scrim servers. | infrastructure | block stdout spam limit stdout spamming to something reasonable so that we don t have to deal with transporting ridiculously large amounts of stdout jabber can also let us use less memory on scrim servers | 1 |
11,351 | 9,321,270,202 | IssuesEvent | 2019-03-27 03:06:07 | BradleyA/docker-security-infrastructure | https://api.github.com/repos/BradleyA/docker-security-infrastructure | opened | Remove firewall/create-ufw.sh Uncomplicated Firwwall (UFW) | new command/service | Create a firewall script to:
pause x seconds, x minutes, x hours;
then remove existing port definitions | 1.0 | Remove firewall/create-ufw.sh Uncomplicated Firwwall (UFW) - Create a firewall script to:
pause x seconds, x minutes, x hours;
then remove existing port definitions | non_infrastructure | remove firewall create ufw sh uncomplicated firwwall ufw create a firewall script to pause x seconds x minutes x hours then remove existing port definitions | 0 |
73,224 | 14,011,967,568 | IssuesEvent | 2020-10-29 08:19:44 | Regalis11/Barotrauma | https://api.github.com/repos/Regalis11/Barotrauma | closed | Oxygen distribution logic doesn't work correctly in multi-hull rooms | Bug Code | - [x] I have searched the issue tracker to check if the issue has already been reported.
**Description**
https://steamcommunity.com/app/602960/discussions/0/2949250308627705158/
> - The amount of oxygen contained in a room is proportional to its size as oxygen level drops faster in small rooms.
> - Oxygen flows through gaps just fine.
> - The amount of oxygen produced by one vent is proportional to the size of the hull where the vent is located.
> - BUG: Multiple hulls with gapsinbetween are not considered as a single volume even when the hulls are linked together.
**Version**
Any
| 1.0 | Oxygen distribution logic doesn't work correctly in multi-hull rooms - - [x] I have searched the issue tracker to check if the issue has already been reported.
**Description**
https://steamcommunity.com/app/602960/discussions/0/2949250308627705158/
> - The amount of oxygen contained in a room is proportional to its size as oxygen level drops faster in small rooms.
> - Oxygen flows through gaps just fine.
> - The amount of oxygen produced by one vent is proportional to the size of the hull where the vent is located.
> - BUG: Multiple hulls with gapsinbetween are not considered as a single volume even when the hulls are linked together.
**Version**
Any
| non_infrastructure | oxygen distribution logic doesn t work correctly in multi hull rooms i have searched the issue tracker to check if the issue has already been reported description the amount of oxygen contained in a room is proportional to its size as oxygen level drops faster in small rooms oxygen flows through gaps just fine the amount of oxygen produced by one vent is proportional to the size of the hull where the vent is located bug multiple hulls with gapsinbetween are not considered as a single volume even when the hulls are linked together version any | 0 |
10,799 | 8,728,203,687 | IssuesEvent | 2018-12-10 16:47:24 | astropy/astropy-tutorials | https://api.github.com/repos/astropy/astropy-tutorials | opened | Hide the "q=filterTutorials" when showing all the tutorials | infrastructure | Right now to get all the tutorials, the URL has to end with the query `?q=filterTutorials`. That's a bit ugly, and is an implementation detail leaking out into the user-space. It also has the (admittedly minor) side-effect that if the text "featureTutorials" is in any notebook it gets highlighted. We should figure out how to have that not be necessary - I think this is probably just a javascript tweak to make the "no query string" default be equivalent to "filterTutorials". But I haven't looked in detail, so @MananAgarwal might have more context/ideas. | 1.0 | Hide the "q=filterTutorials" when showing all the tutorials - Right now to get all the tutorials, the URL has to end with the query `?q=filterTutorials`. That's a bit ugly, and is an implementation detail leaking out into the user-space. It also has the (admittedly minor) side-effect that if the text "featureTutorials" is in any notebook it gets highlighted. We should figure out how to have that not be necessary - I think this is probably just a javascript tweak to make the "no query string" default be equivalent to "filterTutorials". But I haven't looked in detail, so @MananAgarwal might have more context/ideas. | infrastructure | hide the q filtertutorials when showing all the tutorials right now to get all the tutorials the url has to end with the query q filtertutorials that s a bit ugly and is an implementation detail leaking out into the user space it also has the admittedly minor side effect that if the text featuretutorials is in any notebook it gets highlighted we should figure out how to have that not be necessary i think this is probably just a javascript tweak to make the no query string default be equivalent to filtertutorials but i haven t looked in detail so mananagarwal might have more context ideas | 1 |
20,527 | 3,603,609,147 | IssuesEvent | 2016-02-03 19:41:39 | epforgpl/web-kodujdlapolski.pl | https://api.github.com/repos/epforgpl/web-kodujdlapolski.pl | closed | Wyrównanie i pogrubienie tekstu | design do zakodowania | 
Ewentualne wyśrodkowanie do prawej, ale co wtedy z wydarzeniami?
@mszkodzinski | 1.0 | Wyrównanie i pogrubienie tekstu - 
Ewentualne wyśrodkowanie do prawej, ale co wtedy z wydarzeniami?
@mszkodzinski | non_infrastructure | wyrównanie i pogrubienie tekstu ewentualne wyśrodkowanie do prawej ale co wtedy z wydarzeniami mszkodzinski | 0 |
17,138 | 12,235,275,905 | IssuesEvent | 2020-05-04 14:39:44 | denyhosts/denyhosts | https://api.github.com/repos/denyhosts/denyhosts | closed | Denyhosts Sync Server | infrastructure | Is it possible to have denyhosts_sync that @janpascal owns, moved over as a new repository under the DenyHosts organization? That way the sync server can be supported under the DenyHosts Organization, and users can then easily find the Sync server. I think it would allow users to spin up additional sync servers, and give us the ability to further develop it under the DenyHosts "branding".
I don't have permission to fork or create a repo under the DenyHosts organization, that's why I was adding @mruffalo to the assignees. | 1.0 | Denyhosts Sync Server - Is it possible to have denyhosts_sync that @janpascal owns, moved over as a new repository under the DenyHosts organization? That way the sync server can be supported under the DenyHosts Organization, and users can then easily find the Sync server. I think it would allow users to spin up additional sync servers, and give us the ability to further develop it under the DenyHosts "branding".
I don't have permission to fork or create a repo under the DenyHosts organization, that's why I was adding @mruffalo to the assignees. | infrastructure | denyhosts sync server is it possible to have denyhosts sync that janpascal owns moved over as a new repository under the denyhosts organization that way the sync server can be supported under the denyhosts organization and users can then easily find the sync server i think it would allow users to spin up additional sync servers and give us the ability to further develop it under the denyhosts branding i don t have permission to fork or create a repo under the denyhosts organization that s why i was adding mruffalo to the assignees | 1 |
32,957 | 27,108,766,509 | IssuesEvent | 2023-02-15 14:00:17 | ZcashFoundation/zebra | https://api.github.com/repos/ZcashFoundation/zebra | opened | actions: keep scripts out of the workflow scope | A-infrastructure A-devops C-enhancement S-needs-triage P-Low :snowflake: | ## Motivation
Some workflows are script intensive, making the workflows unreadable.
### Specifications
A good approach to handle this would be moving all the scripts to multiple files outside the workflow, or create a GitHub Action to execute them in a reusable manner.
### Complex Code or Requirements
- Define a place to hold all the script files
- Keep linting working on these files
- Use a name convention for script files
| 1.0 | actions: keep scripts out of the workflow scope - ## Motivation
Some workflows are script intensive, making the workflows unreadable.
### Specifications
A good approach to handle this would be moving all the scripts to multiple files outside the workflow, or create a GitHub Action to execute them in a reusable manner.
### Complex Code or Requirements
- Define a place to hold all the script files
- Keep linting working on these files
- Use a name convention for script files
| infrastructure | actions keep scripts out of the workflow scope motivation some workflows are script intensive making the workflows unreadable specifications a good approach to handle this would be moving all the scripts to multiple files outside the workflow or create a github action to execute them in a reusable manner complex code or requirements define a place to hold all the script files keep linting working on these files use a name convention for script files | 1 |
210,518 | 7,190,643,885 | IssuesEvent | 2018-02-02 17:59:55 | ubc/compair | https://api.github.com/repos/ubc/compair | opened | Make grading more robust | enhancement high priority instructor request | Add manual entry option for grading and change how grades can be calculated.
On the assignment form, change participation grade to simply grade. Allow for six options instead of three, allowing for participation-based and instructor-entered for each of the three areas (answering, comparing, self-evaluating). Each of the six options gets its own weighting, totaling 100% overall.
On the comparisons tab (which should probably be renamed since its function is changing, perhaps "Grading + Feedback" once we add #688?), conditionally display input fields for manually entering (percentage-based) grades related to the answer, feedback, and self-evaluation. Most instructors pointed to the right-hand side as where they would expect this option to appear for each grade. We'll probably want to remove the alternating coloured background for the comparisons, so these are grouped better as one area with the grade input at the bottom.
The final, total grade should be output to LTI and the participation tab for each assignment. But the separate, manually-entered grades should appear along with the final grade in the participation reports. | 1.0 | Make grading more robust - Add manual entry option for grading and change how grades can be calculated.
On the assignment form, change participation grade to simply grade. Allow for six options instead of three, allowing for participation-based and instructor-entered for each of the three areas (answering, comparing, self-evaluating). Each of the six options gets its own weighting, totaling 100% overall.
On the comparisons tab (which should probably be renamed since its function is changing, perhaps "Grading + Feedback" once we add #688?), conditionally display input fields for manually entering (percentage-based) grades related to the answer, feedback, and self-evaluation. Most instructors pointed to the right-hand side as where they would expect this option to appear for each grade. We'll probably want to remove the alternating coloured background for the comparisons, so these are grouped better as one area with the grade input at the bottom.
The final, total grade should be output to LTI and the participation tab for each assignment. But the separate, manually-entered grades should appear along with the final grade in the participation reports. | non_infrastructure | make grading more robust add manual entry option for grading and change how grades can be calculated on the assignment form change participation grade to simply grade allow for six options instead of three allowing for participation based and instructor entered for each of the three areas answering comparing self evaluating each of the six options gets its own weighting totaling overall on the comparisons tab which should probably be renamed since its function is changing perhaps grading feedback once we add conditionally display input fields for manually entering percentage based grades related to the answer feedback and self evaluation most instructors pointed to the right hand side as where they would expect this option to appear for each grade we ll probably want to remove the alternating coloured background for the comparisons so these are grouped better as one area with the grade input at the bottom the final total grade should be output to lti and the participation tab for each assignment but the separate manually entered grades should appear along with the final grade in the participation reports | 0 |
127,508 | 27,060,035,069 | IssuesEvent | 2023-02-13 19:00:46 | OpenVPN/openvpn | https://api.github.com/repos/OpenVPN/openvpn | opened | Get rid of --ip-win32 and --route-method | outdated code Windows | As discussed in #239, we want to get rid of all the code path variants in the windows backend.
Since that issue was about a specific bug caused by this old cruft, I'm opening a new one that reminds us "we want this fixed, eventually". | 1.0 | Get rid of --ip-win32 and --route-method - As discussed in #239, we want to get rid of all the code path variants in the windows backend.
Since that issue was about a specific bug caused by this old cruft, I'm opening a new one that reminds us "we want this fixed, eventually". | non_infrastructure | get rid of ip and route method as discussed in we want to get rid of all the code path variants in the windows backend since that issue was about a specific bug caused by this old cruft i m opening a new one that reminds us we want this fixed eventually | 0 |
17,898 | 12,684,712,326 | IssuesEvent | 2020-06-19 23:49:31 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | [libraries] Skipping passing WASM tests | arch-wasm area-Infrastructure-libraries untriaged | When running WASM library tests, a significant amount of [tests](https://github.com/dotnet/runtime/files/4794289/tnse2.txt)
were failing due to threading not being supported. As such, #37822 was created and merged to skip these tests in order to get WASM tests running on helix #37752.
However, it was noticed that some tests being skip actually pass on master now (e.g. Microsoft.Extensions.Configuration.Tests), so there is a need to rerun WASM tests to get a fresh list of test names that fail with `WASM: System.PlatformNotSupportedException : Cannot start threads on this runtime` or `WASM: System.PlatformNotSupportedException : Cannot wait on monitors on this runtime`. In doing so, the changes that skip passing tests on master can be reverted. | 1.0 | [libraries] Skipping passing WASM tests - When running WASM library tests, a significant amount of [tests](https://github.com/dotnet/runtime/files/4794289/tnse2.txt)
were failing due to threading not being supported. As such, #37822 was created and merged to skip these tests in order to get WASM tests running on helix #37752.
However, it was noticed that some tests being skip actually pass on master now (e.g. Microsoft.Extensions.Configuration.Tests), so there is a need to rerun WASM tests to get a fresh list of test names that fail with `WASM: System.PlatformNotSupportedException : Cannot start threads on this runtime` or `WASM: System.PlatformNotSupportedException : Cannot wait on monitors on this runtime`. In doing so, the changes that skip passing tests on master can be reverted. | infrastructure | skipping passing wasm tests when running wasm library tests a significant amount of were failing due to threading not being supported as such was created and merged to skip these tests in order to get wasm tests running on helix however it was noticed that some tests being skip actually pass on master now e g microsoft extensions configuration tests so there is a need to rerun wasm tests to get a fresh list of test names that fail with wasm system platformnotsupportedexception cannot start threads on this runtime or wasm system platformnotsupportedexception cannot wait on monitors on this runtime in doing so the changes that skip passing tests on master can be reverted | 1 |
18,301 | 3,683,244,487 | IssuesEvent | 2016-02-24 13:19:49 | akvo/akvo-rsr | https://api.github.com/repos/akvo/akvo-rsr | closed | Testing Scripts Phase 1 | Feature request Type: Testing | As discussed, we need the Test User setup details to be run in the Admin prior to running any of the Automated Testing.
In addition, we have the following requirements to be added to the existing donation test package, to incorporate the new funding to 100% functionality.
- donating to a project via PayPal
- donating to a project via iDeal
- allowing the project to be fully funded by a single donor
- allowing the project to be funded to completion by a donor
- allowing projects to reach 100% funding from donations and not via manual admin correction
- projects do not get "seriously" over-funded (more than 1-2%)
- any inaccuracies between fees charged by PayPal and fees received by Akvo need to be in Akvo' s favour and easily accountable
- the visuals should display the correct funding and fee amounts per donor
- any over-funding should be clearly visible on the project page
These tests are to test the functionality added by issue #120
<!---
@huboard:{"order":39.9921875}
-->
| 1.0 | Testing Scripts Phase 1 - As discussed, we need the Test User setup details to be run in the Admin prior to running any of the Automated Testing.
In addition, we have the following requirements to be added to the existing donation test package, to incorporate the new funding to 100% functionality.
- donating to a project via PayPal
- donating to a project via iDeal
- allowing the project to be fully funded by a single donor
- allowing the project to be funded to completion by a donor
- allowing projects to reach 100% funding from donations and not via manual admin correction
- projects do not get "seriously" over-funded (more than 1-2%)
- any inaccuracies between fees charged by PayPal and fees received by Akvo need to be in Akvo' s favour and easily accountable
- the visuals should display the correct funding and fee amounts per donor
- any over-funding should be clearly visible on the project page
These tests are to test the functionality added by issue #120
<!---
@huboard:{"order":39.9921875}
-->
| non_infrastructure | testing scripts phase as discussed we need the test user setup details to be run in the admin prior to running any of the automated testing in addition we have the following requirements to be added to the existing donation test package to incorporate the new funding to functionality donating to a project via paypal donating to a project via ideal allowing the project to be fully funded by a single donor allowing the project to be funded to completion by a donor allowing projects to reach funding from donations and not via manual admin correction projects do not get seriously over funded more than any inaccuracies between fees charged by paypal and fees received by akvo need to be in akvo s favour and easily accountable the visuals should display the correct funding and fee amounts per donor any over funding should be clearly visible on the project page these tests are to test the functionality added by issue huboard order | 0 |
565,589 | 16,764,900,626 | IssuesEvent | 2021-06-14 07:34:08 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.jumbo.com - Images are blurred | browser-fenix engine-gecko priority-normal severity-important | <!-- @browser: Firefox Mobile 90.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 11; Mobile; rv:90.0) Gecko/90.0 Firefox/90.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/74453 -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://www.jumbo.com/
**Browser / Version**: Firefox Mobile 90.0
**Operating System**: Android 11
**Tested Another Browser**: Yes Chrome
**Problem type**: Something else
**Description**: Firefox displays images blurred
**Steps to Reproduce**:
Some images are being rendered incorrectly in Firefox, they have a blurry appearance which is not present in other browsers
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2021/5/239e1a74-316c-47b1-b524-53f655a93e67.jpg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20210517094928</li><li>channel: nightly</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2021/5/a3d5f395-dd1a-4a33-9ebf-fcd0563cc238)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.jumbo.com - Images are blurred - <!-- @browser: Firefox Mobile 90.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 11; Mobile; rv:90.0) Gecko/90.0 Firefox/90.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/74453 -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://www.jumbo.com/
**Browser / Version**: Firefox Mobile 90.0
**Operating System**: Android 11
**Tested Another Browser**: Yes Chrome
**Problem type**: Something else
**Description**: Firefox displays images blurred
**Steps to Reproduce**:
Some images are being rendered incorrectly in Firefox, they have a blurry appearance which is not present in other browsers
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2021/5/239e1a74-316c-47b1-b524-53f655a93e67.jpg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20210517094928</li><li>channel: nightly</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2021/5/a3d5f395-dd1a-4a33-9ebf-fcd0563cc238)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_infrastructure | images are blurred url browser version firefox mobile operating system android tested another browser yes chrome problem type something else description firefox displays images blurred steps to reproduce some images are being rendered incorrectly in firefox they have a blurry appearance which is not present in other browsers view the screenshot img alt screenshot src browser configuration gfx webrender all false gfx webrender blob images true gfx webrender enabled false image mem shared true buildid channel nightly hastouchscreen true mixed active content blocked false mixed passive content blocked false tracking content blocked false from with ❤️ | 0 |
14,029 | 10,585,119,385 | IssuesEvent | 2019-10-08 16:47:34 | nilearn/nilearn | https://api.github.com/repos/nilearn/nilearn | closed | Handling Conda's unreliability | Important Infrastructure | Conda, much as I like it as an end user, has been a source of difficulties recently. #2077 #2079
They suddenly dropped support for older versions of packages, which prompted me to suggest upgrading our minimum supported versions of Scikit-learn, Scipy to 0.19. However, with each minor version bump they seemingly were dropping support for more and more packages (scipy 0.19 is no longer available in the main channel).
I asked them about it here, please read this: https://github.com/ContinuumIO/anaconda-issues/issues/11146#event-2509814992
This response, plus reading the linked blog post, indicates to me that conda might be fine as a package manager for end-users, but we cannot rely on it for running our CIs.
For a short term solution, we can either pin its version to 4.6 (currently we are doing that for Nistats).
Or we add the older channel back, as described in the issue link and the blog post.
For a longer term, I am thinking about switching to pip.
We can let CircleCI keep using conda - it always uses the latest version and is a good way to test our conda pipeline. For Travis etc, I propose we move to pip.
I would like to move quickly on this matter. @GaelVaroquaux | 1.0 | Handling Conda's unreliability - Conda, much as I like it as an end user, has been a source of difficulties recently. #2077 #2079
They suddenly dropped support for older versions of packages, which prompted me to suggest upgrading our minimum supported versions of Scikit-learn, Scipy to 0.19. However, with each minor version bump they seemingly were dropping support for more and more packages (scipy 0.19 is no longer available in the main channel).
I asked them about it here, please read this: https://github.com/ContinuumIO/anaconda-issues/issues/11146#event-2509814992
This response, plus reading the linked blog post, indicates to me that conda might be fine as a package manager for end-users, but we cannot rely on it for running our CIs.
For a short term solution, we can either pin its version to 4.6 (currently we are doing that for Nistats).
Or we add the older channel back, as described in the issue link and the blog post.
For a longer term, I am thinking about switching to pip.
We can let CircleCI keep using conda - it always uses the latest version and is a good way to test our conda pipeline. For Travis etc, I propose we move to pip.
I would like to move quickly on this matter. @GaelVaroquaux | infrastructure | handling conda s unreliability conda much as i like it as an end user has been a source of difficulties recently they suddenly dropped support for older versions of packages which prompted me to suggest upgrading our minimum supported versions of scikit learn scipy to however with each minor version bump they seemingly were dropping support for more and more packages scipy is no longer available in the main channel i asked them about it here please read this this response plus reading the linked blog post indicates to me that conda might be fine as a package manager for end users but we cannot rely on it for running our cis for a short term solution we can either pin its version to currently we are doing that for nistats or we add the older channel back as described in the issue link and the blog post for a longer term i am thinking about switching to pip we can let circleci keep using conda it always uses the latest version and is a good way to test our conda pipeline for travis etc i propose we move to pip i would like to move quickly on this matter gaelvaroquaux | 1 |
231,635 | 7,641,539,131 | IssuesEvent | 2018-05-08 05:37:12 | braun-robotics/rust-lpc82x-hal | https://api.github.com/repos/braun-robotics/rust-lpc82x-hal | closed | Add methods for disabling and destroying peripherals | priority: medium type: enhancement | So far, I haven't added any methods to disable peripherals again after they have been initialized. While this shouldn't be necessary to get stuff to work, it is important to save power.
My thoughts on the matter:
- It should be possible to enable peripherals from both the `Unknown` state and the (yet to be added) `Disabled` state, so it probably makes sense to add another trait for the state types, `CanBeEnabled` or similar, to prevent code duplication.
- `Initialized` could be renamed to `Enabled`.
- It's worth thinking about how this relates to peripheral resets. I haven't really looked into those and don't know how they work in detail.
- Do peripherals keep their state when they are disabled but not reset? If so, that needs to be taken into account. | 1.0 | Add methods for disabling and destroying peripherals - So far, I haven't added any methods to disable peripherals again after they have been initialized. While this shouldn't be necessary to get stuff to work, it is important to save power.
My thoughts on the matter:
- It should be possible to enable peripherals from both the `Unknown` state and the (yet to be added) `Disabled` state, so it probably makes sense to add another trait for the state types, `CanBeEnabled` or similar, to prevent code duplication.
- `Initialized` could be renamed to `Enabled`.
- It's worth thinking about how this relates to peripheral resets. I haven't really looked into those and don't know how they work in detail.
- Do peripherals keep their state when they are disabled but not reset? If so, that needs to be taken into account. | non_infrastructure | add methods for disabling and destroying peripherals so far i haven t added any methods to disable peripherals again after they have been initialized while this shouldn t be necessary to get stuff to work it is important to save power my thoughts on the matter it should be possible to enable peripherals from both the unknown state and the yet to be added disabled state so it probably makes sense to add another trait for the state types canbeenabled or similar to prevent code duplication initialized could be renamed to enabled it s worth thinking about how this relates to peripheral resets i haven t really looked into those and don t know how they work in detail do peripherals keep their state when they are disabled but not reset if so that needs to be taken into account | 0 |
17,672 | 12,500,245,702 | IssuesEvent | 2020-06-01 21:49:17 | APSIMInitiative/ApsimX | https://api.github.com/repos/APSIMInitiative/ApsimX | closed | Error when deserializing a plant | bug interface/infrastructure | Deserializing a plant resource model currently causes an error to be thrown when it attempts to copy the EmergenceDate property from the resource model. This occurs because there is the property is writable but not readable. Note that the error is handled internally, so it's only noticeable when debugging with break-on-exception enabeld. | 1.0 | Error when deserializing a plant - Deserializing a plant resource model currently causes an error to be thrown when it attempts to copy the EmergenceDate property from the resource model. This occurs because there is the property is writable but not readable. Note that the error is handled internally, so it's only noticeable when debugging with break-on-exception enabeld. | infrastructure | error when deserializing a plant deserializing a plant resource model currently causes an error to be thrown when it attempts to copy the emergencedate property from the resource model this occurs because there is the property is writable but not readable note that the error is handled internally so it s only noticeable when debugging with break on exception enabeld | 1 |
307,313 | 9,415,423,178 | IssuesEvent | 2019-04-10 12:37:28 | WoWManiaUK/Blackwing-Lair | https://api.github.com/repos/WoWManiaUK/Blackwing-Lair | closed | [NPC/Vendor - 17490 ] Ergh of the Stillpine - Azuremyst Isle | Fixed Confirmed Fixed in Dev Priority zone 1-20 | **Links:**
[Ergh of the Stillpine](https://www.wowhead.com/npc=17490/ergh-of-the-stillpine)
**What is happening:**
Out of goods
**What should happen:**
Need to sell stuff
| 1.0 | [NPC/Vendor - 17490 ] Ergh of the Stillpine - Azuremyst Isle - **Links:**
[Ergh of the Stillpine](https://www.wowhead.com/npc=17490/ergh-of-the-stillpine)
**What is happening:**
Out of goods
**What should happen:**
Need to sell stuff
| non_infrastructure | ergh of the stillpine azuremyst isle links what is happening out of goods what should happen need to sell stuff | 0 |
96,130 | 19,903,593,916 | IssuesEvent | 2022-01-25 10:27:41 | microsoft/code-with-engineering-playbook | https://api.github.com/repos/microsoft/code-with-engineering-playbook | closed | Guidance on suggested repo structures | source code | As an example, for data science and python you can use https://drivendata.github.io/cookiecutter-data-science/#example as a project template to automatically incorporate a lot of best practices.
For DDD .NET MicroServices - https://docs.microsoft.com/en-us/dotnet/architecture/microservices/microservice-ddd-cqrs-patterns/ddd-oriented-microservice
Terraform? | 1.0 | Guidance on suggested repo structures - As an example, for data science and python you can use https://drivendata.github.io/cookiecutter-data-science/#example as a project template to automatically incorporate a lot of best practices.
For DDD .NET MicroServices - https://docs.microsoft.com/en-us/dotnet/architecture/microservices/microservice-ddd-cqrs-patterns/ddd-oriented-microservice
Terraform? | non_infrastructure | guidance on suggested repo structures as an example for data science and python you can use as a project template to automatically incorporate a lot of best practices for ddd net microservices terraform | 0 |
284,753 | 21,468,281,192 | IssuesEvent | 2022-04-26 07:07:30 | awslabs/kubeflow-manifests | https://api.github.com/repos/awslabs/kubeflow-manifests | opened | Spot instance support in kubeflow deployment. | documentation | <!-- Please submit only documentation-related issues or requests for new documentation with this form.-->
Although EKS has support for [spot instance](https://aws.amazon.com/about-aws/whats-new/2020/12/amazon-eks-support-ec2-spot-instances-managed-node-groups/), kubeflow guide doesn't spell it well. We should explicitly call it out and add any guideline or example around it.
| 1.0 | Spot instance support in kubeflow deployment. - <!-- Please submit only documentation-related issues or requests for new documentation with this form.-->
Although EKS has support for [spot instance](https://aws.amazon.com/about-aws/whats-new/2020/12/amazon-eks-support-ec2-spot-instances-managed-node-groups/), kubeflow guide doesn't spell it well. We should explicitly call it out and add any guideline or example around it.
| non_infrastructure | spot instance support in kubeflow deployment although eks has support for kubeflow guide doesn t spell it well we should explicitly call it out and add any guideline or example around it | 0 |
470 | 2,722,123,066 | IssuesEvent | 2015-04-14 00:10:18 | dart-lang/dartdoc | https://api.github.com/repos/dart-lang/dartdoc | closed | Add Support for Pub Global and Snapshotting | bug help wanted Infrastructure P0 | I am willing to implement support for Pub Global and Snapshotting. This can be done by adding a transformer that inlines the templates and resources into the code itself before compilation. | 1.0 | Add Support for Pub Global and Snapshotting - I am willing to implement support for Pub Global and Snapshotting. This can be done by adding a transformer that inlines the templates and resources into the code itself before compilation. | infrastructure | add support for pub global and snapshotting i am willing to implement support for pub global and snapshotting this can be done by adding a transformer that inlines the templates and resources into the code itself before compilation | 1 |
22,278 | 15,083,803,608 | IssuesEvent | 2021-02-05 16:18:31 | aguirre-lab/ml4c3 | https://api.github.com/repos/aguirre-lab/ml4c3 | opened | Group same medicines with different names | infrastructure 🚇 | ## What and why
Same medicines are stored in EDW with different names, for example norepinephrine is known to be stored as:
* `norepinephrine_infusion_syringe_in_swfi_80_mcg|ml_cmpd_central_mgh`
* `norepinephrine_infusion_in_ns_16_mcg|ml_(250_ml)`
* ... up to 36 different names
It would be useful to group all the signals that are actually the same thing.
However, not all those names are necessarily exactly the same. Although they are all norepinephrine, maybe the way it's given to the patient or the type of norepinephrine differs, so knowledge from a physician would be better before grouping them.
## Solution(s)
With the help of Nick, I will group medicines that are actually the same into a single signal.
## Acceptance criteria
Code can create a norepinephrine and other medicines with the values from their different names.
## Blocked by or pending
Discussion with Nick about which signals can be grouped together
| 1.0 | Group same medicines with different names - ## What and why
Same medicines are stored in EDW with different names, for example norepinephrine is known to be stored as:
* `norepinephrine_infusion_syringe_in_swfi_80_mcg|ml_cmpd_central_mgh`
* `norepinephrine_infusion_in_ns_16_mcg|ml_(250_ml)`
* ... up to 36 different names
It would be useful to group all the signals that are actually the same thing.
However, not all those names are necessarily exactly the same. Although they are all norepinephrine, maybe the way it's given to the patient or the type of norepinephrine differs, so knowledge from a physician would be better before grouping them.
## Solution(s)
With the help of Nick, I will group medicines that are actually the same into a single signal.
## Acceptance criteria
Code can create a norepinephrine and other medicines with the values from their different names.
## Blocked by or pending
Discussion with Nick about which signals can be grouped together
| infrastructure | group same medicines with different names what and why same medicines are stored in edw with different names for example norepinephrine is known to be stored as norepinephrine infusion syringe in swfi mcg ml cmpd central mgh norepinephrine infusion in ns mcg ml ml up to different names it would be useful to group all the signals that are actually the same thing however not all those names are necessarily exactly the same although they are all norepinephrine maybe the way it s given to the patient or the type of norepinephrine differs so knowledge from a physician would be better before grouping them solution s with the help of nick i will group medicines that are actually the same into a single signal acceptance criteria code can create a norepinephrine and other medicines with the values from their different names blocked by or pending discussion with nick about which signals can be grouped together | 1 |
243,541 | 20,423,872,424 | IssuesEvent | 2022-02-24 00:17:46 | kubernetes/minikube | https://api.github.com/repos/kubernetes/minikube | reopened | Frequent test failures of `TestJSONOutput/pause/Audit` | priority/backlog kind/failing-test | This test has high flake rates for the following environments:
|Environment|Flake Rate (%)|
|---|---|
|[KVM_Linux_crio](https://storage.googleapis.com/minikube-flake-rate/flake_chart.html?env=KVM_Linux_crio&test=TestJSONOutput/pause/Audit)|75.94| | 1.0 | Frequent test failures of `TestJSONOutput/pause/Audit` - This test has high flake rates for the following environments:
|Environment|Flake Rate (%)|
|---|---|
|[KVM_Linux_crio](https://storage.googleapis.com/minikube-flake-rate/flake_chart.html?env=KVM_Linux_crio&test=TestJSONOutput/pause/Audit)|75.94| | non_infrastructure | frequent test failures of testjsonoutput pause audit this test has high flake rates for the following environments environment flake rate | 0 |
479,333 | 13,794,883,518 | IssuesEvent | 2020-10-09 17:02:15 | aiidateam/aiida-quantumespresso | https://api.github.com/repos/aiidateam/aiida-quantumespresso | opened | Remove explicit checking of existence of retrieved folders in the parsers | priority/nice to have topic/parsers type/refactoring | As of `aiida-core==1.4.0`, the engine itself will check for the presence of the retrieved folder. If it is missing, which is really just a bug in `aiida-core` the engine will terminate the process and not call the parser. Anyway there would be no point since there is nothing to parse. This means that now if the parser is called, it is guaranteed that the retrieve folder exists and so we no longer have to explicitly check for it. | 1.0 | Remove explicit checking of existence of retrieved folders in the parsers - As of `aiida-core==1.4.0`, the engine itself will check for the presence of the retrieved folder. If it is missing, which is really just a bug in `aiida-core` the engine will terminate the process and not call the parser. Anyway there would be no point since there is nothing to parse. This means that now if the parser is called, it is guaranteed that the retrieve folder exists and so we no longer have to explicitly check for it. | non_infrastructure | remove explicit checking of existence of retrieved folders in the parsers as of aiida core the engine itself will check for the presence of the retrieved folder if it is missing which is really just a bug in aiida core the engine will terminate the process and not call the parser anyway there would be no point since there is nothing to parse this means that now if the parser is called it is guaranteed that the retrieve folder exists and so we no longer have to explicitly check for it | 0 |
61,273 | 6,731,780,536 | IssuesEvent | 2017-10-18 08:58:35 | RocketChat/Rocket.Chat.iOS | https://api.github.com/repos/RocketChat/Rocket.Chat.iOS | opened | [CI] Run SwiftLint on CI and comment PR with warnings and errors the result | Hacktoberfest help wanted project tests | # Description
Today we're running SwiftLint already on the CI, but we don't comment the PR with the warnings/errors found. It would be amazing to have a comment from a bot in the PR at each line the code needs to be adjusted. | 1.0 | [CI] Run SwiftLint on CI and comment PR with warnings and errors the result - # Description
Today we're running SwiftLint already on the CI, but we don't comment the PR with the warnings/errors found. It would be amazing to have a comment from a bot in the PR at each line the code needs to be adjusted. | non_infrastructure | run swiftlint on ci and comment pr with warnings and errors the result description today we re running swiftlint already on the ci but we don t comment the pr with the warnings errors found it would be amazing to have a comment from a bot in the pr at each line the code needs to be adjusted | 0 |
1,171 | 2,532,617,535 | IssuesEvent | 2015-01-23 17:16:00 | ThibaultLatrille/ControverSciences | https://api.github.com/repos/ThibaultLatrille/ControverSciences | closed | boutons pas alignés à gauche | * negligible design |
Sur la page http://www.controversciences.org/comments/new?reference_id=9
Par : T. Latrille
Navigateur : chrome modern mac webkit | 1.0 | boutons pas alignés à gauche -
Sur la page http://www.controversciences.org/comments/new?reference_id=9
Par : T. Latrille
Navigateur : chrome modern mac webkit | non_infrastructure | boutons pas alignés à gauche sur la page par t latrille navigateur chrome modern mac webkit | 0 |
112,342 | 4,524,899,710 | IssuesEvent | 2016-09-07 01:27:01 | coreos/coreos-kubernetes | https://api.github.com/repos/coreos/coreos-kubernetes | closed | 401 Unauthorized kube-apiserver in multiple master nodes front of ELB | kind/support priority/P2 | Hi,
We are trying to achieve high availability cluster with multiple master nodes front ELB.
Also trying to use ingress to layer 7 traffic from ELB to master nodes.
http://kubernetes.io/docs/user-guide/ingress/#tls
apiserver-key and apiserver cert configured as secrets.
We also have external hostname for apiserver which points to ELB.
**Scenario-1**: Request through external hostname and passing through ELB get HTTP/1.1 401 Unauthorized error.
**Scenario-2**: service endpoint HTTPS request is working fine over https and admin crt and key.
```
curl -v --cacert ca.pem https://kubernetes.default.svc.cluster.local/version --cert admin.pem --key admin-key.pem
Host: kubernetes.default.svc.cluster.local
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: application/json
< Date: Wed, 10 Aug 2016 16:34:24 GMT
< Content-Length: 260
<
{
"major": "1",
"minor": "3",
"gitVersion": "v1.3.4",
"gitCommit": "dd6b458ef8dbf24aff55795baa68f83383c9b3a9",
"gitTreeState": "clean",
"buildDate": "2016-08-01T16:38:31Z",
"goVersion": "go1.6.2",
"compiler": "gc",
"platform": "linux/amd64"
* Connection #0 to host kubernetes.default.svc.cluster.local left intact
```
**Ingress config:**
```
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: no-rules-map
spec:
tls:
- secretName: testsecret
backend:
serviceName: kubernetes
servicePort: 443
```
```
kubectl describe ing
Name: no-rules-map
Namespace: default
Address:
Default backend: kubernetes:443 (172.18.2.4:443,172.18.2.5:443)
TLS:
testsecret terminates
Rules:
Host Path Backends
---- ---- --------
* * kubernetes:443 (172.18.2.4:443,172.18.2.5:443)
Annotations:
No events.
```
**TLS secret details:**
```
kubectl describe secrets testsecret
Name: testsecret
Namespace: default
Labels: <none>
Annotations: <none>
Type: Opaque
Data
====
tls.crt: 1675 bytes
tls.key: 1679 bytes
```
------------------------------------------------------------------------------------
Question: can you please let me know your inputs why HTTPS request for apiserver fails through external hostname passing through ELB?
Please let me know if you need any more information on this.
Thanks! | 1.0 | 401 Unauthorized kube-apiserver in multiple master nodes front of ELB - Hi,
We are trying to achieve high availability cluster with multiple master nodes front ELB.
Also trying to use ingress to layer 7 traffic from ELB to master nodes.
http://kubernetes.io/docs/user-guide/ingress/#tls
apiserver-key and apiserver cert configured as secrets.
We also have external hostname for apiserver which points to ELB.
**Scenario-1**: Request through external hostname and passing through ELB get HTTP/1.1 401 Unauthorized error.
**Scenario-2**: service endpoint HTTPS request is working fine over https and admin crt and key.
```
curl -v --cacert ca.pem https://kubernetes.default.svc.cluster.local/version --cert admin.pem --key admin-key.pem
Host: kubernetes.default.svc.cluster.local
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: application/json
< Date: Wed, 10 Aug 2016 16:34:24 GMT
< Content-Length: 260
<
{
"major": "1",
"minor": "3",
"gitVersion": "v1.3.4",
"gitCommit": "dd6b458ef8dbf24aff55795baa68f83383c9b3a9",
"gitTreeState": "clean",
"buildDate": "2016-08-01T16:38:31Z",
"goVersion": "go1.6.2",
"compiler": "gc",
"platform": "linux/amd64"
* Connection #0 to host kubernetes.default.svc.cluster.local left intact
```
**Ingress config:**
```
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: no-rules-map
spec:
tls:
- secretName: testsecret
backend:
serviceName: kubernetes
servicePort: 443
```
```
kubectl describe ing
Name: no-rules-map
Namespace: default
Address:
Default backend: kubernetes:443 (172.18.2.4:443,172.18.2.5:443)
TLS:
testsecret terminates
Rules:
Host Path Backends
---- ---- --------
* * kubernetes:443 (172.18.2.4:443,172.18.2.5:443)
Annotations:
No events.
```
**TLS secret details:**
```
kubectl describe secrets testsecret
Name: testsecret
Namespace: default
Labels: <none>
Annotations: <none>
Type: Opaque
Data
====
tls.crt: 1675 bytes
tls.key: 1679 bytes
```
------------------------------------------------------------------------------------
Question: can you please let me know your inputs why HTTPS request for apiserver fails through external hostname passing through ELB?
Please let me know if you need any more information on this.
Thanks! | non_infrastructure | unauthorized kube apiserver in multiple master nodes front of elb hi we are trying to achieve high availability cluster with multiple master nodes front elb also trying to use ingress to layer traffic from elb to master nodes apiserver key and apiserver cert configured as secrets we also have external hostname for apiserver which points to elb scenario request through external hostname and passing through elb get http unauthorized error scenario service endpoint https request is working fine over https and admin crt and key curl v cacert ca pem cert admin pem key admin key pem host kubernetes default svc cluster local user agent curl accept http ok content type application json date wed aug gmt content length major minor gitversion gitcommit gittreestate clean builddate goversion compiler gc platform linux connection to host kubernetes default svc cluster local left intact ingress config apiversion extensions kind ingress metadata name no rules map spec tls secretname testsecret backend servicename kubernetes serviceport kubectl describe ing name no rules map namespace default address default backend kubernetes tls testsecret terminates rules host path backends kubernetes annotations no events tls secret details kubectl describe secrets testsecret name testsecret namespace default labels annotations type opaque data tls crt bytes tls key bytes question can you please let me know your inputs why https request for apiserver fails through external hostname passing through elb please let me know if you need any more information on this thanks | 0 |
1,635 | 2,517,071,869 | IssuesEvent | 2015-01-16 11:25:01 | ferstaberinde/FAMDB | https://api.github.com/repos/ferstaberinde/FAMDB | opened | Newly created users aren't automatically added to "DefaultUser" Role | bug priority:high | Prevents them from creating a mission. | 1.0 | Newly created users aren't automatically added to "DefaultUser" Role - Prevents them from creating a mission. | non_infrastructure | newly created users aren t automatically added to defaultuser role prevents them from creating a mission | 0 |
35,217 | 30,848,507,625 | IssuesEvent | 2023-08-02 15:08:40 | safe-global/safe-ios | https://api.github.com/repos/safe-global/safe-ios | opened | Release 3.22.0 | infrastructure | - [ ] Create a release task in GitHub using the “New Release” template.
- [ ] Create and push the release branch
```
git checkout main -b release/3.22.0
git push -u origin release/3.22.0
```
- [ ] Marketing version is updated (3.22.0)
```
agvtool new-marketing-version 3.22.0
```
- [ ] Notify QA
- [ ] QA approved release candidate build
- [ ] Product Owner approved submission
**AFTER PRODUCT OWNER APPROVAL**
- [ ] Update screenshots in the App Store
- [ ] Submit to the App Store Review with developer approval for distribution
- [ ] Notify the team that release was submitted using the template below:
```
@here Hi everyone! We have submitted new iOS app v3.22.0 for review to the App Store.
```
- [ ] Create a new release in GitHub with release notes. This will create a tag. The tag should be in a format v3.22.0
#### Download DSYMs manually
- [ ] dSYMs are downloaded from AppStoreConnect and uploaded to Firebase Crashlytics.
```
# For the Multisig app (App Store version):
> ./bin/upload-symbols \
-gsp Multisig/Cross-layer/Analytics/Firebase/GoogleService-Info.Production.plist \
-p ios /path/to/dSYMs
```
#### Or download DSYMs with the script
- Install fastlane with `gem install fastlane --verbose`
- Set up the `fastlane` directory with configuraiton (ask team member to help). Do not commit the directory to the repository.
- Change the build version and build number in the `fastlane/upload_dsyms.sh` file
- Run the script `sh fastlane/upload_dsyms.sh`
#### Finally
- [ ] Release the app when it is approved by the App Store Review team (do not release on Thu/Fri). Notify the team using the following template:
```
@here Hi everyone! We have released the iOS app v3.22.0 to the App Store and it will soon be available for download.
```
- [ ] Merge the release branch to master branch via new pull-request
| 1.0 | Release 3.22.0 - - [ ] Create a release task in GitHub using the “New Release” template.
- [ ] Create and push the release branch
```
git checkout main -b release/3.22.0
git push -u origin release/3.22.0
```
- [ ] Marketing version is updated (3.22.0)
```
agvtool new-marketing-version 3.22.0
```
- [ ] Notify QA
- [ ] QA approved release candidate build
- [ ] Product Owner approved submission
**AFTER PRODUCT OWNER APPROVAL**
- [ ] Update screenshots in the App Store
- [ ] Submit to the App Store Review with developer approval for distribution
- [ ] Notify the team that release was submitted using the template below:
```
@here Hi everyone! We have submitted new iOS app v3.22.0 for review to the App Store.
```
- [ ] Create a new release in GitHub with release notes. This will create a tag. The tag should be in a format v3.22.0
#### Download DSYMs manually
- [ ] dSYMs are downloaded from AppStoreConnect and uploaded to Firebase Crashlytics.
```
# For the Multisig app (App Store version):
> ./bin/upload-symbols \
-gsp Multisig/Cross-layer/Analytics/Firebase/GoogleService-Info.Production.plist \
-p ios /path/to/dSYMs
```
#### Or download DSYMs with the script
- Install fastlane with `gem install fastlane --verbose`
- Set up the `fastlane` directory with configuraiton (ask team member to help). Do not commit the directory to the repository.
- Change the build version and build number in the `fastlane/upload_dsyms.sh` file
- Run the script `sh fastlane/upload_dsyms.sh`
#### Finally
- [ ] Release the app when it is approved by the App Store Review team (do not release on Thu/Fri). Notify the team using the following template:
```
@here Hi everyone! We have released the iOS app v3.22.0 to the App Store and it will soon be available for download.
```
- [ ] Merge the release branch to master branch via new pull-request
| infrastructure | release create a release task in github using the “new release” template create and push the release branch git checkout main b release git push u origin release marketing version is updated agvtool new marketing version notify qa qa approved release candidate build product owner approved submission after product owner approval update screenshots in the app store submit to the app store review with developer approval for distribution notify the team that release was submitted using the template below here hi everyone we have submitted new ios app for review to the app store create a new release in github with release notes this will create a tag the tag should be in a format download dsyms manually dsyms are downloaded from appstoreconnect and uploaded to firebase crashlytics for the multisig app app store version bin upload symbols gsp multisig cross layer analytics firebase googleservice info production plist p ios path to dsyms or download dsyms with the script install fastlane with gem install fastlane verbose set up the fastlane directory with configuraiton ask team member to help do not commit the directory to the repository change the build version and build number in the fastlane upload dsyms sh file run the script sh fastlane upload dsyms sh finally release the app when it is approved by the app store review team do not release on thu fri notify the team using the following template here hi everyone we have released the ios app to the app store and it will soon be available for download merge the release branch to master branch via new pull request | 1 |
2,532 | 3,739,303,093 | IssuesEvent | 2016-03-09 03:40:56 | dotnet/corefx | https://api.github.com/repos/dotnet/corefx | closed | Outer loop Win7 and Win10 builds failing consistently with various errors | Infrastructure | Outer loop builds are repeatedly failing with a variety of errors:
http://dotnet-ci.cloudapp.net/job/dotnet_corefx/job/outerloop_win7_debug/98/consoleText
http://dotnet-ci.cloudapp.net/job/dotnet_corefx/job/outerloop_win10_debug/104/consoleText
http://dotnet-ci.cloudapp.net/job/dotnet_corefx/job/outerloop_win7_release/94/consoleText
```
09:17:15 Installing dotnet cli...
09:17:16 Add-Type : Cannot add type. The assembly 'System.IO.Compression.FileSystem' cou
09:17:16 ld not be found.
09:17:16 At line:1 char:250
09:17:16 + (New-Object Net.WebClient).DownloadFile('https://dotnetcli.blob.core.windows.
09:17:16 net/dotnet/beta/Binaries/1.0.0.001504/dotnet-win-x64.1.0.0.001504.zip', 'd:\j\w
09:17:16 orkspace\outerloop_win---9c9e7d59\Tools\dotnetcli\dotnet-win-x64.1.0.0.001504.z
09:17:16 ip'); Add-Type <<<< -Assembly 'System.IO.Compression.FileSystem' -ErrorVariabl
09:17:16 e AddTypeErrors; if ($AddTypeErrors.Count -eq 0) { [System.IO.Compression.ZipFi
09:17:16 le]::ExtractToDirectory('d:\j\workspace\outerloop_win---9c9e7d59\Tools\dotnetcl
09:17:16 i\dotnet-win-x64.1.0.0.001504.zip', 'd:\j\workspace\outerloop_win---9c9e7d59\To
09:17:16 ols\dotnetcli\') } else { (New-Object -com shell.application).namespace('d:\j\w
09:17:16 orkspace\outerloop_win---9c9e7d59\Tools\dotnetcli\').CopyHere((new-object -com
09:17:16 shell.application).namespace('d:\j\workspace\outerloop_win---9c9e7d59\Tools\dot
09:17:16 netcli\dotnet-win-x64.1.0.0.001504.zip').Items(),16) }
09:17:16 + CategoryInfo : ObjectNotFound: (System.IO.Compression.FileSyste
09:17:16 m:String) [Add-Type], Exception
09:17:16 + FullyQualifiedErrorId : ASSEMBLY_NOT_FOUND,Microsoft.PowerShell.Commands
09:17:16 .AddTypeCommand
09:17:16
09:17:17 Add-Type : Cannot add type. One or more required assemblies are missing.
09:17:17 At line:1 char:250
09:17:17 + (New-Object Net.WebClient).DownloadFile('https://dotnetcli.blob.core.windows.
09:17:17 net/dotnet/beta/Binaries/1.0.0.001504/dotnet-win-x64.1.0.0.001504.zip', 'd:\j\w
09:17:17 orkspace\outerloop_win---9c9e7d59\Tools\dotnetcli\dotnet-win-x64.1.0.0.001504.z
09:17:17 ip'); Add-Type <<<< -Assembly 'System.IO.Compression.FileSystem' -ErrorVariabl
09:17:17 e AddTypeErrors; if ($AddTypeErrors.Count -eq 0) { [System.IO.Compression.ZipFi
09:17:17 le]::ExtractToDirectory('d:\j\workspace\outerloop_win---9c9e7d59\Tools\dotnetcl
09:17:17 i\dotnet-win-x64.1.0.0.001504.zip', 'd:\j\workspace\outerloop_win---9c9e7d59\To
09:17:17 ols\dotnetcli\') } else { (New-Object -com shell.application).namespace('d:\j\w
09:17:17 orkspace\outerloop_win---9c9e7d59\Tools\dotnetcli\').CopyHere((new-object -com
09:17:17 shell.application).namespace('d:\j\workspace\outerloop_win---9c9e7d59\Tools\dot
09:17:17 netcli\dotnet-win-x64.1.0.0.001504.zip').Items(),16) }
09:17:17 + CategoryInfo : InvalidData: (:) [Add-Type], InvalidOperationExc
09:17:17 eption
09:17:17 + FullyQualifiedErrorId : ASSEMBLY_LOAD_ERRORS,Microsoft.PowerShell.Comman
09:17:17 ds.AddTypeCommand
09:17:17
09:17:19 Restoring BuildTools version 1.0.25-prerelease-00177...
09:17:24 Initializing BuildTools ...
09:17:37 Done initializing tools.
09:17:37 [17:17:45.06] Building Native Libraries...
09:17:38 CMake is a pre-requisite to build this repository but it was not found on the path. Please install CMake from http://www.cmake.org/download/ and ensure it is on your path.
09:17:38 Native component build failed see nativebuild.log for more details.
09:17:38 [17:17:45.81] Building Managed Libraries...
09:17:39 [17:17:46.59] Restoring all packages...
09:21:19 [17:21:26.71] Restoring all packages...Done.
09:21:20 C:\Program Files (x86)\MSBuild\Microsoft\Portable\Microsoft.Portable.Core.targets(22,9): error : The TargetFrameworkProfile property is not set for project 'Microsoft.CSharp.csproj'. Portable projects must specify a profile. [d:\j\workspace\outerloop_win---9c9e7d59\src\Microsoft.CSharp\ref\Microsoft.CSharp.csproj]
09:21:21 C:\Program Files (x86)\MSBuild\Microsoft\Portable\Microsoft.Portable.Core.targets(22,9): error : The TargetFrameworkProfile property is not set for project 'Microsoft.VisualBasic.csproj'. Portable projects must specify a profile. [d:\j\workspace\outerloop_win---9c9e7d59\src\Microsoft.VisualBasic\ref\Microsoft.VisualBasic.csproj]
``` | 1.0 | Outer loop Win7 and Win10 builds failing consistently with various errors - Outer loop builds are repeatedly failing with a variety of errors:
http://dotnet-ci.cloudapp.net/job/dotnet_corefx/job/outerloop_win7_debug/98/consoleText
http://dotnet-ci.cloudapp.net/job/dotnet_corefx/job/outerloop_win10_debug/104/consoleText
http://dotnet-ci.cloudapp.net/job/dotnet_corefx/job/outerloop_win7_release/94/consoleText
```
09:17:15 Installing dotnet cli...
09:17:16 Add-Type : Cannot add type. The assembly 'System.IO.Compression.FileSystem' cou
09:17:16 ld not be found.
09:17:16 At line:1 char:250
09:17:16 + (New-Object Net.WebClient).DownloadFile('https://dotnetcli.blob.core.windows.
09:17:16 net/dotnet/beta/Binaries/1.0.0.001504/dotnet-win-x64.1.0.0.001504.zip', 'd:\j\w
09:17:16 orkspace\outerloop_win---9c9e7d59\Tools\dotnetcli\dotnet-win-x64.1.0.0.001504.z
09:17:16 ip'); Add-Type <<<< -Assembly 'System.IO.Compression.FileSystem' -ErrorVariabl
09:17:16 e AddTypeErrors; if ($AddTypeErrors.Count -eq 0) { [System.IO.Compression.ZipFi
09:17:16 le]::ExtractToDirectory('d:\j\workspace\outerloop_win---9c9e7d59\Tools\dotnetcl
09:17:16 i\dotnet-win-x64.1.0.0.001504.zip', 'd:\j\workspace\outerloop_win---9c9e7d59\To
09:17:16 ols\dotnetcli\') } else { (New-Object -com shell.application).namespace('d:\j\w
09:17:16 orkspace\outerloop_win---9c9e7d59\Tools\dotnetcli\').CopyHere((new-object -com
09:17:16 shell.application).namespace('d:\j\workspace\outerloop_win---9c9e7d59\Tools\dot
09:17:16 netcli\dotnet-win-x64.1.0.0.001504.zip').Items(),16) }
09:17:16 + CategoryInfo : ObjectNotFound: (System.IO.Compression.FileSyste
09:17:16 m:String) [Add-Type], Exception
09:17:16 + FullyQualifiedErrorId : ASSEMBLY_NOT_FOUND,Microsoft.PowerShell.Commands
09:17:16 .AddTypeCommand
09:17:16
09:17:17 Add-Type : Cannot add type. One or more required assemblies are missing.
09:17:17 At line:1 char:250
09:17:17 + (New-Object Net.WebClient).DownloadFile('https://dotnetcli.blob.core.windows.
09:17:17 net/dotnet/beta/Binaries/1.0.0.001504/dotnet-win-x64.1.0.0.001504.zip', 'd:\j\w
09:17:17 orkspace\outerloop_win---9c9e7d59\Tools\dotnetcli\dotnet-win-x64.1.0.0.001504.z
09:17:17 ip'); Add-Type <<<< -Assembly 'System.IO.Compression.FileSystem' -ErrorVariabl
09:17:17 e AddTypeErrors; if ($AddTypeErrors.Count -eq 0) { [System.IO.Compression.ZipFi
09:17:17 le]::ExtractToDirectory('d:\j\workspace\outerloop_win---9c9e7d59\Tools\dotnetcl
09:17:17 i\dotnet-win-x64.1.0.0.001504.zip', 'd:\j\workspace\outerloop_win---9c9e7d59\To
09:17:17 ols\dotnetcli\') } else { (New-Object -com shell.application).namespace('d:\j\w
09:17:17 orkspace\outerloop_win---9c9e7d59\Tools\dotnetcli\').CopyHere((new-object -com
09:17:17 shell.application).namespace('d:\j\workspace\outerloop_win---9c9e7d59\Tools\dot
09:17:17 netcli\dotnet-win-x64.1.0.0.001504.zip').Items(),16) }
09:17:17 + CategoryInfo : InvalidData: (:) [Add-Type], InvalidOperationExc
09:17:17 eption
09:17:17 + FullyQualifiedErrorId : ASSEMBLY_LOAD_ERRORS,Microsoft.PowerShell.Comman
09:17:17 ds.AddTypeCommand
09:17:17
09:17:19 Restoring BuildTools version 1.0.25-prerelease-00177...
09:17:24 Initializing BuildTools ...
09:17:37 Done initializing tools.
09:17:37 [17:17:45.06] Building Native Libraries...
09:17:38 CMake is a pre-requisite to build this repository but it was not found on the path. Please install CMake from http://www.cmake.org/download/ and ensure it is on your path.
09:17:38 Native component build failed see nativebuild.log for more details.
09:17:38 [17:17:45.81] Building Managed Libraries...
09:17:39 [17:17:46.59] Restoring all packages...
09:21:19 [17:21:26.71] Restoring all packages...Done.
09:21:20 C:\Program Files (x86)\MSBuild\Microsoft\Portable\Microsoft.Portable.Core.targets(22,9): error : The TargetFrameworkProfile property is not set for project 'Microsoft.CSharp.csproj'. Portable projects must specify a profile. [d:\j\workspace\outerloop_win---9c9e7d59\src\Microsoft.CSharp\ref\Microsoft.CSharp.csproj]
09:21:21 C:\Program Files (x86)\MSBuild\Microsoft\Portable\Microsoft.Portable.Core.targets(22,9): error : The TargetFrameworkProfile property is not set for project 'Microsoft.VisualBasic.csproj'. Portable projects must specify a profile. [d:\j\workspace\outerloop_win---9c9e7d59\src\Microsoft.VisualBasic\ref\Microsoft.VisualBasic.csproj]
``` | infrastructure | outer loop and builds failing consistently with various errors outer loop builds are repeatedly failing with a variety of errors installing dotnet cli add type cannot add type the assembly system io compression filesystem cou ld not be found at line char new object net webclient downloadfile net dotnet beta binaries dotnet win zip d j w orkspace outerloop win tools dotnetcli dotnet win z ip add type assembly system io compression filesystem errorvariabl e addtypeerrors if addtypeerrors count eq system io compression zipfi le extracttodirectory d j workspace outerloop win tools dotnetcl i dotnet win zip d j workspace outerloop win to ols dotnetcli else new object com shell application namespace d j w orkspace outerloop win tools dotnetcli copyhere new object com shell application namespace d j workspace outerloop win tools dot netcli dotnet win zip items categoryinfo objectnotfound system io compression filesyste m string exception fullyqualifiederrorid assembly not found microsoft powershell commands addtypecommand add type cannot add type one or more required assemblies are missing at line char new object net webclient downloadfile net dotnet beta binaries dotnet win zip d j w orkspace outerloop win tools dotnetcli dotnet win z ip add type assembly system io compression filesystem errorvariabl e addtypeerrors if addtypeerrors count eq system io compression zipfi le extracttodirectory d j workspace outerloop win tools dotnetcl i dotnet win zip d j workspace outerloop win to ols dotnetcli else new object com shell application namespace d j w orkspace outerloop win tools dotnetcli copyhere new object com shell application namespace d j workspace outerloop win tools dot netcli dotnet win zip items categoryinfo invaliddata invalidoperationexc eption fullyqualifiederrorid assembly load errors microsoft powershell comman ds addtypecommand restoring buildtools version prerelease initializing buildtools done initializing tools building native libraries cmake is a pre requisite to build this repository but it was not found on the path please install cmake from and ensure it is on your path native component build failed see nativebuild log for more details building managed libraries restoring all packages restoring all packages done c program files msbuild microsoft portable microsoft portable core targets error the targetframeworkprofile property is not set for project microsoft csharp csproj portable projects must specify a profile c program files msbuild microsoft portable microsoft portable core targets error the targetframeworkprofile property is not set for project microsoft visualbasic csproj portable projects must specify a profile | 1 |
30,252 | 24,700,256,284 | IssuesEvent | 2022-10-19 14:49:53 | dotnet/dotnet-docker | https://api.github.com/repos/dotnet/dotnet-docker | closed | Support a mix of public and internal .NET builds | area-infrastructure untriaged | The staged builds for pre-release versions of .NET can be a mix of both public and internal builds amongst the .NET components. For example, the SDK and ASP.NET Core builds may be available only in the internal blob container while the associated runtime build may be available in the public container. This is problematic because the current infrastructure for being able to target internal builds of .NET requires that everything be in the internal blob container.
This is made apparent when looking at these variables:
https://github.com/dotnet/dotnet-docker/blob/b946b525d1de42a3217e4c79e1a81e49fe5e5f21/manifest.versions.json#L57-L62
You can see that, for a given .NET version, it's all expected to be either public or internal. There's no differentiation of repo for these variables. All the Dockerfiles (SDK, aspnet, runtime) use the same variable.
In order to support this, each repo needs to have its own variable which indicates its public/internal state. The Dockerfiles for each of those repos would then reference its respective variable.
That's the easy part. The harder part would be the changes necessary to the update-dependencies tool so that it can appropriate set these variables. It would need to interrogate the availability of the build between the different blob containers to determine which one it was in.
The other option would be to always have builds which are copied to the public blob container also get copied to the internal blob container. But storage costs would likely be a concern with that approach, I'm assuming. Is that an option, @mmitche? | 1.0 | Support a mix of public and internal .NET builds - The staged builds for pre-release versions of .NET can be a mix of both public and internal builds amongst the .NET components. For example, the SDK and ASP.NET Core builds may be available only in the internal blob container while the associated runtime build may be available in the public container. This is problematic because the current infrastructure for being able to target internal builds of .NET requires that everything be in the internal blob container.
This is made apparent when looking at these variables:
https://github.com/dotnet/dotnet-docker/blob/b946b525d1de42a3217e4c79e1a81e49fe5e5f21/manifest.versions.json#L57-L62
You can see that, for a given .NET version, it's all expected to be either public or internal. There's no differentiation of repo for these variables. All the Dockerfiles (SDK, aspnet, runtime) use the same variable.
In order to support this, each repo needs to have its own variable which indicates its public/internal state. The Dockerfiles for each of those repos would then reference its respective variable.
That's the easy part. The harder part would be the changes necessary to the update-dependencies tool so that it can appropriate set these variables. It would need to interrogate the availability of the build between the different blob containers to determine which one it was in.
The other option would be to always have builds which are copied to the public blob container also get copied to the internal blob container. But storage costs would likely be a concern with that approach, I'm assuming. Is that an option, @mmitche? | infrastructure | support a mix of public and internal net builds the staged builds for pre release versions of net can be a mix of both public and internal builds amongst the net components for example the sdk and asp net core builds may be available only in the internal blob container while the associated runtime build may be available in the public container this is problematic because the current infrastructure for being able to target internal builds of net requires that everything be in the internal blob container this is made apparent when looking at these variables you can see that for a given net version it s all expected to be either public or internal there s no differentiation of repo for these variables all the dockerfiles sdk aspnet runtime use the same variable in order to support this each repo needs to have its own variable which indicates its public internal state the dockerfiles for each of those repos would then reference its respective variable that s the easy part the harder part would be the changes necessary to the update dependencies tool so that it can appropriate set these variables it would need to interrogate the availability of the build between the different blob containers to determine which one it was in the other option would be to always have builds which are copied to the public blob container also get copied to the internal blob container but storage costs would likely be a concern with that approach i m assuming is that an option mmitche | 1 |
24,620 | 17,468,591,018 | IssuesEvent | 2021-08-06 21:05:41 | sul-dlss/dlme-transform | https://api.github.com/repos/sul-dlss/dlme-transform | closed | Need method for deleting all records | infrastructure | As the DLME data manager, I occasionally need to delete all collections from dev or stage. The current interface
requires me to page through all transforms, find each one, and manually copy the url and paste it into the exhibit dashboard to delete it, then wait until all records are deleted from that collection before moving to the next collection. As the number of collections grow, this strategy is becoming increasingly untenable.
<img width="1205" alt="Screen Shot 2021-06-15 at 9 58 37 AM" src="https://user-images.githubusercontent.com/37662787/122066252-9872b000-cdc0-11eb-90bd-a96ee8873222.png">
- [ ] need a single-button option or a script-triggered option of deleting all records in any site. | 1.0 | Need method for deleting all records - As the DLME data manager, I occasionally need to delete all collections from dev or stage. The current interface
requires me to page through all transforms, find each one, and manually copy the url and paste it into the exhibit dashboard to delete it, then wait until all records are deleted from that collection before moving to the next collection. As the number of collections grow, this strategy is becoming increasingly untenable.
<img width="1205" alt="Screen Shot 2021-06-15 at 9 58 37 AM" src="https://user-images.githubusercontent.com/37662787/122066252-9872b000-cdc0-11eb-90bd-a96ee8873222.png">
- [ ] need a single-button option or a script-triggered option of deleting all records in any site. | infrastructure | need method for deleting all records as the dlme data manager i occasionally need to delete all collections from dev or stage the current interface requires me to page through all transforms find each one and manually copy the url and paste it into the exhibit dashboard to delete it then wait until all records are deleted from that collection before moving to the next collection as the number of collections grow this strategy is becoming increasingly untenable img width alt screen shot at am src need a single button option or a script triggered option of deleting all records in any site | 1 |
234,475 | 7,721,553,130 | IssuesEvent | 2018-05-24 06:03:29 | DashboardHub/PipelineDashboard | https://api.github.com/repos/DashboardHub/PipelineDashboard | closed | Deletes to have confirmation message (confirm/cancel) | priority: high size: 3 stack: ui | ### Requirements
All deletes to have confirmation message, so they can not get deleted by accident.
**UI**
- [x] Token delete
- [x] Monitor delete
- [ ] Environment delete
| 1.0 | Deletes to have confirmation message (confirm/cancel) - ### Requirements
All deletes to have confirmation message, so they can not get deleted by accident.
**UI**
- [x] Token delete
- [x] Monitor delete
- [ ] Environment delete
| non_infrastructure | deletes to have confirmation message confirm cancel requirements all deletes to have confirmation message so they can not get deleted by accident ui token delete monitor delete environment delete | 0 |
632,686 | 20,204,425,673 | IssuesEvent | 2022-02-11 18:34:34 | TeamSparker/Spark-iOS | https://api.github.com/repos/TeamSparker/Spark-iOS | closed | [FIX] 습관방 티켓 폰트수정 및 인증하기 바텀시트 문구 수정 | Fix 👼타락pOwEr천사현규 P1 / Priority High 🙈 QA(Quality Assurance) 🙉 | ## 📌 Issue
<!-- 이슈에 대해 간략하게 설명해주세요 -->
- 습관방 티켓 폰트수정 및 인증하기 바텀시트 문구 수정
## 📝 To-do
<!-- 진행할 작업에 대해 적어주세요 -->
- [x] 습관 인증하기 바텀시트에서 Keep going 로 문구 수정
- [x] 습관방 티켓 완료한 사람 라벨 폰트 수정
| 1.0 | [FIX] 습관방 티켓 폰트수정 및 인증하기 바텀시트 문구 수정 - ## 📌 Issue
<!-- 이슈에 대해 간략하게 설명해주세요 -->
- 습관방 티켓 폰트수정 및 인증하기 바텀시트 문구 수정
## 📝 To-do
<!-- 진행할 작업에 대해 적어주세요 -->
- [x] 습관 인증하기 바텀시트에서 Keep going 로 문구 수정
- [x] 습관방 티켓 완료한 사람 라벨 폰트 수정
| non_infrastructure | 습관방 티켓 폰트수정 및 인증하기 바텀시트 문구 수정 📌 issue 습관방 티켓 폰트수정 및 인증하기 바텀시트 문구 수정 📝 to do 습관 인증하기 바텀시트에서 keep going 로 문구 수정 습관방 티켓 완료한 사람 라벨 폰트 수정 | 0 |
172,505 | 21,047,098,038 | IssuesEvent | 2022-03-31 17:02:28 | samq-wsdemo/apache-roller | https://api.github.com/repos/samq-wsdemo/apache-roller | opened | CVE-2022-22965 (High) detected in spring-beans-5.3.5.jar | security vulnerability | ## CVE-2022-22965 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-beans-5.3.5.jar</b></p></summary>
<p>Spring Beans</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /app/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-beans/5.3.5/spring-beans-5.3.5.jar</p>
<p>
Dependency Hierarchy:
- spring-web-5.3.5.jar (Root Library)
- :x: **spring-beans-5.3.5.jar** (Vulnerable Library)
<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>
Spring Framework before 5.2.20 and 5.3.x before 5.3.18 are vulnerable due to a vulnerability in Spring-beans which allows attackers under certain circumstances to achieve remote code execution, this vulnerability is also known as ״Spring4Shell״ or ״SpringShell״. The current POC related to the attack is done by creating a specially crafted request which manipulates ClassLoader to successfully achieve RCE (Remote Code Execution). Please note that the ease of exploitation may diverge by the code implementation.Currently, the exploit requires JDK 9 or higher, Apache Tomcat as the Servlet container, the application Packaged as WAR, and dependency on spring-webmvc or spring-webflux. Spring Framework 5.3.18 and 5.2.20 have already been released. WhiteSource's research team is carefully observing developments and researching the case. We will keep updating this page and our WhiteSource resources with updates.
<p>Publish Date: 2022-01-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22965>CVE-2022-22965</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement">https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement</a></p>
<p>Release Date: 2022-01-11</p>
<p>Fix Resolution: org.springframework:spring-beans:5.2.20.RELEASE,5.3.18</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.springframework","packageName":"spring-beans","packageVersion":"5.3.5","packageFilePaths":["/app/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework:spring-web:5.3.5;org.springframework:spring-beans:5.3.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework:spring-beans:5.2.20.RELEASE,5.3.18","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2022-22965","vulnerabilityDetails":"Spring Framework before 5.2.20 and 5.3.x before 5.3.18 are vulnerable due to a vulnerability in Spring-beans which allows attackers under certain circumstances to achieve remote code execution, this vulnerability is also known as ״Spring4Shell״ or ״SpringShell״. The current POC related to the attack is done by creating a specially crafted request which manipulates ClassLoader to successfully achieve RCE (Remote Code Execution). Please note that the ease of exploitation may diverge by the code implementation.Currently, the exploit requires JDK 9 or higher, Apache Tomcat as the Servlet container, the application Packaged as WAR, and dependency on spring-webmvc or spring-webflux. Spring Framework 5.3.18 and 5.2.20 have already been released. WhiteSource\u0027s research team is carefully observing developments and researching the case. We will keep updating this page and our WhiteSource resources with updates.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22965","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2022-22965 (High) detected in spring-beans-5.3.5.jar - ## CVE-2022-22965 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-beans-5.3.5.jar</b></p></summary>
<p>Spring Beans</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /app/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-beans/5.3.5/spring-beans-5.3.5.jar</p>
<p>
Dependency Hierarchy:
- spring-web-5.3.5.jar (Root Library)
- :x: **spring-beans-5.3.5.jar** (Vulnerable Library)
<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>
Spring Framework before 5.2.20 and 5.3.x before 5.3.18 are vulnerable due to a vulnerability in Spring-beans which allows attackers under certain circumstances to achieve remote code execution, this vulnerability is also known as ״Spring4Shell״ or ״SpringShell״. The current POC related to the attack is done by creating a specially crafted request which manipulates ClassLoader to successfully achieve RCE (Remote Code Execution). Please note that the ease of exploitation may diverge by the code implementation.Currently, the exploit requires JDK 9 or higher, Apache Tomcat as the Servlet container, the application Packaged as WAR, and dependency on spring-webmvc or spring-webflux. Spring Framework 5.3.18 and 5.2.20 have already been released. WhiteSource's research team is carefully observing developments and researching the case. We will keep updating this page and our WhiteSource resources with updates.
<p>Publish Date: 2022-01-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22965>CVE-2022-22965</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement">https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement</a></p>
<p>Release Date: 2022-01-11</p>
<p>Fix Resolution: org.springframework:spring-beans:5.2.20.RELEASE,5.3.18</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.springframework","packageName":"spring-beans","packageVersion":"5.3.5","packageFilePaths":["/app/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework:spring-web:5.3.5;org.springframework:spring-beans:5.3.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework:spring-beans:5.2.20.RELEASE,5.3.18","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2022-22965","vulnerabilityDetails":"Spring Framework before 5.2.20 and 5.3.x before 5.3.18 are vulnerable due to a vulnerability in Spring-beans which allows attackers under certain circumstances to achieve remote code execution, this vulnerability is also known as ״Spring4Shell״ or ״SpringShell״. The current POC related to the attack is done by creating a specially crafted request which manipulates ClassLoader to successfully achieve RCE (Remote Code Execution). Please note that the ease of exploitation may diverge by the code implementation.Currently, the exploit requires JDK 9 or higher, Apache Tomcat as the Servlet container, the application Packaged as WAR, and dependency on spring-webmvc or spring-webflux. Spring Framework 5.3.18 and 5.2.20 have already been released. WhiteSource\u0027s research team is carefully observing developments and researching the case. We will keep updating this page and our WhiteSource resources with updates.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22965","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_infrastructure | cve high detected in spring beans jar cve high severity vulnerability vulnerable library spring beans jar spring beans library home page a href path to dependency file app pom xml path to vulnerable library home wss scanner repository org springframework spring beans spring beans jar dependency hierarchy spring web jar root library x spring beans jar vulnerable library found in base branch master vulnerability details spring framework before and x before are vulnerable due to a vulnerability in spring beans which allows attackers under certain circumstances to achieve remote code execution this vulnerability is also known as ״ ״ or ״springshell״ the current poc related to the attack is done by creating a specially crafted request which manipulates classloader to successfully achieve rce remote code execution please note that the ease of exploitation may diverge by the code implementation currently the exploit requires jdk or higher apache tomcat as the servlet container the application packaged as war and dependency on spring webmvc or spring webflux spring framework and have already been released whitesource s research team is carefully observing developments and researching the case we will keep updating this page and our whitesource resources with updates publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org springframework spring beans release isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree org springframework spring web org springframework spring beans isminimumfixversionavailable true minimumfixversion org springframework spring beans release isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails spring framework before and x before are vulnerable due to a vulnerability in spring beans which allows attackers under certain circumstances to achieve remote code execution this vulnerability is also known as ״ ״ or ״springshell״ the current poc related to the attack is done by creating a specially crafted request which manipulates classloader to successfully achieve rce remote code execution please note that the ease of exploitation may diverge by the code implementation currently the exploit requires jdk or higher apache tomcat as the servlet container the application packaged as war and dependency on spring webmvc or spring webflux spring framework and have already been released whitesource research team is carefully observing developments and researching the case we will keep updating this page and our whitesource resources with updates vulnerabilityurl | 0 |
12,580 | 9,855,484,252 | IssuesEvent | 2019-06-19 19:31:37 | raiden-network/raiden | https://api.github.com/repos/raiden-network/raiden | closed | (Nightly) Release upload to DigitalOcean spaces bucket is slow | infrastructure | ## Problem Definition
In the CI job that uploads the nightly and release builds to our DigitalOcean Spaces bucket we use `s3cmd`'s `sync` subcommand.
This takes an ever increasing amount of time since it needs to enumerate all items on the remote side before upload (currently [about 6:30](https://circleci.com/gh/raiden-network/raiden/47853) min).
Since we don't actually want to sync but just upload we should switch to the `cp` subcommand with the `--recursive` option (c.f. [SO answer](https://stackoverflow.com/a/41836652/107946)) | 1.0 | (Nightly) Release upload to DigitalOcean spaces bucket is slow - ## Problem Definition
In the CI job that uploads the nightly and release builds to our DigitalOcean Spaces bucket we use `s3cmd`'s `sync` subcommand.
This takes an ever increasing amount of time since it needs to enumerate all items on the remote side before upload (currently [about 6:30](https://circleci.com/gh/raiden-network/raiden/47853) min).
Since we don't actually want to sync but just upload we should switch to the `cp` subcommand with the `--recursive` option (c.f. [SO answer](https://stackoverflow.com/a/41836652/107946)) | infrastructure | nightly release upload to digitalocean spaces bucket is slow problem definition in the ci job that uploads the nightly and release builds to our digitalocean spaces bucket we use s sync subcommand this takes an ever increasing amount of time since it needs to enumerate all items on the remote side before upload currently min since we don t actually want to sync but just upload we should switch to the cp subcommand with the recursive option c f | 1 |
12,540 | 9,817,485,495 | IssuesEvent | 2019-06-13 16:50:28 | volta-cli/volta | https://api.github.com/repos/volta-cli/volta | closed | Windows installer isn't uninstalling completely | bug infrastructure | The Windows installer isn't properly deleting the Node installation directories on uninstall. | 1.0 | Windows installer isn't uninstalling completely - The Windows installer isn't properly deleting the Node installation directories on uninstall. | infrastructure | windows installer isn t uninstalling completely the windows installer isn t properly deleting the node installation directories on uninstall | 1 |
80,308 | 15,586,276,160 | IssuesEvent | 2021-03-18 01:34:18 | venkateshreddypala/aircraft | https://api.github.com/repos/venkateshreddypala/aircraft | opened | CVE-2021-25329 (High) detected in tomcat-embed-core-8.5.28.jar | security vulnerability | ## CVE-2021-25329 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-8.5.28.jar</b></p></summary>
<p>Core Tomcat implementation</p>
<p>Library home page: <a href="http://tomcat.apache.org/">http://tomcat.apache.org/</a></p>
<p>Path to dependency file: /aircraft/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.28/tomcat-embed-core-8.5.28.jar</p>
<p>
Dependency Hierarchy:
- spring-cloud-config-server-2.0.0.M9.jar (Root Library)
- spring-boot-starter-web-2.0.0.RELEASE.jar
- spring-boot-starter-tomcat-2.0.0.RELEASE.jar
- :x: **tomcat-embed-core-8.5.28.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>
The fix for CVE-2020-9484 was incomplete. When using Apache Tomcat 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41, 8.5.0 to 8.5.61 or 7.0.0. to 7.0.107 with a configuration edge case that was highly unlikely to be used, the Tomcat instance was still vulnerable to CVE-2020-9494. Note that both the previously published prerequisites for CVE-2020-9484 and the previously published mitigations for CVE-2020-9484 also apply to this issue.
<p>Publish Date: 2021-03-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-25329>CVE-2021-25329</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.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf%40%3Cannounce.tomcat.apache.org%3E">https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2021-03-01</p>
<p>Fix Resolution: org.apache.tomcat:tomcat:7.0.108, org.apache.tomcat:tomcat:8.5.63, org.apache.tomcat:tomcat:9.0.43,org.apache.tomcat:tomcat:10.0.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-25329 (High) detected in tomcat-embed-core-8.5.28.jar - ## CVE-2021-25329 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-8.5.28.jar</b></p></summary>
<p>Core Tomcat implementation</p>
<p>Library home page: <a href="http://tomcat.apache.org/">http://tomcat.apache.org/</a></p>
<p>Path to dependency file: /aircraft/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.28/tomcat-embed-core-8.5.28.jar</p>
<p>
Dependency Hierarchy:
- spring-cloud-config-server-2.0.0.M9.jar (Root Library)
- spring-boot-starter-web-2.0.0.RELEASE.jar
- spring-boot-starter-tomcat-2.0.0.RELEASE.jar
- :x: **tomcat-embed-core-8.5.28.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>
The fix for CVE-2020-9484 was incomplete. When using Apache Tomcat 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41, 8.5.0 to 8.5.61 or 7.0.0. to 7.0.107 with a configuration edge case that was highly unlikely to be used, the Tomcat instance was still vulnerable to CVE-2020-9494. Note that both the previously published prerequisites for CVE-2020-9484 and the previously published mitigations for CVE-2020-9484 also apply to this issue.
<p>Publish Date: 2021-03-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-25329>CVE-2021-25329</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.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf%40%3Cannounce.tomcat.apache.org%3E">https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2021-03-01</p>
<p>Fix Resolution: org.apache.tomcat:tomcat:7.0.108, org.apache.tomcat:tomcat:8.5.63, org.apache.tomcat:tomcat:9.0.43,org.apache.tomcat:tomcat:10.0.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_infrastructure | cve high detected in tomcat embed core jar cve high severity vulnerability vulnerable library tomcat embed core jar core tomcat implementation library home page a href path to dependency file aircraft pom xml path to vulnerable library root repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring cloud config server jar root library spring boot starter web release jar spring boot starter tomcat release jar x tomcat embed core jar vulnerable library vulnerability details the fix for cve was incomplete when using apache tomcat to to to or to with a configuration edge case that was highly unlikely to be used the tomcat instance was still vulnerable to cve note that both the previously published prerequisites for cve and the previously published mitigations for cve also apply to this issue publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache tomcat tomcat org apache tomcat tomcat org apache tomcat tomcat org apache tomcat tomcat step up your open source security game with whitesource | 0 |
304,029 | 23,048,205,950 | IssuesEvent | 2022-07-24 08:13:18 | CAFECA-IO/iSunTV-Live | https://api.github.com/repos/CAFECA-IO/iSunTV-Live | closed | SendMail API Sequence Diagram 調整 | documentation 1 | 將 Sendmail api 加入 googleapijs pkg 並做調整
調整 api refresh token ( 加上 使用 use config and get google oauth2 refresh token) | 1.0 | SendMail API Sequence Diagram 調整 - 將 Sendmail api 加入 googleapijs pkg 並做調整
調整 api refresh token ( 加上 使用 use config and get google oauth2 refresh token) | non_infrastructure | sendmail api sequence diagram 調整 將 sendmail api 加入 googleapijs pkg 並做調整 調整 api refresh token 加上 使用 use config and get google refresh token | 0 |
11,471 | 9,203,337,912 | IssuesEvent | 2019-03-08 02:00:41 | GSA/datagov-deploy | https://api.github.com/repos/GSA/datagov-deploy | closed | Create: Subsidiary Elasticsearch repository | To Be Prioritized infrastructure refactored-functionality search server | Create subsidiary ElasticSearch repository.
Name: datagov-deploy-elasticsearch
Parent to #355,
Parent to #357,
Parent to #359 | 1.0 | Create: Subsidiary Elasticsearch repository - Create subsidiary ElasticSearch repository.
Name: datagov-deploy-elasticsearch
Parent to #355,
Parent to #357,
Parent to #359 | infrastructure | create subsidiary elasticsearch repository create subsidiary elasticsearch repository name datagov deploy elasticsearch parent to parent to parent to | 1 |
5,943 | 3,700,527,900 | IssuesEvent | 2016-02-29 09:00:12 | BladeRunnerJS/brjs | https://api.github.com/repos/BladeRunnerJS/brjs | opened | Fix the release to github jenkins build | 1 - Planned build | this has been broken for months and is making releases a pain | 1.0 | Fix the release to github jenkins build - this has been broken for months and is making releases a pain | non_infrastructure | fix the release to github jenkins build this has been broken for months and is making releases a pain | 0 |
97,856 | 28,780,629,051 | IssuesEvent | 2023-05-02 00:07:09 | 9mbs/calendar-widgets | https://api.github.com/repos/9mbs/calendar-widgets | closed | Deprecate the `eslint-config` package | help wanted good first issue depreciation build system | We've opted to not use a monorepo, and to instead keep everything in the root dir. this package is no longer needed and is not serving any beneficial purpose
- [ ] replace the root eslint extension `@calendar-widgets/eslint-config` with the rules defined in it
- [ ] delete the `workspaces/eslint-config`
- [ ] uninstall the package from the root package.json | 1.0 | Deprecate the `eslint-config` package - We've opted to not use a monorepo, and to instead keep everything in the root dir. this package is no longer needed and is not serving any beneficial purpose
- [ ] replace the root eslint extension `@calendar-widgets/eslint-config` with the rules defined in it
- [ ] delete the `workspaces/eslint-config`
- [ ] uninstall the package from the root package.json | non_infrastructure | deprecate the eslint config package we ve opted to not use a monorepo and to instead keep everything in the root dir this package is no longer needed and is not serving any beneficial purpose replace the root eslint extension calendar widgets eslint config with the rules defined in it delete the workspaces eslint config uninstall the package from the root package json | 0 |
35,099 | 30,752,925,747 | IssuesEvent | 2023-07-28 21:14:53 | KhronosGroup/glslang | https://api.github.com/repos/KhronosGroup/glslang | closed | Remove the GLSLANG_WEB build define? | enhancement Infrastructure | The `GLSLANG_WEB` build configuration was added early in the WebGPU lifetime. The WGSL spec has changed since it was added so there is a good chance it is no longer valid with what WebGPU expects from SPIR-V.
The usage of the build configuration is also very invasive and makes the code difficult to work with.
@dneto0 | 1.0 | Remove the GLSLANG_WEB build define? - The `GLSLANG_WEB` build configuration was added early in the WebGPU lifetime. The WGSL spec has changed since it was added so there is a good chance it is no longer valid with what WebGPU expects from SPIR-V.
The usage of the build configuration is also very invasive and makes the code difficult to work with.
@dneto0 | infrastructure | remove the glslang web build define the glslang web build configuration was added early in the webgpu lifetime the wgsl spec has changed since it was added so there is a good chance it is no longer valid with what webgpu expects from spir v the usage of the build configuration is also very invasive and makes the code difficult to work with | 1 |
323,933 | 9,880,711,649 | IssuesEvent | 2019-06-24 13:14:46 | prysmaticlabs/prysm | https://api.github.com/repos/prysmaticlabs/prysm | opened | Add support for cross compilation in Bazel | Good For Bounty Help Wanted Priority: Medium | Currently, we're unable to build for other OS / architecture whenever the binary target depends on a cgo library. This includes any dependency on go-ethereum in the beacon-chain and potentially a future BLS library.
To reproduce the issue, try building the beacon chain with a different toolchain specified.
Building in on linux targeting windows:
```
bazel build --platforms=@io_bazel_rules_go//go/toolchain:windows_amd64 //beacon-chain
```
Building on linux amd64 targeting arm64.
```
bazel build --platforms=@io_bazel_rules_go//go/toolchain:linux_arm64 //beacon-chain
```
Important caveats:
- We're using a [fork of go-ethereum](https://github.com/prysmaticlabs/bazel-go-ethereum) which has the generated BUILD files to support bazel.
- Removing cgo dependencies are not an option as we expect to have more cgo dependencies in the future. Pure go builds would be nice and we'd have support for windows / ARM from linux today if that were the case!
- We must support linux -> [darwin_amd64, arm64, windows_amd64] targets. When you're writing cc toolchains, adding Mac OS as the host is optional, but appreciated (expect a bounty tip if Mac OS as host is supported!).
- This is a pretty involved task. If you are up to taking it on, you'll be mostly on your own to figure it out. Good luck :)
These blocked issues may have some additional context from previous attempts to resolve this.
Blocking #654
Blocking #2546 | 1.0 | Add support for cross compilation in Bazel - Currently, we're unable to build for other OS / architecture whenever the binary target depends on a cgo library. This includes any dependency on go-ethereum in the beacon-chain and potentially a future BLS library.
To reproduce the issue, try building the beacon chain with a different toolchain specified.
Building in on linux targeting windows:
```
bazel build --platforms=@io_bazel_rules_go//go/toolchain:windows_amd64 //beacon-chain
```
Building on linux amd64 targeting arm64.
```
bazel build --platforms=@io_bazel_rules_go//go/toolchain:linux_arm64 //beacon-chain
```
Important caveats:
- We're using a [fork of go-ethereum](https://github.com/prysmaticlabs/bazel-go-ethereum) which has the generated BUILD files to support bazel.
- Removing cgo dependencies are not an option as we expect to have more cgo dependencies in the future. Pure go builds would be nice and we'd have support for windows / ARM from linux today if that were the case!
- We must support linux -> [darwin_amd64, arm64, windows_amd64] targets. When you're writing cc toolchains, adding Mac OS as the host is optional, but appreciated (expect a bounty tip if Mac OS as host is supported!).
- This is a pretty involved task. If you are up to taking it on, you'll be mostly on your own to figure it out. Good luck :)
These blocked issues may have some additional context from previous attempts to resolve this.
Blocking #654
Blocking #2546 | non_infrastructure | add support for cross compilation in bazel currently we re unable to build for other os architecture whenever the binary target depends on a cgo library this includes any dependency on go ethereum in the beacon chain and potentially a future bls library to reproduce the issue try building the beacon chain with a different toolchain specified building in on linux targeting windows bazel build platforms io bazel rules go go toolchain windows beacon chain building on linux targeting bazel build platforms io bazel rules go go toolchain linux beacon chain important caveats we re using a which has the generated build files to support bazel removing cgo dependencies are not an option as we expect to have more cgo dependencies in the future pure go builds would be nice and we d have support for windows arm from linux today if that were the case we must support linux targets when you re writing cc toolchains adding mac os as the host is optional but appreciated expect a bounty tip if mac os as host is supported this is a pretty involved task if you are up to taking it on you ll be mostly on your own to figure it out good luck these blocked issues may have some additional context from previous attempts to resolve this blocking blocking | 0 |
22,131 | 30,674,734,551 | IssuesEvent | 2023-07-26 03:35:47 | open-telemetry/opentelemetry-collector-contrib | https://api.github.com/repos/open-telemetry/opentelemetry-collector-contrib | closed | [processor/filter] enable expr evaluation on non-string type metric labels | enhancement Stale priority:p2 processor/filter | **Is your feature request related to a problem? Please describe.**
As of v0.64.0, expr in the filter processor cannot properly evaluate metric labels that are not string type.
**Describe the solution you'd like**
I would like to filter based non-string metric labels. For example:
```yaml
filter:
metrics:
exclude:
match_type: expr
expressions:
- Label("my_boolean_attribute") == true
```
Changes would be centered around the [Label method for the env of the expr filter matcher](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/v0.64.0/internal/coreinternal/processor/filterexpr/matcher.go#L42-L45). Specifically, `v.Str()` [returns an empty string if the attribute is not of type string](https://github.com/open-telemetry/opentelemetry-collector/blob/pdata/v0.64.0/pdata/pcommon/common.go#L203).
Ideally, the Label method would return the appropriate value type by using [`AsRaw()`](https://pkg.go.dev/go.opentelemetry.io/collector/pdata@v0.64.0/pcommon#Value.AsRaw).
Alternatively, `v.StringVal()` can be replaced with `v.AsString()`. While AsString would still require evaluating all attributes as strings (e.g. `Label("my_boolean_attribute") == "true"`) this is an improvement over the empty string returned by StringVal. | 1.0 | [processor/filter] enable expr evaluation on non-string type metric labels - **Is your feature request related to a problem? Please describe.**
As of v0.64.0, expr in the filter processor cannot properly evaluate metric labels that are not string type.
**Describe the solution you'd like**
I would like to filter based non-string metric labels. For example:
```yaml
filter:
metrics:
exclude:
match_type: expr
expressions:
- Label("my_boolean_attribute") == true
```
Changes would be centered around the [Label method for the env of the expr filter matcher](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/v0.64.0/internal/coreinternal/processor/filterexpr/matcher.go#L42-L45). Specifically, `v.Str()` [returns an empty string if the attribute is not of type string](https://github.com/open-telemetry/opentelemetry-collector/blob/pdata/v0.64.0/pdata/pcommon/common.go#L203).
Ideally, the Label method would return the appropriate value type by using [`AsRaw()`](https://pkg.go.dev/go.opentelemetry.io/collector/pdata@v0.64.0/pcommon#Value.AsRaw).
Alternatively, `v.StringVal()` can be replaced with `v.AsString()`. While AsString would still require evaluating all attributes as strings (e.g. `Label("my_boolean_attribute") == "true"`) this is an improvement over the empty string returned by StringVal. | non_infrastructure | enable expr evaluation on non string type metric labels is your feature request related to a problem please describe as of expr in the filter processor cannot properly evaluate metric labels that are not string type describe the solution you d like i would like to filter based non string metric labels for example yaml filter metrics exclude match type expr expressions label my boolean attribute true changes would be centered around the specifically v str ideally the label method would return the appropriate value type by using alternatively v stringval can be replaced with v asstring while asstring would still require evaluating all attributes as strings e g label my boolean attribute true this is an improvement over the empty string returned by stringval | 0 |
80,041 | 23,098,001,951 | IssuesEvent | 2022-07-26 21:46:30 | lightninglabs/lnc-web | https://api.github.com/repos/lightninglabs/lnc-web | closed | Package is being built in development environment | troubleshooting build system | Hey folks, I am experimenting with lnc-web and ran into eval() issues with a web extension. I was running WASM in the wrong script but noticed this package isn't being built in production mode.
```
mode: process.env.NODE_ENV === 'production' ? 'production' : 'development',
```
This makes sense but you are not setting NODE_ENV anywhere in the CI pipeline which results in the mode being set to `development`. This mode results in the following: https://github.com/webpack/webpack/blob/c181294865dca01b28e6e316636fef5f2aad4eb6/lib/config/defaults.js#L155
devtool running in `eval` mode is not ideal and it is not recommended for production to use `false`. (https://webpack.js.org/configuration/devtool/#devtool)
Solution:
Change `"prepare": "npm run build"` --> `"prepare": "NODE_ENV=production npm run build",`
Can submit a PR unless I am missing something.
| 1.0 | Package is being built in development environment - Hey folks, I am experimenting with lnc-web and ran into eval() issues with a web extension. I was running WASM in the wrong script but noticed this package isn't being built in production mode.
```
mode: process.env.NODE_ENV === 'production' ? 'production' : 'development',
```
This makes sense but you are not setting NODE_ENV anywhere in the CI pipeline which results in the mode being set to `development`. This mode results in the following: https://github.com/webpack/webpack/blob/c181294865dca01b28e6e316636fef5f2aad4eb6/lib/config/defaults.js#L155
devtool running in `eval` mode is not ideal and it is not recommended for production to use `false`. (https://webpack.js.org/configuration/devtool/#devtool)
Solution:
Change `"prepare": "npm run build"` --> `"prepare": "NODE_ENV=production npm run build",`
Can submit a PR unless I am missing something.
| non_infrastructure | package is being built in development environment hey folks i am experimenting with lnc web and ran into eval issues with a web extension i was running wasm in the wrong script but noticed this package isn t being built in production mode mode process env node env production production development this makes sense but you are not setting node env anywhere in the ci pipeline which results in the mode being set to development this mode results in the following devtool running in eval mode is not ideal and it is not recommended for production to use false solution change prepare npm run build prepare node env production npm run build can submit a pr unless i am missing something | 0 |
15,614 | 11,615,542,261 | IssuesEvent | 2020-02-26 14:22:54 | microsoft/WindowsTemplateStudio | https://api.github.com/repos/microsoft/WindowsTemplateStudio | opened | Remove WTS support for Visual Studio 2017 | Infrastructure | Visual Studio 2017 usage is below 10 % and is blocking us from updating the SQL And WebAPI templates to the recommended version of .net core (3.1).
| 1.0 | Remove WTS support for Visual Studio 2017 - Visual Studio 2017 usage is below 10 % and is blocking us from updating the SQL And WebAPI templates to the recommended version of .net core (3.1).
| infrastructure | remove wts support for visual studio visual studio usage is below and is blocking us from updating the sql and webapi templates to the recommended version of net core | 1 |
95,282 | 19,686,184,477 | IssuesEvent | 2022-01-11 22:29:49 | microsoft/vscode-python | https://api.github.com/repos/microsoft/vscode-python | closed | Use Python 3.7 to generate the requirements files | needs PR code-health area-internal | <!-- **PLEASE** look for preexisting feature requests before opening a new one as a 👍 on a preexisting issue is more important than opening a new issue or leaving a comment. -->
Now that Python 3.6 has reached EOL, we need to re-generate the requirements.in and requirements.txt files to support Python 3.7 and higher. | 1.0 | Use Python 3.7 to generate the requirements files - <!-- **PLEASE** look for preexisting feature requests before opening a new one as a 👍 on a preexisting issue is more important than opening a new issue or leaving a comment. -->
Now that Python 3.6 has reached EOL, we need to re-generate the requirements.in and requirements.txt files to support Python 3.7 and higher. | non_infrastructure | use python to generate the requirements files now that python has reached eol we need to re generate the requirements in and requirements txt files to support python and higher | 0 |
9,158 | 7,844,572,314 | IssuesEvent | 2018-06-19 10:02:52 | saros-project/saros | https://api.github.com/repos/saros-project/saros | closed | Create nightly stf test in travis | infrastructure | In order to decouple the infrastructure from the Freie Universität, it is useful to create a stf test pipeline which is independent from the VMs of the Freie Universität. A possible solution is a docker setup. | 1.0 | Create nightly stf test in travis - In order to decouple the infrastructure from the Freie Universität, it is useful to create a stf test pipeline which is independent from the VMs of the Freie Universität. A possible solution is a docker setup. | infrastructure | create nightly stf test in travis in order to decouple the infrastructure from the freie universität it is useful to create a stf test pipeline which is independent from the vms of the freie universität a possible solution is a docker setup | 1 |
14,193 | 10,698,000,964 | IssuesEvent | 2019-10-23 17:44:33 | InsightSoftwareConsortium/ITK | https://api.github.com/repos/InsightSoftwareConsortium/ITK | closed | Relax clang-format version from 8.0.1 to just 8.0.x | type:Infrastructure | ### Description
I don't think the format changes in clang-format patch versions, and the tools are typically named without the patch version, so is 8.0.1 too much
See PR #1201 that over-prescribes the version of clang-format.
### Impact analysis
### Expected behavior
Any 8.0.x version of clang-format should work.
### Actual behavior
Explicitly require 8.0.1 for the moment.
| 1.0 | Relax clang-format version from 8.0.1 to just 8.0.x - ### Description
I don't think the format changes in clang-format patch versions, and the tools are typically named without the patch version, so is 8.0.1 too much
See PR #1201 that over-prescribes the version of clang-format.
### Impact analysis
### Expected behavior
Any 8.0.x version of clang-format should work.
### Actual behavior
Explicitly require 8.0.1 for the moment.
| infrastructure | relax clang format version from to just x description i don t think the format changes in clang format patch versions and the tools are typically named without the patch version so is too much see pr that over prescribes the version of clang format impact analysis expected behavior any x version of clang format should work actual behavior explicitly require for the moment | 1 |
270,905 | 20,614,257,163 | IssuesEvent | 2022-03-07 11:38:21 | jamal919/bandsos | https://api.github.com/repos/jamal919/bandsos | closed | :memo: Missing project information | documentation | The project information is missing. A small description can be found here - https://www.spaceclimateobservatory.org/band-sos-bengal-delta - for the first version. | 1.0 | :memo: Missing project information - The project information is missing. A small description can be found here - https://www.spaceclimateobservatory.org/band-sos-bengal-delta - for the first version. | non_infrastructure | memo missing project information the project information is missing a small description can be found here for the first version | 0 |
32,312 | 26,620,883,974 | IssuesEvent | 2023-01-24 11:07:39 | AndreTerra5348/appointment | https://api.github.com/repos/AndreTerra5348/appointment | closed | Add Appointment model | layer: infrastructure spec: low level | ### Description
- The model represents a scheduled appointment for the database
- The model shall extends [`Table`](https://drift.simonbinder.eu/docs/getting-started/advanced_dart_tables/) from [Drift package](https://pub.dev/packages/drift)
### Properties
- startDate: [`DateTimeColumn`](https://pub.dev/documentation/drift/latest/drift/DateTimeColumn.html)
- endDate: [`DateTimeColumn`](https://pub.dev/documentation/drift/latest/drift/DateTimeColumn.html)
### Depends on
-
### Part of
- #25 | 1.0 | Add Appointment model - ### Description
- The model represents a scheduled appointment for the database
- The model shall extends [`Table`](https://drift.simonbinder.eu/docs/getting-started/advanced_dart_tables/) from [Drift package](https://pub.dev/packages/drift)
### Properties
- startDate: [`DateTimeColumn`](https://pub.dev/documentation/drift/latest/drift/DateTimeColumn.html)
- endDate: [`DateTimeColumn`](https://pub.dev/documentation/drift/latest/drift/DateTimeColumn.html)
### Depends on
-
### Part of
- #25 | infrastructure | add appointment model description the model represents a scheduled appointment for the database the model shall extends from properties startdate enddate depends on part of | 1 |
341,965 | 10,310,207,269 | IssuesEvent | 2019-08-29 14:44:36 | hotosm/tasking-manager | https://api.github.com/repos/hotosm/tasking-manager | closed | Allow trailing backslashes in routes | Component: Backend Difficulty: Easy Priority: Low Type: Enhancement | Taking this comment from @eternaltyro in https://github.com/hotosm/tasking-manager/pull/1742#issuecomment-515911059
> This is a flask idiosyncrasy. Quoting flask documentation:
>
>> An important detail to keep in mind is how Flask deals with trailing slashes. The idea is to keep each URL unique so the following rules apply:
>>
>> If a rule ends with a slash and is requested without a slash by the user, the user is automatically redirected to the same page with a trailing slash attached.
>>
>> If a rule does not end with a trailing slash and the user requests the page with a trailing slash, a 404 not found is raised.
>>
> I think we should make trailing slashes to be seamlessly redirected to path without trailing slashes. It is general convention to do so. | 1.0 | Allow trailing backslashes in routes - Taking this comment from @eternaltyro in https://github.com/hotosm/tasking-manager/pull/1742#issuecomment-515911059
> This is a flask idiosyncrasy. Quoting flask documentation:
>
>> An important detail to keep in mind is how Flask deals with trailing slashes. The idea is to keep each URL unique so the following rules apply:
>>
>> If a rule ends with a slash and is requested without a slash by the user, the user is automatically redirected to the same page with a trailing slash attached.
>>
>> If a rule does not end with a trailing slash and the user requests the page with a trailing slash, a 404 not found is raised.
>>
> I think we should make trailing slashes to be seamlessly redirected to path without trailing slashes. It is general convention to do so. | non_infrastructure | allow trailing backslashes in routes taking this comment from eternaltyro in this is a flask idiosyncrasy quoting flask documentation an important detail to keep in mind is how flask deals with trailing slashes the idea is to keep each url unique so the following rules apply if a rule ends with a slash and is requested without a slash by the user the user is automatically redirected to the same page with a trailing slash attached if a rule does not end with a trailing slash and the user requests the page with a trailing slash a not found is raised i think we should make trailing slashes to be seamlessly redirected to path without trailing slashes it is general convention to do so | 0 |
107,703 | 9,221,380,454 | IssuesEvent | 2019-03-11 19:50:08 | ktraunmueller/Compositor | https://api.github.com/repos/ktraunmueller/Compositor | opened | No paragraph inserted when pressing Return | automated test bug | In the following case, pressing Return at the caret position does not insert a new paragraph after the bulleted list:
<img width="777" alt="Screenshot 2019-03-11 at 20 49 23" src="https://user-images.githubusercontent.com/650763/54153164-2ff93380-443f-11e9-9700-a8bc01c115da.png">
| 1.0 | No paragraph inserted when pressing Return - In the following case, pressing Return at the caret position does not insert a new paragraph after the bulleted list:
<img width="777" alt="Screenshot 2019-03-11 at 20 49 23" src="https://user-images.githubusercontent.com/650763/54153164-2ff93380-443f-11e9-9700-a8bc01c115da.png">
| non_infrastructure | no paragraph inserted when pressing return in the following case pressing return at the caret position does not insert a new paragraph after the bulleted list img width alt screenshot at src | 0 |
23,058 | 15,786,364,574 | IssuesEvent | 2021-04-01 17:38:37 | google/site-kit-wp | https://api.github.com/repos/google/site-kit-wp | opened | Storybook stories for setup broken | P1 Type: Infrastructure | ## Bug Description
The Storybook stories for setup using proxy always show the error from the compatibility checks, even for the standard cases where there should be no error. Furthermore, the tracking opt-in checkbox UI is missing from all of these stories.
---------------
_Do not alter or remove anything below. The following sections will be managed by moderators only._
## Acceptance criteria
* The Storybook stories for setup using proxy should only display a compatibility checks error if the respective story is explicitly named to show such an error.
* The Storybook stories for setup using proxy should always display the opt-in checkbox for tracking.
## Implementation Brief
* <!-- One or more bullet points for how to technically resolve the issue. -->
### Test Coverage
* <!-- One or more bullet points for how to implement automated tests to verify the issue is resolved. -->
### Visual Regression Changes
* <!-- One or more bullet points describing how the feature will affect visual regression tests, if applicable. -->
## QA Brief
* <!-- One or more bullet points for how to test that the issue has been resolved. -->
## Changelog entry
* <!-- One sentence summarizing the PR, to be used in the changelog. -->
| 1.0 | Storybook stories for setup broken - ## Bug Description
The Storybook stories for setup using proxy always show the error from the compatibility checks, even for the standard cases where there should be no error. Furthermore, the tracking opt-in checkbox UI is missing from all of these stories.
---------------
_Do not alter or remove anything below. The following sections will be managed by moderators only._
## Acceptance criteria
* The Storybook stories for setup using proxy should only display a compatibility checks error if the respective story is explicitly named to show such an error.
* The Storybook stories for setup using proxy should always display the opt-in checkbox for tracking.
## Implementation Brief
* <!-- One or more bullet points for how to technically resolve the issue. -->
### Test Coverage
* <!-- One or more bullet points for how to implement automated tests to verify the issue is resolved. -->
### Visual Regression Changes
* <!-- One or more bullet points describing how the feature will affect visual regression tests, if applicable. -->
## QA Brief
* <!-- One or more bullet points for how to test that the issue has been resolved. -->
## Changelog entry
* <!-- One sentence summarizing the PR, to be used in the changelog. -->
| infrastructure | storybook stories for setup broken bug description the storybook stories for setup using proxy always show the error from the compatibility checks even for the standard cases where there should be no error furthermore the tracking opt in checkbox ui is missing from all of these stories do not alter or remove anything below the following sections will be managed by moderators only acceptance criteria the storybook stories for setup using proxy should only display a compatibility checks error if the respective story is explicitly named to show such an error the storybook stories for setup using proxy should always display the opt in checkbox for tracking implementation brief test coverage visual regression changes qa brief changelog entry | 1 |
25,015 | 18,045,397,070 | IssuesEvent | 2021-09-18 20:13:45 | leanjunio/scheduler | https://api.github.com/repos/leanjunio/scheduler | closed | Setup the database to work with Docker Compose | enhancement infrastructure | Reasoning:
- This project will be using MongoDB since there's no defined shape or schema for the user's information
- This will also save unnecessary requests (i.e why make multiple DB calls when you can just get all the user's information)
Acceptance Criteria:
- There should be a dedicated container running that can be accessed by other containers when needed
Resources:
- https://www.bmc.com/blogs/mongodb-docker-container/
- https://hub.docker.com/_/mongo | 1.0 | Setup the database to work with Docker Compose - Reasoning:
- This project will be using MongoDB since there's no defined shape or schema for the user's information
- This will also save unnecessary requests (i.e why make multiple DB calls when you can just get all the user's information)
Acceptance Criteria:
- There should be a dedicated container running that can be accessed by other containers when needed
Resources:
- https://www.bmc.com/blogs/mongodb-docker-container/
- https://hub.docker.com/_/mongo | infrastructure | setup the database to work with docker compose reasoning this project will be using mongodb since there s no defined shape or schema for the user s information this will also save unnecessary requests i e why make multiple db calls when you can just get all the user s information acceptance criteria there should be a dedicated container running that can be accessed by other containers when needed resources | 1 |
16,880 | 12,152,145,535 | IssuesEvent | 2020-04-24 21:30:47 | BCDevOps/developer-experience | https://api.github.com/repos/BCDevOps/developer-experience | closed | Review how ocp-monitor tracks registry pods and their status | Infrastructure closed | https://trello.com/c/nhv1oFRr/167-review-how-ocp-monitor-tracks-registry-pods-and-their-status
AlertManager was spamming out one or more registry pods in PROD were not working, but the check in ocp-monitor that tracks this as well did not alert.
Further investigation required, including inspection of today's ocp-monitor.log file to see if there are other symptoms related to registry pods that are also being missed. | 1.0 | Review how ocp-monitor tracks registry pods and their status - https://trello.com/c/nhv1oFRr/167-review-how-ocp-monitor-tracks-registry-pods-and-their-status
AlertManager was spamming out one or more registry pods in PROD were not working, but the check in ocp-monitor that tracks this as well did not alert.
Further investigation required, including inspection of today's ocp-monitor.log file to see if there are other symptoms related to registry pods that are also being missed. | infrastructure | review how ocp monitor tracks registry pods and their status alertmanager was spamming out one or more registry pods in prod were not working but the check in ocp monitor that tracks this as well did not alert further investigation required including inspection of today s ocp monitor log file to see if there are other symptoms related to registry pods that are also being missed | 1 |
84,228 | 24,262,273,992 | IssuesEvent | 2022-09-28 00:42:38 | flutter/flutter | https://api.github.com/repos/flutter/flutter | closed | Allow dependency injection with GoRoute generator | new feature p: first party package proposal p: go_router_builder | As far as I've tried it today, the go router generator, only recognize injected params that should be part of the url, that is you cannot inject anything else like into your route.
Something more lenient around the lines of this could be used:
```dart
@TypedRoute()
class ProductsRoute extends GoRoute {
final ServiceContainer services;
final AppRouteFactory routeFactory;
@override
final String path = '/products';
ProductsRoute(this.services);
@override
Widget build(BuildContext context) => Container();
@override
void redirect() => services.authentication.isUserAuthenticated ? null : routeFactory.login();
}
@TypedRoute(params: {'id': int })
class ProductDetailsRoute extends GoRoute {
final ServiceContainer services;
@override
final String path = '/products/:id';
ProductDetailsRoute(this.services);
@override
Widget build(BuildContext context) => Container();
}
```
The generator is not even required here, it's just to auto generate a `go` function, which can be hand written.
```dart
class ProductsRoute extends GoRoute {
final ServiceContainer services;
final AppRouteFactory routeFactory;
@override
final String path = '/products';
ProductDetailsRoute(this.services);
@override
Widget build(BuildContext context) => Container();
Future<void> go(BuildContext context) => context.go(path);
@override
void redirect() => services.authentication.isUserAuthenticated ? null : routeFactory.login();
}
class ProductDetailsRoute extends GoRoute {
final ServiceContainer services;
@override
final String path = '/products/:id';
ProductsRoute(this.services);
@override
Widget build(BuildContext context) => Container();
Future<void> go(BuildContext context, int id) => context.go(path.replace(':id', id.toString()));
}
```
To know which route is part of the stack you can use the fact that this is just a function of the path really. `/products/:id` contains 2 screens in the stack because the URL says so. Which is how a directory structure works, which conveniently, is also what an url is (supposed) to be, ie a path. Or you can use a stack property or whatever.
Further more the distinction between GoRoute and GoRouteData seems to be an implementation details, with the only reason for it to be split in the public API, to accomodate the internals. | 1.0 | Allow dependency injection with GoRoute generator - As far as I've tried it today, the go router generator, only recognize injected params that should be part of the url, that is you cannot inject anything else like into your route.
Something more lenient around the lines of this could be used:
```dart
@TypedRoute()
class ProductsRoute extends GoRoute {
final ServiceContainer services;
final AppRouteFactory routeFactory;
@override
final String path = '/products';
ProductsRoute(this.services);
@override
Widget build(BuildContext context) => Container();
@override
void redirect() => services.authentication.isUserAuthenticated ? null : routeFactory.login();
}
@TypedRoute(params: {'id': int })
class ProductDetailsRoute extends GoRoute {
final ServiceContainer services;
@override
final String path = '/products/:id';
ProductDetailsRoute(this.services);
@override
Widget build(BuildContext context) => Container();
}
```
The generator is not even required here, it's just to auto generate a `go` function, which can be hand written.
```dart
class ProductsRoute extends GoRoute {
final ServiceContainer services;
final AppRouteFactory routeFactory;
@override
final String path = '/products';
ProductDetailsRoute(this.services);
@override
Widget build(BuildContext context) => Container();
Future<void> go(BuildContext context) => context.go(path);
@override
void redirect() => services.authentication.isUserAuthenticated ? null : routeFactory.login();
}
class ProductDetailsRoute extends GoRoute {
final ServiceContainer services;
@override
final String path = '/products/:id';
ProductsRoute(this.services);
@override
Widget build(BuildContext context) => Container();
Future<void> go(BuildContext context, int id) => context.go(path.replace(':id', id.toString()));
}
```
To know which route is part of the stack you can use the fact that this is just a function of the path really. `/products/:id` contains 2 screens in the stack because the URL says so. Which is how a directory structure works, which conveniently, is also what an url is (supposed) to be, ie a path. Or you can use a stack property or whatever.
Further more the distinction between GoRoute and GoRouteData seems to be an implementation details, with the only reason for it to be split in the public API, to accomodate the internals. | non_infrastructure | allow dependency injection with goroute generator as far as i ve tried it today the go router generator only recognize injected params that should be part of the url that is you cannot inject anything else like into your route something more lenient around the lines of this could be used dart typedroute class productsroute extends goroute final servicecontainer services final approutefactory routefactory override final string path products productsroute this services override widget build buildcontext context container override void redirect services authentication isuserauthenticated null routefactory login typedroute params id int class productdetailsroute extends goroute final servicecontainer services override final string path products id productdetailsroute this services override widget build buildcontext context container the generator is not even required here it s just to auto generate a go function which can be hand written dart class productsroute extends goroute final servicecontainer services final approutefactory routefactory override final string path products productdetailsroute this services override widget build buildcontext context container future go buildcontext context context go path override void redirect services authentication isuserauthenticated null routefactory login class productdetailsroute extends goroute final servicecontainer services override final string path products id productsroute this services override widget build buildcontext context container future go buildcontext context int id context go path replace id id tostring to know which route is part of the stack you can use the fact that this is just a function of the path really products id contains screens in the stack because the url says so which is how a directory structure works which conveniently is also what an url is supposed to be ie a path or you can use a stack property or whatever further more the distinction between goroute and goroutedata seems to be an implementation details with the only reason for it to be split in the public api to accomodate the internals | 0 |
725,217 | 24,954,485,813 | IssuesEvent | 2022-11-01 10:27:18 | FrontMen/resumator | https://api.github.com/repos/FrontMen/resumator | closed | Region is always NL, make it usable for Belgium | good first issue type: feature request priority: high | When the resume is rendered it will say the region is NL.
This is not workable for Belgium.
In the personalia you must be able to select Belgium
| 1.0 | Region is always NL, make it usable for Belgium - When the resume is rendered it will say the region is NL.
This is not workable for Belgium.
In the personalia you must be able to select Belgium
| non_infrastructure | region is always nl make it usable for belgium when the resume is rendered it will say the region is nl this is not workable for belgium in the personalia you must be able to select belgium | 0 |
398,386 | 27,192,841,402 | IssuesEvent | 2023-02-20 00:30:15 | typescript-eslint/typescript-eslint | https://api.github.com/repos/typescript-eslint/typescript-eslint | opened | Docs: Be more clear in differentiating "formatting" vs "style" | triage documentation | ### Before You File a Documentation Request Please Confirm You Have Done The Following...
- [X] I have looked for existing [open or closed documentation requests](https://github.com/typescript-eslint/typescript-eslint/issues?q=is%3Aissue+label%3Adocumentation) that match my proposal.
- [X] I have [read the FAQ](https://typescript-eslint.io/linting/troubleshooting) and my problem is not listed.
### Suggested Changes
I had a conversation with @mattpocock a bit back about how we describe the difference between formatters and linters. This topic has been coming up quite a lot in my dev evangelism in general. Matt had some good feedback from the perspective of a hypothetical new reader:
> I think I get it. Basically, 'let Prettier do your formatting, let ESLint correct your code's logic'?
> I.e. Prettier cares about the actual formatting of the text, ESLint basically only cares about AST structure.
>
> That doc is a little confusing, because of this line:
>
> > We support the ESLint team's decision and backing logic to move away from stylistic rules. > > With the exception of bug fixes, no new formatting-related pull requests will be accepted into typescript-eslint.
>
> ...which makes formatting and style feel interchangeable.
Agreed. I'm thinking at the very least that page should be cleaned up to use terminology consistently, and probably also have a more clear glossary of terms to start. The difference between _formatting_, _logical_, and _stylistic_ concerns is not a shared vocabulary even amongst linter maintenance teams!
### Affected URL(s)
https://typescript-eslint.io/linting/troubleshooting/formatting/ | 1.0 | Docs: Be more clear in differentiating "formatting" vs "style" - ### Before You File a Documentation Request Please Confirm You Have Done The Following...
- [X] I have looked for existing [open or closed documentation requests](https://github.com/typescript-eslint/typescript-eslint/issues?q=is%3Aissue+label%3Adocumentation) that match my proposal.
- [X] I have [read the FAQ](https://typescript-eslint.io/linting/troubleshooting) and my problem is not listed.
### Suggested Changes
I had a conversation with @mattpocock a bit back about how we describe the difference between formatters and linters. This topic has been coming up quite a lot in my dev evangelism in general. Matt had some good feedback from the perspective of a hypothetical new reader:
> I think I get it. Basically, 'let Prettier do your formatting, let ESLint correct your code's logic'?
> I.e. Prettier cares about the actual formatting of the text, ESLint basically only cares about AST structure.
>
> That doc is a little confusing, because of this line:
>
> > We support the ESLint team's decision and backing logic to move away from stylistic rules. > > With the exception of bug fixes, no new formatting-related pull requests will be accepted into typescript-eslint.
>
> ...which makes formatting and style feel interchangeable.
Agreed. I'm thinking at the very least that page should be cleaned up to use terminology consistently, and probably also have a more clear glossary of terms to start. The difference between _formatting_, _logical_, and _stylistic_ concerns is not a shared vocabulary even amongst linter maintenance teams!
### Affected URL(s)
https://typescript-eslint.io/linting/troubleshooting/formatting/ | non_infrastructure | docs be more clear in differentiating formatting vs style before you file a documentation request please confirm you have done the following i have looked for existing that match my proposal i have and my problem is not listed suggested changes i had a conversation with mattpocock a bit back about how we describe the difference between formatters and linters this topic has been coming up quite a lot in my dev evangelism in general matt had some good feedback from the perspective of a hypothetical new reader i think i get it basically let prettier do your formatting let eslint correct your code s logic i e prettier cares about the actual formatting of the text eslint basically only cares about ast structure that doc is a little confusing because of this line we support the eslint team s decision and backing logic to move away from stylistic rules with the exception of bug fixes no new formatting related pull requests will be accepted into typescript eslint which makes formatting and style feel interchangeable agreed i m thinking at the very least that page should be cleaned up to use terminology consistently and probably also have a more clear glossary of terms to start the difference between formatting logical and stylistic concerns is not a shared vocabulary even amongst linter maintenance teams affected url s | 0 |
15,147 | 11,382,710,999 | IssuesEvent | 2020-01-29 02:55:10 | APSIMInitiative/ApsimX | https://api.github.com/repos/APSIMInitiative/ApsimX | opened | There are many defects when importing APSIM 7.10 files to Next Gen | bug interface/infrastructure | - MicroClimate is added without defaults
- Imported soil does not have a CERESSoilTemperature child model.
- Sugar management doesn't compile on import.
- copy / paste modules from APSIM 7.10 GUI to Next Gen. GUI doesn't work at all. | 1.0 | There are many defects when importing APSIM 7.10 files to Next Gen - - MicroClimate is added without defaults
- Imported soil does not have a CERESSoilTemperature child model.
- Sugar management doesn't compile on import.
- copy / paste modules from APSIM 7.10 GUI to Next Gen. GUI doesn't work at all. | infrastructure | there are many defects when importing apsim files to next gen microclimate is added without defaults imported soil does not have a ceressoiltemperature child model sugar management doesn t compile on import copy paste modules from apsim gui to next gen gui doesn t work at all | 1 |
213,914 | 24,022,737,038 | IssuesEvent | 2022-09-15 08:59:49 | sast-automation-dev/JavaVulnerableLab-25 | https://api.github.com/repos/sast-automation-dev/JavaVulnerableLab-25 | opened | hibernate-core-4.0.1.Final.jar: 8 vulnerabilities (highest severity is: 9.8) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hibernate-core-4.0.1.Final.jar</b></p></summary>
<p>A module of the Hibernate Core project</p>
<p>Library home page: <a href="http://hibernate.org">http://hibernate.org</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /org/hibernate/hibernate-core/4.0.1.Final/hibernate-core-4.0.1.Final.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2017-15708](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-15708) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | commons-collections-3.2.1.jar | Transitive | 4.1.1.Final | ✅ |
| [CVE-2019-13116](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-13116) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | commons-collections-3.2.1.jar | Transitive | 4.1.1.Final | ✅ |
| [CVE-2015-7501](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-7501) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | commons-collections-3.2.1.jar | Transitive | 4.1.1.Final | ✅ |
| [CVE-2015-4852](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-4852) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-collections-3.2.1.jar | Transitive | 4.1.1.Final | ✅ |
| [CVE-2015-6420](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-6420) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-collections-3.2.1.jar | Transitive | 4.1.1.Final | ✅ |
| [CVE-2018-1000632](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000632) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | dom4j-1.6.1.jar | Transitive | 4.1.7.Final | ✅ |
| [CVE-2020-25638](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-25638) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.4 | hibernate-core-4.0.1.Final.jar | Direct | 5.3.16.Final-redhat-00002 | ✅ |
| [CVE-2019-14900](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14900) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | hibernate-core-4.0.1.Final.jar | Direct | 5.1.10.Final | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-15708</summary>
### Vulnerable Library - <b>commons-collections-3.2.1.jar</b></p>
<p>Types that extend and augment the Java Collections Framework.</p>
<p>Library home page: <a href="http://commons.apache.org/collections/">http://commons.apache.org/collections/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar</p>
<p>
Dependency Hierarchy:
- hibernate-core-4.0.1.Final.jar (Root Library)
- :x: **commons-collections-3.2.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Apache Synapse, by default no authentication is required for Java Remote Method Invocation (RMI). So Apache Synapse 3.0.1 or all previous releases (3.0.0, 2.1.0, 2.0.0, 1.2, 1.1.2, 1.1.1) allows remote code execution attacks that can be performed by injecting specially crafted serialized objects. And the presence of Apache Commons Collections 3.2.1 (commons-collections-3.2.1.jar) or previous versions in Synapse distribution makes this exploitable. To mitigate the issue, we need to limit RMI access to trusted users only. Further upgrading to 3.0.1 version will eliminate the risk of having said Commons Collection version. In Synapse 3.0.1, Commons Collection has been updated to 3.2.2 version.
<p>Publish Date: 2017-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-15708>CVE-2017-15708</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15708">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15708</a></p>
<p>Release Date: 2017-12-11</p>
<p>Fix Resolution (commons-collections:commons-collections): 3.2.2</p>
<p>Direct dependency fix Resolution (org.hibernate:hibernate-core): 4.1.1.Final</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-13116</summary>
### Vulnerable Library - <b>commons-collections-3.2.1.jar</b></p>
<p>Types that extend and augment the Java Collections Framework.</p>
<p>Library home page: <a href="http://commons.apache.org/collections/">http://commons.apache.org/collections/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar</p>
<p>
Dependency Hierarchy:
- hibernate-core-4.0.1.Final.jar (Root Library)
- :x: **commons-collections-3.2.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The MuleSoft Mule Community Edition runtime engine before 3.8 allows remote attackers to execute arbitrary code because of Java Deserialization, related to Apache Commons Collections
<p>Publish Date: 2019-10-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-13116>CVE-2019-13116</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13116">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13116</a></p>
<p>Release Date: 2019-10-29</p>
<p>Fix Resolution (commons-collections:commons-collections): 3.2.1-atlassian-01</p>
<p>Direct dependency fix Resolution (org.hibernate:hibernate-core): 4.1.1.Final</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2015-7501</summary>
### Vulnerable Library - <b>commons-collections-3.2.1.jar</b></p>
<p>Types that extend and augment the Java Collections Framework.</p>
<p>Library home page: <a href="http://commons.apache.org/collections/">http://commons.apache.org/collections/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar</p>
<p>
Dependency Hierarchy:
- hibernate-core-4.0.1.Final.jar (Root Library)
- :x: **commons-collections-3.2.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Red Hat JBoss A-MQ 6.x; BPM Suite (BPMS) 6.x; BRMS 6.x and 5.x; Data Grid (JDG) 6.x; Data Virtualization (JDV) 6.x and 5.x; Enterprise Application Platform 6.x, 5.x, and 4.3.x; Fuse 6.x; Fuse Service Works (FSW) 6.x; Operations Network (JBoss ON) 3.x; Portal 6.x; SOA Platform (SOA-P) 5.x; Web Server (JWS) 3.x; Red Hat OpenShift/xPAAS 3.x; and Red Hat Subscription Asset Manager 1.3 allow remote attackers to execute arbitrary commands via a crafted serialized Java object, related to the Apache Commons Collections (ACC) library.
<p>Publish Date: 2017-11-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-7501>CVE-2015-7501</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1279330">https://bugzilla.redhat.com/show_bug.cgi?id=1279330</a></p>
<p>Release Date: 2017-11-09</p>
<p>Fix Resolution (commons-collections:commons-collections): 3.2.1-atlassian-01</p>
<p>Direct dependency fix Resolution (org.hibernate:hibernate-core): 4.1.1.Final</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2015-4852</summary>
### Vulnerable Library - <b>commons-collections-3.2.1.jar</b></p>
<p>Types that extend and augment the Java Collections Framework.</p>
<p>Library home page: <a href="http://commons.apache.org/collections/">http://commons.apache.org/collections/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar</p>
<p>
Dependency Hierarchy:
- hibernate-core-4.0.1.Final.jar (Root Library)
- :x: **commons-collections-3.2.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers to execute arbitrary commands via a crafted serialized Java object in T3 protocol traffic to TCP port 7001, related to oracle_common/modules/com.bea.core.apache.commons.collections.jar. NOTE: the scope of this CVE is limited to the WebLogic Server product.
<p>Publish Date: 2015-11-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-4852>CVE-2015-4852</a></p>
</p>
<p></p>
### CVSS 2 Score Details (<b>7.5</b>)
<p>
Base Score Metrics not available</p>
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.openwall.com/lists/oss-security/2015/11/17/19">https://www.openwall.com/lists/oss-security/2015/11/17/19</a></p>
<p>Release Date: 2015-11-18</p>
<p>Fix Resolution (commons-collections:commons-collections): 3.2.1-atlassian-01</p>
<p>Direct dependency fix Resolution (org.hibernate:hibernate-core): 4.1.1.Final</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2015-6420</summary>
### Vulnerable Library - <b>commons-collections-3.2.1.jar</b></p>
<p>Types that extend and augment the Java Collections Framework.</p>
<p>Library home page: <a href="http://commons.apache.org/collections/">http://commons.apache.org/collections/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar</p>
<p>
Dependency Hierarchy:
- hibernate-core-4.0.1.Final.jar (Root Library)
- :x: **commons-collections-3.2.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Serialized-object interfaces in certain Cisco Collaboration and Social Media; Endpoint Clients and Client Software; Network Application, Service, and Acceleration; Network and Content Security Devices; Network Management and Provisioning; Routing and Switching - Enterprise and Service Provider; Unified Computing; Voice and Unified Communications Devices; Video, Streaming, TelePresence, and Transcoding Devices; Wireless; and Cisco Hosted Services products allow remote attackers to execute arbitrary commands via a crafted serialized Java object, related to the Apache Commons Collections (ACC) library.
<p>Publish Date: 2015-12-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-6420>CVE-2015-6420</a></p>
</p>
<p></p>
### CVSS 2 Score Details (<b>7.5</b>)
<p>
Base Score Metrics not available</p>
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2015-12-15</p>
<p>Fix Resolution (commons-collections:commons-collections): 3.2.1-atlassian-01</p>
<p>Direct dependency fix Resolution (org.hibernate:hibernate-core): 4.1.1.Final</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-1000632</summary>
### Vulnerable Library - <b>dom4j-1.6.1.jar</b></p>
<p>dom4j: the flexible XML framework for Java</p>
<p>Library home page: <a href="http://dom4j.org">http://dom4j.org</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar</p>
<p>
Dependency Hierarchy:
- hibernate-core-4.0.1.Final.jar (Root Library)
- :x: **dom4j-1.6.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
dom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element. Methods: addElement, addAttribute that can result in an attacker tampering with XML documents through XML injection. This attack appear to be exploitable via an attacker specifying attributes or elements in the XML document. This vulnerability appears to have been fixed in 2.1.1 or later.
<p>Publish Date: 2018-08-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000632>CVE-2018-1000632</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000632">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000632</a></p>
<p>Release Date: 2018-08-20</p>
<p>Fix Resolution (dom4j:dom4j): 1.6.1-NODEP</p>
<p>Direct dependency fix Resolution (org.hibernate:hibernate-core): 4.1.7.Final</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-25638</summary>
### Vulnerable Library - <b>hibernate-core-4.0.1.Final.jar</b></p>
<p>A module of the Hibernate Core project</p>
<p>Library home page: <a href="http://hibernate.org">http://hibernate.org</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /org/hibernate/hibernate-core/4.0.1.Final/hibernate-core-4.0.1.Final.jar</p>
<p>
Dependency Hierarchy:
- :x: **hibernate-core-4.0.1.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A flaw was found in hibernate-core in versions prior to and including 5.4.23.Final. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SQL comments of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks. The highest threat from this vulnerability is to data confidentiality and integrity.
<p>Publish Date: 2020-12-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-25638>CVE-2020-25638</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.4</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://in.relation.to/2020/11/19/hibernate-orm-5424-final-release/">https://in.relation.to/2020/11/19/hibernate-orm-5424-final-release/</a></p>
<p>Release Date: 2020-12-02</p>
<p>Fix Resolution: 5.3.16.Final-redhat-00002</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-14900</summary>
### Vulnerable Library - <b>hibernate-core-4.0.1.Final.jar</b></p>
<p>A module of the Hibernate Core project</p>
<p>Library home page: <a href="http://hibernate.org">http://hibernate.org</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /org/hibernate/hibernate-core/4.0.1.Final/hibernate-core-4.0.1.Final.jar</p>
<p>
Dependency Hierarchy:
- :x: **hibernate-core-4.0.1.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A flaw was found in Hibernate ORM in versions before 5.3.18, 5.4.18 and 5.5.0.Beta1. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SELECT or GROUP BY parts of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks.
<p>Publish Date: 2020-07-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14900>CVE-2019-14900</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14900">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14900</a></p>
<p>Release Date: 2020-07-06</p>
<p>Fix Resolution: 5.1.10.Final</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | True | hibernate-core-4.0.1.Final.jar: 8 vulnerabilities (highest severity is: 9.8) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hibernate-core-4.0.1.Final.jar</b></p></summary>
<p>A module of the Hibernate Core project</p>
<p>Library home page: <a href="http://hibernate.org">http://hibernate.org</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /org/hibernate/hibernate-core/4.0.1.Final/hibernate-core-4.0.1.Final.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2017-15708](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-15708) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | commons-collections-3.2.1.jar | Transitive | 4.1.1.Final | ✅ |
| [CVE-2019-13116](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-13116) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | commons-collections-3.2.1.jar | Transitive | 4.1.1.Final | ✅ |
| [CVE-2015-7501](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-7501) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | commons-collections-3.2.1.jar | Transitive | 4.1.1.Final | ✅ |
| [CVE-2015-4852](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-4852) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-collections-3.2.1.jar | Transitive | 4.1.1.Final | ✅ |
| [CVE-2015-6420](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-6420) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-collections-3.2.1.jar | Transitive | 4.1.1.Final | ✅ |
| [CVE-2018-1000632](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000632) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | dom4j-1.6.1.jar | Transitive | 4.1.7.Final | ✅ |
| [CVE-2020-25638](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-25638) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.4 | hibernate-core-4.0.1.Final.jar | Direct | 5.3.16.Final-redhat-00002 | ✅ |
| [CVE-2019-14900](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14900) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | hibernate-core-4.0.1.Final.jar | Direct | 5.1.10.Final | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-15708</summary>
### Vulnerable Library - <b>commons-collections-3.2.1.jar</b></p>
<p>Types that extend and augment the Java Collections Framework.</p>
<p>Library home page: <a href="http://commons.apache.org/collections/">http://commons.apache.org/collections/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar</p>
<p>
Dependency Hierarchy:
- hibernate-core-4.0.1.Final.jar (Root Library)
- :x: **commons-collections-3.2.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Apache Synapse, by default no authentication is required for Java Remote Method Invocation (RMI). So Apache Synapse 3.0.1 or all previous releases (3.0.0, 2.1.0, 2.0.0, 1.2, 1.1.2, 1.1.1) allows remote code execution attacks that can be performed by injecting specially crafted serialized objects. And the presence of Apache Commons Collections 3.2.1 (commons-collections-3.2.1.jar) or previous versions in Synapse distribution makes this exploitable. To mitigate the issue, we need to limit RMI access to trusted users only. Further upgrading to 3.0.1 version will eliminate the risk of having said Commons Collection version. In Synapse 3.0.1, Commons Collection has been updated to 3.2.2 version.
<p>Publish Date: 2017-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-15708>CVE-2017-15708</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15708">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15708</a></p>
<p>Release Date: 2017-12-11</p>
<p>Fix Resolution (commons-collections:commons-collections): 3.2.2</p>
<p>Direct dependency fix Resolution (org.hibernate:hibernate-core): 4.1.1.Final</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-13116</summary>
### Vulnerable Library - <b>commons-collections-3.2.1.jar</b></p>
<p>Types that extend and augment the Java Collections Framework.</p>
<p>Library home page: <a href="http://commons.apache.org/collections/">http://commons.apache.org/collections/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar</p>
<p>
Dependency Hierarchy:
- hibernate-core-4.0.1.Final.jar (Root Library)
- :x: **commons-collections-3.2.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The MuleSoft Mule Community Edition runtime engine before 3.8 allows remote attackers to execute arbitrary code because of Java Deserialization, related to Apache Commons Collections
<p>Publish Date: 2019-10-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-13116>CVE-2019-13116</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13116">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13116</a></p>
<p>Release Date: 2019-10-29</p>
<p>Fix Resolution (commons-collections:commons-collections): 3.2.1-atlassian-01</p>
<p>Direct dependency fix Resolution (org.hibernate:hibernate-core): 4.1.1.Final</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2015-7501</summary>
### Vulnerable Library - <b>commons-collections-3.2.1.jar</b></p>
<p>Types that extend and augment the Java Collections Framework.</p>
<p>Library home page: <a href="http://commons.apache.org/collections/">http://commons.apache.org/collections/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar</p>
<p>
Dependency Hierarchy:
- hibernate-core-4.0.1.Final.jar (Root Library)
- :x: **commons-collections-3.2.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Red Hat JBoss A-MQ 6.x; BPM Suite (BPMS) 6.x; BRMS 6.x and 5.x; Data Grid (JDG) 6.x; Data Virtualization (JDV) 6.x and 5.x; Enterprise Application Platform 6.x, 5.x, and 4.3.x; Fuse 6.x; Fuse Service Works (FSW) 6.x; Operations Network (JBoss ON) 3.x; Portal 6.x; SOA Platform (SOA-P) 5.x; Web Server (JWS) 3.x; Red Hat OpenShift/xPAAS 3.x; and Red Hat Subscription Asset Manager 1.3 allow remote attackers to execute arbitrary commands via a crafted serialized Java object, related to the Apache Commons Collections (ACC) library.
<p>Publish Date: 2017-11-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-7501>CVE-2015-7501</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1279330">https://bugzilla.redhat.com/show_bug.cgi?id=1279330</a></p>
<p>Release Date: 2017-11-09</p>
<p>Fix Resolution (commons-collections:commons-collections): 3.2.1-atlassian-01</p>
<p>Direct dependency fix Resolution (org.hibernate:hibernate-core): 4.1.1.Final</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2015-4852</summary>
### Vulnerable Library - <b>commons-collections-3.2.1.jar</b></p>
<p>Types that extend and augment the Java Collections Framework.</p>
<p>Library home page: <a href="http://commons.apache.org/collections/">http://commons.apache.org/collections/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar</p>
<p>
Dependency Hierarchy:
- hibernate-core-4.0.1.Final.jar (Root Library)
- :x: **commons-collections-3.2.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers to execute arbitrary commands via a crafted serialized Java object in T3 protocol traffic to TCP port 7001, related to oracle_common/modules/com.bea.core.apache.commons.collections.jar. NOTE: the scope of this CVE is limited to the WebLogic Server product.
<p>Publish Date: 2015-11-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-4852>CVE-2015-4852</a></p>
</p>
<p></p>
### CVSS 2 Score Details (<b>7.5</b>)
<p>
Base Score Metrics not available</p>
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.openwall.com/lists/oss-security/2015/11/17/19">https://www.openwall.com/lists/oss-security/2015/11/17/19</a></p>
<p>Release Date: 2015-11-18</p>
<p>Fix Resolution (commons-collections:commons-collections): 3.2.1-atlassian-01</p>
<p>Direct dependency fix Resolution (org.hibernate:hibernate-core): 4.1.1.Final</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2015-6420</summary>
### Vulnerable Library - <b>commons-collections-3.2.1.jar</b></p>
<p>Types that extend and augment the Java Collections Framework.</p>
<p>Library home page: <a href="http://commons.apache.org/collections/">http://commons.apache.org/collections/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar</p>
<p>
Dependency Hierarchy:
- hibernate-core-4.0.1.Final.jar (Root Library)
- :x: **commons-collections-3.2.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Serialized-object interfaces in certain Cisco Collaboration and Social Media; Endpoint Clients and Client Software; Network Application, Service, and Acceleration; Network and Content Security Devices; Network Management and Provisioning; Routing and Switching - Enterprise and Service Provider; Unified Computing; Voice and Unified Communications Devices; Video, Streaming, TelePresence, and Transcoding Devices; Wireless; and Cisco Hosted Services products allow remote attackers to execute arbitrary commands via a crafted serialized Java object, related to the Apache Commons Collections (ACC) library.
<p>Publish Date: 2015-12-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-6420>CVE-2015-6420</a></p>
</p>
<p></p>
### CVSS 2 Score Details (<b>7.5</b>)
<p>
Base Score Metrics not available</p>
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2015-12-15</p>
<p>Fix Resolution (commons-collections:commons-collections): 3.2.1-atlassian-01</p>
<p>Direct dependency fix Resolution (org.hibernate:hibernate-core): 4.1.1.Final</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-1000632</summary>
### Vulnerable Library - <b>dom4j-1.6.1.jar</b></p>
<p>dom4j: the flexible XML framework for Java</p>
<p>Library home page: <a href="http://dom4j.org">http://dom4j.org</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar</p>
<p>
Dependency Hierarchy:
- hibernate-core-4.0.1.Final.jar (Root Library)
- :x: **dom4j-1.6.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
dom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element. Methods: addElement, addAttribute that can result in an attacker tampering with XML documents through XML injection. This attack appear to be exploitable via an attacker specifying attributes or elements in the XML document. This vulnerability appears to have been fixed in 2.1.1 or later.
<p>Publish Date: 2018-08-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000632>CVE-2018-1000632</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000632">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000632</a></p>
<p>Release Date: 2018-08-20</p>
<p>Fix Resolution (dom4j:dom4j): 1.6.1-NODEP</p>
<p>Direct dependency fix Resolution (org.hibernate:hibernate-core): 4.1.7.Final</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-25638</summary>
### Vulnerable Library - <b>hibernate-core-4.0.1.Final.jar</b></p>
<p>A module of the Hibernate Core project</p>
<p>Library home page: <a href="http://hibernate.org">http://hibernate.org</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /org/hibernate/hibernate-core/4.0.1.Final/hibernate-core-4.0.1.Final.jar</p>
<p>
Dependency Hierarchy:
- :x: **hibernate-core-4.0.1.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A flaw was found in hibernate-core in versions prior to and including 5.4.23.Final. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SQL comments of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks. The highest threat from this vulnerability is to data confidentiality and integrity.
<p>Publish Date: 2020-12-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-25638>CVE-2020-25638</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.4</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://in.relation.to/2020/11/19/hibernate-orm-5424-final-release/">https://in.relation.to/2020/11/19/hibernate-orm-5424-final-release/</a></p>
<p>Release Date: 2020-12-02</p>
<p>Fix Resolution: 5.3.16.Final-redhat-00002</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-14900</summary>
### Vulnerable Library - <b>hibernate-core-4.0.1.Final.jar</b></p>
<p>A module of the Hibernate Core project</p>
<p>Library home page: <a href="http://hibernate.org">http://hibernate.org</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /org/hibernate/hibernate-core/4.0.1.Final/hibernate-core-4.0.1.Final.jar</p>
<p>
Dependency Hierarchy:
- :x: **hibernate-core-4.0.1.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/JavaVulnerableLab-25/commit/101ae810cdaccca3b7ed34e823ee824f14b4ee1a">101ae810cdaccca3b7ed34e823ee824f14b4ee1a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A flaw was found in Hibernate ORM in versions before 5.3.18, 5.4.18 and 5.5.0.Beta1. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SELECT or GROUP BY parts of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks.
<p>Publish Date: 2020-07-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14900>CVE-2019-14900</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14900">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14900</a></p>
<p>Release Date: 2020-07-06</p>
<p>Fix Resolution: 5.1.10.Final</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | non_infrastructure | hibernate core final jar vulnerabilities highest severity is vulnerable library hibernate core final jar a module of the hibernate core project library home page a href path to dependency file pom xml path to vulnerable library org hibernate hibernate core final hibernate core final jar found in head commit a href vulnerabilities cve severity cvss dependency type fixed in remediation available high commons collections jar transitive final high commons collections jar transitive final high commons collections jar transitive final high commons collections jar transitive final high commons collections jar transitive final high jar transitive final high hibernate core final jar direct final redhat medium hibernate core final jar direct final details cve vulnerable library commons collections jar types that extend and augment the java collections framework library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository commons collections commons collections commons collections jar dependency hierarchy hibernate core final jar root library x commons collections jar vulnerable library found in head commit a href found in base branch master vulnerability details in apache synapse by default no authentication is required for java remote method invocation rmi so apache synapse or all previous releases allows remote code execution attacks that can be performed by injecting specially crafted serialized objects and the presence of apache commons collections commons collections jar or previous versions in synapse distribution makes this exploitable to mitigate the issue we need to limit rmi access to trusted users only further upgrading to version will eliminate the risk of having said commons collection version in synapse commons collection has been updated to version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution commons collections commons collections direct dependency fix resolution org hibernate hibernate core final rescue worker helmet automatic remediation is available for this issue cve vulnerable library commons collections jar types that extend and augment the java collections framework library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository commons collections commons collections commons collections jar dependency hierarchy hibernate core final jar root library x commons collections jar vulnerable library found in head commit a href found in base branch master vulnerability details the mulesoft mule community edition runtime engine before allows remote attackers to execute arbitrary code because of java deserialization related to apache commons collections publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution commons collections commons collections atlassian direct dependency fix resolution org hibernate hibernate core final rescue worker helmet automatic remediation is available for this issue cve vulnerable library commons collections jar types that extend and augment the java collections framework library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository commons collections commons collections commons collections jar dependency hierarchy hibernate core final jar root library x commons collections jar vulnerable library found in head commit a href found in base branch master vulnerability details red hat jboss a mq x bpm suite bpms x brms x and x data grid jdg x data virtualization jdv x and x enterprise application platform x x and x fuse x fuse service works fsw x operations network jboss on x portal x soa platform soa p x web server jws x red hat openshift xpaas x and red hat subscription asset manager allow remote attackers to execute arbitrary commands via a crafted serialized java object related to the apache commons collections acc library publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution commons collections commons collections atlassian direct dependency fix resolution org hibernate hibernate core final rescue worker helmet automatic remediation is available for this issue cve vulnerable library commons collections jar types that extend and augment the java collections framework library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository commons collections commons collections commons collections jar dependency hierarchy hibernate core final jar root library x commons collections jar vulnerable library found in head commit a href found in base branch master vulnerability details the wls security component in oracle weblogic server and allows remote attackers to execute arbitrary commands via a crafted serialized java object in protocol traffic to tcp port related to oracle common modules com bea core apache commons collections jar note the scope of this cve is limited to the weblogic server product publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution commons collections commons collections atlassian direct dependency fix resolution org hibernate hibernate core final rescue worker helmet automatic remediation is available for this issue cve vulnerable library commons collections jar types that extend and augment the java collections framework library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository commons collections commons collections commons collections jar dependency hierarchy hibernate core final jar root library x commons collections jar vulnerable library found in head commit a href found in base branch master vulnerability details serialized object interfaces in certain cisco collaboration and social media endpoint clients and client software network application service and acceleration network and content security devices network management and provisioning routing and switching enterprise and service provider unified computing voice and unified communications devices video streaming telepresence and transcoding devices wireless and cisco hosted services products allow remote attackers to execute arbitrary commands via a crafted serialized java object related to the apache commons collections acc library publish date url a href cvss score details base score metrics not available suggested fix type upgrade version release date fix resolution commons collections commons collections atlassian direct dependency fix resolution org hibernate hibernate core final rescue worker helmet automatic remediation is available for this issue cve vulnerable library jar the flexible xml framework for java library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository jar dependency hierarchy hibernate core final jar root library x jar vulnerable library found in head commit a href found in base branch master vulnerability details version prior to version contains a cwe xml injection vulnerability in class element methods addelement addattribute that can result in an attacker tampering with xml documents through xml injection this attack appear to be exploitable via an attacker specifying attributes or elements in the xml document this vulnerability appears to have been fixed in or later 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 nodep direct dependency fix resolution org hibernate hibernate core final rescue worker helmet automatic remediation is available for this issue cve vulnerable library hibernate core final jar a module of the hibernate core project library home page a href path to dependency file pom xml path to vulnerable library org hibernate hibernate core final hibernate core final jar dependency hierarchy x hibernate core final jar vulnerable library found in head commit a href found in base branch master vulnerability details a flaw was found in hibernate core in versions prior to and including final a sql injection in the implementation of the jpa criteria api can permit unsanitized literals when a literal is used in the sql comments of the query this flaw could allow an attacker to access unauthorized information or possibly conduct further attacks the highest threat from this vulnerability is to data confidentiality and integrity publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution final redhat rescue worker helmet automatic remediation is available for this issue cve vulnerable library hibernate core final jar a module of the hibernate core project library home page a href path to dependency file pom xml path to vulnerable library org hibernate hibernate core final hibernate core final jar dependency hierarchy x hibernate core final jar vulnerable library found in head commit a href found in base branch master vulnerability details a flaw was found in hibernate orm in versions before and a sql injection in the implementation of the jpa criteria api can permit unsanitized literals when a literal is used in the select or group by parts of the query this flaw could allow an attacker to access unauthorized information or possibly conduct further attacks publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution final rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue | 0 |
877 | 2,985,278,791 | IssuesEvent | 2015-07-18 21:41:46 | t3kt/vjzual | https://api.github.com/repos/t3kt/vjzual | opened | switch bypass parameters to special boolean parameters | cleanup and refactoring infrastructure | The hidden parameter components aren't necessary anymore due to #16.
See also #90 and #93. | 1.0 | switch bypass parameters to special boolean parameters - The hidden parameter components aren't necessary anymore due to #16.
See also #90 and #93. | infrastructure | switch bypass parameters to special boolean parameters the hidden parameter components aren t necessary anymore due to see also and | 1 |
548,328 | 16,062,165,982 | IssuesEvent | 2021-04-23 13:59:04 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | get.adobe.com - see bug description | browser-firefox engine-gecko priority-critical | <!-- @browser: Firefox 88.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0 -->
<!-- @reported_with: unknown -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/71067 -->
**URL**: https://get.adobe.com/fr/reader/enterprise/
**Browser / Version**: Firefox 88.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes Chrome
**Problem type**: Something else
**Description**: When clicking on the dropdown menus, nothing shows up. You have to use directional arrows to navigate and when you do that, the first entry you select triggers the next menu, which is troublesome, to say the least...
**Steps to Reproduce**:
Again?! As said in step 2, the dropdown menus content doesn't show, so you have to use directional arrows to (blindly) navigate, and the first entry to appears in the text area is validated automatically, which triggers the next menu, so that if you're not careful, you end up downloading the macOS version in Chinese, instead of the Windows 10 version in French. Pardon my English, but that sucks...! :-D
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | get.adobe.com - see bug description - <!-- @browser: Firefox 88.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0 -->
<!-- @reported_with: unknown -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/71067 -->
**URL**: https://get.adobe.com/fr/reader/enterprise/
**Browser / Version**: Firefox 88.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes Chrome
**Problem type**: Something else
**Description**: When clicking on the dropdown menus, nothing shows up. You have to use directional arrows to navigate and when you do that, the first entry you select triggers the next menu, which is troublesome, to say the least...
**Steps to Reproduce**:
Again?! As said in step 2, the dropdown menus content doesn't show, so you have to use directional arrows to (blindly) navigate, and the first entry to appears in the text area is validated automatically, which triggers the next menu, so that if you're not careful, you end up downloading the macOS version in Chinese, instead of the Windows 10 version in French. Pardon my English, but that sucks...! :-D
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_infrastructure | get adobe com see bug description url browser version firefox operating system windows tested another browser yes chrome problem type something else description when clicking on the dropdown menus nothing shows up you have to use directional arrows to navigate and when you do that the first entry you select triggers the next menu which is troublesome to say the least steps to reproduce again as said in step the dropdown menus content doesn t show so you have to use directional arrows to blindly navigate and the first entry to appears in the text area is validated automatically which triggers the next menu so that if you re not careful you end up downloading the macos version in chinese instead of the windows version in french pardon my english but that sucks d browser configuration none from with ❤️ | 0 |
1,411 | 3,201,027,255 | IssuesEvent | 2015-10-02 02:01:23 | eslint/eslint | https://api.github.com/repos/eslint/eslint | closed | Add load performance check inside perf function | accepted enhancement infrastructure | Current perf function inside Makefile calculates the runtime performance of eslint. I want to add load performance of eslint to it so that it would help us determine the impact whenever new dependencies gets added to the project.
We recently improved our load performance: https://github.com/eslint/eslint/pull/3931
We can use [load-perf](https://github.com/gyandeeps/load-perf) module by consuming its nodejs api.
What do you think @eslint/eslint-team ?
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/27074390-add-load-performance-check-inside-perf-function?utm_campaign=plugin&utm_content=tracker%2F282608&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F282608&utm_medium=issues&utm_source=github).
</bountysource-plugin> | 1.0 | Add load performance check inside perf function - Current perf function inside Makefile calculates the runtime performance of eslint. I want to add load performance of eslint to it so that it would help us determine the impact whenever new dependencies gets added to the project.
We recently improved our load performance: https://github.com/eslint/eslint/pull/3931
We can use [load-perf](https://github.com/gyandeeps/load-perf) module by consuming its nodejs api.
What do you think @eslint/eslint-team ?
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/27074390-add-load-performance-check-inside-perf-function?utm_campaign=plugin&utm_content=tracker%2F282608&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F282608&utm_medium=issues&utm_source=github).
</bountysource-plugin> | infrastructure | add load performance check inside perf function current perf function inside makefile calculates the runtime performance of eslint i want to add load performance of eslint to it so that it would help us determine the impact whenever new dependencies gets added to the project we recently improved our load performance we can use module by consuming its nodejs api what do you think eslint eslint team want to back this issue we accept bounties via | 1 |
139,435 | 5,375,354,124 | IssuesEvent | 2017-02-23 04:19:29 | deevolutionism/Raccoon | https://api.github.com/repos/deevolutionism/Raccoon | opened | Implement upvoting / downvoting system | Feature Priority: LOW | Can this be done with anonymous profiles? How to prevent a client from mashing the upvote/downvote buttons? | 1.0 | Implement upvoting / downvoting system - Can this be done with anonymous profiles? How to prevent a client from mashing the upvote/downvote buttons? | non_infrastructure | implement upvoting downvoting system can this be done with anonymous profiles how to prevent a client from mashing the upvote downvote buttons | 0 |
27,639 | 22,054,523,379 | IssuesEvent | 2022-05-30 11:40:20 | UCL/hivpy | https://api.github.com/repos/UCL/hivpy | closed | Static files for death rates | infrastructure | Following from #17, we should read in the rates from a file rather than hardcode them. | 1.0 | Static files for death rates - Following from #17, we should read in the rates from a file rather than hardcode them. | infrastructure | static files for death rates following from we should read in the rates from a file rather than hardcode them | 1 |
27,201 | 21,417,128,699 | IssuesEvent | 2022-04-22 12:04:24 | XmacsLabs/mogan | https://api.github.com/repos/XmacsLabs/mogan | closed | CMake: the os should be macOS on macOS | Infrastructure | See #153
And here is part of the error messages:
```
System information:
TeXmacs version : 2.1.1
Built by : xmacs
Building date : 2022-04-10T03:46:45
Operating system : linux-gnu
Vendor : pc
Processor : x86_64
Crash date : 2022年 4月10日 星期日 20时45分35秒 CST
``` | 1.0 | CMake: the os should be macOS on macOS - See #153
And here is part of the error messages:
```
System information:
TeXmacs version : 2.1.1
Built by : xmacs
Building date : 2022-04-10T03:46:45
Operating system : linux-gnu
Vendor : pc
Processor : x86_64
Crash date : 2022年 4月10日 星期日 20时45分35秒 CST
``` | infrastructure | cmake the os should be macos on macos see and here is part of the error messages system information texmacs version built by xmacs building date operating system linux gnu vendor pc processor crash date 星期日 cst | 1 |
13,070 | 21,872,740,966 | IssuesEvent | 2022-05-19 07:23:29 | renovatebot/renovate | https://api.github.com/repos/renovatebot/renovate | opened | Refactor code in `tools/docs/config.ts` | type:refactor status:requirements priority-5-triage | ### Describe the proposed change(s).
Creating an issue to track https://github.com/renovatebot/renovate/pull/15637#pullrequestreview-977985457.
PR #15637 inserted some new code, which needs to be cleaned up.
https://github.com/renovatebot/renovate/blob/97fd4b884c4989cdac61bd9feb13e727d16e7e11/tools/docs/config.ts#L31-L36
https://github.com/renovatebot/renovate/blob/97fd4b884c4989cdac61bd9feb13e727d16e7e11/tools/docs/config.ts#L51-L54 | 1.0 | Refactor code in `tools/docs/config.ts` - ### Describe the proposed change(s).
Creating an issue to track https://github.com/renovatebot/renovate/pull/15637#pullrequestreview-977985457.
PR #15637 inserted some new code, which needs to be cleaned up.
https://github.com/renovatebot/renovate/blob/97fd4b884c4989cdac61bd9feb13e727d16e7e11/tools/docs/config.ts#L31-L36
https://github.com/renovatebot/renovate/blob/97fd4b884c4989cdac61bd9feb13e727d16e7e11/tools/docs/config.ts#L51-L54 | non_infrastructure | refactor code in tools docs config ts describe the proposed change s creating an issue to track pr inserted some new code which needs to be cleaned up | 0 |
10,067 | 8,359,695,676 | IssuesEvent | 2018-10-03 09:06:08 | servo/webrender | https://api.github.com/repos/servo/webrender | closed | upgrade dwrote dependency to 0.5.0 | area: infrastructure difficulty: easy priority: soon type: enhancement | This depends on servo/dwrote-rs#14, and would be useful for Firefox eliminating dependencies on `winapi` 0.2.8. | 1.0 | upgrade dwrote dependency to 0.5.0 - This depends on servo/dwrote-rs#14, and would be useful for Firefox eliminating dependencies on `winapi` 0.2.8. | infrastructure | upgrade dwrote dependency to this depends on servo dwrote rs and would be useful for firefox eliminating dependencies on winapi | 1 |
508,366 | 14,698,872,841 | IssuesEvent | 2021-01-04 07:27:20 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.airbnb.com - see bug description | browser-firefox-mobile engine-gecko ml-needsdiagnosis-false ml-probability-high priority-important | <!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 10; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/64835 -->
**URL**: https://www.airbnb.com/
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android
**Tested Another Browser**: Yes Other
**Problem type**: Something else
**Description**: Won't open
**Steps to Reproduce**:
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2021/1/01f8cee4-9242-4d77-a284-7bb6cb5df13b.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20200104123338</li><li>channel: default</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2021/1/535a39ed-b403-4ecb-a87e-777dc28ec981)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.airbnb.com - see bug description - <!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 10; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/64835 -->
**URL**: https://www.airbnb.com/
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android
**Tested Another Browser**: Yes Other
**Problem type**: Something else
**Description**: Won't open
**Steps to Reproduce**:
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2021/1/01f8cee4-9242-4d77-a284-7bb6cb5df13b.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20200104123338</li><li>channel: default</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2021/1/535a39ed-b403-4ecb-a87e-777dc28ec981)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_infrastructure | see bug description url browser version firefox mobile operating system android tested another browser yes other problem type something else description won t open steps to reproduce view the screenshot img alt screenshot src browser configuration gfx webrender all false gfx webrender blob images true gfx webrender enabled false image mem shared true buildid channel default hastouchscreen true mixed active content blocked false mixed passive content blocked false tracking content blocked false from with ❤️ | 0 |
27,965 | 22,648,971,295 | IssuesEvent | 2022-07-01 11:35:33 | bootstrapworld/curriculum | https://api.github.com/repos/bootstrapworld/curriculum | closed | (Presumably) spurious error when building hoc-data | Infrastructure | Since hoc lessons have no exercises, I'm guessing this is just about inserting a check in the build script?
```
preparing hoc-data
open-output-file: error opening file
path: /Users/schanzer/Documents/Bootstrap/Development/curriculum/distribution/en-us/lessons/hoc-data/pages/.cached/.exercise-pages-ls.txt.kp
system error: No such file or directory; errno=2
context...:
/Users/schanzer/Documents/Bootstrap/Development/curriculum/distribution/.prog/collect-exercises.rkt:68:0: collect-exercises
``` | 1.0 | (Presumably) spurious error when building hoc-data - Since hoc lessons have no exercises, I'm guessing this is just about inserting a check in the build script?
```
preparing hoc-data
open-output-file: error opening file
path: /Users/schanzer/Documents/Bootstrap/Development/curriculum/distribution/en-us/lessons/hoc-data/pages/.cached/.exercise-pages-ls.txt.kp
system error: No such file or directory; errno=2
context...:
/Users/schanzer/Documents/Bootstrap/Development/curriculum/distribution/.prog/collect-exercises.rkt:68:0: collect-exercises
``` | infrastructure | presumably spurious error when building hoc data since hoc lessons have no exercises i m guessing this is just about inserting a check in the build script preparing hoc data open output file error opening file path users schanzer documents bootstrap development curriculum distribution en us lessons hoc data pages cached exercise pages ls txt kp system error no such file or directory errno context users schanzer documents bootstrap development curriculum distribution prog collect exercises rkt collect exercises | 1 |
22,668 | 15,363,929,383 | IssuesEvent | 2021-03-01 21:19:49 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | reopened | Add mono binary to Nuget package to run AOT | area-Infrastructure-mono | The current netcore mono with LLVM AOT Nuget package doesn't contain anything which could be used to run AOT. | 1.0 | Add mono binary to Nuget package to run AOT - The current netcore mono with LLVM AOT Nuget package doesn't contain anything which could be used to run AOT. | infrastructure | add mono binary to nuget package to run aot the current netcore mono with llvm aot nuget package doesn t contain anything which could be used to run aot | 1 |
133,703 | 10,860,074,573 | IssuesEvent | 2019-11-14 08:12:46 | ballerina-platform/ballerina-lang | https://api.github.com/repos/ballerina-platform/ballerina-lang | opened | Re-enable WebSubSubscriberStartTest | Area/StandardLibs Component/WebSub Type/TestFailure | **Description:**
WebSubSubscriberStartTest is being disabled temporarily since this is suspected to be causing the build to hang.
Output for a passing build - https://api.travis-ci.com/v3/job/253956997/log.txt
```
> Task :ballerina-websub:createTestBalHome
> Task :ballerina-websub:test
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubCompilationTest STANDARD_OUT
test_compilation_failure.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubCompilationTest > testInvalidAnnotationCount STANDARD_OUT
test_multiple_annots.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubCompilationTest > testInvalidResourceReturnType STANDARD_OUT
test_invalid_return_negative.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubDiscoveryResponseParserTest STANDARD_OUT
test_discovery_response_parsing.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubDiscoveryResponseParserTest STANDARD_ERROR
Nov 08, 2019 6:05:28 AM org.quartz.impl.StdSchedulerFactory instantiate
INFO: Using default implementation for ThreadExecutor
Nov 08, 2019 6:05:28 AM org.quartz.core.SchedulerSignalerImpl <init>
INFO: Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
Nov 08, 2019 6:05:28 AM org.quartz.core.QuartzScheduler <init>
INFO: Quartz Scheduler v.2.3.1 created.
Nov 08, 2019 6:05:28 AM org.quartz.simpl.RAMJobStore initialize
INFO: RAMJobStore initialized.
Nov 08, 2019 6:05:28 AM org.quartz.core.QuartzScheduler initialize
INFO: Scheduler meta-data: Quartz Scheduler (v2.3.1) 'QuartzScheduler' with instanceId 'NON_CLUSTERED'
Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.
Nov 08, 2019 6:05:28 AM org.quartz.impl.StdSchedulerFactory instantiate
INFO: Quartz scheduler 'QuartzScheduler' initialized from an externally provided properties instance.
Nov 08, 2019 6:05:28 AM org.quartz.impl.StdSchedulerFactory instantiate
INFO: Quartz scheduler version: 2.3.1
Nov 08, 2019 6:05:28 AM org.quartz.core.QuartzScheduler start
INFO: Scheduler QuartzScheduler_$_NON_CLUSTERED started.
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest STANDARD_OUT
test_hub_startup.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 6:05:32 AM io.ballerina.messaging.broker.core.BrokerImpl$BrokerHelper startMessageDelivery
INFO: Starting message delivery threads.
Nov 08, 2019 6:05:32 AM io.ballerina.messaging.broker.core.task.TaskExecutorService start
INFO: Starting task manager. Task count 0
[ballerina/websub] Ballerina WebSub Hub started up.
[ballerina/websub] Publish URL: https://localhost:9191/websub/pub
[ballerina/websub] Subscription URL: https://localhost:9191/websub/hub
Nov 08, 2019 6:05:32 AM org.ballerinalang.net.http.HTTPServicesRegistry registerService
INFO: Service deployed : $anonService$0$$service$1 with context /websub
Nov 08, 2019 6:05:32 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector lambda$start$0
INFO: HTTP(S) Interface starting on host 0.0.0.0 and port 9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] started HTTP/WS listener 0.0.0.0:9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 6:05:32 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector unBindInterface
INFO: HttpConnectorListener stopped listening on host 0.0.0.0 and port 9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] stopped HTTP/WS listener 0.0.0.0:9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 6:05:32 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector unBindInterface
INFO: HttpConnectorListener stopped listening on host 0.0.0.0 and port 9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] stopped HTTP/WS listener 0.0.0.0:9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
[ballerina/websub] Ballerina WebSub Hub started up.
[ballerina/websub] Publish URL: http://localhost:9393/publish
[ballerina/websub] Subscription URL: http://localhost:9393/
Nov 08, 2019 6:05:32 AM org.ballerinalang.net.http.HTTPServicesRegistry registerService
INFO: Service deployed : $anonService$0$$service$1 with context /
Nov 08, 2019 6:05:32 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector lambda$start$0
INFO: HTTP(S) Interface starting on host 0.0.0.0 and port 9393
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] started HTTP/WS listener 0.0.0.0:9393
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 6:05:32 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector unBindInterface
INFO: HttpConnectorListener stopped listening on host 0.0.0.0 and port 9393
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] stopped HTTP/WS listener 0.0.0.0:9393
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 6:05:32 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector unBindInterface
INFO: HttpConnectorListener stopped listening on host 0.0.0.0 and port 9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] stopped HTTP/WS listener 0.0.0.0:9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubSpecificSubscriberValidationTest STANDARD_OUT
test_specific_subscriber.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubSpecificSubscriberValidationTest > testInvalidParam STANDARD_ERROR
Nov 08, 2019 6:05:35 AM org.ballerinalang.net.websub.WebSubServicesRegistry registerWebSubSubscriberService
INFO: Service deployed : $anonService$2$$service$3 with context /key
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubSpecificSubscriberValidationTest > testInvalidResourceFunctions STANDARD_ERROR
Nov 08, 2019 6:05:35 AM org.ballerinalang.net.websub.WebSubServicesRegistry registerWebSubSubscriberService
INFO: Service deployed : $anonService$0$$service$1 with context /key
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubSubscriberStartTest STANDARD_OUT
test_subscriber_startup.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubSubscriberStartTest > testMultipleSubscribersStartUpInSamePort STANDARD_ERROR
Nov 08, 2019 6:05:37 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector lambda$start$0
INFO: HTTP(S) Interface starting on host 0.0.0.0 and port 8387
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubSubscriberStartTest > testMultipleSubscribersStartUpInSamePort STANDARD_OUT
[ballerina/http] started HTTP/WS listener 0.0.0.0:8387
> Task :ballerina-websub:check
> Task :ballerina-websub:build
> Task :ballerina-xmlutils:assemble
> Task :ballerina-xmlutils:checkstyleMain
> Task :ballerina-xmlutils:compileTestJava
```
Output for a failing build - https://api.travis-ci.com/v3/job/253956996/log.txt
```
> Task :ballerina-websub:createTestBalHome
> Task :ballerina-xslt:test
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.xslt.XSLTTest STANDARD_OUT
read-from-file.bal
> Task :ballerina-xslt:check
> Task :ballerina-xslt:build
> Task :benchmarks:compileTestJava NO-SOURCE
> Task :benchmarks:processTestResources NO-SOURCE
> Task :benchmarks:testClasses UP-TO-DATE
> Task :benchmarks:checkstyleTest NO-SOURCE
> Task :benchmarks:spotbugsMain NO-SOURCE
> Task :benchmarks:spotbugsTest SKIPPED
> Task :benchmarks:test NO-SOURCE
> Task :benchmarks:check
> Task :benchmarks:build
> Task :ballerina-streams:test
Ballerina-Streaming-Test-Suite > ballerina-streaming-tests > org.ballerinalang.stdlib.streams.nativeimpl.BallerinaStreamsV2AggregationNativeTest STANDARD_OUT
streamingv2-native-aggregation-unit-test.bal
> Task :composer-library:updateVersion
update version to 1.0.4-SNAPSHOT in :composer-library
> @ballerina/composer@1.0.3 update-version /home/travis/build/ballerina-platform/ballerina-lang/composer
> node ./scripts/update-version.js "1.0.4-SNAPSHOT"
> Task :ballerina-websub:test
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubCompilationTest STANDARD_OUT
test_compilation_failure.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubCompilationTest > testInvalidAnnotationCount STANDARD_OUT
test_multiple_annots.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubCompilationTest > testInvalidResourceReturnType STANDARD_OUT
test_invalid_return_negative.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubDiscoveryResponseParserTest STANDARD_OUT
test_discovery_response_parsing.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubDiscoveryResponseParserTest STANDARD_ERROR
Nov 08, 2019 5:26:50 AM org.quartz.impl.StdSchedulerFactory instantiate
INFO: Using default implementation for ThreadExecutor
Nov 08, 2019 5:26:50 AM org.quartz.core.SchedulerSignalerImpl <init>
INFO: Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
Nov 08, 2019 5:26:50 AM org.quartz.core.QuartzScheduler <init>
INFO: Quartz Scheduler v.2.3.1 created.
Nov 08, 2019 5:26:50 AM org.quartz.simpl.RAMJobStore initialize
INFO: RAMJobStore initialized.
Nov 08, 2019 5:26:50 AM org.quartz.core.QuartzScheduler initialize
INFO: Scheduler meta-data: Quartz Scheduler (v2.3.1) 'QuartzScheduler' with instanceId 'NON_CLUSTERED'
Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.
Nov 08, 2019 5:26:50 AM org.quartz.impl.StdSchedulerFactory instantiate
INFO: Quartz scheduler 'QuartzScheduler' initialized from an externally provided properties instance.
Nov 08, 2019 5:26:50 AM org.quartz.impl.StdSchedulerFactory instantiate
INFO: Quartz scheduler version: 2.3.1
Nov 08, 2019 5:26:50 AM org.quartz.core.QuartzScheduler start
INFO: Scheduler QuartzScheduler_$_NON_CLUSTERED started.
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest STANDARD_OUT
test_hub_startup.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 5:26:55 AM io.ballerina.messaging.broker.core.BrokerImpl$BrokerHelper startMessageDelivery
INFO: Starting message delivery threads.
Nov 08, 2019 5:26:55 AM io.ballerina.messaging.broker.core.task.TaskExecutorService start
INFO: Starting task manager. Task count 0
[ballerina/websub] Ballerina WebSub Hub started up.
[ballerina/websub] Publish URL: https://localhost:9191/websub/pub
[ballerina/websub] Subscription URL: https://localhost:9191/websub/hub
Nov 08, 2019 5:26:56 AM org.ballerinalang.net.http.HTTPServicesRegistry registerService
INFO: Service deployed : $anonService$0$$service$1 with context /websub
Nov 08, 2019 5:26:57 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector lambda$start$0
INFO: HTTP(S) Interface starting on host 0.0.0.0 and port 9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] started HTTP/WS listener 0.0.0.0:9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 5:26:57 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector unBindInterface
INFO: HttpConnectorListener stopped listening on host 0.0.0.0 and port 9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] stopped HTTP/WS listener 0.0.0.0:9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 5:26:57 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector unBindInterface
INFO: HttpConnectorListener stopped listening on host 0.0.0.0 and port 9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] stopped HTTP/WS listener 0.0.0.0:9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
[ballerina/websub] Ballerina WebSub Hub started up.
[ballerina/websub] Publish URL: http://localhost:9393/publish
[ballerina/websub] Subscription URL: http://localhost:9393/
Nov 08, 2019 5:26:57 AM org.ballerinalang.net.http.HTTPServicesRegistry registerService
INFO: Service deployed : $anonService$0$$service$1 with context /
Nov 08, 2019 5:26:57 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector lambda$start$0
INFO: HTTP(S) Interface starting on host 0.0.0.0 and port 9393
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] started HTTP/WS listener 0.0.0.0:9393
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 5:26:57 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector unBindInterface
INFO: HttpConnectorListener stopped listening on host 0.0.0.0 and port 9393
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] stopped HTTP/WS listener 0.0.0.0:9393
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 5:26:57 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector unBindInterface
INFO: HttpConnectorListener stopped listening on host 0.0.0.0 and port 9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] stopped HTTP/WS listener 0.0.0.0:9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubSpecificSubscriberValidationTest STANDARD_OUT
test_specific_subscriber.bal
> Task :ballerina-streams:test
Ballerina-Streaming-Test-Suite > ballerina-streaming-tests > org.ballerinalang.stdlib.streams.BallerinaStreamsV2CustomWindowTest STANDARD_OUT
streamingv2-custom-window-test.bal
Ballerina-Streaming-Test-Suite > ballerina-streaming-tests > org.ballerinalang.stdlib.streams.BallerinaStreamsV2FilterWithFunctionTest STANDARD_OUT
streamingv2-filter-with-function-test.bal
streamingv2-filter-with-function-test2.bal
streamingv2-filter-with-function-test.bal
streamingv2-filter-with-function-test2.bal
Ballerina-Streaming-Test-Suite > ballerina-streaming-tests > org.ballerinalang.stdlib.streams.BallerinaStreamsV2OrderByTest STANDARD_OUT
streamingv2-orderby-test.bal
streamingv2-orderby-with-functions-test.bal
streamingv2-orderby-test.bal
streamingv2-orderby-with-functions-test.bal
Ballerina-Streaming-Test-Suite > ballerina-streaming-tests > org.ballerinalang.stdlib.streams.nativeimpl.BallerinaStreamsV2HavingTest STANDARD_OUT
streamingv2-native-having-test.bal
Ballerina-Streaming-Test-Suite > ballerina-streaming-tests > org.ballerinalang.stdlib.streams.BallerinaStreamsV2AggregatorWithoutGroupByTest STANDARD_OUT
streamingv2-aggregate-without-groupby-test.bal
Ballerina-Streaming-Test-Suite > ballerina-streaming-tests > org.ballerinalang.stdlib.streams.BallerinaStreamsV2JoinTest STANDARD_OUT
streamingv2-join-test.bal
> Task :composer-library:npmInstall
``` | 1.0 | Re-enable WebSubSubscriberStartTest - **Description:**
WebSubSubscriberStartTest is being disabled temporarily since this is suspected to be causing the build to hang.
Output for a passing build - https://api.travis-ci.com/v3/job/253956997/log.txt
```
> Task :ballerina-websub:createTestBalHome
> Task :ballerina-websub:test
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubCompilationTest STANDARD_OUT
test_compilation_failure.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubCompilationTest > testInvalidAnnotationCount STANDARD_OUT
test_multiple_annots.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubCompilationTest > testInvalidResourceReturnType STANDARD_OUT
test_invalid_return_negative.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubDiscoveryResponseParserTest STANDARD_OUT
test_discovery_response_parsing.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubDiscoveryResponseParserTest STANDARD_ERROR
Nov 08, 2019 6:05:28 AM org.quartz.impl.StdSchedulerFactory instantiate
INFO: Using default implementation for ThreadExecutor
Nov 08, 2019 6:05:28 AM org.quartz.core.SchedulerSignalerImpl <init>
INFO: Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
Nov 08, 2019 6:05:28 AM org.quartz.core.QuartzScheduler <init>
INFO: Quartz Scheduler v.2.3.1 created.
Nov 08, 2019 6:05:28 AM org.quartz.simpl.RAMJobStore initialize
INFO: RAMJobStore initialized.
Nov 08, 2019 6:05:28 AM org.quartz.core.QuartzScheduler initialize
INFO: Scheduler meta-data: Quartz Scheduler (v2.3.1) 'QuartzScheduler' with instanceId 'NON_CLUSTERED'
Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.
Nov 08, 2019 6:05:28 AM org.quartz.impl.StdSchedulerFactory instantiate
INFO: Quartz scheduler 'QuartzScheduler' initialized from an externally provided properties instance.
Nov 08, 2019 6:05:28 AM org.quartz.impl.StdSchedulerFactory instantiate
INFO: Quartz scheduler version: 2.3.1
Nov 08, 2019 6:05:28 AM org.quartz.core.QuartzScheduler start
INFO: Scheduler QuartzScheduler_$_NON_CLUSTERED started.
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest STANDARD_OUT
test_hub_startup.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 6:05:32 AM io.ballerina.messaging.broker.core.BrokerImpl$BrokerHelper startMessageDelivery
INFO: Starting message delivery threads.
Nov 08, 2019 6:05:32 AM io.ballerina.messaging.broker.core.task.TaskExecutorService start
INFO: Starting task manager. Task count 0
[ballerina/websub] Ballerina WebSub Hub started up.
[ballerina/websub] Publish URL: https://localhost:9191/websub/pub
[ballerina/websub] Subscription URL: https://localhost:9191/websub/hub
Nov 08, 2019 6:05:32 AM org.ballerinalang.net.http.HTTPServicesRegistry registerService
INFO: Service deployed : $anonService$0$$service$1 with context /websub
Nov 08, 2019 6:05:32 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector lambda$start$0
INFO: HTTP(S) Interface starting on host 0.0.0.0 and port 9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] started HTTP/WS listener 0.0.0.0:9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 6:05:32 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector unBindInterface
INFO: HttpConnectorListener stopped listening on host 0.0.0.0 and port 9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] stopped HTTP/WS listener 0.0.0.0:9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 6:05:32 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector unBindInterface
INFO: HttpConnectorListener stopped listening on host 0.0.0.0 and port 9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] stopped HTTP/WS listener 0.0.0.0:9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
[ballerina/websub] Ballerina WebSub Hub started up.
[ballerina/websub] Publish URL: http://localhost:9393/publish
[ballerina/websub] Subscription URL: http://localhost:9393/
Nov 08, 2019 6:05:32 AM org.ballerinalang.net.http.HTTPServicesRegistry registerService
INFO: Service deployed : $anonService$0$$service$1 with context /
Nov 08, 2019 6:05:32 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector lambda$start$0
INFO: HTTP(S) Interface starting on host 0.0.0.0 and port 9393
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] started HTTP/WS listener 0.0.0.0:9393
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 6:05:32 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector unBindInterface
INFO: HttpConnectorListener stopped listening on host 0.0.0.0 and port 9393
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] stopped HTTP/WS listener 0.0.0.0:9393
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 6:05:32 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector unBindInterface
INFO: HttpConnectorListener stopped listening on host 0.0.0.0 and port 9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] stopped HTTP/WS listener 0.0.0.0:9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubSpecificSubscriberValidationTest STANDARD_OUT
test_specific_subscriber.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubSpecificSubscriberValidationTest > testInvalidParam STANDARD_ERROR
Nov 08, 2019 6:05:35 AM org.ballerinalang.net.websub.WebSubServicesRegistry registerWebSubSubscriberService
INFO: Service deployed : $anonService$2$$service$3 with context /key
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubSpecificSubscriberValidationTest > testInvalidResourceFunctions STANDARD_ERROR
Nov 08, 2019 6:05:35 AM org.ballerinalang.net.websub.WebSubServicesRegistry registerWebSubSubscriberService
INFO: Service deployed : $anonService$0$$service$1 with context /key
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubSubscriberStartTest STANDARD_OUT
test_subscriber_startup.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubSubscriberStartTest > testMultipleSubscribersStartUpInSamePort STANDARD_ERROR
Nov 08, 2019 6:05:37 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector lambda$start$0
INFO: HTTP(S) Interface starting on host 0.0.0.0 and port 8387
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubSubscriberStartTest > testMultipleSubscribersStartUpInSamePort STANDARD_OUT
[ballerina/http] started HTTP/WS listener 0.0.0.0:8387
> Task :ballerina-websub:check
> Task :ballerina-websub:build
> Task :ballerina-xmlutils:assemble
> Task :ballerina-xmlutils:checkstyleMain
> Task :ballerina-xmlutils:compileTestJava
```
Output for a failing build - https://api.travis-ci.com/v3/job/253956996/log.txt
```
> Task :ballerina-websub:createTestBalHome
> Task :ballerina-xslt:test
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.xslt.XSLTTest STANDARD_OUT
read-from-file.bal
> Task :ballerina-xslt:check
> Task :ballerina-xslt:build
> Task :benchmarks:compileTestJava NO-SOURCE
> Task :benchmarks:processTestResources NO-SOURCE
> Task :benchmarks:testClasses UP-TO-DATE
> Task :benchmarks:checkstyleTest NO-SOURCE
> Task :benchmarks:spotbugsMain NO-SOURCE
> Task :benchmarks:spotbugsTest SKIPPED
> Task :benchmarks:test NO-SOURCE
> Task :benchmarks:check
> Task :benchmarks:build
> Task :ballerina-streams:test
Ballerina-Streaming-Test-Suite > ballerina-streaming-tests > org.ballerinalang.stdlib.streams.nativeimpl.BallerinaStreamsV2AggregationNativeTest STANDARD_OUT
streamingv2-native-aggregation-unit-test.bal
> Task :composer-library:updateVersion
update version to 1.0.4-SNAPSHOT in :composer-library
> @ballerina/composer@1.0.3 update-version /home/travis/build/ballerina-platform/ballerina-lang/composer
> node ./scripts/update-version.js "1.0.4-SNAPSHOT"
> Task :ballerina-websub:test
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubCompilationTest STANDARD_OUT
test_compilation_failure.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubCompilationTest > testInvalidAnnotationCount STANDARD_OUT
test_multiple_annots.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubCompilationTest > testInvalidResourceReturnType STANDARD_OUT
test_invalid_return_negative.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubDiscoveryResponseParserTest STANDARD_OUT
test_discovery_response_parsing.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubDiscoveryResponseParserTest STANDARD_ERROR
Nov 08, 2019 5:26:50 AM org.quartz.impl.StdSchedulerFactory instantiate
INFO: Using default implementation for ThreadExecutor
Nov 08, 2019 5:26:50 AM org.quartz.core.SchedulerSignalerImpl <init>
INFO: Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
Nov 08, 2019 5:26:50 AM org.quartz.core.QuartzScheduler <init>
INFO: Quartz Scheduler v.2.3.1 created.
Nov 08, 2019 5:26:50 AM org.quartz.simpl.RAMJobStore initialize
INFO: RAMJobStore initialized.
Nov 08, 2019 5:26:50 AM org.quartz.core.QuartzScheduler initialize
INFO: Scheduler meta-data: Quartz Scheduler (v2.3.1) 'QuartzScheduler' with instanceId 'NON_CLUSTERED'
Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.
Nov 08, 2019 5:26:50 AM org.quartz.impl.StdSchedulerFactory instantiate
INFO: Quartz scheduler 'QuartzScheduler' initialized from an externally provided properties instance.
Nov 08, 2019 5:26:50 AM org.quartz.impl.StdSchedulerFactory instantiate
INFO: Quartz scheduler version: 2.3.1
Nov 08, 2019 5:26:50 AM org.quartz.core.QuartzScheduler start
INFO: Scheduler QuartzScheduler_$_NON_CLUSTERED started.
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest STANDARD_OUT
test_hub_startup.bal
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 5:26:55 AM io.ballerina.messaging.broker.core.BrokerImpl$BrokerHelper startMessageDelivery
INFO: Starting message delivery threads.
Nov 08, 2019 5:26:55 AM io.ballerina.messaging.broker.core.task.TaskExecutorService start
INFO: Starting task manager. Task count 0
[ballerina/websub] Ballerina WebSub Hub started up.
[ballerina/websub] Publish URL: https://localhost:9191/websub/pub
[ballerina/websub] Subscription URL: https://localhost:9191/websub/hub
Nov 08, 2019 5:26:56 AM org.ballerinalang.net.http.HTTPServicesRegistry registerService
INFO: Service deployed : $anonService$0$$service$1 with context /websub
Nov 08, 2019 5:26:57 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector lambda$start$0
INFO: HTTP(S) Interface starting on host 0.0.0.0 and port 9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] started HTTP/WS listener 0.0.0.0:9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 5:26:57 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector unBindInterface
INFO: HttpConnectorListener stopped listening on host 0.0.0.0 and port 9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] stopped HTTP/WS listener 0.0.0.0:9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 5:26:57 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector unBindInterface
INFO: HttpConnectorListener stopped listening on host 0.0.0.0 and port 9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] stopped HTTP/WS listener 0.0.0.0:9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
[ballerina/websub] Ballerina WebSub Hub started up.
[ballerina/websub] Publish URL: http://localhost:9393/publish
[ballerina/websub] Subscription URL: http://localhost:9393/
Nov 08, 2019 5:26:57 AM org.ballerinalang.net.http.HTTPServicesRegistry registerService
INFO: Service deployed : $anonService$0$$service$1 with context /
Nov 08, 2019 5:26:57 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector lambda$start$0
INFO: HTTP(S) Interface starting on host 0.0.0.0 and port 9393
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] started HTTP/WS listener 0.0.0.0:9393
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 5:26:57 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector unBindInterface
INFO: HttpConnectorListener stopped listening on host 0.0.0.0 and port 9393
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] stopped HTTP/WS listener 0.0.0.0:9393
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_ERROR
Nov 08, 2019 5:26:57 AM org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector unBindInterface
INFO: HttpConnectorListener stopped listening on host 0.0.0.0 and port 9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubHubStartTest > testHubStartUp STANDARD_OUT
[ballerina/http] stopped HTTP/WS listener 0.0.0.0:9191
ballerina-test-suite > ballerina-lang-test-suite > org.ballerinalang.net.websub.WebSubSpecificSubscriberValidationTest STANDARD_OUT
test_specific_subscriber.bal
> Task :ballerina-streams:test
Ballerina-Streaming-Test-Suite > ballerina-streaming-tests > org.ballerinalang.stdlib.streams.BallerinaStreamsV2CustomWindowTest STANDARD_OUT
streamingv2-custom-window-test.bal
Ballerina-Streaming-Test-Suite > ballerina-streaming-tests > org.ballerinalang.stdlib.streams.BallerinaStreamsV2FilterWithFunctionTest STANDARD_OUT
streamingv2-filter-with-function-test.bal
streamingv2-filter-with-function-test2.bal
streamingv2-filter-with-function-test.bal
streamingv2-filter-with-function-test2.bal
Ballerina-Streaming-Test-Suite > ballerina-streaming-tests > org.ballerinalang.stdlib.streams.BallerinaStreamsV2OrderByTest STANDARD_OUT
streamingv2-orderby-test.bal
streamingv2-orderby-with-functions-test.bal
streamingv2-orderby-test.bal
streamingv2-orderby-with-functions-test.bal
Ballerina-Streaming-Test-Suite > ballerina-streaming-tests > org.ballerinalang.stdlib.streams.nativeimpl.BallerinaStreamsV2HavingTest STANDARD_OUT
streamingv2-native-having-test.bal
Ballerina-Streaming-Test-Suite > ballerina-streaming-tests > org.ballerinalang.stdlib.streams.BallerinaStreamsV2AggregatorWithoutGroupByTest STANDARD_OUT
streamingv2-aggregate-without-groupby-test.bal
Ballerina-Streaming-Test-Suite > ballerina-streaming-tests > org.ballerinalang.stdlib.streams.BallerinaStreamsV2JoinTest STANDARD_OUT
streamingv2-join-test.bal
> Task :composer-library:npmInstall
``` | non_infrastructure | re enable websubsubscriberstarttest description websubsubscriberstarttest is being disabled temporarily since this is suspected to be causing the build to hang output for a passing build task ballerina websub createtestbalhome task ballerina websub test ballerina test suite ballerina lang test suite org ballerinalang net websub websubcompilationtest standard out test compilation failure bal ballerina test suite ballerina lang test suite org ballerinalang net websub websubcompilationtest testinvalidannotationcount standard out test multiple annots bal ballerina test suite ballerina lang test suite org ballerinalang net websub websubcompilationtest testinvalidresourcereturntype standard out test invalid return negative bal ballerina test suite ballerina lang test suite org ballerinalang net websub websubdiscoveryresponseparsertest standard out test discovery response parsing bal ballerina test suite ballerina lang test suite org ballerinalang net websub websubdiscoveryresponseparsertest standard error nov am org quartz impl stdschedulerfactory instantiate info using default implementation for threadexecutor nov am org quartz core schedulersignalerimpl info initialized scheduler signaller of type class org quartz core schedulersignalerimpl nov am org quartz core quartzscheduler info quartz scheduler v created nov am org quartz simpl ramjobstore initialize info ramjobstore initialized nov am org quartz core quartzscheduler initialize info scheduler meta data quartz scheduler quartzscheduler with instanceid non clustered scheduler class org quartz core quartzscheduler running locally not started currently in standby mode number of jobs executed using thread pool org quartz simpl simplethreadpool with threads using job store org quartz simpl ramjobstore which does not support persistence and is not clustered nov am org quartz impl stdschedulerfactory instantiate info quartz scheduler quartzscheduler initialized from an externally provided properties instance nov am org quartz impl stdschedulerfactory instantiate info quartz scheduler version nov am org quartz core quartzscheduler start info scheduler quartzscheduler non clustered started ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest standard out test hub startup bal ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard error nov am io ballerina messaging broker core brokerimpl brokerhelper startmessagedelivery info starting message delivery threads nov am io ballerina messaging broker core task taskexecutorservice start info starting task manager task count ballerina websub hub started up publish url subscription url nov am org ballerinalang net http httpservicesregistry registerservice info service deployed anonservice service with context websub nov am org transport http netty contractimpl listener serverconnectorbootstrap httpserverconnector lambda start info http s interface starting on host and port ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard out started http ws listener ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard error nov am org transport http netty contractimpl listener serverconnectorbootstrap httpserverconnector unbindinterface info httpconnectorlistener stopped listening on host and port ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard out stopped http ws listener ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard error nov am org transport http netty contractimpl listener serverconnectorbootstrap httpserverconnector unbindinterface info httpconnectorlistener stopped listening on host and port ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard out stopped http ws listener ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard error ballerina websub hub started up publish url subscription url nov am org ballerinalang net http httpservicesregistry registerservice info service deployed anonservice service with context nov am org transport http netty contractimpl listener serverconnectorbootstrap httpserverconnector lambda start info http s interface starting on host and port ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard out started http ws listener ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard error nov am org transport http netty contractimpl listener serverconnectorbootstrap httpserverconnector unbindinterface info httpconnectorlistener stopped listening on host and port ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard out stopped http ws listener ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard error nov am org transport http netty contractimpl listener serverconnectorbootstrap httpserverconnector unbindinterface info httpconnectorlistener stopped listening on host and port ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard out stopped http ws listener ballerina test suite ballerina lang test suite org ballerinalang net websub websubspecificsubscribervalidationtest standard out test specific subscriber bal ballerina test suite ballerina lang test suite org ballerinalang net websub websubspecificsubscribervalidationtest testinvalidparam standard error nov am org ballerinalang net websub websubservicesregistry registerwebsubsubscriberservice info service deployed anonservice service with context key ballerina test suite ballerina lang test suite org ballerinalang net websub websubspecificsubscribervalidationtest testinvalidresourcefunctions standard error nov am org ballerinalang net websub websubservicesregistry registerwebsubsubscriberservice info service deployed anonservice service with context key ballerina test suite ballerina lang test suite org ballerinalang net websub websubsubscriberstarttest standard out test subscriber startup bal ballerina test suite ballerina lang test suite org ballerinalang net websub websubsubscriberstarttest testmultiplesubscribersstartupinsameport standard error nov am org transport http netty contractimpl listener serverconnectorbootstrap httpserverconnector lambda start info http s interface starting on host and port ballerina test suite ballerina lang test suite org ballerinalang net websub websubsubscriberstarttest testmultiplesubscribersstartupinsameport standard out started http ws listener task ballerina websub check task ballerina websub build task ballerina xmlutils assemble task ballerina xmlutils checkstylemain task ballerina xmlutils compiletestjava output for a failing build task ballerina websub createtestbalhome task ballerina xslt test ballerina test suite ballerina lang test suite org ballerinalang xslt xslttest standard out read from file bal task ballerina xslt check task ballerina xslt build task benchmarks compiletestjava no source task benchmarks processtestresources no source task benchmarks testclasses up to date task benchmarks checkstyletest no source task benchmarks spotbugsmain no source task benchmarks spotbugstest skipped task benchmarks test no source task benchmarks check task benchmarks build task ballerina streams test ballerina streaming test suite ballerina streaming tests org ballerinalang stdlib streams nativeimpl standard out native aggregation unit test bal task composer library updateversion update version to snapshot in composer library ballerina composer update version home travis build ballerina platform ballerina lang composer node scripts update version js snapshot task ballerina websub test ballerina test suite ballerina lang test suite org ballerinalang net websub websubcompilationtest standard out test compilation failure bal ballerina test suite ballerina lang test suite org ballerinalang net websub websubcompilationtest testinvalidannotationcount standard out test multiple annots bal ballerina test suite ballerina lang test suite org ballerinalang net websub websubcompilationtest testinvalidresourcereturntype standard out test invalid return negative bal ballerina test suite ballerina lang test suite org ballerinalang net websub websubdiscoveryresponseparsertest standard out test discovery response parsing bal ballerina test suite ballerina lang test suite org ballerinalang net websub websubdiscoveryresponseparsertest standard error nov am org quartz impl stdschedulerfactory instantiate info using default implementation for threadexecutor nov am org quartz core schedulersignalerimpl info initialized scheduler signaller of type class org quartz core schedulersignalerimpl nov am org quartz core quartzscheduler info quartz scheduler v created nov am org quartz simpl ramjobstore initialize info ramjobstore initialized nov am org quartz core quartzscheduler initialize info scheduler meta data quartz scheduler quartzscheduler with instanceid non clustered scheduler class org quartz core quartzscheduler running locally not started currently in standby mode number of jobs executed using thread pool org quartz simpl simplethreadpool with threads using job store org quartz simpl ramjobstore which does not support persistence and is not clustered nov am org quartz impl stdschedulerfactory instantiate info quartz scheduler quartzscheduler initialized from an externally provided properties instance nov am org quartz impl stdschedulerfactory instantiate info quartz scheduler version nov am org quartz core quartzscheduler start info scheduler quartzscheduler non clustered started ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest standard out test hub startup bal ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard error nov am io ballerina messaging broker core brokerimpl brokerhelper startmessagedelivery info starting message delivery threads nov am io ballerina messaging broker core task taskexecutorservice start info starting task manager task count ballerina websub hub started up publish url subscription url nov am org ballerinalang net http httpservicesregistry registerservice info service deployed anonservice service with context websub nov am org transport http netty contractimpl listener serverconnectorbootstrap httpserverconnector lambda start info http s interface starting on host and port ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard out started http ws listener ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard error nov am org transport http netty contractimpl listener serverconnectorbootstrap httpserverconnector unbindinterface info httpconnectorlistener stopped listening on host and port ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard out stopped http ws listener ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard error nov am org transport http netty contractimpl listener serverconnectorbootstrap httpserverconnector unbindinterface info httpconnectorlistener stopped listening on host and port ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard out stopped http ws listener ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard error ballerina websub hub started up publish url subscription url nov am org ballerinalang net http httpservicesregistry registerservice info service deployed anonservice service with context nov am org transport http netty contractimpl listener serverconnectorbootstrap httpserverconnector lambda start info http s interface starting on host and port ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard out started http ws listener ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard error nov am org transport http netty contractimpl listener serverconnectorbootstrap httpserverconnector unbindinterface info httpconnectorlistener stopped listening on host and port ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard out stopped http ws listener ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard error nov am org transport http netty contractimpl listener serverconnectorbootstrap httpserverconnector unbindinterface info httpconnectorlistener stopped listening on host and port ballerina test suite ballerina lang test suite org ballerinalang net websub websubhubstarttest testhubstartup standard out stopped http ws listener ballerina test suite ballerina lang test suite org ballerinalang net websub websubspecificsubscribervalidationtest standard out test specific subscriber bal task ballerina streams test ballerina streaming test suite ballerina streaming tests org ballerinalang stdlib streams standard out custom window test bal ballerina streaming test suite ballerina streaming tests org ballerinalang stdlib streams standard out filter with function test bal filter with function bal filter with function test bal filter with function bal ballerina streaming test suite ballerina streaming tests org ballerinalang stdlib streams standard out orderby test bal orderby with functions test bal orderby test bal orderby with functions test bal ballerina streaming test suite ballerina streaming tests org ballerinalang stdlib streams nativeimpl standard out native having test bal ballerina streaming test suite ballerina streaming tests org ballerinalang stdlib streams standard out aggregate without groupby test bal ballerina streaming test suite ballerina streaming tests org ballerinalang stdlib streams standard out join test bal task composer library npminstall | 0 |
34,423 | 29,867,161,793 | IssuesEvent | 2023-06-20 05:29:13 | apache/hop | https://api.github.com/repos/apache/hop | closed | [Task]: Update Helm documentation and chart value | task P3 Infrastructure | ### What needs to happen?
- Add a Readme in the helm chart
- Stick to latest hop version in `appVersion` of the chart
### Issue Priority
Priority: 3
### Issue Component
Component: Infrastructure | 1.0 | [Task]: Update Helm documentation and chart value - ### What needs to happen?
- Add a Readme in the helm chart
- Stick to latest hop version in `appVersion` of the chart
### Issue Priority
Priority: 3
### Issue Component
Component: Infrastructure | infrastructure | update helm documentation and chart value what needs to happen add a readme in the helm chart stick to latest hop version in appversion of the chart issue priority priority issue component component infrastructure | 1 |
16,484 | 11,993,041,981 | IssuesEvent | 2020-04-08 11:14:50 | ampproject/amp-wp | https://api.github.com/repos/ampproject/amp-wp | opened | Add unified sanitizer smoke test | Infrastructure | ## Feature description
I think it would be valuable to have a single test that runs a big chunk of HTML through the sanitizer which contains at least 1 validation error for each of the different sanitizer.
This would allow us to ensure that all sanitizers are active and working.
As an example of what this would catch early on, see https://github.com/ampproject/amp-wp/pull/4535#pullrequestreview-389647527, which demonstrates that:
- I'm a fool;
- PRs that have passing tests can still fail at a fundamental level, which would only be caught during QA right now.
---------------
_Do not alter or remove anything below. The following sections will be managed by moderators only._
## Acceptance criteria
* Have at least 1 test that would fail if any single one of the sanitizers is inactive or ineffective.
## Implementation brief
* <!-- One or more bullet points for how to technically resolve the issue. For significant Implementation Design, it is ok use a Google document **accessible by anyone**. -->
## QA testing instructions
* <!-- One or more bullet points to describe how to test the implementation in QA. -->
## Demo
* <!-- A video or screenshots demoing the implementation. -->
## Changelog entry
* <!-- One sentence summarizing the PR, to be used in the changelog. -->
| 1.0 | Add unified sanitizer smoke test - ## Feature description
I think it would be valuable to have a single test that runs a big chunk of HTML through the sanitizer which contains at least 1 validation error for each of the different sanitizer.
This would allow us to ensure that all sanitizers are active and working.
As an example of what this would catch early on, see https://github.com/ampproject/amp-wp/pull/4535#pullrequestreview-389647527, which demonstrates that:
- I'm a fool;
- PRs that have passing tests can still fail at a fundamental level, which would only be caught during QA right now.
---------------
_Do not alter or remove anything below. The following sections will be managed by moderators only._
## Acceptance criteria
* Have at least 1 test that would fail if any single one of the sanitizers is inactive or ineffective.
## Implementation brief
* <!-- One or more bullet points for how to technically resolve the issue. For significant Implementation Design, it is ok use a Google document **accessible by anyone**. -->
## QA testing instructions
* <!-- One or more bullet points to describe how to test the implementation in QA. -->
## Demo
* <!-- A video or screenshots demoing the implementation. -->
## Changelog entry
* <!-- One sentence summarizing the PR, to be used in the changelog. -->
| infrastructure | add unified sanitizer smoke test feature description i think it would be valuable to have a single test that runs a big chunk of html through the sanitizer which contains at least validation error for each of the different sanitizer this would allow us to ensure that all sanitizers are active and working as an example of what this would catch early on see which demonstrates that i m a fool prs that have passing tests can still fail at a fundamental level which would only be caught during qa right now do not alter or remove anything below the following sections will be managed by moderators only acceptance criteria have at least test that would fail if any single one of the sanitizers is inactive or ineffective implementation brief qa testing instructions demo changelog entry | 1 |
462,979 | 13,257,539,457 | IssuesEvent | 2020-08-20 14:13:24 | climateconnect/climateconnect | https://api.github.com/repos/climateconnect/climateconnect | closed | Give users visual feedback when something is loading | Priority B frontend | Whenever you submit some type of request to the API, e.g. click a button, you should get some visual feedback such as a preloader to show you that something is happening. Otherwise you might think clicking the button didn't work | 1.0 | Give users visual feedback when something is loading - Whenever you submit some type of request to the API, e.g. click a button, you should get some visual feedback such as a preloader to show you that something is happening. Otherwise you might think clicking the button didn't work | non_infrastructure | give users visual feedback when something is loading whenever you submit some type of request to the api e g click a button you should get some visual feedback such as a preloader to show you that something is happening otherwise you might think clicking the button didn t work | 0 |
6,458 | 6,425,849,068 | IssuesEvent | 2017-08-09 16:10:44 | openshiftio/appdev-documentation | https://api.github.com/repos/openshiftio/appdev-documentation | closed | cico_build_deploy.sh is undocumented | Bug Follow-up Infrastructure | There is currently no documentation of the cico_build_deploy.sh script, which can be used for running the server locally.
Follow-up to #432. | 1.0 | cico_build_deploy.sh is undocumented - There is currently no documentation of the cico_build_deploy.sh script, which can be used for running the server locally.
Follow-up to #432. | infrastructure | cico build deploy sh is undocumented there is currently no documentation of the cico build deploy sh script which can be used for running the server locally follow up to | 1 |
17,329 | 12,302,128,409 | IssuesEvent | 2020-05-11 16:27:27 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | Cross-Compilation not working | area-Infrastructure-coreclr untriaged | Post consolidation of .Net Repos, instructions listed here for cross-complining ARM arch on x86_64
https://github.com/dotnet/runtime/blob/master/docs/workflow/building/coreclr/cross-building.md#cross-compilation-for-arm-arm64-or-x86-on-linux
is not working. This needs an update
1) Is Cross-Compile still supported ?
2) Did anyone attempt cross-compile on dotnet/runtime ? | 1.0 | Cross-Compilation not working - Post consolidation of .Net Repos, instructions listed here for cross-complining ARM arch on x86_64
https://github.com/dotnet/runtime/blob/master/docs/workflow/building/coreclr/cross-building.md#cross-compilation-for-arm-arm64-or-x86-on-linux
is not working. This needs an update
1) Is Cross-Compile still supported ?
2) Did anyone attempt cross-compile on dotnet/runtime ? | infrastructure | cross compilation not working post consolidation of net repos instructions listed here for cross complining arm arch on is not working this needs an update is cross compile still supported did anyone attempt cross compile on dotnet runtime | 1 |
316,271 | 27,149,774,329 | IssuesEvent | 2023-02-16 23:37:13 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | opened | [wasm] `System.Reflection.Tests.MethodInfoTests.TestFunctionPointers` failing with trimming on linux | arch-wasm blocking-clean-ci test-failure | [System.Reflection.Tests log](https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-heads-main-f813c52ee3964e05a1/normal-System.Reflection.Tests/1/console.ee1525d7.log?helixlogtype=result):
```
[22:28:04] fail: [FAIL] System.Reflection.Tests.MethodInfoTests.TestFunctionPointers
[22:28:04] info: System.ArgumentException : Object of type 'System.Reflection.Tests.OtherColorsInt' cannot be converted to type 'System.Reflection.Tests.ColorsShort'.
[22:28:04] info: at System.Reflection.MethodInvoker.Invoke(Object , IntPtr* , BindingFlags )
```
[System.Reflection.InvokeInterpreted.Tests](https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-heads-main-f813c52ee3964e05a1/normal-System.Reflection.InvokeInterpreted.Tests/1/console.f436abc1.log?helixlogtype=result):
```
[22:27:07] fail: [FAIL] System.Reflection.Tests.MethodInfoTests.TestFunctionPointers
[22:27:07] info: System.InvalidOperationException : Operation is not valid due to the current state of the object.
[22:27:07] info: at System.Reflection.MethodInvoker.Invoke(Object , IntPtr* , BindingFlags )
```
[System.Reflection.InvokeEmit.Tests](https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-heads-main-f813c52ee3964e05a1/normal-System.Reflection.InvokeEmit.Tests/1/console.636fa5d7.log?helixlogtype=result):
```
[22:26:59] fail: [FAIL] System.Reflection.Tests.MethodInfoTests.TestFunctionPointers
[22:26:59] info: System.ArgumentException : Missing parameter does not have a default value. (Parameter 'parameters')
[22:26:59] info: at System.Reflection.MethodInvoker.Invoke(Object , IntPtr* , BindingFlags )
```
This was added in https://github.com/dotnet/runtime/pull/81006 and didn't get caught because we run only smoke tests for AOT/wasm on PRs. | 1.0 | [wasm] `System.Reflection.Tests.MethodInfoTests.TestFunctionPointers` failing with trimming on linux - [System.Reflection.Tests log](https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-heads-main-f813c52ee3964e05a1/normal-System.Reflection.Tests/1/console.ee1525d7.log?helixlogtype=result):
```
[22:28:04] fail: [FAIL] System.Reflection.Tests.MethodInfoTests.TestFunctionPointers
[22:28:04] info: System.ArgumentException : Object of type 'System.Reflection.Tests.OtherColorsInt' cannot be converted to type 'System.Reflection.Tests.ColorsShort'.
[22:28:04] info: at System.Reflection.MethodInvoker.Invoke(Object , IntPtr* , BindingFlags )
```
[System.Reflection.InvokeInterpreted.Tests](https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-heads-main-f813c52ee3964e05a1/normal-System.Reflection.InvokeInterpreted.Tests/1/console.f436abc1.log?helixlogtype=result):
```
[22:27:07] fail: [FAIL] System.Reflection.Tests.MethodInfoTests.TestFunctionPointers
[22:27:07] info: System.InvalidOperationException : Operation is not valid due to the current state of the object.
[22:27:07] info: at System.Reflection.MethodInvoker.Invoke(Object , IntPtr* , BindingFlags )
```
[System.Reflection.InvokeEmit.Tests](https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-heads-main-f813c52ee3964e05a1/normal-System.Reflection.InvokeEmit.Tests/1/console.636fa5d7.log?helixlogtype=result):
```
[22:26:59] fail: [FAIL] System.Reflection.Tests.MethodInfoTests.TestFunctionPointers
[22:26:59] info: System.ArgumentException : Missing parameter does not have a default value. (Parameter 'parameters')
[22:26:59] info: at System.Reflection.MethodInvoker.Invoke(Object , IntPtr* , BindingFlags )
```
This was added in https://github.com/dotnet/runtime/pull/81006 and didn't get caught because we run only smoke tests for AOT/wasm on PRs. | non_infrastructure | system reflection tests methodinfotests testfunctionpointers failing with trimming on linux fail system reflection tests methodinfotests testfunctionpointers info system argumentexception object of type system reflection tests othercolorsint cannot be converted to type system reflection tests colorsshort info at system reflection methodinvoker invoke object intptr bindingflags fail system reflection tests methodinfotests testfunctionpointers info system invalidoperationexception operation is not valid due to the current state of the object info at system reflection methodinvoker invoke object intptr bindingflags fail system reflection tests methodinfotests testfunctionpointers info system argumentexception missing parameter does not have a default value parameter parameters info at system reflection methodinvoker invoke object intptr bindingflags this was added in and didn t get caught because we run only smoke tests for aot wasm on prs | 0 |
157,817 | 24,732,085,279 | IssuesEvent | 2022-10-20 18:30:08 | rancher/dashboard | https://api.github.com/repos/rancher/dashboard | closed | UX Clarity on which registry takes precedence | kind/design [zube]: Design Backlog kind/enhancement | When multiple registries are set, Global level registry or cluster level registry, it's not clear to the end user of when/which registry is used when provisioning clusters or deploying Feature helm charts.
Not sure if we need to make any changes, but setting/understanding expectations would be good. We may have to look at the layout to figure out highlight defaults. | 2.0 | UX Clarity on which registry takes precedence - When multiple registries are set, Global level registry or cluster level registry, it's not clear to the end user of when/which registry is used when provisioning clusters or deploying Feature helm charts.
Not sure if we need to make any changes, but setting/understanding expectations would be good. We may have to look at the layout to figure out highlight defaults. | non_infrastructure | ux clarity on which registry takes precedence when multiple registries are set global level registry or cluster level registry it s not clear to the end user of when which registry is used when provisioning clusters or deploying feature helm charts not sure if we need to make any changes but setting understanding expectations would be good we may have to look at the layout to figure out highlight defaults | 0 |
316,619 | 27,170,543,126 | IssuesEvent | 2023-02-17 18:59:43 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | roachtest: asyncpg failed | C-test-failure O-robot O-roachtest branch-master release-blocker T-sql-sessions | roachtest.asyncpg [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8740106?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8740106?buildTab=artifacts#/asyncpg) on master @ [7e2df35a2f6bf7a859bb0539c8ca43c4e72ed260](https://github.com/cockroachdb/cockroach/commits/7e2df35a2f6bf7a859bb0539c8ca43c4e72ed260):
```
test artifacts and logs in: /artifacts/asyncpg/run_1
(test_runner.go:989).runTest: test timed out (10h0m0s)
(orm_helpers.go:201).summarizeFailed:
Tests run on Cockroach v23.1.0-alpha.2-405-g7e2df35a2f
Tests run against asyncpg v0.24.0
55 Total Tests Run
33 tests passed
22 tests failed
29 tests skipped
0 tests ignored
3 tests passed unexpectedly
0 tests failed unexpectedly
0 tests expected failed but skipped
53 tests expected failed but not run
---
--- PASS: test_copy.TestCopyFrom.test_copy_from_query_basics - unsupported copy syntax (unexpected)
--- PASS: test_copy.TestCopyFrom.test_copy_from_query_cancellation_on_sink_error - unsupported copy syntax (unexpected)
--- PASS: test_copy.TestCopyFrom.test_copy_from_query_cancellation_explicit - unsupported copy syntax (unexpected)
For a full summary look at the asyncpg artifacts
An updated blocklist (asyncpgBlocklist) is available in the artifacts' asyncpg log
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=16</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_fs=ext4</code>
, <code>ROACHTEST_localSSD=true</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/sql-sessions
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*asyncpg.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 2.0 | roachtest: asyncpg failed - roachtest.asyncpg [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8740106?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8740106?buildTab=artifacts#/asyncpg) on master @ [7e2df35a2f6bf7a859bb0539c8ca43c4e72ed260](https://github.com/cockroachdb/cockroach/commits/7e2df35a2f6bf7a859bb0539c8ca43c4e72ed260):
```
test artifacts and logs in: /artifacts/asyncpg/run_1
(test_runner.go:989).runTest: test timed out (10h0m0s)
(orm_helpers.go:201).summarizeFailed:
Tests run on Cockroach v23.1.0-alpha.2-405-g7e2df35a2f
Tests run against asyncpg v0.24.0
55 Total Tests Run
33 tests passed
22 tests failed
29 tests skipped
0 tests ignored
3 tests passed unexpectedly
0 tests failed unexpectedly
0 tests expected failed but skipped
53 tests expected failed but not run
---
--- PASS: test_copy.TestCopyFrom.test_copy_from_query_basics - unsupported copy syntax (unexpected)
--- PASS: test_copy.TestCopyFrom.test_copy_from_query_cancellation_on_sink_error - unsupported copy syntax (unexpected)
--- PASS: test_copy.TestCopyFrom.test_copy_from_query_cancellation_explicit - unsupported copy syntax (unexpected)
For a full summary look at the asyncpg artifacts
An updated blocklist (asyncpgBlocklist) is available in the artifacts' asyncpg log
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=16</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_fs=ext4</code>
, <code>ROACHTEST_localSSD=true</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/sql-sessions
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*asyncpg.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| non_infrastructure | roachtest asyncpg failed roachtest asyncpg with on master test artifacts and logs in artifacts asyncpg run test runner go runtest test timed out orm helpers go summarizefailed tests run on cockroach alpha tests run against asyncpg total tests run tests passed tests failed tests skipped tests ignored tests passed unexpectedly tests failed unexpectedly tests expected failed but skipped tests expected failed but not run pass test copy testcopyfrom test copy from query basics unsupported copy syntax unexpected pass test copy testcopyfrom test copy from query cancellation on sink error unsupported copy syntax unexpected pass test copy testcopyfrom test copy from query cancellation explicit unsupported copy syntax unexpected for a full summary look at the asyncpg artifacts an updated blocklist asyncpgblocklist is available in the artifacts asyncpg log parameters roachtest cloud gce roachtest cpu roachtest encrypted false roachtest fs roachtest localssd true roachtest ssd help see see cc cockroachdb sql sessions | 0 |
5,468 | 5,680,977,007 | IssuesEvent | 2017-04-13 03:55:56 | dotnet/cli | https://api.github.com/repos/dotnet/cli | closed | Add coreclr dependencies check to build for OSX | infrastructure | #1504 Added Coreclr dependency checks for Ubuntu and CentOS.
OSX should be added as well.
libssl is currently the only known dependency. Need to investigate to see if there are others.
| 1.0 | Add coreclr dependencies check to build for OSX - #1504 Added Coreclr dependency checks for Ubuntu and CentOS.
OSX should be added as well.
libssl is currently the only known dependency. Need to investigate to see if there are others.
| infrastructure | add coreclr dependencies check to build for osx added coreclr dependency checks for ubuntu and centos osx should be added as well libssl is currently the only known dependency need to investigate to see if there are others | 1 |
55,743 | 8,028,184,766 | IssuesEvent | 2018-07-27 11:56:36 | keystonejs/keystone | https://api.github.com/repos/keystonejs/keystone | closed | Add Google Analytics to v4 docs | documentation | The GA identifier (from Keystone v3 docs) is `UA-43970386-1`. The current version of GA code should be included in the footer for all v4 docs pages. | 1.0 | Add Google Analytics to v4 docs - The GA identifier (from Keystone v3 docs) is `UA-43970386-1`. The current version of GA code should be included in the footer for all v4 docs pages. | non_infrastructure | add google analytics to docs the ga identifier from keystone docs is ua the current version of ga code should be included in the footer for all docs pages | 0 |
27,124 | 21,188,891,058 | IssuesEvent | 2022-04-08 15:16:27 | pixiebrix/pixiebrix-extension | https://api.github.com/repos/pixiebrix/pixiebrix-extension | opened | Fix RTK error type in base query | infrastructure | Context
- https://github.com/pixiebrix/pixiebrix-extension/pull/3123/files#r846209216
- Data/errors from RTK need to be serializable because RTK places it in the Redux store
Implementation Sketch:
- Change the error clause of RTK base query to return `{error: serializeError(error)}` of the thrown error. NOTE: for Axios errors we have to delete the toJSON property before making the call
- Review all RTK query call sites and ensure they aren't relying on data/status being top-level properties. The callsite is responsible for deserializing and performing actions based on type | 1.0 | Fix RTK error type in base query - Context
- https://github.com/pixiebrix/pixiebrix-extension/pull/3123/files#r846209216
- Data/errors from RTK need to be serializable because RTK places it in the Redux store
Implementation Sketch:
- Change the error clause of RTK base query to return `{error: serializeError(error)}` of the thrown error. NOTE: for Axios errors we have to delete the toJSON property before making the call
- Review all RTK query call sites and ensure they aren't relying on data/status being top-level properties. The callsite is responsible for deserializing and performing actions based on type | infrastructure | fix rtk error type in base query context data errors from rtk need to be serializable because rtk places it in the redux store implementation sketch change the error clause of rtk base query to return error serializeerror error of the thrown error note for axios errors we have to delete the tojson property before making the call review all rtk query call sites and ensure they aren t relying on data status being top level properties the callsite is responsible for deserializing and performing actions based on type | 1 |
246,603 | 18,848,597,729 | IssuesEvent | 2021-11-11 17:43:24 | eclipse-iceoryx/iceoryx | https://api.github.com/repos/eclipse-iceoryx/iceoryx | closed | Typos in goals/non-goals document | documentation | ## Required information
**Operating system:**
Any
**Compiler version:**
Any
**Observed result or behaviour:**
The goals/non-goals document contains typos.
**Expected result or behaviour:**
The document should not contain typos.
**Conditions where it occurred / Performed steps:**
Always.
| 1.0 | Typos in goals/non-goals document - ## Required information
**Operating system:**
Any
**Compiler version:**
Any
**Observed result or behaviour:**
The goals/non-goals document contains typos.
**Expected result or behaviour:**
The document should not contain typos.
**Conditions where it occurred / Performed steps:**
Always.
| non_infrastructure | typos in goals non goals document required information operating system any compiler version any observed result or behaviour the goals non goals document contains typos expected result or behaviour the document should not contain typos conditions where it occurred performed steps always | 0 |
12,764 | 9,936,332,299 | IssuesEvent | 2019-07-02 18:51:00 | dart-lang/sdk | https://api.github.com/repos/dart-lang/sdk | closed | Status update tool crashes on "add more logs" workflow after autofixing tests | area-infrastructure area-test closed-obsolete | The status update tool was used for browser update status fixes, where it autoupdated 30 tests because they were similar. Then, answering "y" to the question "do you want to add more log files", gave a crash and a stack trace that seems to have two frames for each test that was autofixed. Stack trace follows
Trying to find if any new errors have arised from the fixes.
No errors found.. Do you want to add more logs? (y)es or (n)o.
y
Unhandled exception:
NoSuchMethodError: The getter 'isEmpty' was called on null.
Receiver: null
Tried calling: isEmpty
#0 Object._noSuchMethod (dart:core-patch/object_patch.dart:42)
#1 Object.noSuchMethod (dart:core-patch/object_patch.dart:46)
#2 FixFailingTest.onShow (package:gardening/src/results_workflow/fix_failing_test.dart:41:17)
<asynchronous suspension>
#3 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:97:53)
<asynchronous suspension>
#4 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:86:14)
<asynchronous suspension>
#5 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#6 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#7 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#8 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#9 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#10 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#11 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#12 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#13 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#14 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#15 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#16 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#17 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#18 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#19 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#20 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#21 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#22 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#23 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#24 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#25 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#26 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#27 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#28 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#29 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#30 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#31 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#32 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#33 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#34 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#35 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#36 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#37 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#38 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#39 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#40 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#41 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#42 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#43 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#44 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#45 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#46 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#47 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#48 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#49 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#50 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#51 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#52 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#53 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#54 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#55 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#56 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#57 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#58 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#59 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#60 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#61 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#62 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#63 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#64 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#65 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#66 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#67 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:86:14)
<asynchronous suspension>
#68 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:86:14)
<asynchronous suspension>
#69 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#70 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#71 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:86:14)
<asynchronous suspension>
#72 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#73 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#74 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#75 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#76 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:86:14)
<asynchronous suspension>
#77 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#78 Workflow.start (package:gardening/src/workflow.dart:61:12)
#79 StatusCommand.run (file:///usr/local/google/home/whesse/ssd/sdk/tools/gardening/bin/results_status.dart:27:21)
<asynchronous suspension>
#80 CommandRunner.runCommand (package:args/command_runner.dart:194:27)
<asynchronous suspension>
#81 CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:109:29)
#82 new Future.sync (dart:async/future.dart:222)
#83 CommandRunner.run (package:args/command_runner.dart:109:11)
#84 main (file:///usr/local/google/home/whesse/ssd/sdk/tools/gardening/bin/results.dart:17:10)
#85 _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:263)
#86 _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:151)
@athomas | 1.0 | Status update tool crashes on "add more logs" workflow after autofixing tests - The status update tool was used for browser update status fixes, where it autoupdated 30 tests because they were similar. Then, answering "y" to the question "do you want to add more log files", gave a crash and a stack trace that seems to have two frames for each test that was autofixed. Stack trace follows
Trying to find if any new errors have arised from the fixes.
No errors found.. Do you want to add more logs? (y)es or (n)o.
y
Unhandled exception:
NoSuchMethodError: The getter 'isEmpty' was called on null.
Receiver: null
Tried calling: isEmpty
#0 Object._noSuchMethod (dart:core-patch/object_patch.dart:42)
#1 Object.noSuchMethod (dart:core-patch/object_patch.dart:46)
#2 FixFailingTest.onShow (package:gardening/src/results_workflow/fix_failing_test.dart:41:17)
<asynchronous suspension>
#3 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:97:53)
<asynchronous suspension>
#4 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:86:14)
<asynchronous suspension>
#5 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#6 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#7 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#8 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#9 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#10 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#11 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#12 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#13 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#14 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#15 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#16 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#17 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#18 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#19 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#20 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#21 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#22 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#23 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#24 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#25 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#26 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#27 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#28 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#29 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#30 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#31 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#32 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#33 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#34 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#35 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#36 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#37 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#38 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#39 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#40 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#41 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#42 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#43 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#44 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#45 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#46 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#47 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#48 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#49 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#50 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#51 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#52 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#53 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#54 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#55 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#56 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#57 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#58 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#59 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#60 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#61 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#62 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#63 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#64 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#65 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#66 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#67 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:86:14)
<asynchronous suspension>
#68 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:86:14)
<asynchronous suspension>
#69 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#70 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#71 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:86:14)
<asynchronous suspension>
#72 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#73 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#74 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#75 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:88:14)
<asynchronous suspension>
#76 Workflow._handleWorkflowAction (package:gardening/src/workflow.dart:86:14)
<asynchronous suspension>
#77 Workflow._navigate (package:gardening/src/workflow.dart:79:11)
<asynchronous suspension>
#78 Workflow.start (package:gardening/src/workflow.dart:61:12)
#79 StatusCommand.run (file:///usr/local/google/home/whesse/ssd/sdk/tools/gardening/bin/results_status.dart:27:21)
<asynchronous suspension>
#80 CommandRunner.runCommand (package:args/command_runner.dart:194:27)
<asynchronous suspension>
#81 CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:109:29)
#82 new Future.sync (dart:async/future.dart:222)
#83 CommandRunner.run (package:args/command_runner.dart:109:11)
#84 main (file:///usr/local/google/home/whesse/ssd/sdk/tools/gardening/bin/results.dart:17:10)
#85 _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:263)
#86 _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:151)
@athomas | infrastructure | status update tool crashes on add more logs workflow after autofixing tests the status update tool was used for browser update status fixes where it autoupdated tests because they were similar then answering y to the question do you want to add more log files gave a crash and a stack trace that seems to have two frames for each test that was autofixed stack trace follows trying to find if any new errors have arised from the fixes no errors found do you want to add more logs y es or n o y unhandled exception nosuchmethoderror the getter isempty was called on null receiver null tried calling isempty object nosuchmethod dart core patch object patch dart object nosuchmethod dart core patch object patch dart fixfailingtest onshow package gardening src results workflow fix failing test dart workflow handleworkflowaction package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow handleworkflowaction package gardening src workflow dart workflow navigate package gardening src workflow dart workflow start package gardening src workflow dart statuscommand run file usr local google home whesse ssd sdk tools gardening bin results status dart commandrunner runcommand package args command runner dart commandrunner run package args command runner dart new future sync dart async future dart commandrunner run package args command runner dart main file usr local google home whesse ssd sdk tools gardening bin results dart startisolate dart isolate patch isolate patch dart rawreceiveportimpl handlemessage dart isolate patch isolate patch dart athomas | 1 |
31,805 | 15,092,298,588 | IssuesEvent | 2021-02-06 18:57:13 | ClickHouse/ClickHouse | https://api.github.com/repos/ClickHouse/ClickHouse | opened | DateTime64 or hourly partitions not being optimized well? | performance | **Describe the situation**
We have a MergeTree table which has ~300b rows in it over 1 year and looks like:
```
CREATE TABLE logs (
time DateTime64(3) CODEC(DoubleDelta, ZSTD(1)),
...
) ENGINE = MergeTree()
PARTITION BY toStartOfInterval(time, INTERVAL 1 HOUR)
PRIMARY KEY (cust id, some other cols, toDateTime(time))
```
When doing lookups like
```
select ...
where
cust id = xxx AND
toDateTime(time) > some_time
AND toDateTime(time) < some_time + interval 1 hour
order by time
limit 10
```
it works pretty quickly.
However if we remove the `AND toDateTime(time) < ` clause so the time period continues onwards I would have expected it to return the same 10 results in roughly the same time. However in this case it seems to scan the entire table and only then return the results. I'm not sure if this is something to do with the `DateTime64` type (as we usually have to put in the `toDateTime()` things to make it work in reasonable time) or to do with there being quite a lot of partitions in the table (this is a case where having an initial partition of hours, and then after a week or two merging those into days would be quite handy). | True | DateTime64 or hourly partitions not being optimized well? - **Describe the situation**
We have a MergeTree table which has ~300b rows in it over 1 year and looks like:
```
CREATE TABLE logs (
time DateTime64(3) CODEC(DoubleDelta, ZSTD(1)),
...
) ENGINE = MergeTree()
PARTITION BY toStartOfInterval(time, INTERVAL 1 HOUR)
PRIMARY KEY (cust id, some other cols, toDateTime(time))
```
When doing lookups like
```
select ...
where
cust id = xxx AND
toDateTime(time) > some_time
AND toDateTime(time) < some_time + interval 1 hour
order by time
limit 10
```
it works pretty quickly.
However if we remove the `AND toDateTime(time) < ` clause so the time period continues onwards I would have expected it to return the same 10 results in roughly the same time. However in this case it seems to scan the entire table and only then return the results. I'm not sure if this is something to do with the `DateTime64` type (as we usually have to put in the `toDateTime()` things to make it work in reasonable time) or to do with there being quite a lot of partitions in the table (this is a case where having an initial partition of hours, and then after a week or two merging those into days would be quite handy). | non_infrastructure | or hourly partitions not being optimized well describe the situation we have a mergetree table which has rows in it over year and looks like create table logs time codec doubledelta zstd engine mergetree partition by tostartofinterval time interval hour primary key cust id some other cols todatetime time when doing lookups like select where cust id xxx and todatetime time some time and todatetime time some time interval hour order by time limit it works pretty quickly however if we remove the and todatetime time clause so the time period continues onwards i would have expected it to return the same results in roughly the same time however in this case it seems to scan the entire table and only then return the results i m not sure if this is something to do with the type as we usually have to put in the todatetime things to make it work in reasonable time or to do with there being quite a lot of partitions in the table this is a case where having an initial partition of hours and then after a week or two merging those into days would be quite handy | 0 |
9,991 | 8,305,929,207 | IssuesEvent | 2018-09-22 13:14:00 | ArctosDB/arctos | https://api.github.com/repos/ArctosDB/arctos | opened | PBDB | Display/Interface infrastructure-limited | We should look more like these guys.
How do we get people to develop [resources](https://paleobiodb.org/#/resources) like they have? | 1.0 | PBDB - We should look more like these guys.
How do we get people to develop [resources](https://paleobiodb.org/#/resources) like they have? | infrastructure | pbdb we should look more like these guys how do we get people to develop like they have | 1 |
282,739 | 30,889,416,929 | IssuesEvent | 2023-08-04 02:41:32 | Trinadh465/linux-4.1.15_CVE-2017-1000371 | https://api.github.com/repos/Trinadh465/linux-4.1.15_CVE-2017-1000371 | reopened | CVE-2022-3564 (High) detected in linuxlinux-4.6 | Mend: dependency security vulnerability | ## CVE-2022-3564 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.6</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Trinadh465/linux-4.1.15_CVE-2017-1000371/commit/8cc0bec3d85a996d6015c27f949826b9ffc4d1ae">8cc0bec3d85a996d6015c27f949826b9ffc4d1ae</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/bluetooth/l2cap_core.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/bluetooth/l2cap_core.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
A vulnerability classified as critical was found in Linux Kernel. Affected by this vulnerability is the function l2cap_reassemble_sdu of the file net/bluetooth/l2cap_core.c of the component Bluetooth. The manipulation leads to use after free. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-211087.
<p>Publish Date: 2022-10-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3564>CVE-2022-3564</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Adjacent
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2022-3564">https://www.linuxkernelcves.com/cves/CVE-2022-3564</a></p>
<p>Release Date: 2022-10-17</p>
<p>Fix Resolution: v4.9.333,v4.14.299,v4.19.265,v5.4.224,v5.10.154,v5.15.78,v6.0.8,v6.1-rc4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-3564 (High) detected in linuxlinux-4.6 - ## CVE-2022-3564 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.6</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Trinadh465/linux-4.1.15_CVE-2017-1000371/commit/8cc0bec3d85a996d6015c27f949826b9ffc4d1ae">8cc0bec3d85a996d6015c27f949826b9ffc4d1ae</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/bluetooth/l2cap_core.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/bluetooth/l2cap_core.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
A vulnerability classified as critical was found in Linux Kernel. Affected by this vulnerability is the function l2cap_reassemble_sdu of the file net/bluetooth/l2cap_core.c of the component Bluetooth. The manipulation leads to use after free. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-211087.
<p>Publish Date: 2022-10-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3564>CVE-2022-3564</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Adjacent
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2022-3564">https://www.linuxkernelcves.com/cves/CVE-2022-3564</a></p>
<p>Release Date: 2022-10-17</p>
<p>Fix Resolution: v4.9.333,v4.14.299,v4.19.265,v5.4.224,v5.10.154,v5.15.78,v6.0.8,v6.1-rc4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_infrastructure | cve high detected in linuxlinux cve high severity vulnerability vulnerable library linuxlinux the linux kernel library home page a href found in head commit a href found in base branch master vulnerable source files net bluetooth core c net bluetooth core c vulnerability details a vulnerability classified as critical was found in linux kernel affected by this vulnerability is the function reassemble sdu of the file net bluetooth core c of the component bluetooth the manipulation leads to use after free it is recommended to apply a patch to fix this issue the associated identifier of this vulnerability is vdb publish date url a href cvss score details base score metrics exploitability metrics attack vector adjacent attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
22,584 | 15,286,704,234 | IssuesEvent | 2021-02-23 14:59:31 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | Some iOS tests are failing to launch test app | area-Infrastructure os-ios untriaged | I just saw a couple of failures on a PR on iOS, with:
```
[16:59:08] dbug: 16:59:08.5015570 Xamarin.Hosting: Simulator watchdogs are already disabled for 'iOS 13.5 (17F61) - iPhone X'.
[16:59:08] dbug: 16:59:08.5075460 Xamarin.Hosting: Device 'iOS 13.5 (17F61) - iPhone X' is already booted and the simulator is running.
[16:59:08] dbug: 16:59:08.5182020 Xamarin.Hosting: No need to boot (already booted): iPhone X (iOS 13.5) - created by XHarness
[16:59:08] dbug: 16:59:08.5218370 Xamarin.Hosting: Installing /tmp/helix/working/9F630914/w/A3C008F7/e/Microsoft.Extensions.Configuration.Functional.Tests.app with Bundle Identifier net.dot.Microsoft.Extensions.Configuration.Functional.Tests on 'iOS 13.5 (17F61) - iPhone X'...
[17:28:44] dbug: 17:28:44.9031320 Killing process 14971 as it was cancelled
[17:28:44] dbug: 17:28:44.9088890 Process exited with 137
[17:28:44] dbug: 17:28:44.9095210 Test run failed
[17:28:44] dbug: 17:28:44.9175530 Could not find pid in mtouch output.
[17:28:44] dbug: 17:28:44.9224100 Test run started
[17:28:46] dbug: 17:28:46.0798530 Test run failed to launch
[17:28:46] dbug: 17:28:46.0844090 No crash reports, waiting a second to see if the crash report service just didn't complete in time (4)
[17:28:47] dbug: 17:28:47.2295520 No crash reports, waiting a second to see if the crash report service just didn't complete in time (3)
[17:28:48] dbug: 17:28:48.3149390 No crash reports, waiting a second to see if the crash report service just didn't complete in time (2)
[17:28:49] dbug: 17:28:49.4627860 No crash reports, waiting a second to see if the crash report service just didn't complete in time (1)
[17:28:50] dbug: 17:28:50.5966390 No crash reports, waiting a second to see if the crash report service just didn't complete in time (0)
[17:28:51] fail: Failed to launch the application:
Launch failure
Check logs for more information.
XHarness exit code: 83
+ exit_code=83
```
https://github.com/dotnet/runtime/pull/45172
https://dev.azure.com/dnceng/public/_build/results?buildId=898906&view=results
https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-45172-merge-f3086f428107446aa7/Microsoft.Extensions.Configuration.Functional.Tests/console.c96502f5.log?sv=2019-07-07&se=2020-12-15T00%3A55%3A49Z&sr=c&sp=rl&sig=i1uWKdwS6iGhcUW0XoWG5uWfxxQF%2FwXqK6V6beKh6YM%3D
cc: @premun @dotnet/runtime-infrastructure | 1.0 | Some iOS tests are failing to launch test app - I just saw a couple of failures on a PR on iOS, with:
```
[16:59:08] dbug: 16:59:08.5015570 Xamarin.Hosting: Simulator watchdogs are already disabled for 'iOS 13.5 (17F61) - iPhone X'.
[16:59:08] dbug: 16:59:08.5075460 Xamarin.Hosting: Device 'iOS 13.5 (17F61) - iPhone X' is already booted and the simulator is running.
[16:59:08] dbug: 16:59:08.5182020 Xamarin.Hosting: No need to boot (already booted): iPhone X (iOS 13.5) - created by XHarness
[16:59:08] dbug: 16:59:08.5218370 Xamarin.Hosting: Installing /tmp/helix/working/9F630914/w/A3C008F7/e/Microsoft.Extensions.Configuration.Functional.Tests.app with Bundle Identifier net.dot.Microsoft.Extensions.Configuration.Functional.Tests on 'iOS 13.5 (17F61) - iPhone X'...
[17:28:44] dbug: 17:28:44.9031320 Killing process 14971 as it was cancelled
[17:28:44] dbug: 17:28:44.9088890 Process exited with 137
[17:28:44] dbug: 17:28:44.9095210 Test run failed
[17:28:44] dbug: 17:28:44.9175530 Could not find pid in mtouch output.
[17:28:44] dbug: 17:28:44.9224100 Test run started
[17:28:46] dbug: 17:28:46.0798530 Test run failed to launch
[17:28:46] dbug: 17:28:46.0844090 No crash reports, waiting a second to see if the crash report service just didn't complete in time (4)
[17:28:47] dbug: 17:28:47.2295520 No crash reports, waiting a second to see if the crash report service just didn't complete in time (3)
[17:28:48] dbug: 17:28:48.3149390 No crash reports, waiting a second to see if the crash report service just didn't complete in time (2)
[17:28:49] dbug: 17:28:49.4627860 No crash reports, waiting a second to see if the crash report service just didn't complete in time (1)
[17:28:50] dbug: 17:28:50.5966390 No crash reports, waiting a second to see if the crash report service just didn't complete in time (0)
[17:28:51] fail: Failed to launch the application:
Launch failure
Check logs for more information.
XHarness exit code: 83
+ exit_code=83
```
https://github.com/dotnet/runtime/pull/45172
https://dev.azure.com/dnceng/public/_build/results?buildId=898906&view=results
https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-45172-merge-f3086f428107446aa7/Microsoft.Extensions.Configuration.Functional.Tests/console.c96502f5.log?sv=2019-07-07&se=2020-12-15T00%3A55%3A49Z&sr=c&sp=rl&sig=i1uWKdwS6iGhcUW0XoWG5uWfxxQF%2FwXqK6V6beKh6YM%3D
cc: @premun @dotnet/runtime-infrastructure | infrastructure | some ios tests are failing to launch test app i just saw a couple of failures on a pr on ios with dbug xamarin hosting simulator watchdogs are already disabled for ios iphone x dbug xamarin hosting device ios iphone x is already booted and the simulator is running dbug xamarin hosting no need to boot already booted iphone x ios created by xharness dbug xamarin hosting installing tmp helix working w e microsoft extensions configuration functional tests app with bundle identifier net dot microsoft extensions configuration functional tests on ios iphone x dbug killing process as it was cancelled dbug process exited with dbug test run failed dbug could not find pid in mtouch output dbug test run started dbug test run failed to launch dbug no crash reports waiting a second to see if the crash report service just didn t complete in time dbug no crash reports waiting a second to see if the crash report service just didn t complete in time dbug no crash reports waiting a second to see if the crash report service just didn t complete in time dbug no crash reports waiting a second to see if the crash report service just didn t complete in time dbug no crash reports waiting a second to see if the crash report service just didn t complete in time fail failed to launch the application launch failure check logs for more information xharness exit code exit code cc premun dotnet runtime infrastructure | 1 |
299,944 | 22,633,925,208 | IssuesEvent | 2022-06-30 16:58:26 | ahroncich7/Trabajo-Grupal-ISPC_2 | https://api.github.com/repos/ahroncich7/Trabajo-Grupal-ISPC_2 | closed | Agregar C.V. Ezequiel Heredia | documentation | -Clonar el repositorio accediendo desde la rama principal en GitHub en la opción Code ->(HTTPS) en sus PC’s.
-Ya en sus discos locales, cada uno de los integrantes, crea su rama personal desde la consola de Git.
-Swichearse (moverse) a su rama personal.
-En la rama personal agregar su Curriculum Vitae (un archivo en formato .pdf) usando los comandos que hemos aprendido.
-Subir la rama personal al repositorio remoto. | 1.0 | Agregar C.V. Ezequiel Heredia - -Clonar el repositorio accediendo desde la rama principal en GitHub en la opción Code ->(HTTPS) en sus PC’s.
-Ya en sus discos locales, cada uno de los integrantes, crea su rama personal desde la consola de Git.
-Swichearse (moverse) a su rama personal.
-En la rama personal agregar su Curriculum Vitae (un archivo en formato .pdf) usando los comandos que hemos aprendido.
-Subir la rama personal al repositorio remoto. | non_infrastructure | agregar c v ezequiel heredia clonar el repositorio accediendo desde la rama principal en github en la opción code https en sus pc’s ya en sus discos locales cada uno de los integrantes crea su rama personal desde la consola de git swichearse moverse a su rama personal en la rama personal agregar su curriculum vitae un archivo en formato pdf usando los comandos que hemos aprendido subir la rama personal al repositorio remoto | 0 |
913 | 3,000,192,421 | IssuesEvent | 2015-07-23 23:19:24 | t3kt/vjzual | https://api.github.com/repos/t3kt/vjzual | closed | dependency loop in the master color adjustment module | bug infrastructure video processing | It shows up when the cross TOP that blends the output is active. Bypassing it seems to circumvent the problem. | 1.0 | dependency loop in the master color adjustment module - It shows up when the cross TOP that blends the output is active. Bypassing it seems to circumvent the problem. | infrastructure | dependency loop in the master color adjustment module it shows up when the cross top that blends the output is active bypassing it seems to circumvent the problem | 1 |
628,231 | 19,978,384,299 | IssuesEvent | 2022-01-29 13:35:14 | TeamChocoQuest/ChocolateQuestRepoured | https://api.github.com/repos/TeamChocoQuest/ChocolateQuestRepoured | closed | Grappling Hook Crashes Other Players | Type: Bug Status: Reproduced Priority: Low Status: Working on it | **General Information**
To check a checkbox: Insert a X between the square brackets, you need to remove the space though.
- I play...
- [X] With a large modpack
- [ ] Only with CQR and it's dependencies
- The issue occurs in...
- [ ] Singleplayer
- [X] Multiplayer
- [X] I have searched for this or a similar issue before reporting and it was either (1) not previously reported, or (2) previously fixed and I'm having the same problem.
- [X] I am using the latest version of the mod (all versions can be found on github under releases)
- [X] I read through the FAQ and I could not find something helpful ([FAQ](https://wiki.cq-repoured.net/index.php?title=FAQ))
- [ ] I reproduced the bug without any other mod's except forge, cqr and it's dependencies
- [X] The game crashes because of this bug
**Describe the bug**
Using a grappling hook near other players can sometimes cause their clients to crash.
The crash seems to only happen when players are at a far-away distance.
**Screenshots**
Here's a video: https://youtu.be/5NLkof1Uacc
**Versions (Note that 'latest' is NOT a valid version!**
Chocolate Quest Repoured: In the crash report.
Forge: In the crash report.
Minecraft: In the crash report.
Other mods (necessary to reproduce the bug): In the crash report.
**Crash Report**
https://pastebin.com/raw/sndhhX7W | 1.0 | Grappling Hook Crashes Other Players - **General Information**
To check a checkbox: Insert a X between the square brackets, you need to remove the space though.
- I play...
- [X] With a large modpack
- [ ] Only with CQR and it's dependencies
- The issue occurs in...
- [ ] Singleplayer
- [X] Multiplayer
- [X] I have searched for this or a similar issue before reporting and it was either (1) not previously reported, or (2) previously fixed and I'm having the same problem.
- [X] I am using the latest version of the mod (all versions can be found on github under releases)
- [X] I read through the FAQ and I could not find something helpful ([FAQ](https://wiki.cq-repoured.net/index.php?title=FAQ))
- [ ] I reproduced the bug without any other mod's except forge, cqr and it's dependencies
- [X] The game crashes because of this bug
**Describe the bug**
Using a grappling hook near other players can sometimes cause their clients to crash.
The crash seems to only happen when players are at a far-away distance.
**Screenshots**
Here's a video: https://youtu.be/5NLkof1Uacc
**Versions (Note that 'latest' is NOT a valid version!**
Chocolate Quest Repoured: In the crash report.
Forge: In the crash report.
Minecraft: In the crash report.
Other mods (necessary to reproduce the bug): In the crash report.
**Crash Report**
https://pastebin.com/raw/sndhhX7W | non_infrastructure | grappling hook crashes other players general information to check a checkbox insert a x between the square brackets you need to remove the space though i play with a large modpack only with cqr and it s dependencies the issue occurs in singleplayer multiplayer i have searched for this or a similar issue before reporting and it was either not previously reported or previously fixed and i m having the same problem i am using the latest version of the mod all versions can be found on github under releases i read through the faq and i could not find something helpful i reproduced the bug without any other mod s except forge cqr and it s dependencies the game crashes because of this bug describe the bug using a grappling hook near other players can sometimes cause their clients to crash the crash seems to only happen when players are at a far away distance screenshots here s a video versions note that latest is not a valid version chocolate quest repoured in the crash report forge in the crash report minecraft in the crash report other mods necessary to reproduce the bug in the crash report crash report | 0 |
35,151 | 30,793,827,455 | IssuesEvent | 2023-07-31 18:13:29 | microsoft/microsoft-ui-xaml | https://api.github.com/repos/microsoft/microsoft-ui-xaml | closed | Unit Test run crashes when calling Microsoft.UI.Xaml.Application.Start | area-TestInfrastructure team-Markup product-winui3 no-issue-activity | **Describe the bug**
I've been trying to launch a WinUI dialog from my test project for UI testing, but the app crashes (with not catchable callstack or breakpoint), when calling ` global::Microsoft.UI.Xaml.Application.Start(...)`;
**Steps to reproduce the bug**
1. Open the attached project:
[UnitTestApp.zip](https://github.com/microsoft/microsoft-ui-xaml/files/5655691/UnitTestApp.zip)
2. Verify that the application will launch with normal F5 debugging and an empty window will show.
3. In `TestInitializer.cs` line 21 where the Start call is, place a breakpoint.
4. From TestExplorer, start debugging the tests.
5. Step through the code and verify that the exact same code that worked fine when launching the app, fails when launched from test explorer.
**Expected behavior**
Window opens successfully.
**Version Info**
<!-- Please enter your WinUI NuGet package version, Windows app type (when using WinUI 3+), OS version(s), and form factor(s) -->
NuGet package version:
[Microsoft.WinUI 3.0.0-preview3.201113.0]
<!-- If you are using WinUI 3, please specify for which Windows app type you have encountered the issue. Leave blank if you didn't try that app type. -->
Windows app type:
| UWP | Win32 |
| :--------------- | :--------------- |
| <!-- Yes/No? --> | Yes |
<!-- Which Windows versions did you see the issue on? Leave blank if you didn't try that version. -->
| Windows 10 version | Saw the problem? |
| :--------------------------------- | :-------------------- |
| Insider Build (xxxxx) | <!-- Yes/No? --> |
| May 2020 Update (19041) | <!-- Yes/No? --> |
| November 2019 Update (18363) | <!-- Yes/No? --> |
| May 2019 Update (18362) | <!-- Yes/No? --> |
| October 2018 Update (17763) | <!-- Yes/No? --> |
| April 2018 Update (17134) | <!-- Yes/No? --> |
| Fall Creators Update (16299) | <!-- Yes/No? --> |
| Creators Update (15063) | <!-- Yes/No? --> |
<!-- Which device form factors did you see the issue on? Leave blank if you didn't try that device. -->
| Device form factor | Saw the problem? |
| :----------------- | :--------------- |
| Desktop | Yes |
| Xbox | <!-- Yes/No? --> |
| Surface Hub | <!-- Yes/No? --> |
| IoT | <!-- Yes/No? --> |
**Additional context**
<!-- Enter any other applicable info here -->
| 1.0 | Unit Test run crashes when calling Microsoft.UI.Xaml.Application.Start - **Describe the bug**
I've been trying to launch a WinUI dialog from my test project for UI testing, but the app crashes (with not catchable callstack or breakpoint), when calling ` global::Microsoft.UI.Xaml.Application.Start(...)`;
**Steps to reproduce the bug**
1. Open the attached project:
[UnitTestApp.zip](https://github.com/microsoft/microsoft-ui-xaml/files/5655691/UnitTestApp.zip)
2. Verify that the application will launch with normal F5 debugging and an empty window will show.
3. In `TestInitializer.cs` line 21 where the Start call is, place a breakpoint.
4. From TestExplorer, start debugging the tests.
5. Step through the code and verify that the exact same code that worked fine when launching the app, fails when launched from test explorer.
**Expected behavior**
Window opens successfully.
**Version Info**
<!-- Please enter your WinUI NuGet package version, Windows app type (when using WinUI 3+), OS version(s), and form factor(s) -->
NuGet package version:
[Microsoft.WinUI 3.0.0-preview3.201113.0]
<!-- If you are using WinUI 3, please specify for which Windows app type you have encountered the issue. Leave blank if you didn't try that app type. -->
Windows app type:
| UWP | Win32 |
| :--------------- | :--------------- |
| <!-- Yes/No? --> | Yes |
<!-- Which Windows versions did you see the issue on? Leave blank if you didn't try that version. -->
| Windows 10 version | Saw the problem? |
| :--------------------------------- | :-------------------- |
| Insider Build (xxxxx) | <!-- Yes/No? --> |
| May 2020 Update (19041) | <!-- Yes/No? --> |
| November 2019 Update (18363) | <!-- Yes/No? --> |
| May 2019 Update (18362) | <!-- Yes/No? --> |
| October 2018 Update (17763) | <!-- Yes/No? --> |
| April 2018 Update (17134) | <!-- Yes/No? --> |
| Fall Creators Update (16299) | <!-- Yes/No? --> |
| Creators Update (15063) | <!-- Yes/No? --> |
<!-- Which device form factors did you see the issue on? Leave blank if you didn't try that device. -->
| Device form factor | Saw the problem? |
| :----------------- | :--------------- |
| Desktop | Yes |
| Xbox | <!-- Yes/No? --> |
| Surface Hub | <!-- Yes/No? --> |
| IoT | <!-- Yes/No? --> |
**Additional context**
<!-- Enter any other applicable info here -->
| infrastructure | unit test run crashes when calling microsoft ui xaml application start describe the bug i ve been trying to launch a winui dialog from my test project for ui testing but the app crashes with not catchable callstack or breakpoint when calling global microsoft ui xaml application start steps to reproduce the bug open the attached project verify that the application will launch with normal debugging and an empty window will show in testinitializer cs line where the start call is place a breakpoint from testexplorer start debugging the tests step through the code and verify that the exact same code that worked fine when launching the app fails when launched from test explorer expected behavior window opens successfully version info nuget package version windows app type uwp yes windows version saw the problem insider build xxxxx may update november update may update october update april update fall creators update creators update device form factor saw the problem desktop yes xbox surface hub iot additional context | 1 |
820,425 | 30,771,851,256 | IssuesEvent | 2023-07-31 00:51:26 | isXander/Controlify | https://api.github.com/repos/isXander/Controlify | closed | Server integration | feature low-priority | A server could ban the use of future features of the mod that may be seen as cheating, such as reach-around placement, if it gets added in the future.
Additionally, servers could also register custom keybinds to the client so it can receive custom input in its own way that will trigger a server action. | 1.0 | Server integration - A server could ban the use of future features of the mod that may be seen as cheating, such as reach-around placement, if it gets added in the future.
Additionally, servers could also register custom keybinds to the client so it can receive custom input in its own way that will trigger a server action. | non_infrastructure | server integration a server could ban the use of future features of the mod that may be seen as cheating such as reach around placement if it gets added in the future additionally servers could also register custom keybinds to the client so it can receive custom input in its own way that will trigger a server action | 0 |
21,226 | 14,444,245,444 | IssuesEvent | 2020-12-07 20:56:05 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | opened | Improve documentation on retrieving and using dumps | area-Infrastructure-coreclr | *Initial cost estimate*: 1 week
*Initial contacts*: @tommcdon, @trylek, @janvorli
The purpose of this work item is to improve the workflow / diagnostic md files in the runtime repo by including and / or raising the visibility of information on how to retrieve and use Helix dumps. Multiple developers including myself have been frustrated with non-trivial chores regarding dump retrieval and opening including the following aspects:
[ ] Per-OS debugger launch instructions
[ ] Symbol server configuration
As part of this work item we should also review the process and consider filing follow-up issues to automate parts of this using generated scripts, AzDO links or other means. | 1.0 | Improve documentation on retrieving and using dumps - *Initial cost estimate*: 1 week
*Initial contacts*: @tommcdon, @trylek, @janvorli
The purpose of this work item is to improve the workflow / diagnostic md files in the runtime repo by including and / or raising the visibility of information on how to retrieve and use Helix dumps. Multiple developers including myself have been frustrated with non-trivial chores regarding dump retrieval and opening including the following aspects:
[ ] Per-OS debugger launch instructions
[ ] Symbol server configuration
As part of this work item we should also review the process and consider filing follow-up issues to automate parts of this using generated scripts, AzDO links or other means. | infrastructure | improve documentation on retrieving and using dumps initial cost estimate week initial contacts tommcdon trylek janvorli the purpose of this work item is to improve the workflow diagnostic md files in the runtime repo by including and or raising the visibility of information on how to retrieve and use helix dumps multiple developers including myself have been frustrated with non trivial chores regarding dump retrieval and opening including the following aspects per os debugger launch instructions symbol server configuration as part of this work item we should also review the process and consider filing follow up issues to automate parts of this using generated scripts azdo links or other means | 1 |
201,332 | 7,029,542,565 | IssuesEvent | 2017-12-26 02:06:40 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | ups.surveyrouter.com - desktop site instead of mobile site | browser-firefox-mobile priority-normal | <!-- @browser: Firefox Mobile 59.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 4.4.4; Mobile; rv:59.0) Gecko/59.0 Firefox/59.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: http://ups.surveyrouter.com/surveytrafficui/stmui/end.aspx?flag=2
**Browser / Version**: Firefox Mobile 59.0
**Operating System**: Android 4.4.4
**Tested Another Browser**: Yes
**Problem type**: Desktop site instead of mobile site
**Description**: página em branco
**Steps to Reproduce**:
A página abre, mas não aparece nenhum conteúdo
[](https://webcompat.com/uploads/2017/12/ea1ab309-8d8c-424d-812d-b5f9c119f2df.jpg)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | ups.surveyrouter.com - desktop site instead of mobile site - <!-- @browser: Firefox Mobile 59.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 4.4.4; Mobile; rv:59.0) Gecko/59.0 Firefox/59.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: http://ups.surveyrouter.com/surveytrafficui/stmui/end.aspx?flag=2
**Browser / Version**: Firefox Mobile 59.0
**Operating System**: Android 4.4.4
**Tested Another Browser**: Yes
**Problem type**: Desktop site instead of mobile site
**Description**: página em branco
**Steps to Reproduce**:
A página abre, mas não aparece nenhum conteúdo
[](https://webcompat.com/uploads/2017/12/ea1ab309-8d8c-424d-812d-b5f9c119f2df.jpg)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_infrastructure | ups surveyrouter com desktop site instead of mobile site url browser version firefox mobile operating system android tested another browser yes problem type desktop site instead of mobile site description página em branco steps to reproduce a página abre mas não aparece nenhum conteúdo from with ❤️ | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.