Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3 values | title stringlengths 1 844 | labels stringlengths 4 721 | body stringlengths 1 261k | index stringclasses 12 values | text_combine stringlengths 96 261k | label stringclasses 2 values | text stringlengths 96 248k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
81,084 | 30,703,447,125 | IssuesEvent | 2023-07-27 02:53:02 | vector-im/element-desktop | https://api.github.com/repos/vector-im/element-desktop | opened | Notifications are not shown in desktop notification list despite popping up as a desktop notification | T-Defect | ### Steps to reproduce
1. Receive a notification
2. observe that notification is shown
3. observe that notification is not put into desktop notification list/history
### Outcome
#### What did you expect?
I expect notifications to be put into notification history. Discord does the same, for example.
#### What happened instead?
The notifications are shown, but they are not put into the history.
This may be a bug specific to KDE, I am not sure.
### Operating system
Arch Linux, Kernel v6.4.6-arch-1, KDE Plasma v5.27.6
### Application version
Element v1.11.36, Olm v3.2.14
### How did you install the app?
Arch Linux Repos
### Homeserver
matrix.org
### Will you send logs?
No | 1.0 | Notifications are not shown in desktop notification list despite popping up as a desktop notification - ### Steps to reproduce
1. Receive a notification
2. observe that notification is shown
3. observe that notification is not put into desktop notification list/history
### Outcome
#### What did you expect?
I expect notifications to be put into notification history. Discord does the same, for example.
#### What happened instead?
The notifications are shown, but they are not put into the history.
This may be a bug specific to KDE, I am not sure.
### Operating system
Arch Linux, Kernel v6.4.6-arch-1, KDE Plasma v5.27.6
### Application version
Element v1.11.36, Olm v3.2.14
### How did you install the app?
Arch Linux Repos
### Homeserver
matrix.org
### Will you send logs?
No | non_priority | notifications are not shown in desktop notification list despite popping up as a desktop notification steps to reproduce receive a notification observe that notification is shown observe that notification is not put into desktop notification list history outcome what did you expect i expect notifications to be put into notification history discord does the same for example what happened instead the notifications are shown but they are not put into the history this may be a bug specific to kde i am not sure operating system arch linux kernel arch kde plasma application version element olm how did you install the app arch linux repos homeserver matrix org will you send logs no | 0 |
20,316 | 6,024,288,027 | IssuesEvent | 2017-06-08 04:18:39 | darknite12/rms | https://api.github.com/repos/darknite12/rms | opened | Create first GUI for Person | code todo ui | This UI may consist of multiple pages to view/create/modify/remove a Person from the database | 1.0 | Create first GUI for Person - This UI may consist of multiple pages to view/create/modify/remove a Person from the database | non_priority | create first gui for person this ui may consist of multiple pages to view create modify remove a person from the database | 0 |
314,001 | 23,501,552,660 | IssuesEvent | 2022-08-18 08:52:20 | ali2210/WizDwarf | https://api.github.com/repos/ali2210/WizDwarf | closed | Registries Keygen encryption | documentation enhancement | **Is your feature request related to a problem? Please describe.**
Yes, Many application have third parties registries keygen which is used for different purpose. Like Database connection, third parties application etc. Programmer will use different method to protect application credentials . One way function, key rotation, padding key, Salt key etc are common answers to such problems
**Describe the solution you'd like**
1. Salt Method to improved
2. Pepper Method
3. Salt and Pepper Method
4. Content on private network
**Describe alternatives you've considered**
Encryption Keys
Private Network
**Additional context**
Add any other context or screenshots about the feature request here.
| 1.0 | Registries Keygen encryption - **Is your feature request related to a problem? Please describe.**
Yes, Many application have third parties registries keygen which is used for different purpose. Like Database connection, third parties application etc. Programmer will use different method to protect application credentials . One way function, key rotation, padding key, Salt key etc are common answers to such problems
**Describe the solution you'd like**
1. Salt Method to improved
2. Pepper Method
3. Salt and Pepper Method
4. Content on private network
**Describe alternatives you've considered**
Encryption Keys
Private Network
**Additional context**
Add any other context or screenshots about the feature request here.
| non_priority | registries keygen encryption is your feature request related to a problem please describe yes many application have third parties registries keygen which is used for different purpose like database connection third parties application etc programmer will use different method to protect application credentials one way function key rotation padding key salt key etc are common answers to such problems describe the solution you d like salt method to improved pepper method salt and pepper method content on private network describe alternatives you ve considered encryption keys private network additional context add any other context or screenshots about the feature request here | 0 |
279,746 | 21,182,444,571 | IssuesEvent | 2022-04-08 09:17:08 | Avaiga/taipy-doc | https://api.github.com/repos/Avaiga/taipy-doc | closed | Ubuntu deployment | devops documentation | * Taipy version: 1.0.0
* Python version: Python3.8+
* Operating System: Ubuntu
### Description
Add documentation on how to deploy on Ubuntu.
| 1.0 | Ubuntu deployment - * Taipy version: 1.0.0
* Python version: Python3.8+
* Operating System: Ubuntu
### Description
Add documentation on how to deploy on Ubuntu.
| non_priority | ubuntu deployment taipy version python version operating system ubuntu description add documentation on how to deploy on ubuntu | 0 |
264,959 | 23,145,082,232 | IssuesEvent | 2022-07-28 23:14:22 | MPMG-DCC-UFMG/F01 | https://api.github.com/repos/MPMG-DCC-UFMG/F01 | closed | Teste de generalizacao para a tag Seridores - Registro por lotação - Coluna | generalization test development template-Síntese tecnologia informatica tag-Servidores subtag-Registro por lotação | DoD: Realizar o teste de Generalização do validador da tag Seridores - Registro por lotação para o Município de Coluna. | 1.0 | Teste de generalizacao para a tag Seridores - Registro por lotação - Coluna - DoD: Realizar o teste de Generalização do validador da tag Seridores - Registro por lotação para o Município de Coluna. | non_priority | teste de generalizacao para a tag seridores registro por lotação coluna dod realizar o teste de generalização do validador da tag seridores registro por lotação para o município de coluna | 0 |
241,433 | 18,454,655,556 | IssuesEvent | 2021-10-15 14:58:14 | CMPUT301F21T13/FungalFunhouse | https://api.github.com/repos/CMPUT301F21T13/FungalFunhouse | closed | Draft UI-prototype and mockup storyboard sequences for general UI flow | documentation | Diagram the layout of your main user interface and major dialogs, with comments describing the important elements. Also, diagram storyboard sequences of using your application, with transitions between different states of the user interface, caused by the user manipulating the controls or providing input. Within the diagrams, reference the relevant requirements. | 1.0 | Draft UI-prototype and mockup storyboard sequences for general UI flow - Diagram the layout of your main user interface and major dialogs, with comments describing the important elements. Also, diagram storyboard sequences of using your application, with transitions between different states of the user interface, caused by the user manipulating the controls or providing input. Within the diagrams, reference the relevant requirements. | non_priority | draft ui prototype and mockup storyboard sequences for general ui flow diagram the layout of your main user interface and major dialogs with comments describing the important elements also diagram storyboard sequences of using your application with transitions between different states of the user interface caused by the user manipulating the controls or providing input within the diagrams reference the relevant requirements | 0 |
276,780 | 21,000,096,970 | IssuesEvent | 2022-03-29 16:36:07 | jrenjq/PainAssessment | https://api.github.com/repos/jrenjq/PainAssessment | closed | D2: Updated User Requirements | documentation | - [x] update calculate weightage to save checklist
- [x] add details on save checklist user feature | 1.0 | D2: Updated User Requirements - - [x] update calculate weightage to save checklist
- [x] add details on save checklist user feature | non_priority | updated user requirements update calculate weightage to save checklist add details on save checklist user feature | 0 |
64,451 | 26,744,198,353 | IssuesEvent | 2023-01-30 14:58:28 | cityofaustin/atd-data-tech | https://api.github.com/repos/cityofaustin/atd-data-tech | closed | Bus Stop Scoring Tool | Workgroup: TED Type: New Application Impact: 2-Major Service: Dev Service: Product Need: 2-Should Have | <!-- Email -->
<!-- caitlin.d'alton@austintexas.gov -->
> Name
2022 Bus Stop Analysis and Map
> What application are you using?
Other / Not Sure
> Describe the problem.
ATD has an existing tool (https://capmetro.atxvisionzero.xyz/) that we (ATD and CapMetro) use to identify bus stops that should be evaluated for improvement, relocation or closure in order to improve bus operations and safety (what we call “bus stop optimization”). Bus stops are assigned a score based on a variety of metrics (ridership, distance from a safe crossing, etc.), and that score is used to help us prioritize stops to focus limited resources on for improvement. The tool has not been updated over the last 1+ year to include recent data, and it does not include equity as a metric for scoring bus stops. Not having an up-to-date tool that includes equity as a metric makes it a challenge to identify stops for further project development.
> Describe the solution you have in mind.
Updating the existing "CapMetro Stop Scores" tool (https://capmetro.atxvisionzero.xyz/) with recent data, and adding equity as a measure in that tool.
> How will we know that our solution is successful?
We have an updated tool that can be used to identify bus stops for improvement, relocation or closure, and we are able to integrate that updated tool into our 2020 bond planning work that's currently being supported by a consultant team.
> Users
ATD and Capital Metro staff
> Sponsorship
Transit Enhancement Program - Eric Bollich, Anna Martin
> Which Strategic Direction 2023 “Mobility” indicators would this new application impact?
['System efficiency and congestion', 'Accessibility to and equity of multi-modal transportation choices', 'Safety']
> Which Austin Strategic Mobility Plan goals would this new application support?
['Commuter Delay – Reduce the amount of time workers spend traveling between home and work.', 'Travel Choice — Promote a balanced transportation network and the ability to make informed choices based on personal needs and preferences.', 'Health & Safety — Protect Austinites by lowering the risk of travel-related injury and promoting public health.', 'Affordability — Lower the cost of traveling in Austin by providing affordable travel options.', 'Sustainability — Promote integrated designs and quality additions to the built environment while reducing impacts and promoting efficient use of public resources.', 'Placemaking — Build a transportation network that encourages social interaction through quality urban design, and connects users to the many places that make Austin unique.', 'Economic Prosperity — Promote economic growth for individuals and the city through strategic investments in transportation networks that meet the needs of the 21st century.', 'Innovation — Draw inspiration from forward-looking cities around the world, change the way we think about what’s possible, and set an example for the rest of the country.']
> Describe any workarounds you currently have in place or alternative solutions you've considered.
If this tool cannot be updated in the short term (by September 16), I will work with a consultant team to determine how they can make an update by that September deadline.
> Is there anything else we should know?
I’d ideally like it to be completed by September 16th (4 weeks). If that’s not possible, it would be helpful to know what is possible within that timeframe. Besides just needing to use this tool to inform ongoing bus stop optimization work, we’d like to pull the data from the tool into a separate bus delay analysis tool (BDAT) that is in development for ATD by a consultant team. This BDAT tool is being used to help us identify and prioritize larger corridors for bond-funded transit improvement projects. The next step in that corridor identification and prioritization process starts 9/19, and if we can’t get the bus stop tool back up and running by then, or can get it up and running but can’t complete the requested updates, I’ll need to come up with a plan B for including that bus stop information into the BDAT.
> How have other divisions/departments/cities addressed similar challenges?
I am not sure.
> Requested By
Caitlin D.
Request ID: DTS22-105005
| 2.0 | Bus Stop Scoring Tool - <!-- Email -->
<!-- caitlin.d'alton@austintexas.gov -->
> Name
2022 Bus Stop Analysis and Map
> What application are you using?
Other / Not Sure
> Describe the problem.
ATD has an existing tool (https://capmetro.atxvisionzero.xyz/) that we (ATD and CapMetro) use to identify bus stops that should be evaluated for improvement, relocation or closure in order to improve bus operations and safety (what we call “bus stop optimization”). Bus stops are assigned a score based on a variety of metrics (ridership, distance from a safe crossing, etc.), and that score is used to help us prioritize stops to focus limited resources on for improvement. The tool has not been updated over the last 1+ year to include recent data, and it does not include equity as a metric for scoring bus stops. Not having an up-to-date tool that includes equity as a metric makes it a challenge to identify stops for further project development.
> Describe the solution you have in mind.
Updating the existing "CapMetro Stop Scores" tool (https://capmetro.atxvisionzero.xyz/) with recent data, and adding equity as a measure in that tool.
> How will we know that our solution is successful?
We have an updated tool that can be used to identify bus stops for improvement, relocation or closure, and we are able to integrate that updated tool into our 2020 bond planning work that's currently being supported by a consultant team.
> Users
ATD and Capital Metro staff
> Sponsorship
Transit Enhancement Program - Eric Bollich, Anna Martin
> Which Strategic Direction 2023 “Mobility” indicators would this new application impact?
['System efficiency and congestion', 'Accessibility to and equity of multi-modal transportation choices', 'Safety']
> Which Austin Strategic Mobility Plan goals would this new application support?
['Commuter Delay – Reduce the amount of time workers spend traveling between home and work.', 'Travel Choice — Promote a balanced transportation network and the ability to make informed choices based on personal needs and preferences.', 'Health & Safety — Protect Austinites by lowering the risk of travel-related injury and promoting public health.', 'Affordability — Lower the cost of traveling in Austin by providing affordable travel options.', 'Sustainability — Promote integrated designs and quality additions to the built environment while reducing impacts and promoting efficient use of public resources.', 'Placemaking — Build a transportation network that encourages social interaction through quality urban design, and connects users to the many places that make Austin unique.', 'Economic Prosperity — Promote economic growth for individuals and the city through strategic investments in transportation networks that meet the needs of the 21st century.', 'Innovation — Draw inspiration from forward-looking cities around the world, change the way we think about what’s possible, and set an example for the rest of the country.']
> Describe any workarounds you currently have in place or alternative solutions you've considered.
If this tool cannot be updated in the short term (by September 16), I will work with a consultant team to determine how they can make an update by that September deadline.
> Is there anything else we should know?
I’d ideally like it to be completed by September 16th (4 weeks). If that’s not possible, it would be helpful to know what is possible within that timeframe. Besides just needing to use this tool to inform ongoing bus stop optimization work, we’d like to pull the data from the tool into a separate bus delay analysis tool (BDAT) that is in development for ATD by a consultant team. This BDAT tool is being used to help us identify and prioritize larger corridors for bond-funded transit improvement projects. The next step in that corridor identification and prioritization process starts 9/19, and if we can’t get the bus stop tool back up and running by then, or can get it up and running but can’t complete the requested updates, I’ll need to come up with a plan B for including that bus stop information into the BDAT.
> How have other divisions/departments/cities addressed similar challenges?
I am not sure.
> Requested By
Caitlin D.
Request ID: DTS22-105005
| non_priority | bus stop scoring tool name bus stop analysis and map what application are you using other not sure describe the problem atd has an existing tool that we atd and capmetro use to identify bus stops that should be evaluated for improvement relocation or closure in order to improve bus operations and safety what we call “bus stop optimization” bus stops are assigned a score based on a variety of metrics ridership distance from a safe crossing etc and that score is used to help us prioritize stops to focus limited resources on for improvement the tool has not been updated over the last year to include recent data and it does not include equity as a metric for scoring bus stops not having an up to date tool that includes equity as a metric makes it a challenge to identify stops for further project development describe the solution you have in mind updating the existing capmetro stop scores tool with recent data and adding equity as a measure in that tool how will we know that our solution is successful we have an updated tool that can be used to identify bus stops for improvement relocation or closure and we are able to integrate that updated tool into our bond planning work that s currently being supported by a consultant team users atd and capital metro staff sponsorship transit enhancement program eric bollich anna martin which strategic direction “mobility” indicators would this new application impact which austin strategic mobility plan goals would this new application support describe any workarounds you currently have in place or alternative solutions you ve considered if this tool cannot be updated in the short term by september i will work with a consultant team to determine how they can make an update by that september deadline is there anything else we should know i’d ideally like it to be completed by september weeks if that’s not possible it would be helpful to know what is possible within that timeframe besides just needing to use this tool to inform ongoing bus stop optimization work we’d like to pull the data from the tool into a separate bus delay analysis tool bdat that is in development for atd by a consultant team this bdat tool is being used to help us identify and prioritize larger corridors for bond funded transit improvement projects the next step in that corridor identification and prioritization process starts and if we can’t get the bus stop tool back up and running by then or can get it up and running but can’t complete the requested updates i’ll need to come up with a plan b for including that bus stop information into the bdat how have other divisions departments cities addressed similar challenges i am not sure requested by caitlin d request id | 0 |
158,828 | 12,426,283,731 | IssuesEvent | 2020-05-24 20:23:40 | phetsims/circuit-construction-kit-common | https://api.github.com/repos/phetsims/circuit-construction-kit-common | closed | CT Cannot read property disposeCircuitElement of null | type:automated-testing | Occurs in multiple CCK sims
```
circuit-construction-kit-dc-virtual-lab : interactive-description-fuzzBoard : built : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000
Query: fuzzBoard&supportsDescriptions&memoryLimit=1000
Uncaught TypeError: Cannot read property 'disposeCircuitElement' of null
TypeError: Cannot read property 'disposeCircuitElement' of null
at Object.keydown (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:1188338)
at t.value (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:653256)
at t.value (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:653455)
at t.value (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:652997)
at t.value (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:648420)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:644805
at e.value (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:598885)
at HTMLDivElement.<anonymous> (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:645487)
at t.value (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:1632527)
at t.value (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:1631437)
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
circuit-construction-kit-dc-virtual-lab : interactive-description-fuzzBoard : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/circuit-construction-kit-dc-virtual-lab_en.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&brand=phet&ea&fuzzBoard&supportsDescriptions&memoryLimit=1000
Query: brand=phet&ea&fuzzBoard&supportsDescriptions&memoryLimit=1000
Uncaught TypeError: Cannot read property 'disposeCircuitElement' of null
TypeError: Cannot read property 'disposeCircuitElement' of null
at Object.keydown (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-common/js/view/CircuitElementNode.js:64:21)
at Input.dispatchToListeners (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/scenery/js/input/Input.js:1818:25)
at Input.dispatchToTargets (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/scenery/js/input/Input.js:1850:12)
at Input.dispatchEvent (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/scenery/js/input/Input.js:1776:10)
at Input.dispatchA11yEvent (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/scenery/js/input/Input.js:1017:12)
at Input.keydownAction.Action.phetioPlayback (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/scenery/js/input/Input.js:681:14)
at Action.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at HTMLDivElement.<anonymous> (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/scenery/js/input/Input.js:727:30)
at KeyboardFuzzer.triggerDOMEvent (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/scenery/js/accessibility/KeyboardFuzzer.js:221:37)
at KeyboardFuzzer.triggerKeyDownUpEvents (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/scenery/js/accessibility/KeyboardFuzzer.js:115:12)
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
``` | 1.0 | CT Cannot read property disposeCircuitElement of null - Occurs in multiple CCK sims
```
circuit-construction-kit-dc-virtual-lab : interactive-description-fuzzBoard : built : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000
Query: fuzzBoard&supportsDescriptions&memoryLimit=1000
Uncaught TypeError: Cannot read property 'disposeCircuitElement' of null
TypeError: Cannot read property 'disposeCircuitElement' of null
at Object.keydown (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:1188338)
at t.value (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:653256)
at t.value (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:653455)
at t.value (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:652997)
at t.value (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:648420)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:644805
at e.value (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:598885)
at HTMLDivElement.<anonymous> (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:645487)
at t.value (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:1632527)
at t.value (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/build/phet/circuit-construction-kit-dc-virtual-lab_en_phet.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&fuzzBoard&supportsDescriptions&memoryLimit=1000:924:1631437)
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
circuit-construction-kit-dc-virtual-lab : interactive-description-fuzzBoard : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-dc-virtual-lab/circuit-construction-kit-dc-virtual-lab_en.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&brand=phet&ea&fuzzBoard&supportsDescriptions&memoryLimit=1000
Query: brand=phet&ea&fuzzBoard&supportsDescriptions&memoryLimit=1000
Uncaught TypeError: Cannot read property 'disposeCircuitElement' of null
TypeError: Cannot read property 'disposeCircuitElement' of null
at Object.keydown (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/circuit-construction-kit-common/js/view/CircuitElementNode.js:64:21)
at Input.dispatchToListeners (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/scenery/js/input/Input.js:1818:25)
at Input.dispatchToTargets (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/scenery/js/input/Input.js:1850:12)
at Input.dispatchEvent (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/scenery/js/input/Input.js:1776:10)
at Input.dispatchA11yEvent (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/scenery/js/input/Input.js:1017:12)
at Input.keydownAction.Action.phetioPlayback (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/scenery/js/input/Input.js:681:14)
at Action.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at HTMLDivElement.<anonymous> (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/scenery/js/input/Input.js:727:30)
at KeyboardFuzzer.triggerDOMEvent (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/scenery/js/accessibility/KeyboardFuzzer.js:221:37)
at KeyboardFuzzer.triggerKeyDownUpEvents (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/scenery/js/accessibility/KeyboardFuzzer.js:115:12)
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
``` | non_priority | ct cannot read property disposecircuitelement of null occurs in multiple cck sims circuit construction kit dc virtual lab interactive description fuzzboard built run query fuzzboard supportsdescriptions memorylimit uncaught typeerror cannot read property disposecircuitelement of null typeerror cannot read property disposecircuitelement of null at object keydown at t value at t value at t value at t value at at e value at htmldivelement at t value at t value id bayes chrome approximately pm circuit construction kit dc virtual lab interactive description fuzzboard require js run query brand phet ea fuzzboard supportsdescriptions memorylimit uncaught typeerror cannot read property disposecircuitelement of null typeerror cannot read property disposecircuitelement of null at object keydown at input dispatchtolisteners at input dispatchtotargets at input dispatchevent at input at input keydownaction action phetioplayback at action execute at htmldivelement at keyboardfuzzer triggerdomevent at keyboardfuzzer triggerkeydownupevents id bayes chrome approximately pm | 0 |
87,899 | 17,391,876,145 | IssuesEvent | 2021-08-02 08:28:21 | ministryofjustice/modernisation-platform | https://api.github.com/repos/ministryofjustice/modernisation-platform | closed | Investigate Terraform linters | code quality documentation enhancement | We should investigate using a Terraform linter such as [tflint](/terraform-linters/tflint) to ensure we remain consistent and in-line with best practice with the code we're writing. | 1.0 | Investigate Terraform linters - We should investigate using a Terraform linter such as [tflint](/terraform-linters/tflint) to ensure we remain consistent and in-line with best practice with the code we're writing. | non_priority | investigate terraform linters we should investigate using a terraform linter such as terraform linters tflint to ensure we remain consistent and in line with best practice with the code we re writing | 0 |
401,027 | 27,312,943,111 | IssuesEvent | 2023-02-24 13:39:52 | mcuee/libusb-win32 | https://api.github.com/repos/mcuee/libusb-win32 | opened | libusb0.sys filter driver may not work with some USB devices (please report issues here) | documentation | Take note there is no gurantee that libusb0.sys device filter (which functions as a upper filter) will work for all the USB devices.
Please report issues here. | 1.0 | libusb0.sys filter driver may not work with some USB devices (please report issues here) - Take note there is no gurantee that libusb0.sys device filter (which functions as a upper filter) will work for all the USB devices.
Please report issues here. | non_priority | sys filter driver may not work with some usb devices please report issues here take note there is no gurantee that sys device filter which functions as a upper filter will work for all the usb devices please report issues here | 0 |
130,533 | 18,090,858,211 | IssuesEvent | 2021-09-22 01:22:07 | carbon-design-system/carbon-addons-iot-react | https://api.github.com/repos/carbon-design-system/carbon-addons-iot-react | closed | [Icon content switcher] Styling enhancement | type: enhancement :bulb: val: 2 status: needs design :art: design reconciliation | Looking to update the icon content switcher styling slightly to match what Carbon has for their [content switcher](https://react.carbondesignsystem.com/?path=/story/contentswitcher--content-switcher-playground)
Updates:
- Update color of hover and selected states to match Carbon's content switcher
- remove stroke around default state (although that is in design on the PAL site but I'm not seeing it in code?)
- Round corners on the left and right end buttons
- Build in light variant
- Can we also update the placement of the tooltip that shows up to match what the [icon button](https://react.carbondesignsystem.com/?path=/story/button--playground) does?
Carbon style specs: https://www.carbondesignsystem.com/components/content-switcher/style
Specs:
| 2.0 | [Icon content switcher] Styling enhancement - Looking to update the icon content switcher styling slightly to match what Carbon has for their [content switcher](https://react.carbondesignsystem.com/?path=/story/contentswitcher--content-switcher-playground)
Updates:
- Update color of hover and selected states to match Carbon's content switcher
- remove stroke around default state (although that is in design on the PAL site but I'm not seeing it in code?)
- Round corners on the left and right end buttons
- Build in light variant
- Can we also update the placement of the tooltip that shows up to match what the [icon button](https://react.carbondesignsystem.com/?path=/story/button--playground) does?
Carbon style specs: https://www.carbondesignsystem.com/components/content-switcher/style
Specs:
| non_priority | styling enhancement looking to update the icon content switcher styling slightly to match what carbon has for their updates update color of hover and selected states to match carbon s content switcher remove stroke around default state although that is in design on the pal site but i m not seeing it in code round corners on the left and right end buttons build in light variant can we also update the placement of the tooltip that shows up to match what the does carbon style specs specs | 0 |
96,108 | 27,750,707,435 | IssuesEvent | 2023-03-15 20:29:21 | PowerShell/vscode-powershell | https://api.github.com/repos/PowerShell/vscode-powershell | closed | Adopt the pre-release extension feature | Issue-Enhancement Area-Build & Release | ### Prerequisites
- [X] I have written a descriptive issue title.
- [X] I have searched all [issues](https://github.com/PowerShell/vscode-powershell/issues?q=is%3Aissue) to ensure it has not already been reported.
### Summary
Refs: https://github.com/microsoft/vscode/issues/15756
VS Code now supports pre-release extensions. Docs that should help: https://code.visualstudio.com/api/working-with-extensions/publishing-extension#prerelease-extensions
I know powershell has a separate powershell preview extension. Ideally we would deprecate that extension and you would publish pre-release versions. VS Code can migrate your users automatically once you do the adoption.
Let me know what you think.
fyi @TylerLeonhardt
### Proposed Design
_No response_ | 1.0 | Adopt the pre-release extension feature - ### Prerequisites
- [X] I have written a descriptive issue title.
- [X] I have searched all [issues](https://github.com/PowerShell/vscode-powershell/issues?q=is%3Aissue) to ensure it has not already been reported.
### Summary
Refs: https://github.com/microsoft/vscode/issues/15756
VS Code now supports pre-release extensions. Docs that should help: https://code.visualstudio.com/api/working-with-extensions/publishing-extension#prerelease-extensions
I know powershell has a separate powershell preview extension. Ideally we would deprecate that extension and you would publish pre-release versions. VS Code can migrate your users automatically once you do the adoption.
Let me know what you think.
fyi @TylerLeonhardt
### Proposed Design
_No response_ | non_priority | adopt the pre release extension feature prerequisites i have written a descriptive issue title i have searched all to ensure it has not already been reported summary refs vs code now supports pre release extensions docs that should help i know powershell has a separate powershell preview extension ideally we would deprecate that extension and you would publish pre release versions vs code can migrate your users automatically once you do the adoption let me know what you think fyi tylerleonhardt proposed design no response | 0 |
53,605 | 28,309,581,441 | IssuesEvent | 2023-04-10 14:16:19 | apache/arrow-datafusion | https://api.github.com/repos/apache/arrow-datafusion | opened | Fuse grouped aggregate and filter operators for improved performance | enhancement performance | ### Is your feature request related to a problem or challenge?
When we perform a grouped aggregate on a filtered input (such as with TPC-H q1), the filter operator performs two main tasks:
- Evaluate the filter predicate (usually very fast)
- Create new batches and copy over the filtered data (very slow if the filter is not very selective, as in q1)
I wonder if we would see a significant performance improvement if we could avoid creating the filtered batches in this case.
One idea would be to create the filtered batches by copying the arrays and mutating the validity bitmap to hide the rows that are filtered out. This would potentially change the semantics in some cases though so we can probably only do this under certain conditions.
Another idea is to update the aggregate logic to perform the predicate evaluation and then use the resulting bitmap to determine which rows to accumulate.
### Describe the solution you'd like
I am working on a small prototype of this, outside of DataFusion, that I will share once the code is less embarrassing.
### Describe alternatives you've considered
It would be worth seeing how other engines handle this.
### Additional context
_No response_ | True | Fuse grouped aggregate and filter operators for improved performance - ### Is your feature request related to a problem or challenge?
When we perform a grouped aggregate on a filtered input (such as with TPC-H q1), the filter operator performs two main tasks:
- Evaluate the filter predicate (usually very fast)
- Create new batches and copy over the filtered data (very slow if the filter is not very selective, as in q1)
I wonder if we would see a significant performance improvement if we could avoid creating the filtered batches in this case.
One idea would be to create the filtered batches by copying the arrays and mutating the validity bitmap to hide the rows that are filtered out. This would potentially change the semantics in some cases though so we can probably only do this under certain conditions.
Another idea is to update the aggregate logic to perform the predicate evaluation and then use the resulting bitmap to determine which rows to accumulate.
### Describe the solution you'd like
I am working on a small prototype of this, outside of DataFusion, that I will share once the code is less embarrassing.
### Describe alternatives you've considered
It would be worth seeing how other engines handle this.
### Additional context
_No response_ | non_priority | fuse grouped aggregate and filter operators for improved performance is your feature request related to a problem or challenge when we perform a grouped aggregate on a filtered input such as with tpc h the filter operator performs two main tasks evaluate the filter predicate usually very fast create new batches and copy over the filtered data very slow if the filter is not very selective as in i wonder if we would see a significant performance improvement if we could avoid creating the filtered batches in this case one idea would be to create the filtered batches by copying the arrays and mutating the validity bitmap to hide the rows that are filtered out this would potentially change the semantics in some cases though so we can probably only do this under certain conditions another idea is to update the aggregate logic to perform the predicate evaluation and then use the resulting bitmap to determine which rows to accumulate describe the solution you d like i am working on a small prototype of this outside of datafusion that i will share once the code is less embarrassing describe alternatives you ve considered it would be worth seeing how other engines handle this additional context no response | 0 |
168,780 | 14,172,806,514 | IssuesEvent | 2020-11-12 17:26:10 | dsm-cefet-rj/trabalho-integrado-2020-1-grupo-2 | https://api.github.com/repos/dsm-cefet-rj/trabalho-integrado-2020-1-grupo-2 | closed | Criação do Kanban - aba Projects [8h] | documentation enhancement | :man_pilot: Estruturar todas as colunas com os cartões de tarefas a serem executadas pelas equipes de PSW e Teste de Software | 1.0 | Criação do Kanban - aba Projects [8h] - :man_pilot: Estruturar todas as colunas com os cartões de tarefas a serem executadas pelas equipes de PSW e Teste de Software | non_priority | criação do kanban aba projects man pilot estruturar todas as colunas com os cartões de tarefas a serem executadas pelas equipes de psw e teste de software | 0 |
427,680 | 29,832,419,267 | IssuesEvent | 2023-06-18 12:42:13 | keironchaudhry/june-pride-hackathon-2023 | https://api.github.com/repos/keironchaudhry/june-pride-hackathon-2023 | closed | User Story: History archive | documentation frontend | As a **user**, I want **to be able to view historical information** so that **I can learn and appreciate LGBTQ+ history**.
| 1.0 | User Story: History archive - As a **user**, I want **to be able to view historical information** so that **I can learn and appreciate LGBTQ+ history**.
| non_priority | user story history archive as a user i want to be able to view historical information so that i can learn and appreciate lgbtq history | 0 |
247,294 | 20,971,007,919 | IssuesEvent | 2022-03-28 11:22:11 | opencurve/curve | https://api.github.com/repos/opencurve/curve | closed | curvefs_tool create-fs failed, error is CREATE_PARTITION_ERROR | bug need test | **Describe the bug (描述bug)**
**To Reproduce (复现方法)**
use CurveAdm deploy a cluster with three etcd/mds/metaserver, and after deploy succeed, use curvefs_tool create a filesystem.
**Expected behavior (期望行为)**
**Versions (各种版本)**
fs: v0.2.0-beta
**Additional context/screenshots (更多上下文/截图)**
| 1.0 | curvefs_tool create-fs failed, error is CREATE_PARTITION_ERROR - **Describe the bug (描述bug)**
**To Reproduce (复现方法)**
use CurveAdm deploy a cluster with three etcd/mds/metaserver, and after deploy succeed, use curvefs_tool create a filesystem.
**Expected behavior (期望行为)**
**Versions (各种版本)**
fs: v0.2.0-beta
**Additional context/screenshots (更多上下文/截图)**
| non_priority | curvefs tool create fs failed error is create partition error describe the bug 描述bug to reproduce 复现方法 use curveadm deploy a cluster with three etcd mds metaserver and after deploy succeed use curvefs tool create a filesystem expected behavior 期望行为 versions 各种版本 fs beta additional context screenshots 更多上下文 截图 | 0 |
143,999 | 19,268,469,681 | IssuesEvent | 2021-12-10 00:49:54 | leanswift/bob-frontend | https://api.github.com/repos/leanswift/bob-frontend | opened | CVE-2021-23424 (High) detected in ansi-html-0.0.7.tgz | security vulnerability | ## CVE-2021-23424 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ansi-html-0.0.7.tgz</b></p></summary>
<p>An elegant lib that converts the chalked (ANSI) text to HTML.</p>
<p>Library home page: <a href="https://registry.npmjs.org/ansi-html/-/ansi-html-0.0.7.tgz">https://registry.npmjs.org/ansi-html/-/ansi-html-0.0.7.tgz</a></p>
<p>Path to dependency file: bob-frontend/package.json</p>
<p>Path to vulnerable library: bob-frontend/node_modules/ansi-html/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.7.3.tgz (Root Library)
- webpack-dev-server-2.11.2.tgz
- :x: **ansi-html-0.0.7.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/leanswift/bob-frontend/commit/e09ef1e3a45be925a41a2e1aa6a0bcbc6b3c41ea">e09ef1e3a45be925a41a2e1aa6a0bcbc6b3c41ea</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
This affects all versions of package ansi-html. If an attacker provides a malicious string, it will get stuck processing the input for an extremely long time.
<p>Publish Date: 2021-08-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23424>CVE-2021-23424</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"ansi-html","packageVersion":"0.0.7","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"@angular/cli:1.7.3;webpack-dev-server:2.11.2;ansi-html:0.0.7","isMinimumFixVersionAvailable":false,"isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23424","vulnerabilityDetails":"This affects all versions of package ansi-html. If an attacker provides a malicious string, it will get stuck processing the input for an extremely long time.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23424","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2021-23424 (High) detected in ansi-html-0.0.7.tgz - ## CVE-2021-23424 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ansi-html-0.0.7.tgz</b></p></summary>
<p>An elegant lib that converts the chalked (ANSI) text to HTML.</p>
<p>Library home page: <a href="https://registry.npmjs.org/ansi-html/-/ansi-html-0.0.7.tgz">https://registry.npmjs.org/ansi-html/-/ansi-html-0.0.7.tgz</a></p>
<p>Path to dependency file: bob-frontend/package.json</p>
<p>Path to vulnerable library: bob-frontend/node_modules/ansi-html/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.7.3.tgz (Root Library)
- webpack-dev-server-2.11.2.tgz
- :x: **ansi-html-0.0.7.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/leanswift/bob-frontend/commit/e09ef1e3a45be925a41a2e1aa6a0bcbc6b3c41ea">e09ef1e3a45be925a41a2e1aa6a0bcbc6b3c41ea</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
This affects all versions of package ansi-html. If an attacker provides a malicious string, it will get stuck processing the input for an extremely long time.
<p>Publish Date: 2021-08-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23424>CVE-2021-23424</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"ansi-html","packageVersion":"0.0.7","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"@angular/cli:1.7.3;webpack-dev-server:2.11.2;ansi-html:0.0.7","isMinimumFixVersionAvailable":false,"isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23424","vulnerabilityDetails":"This affects all versions of package ansi-html. If an attacker provides a malicious string, it will get stuck processing the input for an extremely long time.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23424","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in ansi html tgz cve high severity vulnerability vulnerable library ansi html tgz an elegant lib that converts the chalked ansi text to html library home page a href path to dependency file bob frontend package json path to vulnerable library bob frontend node modules ansi html package json dependency hierarchy cli tgz root library webpack dev server tgz x ansi html tgz vulnerable library found in head commit a href found in base branch master vulnerability details this affects all versions of package ansi html if an attacker provides a malicious string it will get stuck processing the input for an extremely long time publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree angular cli webpack dev server ansi html isminimumfixversionavailable false isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails this affects all versions of package ansi html if an attacker provides a malicious string it will get stuck processing the input for an extremely long time vulnerabilityurl | 0 |
91,265 | 15,856,386,602 | IssuesEvent | 2021-04-08 02:13:23 | n-devs/NodeJSControUI | https://api.github.com/repos/n-devs/NodeJSControUI | opened | CVE-2021-23337 (High) detected in lodash-4.17.5.tgz | security vulnerability | ## CVE-2021-23337 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.5.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.5.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.5.tgz</a></p>
<p>Path to dependency file: /NodeJSControUI/package.json</p>
<p>Path to vulnerable library: NodeJSControUI/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- jsdom-11.6.2.tgz (Root Library)
- request-promise-native-1.0.5.tgz
- request-promise-core-1.1.1.tgz
- :x: **lodash-4.17.5.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</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.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash - 4.17.21</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-23337 (High) detected in lodash-4.17.5.tgz - ## CVE-2021-23337 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.5.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.5.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.5.tgz</a></p>
<p>Path to dependency file: /NodeJSControUI/package.json</p>
<p>Path to vulnerable library: NodeJSControUI/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- jsdom-11.6.2.tgz (Root Library)
- request-promise-native-1.0.5.tgz
- request-promise-core-1.1.1.tgz
- :x: **lodash-4.17.5.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</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.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash - 4.17.21</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in lodash tgz cve high severity vulnerability vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file nodejscontroui package json path to vulnerable library nodejscontroui node modules lodash package json dependency hierarchy jsdom tgz root library request promise native tgz request promise core tgz x lodash tgz vulnerable library vulnerability details lodash versions prior to are vulnerable to command injection via the template function publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required high 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 lodash step up your open source security game with whitesource | 0 |
294,870 | 25,410,976,091 | IssuesEvent | 2022-11-22 18:56:57 | USEPA/haztrak | https://api.github.com/repos/USEPA/haztrak | opened | Tsdf Search API endpoint | enhancement good first issue django test | # 🚀 Feature Request
Add a generic API view that allows the client to POST search criteria to http server and return an array of Handler that are TSDFs and meet the search criteria.
This should be similar to #168 and should be relatively easy to implement. | 1.0 | Tsdf Search API endpoint - # 🚀 Feature Request
Add a generic API view that allows the client to POST search criteria to http server and return an array of Handler that are TSDFs and meet the search criteria.
This should be similar to #168 and should be relatively easy to implement. | non_priority | tsdf search api endpoint 🚀 feature request add a generic api view that allows the client to post search criteria to http server and return an array of handler that are tsdfs and meet the search criteria this should be similar to and should be relatively easy to implement | 0 |
19,869 | 4,448,611,708 | IssuesEvent | 2016-08-22 00:53:11 | BergFulton/metropolitan | https://api.github.com/repos/BergFulton/metropolitan | opened | Verify black and white paint job | History/Documentation | Was my car originally the black and white it claims to be (I think yes). But will seek verification. | 1.0 | Verify black and white paint job - Was my car originally the black and white it claims to be (I think yes). But will seek verification. | non_priority | verify black and white paint job was my car originally the black and white it claims to be i think yes but will seek verification | 0 |
31,713 | 4,287,152,798 | IssuesEvent | 2016-07-16 15:34:18 | StockSharp/StockSharp | https://api.github.com/repos/StockSharp/StockSharp | closed | Could not load file or assembly 'DevExpress.Xpf.Core | by design | While I was running my app based on stocksharp 4.3.14.1 referenced from NuGet, I got the following error:
```
Exception thrown: 'System.Windows.Markup.XamlParseException' in PresentationFramework.dll
Additional information: Could not load file or assembly 'DevExpress.Xpf.Core.v15.2, PublicKeyToken=b88d1754d700e49a' or one of its dependencies. The system cannot find the file specified.
```
What is the problem with DevExpress? And why has it never happened with previous versions?
Thanks | 1.0 | Could not load file or assembly 'DevExpress.Xpf.Core - While I was running my app based on stocksharp 4.3.14.1 referenced from NuGet, I got the following error:
```
Exception thrown: 'System.Windows.Markup.XamlParseException' in PresentationFramework.dll
Additional information: Could not load file or assembly 'DevExpress.Xpf.Core.v15.2, PublicKeyToken=b88d1754d700e49a' or one of its dependencies. The system cannot find the file specified.
```
What is the problem with DevExpress? And why has it never happened with previous versions?
Thanks | non_priority | could not load file or assembly devexpress xpf core while i was running my app based on stocksharp referenced from nuget i got the following error exception thrown system windows markup xamlparseexception in presentationframework dll additional information could not load file or assembly devexpress xpf core publickeytoken or one of its dependencies the system cannot find the file specified what is the problem with devexpress and why has it never happened with previous versions thanks | 0 |
375,683 | 26,172,746,639 | IssuesEvent | 2023-01-02 04:07:50 | dokku/dokku | https://api.github.com/repos/dokku/dokku | closed | Documentation Issue | type: documentation merge-level: patch difficulty: easy status: has plan plugin: nginx | ### Description of problem
I have a specific Dokku app which I use to catch all HTTP traffic to my server. This is what I would refer to as my "default app". On this same server, there are other deployed Dokku apps, each of which has one or more domain assigned to it. All HTTP requests which to not match any of the domains assigned to any of my running apps should end up hitting the "default app".
This is covered in the documentation here:
https://dokku.com/docs/networking/proxies/nginx/#default-site
It says:
>By default, Dokku will route any received request with an unknown HOST header value to the lexicographically first site in the nginx config stack.
However, this was not what actually happened. It looks like on a fresh install of Dokku on Ubuntu 20.04, nginx comes with a `default` site which is enabled under `/etc/nginx/sites-enabled/`, and which displays the "Welcome to Nginx" page. Once I removed the `default` symlink from that directory, and restarted nginx, everything worked as expected, with the default site (which is the lexicographically first site) handling all unknown hosts.
I would recommend mentioning this in this section of the docs. I am happy to make this change myself and submit a PR.
### Steps to reproduce
Install Dokku on Ubuntu 20.04.
Deploy two apps named:
- `0-app-1`
- `app-2`
Assign a domain to each app:
`dokku domains:add 0-app-1 app1.mydomain.com`
`dokku domains:add app-2 app2.mydomain.com`
Verify that traffic is being routed to the proper apps when you visit their respective domains.
Point the domain `app3.mydomain.com` to the same server, then visit that domain in a browser or send it a curl.
I would expect that the contents of `0-app-1` would be returned, since there is no app which as the domain `app3.mydomain.com`, but it returns the "Welcome to nginx" page, which is provided by the "default" site in `/etc/nginx/sites-enabled/`.
Remove the `default` symlink from `/etc/nginx/sites-enabled/`, and restart nginx with:
`service nginx restart`
Visit `app3.mydomain.com`, and receive the contents of `0-app-1`
### dokku report $APP_NAME
If this is necessary for this specific issue, please let me know, and I will provide it.
### Additional information
_No response_
### Output of failing commands after running: dokku trace:off
_No response_
### Output of failing commands after running: dokku trace:on
_No response_ | 1.0 | Documentation Issue - ### Description of problem
I have a specific Dokku app which I use to catch all HTTP traffic to my server. This is what I would refer to as my "default app". On this same server, there are other deployed Dokku apps, each of which has one or more domain assigned to it. All HTTP requests which to not match any of the domains assigned to any of my running apps should end up hitting the "default app".
This is covered in the documentation here:
https://dokku.com/docs/networking/proxies/nginx/#default-site
It says:
>By default, Dokku will route any received request with an unknown HOST header value to the lexicographically first site in the nginx config stack.
However, this was not what actually happened. It looks like on a fresh install of Dokku on Ubuntu 20.04, nginx comes with a `default` site which is enabled under `/etc/nginx/sites-enabled/`, and which displays the "Welcome to Nginx" page. Once I removed the `default` symlink from that directory, and restarted nginx, everything worked as expected, with the default site (which is the lexicographically first site) handling all unknown hosts.
I would recommend mentioning this in this section of the docs. I am happy to make this change myself and submit a PR.
### Steps to reproduce
Install Dokku on Ubuntu 20.04.
Deploy two apps named:
- `0-app-1`
- `app-2`
Assign a domain to each app:
`dokku domains:add 0-app-1 app1.mydomain.com`
`dokku domains:add app-2 app2.mydomain.com`
Verify that traffic is being routed to the proper apps when you visit their respective domains.
Point the domain `app3.mydomain.com` to the same server, then visit that domain in a browser or send it a curl.
I would expect that the contents of `0-app-1` would be returned, since there is no app which as the domain `app3.mydomain.com`, but it returns the "Welcome to nginx" page, which is provided by the "default" site in `/etc/nginx/sites-enabled/`.
Remove the `default` symlink from `/etc/nginx/sites-enabled/`, and restart nginx with:
`service nginx restart`
Visit `app3.mydomain.com`, and receive the contents of `0-app-1`
### dokku report $APP_NAME
If this is necessary for this specific issue, please let me know, and I will provide it.
### Additional information
_No response_
### Output of failing commands after running: dokku trace:off
_No response_
### Output of failing commands after running: dokku trace:on
_No response_ | non_priority | documentation issue description of problem i have a specific dokku app which i use to catch all http traffic to my server this is what i would refer to as my default app on this same server there are other deployed dokku apps each of which has one or more domain assigned to it all http requests which to not match any of the domains assigned to any of my running apps should end up hitting the default app this is covered in the documentation here it says by default dokku will route any received request with an unknown host header value to the lexicographically first site in the nginx config stack however this was not what actually happened it looks like on a fresh install of dokku on ubuntu nginx comes with a default site which is enabled under etc nginx sites enabled and which displays the welcome to nginx page once i removed the default symlink from that directory and restarted nginx everything worked as expected with the default site which is the lexicographically first site handling all unknown hosts i would recommend mentioning this in this section of the docs i am happy to make this change myself and submit a pr steps to reproduce install dokku on ubuntu deploy two apps named app app assign a domain to each app dokku domains add app mydomain com dokku domains add app mydomain com verify that traffic is being routed to the proper apps when you visit their respective domains point the domain mydomain com to the same server then visit that domain in a browser or send it a curl i would expect that the contents of app would be returned since there is no app which as the domain mydomain com but it returns the welcome to nginx page which is provided by the default site in etc nginx sites enabled remove the default symlink from etc nginx sites enabled and restart nginx with service nginx restart visit mydomain com and receive the contents of app dokku report app name if this is necessary for this specific issue please let me know and i will provide it additional information no response output of failing commands after running dokku trace off no response output of failing commands after running dokku trace on no response | 0 |
71,672 | 30,914,170,900 | IssuesEvent | 2023-08-05 04:11:52 | Zahlungsmittel/Zahlungsmittel | https://api.github.com/repos/Zahlungsmittel/Zahlungsmittel | opened | [CLOSED] feat: Test Apollo Provider in Frontend | epic service: wallet frontend feature devops test service: admin frontend imported | <a href="https://github.com/Mogge"><img src="https://avatars.githubusercontent.com/u/15882241?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [Mogge](https://github.com/Mogge)**
_Tuesday Dec 07, 2021 at 17:45 GMT_
_Originally opened as https://github.com/gradido/gradido/pull/1161_
----
## 🍰 Pullrequest
Test the middleware of the apollo provider in the frontend.
### Issues
- fixes #739
- fixes #1154
----
_**[Mogge](https://github.com/Mogge)** included the following code: https://github.com/gradido/gradido/pull/1161/commits_
| 2.0 | [CLOSED] feat: Test Apollo Provider in Frontend - <a href="https://github.com/Mogge"><img src="https://avatars.githubusercontent.com/u/15882241?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [Mogge](https://github.com/Mogge)**
_Tuesday Dec 07, 2021 at 17:45 GMT_
_Originally opened as https://github.com/gradido/gradido/pull/1161_
----
## 🍰 Pullrequest
Test the middleware of the apollo provider in the frontend.
### Issues
- fixes #739
- fixes #1154
----
_**[Mogge](https://github.com/Mogge)** included the following code: https://github.com/gradido/gradido/pull/1161/commits_
| non_priority | feat test apollo provider in frontend issue by tuesday dec at gmt originally opened as 🍰 pullrequest test the middleware of the apollo provider in the frontend issues fixes fixes included the following code | 0 |
155,498 | 19,802,891,111 | IssuesEvent | 2022-01-19 01:08:58 | susanstwss/SecurityShepherd | https://api.github.com/repos/susanstwss/SecurityShepherd | opened | CVE-2022-23302 (High) detected in log4j-1.2.7.jar | security vulnerability | ## CVE-2022-23302 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>log4j-1.2.7.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /tory/log4j/log4j/1.2.7/log4j-1.2.7.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.7.jar** (Vulnerable Library)
<p>Found in base branch: <b>dev</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
<p>Publish Date: 2022-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23302>CVE-2022-23302</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.7","packageFilePaths":["/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"log4j:log4j:1.2.7","isMinimumFixVersionAvailable":false,"isBinary":false}],"baseBranches":["dev"],"vulnerabilityIdentifier":"CVE-2022-23302","vulnerabilityDetails":"JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23302","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2022-23302 (High) detected in log4j-1.2.7.jar - ## CVE-2022-23302 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>log4j-1.2.7.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /tory/log4j/log4j/1.2.7/log4j-1.2.7.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.7.jar** (Vulnerable Library)
<p>Found in base branch: <b>dev</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
<p>Publish Date: 2022-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23302>CVE-2022-23302</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.7","packageFilePaths":["/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"log4j:log4j:1.2.7","isMinimumFixVersionAvailable":false,"isBinary":false}],"baseBranches":["dev"],"vulnerabilityIdentifier":"CVE-2022-23302","vulnerabilityDetails":"JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23302","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in jar cve high severity vulnerability vulnerable library jar path to dependency file pom xml path to vulnerable library tory jar dependency hierarchy x jar vulnerable library found in base branch dev vulnerability details jmssink in all versions of x is vulnerable to deserialization of untrusted data when the attacker has write access to the configuration or if the configuration references an ldap service the attacker has access to the attacker can provide a topicconnectionfactorybindingname configuration causing jmssink to perform jndi requests that result in remote code execution in a similar fashion to cve note this issue only affects x when specifically configured to use jmssink which is not the default apache reached end of life in august users should upgrade to as it addresses numerous other issues from the previous versions publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree isminimumfixversionavailable false isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails jmssink in all versions of x is vulnerable to deserialization of untrusted data when the attacker has write access to the configuration or if the configuration references an ldap service the attacker has access to the attacker can provide a topicconnectionfactorybindingname configuration causing jmssink to perform jndi requests that result in remote code execution in a similar fashion to cve note this issue only affects x when specifically configured to use jmssink which is not the default apache reached end of life in august users should upgrade to as it addresses numerous other issues from the previous versions vulnerabilityurl | 0 |
91,787 | 26,486,715,102 | IssuesEvent | 2023-01-17 18:40:29 | golang/go | https://api.github.com/repos/golang/go | opened | x/build: use cloud build to deploy x/build services | Builders NeedsInvestigation | We should automate the building and deployment of infrastructure binaries. The components of the infrastructure should be built in a central environment.
@golang/release | 1.0 | x/build: use cloud build to deploy x/build services - We should automate the building and deployment of infrastructure binaries. The components of the infrastructure should be built in a central environment.
@golang/release | non_priority | x build use cloud build to deploy x build services we should automate the building and deployment of infrastructure binaries the components of the infrastructure should be built in a central environment golang release | 0 |
280,311 | 24,293,579,487 | IssuesEvent | 2022-09-29 08:18:19 | valory-xyz/open-autonomy | https://api.github.com/repos/valory-xyz/open-autonomy | closed | Containers need more time to start on CI from `contracts-amm` image | test | ### Subject of the issue
Some tests are flaky because containers fail to start on time on CI. Specifically, this happened on [Merge pull request #1395 from valory-xyz/feat/autoupdate-packagelist main_workflow #5418](https://github.com/valory-xyz/open-autonomy/actions/runs/3133747181/jobs/5087596544) for some tests that use the `contracts-amm` image.
We could try increasing the max attempts, e.g., from 20 to 25, here:
https://github.com/valory-xyz/open-autonomy/blob/61c7f69b3e6290e94fdc6837cf3bbaaddccdcf22/plugins/aea-test-autonomy/aea_test_autonomy/fixture_helpers.py#L277
Example of the failure:
```
2022-09-27T08:08:33.0046808Z INFO aea_test_autonomy.docker.base:base.py:140 Setting up image valory/contracts-amm:latest...
2022-09-27T08:08:33.0047362Z DEBUG urllib3.connectionpool:connectionpool.py:228 Starting new HTTP connection (1): 127.0.0.1:8545
2022-09-27T08:08:33.0048124Z ERROR root:amm_net.py:98 Exception: ConnectionError: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
2022-09-27T08:08:33.0048653Z INFO root:amm_net.py:99 Attempt 0 failed. Retrying in 2.0 seconds...
.
.
.
2022-09-27T08:08:33.0083634Z DEBUG urllib3.connectionpool:connectionpool.py:228 Starting new HTTP connection (1): 127.0.0.1:8545
2022-09-27T08:08:33.0084423Z ERROR root:amm_net.py:98 Exception: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2022-09-27T08:08:33.0084953Z INFO root:amm_net.py:99 Attempt 19 failed. Retrying in 2.0 seconds...
```
| 1.0 | Containers need more time to start on CI from `contracts-amm` image - ### Subject of the issue
Some tests are flaky because containers fail to start on time on CI. Specifically, this happened on [Merge pull request #1395 from valory-xyz/feat/autoupdate-packagelist main_workflow #5418](https://github.com/valory-xyz/open-autonomy/actions/runs/3133747181/jobs/5087596544) for some tests that use the `contracts-amm` image.
We could try increasing the max attempts, e.g., from 20 to 25, here:
https://github.com/valory-xyz/open-autonomy/blob/61c7f69b3e6290e94fdc6837cf3bbaaddccdcf22/plugins/aea-test-autonomy/aea_test_autonomy/fixture_helpers.py#L277
Example of the failure:
```
2022-09-27T08:08:33.0046808Z INFO aea_test_autonomy.docker.base:base.py:140 Setting up image valory/contracts-amm:latest...
2022-09-27T08:08:33.0047362Z DEBUG urllib3.connectionpool:connectionpool.py:228 Starting new HTTP connection (1): 127.0.0.1:8545
2022-09-27T08:08:33.0048124Z ERROR root:amm_net.py:98 Exception: ConnectionError: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
2022-09-27T08:08:33.0048653Z INFO root:amm_net.py:99 Attempt 0 failed. Retrying in 2.0 seconds...
.
.
.
2022-09-27T08:08:33.0083634Z DEBUG urllib3.connectionpool:connectionpool.py:228 Starting new HTTP connection (1): 127.0.0.1:8545
2022-09-27T08:08:33.0084423Z ERROR root:amm_net.py:98 Exception: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2022-09-27T08:08:33.0084953Z INFO root:amm_net.py:99 Attempt 19 failed. Retrying in 2.0 seconds...
```
| non_priority | containers need more time to start on ci from contracts amm image subject of the issue some tests are flaky because containers fail to start on time on ci specifically this happened on for some tests that use the contracts amm image we could try increasing the max attempts e g from to here example of the failure info aea test autonomy docker base base py setting up image valory contracts amm latest debug connectionpool connectionpool py starting new http connection error root amm net py exception connectionerror connection aborted connectionreseterror connection reset by peer info root amm net py attempt failed retrying in seconds debug connectionpool connectionpool py starting new http connection error root amm net py exception connectionerror connection aborted remotedisconnected remote end closed connection without response info root amm net py attempt failed retrying in seconds | 0 |
227,399 | 25,070,088,718 | IssuesEvent | 2022-11-07 11:24:48 | Watemlifts/Platform-Integration | https://api.github.com/repos/Watemlifts/Platform-Integration | opened | CVE-2020-14343 (High) detected in PyYAML-5.1.1.tar.gz | security vulnerability | ## CVE-2020-14343 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>PyYAML-5.1.1.tar.gz</b></p></summary>
<p>YAML parser and emitter for Python</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a3/65/837fefac7475963d1eccf4aa684c23b95aa6c1d033a2c5965ccb11e22623/PyYAML-5.1.1.tar.gz">https://files.pythonhosted.org/packages/a3/65/837fefac7475963d1eccf4aa684c23b95aa6c1d033a2c5965ccb11e22623/PyYAML-5.1.1.tar.gz</a></p>
<p>Path to dependency file: /homeassistant</p>
<p>Path to vulnerable library: /homeassistant,/homeassistant/components/device_tracker,/tmp/ws-scm/Platform-Integration</p>
<p>
Dependency Hierarchy:
- :x: **PyYAML-5.1.1.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Watemlifts/Platform-Integration/commit/815dc70d82791ab5e7a25a43588702e4458fd9f6">815dc70d82791ab5e7a25a43588702e4458fd9f6</a></p>
<p>Found in base branch: <b>dev</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747.
<p>Publish Date: 2021-02-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-14343>CVE-2020-14343</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14343">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14343</a></p>
<p>Release Date: 2021-02-09</p>
<p>Fix Resolution: PyYAML - 5.4</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-2020-14343 (High) detected in PyYAML-5.1.1.tar.gz - ## CVE-2020-14343 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>PyYAML-5.1.1.tar.gz</b></p></summary>
<p>YAML parser and emitter for Python</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/a3/65/837fefac7475963d1eccf4aa684c23b95aa6c1d033a2c5965ccb11e22623/PyYAML-5.1.1.tar.gz">https://files.pythonhosted.org/packages/a3/65/837fefac7475963d1eccf4aa684c23b95aa6c1d033a2c5965ccb11e22623/PyYAML-5.1.1.tar.gz</a></p>
<p>Path to dependency file: /homeassistant</p>
<p>Path to vulnerable library: /homeassistant,/homeassistant/components/device_tracker,/tmp/ws-scm/Platform-Integration</p>
<p>
Dependency Hierarchy:
- :x: **PyYAML-5.1.1.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Watemlifts/Platform-Integration/commit/815dc70d82791ab5e7a25a43588702e4458fd9f6">815dc70d82791ab5e7a25a43588702e4458fd9f6</a></p>
<p>Found in base branch: <b>dev</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747.
<p>Publish Date: 2021-02-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-14343>CVE-2020-14343</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14343">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14343</a></p>
<p>Release Date: 2021-02-09</p>
<p>Fix Resolution: PyYAML - 5.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in pyyaml tar gz cve high severity vulnerability vulnerable library pyyaml tar gz yaml parser and emitter for python library home page a href path to dependency file homeassistant path to vulnerable library homeassistant homeassistant components device tracker tmp ws scm platform integration dependency hierarchy x pyyaml tar gz vulnerable library found in head commit a href found in base branch dev vulnerability details a vulnerability was discovered in the pyyaml library in versions before where it is susceptible to arbitrary code execution when it processes untrusted yaml files through the full load method or with the fullloader loader applications that use the library to process untrusted input may be vulnerable to this flaw this flaw allows an attacker to execute arbitrary code on the system by abusing the python object new constructor this flaw is due to an incomplete fix for cve publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact 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 pyyaml step up your open source security game with mend | 0 |
105,228 | 16,624,753,868 | IssuesEvent | 2021-06-03 08:10:08 | tabac-ws-demo/js-demo | https://api.github.com/repos/tabac-ws-demo/js-demo | opened | CVE-2020-7598 (Medium) detected in multiple libraries | security vulnerability | ## CVE-2020-7598 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>minimist-0.0.8.tgz</b>, <b>minimist-1.2.0.tgz</b>, <b>minimist-0.0.10.tgz</b></p></summary>
<p>
<details><summary><b>minimist-0.0.8.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz</a></p>
<p>Path to dependency file: js-demo/package.json</p>
<p>Path to vulnerable library: js-demo/node_modules/npm/node_modules/mkdirp/node_modules/minimist/package.json,js-demo/node_modules/mkdirp/node_modules/minimist/package.json,js-demo/node_modules/nyc/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- mkdirp-0.5.1.tgz
- :x: **minimist-0.0.8.tgz** (Vulnerable Library)
</details>
<details><summary><b>minimist-1.2.0.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz</a></p>
<p>Path to dependency file: js-demo/package.json</p>
<p>Path to vulnerable library: js-demo/node_modules/cypress/node_modules/minimist/package.json,js-demo/node_modules/meow/node_modules/minimist/package.json,js-demo/node_modules/nyc/node_modules/detect-indent/node_modules/minimist/package.json,js-demo/node_modules/coveralls/node_modules/minimist/package.json,js-demo/node_modules/rc/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- grunt-jsbeautifier-0.2.13.tgz (Root Library)
- rc-1.2.8.tgz
- :x: **minimist-1.2.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>minimist-0.0.10.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz</a></p>
<p>Path to dependency file: js-demo/package.json</p>
<p>Path to vulnerable library: js-demo/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- optimist-0.6.1.tgz
- :x: **minimist-0.0.10.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://api.github.com/repos/tabac-ws-demo/js-demo/commits/4840889fc8b8ea4bff3ddf2e3e2ebb4f9eb28d88">4840889fc8b8ea4bff3ddf2e3e2ebb4f9eb28d88</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "__proto__" payload.
<p>Publish Date: 2020-03-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598>CVE-2020-7598</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94">https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94</a></p>
<p>Release Date: 2020-03-11</p>
<p>Fix Resolution: minimist - 0.2.1,1.2.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"0.0.8","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;mkdirp:0.5.1;minimist:0.0.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"minimist - 0.2.1,1.2.3"},{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"1.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-jsbeautifier:0.2.13;rc:1.2.8;minimist:1.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"minimist - 0.2.1,1.2.3"},{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"0.0.10","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"forever:2.0.0;optimist:0.6.1;minimist:0.0.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"minimist - 0.2.1,1.2.3"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-7598","vulnerabilityDetails":"minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a \"constructor\" or \"__proto__\" payload.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598","cvss3Severity":"medium","cvss3Score":"5.6","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-7598 (Medium) detected in multiple libraries - ## CVE-2020-7598 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>minimist-0.0.8.tgz</b>, <b>minimist-1.2.0.tgz</b>, <b>minimist-0.0.10.tgz</b></p></summary>
<p>
<details><summary><b>minimist-0.0.8.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz</a></p>
<p>Path to dependency file: js-demo/package.json</p>
<p>Path to vulnerable library: js-demo/node_modules/npm/node_modules/mkdirp/node_modules/minimist/package.json,js-demo/node_modules/mkdirp/node_modules/minimist/package.json,js-demo/node_modules/nyc/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- mkdirp-0.5.1.tgz
- :x: **minimist-0.0.8.tgz** (Vulnerable Library)
</details>
<details><summary><b>minimist-1.2.0.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz</a></p>
<p>Path to dependency file: js-demo/package.json</p>
<p>Path to vulnerable library: js-demo/node_modules/cypress/node_modules/minimist/package.json,js-demo/node_modules/meow/node_modules/minimist/package.json,js-demo/node_modules/nyc/node_modules/detect-indent/node_modules/minimist/package.json,js-demo/node_modules/coveralls/node_modules/minimist/package.json,js-demo/node_modules/rc/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- grunt-jsbeautifier-0.2.13.tgz (Root Library)
- rc-1.2.8.tgz
- :x: **minimist-1.2.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>minimist-0.0.10.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz</a></p>
<p>Path to dependency file: js-demo/package.json</p>
<p>Path to vulnerable library: js-demo/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- optimist-0.6.1.tgz
- :x: **minimist-0.0.10.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://api.github.com/repos/tabac-ws-demo/js-demo/commits/4840889fc8b8ea4bff3ddf2e3e2ebb4f9eb28d88">4840889fc8b8ea4bff3ddf2e3e2ebb4f9eb28d88</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "__proto__" payload.
<p>Publish Date: 2020-03-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598>CVE-2020-7598</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94">https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94</a></p>
<p>Release Date: 2020-03-11</p>
<p>Fix Resolution: minimist - 0.2.1,1.2.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"0.0.8","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;mkdirp:0.5.1;minimist:0.0.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"minimist - 0.2.1,1.2.3"},{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"1.2.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-jsbeautifier:0.2.13;rc:1.2.8;minimist:1.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"minimist - 0.2.1,1.2.3"},{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"0.0.10","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"forever:2.0.0;optimist:0.6.1;minimist:0.0.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"minimist - 0.2.1,1.2.3"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-7598","vulnerabilityDetails":"minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a \"constructor\" or \"__proto__\" payload.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598","cvss3Severity":"medium","cvss3Score":"5.6","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries minimist tgz minimist tgz minimist tgz minimist tgz parse argument options library home page a href path to dependency file js demo package json path to vulnerable library js demo node modules npm node modules mkdirp node modules minimist package json js demo node modules mkdirp node modules minimist package json js demo node modules nyc node modules minimist package json dependency hierarchy grunt npm install tgz root library npm tgz mkdirp tgz x minimist tgz vulnerable library minimist tgz parse argument options library home page a href path to dependency file js demo package json path to vulnerable library js demo node modules cypress node modules minimist package json js demo node modules meow node modules minimist package json js demo node modules nyc node modules detect indent node modules minimist package json js demo node modules coveralls node modules minimist package json js demo node modules rc node modules minimist package json dependency hierarchy grunt jsbeautifier tgz root library rc tgz x minimist tgz vulnerable library minimist tgz parse argument options library home page a href path to dependency file js demo package json path to vulnerable library js demo node modules minimist package json dependency hierarchy forever tgz root library optimist tgz x minimist tgz vulnerable library found in head commit a href found in base branch master vulnerability details minimist before could be tricked into adding or modifying properties of object prototype using a constructor or proto payload publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution minimist isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree grunt npm install npm mkdirp minimist isminimumfixversionavailable true minimumfixversion minimist packagetype javascript node js packagename minimist packageversion packagefilepaths istransitivedependency true dependencytree grunt jsbeautifier rc minimist isminimumfixversionavailable true minimumfixversion minimist packagetype javascript node js packagename minimist packageversion packagefilepaths istransitivedependency true dependencytree forever optimist minimist isminimumfixversionavailable true minimumfixversion minimist basebranches vulnerabilityidentifier cve vulnerabilitydetails minimist before could be tricked into adding or modifying properties of object prototype using a constructor or proto payload vulnerabilityurl | 0 |
134,094 | 18,421,773,587 | IssuesEvent | 2021-10-13 16:54:17 | daniel-brown-ws-test/verademo | https://api.github.com/repos/daniel-brown-ws-test/verademo | closed | CVE-2020-5421 (Medium) detected in spring-web-5.2.7.RELEASE.jar | security vulnerability IaC violation | ## CVE-2020-5421 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-web-5.2.7.RELEASE.jar</b></p></summary>
<p>Spring Web</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: verademo/app/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.7.RELEASE/spring-web-5.2.7.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.3.1.RELEASE.jar (Root Library)
- :x: **spring-web-5.2.7.RELEASE.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/daniel-brown-ws-test/verademo/commit/93ec43e511ee189f3bf2254c555dfd88253afa89">93ec43e511ee189f3bf2254c555dfd88253afa89</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported versions, the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the browser used through the use of a jsessionid path parameter.
<p>Publish Date: 2020-09-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-5421>CVE-2020-5421</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://tanzu.vmware.com/security/cve-2020-5421">https://tanzu.vmware.com/security/cve-2020-5421</a></p>
<p>Release Date: 2020-09-19</p>
<p>Fix Resolution: org.springframework:spring-web:4.3.29,5.0.19,5.1.18,5.2.9</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.springframework","packageName":"spring-web","packageVersion":"5.2.7.RELEASE","packageFilePaths":["/app/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework.boot:spring-boot-starter-web:2.3.1.RELEASE;org.springframework:spring-web:5.2.7.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework:spring-web:4.3.29,5.0.19,5.1.18,5.2.9"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2020-5421","vulnerabilityDetails":"In Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported versions, the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the browser used through the use of a jsessionid path parameter.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-5421","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"High","PR":"Low","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-5421 (Medium) detected in spring-web-5.2.7.RELEASE.jar - ## CVE-2020-5421 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-web-5.2.7.RELEASE.jar</b></p></summary>
<p>Spring Web</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: verademo/app/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.7.RELEASE/spring-web-5.2.7.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.3.1.RELEASE.jar (Root Library)
- :x: **spring-web-5.2.7.RELEASE.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/daniel-brown-ws-test/verademo/commit/93ec43e511ee189f3bf2254c555dfd88253afa89">93ec43e511ee189f3bf2254c555dfd88253afa89</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported versions, the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the browser used through the use of a jsessionid path parameter.
<p>Publish Date: 2020-09-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-5421>CVE-2020-5421</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://tanzu.vmware.com/security/cve-2020-5421">https://tanzu.vmware.com/security/cve-2020-5421</a></p>
<p>Release Date: 2020-09-19</p>
<p>Fix Resolution: org.springframework:spring-web:4.3.29,5.0.19,5.1.18,5.2.9</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.springframework","packageName":"spring-web","packageVersion":"5.2.7.RELEASE","packageFilePaths":["/app/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework.boot:spring-boot-starter-web:2.3.1.RELEASE;org.springframework:spring-web:5.2.7.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework:spring-web:4.3.29,5.0.19,5.1.18,5.2.9"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2020-5421","vulnerabilityDetails":"In Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported versions, the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the browser used through the use of a jsessionid path parameter.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-5421","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"High","PR":"Low","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in spring web release jar cve medium severity vulnerability vulnerable library spring web release jar spring web library home page a href path to dependency file verademo app pom xml path to vulnerable library home wss scanner repository org springframework spring web release spring web release jar dependency hierarchy spring boot starter web release jar root library x spring web release jar vulnerable library found in head commit a href found in base branch main vulnerability details in spring framework versions and older unsupported versions the protections against rfd attacks from cve may be bypassed depending on the browser used through the use of a jsessionid path parameter publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction required scope changed impact metrics confidentiality impact low 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 org springframework spring web isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree org springframework boot spring boot starter web release org springframework spring web release isminimumfixversionavailable true minimumfixversion org springframework spring web basebranches vulnerabilityidentifier cve vulnerabilitydetails in spring framework versions and older unsupported versions the protections against rfd attacks from cve may be bypassed depending on the browser used through the use of a jsessionid path parameter vulnerabilityurl | 0 |
101,814 | 31,683,149,037 | IssuesEvent | 2023-09-08 02:49:17 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | opened | [wasm][debugger] CheckInspectLocalsAtBreakpointSite | blocking-clean-ci Known Build Error | ## Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=398924
Build error leg or test failing: chrome-DebuggerTests.GetPropertiesTests.WorkItemExecution
Pull request: https://github.com/dotnet/runtime/pull/91759
<!-- Error message template -->
## Error Message
Fill the error message using [step by step known issues guidance](https://github.com/dotnet/arcade/blob/main/Documentation/Projects/Build%20Analysis/KnownIssues.md#how-to-fill-out-a-known-issue-error-section).
<!-- Use ErrorMessage for String.Contains matches. Use ErrorPattern for regex matches (single line/no backtracking). Set BuildRetry to `true` to retry builds with this error. Set ExcludeConsoleLog to `true` to skip helix logs analysis. -->
```json
{
"ErrorMessage": "CheckInspectLocalsAtBreakpointSite",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
```
| 1.0 | [wasm][debugger] CheckInspectLocalsAtBreakpointSite - ## Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=398924
Build error leg or test failing: chrome-DebuggerTests.GetPropertiesTests.WorkItemExecution
Pull request: https://github.com/dotnet/runtime/pull/91759
<!-- Error message template -->
## Error Message
Fill the error message using [step by step known issues guidance](https://github.com/dotnet/arcade/blob/main/Documentation/Projects/Build%20Analysis/KnownIssues.md#how-to-fill-out-a-known-issue-error-section).
<!-- Use ErrorMessage for String.Contains matches. Use ErrorPattern for regex matches (single line/no backtracking). Set BuildRetry to `true` to retry builds with this error. Set ExcludeConsoleLog to `true` to skip helix logs analysis. -->
```json
{
"ErrorMessage": "CheckInspectLocalsAtBreakpointSite",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
```
| non_priority | checkinspectlocalsatbreakpointsite build information build build error leg or test failing chrome debuggertests getpropertiestests workitemexecution pull request error message fill the error message using json errormessage checkinspectlocalsatbreakpointsite errorpattern buildretry false excludeconsolelog false | 0 |
103,933 | 16,613,263,775 | IssuesEvent | 2021-06-02 13:58:26 | Thanraj/linux-4.1.15 | https://api.github.com/repos/Thanraj/linux-4.1.15 | opened | CVE-2019-19966 (Medium) detected in linux-stable-rtv4.1.33 | security vulnerability | ## CVE-2019-19966 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://api.github.com/repos/Thanraj/linux-4.1.15/commits/5e3fb3e332499e1ad10a0969e55582af1027b085">5e3fb3e332499e1ad10a0969e55582af1027b085</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 (3)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>linux-4.1.15/drivers/media/usb/cpia2/cpia2_v4l.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>linux-4.1.15/drivers/media/usb/cpia2/cpia2_v4l.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>linux-4.1.15/drivers/media/usb/cpia2/cpia2_v4l.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In the Linux kernel before 5.1.6, there is a use-after-free in cpia2_exit() in drivers/media/usb/cpia2/cpia2_v4l.c that will cause denial of service, aka CID-dea37a972655.
<p>Publish Date: 2019-12-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-19966>CVE-2019-19966</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Physical
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19966">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19966</a></p>
<p>Release Date: 2019-12-25</p>
<p>Fix Resolution: v5.2-rc1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2019-19966 (Medium) detected in linux-stable-rtv4.1.33 - ## CVE-2019-19966 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://api.github.com/repos/Thanraj/linux-4.1.15/commits/5e3fb3e332499e1ad10a0969e55582af1027b085">5e3fb3e332499e1ad10a0969e55582af1027b085</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 (3)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>linux-4.1.15/drivers/media/usb/cpia2/cpia2_v4l.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>linux-4.1.15/drivers/media/usb/cpia2/cpia2_v4l.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>linux-4.1.15/drivers/media/usb/cpia2/cpia2_v4l.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In the Linux kernel before 5.1.6, there is a use-after-free in cpia2_exit() in drivers/media/usb/cpia2/cpia2_v4l.c that will cause denial of service, aka CID-dea37a972655.
<p>Publish Date: 2019-12-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-19966>CVE-2019-19966</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Physical
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19966">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19966</a></p>
<p>Release Date: 2019-12-25</p>
<p>Fix Resolution: v5.2-rc1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in linux stable cve medium severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href found in base branch master vulnerable source files linux drivers media usb c linux drivers media usb c linux drivers media usb c vulnerability details in the linux kernel before there is a use after free in exit in drivers media usb c that will cause denial of service aka cid publish date url a href cvss score details base score metrics exploitability metrics attack vector physical attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
347,974 | 24,905,251,326 | IssuesEvent | 2022-10-29 06:36:35 | aws-actions/amazon-ecr-login | https://api.github.com/repos/aws-actions/amazon-ecr-login | closed | Possible to just use and deploy containers for my github aciton environment from aws (NOT TO PUSH, IF NOT PULL) | documentation | Hi community!
I would like to ask for a feature (or in case of me missing this feature please help me to see how to proceed), when deploying actions in github CI.
**Basically I dont find any info about how to pull containers from aws and deploy them in CI github actions during the job execution**
```
jobs:
backend-job:
name: CI backend Integration env
runs-on: ubuntu-latest
services:
postgres:
image: postgres:10
ports:
- 5432:5432
rabbitmq:
image: rabbitmq
ports:
- 5672:5672
redis:
image: redis:alpine
ports:
- 6379:6379
steps:
- name: Step 1
uses: ...
- name: Step 2
uses: ...
```
and add own docker-based app containers (from aws, google, heroku... whatever) passing credentials like:
```
...
services:
.....
some-aws-service:
image: XXXXXXXXX.YYY.ecr.eu-west-1.amazonaws.com/<AWS OWN SERVICE>:latest
ports:
- 5000:5000
credentials:
username: ${{ secrets.AWS_ACCESS_KEY_ID }}
password: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
```
Following multiple approaches like proposed (here:)[https://docs.github.com/es/actions/using-jobs/running-jobs-in-a-container]
But I receive this:
I also added these (steps)[https://github.com/aws-actions/amazon-ecr-login] at the begining:
```
- name: Configure AWS credentials
uses: aws-actions/configure-aws-credentials@v1
with:
role-to-assume: arn:aws:iam::123456789012:role/my-github-actions-role
aws-region: us-east-1
- name: Login to Amazon ECR Private
id: login-ecr
uses: aws-actions/amazon-ecr-login@v1
...
```
But nothing was possible...
Can you shed more light on this please?
Many thanks in advance!!!! | 1.0 | Possible to just use and deploy containers for my github aciton environment from aws (NOT TO PUSH, IF NOT PULL) - Hi community!
I would like to ask for a feature (or in case of me missing this feature please help me to see how to proceed), when deploying actions in github CI.
**Basically I dont find any info about how to pull containers from aws and deploy them in CI github actions during the job execution**
```
jobs:
backend-job:
name: CI backend Integration env
runs-on: ubuntu-latest
services:
postgres:
image: postgres:10
ports:
- 5432:5432
rabbitmq:
image: rabbitmq
ports:
- 5672:5672
redis:
image: redis:alpine
ports:
- 6379:6379
steps:
- name: Step 1
uses: ...
- name: Step 2
uses: ...
```
and add own docker-based app containers (from aws, google, heroku... whatever) passing credentials like:
```
...
services:
.....
some-aws-service:
image: XXXXXXXXX.YYY.ecr.eu-west-1.amazonaws.com/<AWS OWN SERVICE>:latest
ports:
- 5000:5000
credentials:
username: ${{ secrets.AWS_ACCESS_KEY_ID }}
password: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
```
Following multiple approaches like proposed (here:)[https://docs.github.com/es/actions/using-jobs/running-jobs-in-a-container]
But I receive this:
I also added these (steps)[https://github.com/aws-actions/amazon-ecr-login] at the begining:
```
- name: Configure AWS credentials
uses: aws-actions/configure-aws-credentials@v1
with:
role-to-assume: arn:aws:iam::123456789012:role/my-github-actions-role
aws-region: us-east-1
- name: Login to Amazon ECR Private
id: login-ecr
uses: aws-actions/amazon-ecr-login@v1
...
```
But nothing was possible...
Can you shed more light on this please?
Many thanks in advance!!!! | non_priority | possible to just use and deploy containers for my github aciton environment from aws not to push if not pull hi community i would like to ask for a feature or in case of me missing this feature please help me to see how to proceed when deploying actions in github ci basically i dont find any info about how to pull containers from aws and deploy them in ci github actions during the job execution jobs backend job name ci backend integration env runs on ubuntu latest services postgres image postgres ports rabbitmq image rabbitmq ports redis image redis alpine ports steps name step uses name step uses and add own docker based app containers from aws google heroku whatever passing credentials like services some aws service image xxxxxxxxx yyy ecr eu west amazonaws com latest ports credentials username secrets aws access key id password secrets aws secret access key following multiple approaches like proposed here but i receive this i also added these steps at the begining name configure aws credentials uses aws actions configure aws credentials with role to assume arn aws iam role my github actions role aws region us east name login to amazon ecr private id login ecr uses aws actions amazon ecr login but nothing was possible can you shed more light on this please many thanks in advance | 0 |
65,559 | 12,620,375,627 | IssuesEvent | 2020-06-13 06:21:01 | fabianschuiki/moore | https://api.github.com/repos/fabianschuiki/moore | opened | Canonicalize param env before codegen | A-codegen C-enhancement L-vlog | Codegen currently uses the `ParamEnv` to determine if two modules have the same parametrization. However, since most parameters are indirectly bound, i.e., they depend on outer parameters, these param envs look distinct in many cases, even though they will resolve to the exact same parametrization. To fix this, codegen should "canonicalize" the param envs, which would mean going through the param env data, converting each binding to a `Direct` one with the concrete value/type, and interning this as new param env. Then use this canonical param env for code generation.
## Todo
- [ ] Create a `canonical_param_type` and `canonical_param_value` query, which resolves *one* param
- [ ] Create a `canonical_param_env` query which creates a canonicalized param env
- [ ] Use the above in codegen before emitting a module | 1.0 | Canonicalize param env before codegen - Codegen currently uses the `ParamEnv` to determine if two modules have the same parametrization. However, since most parameters are indirectly bound, i.e., they depend on outer parameters, these param envs look distinct in many cases, even though they will resolve to the exact same parametrization. To fix this, codegen should "canonicalize" the param envs, which would mean going through the param env data, converting each binding to a `Direct` one with the concrete value/type, and interning this as new param env. Then use this canonical param env for code generation.
## Todo
- [ ] Create a `canonical_param_type` and `canonical_param_value` query, which resolves *one* param
- [ ] Create a `canonical_param_env` query which creates a canonicalized param env
- [ ] Use the above in codegen before emitting a module | non_priority | canonicalize param env before codegen codegen currently uses the paramenv to determine if two modules have the same parametrization however since most parameters are indirectly bound i e they depend on outer parameters these param envs look distinct in many cases even though they will resolve to the exact same parametrization to fix this codegen should canonicalize the param envs which would mean going through the param env data converting each binding to a direct one with the concrete value type and interning this as new param env then use this canonical param env for code generation todo create a canonical param type and canonical param value query which resolves one param create a canonical param env query which creates a canonicalized param env use the above in codegen before emitting a module | 0 |
69,773 | 17,851,584,532 | IssuesEvent | 2021-09-04 06:46:52 | spack/spack | https://api.github.com/repos/spack/spack | opened | Installation issue: motif | build-error | ### Steps to reproduce the issue
```console
spack install motif
```
### Information on your system
Ubuntu 20.04 LTS (x86_64)
* **Spack:** 0.16.2-4144-536121cadf
* **Python:** 3.8.10
* **Platform:** linux-ubuntu20.04-skylake
* **Concretizer:** original
### Additional information
cc main authors of the package: @briedel @awacha
cc original reporter: @WeiqunZhang
Linker error in motif build:
```
3903 libtool: link: /home/axel/src/spack/lib/spack/env/gcc/gcc -g -O2 -Wall -g -fno-strict-a
liasing -Wno-unused -Wno-comment -I/home/axel/src/spack/opt/spack/linux-ubuntu20.04-sky
lake/gcc-10.2.0/libxft-2.3.2-nuuvhnzngtgz7s2vdf2ixyhenvmiy7qf/include -I/home/axel/src/
spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/xproto-7.0.31-yyo45uhkk7ch6zvamphv
5rqwgj26wxbr/include -I/home/axel/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.
2.0/libxrender-0.9.10-imrlx4fnuyzvsn7fx6wvlzm7czkd7uxx/include -I/home/axel/src/spack/o
pt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/renderproto-0.11.1-djhcvvzwy5zoivcwgr7y62
erldjk663j/include -I/home/axel/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.
0/libx11-1.7.0-jucmd7qpodrjnctzb6ypsqxoqaps46nl/include -I/home/axel/src/spack/opt/spac
k/linux-ubuntu20.04-skylake/gcc-10.2.0/kbproto-1.0.7-v6kpza23webuf7rgqfzicdbaetcdgazi/i
nclude -I/home/axel/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/libxcb-1.1
4-fxydy3ldygwt62nh7fi6rtcvteqfzrgw/include -I/home/axel/src/spack/opt/spack/linux-ubunt
u20.04-skylake/gcc-10.2.0/libxau-1.0.8-wv2mjdy5lj37m3n5verrvesyooewhwrd/include -I/home
/axel/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/libxdmcp-1.1.2-tt6cnuxna
rpibaa23g3ft7sbu7w5ms3z/include -I/home/axel/src/spack/opt/spack/linux-ubuntu20.04-skyl
ake/gcc-10.2.0/fontconfig-2.13.93-kf3f432efaqjpvsjjoi25asd4eyabr3f/include -I/home/axel
/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/freetype-2.11.0-bsncivagqvyzg
ltvlzepwhabocx27gya/include/freetype2 -I/home/axel/src/spack/opt/spack/linux-ubuntu20.0
4-skylake/gcc-10.2.0/zlib-1.2.11-ic4fxjxrxsg3kfkhv33o7crpwbcrivdx/include -I/home/axel/
src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/libpng-1.6.37-uo6zzvy3q34yiqbh
77gzdpqty4dvcziy/include/libpng16 -I/home/axel/src/spack/opt/spack/linux-ubuntu20.04-sk
ylake/gcc-10.2.0/libxml2-2.9.12-bbzpoynrstvz5keau2o5clwjbtb3sjo3/include/libxml2 -I/hom
e/axel/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/libiconv-1.16-xkkjjzazq
oxfigndvrk3wgpub3cba2os/include -I/home/axel/src/spack/opt/spack/linux-ubuntu20.04-skyl
ake/gcc-10.2.0/xbitmaps-1.1.1-2jo4l4uqemkhizqjaq3bqnf5xs7mg5hg/include -o .libs/simpleD
emo simpleDemo.o ../../../../lib/Xm/.libs/libXm.so -L/home/axel/src/spack/opt/spack/li
nux-ubuntu20.04-skylake/gcc-10.2.0/fontconfig-2.13.93-kf3f432efaqjpvsjjoi25asd4eyabr3f/
lib -L/home/axel/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/freetype-2.11
.0-bsncivagqvyzgltvlzepwhabocx27gya/lib -L/home/axel/src/spack/opt/spack/linux-ubuntu20
.04-skylake/gcc-10.2.0/libxft-2.3.2-nuuvhnzngtgz7s2vdf2ixyhenvmiy7qf/lib -lXt -lXext -l
X11 ../../../lib/Exm/libExm.a -lfontconfig -lfreetype -lXft -ljpeg -lpng -Wl,-rpath -Wl
,/home/axel/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/motif-2.3.8-wbz3cf
bbpoa5owyf5imcddbmnyyuwc7i/lib
>> 3904 /usr/bin/ld: ../../../../lib/Xm/.libs/libXm.so: undefined reference to symbol 'XFillArc
'
>> 3905 /usr/bin/ld: /home/axel/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/libx11
-1.7.0-jucmd7qpodrjnctzb6ypsqxoqaps46nl/lib/libX11.so: error adding symbols: DSO missin
g from command line
>> 3906 collect2: error: ld returned 1 exit status
```
* [spack-build-env.txt](https://github.com/spack/spack/files/7109332/spack-build-env.txt)
* [spack-build-out.txt](https://github.com/spack/spack/files/7109333/spack-build-out.txt)
### General information
- [X] I have run `spack debug report` and reported the version of Spack/Python/Platform
- [X] I have run `spack maintainers <name-of-the-package>` and **@mentioned** any maintainers
- [X] I have uploaded the build log and environment files
- [X] I have searched the issues of this repo and believe this is not a duplicate | 1.0 | Installation issue: motif - ### Steps to reproduce the issue
```console
spack install motif
```
### Information on your system
Ubuntu 20.04 LTS (x86_64)
* **Spack:** 0.16.2-4144-536121cadf
* **Python:** 3.8.10
* **Platform:** linux-ubuntu20.04-skylake
* **Concretizer:** original
### Additional information
cc main authors of the package: @briedel @awacha
cc original reporter: @WeiqunZhang
Linker error in motif build:
```
3903 libtool: link: /home/axel/src/spack/lib/spack/env/gcc/gcc -g -O2 -Wall -g -fno-strict-a
liasing -Wno-unused -Wno-comment -I/home/axel/src/spack/opt/spack/linux-ubuntu20.04-sky
lake/gcc-10.2.0/libxft-2.3.2-nuuvhnzngtgz7s2vdf2ixyhenvmiy7qf/include -I/home/axel/src/
spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/xproto-7.0.31-yyo45uhkk7ch6zvamphv
5rqwgj26wxbr/include -I/home/axel/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.
2.0/libxrender-0.9.10-imrlx4fnuyzvsn7fx6wvlzm7czkd7uxx/include -I/home/axel/src/spack/o
pt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/renderproto-0.11.1-djhcvvzwy5zoivcwgr7y62
erldjk663j/include -I/home/axel/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.
0/libx11-1.7.0-jucmd7qpodrjnctzb6ypsqxoqaps46nl/include -I/home/axel/src/spack/opt/spac
k/linux-ubuntu20.04-skylake/gcc-10.2.0/kbproto-1.0.7-v6kpza23webuf7rgqfzicdbaetcdgazi/i
nclude -I/home/axel/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/libxcb-1.1
4-fxydy3ldygwt62nh7fi6rtcvteqfzrgw/include -I/home/axel/src/spack/opt/spack/linux-ubunt
u20.04-skylake/gcc-10.2.0/libxau-1.0.8-wv2mjdy5lj37m3n5verrvesyooewhwrd/include -I/home
/axel/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/libxdmcp-1.1.2-tt6cnuxna
rpibaa23g3ft7sbu7w5ms3z/include -I/home/axel/src/spack/opt/spack/linux-ubuntu20.04-skyl
ake/gcc-10.2.0/fontconfig-2.13.93-kf3f432efaqjpvsjjoi25asd4eyabr3f/include -I/home/axel
/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/freetype-2.11.0-bsncivagqvyzg
ltvlzepwhabocx27gya/include/freetype2 -I/home/axel/src/spack/opt/spack/linux-ubuntu20.0
4-skylake/gcc-10.2.0/zlib-1.2.11-ic4fxjxrxsg3kfkhv33o7crpwbcrivdx/include -I/home/axel/
src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/libpng-1.6.37-uo6zzvy3q34yiqbh
77gzdpqty4dvcziy/include/libpng16 -I/home/axel/src/spack/opt/spack/linux-ubuntu20.04-sk
ylake/gcc-10.2.0/libxml2-2.9.12-bbzpoynrstvz5keau2o5clwjbtb3sjo3/include/libxml2 -I/hom
e/axel/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/libiconv-1.16-xkkjjzazq
oxfigndvrk3wgpub3cba2os/include -I/home/axel/src/spack/opt/spack/linux-ubuntu20.04-skyl
ake/gcc-10.2.0/xbitmaps-1.1.1-2jo4l4uqemkhizqjaq3bqnf5xs7mg5hg/include -o .libs/simpleD
emo simpleDemo.o ../../../../lib/Xm/.libs/libXm.so -L/home/axel/src/spack/opt/spack/li
nux-ubuntu20.04-skylake/gcc-10.2.0/fontconfig-2.13.93-kf3f432efaqjpvsjjoi25asd4eyabr3f/
lib -L/home/axel/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/freetype-2.11
.0-bsncivagqvyzgltvlzepwhabocx27gya/lib -L/home/axel/src/spack/opt/spack/linux-ubuntu20
.04-skylake/gcc-10.2.0/libxft-2.3.2-nuuvhnzngtgz7s2vdf2ixyhenvmiy7qf/lib -lXt -lXext -l
X11 ../../../lib/Exm/libExm.a -lfontconfig -lfreetype -lXft -ljpeg -lpng -Wl,-rpath -Wl
,/home/axel/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/motif-2.3.8-wbz3cf
bbpoa5owyf5imcddbmnyyuwc7i/lib
>> 3904 /usr/bin/ld: ../../../../lib/Xm/.libs/libXm.so: undefined reference to symbol 'XFillArc
'
>> 3905 /usr/bin/ld: /home/axel/src/spack/opt/spack/linux-ubuntu20.04-skylake/gcc-10.2.0/libx11
-1.7.0-jucmd7qpodrjnctzb6ypsqxoqaps46nl/lib/libX11.so: error adding symbols: DSO missin
g from command line
>> 3906 collect2: error: ld returned 1 exit status
```
* [spack-build-env.txt](https://github.com/spack/spack/files/7109332/spack-build-env.txt)
* [spack-build-out.txt](https://github.com/spack/spack/files/7109333/spack-build-out.txt)
### General information
- [X] I have run `spack debug report` and reported the version of Spack/Python/Platform
- [X] I have run `spack maintainers <name-of-the-package>` and **@mentioned** any maintainers
- [X] I have uploaded the build log and environment files
- [X] I have searched the issues of this repo and believe this is not a duplicate | non_priority | installation issue motif steps to reproduce the issue console spack install motif information on your system ubuntu lts spack python platform linux skylake concretizer original additional information cc main authors of the package briedel awacha cc original reporter weiqunzhang linker error in motif build libtool link home axel src spack lib spack env gcc gcc g wall g fno strict a liasing wno unused wno comment i home axel src spack opt spack linux sky lake gcc libxft include i home axel src spack opt spack linux skylake gcc xproto include i home axel src spack opt spack linux skylake gcc libxrender include i home axel src spack o pt spack linux skylake gcc renderproto include i home axel src spack opt spack linux skylake gcc include i home axel src spack opt spac k linux skylake gcc kbproto i nclude i home axel src spack opt spack linux skylake gcc libxcb include i home axel src spack opt spack linux ubunt skylake gcc libxau include i home axel src spack opt spack linux skylake gcc libxdmcp include i home axel src spack opt spack linux skyl ake gcc fontconfig include i home axel src spack opt spack linux skylake gcc freetype bsncivagqvyzg include i home axel src spack opt spack linux skylake gcc zlib include i home axel src spack opt spack linux skylake gcc libpng include i home axel src spack opt spack linux sk ylake gcc include i hom e axel src spack opt spack linux skylake gcc libiconv xkkjjzazq include i home axel src spack opt spack linux skyl ake gcc xbitmaps include o libs simpled emo simpledemo o lib xm libs libxm so l home axel src spack opt spack li nux skylake gcc fontconfig lib l home axel src spack opt spack linux skylake gcc freetype lib l home axel src spack opt spack linux skylake gcc libxft lib lxt lxext l lib exm libexm a lfontconfig lfreetype lxft ljpeg lpng wl rpath wl home axel src spack opt spack linux skylake gcc motif lib usr bin ld lib xm libs libxm so undefined reference to symbol xfillarc usr bin ld home axel src spack opt spack linux skylake gcc lib so error adding symbols dso missin g from command line error ld returned exit status general information i have run spack debug report and reported the version of spack python platform i have run spack maintainers and mentioned any maintainers i have uploaded the build log and environment files i have searched the issues of this repo and believe this is not a duplicate | 0 |
139,662 | 12,877,676,761 | IssuesEvent | 2020-07-11 12:31:04 | toolisticon/jgiven-addons | https://api.github.com/repos/toolisticon/jgiven-addons | opened | provide better docs | documentation | The readme should provide information how to use the library (include coordinates for both gradle and maven) | 1.0 | provide better docs - The readme should provide information how to use the library (include coordinates for both gradle and maven) | non_priority | provide better docs the readme should provide information how to use the library include coordinates for both gradle and maven | 0 |
337,644 | 30,252,882,090 | IssuesEvent | 2023-07-06 22:21:10 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | jobs: TestJobInfoUpgradeRegressionTests failed | C-test-failure O-robot branch-master T-disaster-recovery T-jobs | jobs.TestJobInfoUpgradeRegressionTests [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/10810911?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/10810911?buildTab=artifacts#/) on master @ [818aec861357579eb3a3e987cf5887f3cf112be4](https://github.com/cockroachdb/cockroach/commits/818aec861357579eb3a3e987cf5887f3cf112be4):
```
I230706 22:11:07.395057 1840 upgrade/upgradecluster/cluster.go:121 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1767 executing bump-cluster-version=1000022.2-77(fence) on nodes n{1}
I230706 22:11:07.404103 16892 server/migration.go:150 [T1,n1,bump-cluster-version] 1768 active cluster version setting is now 1000022.2-77(fence) (up from 1000022.2-76)
I230706 22:11:07.404575 1840 upgrade/upgrademanager/manager.go:657 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1769 executing operation validate-cluster-version=1000022.2-78
I230706 22:11:07.404985 1840 upgrade/upgradecluster/cluster.go:121 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1770 executing validate-cluster-version=1000022.2-78 on nodes n{1}
I230706 22:11:07.406167 1840 upgrade/upgrademanager/manager.go:657 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1771 executing operation bump-cluster-version=1000022.2-78
I230706 22:11:07.406594 1840 upgrade/upgradecluster/cluster.go:121 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1772 executing bump-cluster-version=1000022.2-78 on nodes n{1}
I230706 22:11:07.406999 16897 server/migration.go:150 [T1,n1,bump-cluster-version] 1773 active cluster version setting is now 1000022.2-78 (up from 1000022.2-77(fence))
I230706 22:11:07.421796 1840 upgrade/upgrademanager/manager.go:517 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1774 stepping through 1000022.2-80
I230706 22:11:07.421963 1840 upgrade/upgrademanager/manager.go:657 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1775 executing operation bump-cluster-version=1000022.2-79(fence)
I230706 22:11:07.422398 1840 upgrade/upgradecluster/cluster.go:121 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1776 executing bump-cluster-version=1000022.2-79(fence) on nodes n{1}
I230706 22:11:07.423272 16939 server/migration.go:150 [T1,n1,bump-cluster-version] 1777 active cluster version setting is now 1000022.2-79(fence) (up from 1000022.2-78)
I230706 22:11:07.424778 1840 upgrade/upgrademanager/manager.go:657 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1778 executing operation validate-cluster-version=1000022.2-80
I230706 22:11:07.425030 1840 upgrade/upgradecluster/cluster.go:121 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1779 executing validate-cluster-version=1000022.2-80 on nodes n{1}
I230706 22:11:07.450150 16863 jobs/adopt.go:261 [T1,n1] 1781 job 880184745739550721: resuming execution
I230706 22:11:07.448976 1840 upgrade/upgrademanager/manager.go:742 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1780 running Upgrade to 1000022.2-80: "backfill the system.job_info table with the payload and progress of each job in the system.jobs table"
I230706 22:11:07.457530 16865 jobs/registry.go:1606 [T1,n1] 1782 MIGRATION job 880184745739550721: stepping through state running
I230706 22:11:07.547964 16865 upgrade/upgrades/backfill_job_info_table_migration.go:81 [T1,n1,job=MIGRATION id=880184745739550721,upgrade=1000022.2-80] 1783 backfilling job_info, step0, batch0 done; resume after 0, done false
I230706 22:11:07.551043 16865 upgrade/upgrades/backfill_job_info_table_migration.go:81 [T1,n1,job=MIGRATION id=880184745739550721,upgrade=1000022.2-80] 1784 backfilling job_info, step0, batch1 done; resume after 880184745739550721, done true
I230706 22:11:07.632088 16865 upgrade/upgrades/backfill_job_info_table_migration.go:81 [T1,n1,job=MIGRATION id=880184745739550721,upgrade=1000022.2-80] 1785 backfilling job_info, step1, batch0 done; resume after 0, done false
I230706 22:11:07.649981 16865 upgrade/upgrades/backfill_job_info_table_migration.go:81 [T1,n1,job=MIGRATION id=880184745739550721,upgrade=1000022.2-80] 1786 backfilling job_info, step1, batch1 done; resume after 880184745739550721, done true
I230706 22:11:07.651325 16865 jobs/registry.go:1606 [T1,n1] 1787 MIGRATION job 880184745739550721: stepping through state succeeded
I230706 22:11:07.662184 1840 jobs/wait.go:145 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1788 waited for 1 [880184745739550721] queued jobs to complete 210.019003ms
I230706 22:11:07.662257 1840 upgrade/upgrademanager/manager.go:657 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1789 executing operation bump-cluster-version=1000022.2-80
I230706 22:11:07.662566 1840 upgrade/upgradecluster/cluster.go:121 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1790 executing bump-cluster-version=1000022.2-80 on nodes n{1}
I230706 22:11:07.662831 17135 server/migration.go:150 [T1,n1,bump-cluster-version] 1791 active cluster version setting is now 1000022.2-80 (up from 1000022.2-79(fence))
I230706 22:11:07.667852 1840 util/log/event_log.go:32 [T1,n1,client=127.0.0.1:41314,hostssl,user=root] 1792 ={"Timestamp":1688681461014926435,"EventType":"set_cluster_setting","Statement":"SET CLUSTER SETTING version = $1","Tag":"SET CLUSTER SETTING","User":"root","PlaceholderValues":["'1000022.2-80'"],"SettingName":"version","Value":"1000022.2-80"}
job_info_storage_test.go:366: query 'SELECT count(*) FROM crdb_internal.system_jobs WHERE job_type = 'BACKUP'': expected:
1
got:
0
W230706 22:11:07.756134 17097 kv/kvserver/intentresolver/intent_resolver.go:826 [-] 1793 failed to gc transaction record: could not GC completed transaction anchored at /Table/6/1/"version"/0: node unavailable; try another peer
I230706 22:11:07.756204 900 sql/stats/automatic_stats.go:572 [T1,n1] 1794 quiescing auto stats refresher
I230706 22:11:07.756382 10921 jobs/registry.go:1606 [T1,n1] 1795 KEY VISUALIZER job 100: stepping through state succeeded
W230706 22:11:07.758610 10921 jobs/adopt.go:531 [T1,n1] 1796 could not clear job claim: clear-job-claim: failed to send RPC: sending to all replicas failed; last error: ba: Scan [/Table/15/1/100,/Table/15/1/101), [txn: cac76053], [can-forward-ts] RPC error: node unavailable; try another peer
I230706 22:11:07.759080 901 sql/stats/automatic_stats.go:624 [T1,n1] 1797 quiescing stats garbage collector
I230706 22:11:07.759309 373 server/start_listen.go:103 [T1,n1] 1798 server shutting down: instructing cmux to stop accepting
I230706 22:11:07.762217 9363 jobs/registry.go:1606 [T1,n1] 1799 AUTO SPAN CONFIG RECONCILIATION job 880184732354183169: stepping through state succeeded
W230706 22:11:07.762427 11268 jobs/adopt.go:531 [T1,n1] 1800 could not clear job claim: clear-job-claim: node unavailable; try another peer
W230706 22:11:07.762529 650 sql/sqlliveness/slinstance/slinstance.go:334 [T1,n1] 1801 exiting heartbeat loop
W230706 22:11:07.764876 650 sql/sqlliveness/slinstance/slinstance.go:321 [T1,n1] 1804 exiting heartbeat loop with error: node unavailable; try another peer
I230706 22:11:07.762669 977 jobs/registry.go:1606 [T1,n1] 1802 AUTO SPAN CONFIG RECONCILIATION job 880184715132862465: stepping through state succeeded
W230706 22:11:07.764785 9363 jobs/adopt.go:531 [T1,n1] 1803 could not clear job claim: clear-job-claim: node unavailable; try another peer
E230706 22:11:07.765004 650 server/server_sql.go:514 [T1,n1] 1805 failed to run update of instance with new session ID: node unavailable; try another peer
E230706 22:11:07.765174 977 jobs/registry.go:1004 [T1,n1] 1806 error getting live session: node unavailable; try another peer
I230706 22:11:07.768845 58 server/server_controller_orchestration.go:263 [T1,n1] 1807 server controller shutting down ungracefully
I230706 22:11:07.769028 58 server/server_controller_orchestration.go:274 [T1,n1] 1808 waiting for tenant servers to report stopped
W230706 22:11:07.769212 58 server/server_sql.go:1712 [T1,n1] 1809 server shutdown without a prior graceful drain
--- FAIL: TestJobInfoUpgradeRegressionTests (9.81s)
```
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>
- #106246 jobs: TestJobInfoUpgradeRegressionTests failed [C-test-failure O-robot T-jobs branch-release-23.1]
</p>
</details>
/cc @cockroachdb/jobs @cockroachdb/disaster-recovery
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestJobInfoUpgradeRegressionTests.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 1.0 | jobs: TestJobInfoUpgradeRegressionTests failed - jobs.TestJobInfoUpgradeRegressionTests [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/10810911?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/10810911?buildTab=artifacts#/) on master @ [818aec861357579eb3a3e987cf5887f3cf112be4](https://github.com/cockroachdb/cockroach/commits/818aec861357579eb3a3e987cf5887f3cf112be4):
```
I230706 22:11:07.395057 1840 upgrade/upgradecluster/cluster.go:121 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1767 executing bump-cluster-version=1000022.2-77(fence) on nodes n{1}
I230706 22:11:07.404103 16892 server/migration.go:150 [T1,n1,bump-cluster-version] 1768 active cluster version setting is now 1000022.2-77(fence) (up from 1000022.2-76)
I230706 22:11:07.404575 1840 upgrade/upgrademanager/manager.go:657 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1769 executing operation validate-cluster-version=1000022.2-78
I230706 22:11:07.404985 1840 upgrade/upgradecluster/cluster.go:121 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1770 executing validate-cluster-version=1000022.2-78 on nodes n{1}
I230706 22:11:07.406167 1840 upgrade/upgrademanager/manager.go:657 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1771 executing operation bump-cluster-version=1000022.2-78
I230706 22:11:07.406594 1840 upgrade/upgradecluster/cluster.go:121 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1772 executing bump-cluster-version=1000022.2-78 on nodes n{1}
I230706 22:11:07.406999 16897 server/migration.go:150 [T1,n1,bump-cluster-version] 1773 active cluster version setting is now 1000022.2-78 (up from 1000022.2-77(fence))
I230706 22:11:07.421796 1840 upgrade/upgrademanager/manager.go:517 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1774 stepping through 1000022.2-80
I230706 22:11:07.421963 1840 upgrade/upgrademanager/manager.go:657 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1775 executing operation bump-cluster-version=1000022.2-79(fence)
I230706 22:11:07.422398 1840 upgrade/upgradecluster/cluster.go:121 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1776 executing bump-cluster-version=1000022.2-79(fence) on nodes n{1}
I230706 22:11:07.423272 16939 server/migration.go:150 [T1,n1,bump-cluster-version] 1777 active cluster version setting is now 1000022.2-79(fence) (up from 1000022.2-78)
I230706 22:11:07.424778 1840 upgrade/upgrademanager/manager.go:657 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1778 executing operation validate-cluster-version=1000022.2-80
I230706 22:11:07.425030 1840 upgrade/upgradecluster/cluster.go:121 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1779 executing validate-cluster-version=1000022.2-80 on nodes n{1}
I230706 22:11:07.450150 16863 jobs/adopt.go:261 [T1,n1] 1781 job 880184745739550721: resuming execution
I230706 22:11:07.448976 1840 upgrade/upgrademanager/manager.go:742 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1780 running Upgrade to 1000022.2-80: "backfill the system.job_info table with the payload and progress of each job in the system.jobs table"
I230706 22:11:07.457530 16865 jobs/registry.go:1606 [T1,n1] 1782 MIGRATION job 880184745739550721: stepping through state running
I230706 22:11:07.547964 16865 upgrade/upgrades/backfill_job_info_table_migration.go:81 [T1,n1,job=MIGRATION id=880184745739550721,upgrade=1000022.2-80] 1783 backfilling job_info, step0, batch0 done; resume after 0, done false
I230706 22:11:07.551043 16865 upgrade/upgrades/backfill_job_info_table_migration.go:81 [T1,n1,job=MIGRATION id=880184745739550721,upgrade=1000022.2-80] 1784 backfilling job_info, step0, batch1 done; resume after 880184745739550721, done true
I230706 22:11:07.632088 16865 upgrade/upgrades/backfill_job_info_table_migration.go:81 [T1,n1,job=MIGRATION id=880184745739550721,upgrade=1000022.2-80] 1785 backfilling job_info, step1, batch0 done; resume after 0, done false
I230706 22:11:07.649981 16865 upgrade/upgrades/backfill_job_info_table_migration.go:81 [T1,n1,job=MIGRATION id=880184745739550721,upgrade=1000022.2-80] 1786 backfilling job_info, step1, batch1 done; resume after 880184745739550721, done true
I230706 22:11:07.651325 16865 jobs/registry.go:1606 [T1,n1] 1787 MIGRATION job 880184745739550721: stepping through state succeeded
I230706 22:11:07.662184 1840 jobs/wait.go:145 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1788 waited for 1 [880184745739550721] queued jobs to complete 210.019003ms
I230706 22:11:07.662257 1840 upgrade/upgrademanager/manager.go:657 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1789 executing operation bump-cluster-version=1000022.2-80
I230706 22:11:07.662566 1840 upgrade/upgradecluster/cluster.go:121 [T1,n1,client=127.0.0.1:41314,hostssl,user=root,migration-mgr] 1790 executing bump-cluster-version=1000022.2-80 on nodes n{1}
I230706 22:11:07.662831 17135 server/migration.go:150 [T1,n1,bump-cluster-version] 1791 active cluster version setting is now 1000022.2-80 (up from 1000022.2-79(fence))
I230706 22:11:07.667852 1840 util/log/event_log.go:32 [T1,n1,client=127.0.0.1:41314,hostssl,user=root] 1792 ={"Timestamp":1688681461014926435,"EventType":"set_cluster_setting","Statement":"SET CLUSTER SETTING version = $1","Tag":"SET CLUSTER SETTING","User":"root","PlaceholderValues":["'1000022.2-80'"],"SettingName":"version","Value":"1000022.2-80"}
job_info_storage_test.go:366: query 'SELECT count(*) FROM crdb_internal.system_jobs WHERE job_type = 'BACKUP'': expected:
1
got:
0
W230706 22:11:07.756134 17097 kv/kvserver/intentresolver/intent_resolver.go:826 [-] 1793 failed to gc transaction record: could not GC completed transaction anchored at /Table/6/1/"version"/0: node unavailable; try another peer
I230706 22:11:07.756204 900 sql/stats/automatic_stats.go:572 [T1,n1] 1794 quiescing auto stats refresher
I230706 22:11:07.756382 10921 jobs/registry.go:1606 [T1,n1] 1795 KEY VISUALIZER job 100: stepping through state succeeded
W230706 22:11:07.758610 10921 jobs/adopt.go:531 [T1,n1] 1796 could not clear job claim: clear-job-claim: failed to send RPC: sending to all replicas failed; last error: ba: Scan [/Table/15/1/100,/Table/15/1/101), [txn: cac76053], [can-forward-ts] RPC error: node unavailable; try another peer
I230706 22:11:07.759080 901 sql/stats/automatic_stats.go:624 [T1,n1] 1797 quiescing stats garbage collector
I230706 22:11:07.759309 373 server/start_listen.go:103 [T1,n1] 1798 server shutting down: instructing cmux to stop accepting
I230706 22:11:07.762217 9363 jobs/registry.go:1606 [T1,n1] 1799 AUTO SPAN CONFIG RECONCILIATION job 880184732354183169: stepping through state succeeded
W230706 22:11:07.762427 11268 jobs/adopt.go:531 [T1,n1] 1800 could not clear job claim: clear-job-claim: node unavailable; try another peer
W230706 22:11:07.762529 650 sql/sqlliveness/slinstance/slinstance.go:334 [T1,n1] 1801 exiting heartbeat loop
W230706 22:11:07.764876 650 sql/sqlliveness/slinstance/slinstance.go:321 [T1,n1] 1804 exiting heartbeat loop with error: node unavailable; try another peer
I230706 22:11:07.762669 977 jobs/registry.go:1606 [T1,n1] 1802 AUTO SPAN CONFIG RECONCILIATION job 880184715132862465: stepping through state succeeded
W230706 22:11:07.764785 9363 jobs/adopt.go:531 [T1,n1] 1803 could not clear job claim: clear-job-claim: node unavailable; try another peer
E230706 22:11:07.765004 650 server/server_sql.go:514 [T1,n1] 1805 failed to run update of instance with new session ID: node unavailable; try another peer
E230706 22:11:07.765174 977 jobs/registry.go:1004 [T1,n1] 1806 error getting live session: node unavailable; try another peer
I230706 22:11:07.768845 58 server/server_controller_orchestration.go:263 [T1,n1] 1807 server controller shutting down ungracefully
I230706 22:11:07.769028 58 server/server_controller_orchestration.go:274 [T1,n1] 1808 waiting for tenant servers to report stopped
W230706 22:11:07.769212 58 server/server_sql.go:1712 [T1,n1] 1809 server shutdown without a prior graceful drain
--- FAIL: TestJobInfoUpgradeRegressionTests (9.81s)
```
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>
- #106246 jobs: TestJobInfoUpgradeRegressionTests failed [C-test-failure O-robot T-jobs branch-release-23.1]
</p>
</details>
/cc @cockroachdb/jobs @cockroachdb/disaster-recovery
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestJobInfoUpgradeRegressionTests.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| non_priority | jobs testjobinfoupgraderegressiontests failed jobs testjobinfoupgraderegressiontests with on master upgrade upgradecluster cluster go executing bump cluster version fence on nodes n server migration go active cluster version setting is now fence up from upgrade upgrademanager manager go executing operation validate cluster version upgrade upgradecluster cluster go executing validate cluster version on nodes n upgrade upgrademanager manager go executing operation bump cluster version upgrade upgradecluster cluster go executing bump cluster version on nodes n server migration go active cluster version setting is now up from fence upgrade upgrademanager manager go stepping through upgrade upgrademanager manager go executing operation bump cluster version fence upgrade upgradecluster cluster go executing bump cluster version fence on nodes n server migration go active cluster version setting is now fence up from upgrade upgrademanager manager go executing operation validate cluster version upgrade upgradecluster cluster go executing validate cluster version on nodes n jobs adopt go job resuming execution upgrade upgrademanager manager go running upgrade to backfill the system job info table with the payload and progress of each job in the system jobs table jobs registry go migration job stepping through state running upgrade upgrades backfill job info table migration go backfilling job info done resume after done false upgrade upgrades backfill job info table migration go backfilling job info done resume after done true upgrade upgrades backfill job info table migration go backfilling job info done resume after done false upgrade upgrades backfill job info table migration go backfilling job info done resume after done true jobs registry go migration job stepping through state succeeded jobs wait go waited for queued jobs to complete upgrade upgrademanager manager go executing operation bump cluster version upgrade upgradecluster cluster go executing bump cluster version on nodes n server migration go active cluster version setting is now up from fence util log event log go timestamp eventtype set cluster setting statement set cluster setting version tag set cluster setting user root placeholdervalues settingname version value job info storage test go query select count from crdb internal system jobs where job type backup expected got kv kvserver intentresolver intent resolver go failed to gc transaction record could not gc completed transaction anchored at table version node unavailable try another peer sql stats automatic stats go quiescing auto stats refresher jobs registry go key visualizer job stepping through state succeeded jobs adopt go could not clear job claim clear job claim failed to send rpc sending to all replicas failed last error ba scan rpc error node unavailable try another peer sql stats automatic stats go quiescing stats garbage collector server start listen go server shutting down instructing cmux to stop accepting jobs registry go auto span config reconciliation job stepping through state succeeded jobs adopt go could not clear job claim clear job claim node unavailable try another peer sql sqlliveness slinstance slinstance go exiting heartbeat loop sql sqlliveness slinstance slinstance go exiting heartbeat loop with error node unavailable try another peer jobs registry go auto span config reconciliation job stepping through state succeeded jobs adopt go could not clear job claim clear job claim node unavailable try another peer server server sql go failed to run update of instance with new session id node unavailable try another peer jobs registry go error getting live session node unavailable try another peer server server controller orchestration go server controller shutting down ungracefully server server controller orchestration go waiting for tenant servers to report stopped server server sql go server shutdown without a prior graceful drain fail testjobinfoupgraderegressiontests help see also same failure on other branches jobs testjobinfoupgraderegressiontests failed cc cockroachdb jobs cockroachdb disaster recovery | 0 |
296,716 | 25,571,714,966 | IssuesEvent | 2022-11-30 18:14:39 | MD-Anderson-Bioinformatics/NG-CHM | https://api.github.com/repos/MD-Anderson-Bioinformatics/NG-CHM | closed | Expand pane doesn't take pane resizes while collapsed into account when redrawing expanded pane. | bug ready-for-testing 2.23.0 | To recreate:
Open map with two default panes.
Below left pane open new pane.
Set new pane to detail map.
Collapse new pane.
Grab resize bar in middle of screen and drag it left.
Expand hidden pane.
New pane will overwrite area of right pane by amount the resize bar was moved.
| 1.0 | Expand pane doesn't take pane resizes while collapsed into account when redrawing expanded pane. - To recreate:
Open map with two default panes.
Below left pane open new pane.
Set new pane to detail map.
Collapse new pane.
Grab resize bar in middle of screen and drag it left.
Expand hidden pane.
New pane will overwrite area of right pane by amount the resize bar was moved.
| non_priority | expand pane doesn t take pane resizes while collapsed into account when redrawing expanded pane to recreate open map with two default panes below left pane open new pane set new pane to detail map collapse new pane grab resize bar in middle of screen and drag it left expand hidden pane new pane will overwrite area of right pane by amount the resize bar was moved | 0 |
224,768 | 17,774,173,602 | IssuesEvent | 2021-08-30 17:00:18 | getodk/collect | https://api.github.com/repos/getodk/collect | closed | Three OkHttpOpenRosaServerClientProviderTest fail under some circumstances | testing | There are 4 `OkHttpOpenRosaServerClientProviderTest` that use `MockWebServer`. Three of them fail for some configurations. I can get them to fail when running `./gradlew testDebugUnitTest` but not when running from Android Studio.
Changing `httpsMockWebServer.start(8443)` to `httpsMockWebServer.start()` in the mock makes the tests pass but it points to a possible cleanup issue that would be good to understand and fix.
```
java.net.ConnectException: Failed to connect to localhost/0:0:0:0:0:0:0:1:8443
at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:249)
at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:167)
at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:258)
at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:135)
at okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:114)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:127)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at com.burgstaller.okhttp.AuthenticationCacheInterceptor.intercept(AuthenticationCacheInterceptor.java:50)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:250)
at okhttp3.RealCall.execute(RealCall.java:93)
at org.odk.collect.android.http.openrosa.okhttp.OkHttpOpenRosaServerClientProvider$OkHttpOpenRosaServerClient.makeRequest(OkHttpOpenRosaServerClientProvider.java:105)
at org.odk.collect.android.http.OpenRosaServerClientProviderTest.withCredentials_onceBasicChallenged_whenHttps_proactivelySendsCredentials(OpenRosaServerClientProviderTest.java:149)
```
Slack conversation at https://opendatakit.slack.com/archives/C35ENHA64/p1573167021119600
CC @shouryaj | 1.0 | Three OkHttpOpenRosaServerClientProviderTest fail under some circumstances - There are 4 `OkHttpOpenRosaServerClientProviderTest` that use `MockWebServer`. Three of them fail for some configurations. I can get them to fail when running `./gradlew testDebugUnitTest` but not when running from Android Studio.
Changing `httpsMockWebServer.start(8443)` to `httpsMockWebServer.start()` in the mock makes the tests pass but it points to a possible cleanup issue that would be good to understand and fix.
```
java.net.ConnectException: Failed to connect to localhost/0:0:0:0:0:0:0:1:8443
at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:249)
at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:167)
at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:258)
at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:135)
at okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:114)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:127)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at com.burgstaller.okhttp.AuthenticationCacheInterceptor.intercept(AuthenticationCacheInterceptor.java:50)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:250)
at okhttp3.RealCall.execute(RealCall.java:93)
at org.odk.collect.android.http.openrosa.okhttp.OkHttpOpenRosaServerClientProvider$OkHttpOpenRosaServerClient.makeRequest(OkHttpOpenRosaServerClientProvider.java:105)
at org.odk.collect.android.http.OpenRosaServerClientProviderTest.withCredentials_onceBasicChallenged_whenHttps_proactivelySendsCredentials(OpenRosaServerClientProviderTest.java:149)
```
Slack conversation at https://opendatakit.slack.com/archives/C35ENHA64/p1573167021119600
CC @shouryaj | non_priority | three okhttpopenrosaserverclientprovidertest fail under some circumstances there are okhttpopenrosaserverclientprovidertest that use mockwebserver three of them fail for some configurations i can get them to fail when running gradlew testdebugunittest but not when running from android studio changing httpsmockwebserver start to httpsmockwebserver start in the mock makes the tests pass but it points to a possible cleanup issue that would be good to understand and fix java net connectexception failed to connect to localhost at internal connection realconnection connectsocket realconnection java at internal connection realconnection connect realconnection java at internal connection streamallocation findconnection streamallocation java at internal connection streamallocation findhealthyconnection streamallocation java at internal connection streamallocation newstream streamallocation java at internal connection connectinterceptor intercept connectinterceptor java at internal http realinterceptorchain proceed realinterceptorchain java at internal http realinterceptorchain proceed realinterceptorchain java at internal cache cacheinterceptor intercept cacheinterceptor java at internal http realinterceptorchain proceed realinterceptorchain java at internal http realinterceptorchain proceed realinterceptorchain java at internal http bridgeinterceptor intercept bridgeinterceptor java at internal http realinterceptorchain proceed realinterceptorchain java at internal http retryandfollowupinterceptor intercept retryandfollowupinterceptor java at internal http realinterceptorchain proceed realinterceptorchain java at internal http realinterceptorchain proceed realinterceptorchain java at com burgstaller okhttp authenticationcacheinterceptor intercept authenticationcacheinterceptor java at internal http realinterceptorchain proceed realinterceptorchain java at internal http realinterceptorchain proceed realinterceptorchain java at realcall getresponsewithinterceptorchain realcall java at realcall execute realcall java at org odk collect android http openrosa okhttp okhttpopenrosaserverclientprovider okhttpopenrosaserverclient makerequest okhttpopenrosaserverclientprovider java at org odk collect android http openrosaserverclientprovidertest withcredentials oncebasicchallenged whenhttps proactivelysendscredentials openrosaserverclientprovidertest java slack conversation at cc shouryaj | 0 |
64,192 | 26,641,161,902 | IssuesEvent | 2023-01-25 05:03:56 | hashicorp/terraform-provider-aws | https://api.github.com/repos/hashicorp/terraform-provider-aws | closed | Flaky bug: error waiting for DynamoDB PITR update: unexpected state 'DISABLED', wanted target 'ENABLED' | bug service/dynamodb | ### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
### Terraform CLI and Terraform AWS Provider Version
- terraform CLI: `v1.1.7`
- AWS provider: `v4.8.0`
### Affected Resource(s)
* aws_dynamodb_table
### Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
<details>
<summary>Terraform code (under spoiler due to size)</summary>
```hcl
resource "aws_dynamodb_table" "this" {
name = "elastio-vaults'
billing_mode = "PAY_PER_REQUEST"
point_in_time_recovery {
enabled = true
}
tags = {
"elastio:resource": "true"
}
hash_key = "pk"
range_key = "sk"
attribute {
name = "pk"
type = "S"
}
attribute {
name = "sk"
type = "S"
}
attribute {
name = "gsi1_pk"
type = "S"
}
attribute {
name = "gsi1_sk"
type = "S"
}
attribute {
name = "gsi2_pk"
type = "S"
}
attribute {
name = "gsi2_sk"
type = "S"
}
attribute {
name = "gsi3_pk"
type = "S"
}
attribute {
name = "gsi3_sk"
type = "S"
}
attribute {
name = "gsi4_pk"
type = "S"
}
attribute {
name = "gsi4_sk"
type = "S"
}
attribute {
name = "gsi5_pk"
type = "S"
}
attribute {
name = "gsi5_sk"
type = "S"
}
global_secondary_index {
name = "gsi1"
hash_key = "gsi1_pk"
range_key = "gsi1_sk"
projection_type = "ALL"
}
global_secondary_index {
name = "gsi2"
hash_key = "gsi2_pk"
range_key = "gsi2_sk"
projection_type = "ALL"
}
global_secondary_index {
name = "gsi3"
hash_key = "gsi3_pk"
range_key = "gsi3_sk"
projection_type = "ALL"
}
global_secondary_index {
name = "gsi4"
hash_key = "gsi4_pk"
range_key = "gsi4_sk"
projection_type = "ALL"
}
global_secondary_index {
name = "gsi5"
hash_key = "gsi5_pk"
range_key = "gsi5_sk"
projection_type = "ALL"
}
}
```
</details>
### Debug Output
Unfortunately, there aren't logs with `TF_LOG=debug` available. This bug reproduced only once our CI, where we don't have verbose debug logging enabled because it produces too much output...
The stderr of `terraform apply` :
```
╷
│ Error: error enabling DynamoDB Table (elastio-exp-1653068446-rvolxt-catalog-vaults) point in time recovery: error waiting for DynamoDB PITR update: unexpected state 'DISABLED', wanted target 'ENABLED'. last error: %!s(<nil>)
│
│ with module.catalog_region.aws_dynamodb_table.this,
│ on ../../../modules/catalog/region/dynamodb_table.tf line 4, in resource "aws_dynamodb_table" "this":
│ 4: resource "aws_dynamodb_table" "this" {
│
╵
```
### Expected Behavior
The table should've been deployed without any problems
### Actual Behavior
We run a lot of deployments with terraform on our CI every day, and see a lot of flakiness like this.
However, we enable PITR only in release builds which occur roughly every two weeks.
In this case, it is an error deploying the DynamoDB table, and it reproduced only once.
### Steps to Reproduce
The deployment is clean (it a non-incremental `apply`).
1. `terraform apply` | 1.0 | Flaky bug: error waiting for DynamoDB PITR update: unexpected state 'DISABLED', wanted target 'ENABLED' - ### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
### Terraform CLI and Terraform AWS Provider Version
- terraform CLI: `v1.1.7`
- AWS provider: `v4.8.0`
### Affected Resource(s)
* aws_dynamodb_table
### Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
<details>
<summary>Terraform code (under spoiler due to size)</summary>
```hcl
resource "aws_dynamodb_table" "this" {
name = "elastio-vaults'
billing_mode = "PAY_PER_REQUEST"
point_in_time_recovery {
enabled = true
}
tags = {
"elastio:resource": "true"
}
hash_key = "pk"
range_key = "sk"
attribute {
name = "pk"
type = "S"
}
attribute {
name = "sk"
type = "S"
}
attribute {
name = "gsi1_pk"
type = "S"
}
attribute {
name = "gsi1_sk"
type = "S"
}
attribute {
name = "gsi2_pk"
type = "S"
}
attribute {
name = "gsi2_sk"
type = "S"
}
attribute {
name = "gsi3_pk"
type = "S"
}
attribute {
name = "gsi3_sk"
type = "S"
}
attribute {
name = "gsi4_pk"
type = "S"
}
attribute {
name = "gsi4_sk"
type = "S"
}
attribute {
name = "gsi5_pk"
type = "S"
}
attribute {
name = "gsi5_sk"
type = "S"
}
global_secondary_index {
name = "gsi1"
hash_key = "gsi1_pk"
range_key = "gsi1_sk"
projection_type = "ALL"
}
global_secondary_index {
name = "gsi2"
hash_key = "gsi2_pk"
range_key = "gsi2_sk"
projection_type = "ALL"
}
global_secondary_index {
name = "gsi3"
hash_key = "gsi3_pk"
range_key = "gsi3_sk"
projection_type = "ALL"
}
global_secondary_index {
name = "gsi4"
hash_key = "gsi4_pk"
range_key = "gsi4_sk"
projection_type = "ALL"
}
global_secondary_index {
name = "gsi5"
hash_key = "gsi5_pk"
range_key = "gsi5_sk"
projection_type = "ALL"
}
}
```
</details>
### Debug Output
Unfortunately, there aren't logs with `TF_LOG=debug` available. This bug reproduced only once our CI, where we don't have verbose debug logging enabled because it produces too much output...
The stderr of `terraform apply` :
```
╷
│ Error: error enabling DynamoDB Table (elastio-exp-1653068446-rvolxt-catalog-vaults) point in time recovery: error waiting for DynamoDB PITR update: unexpected state 'DISABLED', wanted target 'ENABLED'. last error: %!s(<nil>)
│
│ with module.catalog_region.aws_dynamodb_table.this,
│ on ../../../modules/catalog/region/dynamodb_table.tf line 4, in resource "aws_dynamodb_table" "this":
│ 4: resource "aws_dynamodb_table" "this" {
│
╵
```
### Expected Behavior
The table should've been deployed without any problems
### Actual Behavior
We run a lot of deployments with terraform on our CI every day, and see a lot of flakiness like this.
However, we enable PITR only in release builds which occur roughly every two weeks.
In this case, it is an error deploying the DynamoDB table, and it reproduced only once.
### Steps to Reproduce
The deployment is clean (it a non-incremental `apply`).
1. `terraform apply` | non_priority | flaky bug error waiting for dynamodb pitr update unexpected state disabled wanted target enabled community note please vote on this issue by adding a 👍 to the original issue to help the community and maintainers prioritize this request please do not leave or other comments that do not add relevant new information or questions they generate extra noise for issue followers and do not help prioritize the request if you are interested in working on this issue or have submitted a pull request please leave a comment terraform cli and terraform aws provider version terraform cli aws provider affected resource s aws dynamodb table terraform configuration files please include all terraform configurations required to reproduce the bug bug reports without a functional reproduction may be closed without investigation terraform code under spoiler due to size hcl resource aws dynamodb table this name elastio vaults billing mode pay per request point in time recovery enabled true tags elastio resource true hash key pk range key sk attribute name pk type s attribute name sk type s attribute name pk type s attribute name sk type s attribute name pk type s attribute name sk type s attribute name pk type s attribute name sk type s attribute name pk type s attribute name sk type s attribute name pk type s attribute name sk type s global secondary index name hash key pk range key sk projection type all global secondary index name hash key pk range key sk projection type all global secondary index name hash key pk range key sk projection type all global secondary index name hash key pk range key sk projection type all global secondary index name hash key pk range key sk projection type all debug output unfortunately there aren t logs with tf log debug available this bug reproduced only once our ci where we don t have verbose debug logging enabled because it produces too much output the stderr of terraform apply ╷ │ error error enabling dynamodb table elastio exp rvolxt catalog vaults point in time recovery error waiting for dynamodb pitr update unexpected state disabled wanted target enabled last error s │ │ with module catalog region aws dynamodb table this │ on modules catalog region dynamodb table tf line in resource aws dynamodb table this │ resource aws dynamodb table this │ ╵ expected behavior the table should ve been deployed without any problems actual behavior we run a lot of deployments with terraform on our ci every day and see a lot of flakiness like this however we enable pitr only in release builds which occur roughly every two weeks in this case it is an error deploying the dynamodb table and it reproduced only once steps to reproduce the deployment is clean it a non incremental apply terraform apply | 0 |
92,917 | 8,388,194,666 | IssuesEvent | 2018-10-09 05:02:22 | TerriaJS/aremi-natmap | https://api.github.com/repos/TerriaJS/aremi-natmap | closed | AREMI v2018-09-28 Pre-Release Test - Error accessing catalogue item #13 | GA-testing | Layer: Topography/Elevation/LIDAR 25m DEM
Error: Request has failed - Status code: 503
| 1.0 | AREMI v2018-09-28 Pre-Release Test - Error accessing catalogue item #13 - Layer: Topography/Elevation/LIDAR 25m DEM
Error: Request has failed - Status code: 503
| non_priority | aremi pre release test error accessing catalogue item layer topography elevation lidar dem error request has failed status code | 0 |
25,089 | 12,217,681,904 | IssuesEvent | 2020-05-01 17:42:51 | terraform-providers/terraform-provider-aws | https://api.github.com/repos/terraform-providers/terraform-provider-aws | closed | AWS Sqs Queue not setting visibility_timeout_seconds = 0 on create | bug service/sqs stale | _This issue was originally opened by @scottharrisaus as hashicorp/terraform#14300. It was migrated here as part of the [provider split](https://www.hashicorp.com/blog/upcoming-provider-changes-in-terraform-0-10/). The original body of the issue is below._
<hr>
When creating a sqs queue and setting visibility_timeout_seconds = 0 the queue gets created with the default setting of 30 instead, running the apply for a second time then modifies the queue setting from 30 -> 0. Using a value other than 0 applies correctly on first run.
### Terraform Version
Terraform v0.9.4
### Affected Resource(s)
aws_sqs_queue
### Terraform Configuration Files
```hcl
resource "aws_sqs_queue" "queue_dead" {
name = "${terraform.env}-sqstest-dead"
delay_seconds = 0
message_retention_seconds = 1209600
visibility_timeout_seconds = 0
receive_wait_time_seconds = 20
}
```
### Expected Behavior
new sqs queue should be created with visibility_timeout_seconds = 0
### Actual Behavior
new sqs queue has visibility_timeout_seconds set to default of 30 seconds.
### Steps to Reproduce
1. `terraform apply`
2. `terraform apply`
| 1.0 | AWS Sqs Queue not setting visibility_timeout_seconds = 0 on create - _This issue was originally opened by @scottharrisaus as hashicorp/terraform#14300. It was migrated here as part of the [provider split](https://www.hashicorp.com/blog/upcoming-provider-changes-in-terraform-0-10/). The original body of the issue is below._
<hr>
When creating a sqs queue and setting visibility_timeout_seconds = 0 the queue gets created with the default setting of 30 instead, running the apply for a second time then modifies the queue setting from 30 -> 0. Using a value other than 0 applies correctly on first run.
### Terraform Version
Terraform v0.9.4
### Affected Resource(s)
aws_sqs_queue
### Terraform Configuration Files
```hcl
resource "aws_sqs_queue" "queue_dead" {
name = "${terraform.env}-sqstest-dead"
delay_seconds = 0
message_retention_seconds = 1209600
visibility_timeout_seconds = 0
receive_wait_time_seconds = 20
}
```
### Expected Behavior
new sqs queue should be created with visibility_timeout_seconds = 0
### Actual Behavior
new sqs queue has visibility_timeout_seconds set to default of 30 seconds.
### Steps to Reproduce
1. `terraform apply`
2. `terraform apply`
| non_priority | aws sqs queue not setting visibility timeout seconds on create this issue was originally opened by scottharrisaus as hashicorp terraform it was migrated here as part of the the original body of the issue is below when creating a sqs queue and setting visibility timeout seconds the queue gets created with the default setting of instead running the apply for a second time then modifies the queue setting from using a value other than applies correctly on first run terraform version terraform affected resource s aws sqs queue terraform configuration files hcl resource aws sqs queue queue dead name terraform env sqstest dead delay seconds message retention seconds visibility timeout seconds receive wait time seconds expected behavior new sqs queue should be created with visibility timeout seconds actual behavior new sqs queue has visibility timeout seconds set to default of seconds steps to reproduce terraform apply terraform apply | 0 |
30,941 | 14,704,327,640 | IssuesEvent | 2021-01-04 16:20:08 | ClickHouse/ClickHouse | https://api.github.com/repos/ClickHouse/ClickHouse | opened | Poor performance of IS NULL / IS NOT NULL queries against table with allow_nullable_key | performance | ```sql
CREATE TABLE test_nullable_key.test
(
`n` Nullable(UInt8)
)
ENGINE = MergeTree
ORDER BY n
SETTINGS allow_nullable_key = 1, index_granularity = 8192;
insert into test select * from numbers_mt(1000000000);
optimize table test;
```
Here PK is used:
```
echo 'select count() from test_nullable_key.test where n = 11' | clickhouse-benchmark -i 1000
Queries executed: 1000.
localhost:9000, queries 1000, QPS: 361.415, RPS: 1415219692.792, MiB/s: 2699.317, result RPS: 361.415, result MiB/s: 0.003.
0.000% 0.002 sec.
10.000% 0.003 sec.
20.000% 0.003 sec.
30.000% 0.003 sec.
40.000% 0.003 sec.
50.000% 0.003 sec.
60.000% 0.003 sec.
70.000% 0.003 sec.
80.000% 0.003 sec.
90.000% 0.003 sec.
95.000% 0.003 sec.
99.000% 0.004 sec.
99.900% 0.007 sec.
99.990% 0.012 sec.
```
And here - not:
```
echo 'select count() from test_nullable_key.test where n is null' | clickhouse-benchmark -i 100
Queries executed: 100.
localhost:9000, queries 100, QPS: 9.281, RPS: 9281304039.018, MiB/s: 17702.683, result RPS: 9.281, result MiB/s: 0.000.
0.000% 0.085 sec.
10.000% 0.091 sec.
20.000% 0.093 sec.
30.000% 0.098 sec.
40.000% 0.102 sec.
50.000% 0.104 sec.
60.000% 0.107 sec.
70.000% 0.112 sec.
80.000% 0.119 sec.
90.000% 0.131 sec.
95.000% 0.140 sec.
99.000% 0.157 sec.
99.900% 0.163 sec.
99.990% 0.163 sec.
```
See
#12433
#12455 | True | Poor performance of IS NULL / IS NOT NULL queries against table with allow_nullable_key - ```sql
CREATE TABLE test_nullable_key.test
(
`n` Nullable(UInt8)
)
ENGINE = MergeTree
ORDER BY n
SETTINGS allow_nullable_key = 1, index_granularity = 8192;
insert into test select * from numbers_mt(1000000000);
optimize table test;
```
Here PK is used:
```
echo 'select count() from test_nullable_key.test where n = 11' | clickhouse-benchmark -i 1000
Queries executed: 1000.
localhost:9000, queries 1000, QPS: 361.415, RPS: 1415219692.792, MiB/s: 2699.317, result RPS: 361.415, result MiB/s: 0.003.
0.000% 0.002 sec.
10.000% 0.003 sec.
20.000% 0.003 sec.
30.000% 0.003 sec.
40.000% 0.003 sec.
50.000% 0.003 sec.
60.000% 0.003 sec.
70.000% 0.003 sec.
80.000% 0.003 sec.
90.000% 0.003 sec.
95.000% 0.003 sec.
99.000% 0.004 sec.
99.900% 0.007 sec.
99.990% 0.012 sec.
```
And here - not:
```
echo 'select count() from test_nullable_key.test where n is null' | clickhouse-benchmark -i 100
Queries executed: 100.
localhost:9000, queries 100, QPS: 9.281, RPS: 9281304039.018, MiB/s: 17702.683, result RPS: 9.281, result MiB/s: 0.000.
0.000% 0.085 sec.
10.000% 0.091 sec.
20.000% 0.093 sec.
30.000% 0.098 sec.
40.000% 0.102 sec.
50.000% 0.104 sec.
60.000% 0.107 sec.
70.000% 0.112 sec.
80.000% 0.119 sec.
90.000% 0.131 sec.
95.000% 0.140 sec.
99.000% 0.157 sec.
99.900% 0.163 sec.
99.990% 0.163 sec.
```
See
#12433
#12455 | non_priority | poor performance of is null is not null queries against table with allow nullable key sql create table test nullable key test n nullable engine mergetree order by n settings allow nullable key index granularity insert into test select from numbers mt optimize table test here pk is used echo select count from test nullable key test where n clickhouse benchmark i queries executed localhost queries qps rps mib s result rps result mib s sec sec sec sec sec sec sec sec sec sec sec sec sec sec and here not echo select count from test nullable key test where n is null clickhouse benchmark i queries executed localhost queries qps rps mib s result rps result mib s sec sec sec sec sec sec sec sec sec sec sec sec sec sec see | 0 |
336,560 | 30,201,958,712 | IssuesEvent | 2023-07-05 06:44:22 | snu-quiqcl/artiq-proxy | https://api.github.com/repos/snu-quiqcl/artiq-proxy | closed | Unit tests for the implemented functions | test | ### Feature you want to implement
What is the feature you want to implement?
### How the feature is implemented
ex) Add *B* method to *A* class, Upgrade *C* model
### Additional context
Add any other context or screenshots about the feature here.
| 1.0 | Unit tests for the implemented functions - ### Feature you want to implement
What is the feature you want to implement?
### How the feature is implemented
ex) Add *B* method to *A* class, Upgrade *C* model
### Additional context
Add any other context or screenshots about the feature here.
| non_priority | unit tests for the implemented functions feature you want to implement what is the feature you want to implement how the feature is implemented ex add b method to a class upgrade c model additional context add any other context or screenshots about the feature here | 0 |
32,989 | 14,000,579,743 | IssuesEvent | 2020-10-28 12:32:01 | aws/aws-controllers-k8s | https://api.github.com/repos/aws/aws-controllers-k8s | closed | ECR service controller | ECR Service Controller | ## ACK service controller
Support for Amazon ECR.
### Checklist for Dev Preview
- [x] Code generation (`make build-controller`)
- [x] End-to-end test (`make kind-test`)
- [x] Docs are updated, at least:
- [x] [testing](https://aws.github.io/aws-controllers-k8s/dev-docs/testing/)
- [x] [svc controller listing](https://aws.github.io/aws-controllers-k8s/services/)
| 1.0 | ECR service controller - ## ACK service controller
Support for Amazon ECR.
### Checklist for Dev Preview
- [x] Code generation (`make build-controller`)
- [x] End-to-end test (`make kind-test`)
- [x] Docs are updated, at least:
- [x] [testing](https://aws.github.io/aws-controllers-k8s/dev-docs/testing/)
- [x] [svc controller listing](https://aws.github.io/aws-controllers-k8s/services/)
| non_priority | ecr service controller ack service controller support for amazon ecr checklist for dev preview code generation make build controller end to end test make kind test docs are updated at least | 0 |
32,595 | 4,381,876,385 | IssuesEvent | 2016-08-06 14:38:40 | hoburg/gpkit | https://api.github.com/repos/hoburg/gpkit | closed | Model.__getitem__ should return highest-level varkey | design discussion | list of varkeys all with the same name should be in `.byname`. Also there could be a fuzzy search, `.search("W wing")` which would get all of `W_wing`, `W with model=['wing']`, `W descr="wing weight"` and return a list sorted by relevance (or just the most relevant) | 1.0 | Model.__getitem__ should return highest-level varkey - list of varkeys all with the same name should be in `.byname`. Also there could be a fuzzy search, `.search("W wing")` which would get all of `W_wing`, `W with model=['wing']`, `W descr="wing weight"` and return a list sorted by relevance (or just the most relevant) | non_priority | model getitem should return highest level varkey list of varkeys all with the same name should be in byname also there could be a fuzzy search search w wing which would get all of w wing w with model w descr wing weight and return a list sorted by relevance or just the most relevant | 0 |
108,331 | 23,592,958,270 | IssuesEvent | 2022-08-23 16:40:49 | dart-lang/sdk | https://api.github.com/repos/dart-lang/sdk | closed | Disabled PC-relative calls for object allocations | area-vm type-performance vm-aot-code-size | The change in 91ed53413990eab8a0410e8c88f00f7a4007330c has disabled PC-relative calls for allocation stubs. The corresponding code was commented out:
```diff
diff --git a/runtime/vm/compiler/stub_code_compiler_arm64.cc b/runtime/vm/compiler/stub_code_compiler_arm64.cc
index db103f75f2f..afc9b109efa 100644
--- a/runtime/vm/compiler/stub_code_compiler_arm64.cc
+++ b/runtime/vm/compiler/stub_code_compiler_arm64.cc
@@ -2266,7 +2266,9 @@ void StubCodeCompiler::GenerateAllocationStubForClass(
!target::Class::TraceAllocation(cls) &&
target::SizeFitsInSizeTag(instance_size)) {
if (is_cls_parameterized) {
- if (!IsSameObject(NullObject(),
+ // TODO(41974): Assign all allocation stubs to the root loading unit?
+ if (false &&
+ !IsSameObject(NullObject(),
CastHandle<Object>(allocat_object_parametrized))) {
__ GenerateUnRelocatedPcRelativeTailCall();
unresolved_calls->Add(new UnresolvedPcRelativeCall(
@@ -2279,7 +2281,9 @@ void StubCodeCompiler::GenerateAllocationStubForClass(
__ br(R4);
}
} else {
- if (!IsSameObject(NullObject(), CastHandle<Object>(allocate_object))) {
+ // TODO(41974): Assign all allocation stubs to the root loading unit?
+ if (false &&
+ !IsSameObject(NullObject(), CastHandle<Object>(allocate_object))) {
__ GenerateUnRelocatedPcRelativeTailCall();
unresolved_calls->Add(new UnresolvedPcRelativeCall(
__ CodeSize(), allocate_object, /*is_tail_call=*/true));
```
The referenced https://github.com/dart-lang/sdk/issues/41974 is already closed.
/cc @rmacnak-google | 1.0 | Disabled PC-relative calls for object allocations - The change in 91ed53413990eab8a0410e8c88f00f7a4007330c has disabled PC-relative calls for allocation stubs. The corresponding code was commented out:
```diff
diff --git a/runtime/vm/compiler/stub_code_compiler_arm64.cc b/runtime/vm/compiler/stub_code_compiler_arm64.cc
index db103f75f2f..afc9b109efa 100644
--- a/runtime/vm/compiler/stub_code_compiler_arm64.cc
+++ b/runtime/vm/compiler/stub_code_compiler_arm64.cc
@@ -2266,7 +2266,9 @@ void StubCodeCompiler::GenerateAllocationStubForClass(
!target::Class::TraceAllocation(cls) &&
target::SizeFitsInSizeTag(instance_size)) {
if (is_cls_parameterized) {
- if (!IsSameObject(NullObject(),
+ // TODO(41974): Assign all allocation stubs to the root loading unit?
+ if (false &&
+ !IsSameObject(NullObject(),
CastHandle<Object>(allocat_object_parametrized))) {
__ GenerateUnRelocatedPcRelativeTailCall();
unresolved_calls->Add(new UnresolvedPcRelativeCall(
@@ -2279,7 +2281,9 @@ void StubCodeCompiler::GenerateAllocationStubForClass(
__ br(R4);
}
} else {
- if (!IsSameObject(NullObject(), CastHandle<Object>(allocate_object))) {
+ // TODO(41974): Assign all allocation stubs to the root loading unit?
+ if (false &&
+ !IsSameObject(NullObject(), CastHandle<Object>(allocate_object))) {
__ GenerateUnRelocatedPcRelativeTailCall();
unresolved_calls->Add(new UnresolvedPcRelativeCall(
__ CodeSize(), allocate_object, /*is_tail_call=*/true));
```
The referenced https://github.com/dart-lang/sdk/issues/41974 is already closed.
/cc @rmacnak-google | non_priority | disabled pc relative calls for object allocations the change in has disabled pc relative calls for allocation stubs the corresponding code was commented out diff diff git a runtime vm compiler stub code compiler cc b runtime vm compiler stub code compiler cc index a runtime vm compiler stub code compiler cc b runtime vm compiler stub code compiler cc void stubcodecompiler generateallocationstubforclass target class traceallocation cls target sizefitsinsizetag instance size if is cls parameterized if issameobject nullobject todo assign all allocation stubs to the root loading unit if false issameobject nullobject casthandle allocat object parametrized generateunrelocatedpcrelativetailcall unresolved calls add new unresolvedpcrelativecall void stubcodecompiler generateallocationstubforclass br else if issameobject nullobject casthandle allocate object todo assign all allocation stubs to the root loading unit if false issameobject nullobject casthandle allocate object generateunrelocatedpcrelativetailcall unresolved calls add new unresolvedpcrelativecall codesize allocate object is tail call true the referenced is already closed cc rmacnak google | 0 |
266,187 | 23,226,658,329 | IssuesEvent | 2022-08-03 01:23:42 | MPMG-DCC-UFMG/F01 | https://api.github.com/repos/MPMG-DCC-UFMG/F01 | closed | Teste de generalizacao para a tag Servidores - Relatório mensal da despesa com pessoal - Felício dos Santos | generalization test development template-Síntese tecnologia informatica subtag-Relatórios Despesas com Pessoal tag-Servidores | DoD: Realizar o teste de Generalização do validador da tag Servidores - Relatório mensal da despesa com pessoal para o Município de Felício dos Santos. | 1.0 | Teste de generalizacao para a tag Servidores - Relatório mensal da despesa com pessoal - Felício dos Santos - DoD: Realizar o teste de Generalização do validador da tag Servidores - Relatório mensal da despesa com pessoal para o Município de Felício dos Santos. | non_priority | teste de generalizacao para a tag servidores relatório mensal da despesa com pessoal felício dos santos dod realizar o teste de generalização do validador da tag servidores relatório mensal da despesa com pessoal para o município de felício dos santos | 0 |
297,445 | 25,732,020,513 | IssuesEvent | 2022-12-07 21:06:02 | MicrosoftDocs/azure-docs | https://api.github.com/repos/MicrosoftDocs/azure-docs | closed | Doesn't work with Windows 11 VHD | devtest-lab/svc triaged in-progress assigned-to-author doc-enhancement Pri2 |
Hello,
Thanks for the wonderful examples here and on the Azure pages, many have been very helpful. We have been using this example script almost verbatim for a while now with Windows 10 and it works beautifully. We just created our first Windows 11 vhd and the script generates a custom image without error, however that image will not boot. Will not even get to the point where you can ping it or do any diagnostics of the VM. Presumably this is because there is nothing to specify that it needs to create a HyperV Gen 2 disk/VM, which uses different boot logic. Any ideas on what needs to change in the example to allow it to work for Windows 11?
Following the steps in the Portal work like a charm, so I guess those must be using different calls.
# Create the custom image.
New-AzResourceGroupDeployment -ResourceGroupName $lab.ResourceGroupName -Name CreateCustomImage -TemplateUri 'https://raw.githubusercontent.com/Azure/azure-devtestlab/master/samples/DevTestLabs/QuickStartTemplates/201-dtl-create-customimage-from-vhd/azuredeploy.json' -TemplateParameterObject $parameters
Thanks,
Brian
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: a96b4af7-04e1-763b-90a4-d43e85cb0787
* Version Independent ID: b05aa41c-61a6-50ef-2644-d04459e23348
* Content: [Create a custom image from VHD file by using Azure PowerShell - Azure DevTest Labs](https://docs.microsoft.com/en-us/azure/devtest-labs/devtest-lab-create-custom-image-from-vhd-using-powershell)
* Content Source: [articles/devtest-labs/devtest-lab-create-custom-image-from-vhd-using-powershell.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/devtest-labs/devtest-lab-create-custom-image-from-vhd-using-powershell.md)
* Service: **devtest-lab**
* GitHub Login: @j-martens
* Microsoft Alias: **juliako** | 1.0 | Doesn't work with Windows 11 VHD -
Hello,
Thanks for the wonderful examples here and on the Azure pages, many have been very helpful. We have been using this example script almost verbatim for a while now with Windows 10 and it works beautifully. We just created our first Windows 11 vhd and the script generates a custom image without error, however that image will not boot. Will not even get to the point where you can ping it or do any diagnostics of the VM. Presumably this is because there is nothing to specify that it needs to create a HyperV Gen 2 disk/VM, which uses different boot logic. Any ideas on what needs to change in the example to allow it to work for Windows 11?
Following the steps in the Portal work like a charm, so I guess those must be using different calls.
# Create the custom image.
New-AzResourceGroupDeployment -ResourceGroupName $lab.ResourceGroupName -Name CreateCustomImage -TemplateUri 'https://raw.githubusercontent.com/Azure/azure-devtestlab/master/samples/DevTestLabs/QuickStartTemplates/201-dtl-create-customimage-from-vhd/azuredeploy.json' -TemplateParameterObject $parameters
Thanks,
Brian
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: a96b4af7-04e1-763b-90a4-d43e85cb0787
* Version Independent ID: b05aa41c-61a6-50ef-2644-d04459e23348
* Content: [Create a custom image from VHD file by using Azure PowerShell - Azure DevTest Labs](https://docs.microsoft.com/en-us/azure/devtest-labs/devtest-lab-create-custom-image-from-vhd-using-powershell)
* Content Source: [articles/devtest-labs/devtest-lab-create-custom-image-from-vhd-using-powershell.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/devtest-labs/devtest-lab-create-custom-image-from-vhd-using-powershell.md)
* Service: **devtest-lab**
* GitHub Login: @j-martens
* Microsoft Alias: **juliako** | non_priority | doesn t work with windows vhd hello thanks for the wonderful examples here and on the azure pages many have been very helpful we have been using this example script almost verbatim for a while now with windows and it works beautifully we just created our first windows vhd and the script generates a custom image without error however that image will not boot will not even get to the point where you can ping it or do any diagnostics of the vm presumably this is because there is nothing to specify that it needs to create a hyperv gen disk vm which uses different boot logic any ideas on what needs to change in the example to allow it to work for windows following the steps in the portal work like a charm so i guess those must be using different calls create the custom image new azresourcegroupdeployment resourcegroupname lab resourcegroupname name createcustomimage templateuri templateparameterobject parameters thanks brian document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service devtest lab github login j martens microsoft alias juliako | 0 |
132,547 | 10,758,972,403 | IssuesEvent | 2019-10-31 15:50:21 | rancher/rancher | https://api.github.com/repos/rancher/rancher | closed | FATA: Only support with English System Locale | [zube]: To Test area/windows kind/bug team/cn | Rancher version: 2.3.0.0-rc8
I had Rancher 2.3.0.0-rc3/4 was working.
When adding a windows node i get the error message: FATA: Only support with English System Locale . ( Screenshot: https://imgur.com/a/xGXKgcp )
First of all its hard to know what this means? (Im work mostly with windows). Is it complaining about Region? Character set? Keybaord layout,TimeZone? Who knows.
Its NOT windows language. Because my windows is in English ( But setup with Norwegian keyboard)
| 1.0 | FATA: Only support with English System Locale - Rancher version: 2.3.0.0-rc8
I had Rancher 2.3.0.0-rc3/4 was working.
When adding a windows node i get the error message: FATA: Only support with English System Locale . ( Screenshot: https://imgur.com/a/xGXKgcp )
First of all its hard to know what this means? (Im work mostly with windows). Is it complaining about Region? Character set? Keybaord layout,TimeZone? Who knows.
Its NOT windows language. Because my windows is in English ( But setup with Norwegian keyboard)
| non_priority | fata only support with english system locale rancher version i had rancher was working when adding a windows node i get the error message fata only support with english system locale screenshot first of all its hard to know what this means im work mostly with windows is it complaining about region character set keybaord layout timezone who knows its not windows language because my windows is in english but setup with norwegian keyboard | 0 |
239,647 | 19,905,866,454 | IssuesEvent | 2022-01-25 12:44:31 | vector-im/element-android | https://api.github.com/repos/vector-im/element-android | opened | Threads: Turning Threads on doesn't move messages into a Thread | T-Enhancement A-Threads Z-ThreadsP0 Z-ThreadsInternalTesting | ### Your use case
Found during testing on January 20, 2022
- Turned threads off
- Used "reply" to respond to a thread message
- Turned threads back on
- Reply was not in the thread, but still on the timeline
@daniellekirkwood to add a screenshot
### Have you considered any alternatives?
_No response_
### Additional context
_No response_ | 1.0 | Threads: Turning Threads on doesn't move messages into a Thread - ### Your use case
Found during testing on January 20, 2022
- Turned threads off
- Used "reply" to respond to a thread message
- Turned threads back on
- Reply was not in the thread, but still on the timeline
@daniellekirkwood to add a screenshot
### Have you considered any alternatives?
_No response_
### Additional context
_No response_ | non_priority | threads turning threads on doesn t move messages into a thread your use case found during testing on january turned threads off used reply to respond to a thread message turned threads back on reply was not in the thread but still on the timeline daniellekirkwood to add a screenshot have you considered any alternatives no response additional context no response | 0 |
28,384 | 5,246,676,846 | IssuesEvent | 2017-02-01 10:23:56 | hazelcast/hazelcast | https://api.github.com/repos/hazelcast/hazelcast | opened | NullPointerException in LockServiceImpl | Team: Core Type: Defect | We can produce a NPE in `LockServiceImpl` by creating one map with a quorum configuration (which activates the `QuorumServiceImpl` for all `QuorumAware` operations) and then call an `QuorumAware` operation on another data structure without a quorum configuration:
```
java.lang.NullPointerException
at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
at com.hazelcast.util.ConcurrencyUtil.getOrPutSynchronized(ConcurrencyUtil.java:94)
at com.hazelcast.concurrent.lock.LockServiceImpl.getQuorumName(LockServiceImpl.java:336)
at com.hazelcast.quorum.impl.QuorumServiceImpl.findQuorum(QuorumServiceImpl.java:144)
at com.hazelcast.quorum.impl.QuorumServiceImpl.ensureQuorumPresent(QuorumServiceImpl.java:123)
at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.ensureQuorumPresent(OperationRunnerImpl.java:237)
at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:178)
at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:401)
at com.hazelcast.spi.impl.operationexecutor.impl.OperationThread.process(OperationThread.java:117)
at com.hazelcast.spi.impl.operationexecutor.impl.OperationThread.run(OperationThread.java:102)
at ------ submitted from ------.(Unknown Source)
at com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolve(InvocationFuture.java:114)
at com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolveAndThrowIfException(InvocationFuture.java:75)
at com.hazelcast.spi.impl.AbstractInvocationFuture.get(AbstractInvocationFuture.java:155)
at com.hazelcast.spi.impl.AbstractInvocationFuture.join(AbstractInvocationFuture.java:136)
at com.hazelcast.concurrent.lock.LockProxySupport.unlock(LockProxySupport.java:149)
at com.hazelcast.concurrent.lock.LockProxy.unlock(LockProxy.java:106)
at com.hazelcast.quorum.QuorumTest.quorumOnOneMapShouldNotAffectOtherQuorumAwareOperations(QuorumTest.java:307)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:89)
at com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:81)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.lang.Thread.run(Thread.java:745)
```
The reason is the `LockConfig lockConfig = nodeEngine.getConfig().findLockConfig(name)` which returns the default configuration for non-quorum data structures, which has `null` as quorum name. This `null` is then put into the `ConcurrentMap<String, String> quorumConfigCache` which produces the NPE. | 1.0 | NullPointerException in LockServiceImpl - We can produce a NPE in `LockServiceImpl` by creating one map with a quorum configuration (which activates the `QuorumServiceImpl` for all `QuorumAware` operations) and then call an `QuorumAware` operation on another data structure without a quorum configuration:
```
java.lang.NullPointerException
at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
at com.hazelcast.util.ConcurrencyUtil.getOrPutSynchronized(ConcurrencyUtil.java:94)
at com.hazelcast.concurrent.lock.LockServiceImpl.getQuorumName(LockServiceImpl.java:336)
at com.hazelcast.quorum.impl.QuorumServiceImpl.findQuorum(QuorumServiceImpl.java:144)
at com.hazelcast.quorum.impl.QuorumServiceImpl.ensureQuorumPresent(QuorumServiceImpl.java:123)
at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.ensureQuorumPresent(OperationRunnerImpl.java:237)
at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:178)
at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:401)
at com.hazelcast.spi.impl.operationexecutor.impl.OperationThread.process(OperationThread.java:117)
at com.hazelcast.spi.impl.operationexecutor.impl.OperationThread.run(OperationThread.java:102)
at ------ submitted from ------.(Unknown Source)
at com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolve(InvocationFuture.java:114)
at com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolveAndThrowIfException(InvocationFuture.java:75)
at com.hazelcast.spi.impl.AbstractInvocationFuture.get(AbstractInvocationFuture.java:155)
at com.hazelcast.spi.impl.AbstractInvocationFuture.join(AbstractInvocationFuture.java:136)
at com.hazelcast.concurrent.lock.LockProxySupport.unlock(LockProxySupport.java:149)
at com.hazelcast.concurrent.lock.LockProxy.unlock(LockProxy.java:106)
at com.hazelcast.quorum.QuorumTest.quorumOnOneMapShouldNotAffectOtherQuorumAwareOperations(QuorumTest.java:307)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:89)
at com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:81)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.lang.Thread.run(Thread.java:745)
```
The reason is the `LockConfig lockConfig = nodeEngine.getConfig().findLockConfig(name)` which returns the default configuration for non-quorum data structures, which has `null` as quorum name. This `null` is then put into the `ConcurrentMap<String, String> quorumConfigCache` which produces the NPE. | non_priority | nullpointerexception in lockserviceimpl we can produce a npe in lockserviceimpl by creating one map with a quorum configuration which activates the quorumserviceimpl for all quorumaware operations and then call an quorumaware operation on another data structure without a quorum configuration java lang nullpointerexception at java util concurrent concurrenthashmap putval concurrenthashmap java at java util concurrent concurrenthashmap put concurrenthashmap java at com hazelcast util concurrencyutil getorputsynchronized concurrencyutil java at com hazelcast concurrent lock lockserviceimpl getquorumname lockserviceimpl java at com hazelcast quorum impl quorumserviceimpl findquorum quorumserviceimpl java at com hazelcast quorum impl quorumserviceimpl ensurequorumpresent quorumserviceimpl java at com hazelcast spi impl operationservice impl operationrunnerimpl ensurequorumpresent operationrunnerimpl java at com hazelcast spi impl operationservice impl operationrunnerimpl run operationrunnerimpl java at com hazelcast spi impl operationservice impl operationrunnerimpl run operationrunnerimpl java at com hazelcast spi impl operationexecutor impl operationthread process operationthread java at com hazelcast spi impl operationexecutor impl operationthread run operationthread java at submitted from unknown source at com hazelcast spi impl operationservice impl invocationfuture resolve invocationfuture java at com hazelcast spi impl operationservice impl invocationfuture resolveandthrowifexception invocationfuture java at com hazelcast spi impl abstractinvocationfuture get abstractinvocationfuture java at com hazelcast spi impl abstractinvocationfuture join abstractinvocationfuture java at com hazelcast concurrent lock lockproxysupport unlock lockproxysupport java at com hazelcast concurrent lock lockproxy unlock lockproxy java at com hazelcast quorum quorumtest quorumononemapshouldnotaffectotherquorumawareoperations quorumtest java at sun reflect nativemethodaccessorimpl native method at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org junit runners model frameworkmethod runreflectivecall frameworkmethod java at org junit internal runners model reflectivecallable run reflectivecallable java at org junit runners model frameworkmethod invokeexplosively frameworkmethod java at org junit internal runners statements invokemethod evaluate invokemethod java at com hazelcast test failontimeoutstatement callablestatement call failontimeoutstatement java at com hazelcast test failontimeoutstatement callablestatement call failontimeoutstatement java at java util concurrent futuretask run futuretask java at java lang thread run thread java the reason is the lockconfig lockconfig nodeengine getconfig findlockconfig name which returns the default configuration for non quorum data structures which has null as quorum name this null is then put into the concurrentmap quorumconfigcache which produces the npe | 0 |
258,990 | 19,581,313,103 | IssuesEvent | 2022-01-04 21:45:38 | napari/napari | https://api.github.com/repos/napari/napari | closed | Better autogenerated docs | documentation | ## 📚 Documentation
we currently use `sphinx-apidoc` to autogenerate docs, but it leaves a little to be desired in the way of organization... but it also doesn't provide a ton of options (beyond templates) to configure it. This issue is just to remind us to look into autogenerating our own API docs to look just as we want them.
| 1.0 | Better autogenerated docs - ## 📚 Documentation
we currently use `sphinx-apidoc` to autogenerate docs, but it leaves a little to be desired in the way of organization... but it also doesn't provide a ton of options (beyond templates) to configure it. This issue is just to remind us to look into autogenerating our own API docs to look just as we want them.
| non_priority | better autogenerated docs 📚 documentation we currently use sphinx apidoc to autogenerate docs but it leaves a little to be desired in the way of organization but it also doesn t provide a ton of options beyond templates to configure it this issue is just to remind us to look into autogenerating our own api docs to look just as we want them | 0 |
33,144 | 7,660,415,297 | IssuesEvent | 2018-05-11 10:26:09 | rust-community/content-o-tron | https://api.github.com/repos/rust-community/content-o-tron | closed | Create a new content-o-tron task issue template | mozsprint no code work-in-progress | Should include various fields we require to have a task that someone can help out on. Also add a create new link at the top of the template. | 1.0 | Create a new content-o-tron task issue template - Should include various fields we require to have a task that someone can help out on. Also add a create new link at the top of the template. | non_priority | create a new content o tron task issue template should include various fields we require to have a task that someone can help out on also add a create new link at the top of the template | 0 |
304,174 | 23,052,160,210 | IssuesEvent | 2022-07-24 19:50:13 | P2JN/doit | https://api.github.com/repos/P2JN/doit | closed | doc - inicio, plan y diseño | documentation | ## descripcion
revisar la documentación de las fases iniciales del proyecto y pasarlas a la memoria, haciendo uso de la wiki y la memoria
## to-do
- [ ] comprobar usabilidad de formato markdown en latex
- [x] documentar el Inicio
- [ ] documentar la Planificación
- [ ] documentar el Diseño
## recursos
- memoria
- wiki | 1.0 | doc - inicio, plan y diseño - ## descripcion
revisar la documentación de las fases iniciales del proyecto y pasarlas a la memoria, haciendo uso de la wiki y la memoria
## to-do
- [ ] comprobar usabilidad de formato markdown en latex
- [x] documentar el Inicio
- [ ] documentar la Planificación
- [ ] documentar el Diseño
## recursos
- memoria
- wiki | non_priority | doc inicio plan y diseño descripcion revisar la documentación de las fases iniciales del proyecto y pasarlas a la memoria haciendo uso de la wiki y la memoria to do comprobar usabilidad de formato markdown en latex documentar el inicio documentar la planificación documentar el diseño recursos memoria wiki | 0 |
46,274 | 13,153,311,384 | IssuesEvent | 2020-08-10 02:49:24 | WKHAllen/NorseBooks | https://api.github.com/repos/WKHAllen/NorseBooks | closed | Improve security on user contact info modal | backend bug frontend security | Make user info available through an API endpoint. Access the endpoint and set results in the modal's inner text accordingly. **Do not pass contact info values to the view.** | True | Improve security on user contact info modal - Make user info available through an API endpoint. Access the endpoint and set results in the modal's inner text accordingly. **Do not pass contact info values to the view.** | non_priority | improve security on user contact info modal make user info available through an api endpoint access the endpoint and set results in the modal s inner text accordingly do not pass contact info values to the view | 0 |
63,972 | 7,756,507,858 | IssuesEvent | 2018-05-31 13:49:30 | Threespot/aldf-wp | https://api.github.com/repos/Threespot/aldf-wp | closed | Article: Increase title block subtitle font size | Design Issue 🎨 | Increase subtitle to match subtitles on issue and case pages
* Font-size: 22px
* Line-height: 29px
Dev
Issue subtitle
https://live-aldf-wp.pantheonsite.io/article/test-article-with-components/
https://live-aldf-wp.pantheonsite.io/article/test-article-with-components/test-for-grouping/ | 1.0 | Article: Increase title block subtitle font size - Increase subtitle to match subtitles on issue and case pages
* Font-size: 22px
* Line-height: 29px
Dev
Issue subtitle
https://live-aldf-wp.pantheonsite.io/article/test-article-with-components/
https://live-aldf-wp.pantheonsite.io/article/test-article-with-components/test-for-grouping/ | non_priority | article increase title block subtitle font size increase subtitle to match subtitles on issue and case pages font size line height dev issue subtitle | 0 |
141,415 | 11,417,790,023 | IssuesEvent | 2020-02-03 01:30:54 | brave/brave-browser | https://api.github.com/repos/brave/brave-browser | opened | Manual test run on Linux for Ethereum Remote Client 1.0.16 | OS/unix-like/linux QA/Yes release-notes/exclude tests | ## Per release specialty tests
- [ ] Add reset data / delete account option to Crypto Wallets.([#5741](https://github.com/brave/brave-browser/issues/5741))
- [ ] Import wallet learn more links to MM help page.([#6103](https://github.com/brave/brave-browser/issues/6103))
- [ ] JSON file import help links to MM help page.([#6104](https://github.com/brave/brave-browser/issues/6104))
- [ ] Allowing Dapp sites to install opens a blank brave://wallet page .([#6279](https://github.com/brave/brave-browser/issues/6279))
- [ ] Crypto Wallet dark theme issues.([#6381](https://github.com/brave/brave-browser/issues/6381))
- [ ] Wallet backup screen should be responsive to browser size .([#7045](https://github.com/brave/brave-browser/issues/7045))
- [ ] Clicking on `Restore account? Import using account seed phrase` does nothing.([#7537](https://github.com/brave/brave-browser/issues/7537))
- [ ] Learn more on connect wallet popup links to MM support page.([#7695](https://github.com/brave/brave-browser/issues/7695))
- [ ] Removing "Choose a type to set up" from brave://wallet.([#7791](https://github.com/brave/brave-browser/issues/7791))
- [ ] Connect to wallet popup needs to be responsive.([#7882](https://github.com/brave/brave-browser/issues/7882))
## Branding
- [ ] Verify there are no appearances of the word MetaMask
- [ ] Verify links to MetaMask resources such as websites and email should point to Brave resources
- [ ] Verify all downloadable resources (Seed/Logs) contains Brave file names
- [ ] Verify MetaFox logo is not present on any screen
## Component
- [ ] Verify Ethereum client component is downloaded when you open brave://wallet for the first time
- [ ] Verify Ethereum client component is successfully updated and doesn't corrupt the browser wallet
- [ ] Delete component folder. Verify the component is downloaded successfully after browser relaunch
## Ðapps
- [ ] Verify Ðapp can successfully connect to your crypto wallets account, signed via a pop-up notification
- [ ] Verify Ðapp transactions where assets are set/received show up in the account activity view within the extension
## Import & Recovery
- [ ] Verify you can import Brave Crypto Wallet using 24 seed words
- [ ] Verify you can import MetaMask Wallet using only 12 seed words
- [ ] Verify you can restore Brave CW/MM account from the login screen
## Transactions
- [ ] Verify Eth/ERC-20 tokens can be received at the addresses generated for your account
- [ ] Verify Eth/ERC-20 tokens can be sent to other addresses from your account
- [ ] Verify a successful transaction can be done on a restored wallet
## Hardware
- [ ] Verify you can link hardware wallet using Trezor and unlock the wallet
- [ ] Verify you can link hardware wallet using Ledger Nano and unlock the wallet | 1.0 | Manual test run on Linux for Ethereum Remote Client 1.0.16 - ## Per release specialty tests
- [ ] Add reset data / delete account option to Crypto Wallets.([#5741](https://github.com/brave/brave-browser/issues/5741))
- [ ] Import wallet learn more links to MM help page.([#6103](https://github.com/brave/brave-browser/issues/6103))
- [ ] JSON file import help links to MM help page.([#6104](https://github.com/brave/brave-browser/issues/6104))
- [ ] Allowing Dapp sites to install opens a blank brave://wallet page .([#6279](https://github.com/brave/brave-browser/issues/6279))
- [ ] Crypto Wallet dark theme issues.([#6381](https://github.com/brave/brave-browser/issues/6381))
- [ ] Wallet backup screen should be responsive to browser size .([#7045](https://github.com/brave/brave-browser/issues/7045))
- [ ] Clicking on `Restore account? Import using account seed phrase` does nothing.([#7537](https://github.com/brave/brave-browser/issues/7537))
- [ ] Learn more on connect wallet popup links to MM support page.([#7695](https://github.com/brave/brave-browser/issues/7695))
- [ ] Removing "Choose a type to set up" from brave://wallet.([#7791](https://github.com/brave/brave-browser/issues/7791))
- [ ] Connect to wallet popup needs to be responsive.([#7882](https://github.com/brave/brave-browser/issues/7882))
## Branding
- [ ] Verify there are no appearances of the word MetaMask
- [ ] Verify links to MetaMask resources such as websites and email should point to Brave resources
- [ ] Verify all downloadable resources (Seed/Logs) contains Brave file names
- [ ] Verify MetaFox logo is not present on any screen
## Component
- [ ] Verify Ethereum client component is downloaded when you open brave://wallet for the first time
- [ ] Verify Ethereum client component is successfully updated and doesn't corrupt the browser wallet
- [ ] Delete component folder. Verify the component is downloaded successfully after browser relaunch
## Ðapps
- [ ] Verify Ðapp can successfully connect to your crypto wallets account, signed via a pop-up notification
- [ ] Verify Ðapp transactions where assets are set/received show up in the account activity view within the extension
## Import & Recovery
- [ ] Verify you can import Brave Crypto Wallet using 24 seed words
- [ ] Verify you can import MetaMask Wallet using only 12 seed words
- [ ] Verify you can restore Brave CW/MM account from the login screen
## Transactions
- [ ] Verify Eth/ERC-20 tokens can be received at the addresses generated for your account
- [ ] Verify Eth/ERC-20 tokens can be sent to other addresses from your account
- [ ] Verify a successful transaction can be done on a restored wallet
## Hardware
- [ ] Verify you can link hardware wallet using Trezor and unlock the wallet
- [ ] Verify you can link hardware wallet using Ledger Nano and unlock the wallet | non_priority | manual test run on linux for ethereum remote client per release specialty tests add reset data delete account option to crypto wallets import wallet learn more links to mm help page json file import help links to mm help page allowing dapp sites to install opens a blank brave wallet page crypto wallet dark theme issues wallet backup screen should be responsive to browser size clicking on restore account import using account seed phrase does nothing learn more on connect wallet popup links to mm support page removing choose a type to set up from brave wallet connect to wallet popup needs to be responsive branding verify there are no appearances of the word metamask verify links to metamask resources such as websites and email should point to brave resources verify all downloadable resources seed logs contains brave file names verify metafox logo is not present on any screen component verify ethereum client component is downloaded when you open brave wallet for the first time verify ethereum client component is successfully updated and doesn t corrupt the browser wallet delete component folder verify the component is downloaded successfully after browser relaunch ðapps verify ðapp can successfully connect to your crypto wallets account signed via a pop up notification verify ðapp transactions where assets are set received show up in the account activity view within the extension import recovery verify you can import brave crypto wallet using seed words verify you can import metamask wallet using only seed words verify you can restore brave cw mm account from the login screen transactions verify eth erc tokens can be received at the addresses generated for your account verify eth erc tokens can be sent to other addresses from your account verify a successful transaction can be done on a restored wallet hardware verify you can link hardware wallet using trezor and unlock the wallet verify you can link hardware wallet using ledger nano and unlock the wallet | 0 |
13,740 | 3,355,460,874 | IssuesEvent | 2015-11-18 16:30:50 | mozilla/webmaker-core | https://api.github.com/repos/mozilla/webmaker-core | closed | Webmaker 1.5 Android Viewing Project | Quality test | * [x] Open the app and tap the Discover tab, which opens the Discover view
**Discover View**
* [x] In the Discover view you see a list of projects. Each projects includes...
* [x] a title
* [x] a preview image
* [x] an author (indicated in blue)
* [x] scroll up and down to view additional projects
* [x] tap on any project in the Discover view, it will open
**Project Play Mode**
* [x] when the project opens, the header title is "Play"
* [x] you see a grid of pages
* [x] pinch to zoom in and out
* [x] drag to pan the view
* [x] tap a page to enter the Page view
**Page View**
* [x] In the Page view, you see the page you tapped previously, but zoomed in
* [x] there are arrows on the edge of the page that point to any adjacent pages
* [x] tapping an arrow moves the view to the adjacent page in that direction
* [ ] ~~swiping the page in the direction of any of the arrows also moves the view to the adjacent page~~ (not availabe)
* [ ] ~~the view animates to the adjacent page smoothly~~ (not availabe)
* [ ] ~~swipe in a direction where there isn't an adjacent page, the view will not move~~ (not availabe)
* [x] tap the back button in the header to zoom back out to the Project view
**Project View**
* [x] the Project View is centered on the page you were just viewing
* [x] tap the menu (⋮) to reveal the share option
* [x] tap Share option to see a list of applications
* [x] tap anywhere to cancel
* [x] tap the back to exit the project and return to Discover mode | 1.0 | Webmaker 1.5 Android Viewing Project - * [x] Open the app and tap the Discover tab, which opens the Discover view
**Discover View**
* [x] In the Discover view you see a list of projects. Each projects includes...
* [x] a title
* [x] a preview image
* [x] an author (indicated in blue)
* [x] scroll up and down to view additional projects
* [x] tap on any project in the Discover view, it will open
**Project Play Mode**
* [x] when the project opens, the header title is "Play"
* [x] you see a grid of pages
* [x] pinch to zoom in and out
* [x] drag to pan the view
* [x] tap a page to enter the Page view
**Page View**
* [x] In the Page view, you see the page you tapped previously, but zoomed in
* [x] there are arrows on the edge of the page that point to any adjacent pages
* [x] tapping an arrow moves the view to the adjacent page in that direction
* [ ] ~~swiping the page in the direction of any of the arrows also moves the view to the adjacent page~~ (not availabe)
* [ ] ~~the view animates to the adjacent page smoothly~~ (not availabe)
* [ ] ~~swipe in a direction where there isn't an adjacent page, the view will not move~~ (not availabe)
* [x] tap the back button in the header to zoom back out to the Project view
**Project View**
* [x] the Project View is centered on the page you were just viewing
* [x] tap the menu (⋮) to reveal the share option
* [x] tap Share option to see a list of applications
* [x] tap anywhere to cancel
* [x] tap the back to exit the project and return to Discover mode | non_priority | webmaker android viewing project open the app and tap the discover tab which opens the discover view discover view in the discover view you see a list of projects each projects includes a title a preview image an author indicated in blue scroll up and down to view additional projects tap on any project in the discover view it will open project play mode when the project opens the header title is play you see a grid of pages pinch to zoom in and out drag to pan the view tap a page to enter the page view page view in the page view you see the page you tapped previously but zoomed in there are arrows on the edge of the page that point to any adjacent pages tapping an arrow moves the view to the adjacent page in that direction swiping the page in the direction of any of the arrows also moves the view to the adjacent page not availabe the view animates to the adjacent page smoothly not availabe swipe in a direction where there isn t an adjacent page the view will not move not availabe tap the back button in the header to zoom back out to the project view project view the project view is centered on the page you were just viewing tap the menu ⋮ to reveal the share option tap share option to see a list of applications tap anywhere to cancel tap the back to exit the project and return to discover mode | 0 |
289,575 | 24,998,641,694 | IssuesEvent | 2022-11-03 04:48:53 | csssbot/testing | https://api.github.com/repos/csssbot/testing | closed | New review for CPSC 100 by Test | octokit test | > Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
>
> Difficulty: 3.5/5
> Overall: 2.5/5
> <cite><a href="https://test.com">Test</a>, Sep 22 2022</cite>
<details><summary>View YAML to copy</summary><pre>- author: Test
authorLink: https://test.com
date: 2022-08-22
review: |
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
difficulty: 3.5
quality: 2.5</pre></details> | 1.0 | New review for CPSC 100 by Test - > Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
>
> Difficulty: 3.5/5
> Overall: 2.5/5
> <cite><a href="https://test.com">Test</a>, Sep 22 2022</cite>
<details><summary>View YAML to copy</summary><pre>- author: Test
authorLink: https://test.com
date: 2022-08-22
review: |
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
difficulty: 3.5
quality: 2.5</pre></details> | non_priority | new review for cpsc by test lorem ipsum dolor sit amet consectetur adipiscing elit sed do eiusmod tempor incididunt ut labore et dolore magna aliqua ut enim ad minim veniam quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur excepteur sint occaecat cupidatat non proident sunt in culpa qui officia deserunt mollit anim id est laborum difficulty overall view yaml to copy author test authorlink date review lorem ipsum dolor sit amet consectetur adipiscing elit sed do eiusmod tempor incididunt ut labore et dolore magna aliqua ut enim ad minim veniam quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur excepteur sint occaecat cupidatat non proident sunt in culpa qui officia deserunt mollit anim id est laborum difficulty quality | 0 |
79,441 | 15,586,151,952 | IssuesEvent | 2021-03-18 01:17:25 | logicalguru/WG | https://api.github.com/repos/logicalguru/WG | opened | CVE-2020-8908 (Low) detected in guava-18.0.jar | security vulnerability | ## CVE-2020-8908 - Low Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>guava-18.0.jar</b></p></summary>
<p>Guava is a suite of core and expanded libraries that include
utility classes, google's collections, io classes, and much
much more.
Guava has only one code dependency - javax.annotation,
per the JSR-305 spec.</p>
<p>Library home page: <a href="http://code.google.com/p/guava-libraries">http://code.google.com/p/guava-libraries</a></p>
<p>Path to dependency file: /WG/webgoat-container/pom.xml</p>
<p>Path to vulnerable library: 2/repository/com/google/guava/guava/18.0/guava-18.0.jar,2/repository/com/google/guava/guava/18.0/guava-18.0.jar</p>
<p>
Dependency Hierarchy:
- :x: **guava-18.0.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A temp directory creation vulnerability exists in all versions of Guava, allowing an attacker with access to the machine to potentially access data in a temporary directory created by the Guava API com.google.common.io.Files.createTempDir(). By default, on unix-like systems, the created directory is world-readable (readable by an attacker with access to the system). The method in question has been marked @Deprecated in versions 30.0 and later and should not be used. For Android developers, we recommend choosing a temporary directory API provided by Android, such as context.getCacheDir(). For other Java developers, we recommend migrating to the Java 7 API java.nio.file.Files.createTempDirectory() which explicitly configures permissions of 700, or configuring the Java runtime's java.io.tmpdir system property to point to a location whose permissions are appropriately configured.
<p>Publish Date: 2020-12-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8908>CVE-2020-8908</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>3.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8908">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8908</a></p>
<p>Release Date: 2020-12-10</p>
<p>Fix Resolution: v30.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-8908 (Low) detected in guava-18.0.jar - ## CVE-2020-8908 - Low Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>guava-18.0.jar</b></p></summary>
<p>Guava is a suite of core and expanded libraries that include
utility classes, google's collections, io classes, and much
much more.
Guava has only one code dependency - javax.annotation,
per the JSR-305 spec.</p>
<p>Library home page: <a href="http://code.google.com/p/guava-libraries">http://code.google.com/p/guava-libraries</a></p>
<p>Path to dependency file: /WG/webgoat-container/pom.xml</p>
<p>Path to vulnerable library: 2/repository/com/google/guava/guava/18.0/guava-18.0.jar,2/repository/com/google/guava/guava/18.0/guava-18.0.jar</p>
<p>
Dependency Hierarchy:
- :x: **guava-18.0.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A temp directory creation vulnerability exists in all versions of Guava, allowing an attacker with access to the machine to potentially access data in a temporary directory created by the Guava API com.google.common.io.Files.createTempDir(). By default, on unix-like systems, the created directory is world-readable (readable by an attacker with access to the system). The method in question has been marked @Deprecated in versions 30.0 and later and should not be used. For Android developers, we recommend choosing a temporary directory API provided by Android, such as context.getCacheDir(). For other Java developers, we recommend migrating to the Java 7 API java.nio.file.Files.createTempDirectory() which explicitly configures permissions of 700, or configuring the Java runtime's java.io.tmpdir system property to point to a location whose permissions are appropriately configured.
<p>Publish Date: 2020-12-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8908>CVE-2020-8908</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>3.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8908">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8908</a></p>
<p>Release Date: 2020-12-10</p>
<p>Fix Resolution: v30.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve low detected in guava jar cve low severity vulnerability vulnerable library guava jar guava is a suite of core and expanded libraries that include utility classes google s collections io classes and much much more guava has only one code dependency javax annotation per the jsr spec library home page a href path to dependency file wg webgoat container pom xml path to vulnerable library repository com google guava guava guava jar repository com google guava guava guava jar dependency hierarchy x guava jar vulnerable library vulnerability details a temp directory creation vulnerability exists in all versions of guava allowing an attacker with access to the machine to potentially access data in a temporary directory created by the guava api com google common io files createtempdir by default on unix like systems the created directory is world readable readable by an attacker with access to the system the method in question has been marked deprecated in versions and later and should not be used for android developers we recommend choosing a temporary directory api provided by android such as context getcachedir for other java developers we recommend migrating to the java api java nio file files createtempdirectory which explicitly configures permissions of or configuring the java runtime s java io tmpdir system property to point to a location whose permissions are appropriately configured publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
273,405 | 29,820,297,847 | IssuesEvent | 2023-06-17 01:23:23 | Nivaskumark/CVE-2020-0074-frameworks_base_after | https://api.github.com/repos/Nivaskumark/CVE-2020-0074-frameworks_base_after | closed | CVE-2023-20919 (High) detected in baseandroid-11.0.0_r39 - autoclosed | Mend: dependency security vulnerability | ## CVE-2023-20919 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>baseandroid-11.0.0_r39</b></p></summary>
<p>
<p>Android framework classes and services</p>
<p>Library home page: <a href=https://android.googlesource.com/platform/frameworks/base>https://android.googlesource.com/platform/frameworks/base</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Nivaskumark/CVE-2020-0074-frameworks_base/commit/0c69838322e9b0e0108a995e20cd5099881ed0e6">0c69838322e9b0e0108a995e20cd5099881ed0e6</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/core/java/android/provider/Settings.java</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>
In getStringsForPrefix of Settings.java, there is a possible prevention of package uninstallation due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-252663068
<p>Publish Date: 2023-01-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-20919>CVE-2023-20919</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://android.googlesource.com/platform/frameworks/base/+/c224467912010cce927d206366d772f511c98728">https://android.googlesource.com/platform/frameworks/base/+/c224467912010cce927d206366d772f511c98728</a></p>
<p>Release Date: 2022-11-04</p>
<p>Fix Resolution: android-13.0.0_r19</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2023-20919 (High) detected in baseandroid-11.0.0_r39 - autoclosed - ## CVE-2023-20919 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>baseandroid-11.0.0_r39</b></p></summary>
<p>
<p>Android framework classes and services</p>
<p>Library home page: <a href=https://android.googlesource.com/platform/frameworks/base>https://android.googlesource.com/platform/frameworks/base</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Nivaskumark/CVE-2020-0074-frameworks_base/commit/0c69838322e9b0e0108a995e20cd5099881ed0e6">0c69838322e9b0e0108a995e20cd5099881ed0e6</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/core/java/android/provider/Settings.java</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>
In getStringsForPrefix of Settings.java, there is a possible prevention of package uninstallation due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-252663068
<p>Publish Date: 2023-01-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-20919>CVE-2023-20919</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://android.googlesource.com/platform/frameworks/base/+/c224467912010cce927d206366d772f511c98728">https://android.googlesource.com/platform/frameworks/base/+/c224467912010cce927d206366d772f511c98728</a></p>
<p>Release Date: 2022-11-04</p>
<p>Fix Resolution: android-13.0.0_r19</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in baseandroid autoclosed cve high severity vulnerability vulnerable library baseandroid android framework classes and services library home page a href found in head commit a href found in base branch master vulnerable source files core java android provider settings java vulnerability details in getstringsforprefix of settings java there is a possible prevention of package uninstallation due to a logic error in the code this could lead to local escalation of privilege with no additional execution privileges needed user interaction is not needed for exploitation product androidversions android id a publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution android step up your open source security game with mend | 0 |
480 | 3,454,483,835 | IssuesEvent | 2015-12-17 16:06:05 | softlayer/sl-ember-components | https://api.github.com/repos/softlayer/sl-ember-components | opened | Refactor to align with updated style guide | architecture changetype:6 internal ready refactor sl-select | https://github.com/softlayer/ember-style-guide#defining-functions-to-be-called-when-events-are-triggered
* `willClearRender()` - https://github.com/softlayer/sl-ember-components/blob/v0.11.0/addon/components/sl-select.js#L104
* `didInsertElement()` - https://github.com/softlayer/sl-ember-components/blob/v0.11.0/addon/components/sl-select.js#L117 | 1.0 | Refactor to align with updated style guide - https://github.com/softlayer/ember-style-guide#defining-functions-to-be-called-when-events-are-triggered
* `willClearRender()` - https://github.com/softlayer/sl-ember-components/blob/v0.11.0/addon/components/sl-select.js#L104
* `didInsertElement()` - https://github.com/softlayer/sl-ember-components/blob/v0.11.0/addon/components/sl-select.js#L117 | non_priority | refactor to align with updated style guide willclearrender didinsertelement | 0 |
89,437 | 10,599,562,914 | IssuesEvent | 2019-10-10 08:14:42 | gotson/komga | https://api.github.com/repos/gotson/komga | closed | Unclear OS compatibility information, no CUI/GUI on Fat Jar execution | documentation | I first want to thank you for what you are attempting/executing.I have followed other's work on the creation of comic servers namely Tachiyomi-Server (only a client, actually), ubooqity, HappyPanda-X (Most Detailed Metadata+Search), ComicRack. It is awesome to see someone finally adding this func. to Tachiyomi
Even though I kind of settled with Happypanda-X/ComicRack lately, I would like to take this application for a spin, I run Windows 10 Home on the PC that holds my comics. Docker, unfortunately is only Windows 10 Pro. Using the jar, does absolutely nothing, as far as I can tell.
I can also run Ubuntu live on my laptop, and am currently wrangling with wrapping my head getting the container to be created and starting the application.
So I guess my request would be for clearer documentation so that I can know what the application looks like when its running. This might just me being ingorant/dumb, if so my apologies.
| 1.0 | Unclear OS compatibility information, no CUI/GUI on Fat Jar execution - I first want to thank you for what you are attempting/executing.I have followed other's work on the creation of comic servers namely Tachiyomi-Server (only a client, actually), ubooqity, HappyPanda-X (Most Detailed Metadata+Search), ComicRack. It is awesome to see someone finally adding this func. to Tachiyomi
Even though I kind of settled with Happypanda-X/ComicRack lately, I would like to take this application for a spin, I run Windows 10 Home on the PC that holds my comics. Docker, unfortunately is only Windows 10 Pro. Using the jar, does absolutely nothing, as far as I can tell.
I can also run Ubuntu live on my laptop, and am currently wrangling with wrapping my head getting the container to be created and starting the application.
So I guess my request would be for clearer documentation so that I can know what the application looks like when its running. This might just me being ingorant/dumb, if so my apologies.
| non_priority | unclear os compatibility information no cui gui on fat jar execution i first want to thank you for what you are attempting executing i have followed other s work on the creation of comic servers namely tachiyomi server only a client actually ubooqity happypanda x most detailed metadata search comicrack it is awesome to see someone finally adding this func to tachiyomi even though i kind of settled with happypanda x comicrack lately i would like to take this application for a spin i run windows home on the pc that holds my comics docker unfortunately is only windows pro using the jar does absolutely nothing as far as i can tell i can also run ubuntu live on my laptop and am currently wrangling with wrapping my head getting the container to be created and starting the application so i guess my request would be for clearer documentation so that i can know what the application looks like when its running this might just me being ingorant dumb if so my apologies | 0 |
98,562 | 12,339,406,776 | IssuesEvent | 2020-05-14 18:04:26 | unicode-org/icu4x | https://api.github.com/repos/unicode-org/icu4x | closed | How should we build static data? | A-design C-data T-enhancement backlog | When we don't want to perform file or network I/O, it may be necessary to build the data into a binary format that can be built into the Rust static memory space.
We can use a solution like [CBOR](https://github.com/pyfisch/cbor) or [bincode](https://crates.io/crates/bincode).
However, these solutions require parsing the data structure into Rust objects at runtime. That should be pretty quick, and strings buffers could point into the static memory, but a pure Rust static structure would likely be the fastest. However, I have not yet done code size or performance testing. | 1.0 | How should we build static data? - When we don't want to perform file or network I/O, it may be necessary to build the data into a binary format that can be built into the Rust static memory space.
We can use a solution like [CBOR](https://github.com/pyfisch/cbor) or [bincode](https://crates.io/crates/bincode).
However, these solutions require parsing the data structure into Rust objects at runtime. That should be pretty quick, and strings buffers could point into the static memory, but a pure Rust static structure would likely be the fastest. However, I have not yet done code size or performance testing. | non_priority | how should we build static data when we don t want to perform file or network i o it may be necessary to build the data into a binary format that can be built into the rust static memory space we can use a solution like or however these solutions require parsing the data structure into rust objects at runtime that should be pretty quick and strings buffers could point into the static memory but a pure rust static structure would likely be the fastest however i have not yet done code size or performance testing | 0 |
120,202 | 10,109,714,448 | IssuesEvent | 2019-07-30 08:40:00 | khartec/waltz | https://api.github.com/repos/khartec/waltz | closed | Support for licence as an entity in Waltz | DDL change fixed (test & close) noteworthy | Table definition:
```
id | name | description | external_id | created_by / at | last_updated_by / at | provenance
```
Page to view licence definition, which should also include an `approval status` assessment. Bookmarks to be able to reference a destination URL. Also, include the ability to associate applications with licences. | 1.0 | Support for licence as an entity in Waltz - Table definition:
```
id | name | description | external_id | created_by / at | last_updated_by / at | provenance
```
Page to view licence definition, which should also include an `approval status` assessment. Bookmarks to be able to reference a destination URL. Also, include the ability to associate applications with licences. | non_priority | support for licence as an entity in waltz table definition id name description external id created by at last updated by at provenance page to view licence definition which should also include an approval status assessment bookmarks to be able to reference a destination url also include the ability to associate applications with licences | 0 |
348,103 | 24,906,764,573 | IssuesEvent | 2022-10-29 10:54:47 | Azure/terraform-azurerm-caf-enterprise-scale | https://api.github.com/repos/Azure/terraform-azurerm-caf-enterprise-scale | closed | Error received when running custom network connectivity deployment | documentation | <h3 id=communitynote>Community Note </h3>
<ul>
<li>Please vote on this issue by adding a 👍 <a href="https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/">reaction</a> to the original issue to help the community and maintainers prioritize this request </li>
<li>Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request </li>
<li>If you are interested in working on this issue or have submitted a pull request, please leave a comment </li>
</ul>
<h3 id=versions>Versions </h3>
<p><strong>terraform</strong>: v1.1.2 </p>
<p><strong>azure provider</strong>: 3.0.2 </p>
<p><strong>module</strong>: 2.3.1 </p>
<h3 id=description>Description </h3>
<p>Error received when using the "Deploy Connectivity Resources With Custom Settings" configuration guide. Specific error received is: "The given value is not suitable for child module variable "configure<em>connectivity</em>resources" defined at .terraform\modules\enterprise<em>scale\variables.tf:224,1-44: attribute "settings": attribute
│ "hub</em>networks": element 0: attribute "config": attribute "<strong>enable<em>hub</em>network<em>mesh</em>peering</strong>" is required." </p>
<h4 id=describethebug>Describe the bug </h4>
<p>The bug appears to be relating to new functionality within the terraform module for hub network mesh peering, which has a mandatory attribute missing from the <strong>settings.connectivity.tf</strong> </p>
<h4 id=stepstoreproduce>Steps to Reproduce </h4>
<p>Following the "Deploy Connectivity Resources with Custom Settings" guide reproduces the error.
https://github.com/Azure/terraform-azurerm-caf-enterprise-scale/wiki/%5BExamples%5D-Deploy-Connectivity-Resources-With-Custom-Settings </p>
<p>As above, by following the guide here: https://github.com/Azure/terraform-azurerm-caf-enterprise-scale/wiki/%5BExamples%5D-Deploy-Connectivity-Resources-With-Custom-Settings </p>
<h4 id=screenshots>Screenshots </h4>
<p><img src="https://user-images.githubusercontent.com/106317528/186480513-ed23aff6-4178-4ae0-b63b-b1e5904c5a91.png" alt=image> </p>
<h4 id=additionalcontext>Additional context </h4>
<p>I believe adding this line resolves the issue:
<img src="https://user-images.githubusercontent.com/106317528/186480612-6b7a62fe-806a-4aed-9a48-ded844cd23a0.png" alt=image> </p> | 1.0 | Error received when running custom network connectivity deployment - <h3 id=communitynote>Community Note </h3>
<ul>
<li>Please vote on this issue by adding a 👍 <a href="https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/">reaction</a> to the original issue to help the community and maintainers prioritize this request </li>
<li>Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request </li>
<li>If you are interested in working on this issue or have submitted a pull request, please leave a comment </li>
</ul>
<h3 id=versions>Versions </h3>
<p><strong>terraform</strong>: v1.1.2 </p>
<p><strong>azure provider</strong>: 3.0.2 </p>
<p><strong>module</strong>: 2.3.1 </p>
<h3 id=description>Description </h3>
<p>Error received when using the "Deploy Connectivity Resources With Custom Settings" configuration guide. Specific error received is: "The given value is not suitable for child module variable "configure<em>connectivity</em>resources" defined at .terraform\modules\enterprise<em>scale\variables.tf:224,1-44: attribute "settings": attribute
│ "hub</em>networks": element 0: attribute "config": attribute "<strong>enable<em>hub</em>network<em>mesh</em>peering</strong>" is required." </p>
<h4 id=describethebug>Describe the bug </h4>
<p>The bug appears to be relating to new functionality within the terraform module for hub network mesh peering, which has a mandatory attribute missing from the <strong>settings.connectivity.tf</strong> </p>
<h4 id=stepstoreproduce>Steps to Reproduce </h4>
<p>Following the "Deploy Connectivity Resources with Custom Settings" guide reproduces the error.
https://github.com/Azure/terraform-azurerm-caf-enterprise-scale/wiki/%5BExamples%5D-Deploy-Connectivity-Resources-With-Custom-Settings </p>
<p>As above, by following the guide here: https://github.com/Azure/terraform-azurerm-caf-enterprise-scale/wiki/%5BExamples%5D-Deploy-Connectivity-Resources-With-Custom-Settings </p>
<h4 id=screenshots>Screenshots </h4>
<p><img src="https://user-images.githubusercontent.com/106317528/186480513-ed23aff6-4178-4ae0-b63b-b1e5904c5a91.png" alt=image> </p>
<h4 id=additionalcontext>Additional context </h4>
<p>I believe adding this line resolves the issue:
<img src="https://user-images.githubusercontent.com/106317528/186480612-6b7a62fe-806a-4aed-9a48-ded844cd23a0.png" alt=image> </p> | non_priority | error received when running custom network connectivity deployment community note please vote on this issue by adding a please do not leave quot quot or quot me too quot comments they generate extra noise for issue followers and do not help prioritize the request if you are interested in working on this issue or have submitted a pull request please leave a comment versions terraform azure provider module description error received when using the quot deploy connectivity resources with custom settings quot configuration guide specific error received is quot the given value is not suitable for child module variable quot configure connectivity resources quot defined at terraform modules enterprise scale variables tf attribute quot settings quot attribute │ quot hub networks quot element attribute quot config quot attribute quot enable hub network mesh peering quot is required quot describe the bug the bug appears to be relating to new functionality within the terraform module for hub network mesh peering which has a mandatory attribute missing from the settings connectivity tf steps to reproduce following the quot deploy connectivity resources with custom settings quot guide reproduces the error as above by following the guide here screenshots additional context i believe adding this line resolves the issue | 0 |
49,924 | 20,978,796,529 | IssuesEvent | 2022-03-28 17:43:04 | department-of-veterans-affairs/va.gov-team | https://api.github.com/repos/department-of-veterans-affairs/va.gov-team | closed | Clean up Dockerfile and docker-compose yml files | BE autonomous deploys platform-team-focus Console-Services | Clean up dockerfile, getting it “k8s ready”. Refactor docker-compose setup so it doesn’t suck.
## AC
- [ ] Dockerfile is K8s Ready (we may need two Dockerfiles)
- [ ] Development doesn't require rebuilding docker image when files change
- [ ] Dockerfile is compatible with GitHub Actions
- [ ] [Sidekiq workers TSTP cleanly](https://github.com/department-of-veterans-affairs/va.gov-team/issues/26520)
Less is more. | 1.0 | Clean up Dockerfile and docker-compose yml files - Clean up dockerfile, getting it “k8s ready”. Refactor docker-compose setup so it doesn’t suck.
## AC
- [ ] Dockerfile is K8s Ready (we may need two Dockerfiles)
- [ ] Development doesn't require rebuilding docker image when files change
- [ ] Dockerfile is compatible with GitHub Actions
- [ ] [Sidekiq workers TSTP cleanly](https://github.com/department-of-veterans-affairs/va.gov-team/issues/26520)
Less is more. | non_priority | clean up dockerfile and docker compose yml files clean up dockerfile getting it “ ready” refactor docker compose setup so it doesn’t suck ac dockerfile is ready we may need two dockerfiles development doesn t require rebuilding docker image when files change dockerfile is compatible with github actions less is more | 0 |
56,592 | 8,101,379,315 | IssuesEvent | 2018-08-12 13:04:47 | salaros/vtwsclib-php | https://api.github.com/repos/salaros/vtwsclib-php | closed | Update Sales Order, removes Items | bug documentation | When I update an existing Sales order it remove all items from sales order.
Below you can find my code. Please help me to find issue.
I developed my code in 2 styles and every 2 styles has this issue :
1-
function update_sales_order($id)
{
$client = new WSClient(VTIGER_URL, VTIGER_API_USER, VTIGER_API_KEY);
$UpdSOrder = $client->entities->findOneByID('SalesOrder', $id,[] );
$UpdSOrder['invoicestatus'] = 'Cancel';
$UpdSOrder['subject'] = 'TEST2-FOR-IT- ';
$entities = $client->entities->updateOne('SalesOrder', $id, $UpdSOrder);
return $entities;
}
2-
function update_sales_order($id)
{
$client = new WSClient(VTIGER_URL, VTIGER_API_USER, VTIGER_API_KEY);
$UpdSOrder = array(
'invoicestatus' => 'Cancel',
'subject' => 'TEST2-FOR-IT- '
);
$entities = $client->entities->updateOne('SalesOrder', $id, $UpdSOrder);
return $entities;
}
| 1.0 | Update Sales Order, removes Items - When I update an existing Sales order it remove all items from sales order.
Below you can find my code. Please help me to find issue.
I developed my code in 2 styles and every 2 styles has this issue :
1-
function update_sales_order($id)
{
$client = new WSClient(VTIGER_URL, VTIGER_API_USER, VTIGER_API_KEY);
$UpdSOrder = $client->entities->findOneByID('SalesOrder', $id,[] );
$UpdSOrder['invoicestatus'] = 'Cancel';
$UpdSOrder['subject'] = 'TEST2-FOR-IT- ';
$entities = $client->entities->updateOne('SalesOrder', $id, $UpdSOrder);
return $entities;
}
2-
function update_sales_order($id)
{
$client = new WSClient(VTIGER_URL, VTIGER_API_USER, VTIGER_API_KEY);
$UpdSOrder = array(
'invoicestatus' => 'Cancel',
'subject' => 'TEST2-FOR-IT- '
);
$entities = $client->entities->updateOne('SalesOrder', $id, $UpdSOrder);
return $entities;
}
| non_priority | update sales order removes items when i update an existing sales order it remove all items from sales order below you can find my code please help me to find issue i developed my code in styles and every styles has this issue function update sales order id client new wsclient vtiger url vtiger api user vtiger api key updsorder client entities findonebyid salesorder id updsorder cancel updsorder for it entities client entities updateone salesorder id updsorder return entities function update sales order id client new wsclient vtiger url vtiger api user vtiger api key updsorder array invoicestatus cancel subject for it entities client entities updateone salesorder id updsorder return entities | 0 |
44,197 | 12,037,294,693 | IssuesEvent | 2020-04-13 21:31:25 | madchap/deleteme_ghtest | https://api.github.com/repos/madchap/deleteme_ghtest | opened | CVE-2011-3389 - Libgnutls30-3.5.8-5+deb9u4(dpkg) | defectdojo security / medium | *CVE-2011-3389 - Libgnutls30-3.5.8-5+deb9u4(dpkg)*
*Severity:* Medium
*Cve:* CVE-2011-3389
*Product/Engagement:* _ghtest / AdHoc Import - Mon, 13 Apr 2020 21:23:11
*Systems*:
*Description*:
Image hash: sha256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Package: libgnutls30-3.5.8-5+deb9u4
Package path: None
Package type: dpkg
Feed: vulnerabilities/debian:9
CVE: CVE-2011-3389
CPE: None
*Mitigation*:
Upgrade to libgnutls30 None
URL: https://security-tracker.debian.org/tracker/CVE-2011-3389
*Impact*:
tw
*References*:https://security-tracker.debian.org/tracker/CVE-2011-3389 | 1.0 | CVE-2011-3389 - Libgnutls30-3.5.8-5+deb9u4(dpkg) - *CVE-2011-3389 - Libgnutls30-3.5.8-5+deb9u4(dpkg)*
*Severity:* Medium
*Cve:* CVE-2011-3389
*Product/Engagement:* _ghtest / AdHoc Import - Mon, 13 Apr 2020 21:23:11
*Systems*:
*Description*:
Image hash: sha256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Package: libgnutls30-3.5.8-5+deb9u4
Package path: None
Package type: dpkg
Feed: vulnerabilities/debian:9
CVE: CVE-2011-3389
CPE: None
*Mitigation*:
Upgrade to libgnutls30 None
URL: https://security-tracker.debian.org/tracker/CVE-2011-3389
*Impact*:
tw
*References*:https://security-tracker.debian.org/tracker/CVE-2011-3389 | non_priority | cve dpkg cve dpkg severity medium cve cve product engagement ghtest adhoc import mon apr systems description image hash xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx package package path none package type dpkg feed vulnerabilities debian cve cve cpe none mitigation upgrade to none url impact tw references | 0 |
93,037 | 26,844,581,845 | IssuesEvent | 2023-02-03 05:22:22 | open-telemetry/opentelemetry-cpp | https://api.github.com/repos/open-telemetry/opentelemetry-cpp | closed | [BUILD] OTLP HTTP Exporter has build warnings in maintainer mode | bug build and test | Build the OTLP HTTP exporter in maintainer mode:
```
/home/malff/CODE/MY_GITHUB/opentelemetry-cpp/exporters/otlp/src/otlp_metric_utils.cc:269:34: error: unused parameter 'instrument_type' [-Werror,-Wunused-parameter]
sdk::metrics::InstrumentType instrument_type) noexcept
```
To fix:
* fix the relevant build warnings
* fix CI to include WITH_OTLP_HTTP to the maintainer test builds, so this gets detected.
| 1.0 | [BUILD] OTLP HTTP Exporter has build warnings in maintainer mode - Build the OTLP HTTP exporter in maintainer mode:
```
/home/malff/CODE/MY_GITHUB/opentelemetry-cpp/exporters/otlp/src/otlp_metric_utils.cc:269:34: error: unused parameter 'instrument_type' [-Werror,-Wunused-parameter]
sdk::metrics::InstrumentType instrument_type) noexcept
```
To fix:
* fix the relevant build warnings
* fix CI to include WITH_OTLP_HTTP to the maintainer test builds, so this gets detected.
| non_priority | otlp http exporter has build warnings in maintainer mode build the otlp http exporter in maintainer mode home malff code my github opentelemetry cpp exporters otlp src otlp metric utils cc error unused parameter instrument type sdk metrics instrumenttype instrument type noexcept to fix fix the relevant build warnings fix ci to include with otlp http to the maintainer test builds so this gets detected | 0 |
59,821 | 14,478,901,472 | IssuesEvent | 2020-12-10 09:05:10 | olivialancaster/amplify-cli | https://api.github.com/repos/olivialancaster/amplify-cli | opened | CVE-2018-21270 (High) detected in stringstream-0.0.5.tgz | security vulnerability | ## CVE-2018-21270 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>stringstream-0.0.5.tgz</b></p></summary>
<p>Encode and decode streams into string streams</p>
<p>Library home page: <a href="https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz">https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz</a></p>
<p>Path to dependency file: amplify-cli/packages/amplify-category-interactions/package.json</p>
<p>Path to vulnerable library: amplify-cli/packages/amplify-category-interactions/node_modules/npm/node_modules/request/node_modules/stringstream/package.json,amplify-cli/packages/amplify-category-api/node_modules/npm/node_modules/request/node_modules/stringstream/package.json,amplify-cli/packages/amplify-category-function/node_modules/npm/node_modules/request/node_modules/stringstream/package.json,amplify-cli/packages/amplify-cli/node_modules/npm/node_modules/request/node_modules/stringstream/package.json</p>
<p>
Dependency Hierarchy:
- grunt-aws-lambda-0.13.0.tgz (Root Library)
- npm-2.15.12.tgz
- request-2.74.0.tgz
- :x: **stringstream-0.0.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/olivialancaster/amplify-cli/commit/065395613fa8eae16ebfe8c773ef12a8256448b0">065395613fa8eae16ebfe8c773ef12a8256448b0</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).
<p>Publish Date: 2020-12-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-21270>CVE-2018-21270</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.1</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: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21270">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21270</a></p>
<p>Release Date: 2020-12-03</p>
<p>Fix Resolution: 0.0.6</p>
</p>
</details>
<p></p>
| True | CVE-2018-21270 (High) detected in stringstream-0.0.5.tgz - ## CVE-2018-21270 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>stringstream-0.0.5.tgz</b></p></summary>
<p>Encode and decode streams into string streams</p>
<p>Library home page: <a href="https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz">https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz</a></p>
<p>Path to dependency file: amplify-cli/packages/amplify-category-interactions/package.json</p>
<p>Path to vulnerable library: amplify-cli/packages/amplify-category-interactions/node_modules/npm/node_modules/request/node_modules/stringstream/package.json,amplify-cli/packages/amplify-category-api/node_modules/npm/node_modules/request/node_modules/stringstream/package.json,amplify-cli/packages/amplify-category-function/node_modules/npm/node_modules/request/node_modules/stringstream/package.json,amplify-cli/packages/amplify-cli/node_modules/npm/node_modules/request/node_modules/stringstream/package.json</p>
<p>
Dependency Hierarchy:
- grunt-aws-lambda-0.13.0.tgz (Root Library)
- npm-2.15.12.tgz
- request-2.74.0.tgz
- :x: **stringstream-0.0.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/olivialancaster/amplify-cli/commit/065395613fa8eae16ebfe8c773ef12a8256448b0">065395613fa8eae16ebfe8c773ef12a8256448b0</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).
<p>Publish Date: 2020-12-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-21270>CVE-2018-21270</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.1</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: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21270">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21270</a></p>
<p>Release Date: 2020-12-03</p>
<p>Fix Resolution: 0.0.6</p>
</p>
</details>
<p></p>
| non_priority | cve high detected in stringstream tgz cve high severity vulnerability vulnerable library stringstream tgz encode and decode streams into string streams library home page a href path to dependency file amplify cli packages amplify category interactions package json path to vulnerable library amplify cli packages amplify category interactions node modules npm node modules request node modules stringstream package json amplify cli packages amplify category api node modules npm node modules request node modules stringstream package json amplify cli packages amplify category function node modules npm node modules request node modules stringstream package json amplify cli packages amplify cli node modules npm node modules request node modules stringstream package json dependency hierarchy grunt aws lambda tgz root library npm tgz request tgz x stringstream tgz vulnerable library found in head commit a href vulnerability details versions less than of the node js stringstream module are vulnerable to an out of bounds read because of allocation of uninitialized buffers when a number is passed in the input stream when using node js x 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 none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution | 0 |
17,315 | 23,138,122,761 | IssuesEvent | 2022-07-28 15:51:01 | ORNL-AMO/AMO-Tools-Desktop | https://api.github.com/repos/ORNL-AMO/AMO-Tools-Desktop | closed | Add Hydrogen to "Other Fuels" for carbon | Process Heating important CO2 Emissions | Add Hydrogen to teh list of "Other Fuels" for carbon / CO2 calcs.
It has a value of 0 CO2/MMBTU, but the work around for using it is a bit of a pain, so would be better if it had an entry. | 1.0 | Add Hydrogen to "Other Fuels" for carbon - Add Hydrogen to teh list of "Other Fuels" for carbon / CO2 calcs.
It has a value of 0 CO2/MMBTU, but the work around for using it is a bit of a pain, so would be better if it had an entry. | non_priority | add hydrogen to other fuels for carbon add hydrogen to teh list of other fuels for carbon calcs it has a value of mmbtu but the work around for using it is a bit of a pain so would be better if it had an entry | 0 |
181,083 | 21,645,530,556 | IssuesEvent | 2022-05-06 01:03:39 | renfei/start | https://api.github.com/repos/renfei/start | opened | CVE-2022-25647 (High) detected in gson-2.8.6.jar | security vulnerability | ## CVE-2022-25647 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>gson-2.8.6.jar</b></p></summary>
<p>Gson JSON library</p>
<p>Library home page: <a href="https://github.com/google/gson">https://github.com/google/gson</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/google/code/gson/gson/2.8.6/gson-2.8.6.jar</p>
<p>
Dependency Hierarchy:
- aliyun-java-sdk-core-4.5.20.jar (Root Library)
- :x: **gson-2.8.6.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>
The package com.google.code.gson:gson before 2.8.9 are vulnerable to Deserialization of Untrusted Data via the writeReplace() method in internal classes, which may lead to DoS attacks.
<p>Publish Date: 2022-05-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-25647>CVE-2022-25647</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25647`">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25647`</a></p>
<p>Release Date: 2022-05-01</p>
<p>Fix Resolution (com.google.code.gson:gson): 2.8.9</p>
<p>Direct dependency fix Resolution (com.aliyun:aliyun-java-sdk-core): 4.5.28</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-25647 (High) detected in gson-2.8.6.jar - ## CVE-2022-25647 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>gson-2.8.6.jar</b></p></summary>
<p>Gson JSON library</p>
<p>Library home page: <a href="https://github.com/google/gson">https://github.com/google/gson</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/google/code/gson/gson/2.8.6/gson-2.8.6.jar</p>
<p>
Dependency Hierarchy:
- aliyun-java-sdk-core-4.5.20.jar (Root Library)
- :x: **gson-2.8.6.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>
The package com.google.code.gson:gson before 2.8.9 are vulnerable to Deserialization of Untrusted Data via the writeReplace() method in internal classes, which may lead to DoS attacks.
<p>Publish Date: 2022-05-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-25647>CVE-2022-25647</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25647`">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25647`</a></p>
<p>Release Date: 2022-05-01</p>
<p>Fix Resolution (com.google.code.gson:gson): 2.8.9</p>
<p>Direct dependency fix Resolution (com.aliyun:aliyun-java-sdk-core): 4.5.28</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in gson jar cve high severity vulnerability vulnerable library gson jar gson json library library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository com google code gson gson gson jar dependency hierarchy aliyun java sdk core jar root library x gson jar vulnerable library found in base branch master vulnerability details the package com google code gson gson before are vulnerable to deserialization of untrusted data via the writereplace method in internal classes which may lead to dos attacks publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution com google code gson gson direct dependency fix resolution com aliyun aliyun java sdk core step up your open source security game with whitesource | 0 |
241,278 | 18,440,723,088 | IssuesEvent | 2021-10-14 17:45:01 | dmtzs/NierWorldsWeaponManager | https://api.github.com/repos/dmtzs/NierWorldsWeaponManager | opened | Specifications migration | documentation | Migrate to the README file to the documentation part in the wiki, in specifications should be only the technologies used in this project, not commands or other stuffs like that.
That should be in the documentation. | 1.0 | Specifications migration - Migrate to the README file to the documentation part in the wiki, in specifications should be only the technologies used in this project, not commands or other stuffs like that.
That should be in the documentation. | non_priority | specifications migration migrate to the readme file to the documentation part in the wiki in specifications should be only the technologies used in this project not commands or other stuffs like that that should be in the documentation | 0 |
7,509 | 6,925,167,809 | IssuesEvent | 2017-11-30 15:10:36 | OpenLiberty/open-liberty | https://api.github.com/repos/OpenLiberty/open-liberty | closed | Update the metatype description for LdapRegistry to clarify the context pool timeout | in:Security team:Wendigo East | Follow up on fixing a problem with the context pool timeout. The code change is in, updating the context pool timeout description in the metatype for LdapRegistry. | True | Update the metatype description for LdapRegistry to clarify the context pool timeout - Follow up on fixing a problem with the context pool timeout. The code change is in, updating the context pool timeout description in the metatype for LdapRegistry. | non_priority | update the metatype description for ldapregistry to clarify the context pool timeout follow up on fixing a problem with the context pool timeout the code change is in updating the context pool timeout description in the metatype for ldapregistry | 0 |
307,410 | 26,529,824,018 | IssuesEvent | 2023-01-19 11:36:01 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | closed | Fix math.test_tensorflow_argmax | TensorFlow Frontend Sub Task Failing Test | | | |
|---|---|
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/3951396504/jobs/6765195651" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/3951396504/jobs/6765195651" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/3951396504/jobs/6765195651" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/3951396504/jobs/6765195651" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
<details>
<summary>FAILED ivy_tests/test_ivy/test_frontends/test_tensorflow/test_math.py::test_tensorflow_argmax[cpu-ivy.functional.backends.torch-False-False]</summary>
2023-01-18T17:47:30.5918548Z E ivy.exceptions.IvyException: Cannot convert to PyTorch dtype. uint16 is not supported by PyTorch.
2023-01-18T17:47:30.5925510Z E ivy.exceptions.IvyBackendException: torch: as_native_dtype: Cannot convert to PyTorch dtype. uint16 is not supported by PyTorch.
2023-01-18T17:47:30.5935311Z E ivy.exceptions.IvyBackendException: torch: astype: torch: as_native_dtype: Cannot convert to PyTorch dtype. uint16 is not supported by PyTorch.
2023-01-18T17:47:30.5935920Z E Falsifying example: test_tensorflow_argmax(
2023-01-18T17:47:30.5936555Z E dtype_and_x=(['bfloat16'], [array([-1, -1], dtype=bfloat16)], 0),
2023-01-18T17:47:30.5937062Z E output_type='uint16',
2023-01-18T17:47:30.5937623Z E fn_tree='ivy.functional.frontends.tensorflow.math.argmax',
2023-01-18T17:47:30.5938251Z E test_flags=num_positional_args=0. with_out=False. inplace=False. native_arrays=[False]. as_variable=[False]. ,
2023-01-18T17:47:30.5938805Z E frontend='tensorflow',
2023-01-18T17:47:30.5939340Z E on_device='cpu',
2023-01-18T17:47:30.5941629Z E )
2023-01-18T17:47:30.5941998Z E
2023-01-18T17:47:30.5942695Z E You can reproduce this example by temporarily adding @reproduce_failure('6.55.0', b'AXicY2BkAAMoBaaR2GAmAACUAAc=') as a decorator on your test case
</details>
| 1.0 | Fix math.test_tensorflow_argmax - | | |
|---|---|
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/3951396504/jobs/6765195651" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/3951396504/jobs/6765195651" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/3951396504/jobs/6765195651" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/3951396504/jobs/6765195651" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
<details>
<summary>FAILED ivy_tests/test_ivy/test_frontends/test_tensorflow/test_math.py::test_tensorflow_argmax[cpu-ivy.functional.backends.torch-False-False]</summary>
2023-01-18T17:47:30.5918548Z E ivy.exceptions.IvyException: Cannot convert to PyTorch dtype. uint16 is not supported by PyTorch.
2023-01-18T17:47:30.5925510Z E ivy.exceptions.IvyBackendException: torch: as_native_dtype: Cannot convert to PyTorch dtype. uint16 is not supported by PyTorch.
2023-01-18T17:47:30.5935311Z E ivy.exceptions.IvyBackendException: torch: astype: torch: as_native_dtype: Cannot convert to PyTorch dtype. uint16 is not supported by PyTorch.
2023-01-18T17:47:30.5935920Z E Falsifying example: test_tensorflow_argmax(
2023-01-18T17:47:30.5936555Z E dtype_and_x=(['bfloat16'], [array([-1, -1], dtype=bfloat16)], 0),
2023-01-18T17:47:30.5937062Z E output_type='uint16',
2023-01-18T17:47:30.5937623Z E fn_tree='ivy.functional.frontends.tensorflow.math.argmax',
2023-01-18T17:47:30.5938251Z E test_flags=num_positional_args=0. with_out=False. inplace=False. native_arrays=[False]. as_variable=[False]. ,
2023-01-18T17:47:30.5938805Z E frontend='tensorflow',
2023-01-18T17:47:30.5939340Z E on_device='cpu',
2023-01-18T17:47:30.5941629Z E )
2023-01-18T17:47:30.5941998Z E
2023-01-18T17:47:30.5942695Z E You can reproduce this example by temporarily adding @reproduce_failure('6.55.0', b'AXicY2BkAAMoBaaR2GAmAACUAAc=') as a decorator on your test case
</details>
| non_priority | fix math test tensorflow argmax tensorflow img src torch img src numpy img src jax img src failed ivy tests test ivy test frontends test tensorflow test math py test tensorflow argmax e ivy exceptions ivyexception cannot convert to pytorch dtype is not supported by pytorch e ivy exceptions ivybackendexception torch as native dtype cannot convert to pytorch dtype is not supported by pytorch e ivy exceptions ivybackendexception torch astype torch as native dtype cannot convert to pytorch dtype is not supported by pytorch e falsifying example test tensorflow argmax e dtype and x dtype e output type e fn tree ivy functional frontends tensorflow math argmax e test flags num positional args with out false inplace false native arrays as variable e frontend tensorflow e on device cpu e e e you can reproduce this example by temporarily adding reproduce failure b as a decorator on your test case | 0 |
81,069 | 15,603,034,725 | IssuesEvent | 2021-03-19 01:03:21 | k8s-team/asynql | https://api.github.com/repos/k8s-team/asynql | opened | CVE-2021-27291 (Medium) detected in Pygments-2.4.2-py2.py3-none-any.whl | security vulnerability | ## CVE-2021-27291 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Pygments-2.4.2-py2.py3-none-any.whl</b></p></summary>
<p>Pygments is a syntax highlighting package written in Python.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/5c/73/1dfa428150e3ccb0fa3e68db406e5be48698f2a979ccbcec795f28f44048/Pygments-2.4.2-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/5c/73/1dfa428150e3ccb0fa3e68db406e5be48698f2a979ccbcec795f28f44048/Pygments-2.4.2-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /asynql/docs/requirements.txt</p>
<p>Path to vulnerable library: teSource-ArchiveExtractor_c7182848-0dc6-4a0a-8209-5c716eca17c9/20190619005844_75866/20190619005751_depth_0/46/Pygments-2.4.2-py2.py3-none-any/pygments</p>
<p>
Dependency Hierarchy:
- :x: **Pygments-2.4.2-py2.py3-none-any.whl** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In pygments 1.1+, fixed in 2.7.4, the lexers used to parse programming languages rely heavily on regular expressions. Some of the regular expressions have exponential or cubic worst-case complexity and are vulnerable to ReDoS. By crafting malicious input, an attacker can cause a denial of service.
<p>Publish Date: 2021-03-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-27291>CVE-2021-27291</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/pygments/pygments/releases/tag/2.7.4">https://github.com/pygments/pygments/releases/tag/2.7.4</a></p>
<p>Release Date: 2021-03-17</p>
<p>Fix Resolution: Pygments - 2.7.4</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-27291 (Medium) detected in Pygments-2.4.2-py2.py3-none-any.whl - ## CVE-2021-27291 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Pygments-2.4.2-py2.py3-none-any.whl</b></p></summary>
<p>Pygments is a syntax highlighting package written in Python.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/5c/73/1dfa428150e3ccb0fa3e68db406e5be48698f2a979ccbcec795f28f44048/Pygments-2.4.2-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/5c/73/1dfa428150e3ccb0fa3e68db406e5be48698f2a979ccbcec795f28f44048/Pygments-2.4.2-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /asynql/docs/requirements.txt</p>
<p>Path to vulnerable library: teSource-ArchiveExtractor_c7182848-0dc6-4a0a-8209-5c716eca17c9/20190619005844_75866/20190619005751_depth_0/46/Pygments-2.4.2-py2.py3-none-any/pygments</p>
<p>
Dependency Hierarchy:
- :x: **Pygments-2.4.2-py2.py3-none-any.whl** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In pygments 1.1+, fixed in 2.7.4, the lexers used to parse programming languages rely heavily on regular expressions. Some of the regular expressions have exponential or cubic worst-case complexity and are vulnerable to ReDoS. By crafting malicious input, an attacker can cause a denial of service.
<p>Publish Date: 2021-03-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-27291>CVE-2021-27291</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/pygments/pygments/releases/tag/2.7.4">https://github.com/pygments/pygments/releases/tag/2.7.4</a></p>
<p>Release Date: 2021-03-17</p>
<p>Fix Resolution: Pygments - 2.7.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in pygments none any whl cve medium severity vulnerability vulnerable library pygments none any whl pygments is a syntax highlighting package written in python library home page a href path to dependency file asynql docs requirements txt path to vulnerable library tesource archiveextractor depth pygments none any pygments dependency hierarchy x pygments none any whl vulnerable library vulnerability details in pygments fixed in the lexers used to parse programming languages rely heavily on regular expressions some of the regular expressions have exponential or cubic worst case complexity and are vulnerable to redos by crafting malicious input an attacker can cause a denial of service publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution pygments step up your open source security game with whitesource | 0 |
44,506 | 7,111,979,450 | IssuesEvent | 2018-01-17 15:45:04 | thayerAlshaabi/DeepEye | https://api.github.com/repos/thayerAlshaabi/DeepEye | opened | CHAPTER 4: RESULTS | documentation | (5-7 pages)
User Interface Design
----
Design details of your project. This section can include various visualizations (e.g., user interfaces, screenshots) that depict your final project implementation.
Architecture
------
Statement and descriptions of systems and structures (e.g., data structures) used in the implementation of your project. This section should detail the inter- and intra-workings of your software and the systems on which the software relies.
Algorithms
------
Implementations, explanations, and performance of important algorithms in use as part of your project.
Analytical Results
------
Results of quantitative and/or qualitative analysis. This section is most applicable for projects with a data analysis focus or component.
Features
----
Describe the planned features which were implemented. Briefly discuss the planned features that were not implemented.
Testing Results
----
A brief overview of what and how you tested your project code? | 1.0 | CHAPTER 4: RESULTS - (5-7 pages)
User Interface Design
----
Design details of your project. This section can include various visualizations (e.g., user interfaces, screenshots) that depict your final project implementation.
Architecture
------
Statement and descriptions of systems and structures (e.g., data structures) used in the implementation of your project. This section should detail the inter- and intra-workings of your software and the systems on which the software relies.
Algorithms
------
Implementations, explanations, and performance of important algorithms in use as part of your project.
Analytical Results
------
Results of quantitative and/or qualitative analysis. This section is most applicable for projects with a data analysis focus or component.
Features
----
Describe the planned features which were implemented. Briefly discuss the planned features that were not implemented.
Testing Results
----
A brief overview of what and how you tested your project code? | non_priority | chapter results pages user interface design design details of your project this section can include various visualizations e g user interfaces screenshots that depict your final project implementation architecture statement and descriptions of systems and structures e g data structures used in the implementation of your project this section should detail the inter and intra workings of your software and the systems on which the software relies algorithms implementations explanations and performance of important algorithms in use as part of your project analytical results results of quantitative and or qualitative analysis this section is most applicable for projects with a data analysis focus or component features describe the planned features which were implemented briefly discuss the planned features that were not implemented testing results a brief overview of what and how you tested your project code | 0 |
190,038 | 14,531,399,105 | IssuesEvent | 2020-12-14 20:43:39 | mswinkels09/finalcapstone | https://api.github.com/repos/mswinkels09/finalcapstone | closed | User can update listed items when item is sold | TEST postman | When user fills out the `"shipping_cost", "shipping_paid", "item_paid", "final_value_fee", "sold_date"` the item is then considered a sold item.
All fields must be filled out to be considered sold.
| 1.0 | User can update listed items when item is sold - When user fills out the `"shipping_cost", "shipping_paid", "item_paid", "final_value_fee", "sold_date"` the item is then considered a sold item.
All fields must be filled out to be considered sold.
| non_priority | user can update listed items when item is sold when user fills out the shipping cost shipping paid item paid final value fee sold date the item is then considered a sold item all fields must be filled out to be considered sold | 0 |
134,771 | 30,182,304,299 | IssuesEvent | 2023-07-04 09:40:54 | Regalis11/Barotrauma | https://api.github.com/repos/Regalis11/Barotrauma | closed | Character reset (removed when dead on round end) | Bug Need more info Code Severe | ### Disclaimers
- [X] I have searched the issue tracker to check if the issue has already been reported.
- [X] My issue happened while using mods.
### What happened?
The character of one of the players in our host's campaign had died and got removed from the save file completely on round end. The player spawned with a new character. There were no traces of the previous character in the save file after when we returned to the lobby, not of his name and not even of his job (Engineer). There was no way to revert it.
**The name of the character was different than the player's name.**
Mod list from a crash file I got at the same time (coincidentally, I crashed when the round ended):
```
Selected content packages: Vanilla, BaroTraumatic Nightmare, Improved Husks, Barotraumatic Creature Pack, Lua For Barotrauma, CsForBarotrauma, AVP-Aliens, Neurotrauma, Neurotrauma Cybernetics, NT Pharmacy, Enhanced Armaments, Enhanced Armaments Neurotrauma Patch, Visual Variety Pack, ADV Beacon Stations, Beacons Extended, EK | Dockyard, EK | Gunnery, Alarms Extended, Custom Fins and Decals (New custom letters added), Submarine Weapon Sound Makeover, Stations from beyond, Movable and Sellable Wrecks, New Wrecks For Barotrauma (With sellable wrecks), Spoon's Pirate Vessels Expanded, Avali Posters, MoreMissionsMod, Dont Open Debug Console On Errors, BaroCraftables, Acolyte Job, BetterFabricatorUI, No Role Balance v2, BetterHealthUI
Level seed: YasaPhoenix Linea
Loaded submarine: Lucifer (72EC8E70DF927973488714547E0857D2)
Selected screen: Barotrauma.RoundSummaryScreen
SteamManager initialized
Client (Round hadn't been started)
```
### Reproduction steps
unknown
### Bug prevalence
Just once
### Version
0.19.14.0
### -
_No response_
### Which operating system did you encounter this bug on?
Windows
### Relevant error messages and crash reports
_No response_ | 1.0 | Character reset (removed when dead on round end) - ### Disclaimers
- [X] I have searched the issue tracker to check if the issue has already been reported.
- [X] My issue happened while using mods.
### What happened?
The character of one of the players in our host's campaign had died and got removed from the save file completely on round end. The player spawned with a new character. There were no traces of the previous character in the save file after when we returned to the lobby, not of his name and not even of his job (Engineer). There was no way to revert it.
**The name of the character was different than the player's name.**
Mod list from a crash file I got at the same time (coincidentally, I crashed when the round ended):
```
Selected content packages: Vanilla, BaroTraumatic Nightmare, Improved Husks, Barotraumatic Creature Pack, Lua For Barotrauma, CsForBarotrauma, AVP-Aliens, Neurotrauma, Neurotrauma Cybernetics, NT Pharmacy, Enhanced Armaments, Enhanced Armaments Neurotrauma Patch, Visual Variety Pack, ADV Beacon Stations, Beacons Extended, EK | Dockyard, EK | Gunnery, Alarms Extended, Custom Fins and Decals (New custom letters added), Submarine Weapon Sound Makeover, Stations from beyond, Movable and Sellable Wrecks, New Wrecks For Barotrauma (With sellable wrecks), Spoon's Pirate Vessels Expanded, Avali Posters, MoreMissionsMod, Dont Open Debug Console On Errors, BaroCraftables, Acolyte Job, BetterFabricatorUI, No Role Balance v2, BetterHealthUI
Level seed: YasaPhoenix Linea
Loaded submarine: Lucifer (72EC8E70DF927973488714547E0857D2)
Selected screen: Barotrauma.RoundSummaryScreen
SteamManager initialized
Client (Round hadn't been started)
```
### Reproduction steps
unknown
### Bug prevalence
Just once
### Version
0.19.14.0
### -
_No response_
### Which operating system did you encounter this bug on?
Windows
### Relevant error messages and crash reports
_No response_ | non_priority | character reset removed when dead on round end disclaimers i have searched the issue tracker to check if the issue has already been reported my issue happened while using mods what happened the character of one of the players in our host s campaign had died and got removed from the save file completely on round end the player spawned with a new character there were no traces of the previous character in the save file after when we returned to the lobby not of his name and not even of his job engineer there was no way to revert it the name of the character was different than the player s name mod list from a crash file i got at the same time coincidentally i crashed when the round ended selected content packages vanilla barotraumatic nightmare improved husks barotraumatic creature pack lua for barotrauma csforbarotrauma avp aliens neurotrauma neurotrauma cybernetics nt pharmacy enhanced armaments enhanced armaments neurotrauma patch visual variety pack adv beacon stations beacons extended ek dockyard ek gunnery alarms extended custom fins and decals new custom letters added submarine weapon sound makeover stations from beyond movable and sellable wrecks new wrecks for barotrauma with sellable wrecks spoon s pirate vessels expanded avali posters moremissionsmod dont open debug console on errors barocraftables acolyte job betterfabricatorui no role balance betterhealthui level seed yasaphoenix linea loaded submarine lucifer selected screen barotrauma roundsummaryscreen steammanager initialized client round hadn t been started reproduction steps unknown bug prevalence just once version no response which operating system did you encounter this bug on windows relevant error messages and crash reports no response | 0 |
186,289 | 21,922,862,062 | IssuesEvent | 2022-05-22 20:47:53 | AlexRogalskiy/object-mappers-playground | https://api.github.com/repos/AlexRogalskiy/object-mappers-playground | closed | CVE-2020-14338 (Medium) detected in xercesImpl-2.9.1.jar - autoclosed | security vulnerability | ## CVE-2020-14338 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xercesImpl-2.9.1.jar</b></p></summary>
<p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the
Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI),
a complete framework for building parser components and configurations that is extremely
modular and easy to program.</p>
<p>Path to dependency file: object-mappers-playground/modules/objectmappers-all/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar,/home/wss-scanner/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar</p>
<p>
Dependency Hierarchy:
- milyn-smooks-all-1.7.1.jar (Root Library)
- milyn-commons-1.7.1.jar
- :x: **xercesImpl-2.9.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/object-mappers-playground/commit/ccc3fe199db8575ce11d67be41855d33c5e718ab">ccc3fe199db8575ce11d67be41855d33c5e718ab</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was found in Wildfly's implementation of Xerces, specifically in the way the XMLSchemaValidator class in the JAXP component of Wildfly enforced the "use-grammar-pool-only" feature. This flaw allows a specially-crafted XML file to manipulate the validation process in certain cases. This issue is the same flaw as CVE-2020-14621, which affected OpenJDK, and uses a similar code. This flaw affects all Xerces JBoss versions before 2.12.0.SP3.
<p>Publish Date: 2020-09-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-14338>CVE-2020-14338</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1860054">https://bugzilla.redhat.com/show_bug.cgi?id=1860054</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: xerces:xercesImpl:2.12.0.SP3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-14338 (Medium) detected in xercesImpl-2.9.1.jar - autoclosed - ## CVE-2020-14338 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xercesImpl-2.9.1.jar</b></p></summary>
<p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the
Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI),
a complete framework for building parser components and configurations that is extremely
modular and easy to program.</p>
<p>Path to dependency file: object-mappers-playground/modules/objectmappers-all/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar,/home/wss-scanner/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar</p>
<p>
Dependency Hierarchy:
- milyn-smooks-all-1.7.1.jar (Root Library)
- milyn-commons-1.7.1.jar
- :x: **xercesImpl-2.9.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/object-mappers-playground/commit/ccc3fe199db8575ce11d67be41855d33c5e718ab">ccc3fe199db8575ce11d67be41855d33c5e718ab</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was found in Wildfly's implementation of Xerces, specifically in the way the XMLSchemaValidator class in the JAXP component of Wildfly enforced the "use-grammar-pool-only" feature. This flaw allows a specially-crafted XML file to manipulate the validation process in certain cases. This issue is the same flaw as CVE-2020-14621, which affected OpenJDK, and uses a similar code. This flaw affects all Xerces JBoss versions before 2.12.0.SP3.
<p>Publish Date: 2020-09-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-14338>CVE-2020-14338</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1860054">https://bugzilla.redhat.com/show_bug.cgi?id=1860054</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: xerces:xercesImpl:2.12.0.SP3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in xercesimpl jar autoclosed cve medium severity vulnerability vulnerable library xercesimpl jar is the next generation of high performance fully compliant xml parsers in the apache xerces family this new version of xerces introduces the xerces native interface xni a complete framework for building parser components and configurations that is extremely modular and easy to program path to dependency file object mappers playground modules objectmappers all pom xml path to vulnerable library home wss scanner repository xerces xercesimpl xercesimpl jar home wss scanner repository xerces xercesimpl xercesimpl jar dependency hierarchy milyn smooks all jar root library milyn commons jar x xercesimpl jar vulnerable library found in head commit a href vulnerability details a flaw was found in wildfly s implementation of xerces specifically in the way the xmlschemavalidator class in the jaxp component of wildfly enforced the use grammar pool only feature this flaw allows a specially crafted xml file to manipulate the validation process in certain cases this issue is the same flaw as cve which affected openjdk and uses a similar code this flaw affects all xerces jboss versions before publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution xerces xercesimpl step up your open source security game with whitesource | 0 |
336,707 | 30,217,337,629 | IssuesEvent | 2023-07-05 16:30:20 | BoBAdministration/QA-Bug-Reports | https://api.github.com/repos/BoBAdministration/QA-Bug-Reports | closed | Acro doesnt have its idle animation in its emote wheel | Fixed-PendingTesting | **Describe the Bug**
Acro doesnt have its idle animation in the emote wheel
**To Reproduce**
1. log into tester server
2. spawn in as acro
3. open emote menu
**Expected behavior**
emote menu has idle anim
**Actual behavior**
emote menu does not have idle anim
**Screenshots & Video**
**Branch Version**
Tester
**Character Information**
1.2 Acro
**Additional Information**
Tested on titania | 1.0 | Acro doesnt have its idle animation in its emote wheel - **Describe the Bug**
Acro doesnt have its idle animation in the emote wheel
**To Reproduce**
1. log into tester server
2. spawn in as acro
3. open emote menu
**Expected behavior**
emote menu has idle anim
**Actual behavior**
emote menu does not have idle anim
**Screenshots & Video**
**Branch Version**
Tester
**Character Information**
1.2 Acro
**Additional Information**
Tested on titania | non_priority | acro doesnt have its idle animation in its emote wheel describe the bug acro doesnt have its idle animation in the emote wheel to reproduce log into tester server spawn in as acro open emote menu expected behavior emote menu has idle anim actual behavior emote menu does not have idle anim screenshots video branch version tester character information acro additional information tested on titania | 0 |
132,283 | 10,739,983,269 | IssuesEvent | 2019-10-29 17:19:50 | pantsbuild/pants | https://api.github.com/repos/pantsbuild/pants | closed | Remoting: Request had invalid authentication credentials | flaky-test | E.g.
```
<snip>
Computing MultiPlatformExecuteProcess(MultiPlatformExecuteProcessRequest({(None, None): ExecuteProcessRequest { argv: ["python", "./pytest-with-requirements.pex", "pants_test/backend/jvm/tasks/test_scope_runtime_integration.py"], env: {"LANG": "en_US.UTF-8", "LC_ALL": "en_US.UTF-8", "PATH": "/opt/pyenv/versions/3.6.7/bin:/opt/pyenv/libexec:/opt/pyenv/plugins/python-build/bin:/usr/lib/jvm/java-8-openjdk-amd64/jre/bin:/home/travis/.rvm/gems/ruby-2.5.3/bin:/home/travis/.rvm/gems/ruby-2.5.3@global/bin:/home/travis/.rvm/rubies/ruby-2.5.3/bin:/home/travis/.rvm/bin:/home/travis/virtualenv/python2.7.15/bin:/opt/pyenv/shims:/home/travis/bin:/home/travis/.local/bin:/usr/local/lib/jvm/openjdk11/bin:/opt/pyenv/shims:/home/travis/.phpenv/shims:/home/travis/perl5/perlbrew/bin:/home/travis/.nvm/versions/node/v8.12.0/bin:/home/travis/gopath/bin:/home/travis/.gimme/versions/go1.11.1.linux.amd64/bin:/usr/local/maven-3.6.0/bin:/usr/local/cmake-3.12.4/bin:/usr/local/clang-7.0.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/home/travis/.phpenv/bin:/opt/pyenv/bin:/home/travis/.yarn/bin:/pyenv-docker-build/versions/3.7.3/bin:/pyenv-docker-build/versions/3.6.8/bin:/pyenv-docker-build/versions/2.7.15/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/go/bin", "PEX_IGNORE_RCFILES": "true", "PEX_INHERIT_PATH": "false", "PEX_ROOT": "./pex_root"}, input_files: Digest(Fingerprint<59187b4d4fd63c8ab41cfe4217ef7023abaabac9a615107a800aa6f01d50885d>, 1298), output_files: {}, output_directories: {}, timeout: 900s, description: "Run Pytest for tests/python/pants_test/backend/jvm/tasks:scope_runtime_integration", unsafe_local_only_files_because_we_favor_speed_over_correctness_for_this_rule: Digest(Fingerprint<e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855>, 0), jdk_home: None, target_platform: None }})
Throw(Failed to execute process: Unauthenticated: "Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.")
Traceback (no traceback):
<pants native internals>
Exception: Failed to execute process: Unauthenticated: "Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project."
<snip>
``` | 1.0 | Remoting: Request had invalid authentication credentials - E.g.
```
<snip>
Computing MultiPlatformExecuteProcess(MultiPlatformExecuteProcessRequest({(None, None): ExecuteProcessRequest { argv: ["python", "./pytest-with-requirements.pex", "pants_test/backend/jvm/tasks/test_scope_runtime_integration.py"], env: {"LANG": "en_US.UTF-8", "LC_ALL": "en_US.UTF-8", "PATH": "/opt/pyenv/versions/3.6.7/bin:/opt/pyenv/libexec:/opt/pyenv/plugins/python-build/bin:/usr/lib/jvm/java-8-openjdk-amd64/jre/bin:/home/travis/.rvm/gems/ruby-2.5.3/bin:/home/travis/.rvm/gems/ruby-2.5.3@global/bin:/home/travis/.rvm/rubies/ruby-2.5.3/bin:/home/travis/.rvm/bin:/home/travis/virtualenv/python2.7.15/bin:/opt/pyenv/shims:/home/travis/bin:/home/travis/.local/bin:/usr/local/lib/jvm/openjdk11/bin:/opt/pyenv/shims:/home/travis/.phpenv/shims:/home/travis/perl5/perlbrew/bin:/home/travis/.nvm/versions/node/v8.12.0/bin:/home/travis/gopath/bin:/home/travis/.gimme/versions/go1.11.1.linux.amd64/bin:/usr/local/maven-3.6.0/bin:/usr/local/cmake-3.12.4/bin:/usr/local/clang-7.0.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/home/travis/.phpenv/bin:/opt/pyenv/bin:/home/travis/.yarn/bin:/pyenv-docker-build/versions/3.7.3/bin:/pyenv-docker-build/versions/3.6.8/bin:/pyenv-docker-build/versions/2.7.15/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/go/bin", "PEX_IGNORE_RCFILES": "true", "PEX_INHERIT_PATH": "false", "PEX_ROOT": "./pex_root"}, input_files: Digest(Fingerprint<59187b4d4fd63c8ab41cfe4217ef7023abaabac9a615107a800aa6f01d50885d>, 1298), output_files: {}, output_directories: {}, timeout: 900s, description: "Run Pytest for tests/python/pants_test/backend/jvm/tasks:scope_runtime_integration", unsafe_local_only_files_because_we_favor_speed_over_correctness_for_this_rule: Digest(Fingerprint<e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855>, 0), jdk_home: None, target_platform: None }})
Throw(Failed to execute process: Unauthenticated: "Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.")
Traceback (no traceback):
<pants native internals>
Exception: Failed to execute process: Unauthenticated: "Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project."
<snip>
``` | non_priority | remoting request had invalid authentication credentials e g computing multiplatformexecuteprocess multiplatformexecuteprocessrequest none none executeprocessrequest argv env lang en us utf lc all en us utf path opt pyenv versions bin opt pyenv libexec opt pyenv plugins python build bin usr lib jvm java openjdk jre bin home travis rvm gems ruby bin home travis rvm gems ruby global bin home travis rvm rubies ruby bin home travis rvm bin home travis virtualenv bin opt pyenv shims home travis bin home travis local bin usr local lib jvm bin opt pyenv shims home travis phpenv shims home travis perlbrew bin home travis nvm versions node bin home travis gopath bin home travis gimme versions linux bin usr local maven bin usr local cmake bin usr local clang bin usr local sbin usr local bin usr sbin usr bin sbin bin snap bin home travis phpenv bin opt pyenv bin home travis yarn bin pyenv docker build versions bin pyenv docker build versions bin pyenv docker build versions bin usr local sbin usr local bin usr sbin usr bin sbin bin usr local go bin pex ignore rcfiles true pex inherit path false pex root pex root input files digest fingerprint output files output directories timeout description run pytest for tests python pants test backend jvm tasks scope runtime integration unsafe local only files because we favor speed over correctness for this rule digest fingerprint jdk home none target platform none throw failed to execute process unauthenticated request had invalid authentication credentials expected oauth access token login cookie or other valid authentication credential see traceback no traceback exception failed to execute process unauthenticated request had invalid authentication credentials expected oauth access token login cookie or other valid authentication credential see | 0 |
102,633 | 16,576,205,217 | IssuesEvent | 2021-05-31 05:24:01 | AlexRogalskiy/github-action-file-size | https://api.github.com/repos/AlexRogalskiy/github-action-file-size | opened | CVE-2021-33502 (High) detected in normalize-url-6.0.0.tgz | security vulnerability | ## CVE-2021-33502 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>normalize-url-6.0.0.tgz</b></p></summary>
<p>Normalize a URL</p>
<p>Library home page: <a href="https://registry.npmjs.org/normalize-url/-/normalize-url-6.0.0.tgz">https://registry.npmjs.org/normalize-url/-/normalize-url-6.0.0.tgz</a></p>
<p>Path to dependency file: github-action-file-size/package.json</p>
<p>Path to vulnerable library: github-action-file-size/node_modules/normalize-url/package.json</p>
<p>
Dependency Hierarchy:
- npm-7.1.1.tgz (Root Library)
- :x: **normalize-url-6.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/github-action-file-size/commit/3b8b0842d85a1411f9408da2dab5d65e158f73a2">3b8b0842d85a1411f9408da2dab5d65e158f73a2</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.
<p>Publish Date: 2021-05-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33502>CVE-2021-33502</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502</a></p>
<p>Release Date: 2021-05-24</p>
<p>Fix Resolution: normalize-url - 4.5.1, 5.3.1, 6.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-33502 (High) detected in normalize-url-6.0.0.tgz - ## CVE-2021-33502 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>normalize-url-6.0.0.tgz</b></p></summary>
<p>Normalize a URL</p>
<p>Library home page: <a href="https://registry.npmjs.org/normalize-url/-/normalize-url-6.0.0.tgz">https://registry.npmjs.org/normalize-url/-/normalize-url-6.0.0.tgz</a></p>
<p>Path to dependency file: github-action-file-size/package.json</p>
<p>Path to vulnerable library: github-action-file-size/node_modules/normalize-url/package.json</p>
<p>
Dependency Hierarchy:
- npm-7.1.1.tgz (Root Library)
- :x: **normalize-url-6.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/github-action-file-size/commit/3b8b0842d85a1411f9408da2dab5d65e158f73a2">3b8b0842d85a1411f9408da2dab5d65e158f73a2</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.
<p>Publish Date: 2021-05-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33502>CVE-2021-33502</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502</a></p>
<p>Release Date: 2021-05-24</p>
<p>Fix Resolution: normalize-url - 4.5.1, 5.3.1, 6.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in normalize url tgz cve high severity vulnerability vulnerable library normalize url tgz normalize a url library home page a href path to dependency file github action file size package json path to vulnerable library github action file size node modules normalize url package json dependency hierarchy npm tgz root library x normalize url tgz vulnerable library found in head commit a href vulnerability details the normalize url package before x before and x before for node js has a redos regular expression denial of service issue because it has exponential performance for data urls publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution normalize url step up your open source security game with whitesource | 0 |
132,981 | 12,528,778,693 | IssuesEvent | 2020-06-04 10:08:45 | saidfathalla/Science-knowledge-graph-ontologies | https://api.github.com/repos/saidfathalla/Science-knowledge-graph-ontologies | closed | [Improvement] for ModSci ontology | documentation enhancement | **Is your feature request related to a problem? Please describe.**
no.
For ModSci ontology:
I'd suggest integrating several existing taxonomies of research fields, such as Field of Research (FoR) by ANZSRC and Dewey Decimal Classification scheme. | 1.0 | [Improvement] for ModSci ontology - **Is your feature request related to a problem? Please describe.**
no.
For ModSci ontology:
I'd suggest integrating several existing taxonomies of research fields, such as Field of Research (FoR) by ANZSRC and Dewey Decimal Classification scheme. | non_priority | for modsci ontology is your feature request related to a problem please describe no for modsci ontology i d suggest integrating several existing taxonomies of research fields such as field of research for by anzsrc and dewey decimal classification scheme | 0 |
7,636 | 3,105,830,633 | IssuesEvent | 2015-08-31 23:14:23 | rackerlabs/encore-ui | https://api.github.com/repos/rackerlabs/encore-ui | closed | Add something about distributed LESS files to styleguide | documentation | Once https://github.com/rackerlabs/encore-ui/pull/901 gets merged in, we need to think about how to address this in the style guide. | 1.0 | Add something about distributed LESS files to styleguide - Once https://github.com/rackerlabs/encore-ui/pull/901 gets merged in, we need to think about how to address this in the style guide. | non_priority | add something about distributed less files to styleguide once gets merged in we need to think about how to address this in the style guide | 0 |
171,303 | 20,961,350,967 | IssuesEvent | 2022-03-27 21:00:20 | jmservera/videochat-webapp | https://api.github.com/repos/jmservera/videochat-webapp | opened | CVE-2020-7788 (High) detected in ini-1.3.5.tgz | security vulnerability | ## CVE-2020-7788 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ini-1.3.5.tgz</b></p></summary>
<p>An ini encoder/decoder for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/ini/-/ini-1.3.5.tgz">https://registry.npmjs.org/ini/-/ini-1.3.5.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/ini/package.json</p>
<p>
Dependency Hierarchy:
- nodemon-2.0.3.tgz (Root Library)
- update-notifier-4.1.0.tgz
- is-installed-globally-0.3.2.tgz
- global-dirs-2.0.1.tgz
- :x: **ini-1.3.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/jmservera/videochat-webapp/commit/9f550a8f401e799aaead2709d1ff63340172d99d">9f550a8f401e799aaead2709d1ff63340172d99d</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
This affects the package ini before 1.3.6. If an attacker submits a malicious INI file to an application that parses it with ini.parse, they will pollute the prototype on the application. This can be exploited further depending on the context.
<p>Publish Date: 2020-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7788>CVE-2020-7788</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.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7788">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7788</a></p>
<p>Release Date: 2020-12-11</p>
<p>Fix Resolution (ini): 1.3.6</p>
<p>Direct dependency fix Resolution (nodemon): 2.0.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-7788 (High) detected in ini-1.3.5.tgz - ## CVE-2020-7788 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ini-1.3.5.tgz</b></p></summary>
<p>An ini encoder/decoder for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/ini/-/ini-1.3.5.tgz">https://registry.npmjs.org/ini/-/ini-1.3.5.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/ini/package.json</p>
<p>
Dependency Hierarchy:
- nodemon-2.0.3.tgz (Root Library)
- update-notifier-4.1.0.tgz
- is-installed-globally-0.3.2.tgz
- global-dirs-2.0.1.tgz
- :x: **ini-1.3.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/jmservera/videochat-webapp/commit/9f550a8f401e799aaead2709d1ff63340172d99d">9f550a8f401e799aaead2709d1ff63340172d99d</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
This affects the package ini before 1.3.6. If an attacker submits a malicious INI file to an application that parses it with ini.parse, they will pollute the prototype on the application. This can be exploited further depending on the context.
<p>Publish Date: 2020-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7788>CVE-2020-7788</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.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7788">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7788</a></p>
<p>Release Date: 2020-12-11</p>
<p>Fix Resolution (ini): 1.3.6</p>
<p>Direct dependency fix Resolution (nodemon): 2.0.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in ini tgz cve high severity vulnerability vulnerable library ini tgz an ini encoder decoder for node library home page a href path to dependency file package json path to vulnerable library node modules ini package json dependency hierarchy nodemon tgz root library update notifier tgz is installed globally tgz global dirs tgz x ini tgz vulnerable library found in head commit a href found in base branch main vulnerability details this affects the package ini before if an attacker submits a malicious ini file to an application that parses it with ini parse they will pollute the prototype on the application this can be exploited further depending on the context publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution ini direct dependency fix resolution nodemon step up your open source security game with whitesource | 0 |
18,205 | 5,607,139,051 | IssuesEvent | 2017-04-01 02:21:08 | mcsheaj/SPEasyForms | https://api.github.com/repos/mcsheaj/SPEasyForms | closed | Changing the height of SuiteBar Nav causes Overlap Issues with the Settings Page | bug codeplex | **This issue was imported from [CodePlex](http://SPEasyForms.codeplex.com/workitem/23)**
**[mcsheaj](http://www.codeplex.com/site/users/view/mcsheaj)** wrote 2015-02-06 at 18:18
This isn't actually a problem specific to the SuiteBar Nav, changing the height of any part of the header would yield the same results. The worst of the results is that the properties and WYSIWYG both get sized partially off of the page, and you can't
even scroll to the bottom. That's the only part I'm planning to fix in a patch.
In addition, another problem is that there is never a scroll bar on the WYSIWYG side. You can get to the bottom using the keyboard or a mouse wheel when it's properly sized, but the lack of scroll bar is pretty awkward if you have a large form. Fixing this
would actually require a more major overhaul of the UI, and will have to wait until the next major release (i.e. 2015.01). | 1.0 | Changing the height of SuiteBar Nav causes Overlap Issues with the Settings Page - **This issue was imported from [CodePlex](http://SPEasyForms.codeplex.com/workitem/23)**
**[mcsheaj](http://www.codeplex.com/site/users/view/mcsheaj)** wrote 2015-02-06 at 18:18
This isn't actually a problem specific to the SuiteBar Nav, changing the height of any part of the header would yield the same results. The worst of the results is that the properties and WYSIWYG both get sized partially off of the page, and you can't
even scroll to the bottom. That's the only part I'm planning to fix in a patch.
In addition, another problem is that there is never a scroll bar on the WYSIWYG side. You can get to the bottom using the keyboard or a mouse wheel when it's properly sized, but the lack of scroll bar is pretty awkward if you have a large form. Fixing this
would actually require a more major overhaul of the UI, and will have to wait until the next major release (i.e. 2015.01). | non_priority | changing the height of suitebar nav causes overlap issues with the settings page this issue was imported from wrote at this isn t actually a problem specific to the suitebar nav changing the height of any part of the header would yield the same results the worst of the results is that the properties and wysiwyg both get sized partially off of the page and you can t even scroll to the bottom that s the only part i m planning to fix in a patch in addition another problem is that there is never a scroll bar on the wysiwyg side you can get to the bottom using the keyboard or a mouse wheel when it s properly sized but the lack of scroll bar is pretty awkward if you have a large form fixing this would actually require a more major overhaul of the ui and will have to wait until the next major release i e | 0 |
170,752 | 14,269,053,188 | IssuesEvent | 2020-11-21 00:03:43 | zio/zio-redis | https://api.github.com/repos/zio/zio-redis | opened | Document hashes API | documentation good first issue zio-hackathon | The current hashes API (see `zio.redis.api.Hashes`) exposes functions with argument names that are generic and meaningless. I propose to rename those to match those used in the [official documentation](https://redis.io/commands). Additionally, it would be great to provide a small, single-sentence scaladoc for them. | 1.0 | Document hashes API - The current hashes API (see `zio.redis.api.Hashes`) exposes functions with argument names that are generic and meaningless. I propose to rename those to match those used in the [official documentation](https://redis.io/commands). Additionally, it would be great to provide a small, single-sentence scaladoc for them. | non_priority | document hashes api the current hashes api see zio redis api hashes exposes functions with argument names that are generic and meaningless i propose to rename those to match those used in the additionally it would be great to provide a small single sentence scaladoc for them | 0 |
334,805 | 29,992,309,688 | IssuesEvent | 2023-06-26 00:00:50 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | closed | Fix general_functions.test_tensorflow_ones | TensorFlow Frontend Sub Task Failing Test | | | |
|---|---|
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5372121654/jobs/9745312844"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5372121654/jobs/9745312844"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5372121654/jobs/9745312844"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5372121654/jobs/9745312844"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5372121654/jobs/9745312844"><img src=https://img.shields.io/badge/-success-success></a>
| 1.0 | Fix general_functions.test_tensorflow_ones - | | |
|---|---|
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5372121654/jobs/9745312844"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5372121654/jobs/9745312844"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5372121654/jobs/9745312844"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5372121654/jobs/9745312844"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5372121654/jobs/9745312844"><img src=https://img.shields.io/badge/-success-success></a>
| non_priority | fix general functions test tensorflow ones numpy a href src tensorflow a href src jax a href src torch a href src paddle a href src | 0 |
29,868 | 7,127,404,540 | IssuesEvent | 2018-01-20 21:17:48 | elves/elvish | https://api.github.com/repos/elves/elvish | opened | Do not abuse panic for errors | better-code | Currently the Elvish codebase abuses panics for returning errors in the runtime (the `eval` package). This has turned out to cause more problems than it solves. Let's switch to the typical Go style of returning an `error` to indicate an error. | 1.0 | Do not abuse panic for errors - Currently the Elvish codebase abuses panics for returning errors in the runtime (the `eval` package). This has turned out to cause more problems than it solves. Let's switch to the typical Go style of returning an `error` to indicate an error. | non_priority | do not abuse panic for errors currently the elvish codebase abuses panics for returning errors in the runtime the eval package this has turned out to cause more problems than it solves let s switch to the typical go style of returning an error to indicate an error | 0 |
413,433 | 27,952,043,985 | IssuesEvent | 2023-03-24 09:36:17 | jle1001/AI-Music | https://api.github.com/repos/jle1001/AI-Music | opened | documentation: TensorFlow model | documentation | The purpose of this issue is to add the implementation process of the TensorFlow model to the documentation. | 1.0 | documentation: TensorFlow model - The purpose of this issue is to add the implementation process of the TensorFlow model to the documentation. | non_priority | documentation tensorflow model the purpose of this issue is to add the implementation process of the tensorflow model to the documentation | 0 |
307 | 2,571,518,732 | IssuesEvent | 2015-02-10 16:56:59 | Graylog2/graylog2-web-interface | https://api.github.com/repos/Graylog2/graylog2-web-interface | closed | Newlines in message property values not displayed as pre on message detail page. | papercut usability | In the stream view newlines are shown as pre for message property values in the message detail panel in the sidebar. When navigating to a message detail page the newlines are not handled as pre. The div in the sidebar message detail with class `message-detail` gives the nested detail dl -> dd the following css properties.
`.detail-message .description {
word-wrap: break-word;
white-space: pre-wrap;
}`
A similar fix should be applied on the message detail page.
| True | Newlines in message property values not displayed as pre on message detail page. - In the stream view newlines are shown as pre for message property values in the message detail panel in the sidebar. When navigating to a message detail page the newlines are not handled as pre. The div in the sidebar message detail with class `message-detail` gives the nested detail dl -> dd the following css properties.
`.detail-message .description {
word-wrap: break-word;
white-space: pre-wrap;
}`
A similar fix should be applied on the message detail page.
| non_priority | newlines in message property values not displayed as pre on message detail page in the stream view newlines are shown as pre for message property values in the message detail panel in the sidebar when navigating to a message detail page the newlines are not handled as pre the div in the sidebar message detail with class message detail gives the nested detail dl dd the following css properties detail message description word wrap break word white space pre wrap a similar fix should be applied on the message detail page | 0 |
280,914 | 24,344,539,604 | IssuesEvent | 2022-10-02 05:52:06 | hoppscotch/hoppscotch | https://api.github.com/repos/hoppscotch/hoppscotch | closed | [bug]: delete request in the collection is invalid | bug need testing | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behavior
The prompt delete was successful, but it actually exists
### Steps to reproduce
1. click collection button
2. Prompts for deletion
3. click "ok"
4.Check the request and find that it has not been deleted
### Environment
Release
### Version
Local | 1.0 | [bug]: delete request in the collection is invalid - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behavior
The prompt delete was successful, but it actually exists
### Steps to reproduce
1. click collection button
2. Prompts for deletion
3. click "ok"
4.Check the request and find that it has not been deleted
### Environment
Release
### Version
Local | non_priority | delete request in the collection is invalid is there an existing issue for this i have searched the existing issues current behavior the prompt delete was successful but it actually exists steps to reproduce click collection button prompts for deletion click ok check the request and find that it has not been deleted environment release version local | 0 |
234,952 | 18,023,935,231 | IssuesEvent | 2021-09-17 00:12:32 | timescale/docs | https://api.github.com/repos/timescale/docs | opened | [Site Bug] Issue with the page: /timescaledb/latest/getting-started/create-hypertable/ | bug documentation | _Use this template for reporting bugs in the docs._
# Describe the bug
Overall I think the Timescale documentation is excellent, and I really appreciate it. This page is useful. That said, I am technical user but I didn't find the TIP on this page to be helpful:
> TIP
For technically interested readers, the value of the Hypertable is how data is partitioned on disk. The index value is automatically augmented by the time dependency of the data to allow more focused use of memory and query planning resources. While in PostgreSQL (and other Relational Database Management Systems) you can build indexes on one or more values, the data must still be retrieved. Retrieval is in most cases, from portions of the physical layer (memory or disk), which doesn't always result in effective use of memory and disk resources. By automatically partitioning on time, transparently, Hypertables improve the resource usages grouping data into smaller chunks based on time, so that queries and data-stores are much more efficient with time-series data.
The last sentence, in particular, seems to repeat itself and chase its own tail. Maybe it would be better to point technically inclined users to a more complete dive into hypertables, such as https://docs.timescale.com/timescaledb/latest/overview/core-concepts/hypertables-and-chunks/ ? I don't know. | 1.0 | [Site Bug] Issue with the page: /timescaledb/latest/getting-started/create-hypertable/ - _Use this template for reporting bugs in the docs._
# Describe the bug
Overall I think the Timescale documentation is excellent, and I really appreciate it. This page is useful. That said, I am technical user but I didn't find the TIP on this page to be helpful:
> TIP
For technically interested readers, the value of the Hypertable is how data is partitioned on disk. The index value is automatically augmented by the time dependency of the data to allow more focused use of memory and query planning resources. While in PostgreSQL (and other Relational Database Management Systems) you can build indexes on one or more values, the data must still be retrieved. Retrieval is in most cases, from portions of the physical layer (memory or disk), which doesn't always result in effective use of memory and disk resources. By automatically partitioning on time, transparently, Hypertables improve the resource usages grouping data into smaller chunks based on time, so that queries and data-stores are much more efficient with time-series data.
The last sentence, in particular, seems to repeat itself and chase its own tail. Maybe it would be better to point technically inclined users to a more complete dive into hypertables, such as https://docs.timescale.com/timescaledb/latest/overview/core-concepts/hypertables-and-chunks/ ? I don't know. | non_priority | issue with the page timescaledb latest getting started create hypertable use this template for reporting bugs in the docs describe the bug overall i think the timescale documentation is excellent and i really appreciate it this page is useful that said i am technical user but i didn t find the tip on this page to be helpful tip for technically interested readers the value of the hypertable is how data is partitioned on disk the index value is automatically augmented by the time dependency of the data to allow more focused use of memory and query planning resources while in postgresql and other relational database management systems you can build indexes on one or more values the data must still be retrieved retrieval is in most cases from portions of the physical layer memory or disk which doesn t always result in effective use of memory and disk resources by automatically partitioning on time transparently hypertables improve the resource usages grouping data into smaller chunks based on time so that queries and data stores are much more efficient with time series data the last sentence in particular seems to repeat itself and chase its own tail maybe it would be better to point technically inclined users to a more complete dive into hypertables such as i don t know | 0 |
73,683 | 19,760,954,775 | IssuesEvent | 2022-01-16 12:06:13 | Stupid4You/Digit | https://api.github.com/repos/Stupid4You/Digit | opened | Change from the beginning and not when we edit the file. | Easier Build | We now just change the 0000 in the checker then we have lesser code.
if len(str(num)) == 2:
num0 = "00"
if len(str(num)) == 3:
num0 = "0"
if len(str(num)) == 4:
num0 = ""
if num >= 9999:
done = 1 | 1.0 | Change from the beginning and not when we edit the file. - We now just change the 0000 in the checker then we have lesser code.
if len(str(num)) == 2:
num0 = "00"
if len(str(num)) == 3:
num0 = "0"
if len(str(num)) == 4:
num0 = ""
if num >= 9999:
done = 1 | non_priority | change from the beginning and not when we edit the file we now just change the in the checker then we have lesser code if len str num if len str num if len str num if num done | 0 |
185,631 | 15,027,156,241 | IssuesEvent | 2021-02-02 00:09:27 | spring-projects/spring-boot | https://api.github.com/repos/spring-projects/spring-boot | closed | Improve usage description for BufferedApplicationStartup | type: documentation | I was trying the nice new Spring Boot startup tracking feature and used `BufferedApplicationStartup` to collect initialization data. I found that the collected data is drained from the buffer after each request. In particular, it took me a moment to recognize that the most important data is lost after the first request. As discussed with @bclozel this could be emphasized in the documentation, cf. https://stackoverflow.com/questions/65413579/spring-boot-bufferedapplicationstartup-drained-after-first-request
| 1.0 | Improve usage description for BufferedApplicationStartup - I was trying the nice new Spring Boot startup tracking feature and used `BufferedApplicationStartup` to collect initialization data. I found that the collected data is drained from the buffer after each request. In particular, it took me a moment to recognize that the most important data is lost after the first request. As discussed with @bclozel this could be emphasized in the documentation, cf. https://stackoverflow.com/questions/65413579/spring-boot-bufferedapplicationstartup-drained-after-first-request
| non_priority | improve usage description for bufferedapplicationstartup i was trying the nice new spring boot startup tracking feature and used bufferedapplicationstartup to collect initialization data i found that the collected data is drained from the buffer after each request in particular it took me a moment to recognize that the most important data is lost after the first request as discussed with bclozel this could be emphasized in the documentation cf | 0 |
15,383 | 3,955,096,993 | IssuesEvent | 2016-04-29 19:31:54 | facebook/hhvm | https://api.github.com/repos/facebook/hhvm | closed | HHVM-3.3.0 Core dumped: Aborted - stack trace | crash documentation duplicate | We've been running HHVM in production for a few weeks to great effect. Unfortunately it randomly crashed this morning with the line "Core dumped: Aborted". The PHP function it crashed on is a simple text parsing/printing function, called frequently.
The stack trace message mentions "increasing Eval.JitASize, Eval.JitAColdSize, Eval.JitAFrozenSize and Eval.JitGlobalDataSize" -- is there a page somewhere documenting these and/or recommendations on values?
Here's the stack trace:
```
ProcessID: 26834
ThreadID: 7ff179bff700
ThreadPID: 26845
Name: unknown program
Type: Aborted
Runtime: hhvm
Version: tags/HHVM-3.3.0-0-g0a3cfb87b8a353fc7e1d15374f4adc413e37aba9
DebuggerCount: 0
Failed Assertion: /tmp/tmp.0fAfwqfjdP/hphp/runtime/vm/jit/translator.cpp:1937: HPHP::jit::Translator::TranslateResult HPHP::jit::Translator::translateRegion(const HPHP::jit::RegionDesc&, bool, HPHP::jit::Translator::RegionBlacklist&, HPHP::jit::TransFlags): assertion `0' failed.
URL: /
Server: www.gigsalad.com
0: data block = cold
message: Attempted to emit 19 byte(s) into a 69 byte DataBlock with 14 bytes available. This almost certainly means the TC is full. If this is the case, increasing Eval.JitASize, Eval.JitAColdSize, Eval.JitAFrozenSize and Eval.JitGlobalDataSize in the configuration file when running this script or application should fix this problem.
Server_SERVER_NAME: www.gigsalad.com
ThreadType: Web Request
# 0 gsignal at /lib/x86_64-linux-gnu/libc.so.6:0
# 1 abort at /lib/x86_64-linux-gnu/libc.so.6:0
# 2 HPHP::assert_fail(char const*, char const*, unsigned int, char const*) at /usr/bin/hhvm:0
# 3 HPHP::jit::Translator::translateRegion(HPHP::jit::RegionDesc const&, bool, HPHP::hphp_hash_set<HPHP::jit::ProfSrcKey, HPHP::jit::ProfSrcKey::Hasher, std::equal_to<HPHP::jit::ProfSrcKey> >&, HPHP::jit::TransFlags) at /usr/bin/hhvm:0
# 4 HPHP::jit::MCGenerator::translateWork(HPHP::jit::TranslArgs const&) at /usr/bin/hhvm:0
# 5 HPHP::jit::MCGenerator::translate(HPHP::jit::TranslArgs const&) at /usr/bin/hhvm:0
# 6 HPHP::jit::MCGenerator::retranslate(HPHP::jit::TranslArgs const&) at /usr/bin/hhvm:0
# 7 HPHP::jit::MCGenerator::createTranslation(HPHP::jit::TranslArgs const&) at /usr/bin/hhvm:0
# 8 HPHP::jit::MCGenerator::getCallArrayPrologue(HPHP::Func*) at /usr/bin/hhvm:0
# 9 HPHP::jit::funcBodyHelper(HPHP::ActRec*, void*) at /usr/bin/hhvm:0
# 10 HPHP::jit::x64::BackEnd::enterTCHelper(unsigned char*, HPHP::jit::TReqInfo&) at /usr/bin/hhvm:0
# 11 HPHP::jit::MCGenerator::enterTC(unsigned char*, void*) at /usr/bin/hhvm:0
# 12 HPHP::ExecutionContext::enterVM(HPHP::ActRec*, HPHP::ExecutionContext::StackArgsState, HPHP::Resumable*, HPHP::ObjectData*) at /usr/bin/hhvm:0
# 13 HPHP::ExecutionContext::invokeFunc(HPHP::TypedValue*, HPHP::Func const*, HPHP::Variant const&, HPHP::ObjectData*, HPHP::Class*, HPHP::VarEnv*, HPHP::StringData*, HPHP::ExecutionContext::InvokeFlags) at /usr/bin/hhvm:0
# 14 HPHP::ExecutionContext::createFunction(HPHP::String const&, HPHP::String const&) at /usr/bin/hhvm:0
# 15 HPHP::f_create_function(HPHP::String const&, HPHP::String const&) at /usr/bin/hhvm:0
# 16 HPHP::jit::x64::BackEnd::enterTCHelper(unsigned char*, HPHP::jit::TReqInfo&) at /usr/bin/hhvm:0
# 17 HPHP::jit::MCGenerator::enterTC(unsigned char*, void*) at /usr/bin/hhvm:0
# 18 HPHP::ExecutionContext::enterVM(HPHP::ActRec*, HPHP::ExecutionContext::StackArgsState, HPHP::Resumable*, HPHP::ObjectData*) at /usr/bin/hhvm:0
# 19 HPHP::ExecutionContext::invokeFunc(HPHP::TypedValue*, HPHP::Func const*, HPHP::Variant const&, HPHP::ObjectData*, HPHP::Class*, HPHP::VarEnv*, HPHP::StringData*, HPHP::ExecutionContext::InvokeFlags) at /usr/bin/hhvm:0
# 20 HPHP::ExecutionContext::invokeUnit(HPHP::TypedValue*, HPHP::Unit const*) at /usr/bin/hhvm:0
# 21 HPHP::invoke_file(HPHP::String const&, bool, char const*) at builtin-functions.cpp:0
# 22 HPHP::include_impl_invoke(HPHP::String const&, bool, char const*) at /usr/bin/hhvm:0
# 23 HPHP::hphp_invoke(HPHP::ExecutionContext*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool, HPHP::Array const&, HPHP::VRefParamValue const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool&, std::basic_string<char, std::char_traits<char>, std::allocator<char> >&, bool, bool, bool) at /usr/bin/hhvm:0
# 24 HPHP::HttpRequestHandler::executePHPRequest(HPHP::Transport*, HPHP::RequestURI&, HPHP::SourceRootInfo&, bool) at /usr/bin/hhvm:0
# 25 HPHP::HttpRequestHandler::handleRequestImpl(HPHP::Transport*) at /usr/bin/hhvm:0
# 26 HPHP::HttpRequestHandler::handleRequest(HPHP::Transport*) at /usr/bin/hhvm:0
# 27 HPHP::ServerWorker<std::shared_ptr<HPHP::FastCGIJob>, HPHP::FastCGITransportTraits>::doJobImpl(std::shared_ptr<HPHP::FastCGIJob>, bool) at /usr/bin/hhvm:0
# 28 HPHP::ServerWorker<std::shared_ptr<HPHP::FastCGIJob>, HPHP::FastCGITransportTraits>::doJob(std::shared_ptr<HPHP::FastCGIJob>) at /usr/bin/hhvm:0
# 29 HPHP::JobQueueWorker<std::shared_ptr<HPHP::FastCGIJob>, HPHP::Server*, true, false, HPHP::JobQueueDropVMStack>::start() at /usr/bin/hhvm:0
# 30 HPHP::AsyncFuncImpl::ThreadFunc(void*) at /usr/bin/hhvm:0
# 31 start_thread at /lib/x86_64-linux-gnu/libpthread.so.0:0
# 32 clone at /lib/x86_64-linux-gnu/libc.so.6:0
``` | 1.0 | HHVM-3.3.0 Core dumped: Aborted - stack trace - We've been running HHVM in production for a few weeks to great effect. Unfortunately it randomly crashed this morning with the line "Core dumped: Aborted". The PHP function it crashed on is a simple text parsing/printing function, called frequently.
The stack trace message mentions "increasing Eval.JitASize, Eval.JitAColdSize, Eval.JitAFrozenSize and Eval.JitGlobalDataSize" -- is there a page somewhere documenting these and/or recommendations on values?
Here's the stack trace:
```
ProcessID: 26834
ThreadID: 7ff179bff700
ThreadPID: 26845
Name: unknown program
Type: Aborted
Runtime: hhvm
Version: tags/HHVM-3.3.0-0-g0a3cfb87b8a353fc7e1d15374f4adc413e37aba9
DebuggerCount: 0
Failed Assertion: /tmp/tmp.0fAfwqfjdP/hphp/runtime/vm/jit/translator.cpp:1937: HPHP::jit::Translator::TranslateResult HPHP::jit::Translator::translateRegion(const HPHP::jit::RegionDesc&, bool, HPHP::jit::Translator::RegionBlacklist&, HPHP::jit::TransFlags): assertion `0' failed.
URL: /
Server: www.gigsalad.com
0: data block = cold
message: Attempted to emit 19 byte(s) into a 69 byte DataBlock with 14 bytes available. This almost certainly means the TC is full. If this is the case, increasing Eval.JitASize, Eval.JitAColdSize, Eval.JitAFrozenSize and Eval.JitGlobalDataSize in the configuration file when running this script or application should fix this problem.
Server_SERVER_NAME: www.gigsalad.com
ThreadType: Web Request
# 0 gsignal at /lib/x86_64-linux-gnu/libc.so.6:0
# 1 abort at /lib/x86_64-linux-gnu/libc.so.6:0
# 2 HPHP::assert_fail(char const*, char const*, unsigned int, char const*) at /usr/bin/hhvm:0
# 3 HPHP::jit::Translator::translateRegion(HPHP::jit::RegionDesc const&, bool, HPHP::hphp_hash_set<HPHP::jit::ProfSrcKey, HPHP::jit::ProfSrcKey::Hasher, std::equal_to<HPHP::jit::ProfSrcKey> >&, HPHP::jit::TransFlags) at /usr/bin/hhvm:0
# 4 HPHP::jit::MCGenerator::translateWork(HPHP::jit::TranslArgs const&) at /usr/bin/hhvm:0
# 5 HPHP::jit::MCGenerator::translate(HPHP::jit::TranslArgs const&) at /usr/bin/hhvm:0
# 6 HPHP::jit::MCGenerator::retranslate(HPHP::jit::TranslArgs const&) at /usr/bin/hhvm:0
# 7 HPHP::jit::MCGenerator::createTranslation(HPHP::jit::TranslArgs const&) at /usr/bin/hhvm:0
# 8 HPHP::jit::MCGenerator::getCallArrayPrologue(HPHP::Func*) at /usr/bin/hhvm:0
# 9 HPHP::jit::funcBodyHelper(HPHP::ActRec*, void*) at /usr/bin/hhvm:0
# 10 HPHP::jit::x64::BackEnd::enterTCHelper(unsigned char*, HPHP::jit::TReqInfo&) at /usr/bin/hhvm:0
# 11 HPHP::jit::MCGenerator::enterTC(unsigned char*, void*) at /usr/bin/hhvm:0
# 12 HPHP::ExecutionContext::enterVM(HPHP::ActRec*, HPHP::ExecutionContext::StackArgsState, HPHP::Resumable*, HPHP::ObjectData*) at /usr/bin/hhvm:0
# 13 HPHP::ExecutionContext::invokeFunc(HPHP::TypedValue*, HPHP::Func const*, HPHP::Variant const&, HPHP::ObjectData*, HPHP::Class*, HPHP::VarEnv*, HPHP::StringData*, HPHP::ExecutionContext::InvokeFlags) at /usr/bin/hhvm:0
# 14 HPHP::ExecutionContext::createFunction(HPHP::String const&, HPHP::String const&) at /usr/bin/hhvm:0
# 15 HPHP::f_create_function(HPHP::String const&, HPHP::String const&) at /usr/bin/hhvm:0
# 16 HPHP::jit::x64::BackEnd::enterTCHelper(unsigned char*, HPHP::jit::TReqInfo&) at /usr/bin/hhvm:0
# 17 HPHP::jit::MCGenerator::enterTC(unsigned char*, void*) at /usr/bin/hhvm:0
# 18 HPHP::ExecutionContext::enterVM(HPHP::ActRec*, HPHP::ExecutionContext::StackArgsState, HPHP::Resumable*, HPHP::ObjectData*) at /usr/bin/hhvm:0
# 19 HPHP::ExecutionContext::invokeFunc(HPHP::TypedValue*, HPHP::Func const*, HPHP::Variant const&, HPHP::ObjectData*, HPHP::Class*, HPHP::VarEnv*, HPHP::StringData*, HPHP::ExecutionContext::InvokeFlags) at /usr/bin/hhvm:0
# 20 HPHP::ExecutionContext::invokeUnit(HPHP::TypedValue*, HPHP::Unit const*) at /usr/bin/hhvm:0
# 21 HPHP::invoke_file(HPHP::String const&, bool, char const*) at builtin-functions.cpp:0
# 22 HPHP::include_impl_invoke(HPHP::String const&, bool, char const*) at /usr/bin/hhvm:0
# 23 HPHP::hphp_invoke(HPHP::ExecutionContext*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool, HPHP::Array const&, HPHP::VRefParamValue const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool&, std::basic_string<char, std::char_traits<char>, std::allocator<char> >&, bool, bool, bool) at /usr/bin/hhvm:0
# 24 HPHP::HttpRequestHandler::executePHPRequest(HPHP::Transport*, HPHP::RequestURI&, HPHP::SourceRootInfo&, bool) at /usr/bin/hhvm:0
# 25 HPHP::HttpRequestHandler::handleRequestImpl(HPHP::Transport*) at /usr/bin/hhvm:0
# 26 HPHP::HttpRequestHandler::handleRequest(HPHP::Transport*) at /usr/bin/hhvm:0
# 27 HPHP::ServerWorker<std::shared_ptr<HPHP::FastCGIJob>, HPHP::FastCGITransportTraits>::doJobImpl(std::shared_ptr<HPHP::FastCGIJob>, bool) at /usr/bin/hhvm:0
# 28 HPHP::ServerWorker<std::shared_ptr<HPHP::FastCGIJob>, HPHP::FastCGITransportTraits>::doJob(std::shared_ptr<HPHP::FastCGIJob>) at /usr/bin/hhvm:0
# 29 HPHP::JobQueueWorker<std::shared_ptr<HPHP::FastCGIJob>, HPHP::Server*, true, false, HPHP::JobQueueDropVMStack>::start() at /usr/bin/hhvm:0
# 30 HPHP::AsyncFuncImpl::ThreadFunc(void*) at /usr/bin/hhvm:0
# 31 start_thread at /lib/x86_64-linux-gnu/libpthread.so.0:0
# 32 clone at /lib/x86_64-linux-gnu/libc.so.6:0
``` | non_priority | hhvm core dumped aborted stack trace we ve been running hhvm in production for a few weeks to great effect unfortunately it randomly crashed this morning with the line core dumped aborted the php function it crashed on is a simple text parsing printing function called frequently the stack trace message mentions increasing eval jitasize eval jitacoldsize eval jitafrozensize and eval jitglobaldatasize is there a page somewhere documenting these and or recommendations on values here s the stack trace processid threadid threadpid name unknown program type aborted runtime hhvm version tags hhvm debuggercount failed assertion tmp tmp hphp runtime vm jit translator cpp hphp jit translator translateresult hphp jit translator translateregion const hphp jit regiondesc bool hphp jit translator regionblacklist hphp jit transflags assertion failed url server data block cold message attempted to emit byte s into a byte datablock with bytes available this almost certainly means the tc is full if this is the case increasing eval jitasize eval jitacoldsize eval jitafrozensize and eval jitglobaldatasize in the configuration file when running this script or application should fix this problem server server name threadtype web request gsignal at lib linux gnu libc so abort at lib linux gnu libc so hphp assert fail char const char const unsigned int char const at usr bin hhvm hphp jit translator translateregion hphp jit regiondesc const bool hphp hphp hash set hphp jit transflags at usr bin hhvm hphp jit mcgenerator translatework hphp jit translargs const at usr bin hhvm hphp jit mcgenerator translate hphp jit translargs const at usr bin hhvm hphp jit mcgenerator retranslate hphp jit translargs const at usr bin hhvm hphp jit mcgenerator createtranslation hphp jit translargs const at usr bin hhvm hphp jit mcgenerator getcallarrayprologue hphp func at usr bin hhvm hphp jit funcbodyhelper hphp actrec void at usr bin hhvm hphp jit backend entertchelper unsigned char hphp jit treqinfo at usr bin hhvm hphp jit mcgenerator entertc unsigned char void at usr bin hhvm hphp executioncontext entervm hphp actrec hphp executioncontext stackargsstate hphp resumable hphp objectdata at usr bin hhvm hphp executioncontext invokefunc hphp typedvalue hphp func const hphp variant const hphp objectdata hphp class hphp varenv hphp stringdata hphp executioncontext invokeflags at usr bin hhvm hphp executioncontext createfunction hphp string const hphp string const at usr bin hhvm hphp f create function hphp string const hphp string const at usr bin hhvm hphp jit backend entertchelper unsigned char hphp jit treqinfo at usr bin hhvm hphp jit mcgenerator entertc unsigned char void at usr bin hhvm hphp executioncontext entervm hphp actrec hphp executioncontext stackargsstate hphp resumable hphp objectdata at usr bin hhvm hphp executioncontext invokefunc hphp typedvalue hphp func const hphp variant const hphp objectdata hphp class hphp varenv hphp stringdata hphp executioncontext invokeflags at usr bin hhvm hphp executioncontext invokeunit hphp typedvalue hphp unit const at usr bin hhvm hphp invoke file hphp string const bool char const at builtin functions cpp hphp include impl invoke hphp string const bool char const at usr bin hhvm hphp hphp invoke hphp executioncontext std basic string std allocator const bool hphp array const hphp vrefparamvalue const std basic string std allocator const std basic string std allocator const bool std basic string std allocator bool bool bool at usr bin hhvm hphp httprequesthandler executephprequest hphp transport hphp requesturi hphp sourcerootinfo bool at usr bin hhvm hphp httprequesthandler handlerequestimpl hphp transport at usr bin hhvm hphp httprequesthandler handlerequest hphp transport at usr bin hhvm hphp serverworker hphp fastcgitransporttraits dojobimpl std shared ptr bool at usr bin hhvm hphp serverworker hphp fastcgitransporttraits dojob std shared ptr at usr bin hhvm hphp jobqueueworker hphp server true false hphp jobqueuedropvmstack start at usr bin hhvm hphp asyncfuncimpl threadfunc void at usr bin hhvm start thread at lib linux gnu libpthread so clone at lib linux gnu libc so | 0 |
233,944 | 25,784,580,187 | IssuesEvent | 2022-12-09 19:03:59 | MatBenfield/news | https://api.github.com/repos/MatBenfield/news | closed | [SecurityWeek] WAFs of Several Major Vendors Bypassed With Generic Attack Method | SecurityWeek Stale |
**Researchers at industrial and IoT cybersecurity firm Claroty have identified a generic method for bypassing the web application firewalls (WAFs) of several major vendors.**
[read more](https://www.securityweek.com/wafs-several-major-vendors-bypassed-generic-attack-method)
<https://www.securityweek.com/wafs-several-major-vendors-bypassed-generic-attack-method>
| True | [SecurityWeek] WAFs of Several Major Vendors Bypassed With Generic Attack Method -
**Researchers at industrial and IoT cybersecurity firm Claroty have identified a generic method for bypassing the web application firewalls (WAFs) of several major vendors.**
[read more](https://www.securityweek.com/wafs-several-major-vendors-bypassed-generic-attack-method)
<https://www.securityweek.com/wafs-several-major-vendors-bypassed-generic-attack-method>
| non_priority | wafs of several major vendors bypassed with generic attack method researchers at industrial and iot cybersecurity firm claroty have identified a generic method for bypassing the web application firewalls wafs of several major vendors | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.