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 1k | labels stringlengths 4 1.38k | body stringlengths 1 262k | index stringclasses 16
values | text_combine stringlengths 96 262k | label stringclasses 2
values | text stringlengths 96 252k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
77,601 | 10,010,861,599 | IssuesEvent | 2019-07-15 09:07:48 | Xabaril/Esquio | https://api.github.com/repos/Xabaril/Esquio | opened | Consider move azure devops extensions overview doc files | Documentation devops | Hi @lfraile
AzureDevOps extensions overview is not included on our docs directory, used by ReadTheDocs!, can you consider moving the overview.md into doc folder or create a new walkthrought on this topic?
Thanks
| 1.0 | Consider move azure devops extensions overview doc files - Hi @lfraile
AzureDevOps extensions overview is not included on our docs directory, used by ReadTheDocs!, can you consider moving the overview.md into doc folder or create a new walkthrought on this topic?
Thanks
| non_priority | consider move azure devops extensions overview doc files hi lfraile azuredevops extensions overview is not included on our docs directory used by readthedocs can you consider moving the overview md into doc folder or create a new walkthrought on this topic thanks | 0 |
177,243 | 6,576,058,600 | IssuesEvent | 2017-09-11 18:22:05 | opencurrents/opencurrents | https://api.github.com/repos/opencurrents/opencurrents | opened | invite-volunteers: Add personal message to invite-volunteers | mvp priority medium | Personal message should be attached to admin, not the event. This way we can autopopulate the message when an admin creates another event. | 1.0 | invite-volunteers: Add personal message to invite-volunteers - Personal message should be attached to admin, not the event. This way we can autopopulate the message when an admin creates another event. | priority | invite volunteers add personal message to invite volunteers personal message should be attached to admin not the event this way we can autopopulate the message when an admin creates another event | 1 |
69,973 | 13,388,514,737 | IssuesEvent | 2020-09-02 17:29:06 | photonstorm/phaser | https://api.github.com/repos/photonstorm/phaser | closed | Text gets an ultra thin outline after "setText()" | 👩💻 Code example needed | ## Version
* Phaser Version: v3.23.0-FB
* Operating system: Win10
* Browser:
## Description
Text gets an ultra thin outline, which can't be removed, after "setText()" has been called.
## Example Test Code
"Roboto-Bold" is a custom imported font, which works.
```JavaScript
this.sampletext = this.add.text(0, 0, "Sample text", {fixedWidth: 200, align: "center", fontSize: 20 + "px", fontFamily: "Roboto-Bold", color: "#222222"});
// ....
this.sampletext.setText("Sample text 2"); // now text has outline. setting strokeThickness to 0 has no affect.
``` | 1.0 | Text gets an ultra thin outline after "setText()" - ## Version
* Phaser Version: v3.23.0-FB
* Operating system: Win10
* Browser:
## Description
Text gets an ultra thin outline, which can't be removed, after "setText()" has been called.
## Example Test Code
"Roboto-Bold" is a custom imported font, which works.
```JavaScript
this.sampletext = this.add.text(0, 0, "Sample text", {fixedWidth: 200, align: "center", fontSize: 20 + "px", fontFamily: "Roboto-Bold", color: "#222222"});
// ....
this.sampletext.setText("Sample text 2"); // now text has outline. setting strokeThickness to 0 has no affect.
``` | non_priority | text gets an ultra thin outline after settext version phaser version fb operating system browser description text gets an ultra thin outline which can t be removed after settext has been called example test code roboto bold is a custom imported font which works javascript this sampletext this add text sample text fixedwidth align center fontsize px fontfamily roboto bold color this sampletext settext sample text now text has outline setting strokethickness to has no affect | 0 |
100,181 | 4,080,322,487 | IssuesEvent | 2016-05-31 01:05:27 | nim-lang/Nim | https://api.github.com/repos/nim-lang/Nim | closed | Slurp doesn't work with relative imports | Medium Priority Path Handling | Slurp opens files using paths relative to the module using ``slurp``. However this breaks when the module calling ``slurp`` is imported with the ``import path/to/module`` syntax. This can be tested with the following tree structure and files:
```nimrod
# outer.nim
import private/du
show()
# private/du.nim
const txt = slurp"du.nim"
proc show*() =
echo txt
when isMainModule:
show()
```
When ``outer.nim`` is compiled the relative import of ``du.nim`` is unable to find itself, it looks for the file in the directory of ``outer.nim`` instead of ``private/du.nim``.
While this can be solved for projects avoiding relative imports and using the compiler ``--path`` switch or through a config file, it is going to be a problem for [babel packages using relative private imports](https://github.com/nimrod-code/babel/blob/master/developers.markdown#libraries). | 1.0 | Slurp doesn't work with relative imports - Slurp opens files using paths relative to the module using ``slurp``. However this breaks when the module calling ``slurp`` is imported with the ``import path/to/module`` syntax. This can be tested with the following tree structure and files:
```nimrod
# outer.nim
import private/du
show()
# private/du.nim
const txt = slurp"du.nim"
proc show*() =
echo txt
when isMainModule:
show()
```
When ``outer.nim`` is compiled the relative import of ``du.nim`` is unable to find itself, it looks for the file in the directory of ``outer.nim`` instead of ``private/du.nim``.
While this can be solved for projects avoiding relative imports and using the compiler ``--path`` switch or through a config file, it is going to be a problem for [babel packages using relative private imports](https://github.com/nimrod-code/babel/blob/master/developers.markdown#libraries). | priority | slurp doesn t work with relative imports slurp opens files using paths relative to the module using slurp however this breaks when the module calling slurp is imported with the import path to module syntax this can be tested with the following tree structure and files nimrod outer nim import private du show private du nim const txt slurp du nim proc show echo txt when ismainmodule show when outer nim is compiled the relative import of du nim is unable to find itself it looks for the file in the directory of outer nim instead of private du nim while this can be solved for projects avoiding relative imports and using the compiler path switch or through a config file it is going to be a problem for | 1 |
2,392 | 5,190,341,474 | IssuesEvent | 2017-01-21 07:34:30 | nodejs/node | https://api.github.com/repos/nodejs/node | opened | process: misaligned node --help text | good first contribution process | * **Version**: master
* **Platform**: n/a
* **Subsystem**: process
The alignment of the argument descriptions in the `node --help` text is off. Specifically the `--inspect` and `--inspect-brk` options do not match up. Because the full `--inspect-brk` argument name is the longest, all of the other arguments' descriptions may need to be indented a couple of spaces further to accommodate this longer argument name. | 1.0 | process: misaligned node --help text - * **Version**: master
* **Platform**: n/a
* **Subsystem**: process
The alignment of the argument descriptions in the `node --help` text is off. Specifically the `--inspect` and `--inspect-brk` options do not match up. Because the full `--inspect-brk` argument name is the longest, all of the other arguments' descriptions may need to be indented a couple of spaces further to accommodate this longer argument name. | non_priority | process misaligned node help text version master platform n a subsystem process the alignment of the argument descriptions in the node help text is off specifically the inspect and inspect brk options do not match up because the full inspect brk argument name is the longest all of the other arguments descriptions may need to be indented a couple of spaces further to accommodate this longer argument name | 0 |
578,999 | 17,169,815,764 | IssuesEvent | 2021-07-15 01:32:38 | GlowstoneMC/Glowstone | https://api.github.com/repos/GlowstoneMC/Glowstone | closed | Cannot exit fly and other world issues | Category: server feature Priority: minor | Hello i am having some issues already unfortunately.. I just started using this today and i cannot seem to fly without getting stuck in the air. I also have a plugin that cannot register PlayerDeathEvent (i have source to it so if i need, i'll fix it). Other than that once i'm flying, i cannot exit fly and i tend to fly up into the air? Mobs/Animals do not move but they continuously look at me.. The server is also a bit sluggish compared to the spigot jar but i'm not sure if that's just the commands i used to start it or if Windows makes it that way.
I copied the worlds over to the Spigot server and i am still stuck in the air oddly enough.. The mobs move tho.
So far aside from those issues i only have 2 plugins that died and one that half works with no errors.
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/44327796-cannot-exit-fly-and-other-world-issues?utm_campaign=plugin&utm_content=tracker%2F14691067&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F14691067&utm_medium=issues&utm_source=github).
</bountysource-plugin> | 1.0 | Cannot exit fly and other world issues - Hello i am having some issues already unfortunately.. I just started using this today and i cannot seem to fly without getting stuck in the air. I also have a plugin that cannot register PlayerDeathEvent (i have source to it so if i need, i'll fix it). Other than that once i'm flying, i cannot exit fly and i tend to fly up into the air? Mobs/Animals do not move but they continuously look at me.. The server is also a bit sluggish compared to the spigot jar but i'm not sure if that's just the commands i used to start it or if Windows makes it that way.
I copied the worlds over to the Spigot server and i am still stuck in the air oddly enough.. The mobs move tho.
So far aside from those issues i only have 2 plugins that died and one that half works with no errors.
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/44327796-cannot-exit-fly-and-other-world-issues?utm_campaign=plugin&utm_content=tracker%2F14691067&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F14691067&utm_medium=issues&utm_source=github).
</bountysource-plugin> | priority | cannot exit fly and other world issues hello i am having some issues already unfortunately i just started using this today and i cannot seem to fly without getting stuck in the air i also have a plugin that cannot register playerdeathevent i have source to it so if i need i ll fix it other than that once i m flying i cannot exit fly and i tend to fly up into the air mobs animals do not move but they continuously look at me the server is also a bit sluggish compared to the spigot jar but i m not sure if that s just the commands i used to start it or if windows makes it that way i copied the worlds over to the spigot server and i am still stuck in the air oddly enough the mobs move tho so far aside from those issues i only have plugins that died and one that half works with no errors want to back this issue we accept bounties via | 1 |
435,192 | 12,532,574,323 | IssuesEvent | 2020-06-04 16:09:25 | umple/umple | https://api.github.com/repos/umple/umple | closed | State machines cut off in some installations of UmpleOnline | Component-UmpleOnline Diffic-Med Priority-High bug | In some installations of UmpleOnline, state machines are 'cut off' so you can't see them completely. This might be due to the version of graphviz. It may be something wrong with the way the svg is being generated or displayed.
The cutoff seems to be related to percentage and the problem occurs whether or not the diagram is displayed at the right (e.g. with the 'S' button) or at the bottom (i.e. using 'generate and selecting state diagram).
The main server implementation does not seem to have the problem (running 2.38) , but recent installations e.g. generated using graphviz 2.43 do, so any fix will still have to work in all installations. So the version in Docker has the problem
Even downloaded files have the problem. The following are two files one with the problem and one not.
[stateDiagram2.svg.zip](https://github.com/umple/umple/files/4578196/stateDiagram2.svg.zip)
[stateDiagram.svg.zip](https://github.com/umple/umple/files/4578197/stateDiagram.svg.zip)
These files were generated from the DigitalWatch nested example
The problem seems to be fixed if the line 9 that starts
<g id="graph0" class="graph" transform="scale(1.14 1.14) ...
is changed to
<g id="graph0" class="graph" transform="scale(1.00 1.00)
Maybe this could be special-cases so this transformation is done post-generation
| 1.0 | State machines cut off in some installations of UmpleOnline - In some installations of UmpleOnline, state machines are 'cut off' so you can't see them completely. This might be due to the version of graphviz. It may be something wrong with the way the svg is being generated or displayed.
The cutoff seems to be related to percentage and the problem occurs whether or not the diagram is displayed at the right (e.g. with the 'S' button) or at the bottom (i.e. using 'generate and selecting state diagram).
The main server implementation does not seem to have the problem (running 2.38) , but recent installations e.g. generated using graphviz 2.43 do, so any fix will still have to work in all installations. So the version in Docker has the problem
Even downloaded files have the problem. The following are two files one with the problem and one not.
[stateDiagram2.svg.zip](https://github.com/umple/umple/files/4578196/stateDiagram2.svg.zip)
[stateDiagram.svg.zip](https://github.com/umple/umple/files/4578197/stateDiagram.svg.zip)
These files were generated from the DigitalWatch nested example
The problem seems to be fixed if the line 9 that starts
<g id="graph0" class="graph" transform="scale(1.14 1.14) ...
is changed to
<g id="graph0" class="graph" transform="scale(1.00 1.00)
Maybe this could be special-cases so this transformation is done post-generation
| priority | state machines cut off in some installations of umpleonline in some installations of umpleonline state machines are cut off so you can t see them completely this might be due to the version of graphviz it may be something wrong with the way the svg is being generated or displayed the cutoff seems to be related to percentage and the problem occurs whether or not the diagram is displayed at the right e g with the s button or at the bottom i e using generate and selecting state diagram the main server implementation does not seem to have the problem running but recent installations e g generated using graphviz do so any fix will still have to work in all installations so the version in docker has the problem even downloaded files have the problem the following are two files one with the problem and one not these files were generated from the digitalwatch nested example the problem seems to be fixed if the line that starts g id class graph transform scale is changed to g id class graph transform scale maybe this could be special cases so this transformation is done post generation | 1 |
400,275 | 27,276,445,651 | IssuesEvent | 2023-02-23 05:56:22 | ZORALab/Hestia | https://api.github.com/repos/ZORALab/Hestia | closed | Add 404 Page | Documentation Done and Pending Release | # Description
```
Please provide a short description of what you have encountered below.
```
The documentation site does not have a 404 page. Hence, let's add it.
# Link
```
Please provide the documentation link(s) below.
```
`/en/404/`
# Expected Presentation
```
Please specify the expected presentation of the documentation.
```
`/en/404` is available.
# Current Presentation
```
Please specify the current presentation of the documentation.
```
`/en/404` is not available.
# Attachment
```
Please drag and drop the necessary data files (e.g. screenshot, logs, etc)
below.
```
| 1.0 | Add 404 Page - # Description
```
Please provide a short description of what you have encountered below.
```
The documentation site does not have a 404 page. Hence, let's add it.
# Link
```
Please provide the documentation link(s) below.
```
`/en/404/`
# Expected Presentation
```
Please specify the expected presentation of the documentation.
```
`/en/404` is available.
# Current Presentation
```
Please specify the current presentation of the documentation.
```
`/en/404` is not available.
# Attachment
```
Please drag and drop the necessary data files (e.g. screenshot, logs, etc)
below.
```
| non_priority | add page description please provide a short description of what you have encountered below the documentation site does not have a page hence let s add it link please provide the documentation link s below en expected presentation please specify the expected presentation of the documentation en is available current presentation please specify the current presentation of the documentation en is not available attachment please drag and drop the necessary data files e g screenshot logs etc below | 0 |
216,695 | 16,795,773,974 | IssuesEvent | 2021-06-16 03:07:50 | ShaunaMyers/Overlook_Hotel | https://api.github.com/repos/ShaunaMyers/Overlook_Hotel | closed | ## Testing | enhancement testing | - [x] Write tests for all Classes
- [x] Write tests for properties and any methods in classes
- [x] Test anything that updates class properties
- [x] Test for happy and sad paths | 1.0 | ## Testing - - [x] Write tests for all Classes
- [x] Write tests for properties and any methods in classes
- [x] Test anything that updates class properties
- [x] Test for happy and sad paths | non_priority | testing write tests for all classes write tests for properties and any methods in classes test anything that updates class properties test for happy and sad paths | 0 |
778,087 | 27,303,173,799 | IssuesEvent | 2023-02-24 05:05:41 | dvrpc/TrackingProgress | https://api.github.com/repos/dvrpc/TrackingProgress | opened | Mortgage Lending Chart 2(a,b,c,d) | high priority | @hachadorian This is the second of three charts for Mortgage Lending. I'm not doing the visual mockups for this. Hopefully you'll follow along. Let me know if you have question or want to meet.
Source CSVs are here: G:\Shared drives\Socioeconomic and Land Use Analytics\Tracking Progress\Web\Data\Mortgage Lending
### Chart 2a - where "Select Purpose" = All
**Chart Type:** line
**Data File:** mortgage_lending_2a.csv
**Chart Title:** Loan Origination Rates
**Legend Items and CSV header beginnings:**
Legend Label | CSV_Header_Endings
-- | --
Female* | female
Male* | male
Latinx** | latinx
Non-Latinx** | nonlatinx
Non-White*** | minority
Asian to White*** | asian
Black to White*** | black
Other Non-White*** | other
White*** | white
**Drop-down 1 Label:** Select Geography:
**Drop-down 1 List**
Dropdown List | CSV Header Endings
-- | --
DVRPC Region | dvrpc_
NJ Counties | njcos_
PA Suburban Counties | pasubcos_
Bucks | bucks_
Burlington | burl_
Camden | camd_
Chester | ches_
Delaware | del_
Gloucester | glo_
Mercer | mer_
Montgomery | mont_
Philadelphia | phil_
**Drop-down 2 Label:** Select Purpose:
**Drop-down 2 List:** All
**Y Axis Label:** Origination Rate
**Y Axis # format:** xx.x%
**Mouse-over display:** xx.x%
**X axis label:** Year
**Legend Note:** Geography: * Sex, ** Ethnicity, *** Race
**Singular/ Plural Source:** Source:
**Source line:** Federal Financial Institutions Examination Council's (FFIEC) Home Mortgage Disclosure Act (HMDA) Data
### Chart 2b - where "Select Purpose" = Home Purchase
**Chart Type:** line
**Data File:** mortgage_lending_2b.csv
**Chart Title:** Loan Origination Rates
**Legend Items and CSV header beginnings:**
Legend Label | CSV_Header_Endings
-- | --
Female* | female
Male* | male
Latinx** | latinx
Non-Latinx** | nonlatinx
Non-White*** | minority
Asian to White*** | asian
Black to White*** | black
Other Non-White*** | other
White*** | white
**Drop-down 1 Label:** Select Geography:
**Drop-down 1 List**
Dropdown List | CSV Header Endings
-- | --
DVRPC Region | dvrpc_
NJ Counties | njcos_
PA Suburban Counties | pasubcos_
Bucks | bucks_
Burlington | burl_
Camden | camd_
Chester | ches_
Delaware | del_
Gloucester | glo_
Mercer | mer_
Montgomery | mont_
Philadelphia | phil_
**Drop-down 2 Label:** Select Purpose:
**Drop-down 2 List:** Home Purchase
**Y Axis Label:** Origination Rate
**Y Axis # format:** xx.x%
**Mouse-over display:** xx.x%
**X axis label:** Year
**Legend Note:** Geography: * Sex, ** Ethnicity, *** Race
**Singular/ Plural Source:** Source:
**Source line:** Federal Financial Institutions Examination Council's (FFIEC) Home Mortgage Disclosure Act (HMDA) Data
### Chart 2c - where "Select Purpose" = Home Improvement
**Chart Type:** line
**Data File:** mortgage_lending_2c.csv
**Chart Title:** Loan Origination Rates
**Legend Items and CSV header beginnings:**
Legend Label | CSV_Header_Endings
-- | --
Female* | female
Male* | male
Latinx** | latinx
Non-Latinx** | nonlatinx
Non-White*** | minority
Asian to White*** | asian
Black to White*** | black
Other Non-White*** | other
White*** | white
**Drop-down 1 Label:** Select Geography:
**Drop-down 1 List**
Dropdown List | CSV Header Endings
-- | --
DVRPC Region | dvrpc_
NJ Counties | njcos_
PA Suburban Counties | pasubcos_
Bucks | bucks_
Burlington | burl_
Camden | camd_
Chester | ches_
Delaware | del_
Gloucester | glo_
Mercer | mer_
Montgomery | mont_
Philadelphia | phil_
**Drop-down 2 Label:** Select Purpose:
**Drop-down 2 List:** Home Improvement
**Y Axis Label:** Origination Rate
**Y Axis # format:** xx.x%
**Mouse-over display:** xx.x%
**X axis label:** Year
**Legend Note:** Geography: * Sex, ** Ethnicity, *** Race
**Singular/ Plural Source:** Source:
**Source line:** Federal Financial Institutions Examination Council's (FFIEC) Home Mortgage Disclosure Act (HMDA) Data
### Chart 2d - where "Select Purpose" = Refinancing
**Chart Type:** line
**Data File:** mortgage_lending_2d.csv
**Chart Title:** Loan Origination Rates
**Legend Items and CSV header beginnings:**
Legend Label | CSV_Header_Endings
-- | --
Female* | female
Male* | male
Latinx** | latinx
Non-Latinx** | nonlatinx
Non-White*** | minority
Asian to White*** | asian
Black to White*** | black
Other Non-White*** | other
White*** | white
**Drop-down 1 Label:** Select Geography:
**Drop-down 1 List**
Dropdown List | CSV Header Endings
-- | --
DVRPC Region | dvrpc_
NJ Counties | njcos_
PA Suburban Counties | pasubcos_
Bucks | bucks_
Burlington | burl_
Camden | camd_
Chester | ches_
Delaware | del_
Gloucester | glo_
Mercer | mer_
Montgomery | mont_
Philadelphia | phil_
**Drop-down 2 Label:** Select Purpose:
**Drop-down 2 List:** Refinancing
**Y Axis Label:** Origination Rate
**Y Axis # format:** xx.x%
**Mouse-over display:** xx.x%
**X axis label:** Year
**Legend Note:** Geography: * Sex, ** Ethnicity, *** Race
**Singular/ Plural Source:** Source:
**Source line:** Federal Financial Institutions Examination Council's (FFIEC) Home Mortgage Disclosure Act (HMDA) Data
| 1.0 | Mortgage Lending Chart 2(a,b,c,d) - @hachadorian This is the second of three charts for Mortgage Lending. I'm not doing the visual mockups for this. Hopefully you'll follow along. Let me know if you have question or want to meet.
Source CSVs are here: G:\Shared drives\Socioeconomic and Land Use Analytics\Tracking Progress\Web\Data\Mortgage Lending
### Chart 2a - where "Select Purpose" = All
**Chart Type:** line
**Data File:** mortgage_lending_2a.csv
**Chart Title:** Loan Origination Rates
**Legend Items and CSV header beginnings:**
Legend Label | CSV_Header_Endings
-- | --
Female* | female
Male* | male
Latinx** | latinx
Non-Latinx** | nonlatinx
Non-White*** | minority
Asian to White*** | asian
Black to White*** | black
Other Non-White*** | other
White*** | white
**Drop-down 1 Label:** Select Geography:
**Drop-down 1 List**
Dropdown List | CSV Header Endings
-- | --
DVRPC Region | dvrpc_
NJ Counties | njcos_
PA Suburban Counties | pasubcos_
Bucks | bucks_
Burlington | burl_
Camden | camd_
Chester | ches_
Delaware | del_
Gloucester | glo_
Mercer | mer_
Montgomery | mont_
Philadelphia | phil_
**Drop-down 2 Label:** Select Purpose:
**Drop-down 2 List:** All
**Y Axis Label:** Origination Rate
**Y Axis # format:** xx.x%
**Mouse-over display:** xx.x%
**X axis label:** Year
**Legend Note:** Geography: * Sex, ** Ethnicity, *** Race
**Singular/ Plural Source:** Source:
**Source line:** Federal Financial Institutions Examination Council's (FFIEC) Home Mortgage Disclosure Act (HMDA) Data
### Chart 2b - where "Select Purpose" = Home Purchase
**Chart Type:** line
**Data File:** mortgage_lending_2b.csv
**Chart Title:** Loan Origination Rates
**Legend Items and CSV header beginnings:**
Legend Label | CSV_Header_Endings
-- | --
Female* | female
Male* | male
Latinx** | latinx
Non-Latinx** | nonlatinx
Non-White*** | minority
Asian to White*** | asian
Black to White*** | black
Other Non-White*** | other
White*** | white
**Drop-down 1 Label:** Select Geography:
**Drop-down 1 List**
Dropdown List | CSV Header Endings
-- | --
DVRPC Region | dvrpc_
NJ Counties | njcos_
PA Suburban Counties | pasubcos_
Bucks | bucks_
Burlington | burl_
Camden | camd_
Chester | ches_
Delaware | del_
Gloucester | glo_
Mercer | mer_
Montgomery | mont_
Philadelphia | phil_
**Drop-down 2 Label:** Select Purpose:
**Drop-down 2 List:** Home Purchase
**Y Axis Label:** Origination Rate
**Y Axis # format:** xx.x%
**Mouse-over display:** xx.x%
**X axis label:** Year
**Legend Note:** Geography: * Sex, ** Ethnicity, *** Race
**Singular/ Plural Source:** Source:
**Source line:** Federal Financial Institutions Examination Council's (FFIEC) Home Mortgage Disclosure Act (HMDA) Data
### Chart 2c - where "Select Purpose" = Home Improvement
**Chart Type:** line
**Data File:** mortgage_lending_2c.csv
**Chart Title:** Loan Origination Rates
**Legend Items and CSV header beginnings:**
Legend Label | CSV_Header_Endings
-- | --
Female* | female
Male* | male
Latinx** | latinx
Non-Latinx** | nonlatinx
Non-White*** | minority
Asian to White*** | asian
Black to White*** | black
Other Non-White*** | other
White*** | white
**Drop-down 1 Label:** Select Geography:
**Drop-down 1 List**
Dropdown List | CSV Header Endings
-- | --
DVRPC Region | dvrpc_
NJ Counties | njcos_
PA Suburban Counties | pasubcos_
Bucks | bucks_
Burlington | burl_
Camden | camd_
Chester | ches_
Delaware | del_
Gloucester | glo_
Mercer | mer_
Montgomery | mont_
Philadelphia | phil_
**Drop-down 2 Label:** Select Purpose:
**Drop-down 2 List:** Home Improvement
**Y Axis Label:** Origination Rate
**Y Axis # format:** xx.x%
**Mouse-over display:** xx.x%
**X axis label:** Year
**Legend Note:** Geography: * Sex, ** Ethnicity, *** Race
**Singular/ Plural Source:** Source:
**Source line:** Federal Financial Institutions Examination Council's (FFIEC) Home Mortgage Disclosure Act (HMDA) Data
### Chart 2d - where "Select Purpose" = Refinancing
**Chart Type:** line
**Data File:** mortgage_lending_2d.csv
**Chart Title:** Loan Origination Rates
**Legend Items and CSV header beginnings:**
Legend Label | CSV_Header_Endings
-- | --
Female* | female
Male* | male
Latinx** | latinx
Non-Latinx** | nonlatinx
Non-White*** | minority
Asian to White*** | asian
Black to White*** | black
Other Non-White*** | other
White*** | white
**Drop-down 1 Label:** Select Geography:
**Drop-down 1 List**
Dropdown List | CSV Header Endings
-- | --
DVRPC Region | dvrpc_
NJ Counties | njcos_
PA Suburban Counties | pasubcos_
Bucks | bucks_
Burlington | burl_
Camden | camd_
Chester | ches_
Delaware | del_
Gloucester | glo_
Mercer | mer_
Montgomery | mont_
Philadelphia | phil_
**Drop-down 2 Label:** Select Purpose:
**Drop-down 2 List:** Refinancing
**Y Axis Label:** Origination Rate
**Y Axis # format:** xx.x%
**Mouse-over display:** xx.x%
**X axis label:** Year
**Legend Note:** Geography: * Sex, ** Ethnicity, *** Race
**Singular/ Plural Source:** Source:
**Source line:** Federal Financial Institutions Examination Council's (FFIEC) Home Mortgage Disclosure Act (HMDA) Data
| priority | mortgage lending chart a b c d hachadorian this is the second of three charts for mortgage lending i m not doing the visual mockups for this hopefully you ll follow along let me know if you have question or want to meet source csvs are here g shared drives socioeconomic and land use analytics tracking progress web data mortgage lending chart where select purpose all chart type line data file mortgage lending csv chart title loan origination rates legend items and csv header beginnings legend label csv header endings female female male male latinx latinx non latinx nonlatinx non white minority asian to white asian black to white black other non white other white white drop down label select geography drop down list dropdown list csv header endings dvrpc region dvrpc nj counties njcos pa suburban counties pasubcos bucks bucks burlington burl camden camd chester ches delaware del gloucester glo mercer mer montgomery mont philadelphia phil drop down label select purpose drop down list all y axis label origination rate y axis format xx x mouse over display xx x x axis label year legend note geography sex ethnicity race singular plural source source source line federal financial institutions examination council s ffiec home mortgage disclosure act hmda data chart where select purpose home purchase chart type line data file mortgage lending csv chart title loan origination rates legend items and csv header beginnings legend label csv header endings female female male male latinx latinx non latinx nonlatinx non white minority asian to white asian black to white black other non white other white white drop down label select geography drop down list dropdown list csv header endings dvrpc region dvrpc nj counties njcos pa suburban counties pasubcos bucks bucks burlington burl camden camd chester ches delaware del gloucester glo mercer mer montgomery mont philadelphia phil drop down label select purpose drop down list home purchase y axis label origination rate y axis format xx x mouse over display xx x x axis label year legend note geography sex ethnicity race singular plural source source source line federal financial institutions examination council s ffiec home mortgage disclosure act hmda data chart where select purpose home improvement chart type line data file mortgage lending csv chart title loan origination rates legend items and csv header beginnings legend label csv header endings female female male male latinx latinx non latinx nonlatinx non white minority asian to white asian black to white black other non white other white white drop down label select geography drop down list dropdown list csv header endings dvrpc region dvrpc nj counties njcos pa suburban counties pasubcos bucks bucks burlington burl camden camd chester ches delaware del gloucester glo mercer mer montgomery mont philadelphia phil drop down label select purpose drop down list home improvement y axis label origination rate y axis format xx x mouse over display xx x x axis label year legend note geography sex ethnicity race singular plural source source source line federal financial institutions examination council s ffiec home mortgage disclosure act hmda data chart where select purpose refinancing chart type line data file mortgage lending csv chart title loan origination rates legend items and csv header beginnings legend label csv header endings female female male male latinx latinx non latinx nonlatinx non white minority asian to white asian black to white black other non white other white white drop down label select geography drop down list dropdown list csv header endings dvrpc region dvrpc nj counties njcos pa suburban counties pasubcos bucks bucks burlington burl camden camd chester ches delaware del gloucester glo mercer mer montgomery mont philadelphia phil drop down label select purpose drop down list refinancing y axis label origination rate y axis format xx x mouse over display xx x x axis label year legend note geography sex ethnicity race singular plural source source source line federal financial institutions examination council s ffiec home mortgage disclosure act hmda data | 1 |
195,304 | 6,910,373,737 | IssuesEvent | 2017-11-28 01:55:03 | jlizier/jidt | https://api.github.com/repos/jlizier/jidt | closed | Kraskov calculators to ensure they use actual k in joint space than assumed k | auto-migrated Priority-Low Type-Enhancement | ```
At the moment, our Kraskov calculators assume that they have k values within
epsilon in the full joint space. Where the distribution is composed of delta
functions (i.e. somewhat discretised) this won't be the case - there could be
many more than k. As such, it may be more correct to use the actual k for each
observation in contributing digamma(k) - 1/k, then averaging, rather than
assume the parameter k.
This may add significantly to the runtime however so we could either:
- just issue a warning were this to occur, or
- track the actual k values in an array, then compute digamma(k) - 1/k once for
each distinct value and add these in to the result.
```
Original issue reported on code.google.com by `joseph.lizier` on 7 Sep 2012 at 5:47
| 1.0 | Kraskov calculators to ensure they use actual k in joint space than assumed k - ```
At the moment, our Kraskov calculators assume that they have k values within
epsilon in the full joint space. Where the distribution is composed of delta
functions (i.e. somewhat discretised) this won't be the case - there could be
many more than k. As such, it may be more correct to use the actual k for each
observation in contributing digamma(k) - 1/k, then averaging, rather than
assume the parameter k.
This may add significantly to the runtime however so we could either:
- just issue a warning were this to occur, or
- track the actual k values in an array, then compute digamma(k) - 1/k once for
each distinct value and add these in to the result.
```
Original issue reported on code.google.com by `joseph.lizier` on 7 Sep 2012 at 5:47
| priority | kraskov calculators to ensure they use actual k in joint space than assumed k at the moment our kraskov calculators assume that they have k values within epsilon in the full joint space where the distribution is composed of delta functions i e somewhat discretised this won t be the case there could be many more than k as such it may be more correct to use the actual k for each observation in contributing digamma k k then averaging rather than assume the parameter k this may add significantly to the runtime however so we could either just issue a warning were this to occur or track the actual k values in an array then compute digamma k k once for each distinct value and add these in to the result original issue reported on code google com by joseph lizier on sep at | 1 |
132,578 | 28,236,607,622 | IssuesEvent | 2023-04-06 01:28:31 | haproxy/haproxy | https://api.github.com/repos/haproxy/haproxy | opened | src/applet.c: null pointer dereference suspected by coverity | type: code-report | ### Tool Name and Version
coverity
### Code Report
```plain
*** CID 1508680: Null pointer dereferences (FORWARD_NULL)
/src/applet.c: 139 in applet_trace()
133 appctx, appctx->t, tick_isset(appctx->t->expire) ? TICKS_TO_MS(appctx->t->expire - now_ms) : TICK_ETERNITY,
134 appctx->state, appctx->st0, appctx->st1);
135
136 if (!sc || src->verbosity == STRM_VERB_MINIMAL)
137 return;
138
>>> CID 1508680: Null pointer dereferences (FORWARD_NULL)
>>> Dereferencing null pointer "s".
139 chunk_appendf(&trace_buf, " - s=(%p,0x%08x,0x%x)", s, s->flags, s->conn_err_type);
140
141 chunk_appendf(&trace_buf, " sc=(%p,%d,0x%08x,0x%x) sco=(%p,%d,0x%08x,0x%x) sc.exp(r,w)=(%d,%d) sc.exp(r,w)=(%d,%d)",
142 sc, sc->state, sc->flags, sc->sedesc->flags,
143 sco, sco->state, sco->flags, sco->sedesc->flags,
144 tick_isset(sc_ep_rcv_ex(sc)) ? TICKS_TO_MS(sc_ep_rcv_ex(sc) - now_ms) : TICK_ETERNITY,
```
### Additional Information
_No response_
### Output of `haproxy -vv`
```plain
no
```
| 1.0 | src/applet.c: null pointer dereference suspected by coverity - ### Tool Name and Version
coverity
### Code Report
```plain
*** CID 1508680: Null pointer dereferences (FORWARD_NULL)
/src/applet.c: 139 in applet_trace()
133 appctx, appctx->t, tick_isset(appctx->t->expire) ? TICKS_TO_MS(appctx->t->expire - now_ms) : TICK_ETERNITY,
134 appctx->state, appctx->st0, appctx->st1);
135
136 if (!sc || src->verbosity == STRM_VERB_MINIMAL)
137 return;
138
>>> CID 1508680: Null pointer dereferences (FORWARD_NULL)
>>> Dereferencing null pointer "s".
139 chunk_appendf(&trace_buf, " - s=(%p,0x%08x,0x%x)", s, s->flags, s->conn_err_type);
140
141 chunk_appendf(&trace_buf, " sc=(%p,%d,0x%08x,0x%x) sco=(%p,%d,0x%08x,0x%x) sc.exp(r,w)=(%d,%d) sc.exp(r,w)=(%d,%d)",
142 sc, sc->state, sc->flags, sc->sedesc->flags,
143 sco, sco->state, sco->flags, sco->sedesc->flags,
144 tick_isset(sc_ep_rcv_ex(sc)) ? TICKS_TO_MS(sc_ep_rcv_ex(sc) - now_ms) : TICK_ETERNITY,
```
### Additional Information
_No response_
### Output of `haproxy -vv`
```plain
no
```
| non_priority | src applet c null pointer dereference suspected by coverity tool name and version coverity code report plain cid null pointer dereferences forward null src applet c in applet trace appctx appctx t tick isset appctx t expire ticks to ms appctx t expire now ms tick eternity appctx state appctx appctx if sc src verbosity strm verb minimal return cid null pointer dereferences forward null dereferencing null pointer s chunk appendf trace buf s p x s s flags s conn err type chunk appendf trace buf sc p d x sco p d x sc exp r w d d sc exp r w d d sc sc state sc flags sc sedesc flags sco sco state sco flags sco sedesc flags tick isset sc ep rcv ex sc ticks to ms sc ep rcv ex sc now ms tick eternity additional information no response output of haproxy vv plain no | 0 |
168,043 | 6,360,295,860 | IssuesEvent | 2017-07-31 09:42:53 | mozilla/addons-server | https://api.github.com/repos/mozilla/addons-server | closed | Update text for developer profile notification box "news and events" | priority: blocks release | Brian Smith just advised that we revise the opt-in language from "stay up-to-date with news and events relevant to add-on developers" to "stay up-to-date with news and events relevant to add-on developers (including the about:addons newsletter).
Any chance we could get this patched by Aug 2 (next issue send date)?
**11:11am PST edit: No need for an unscheduled push -- it's ok if this goes through with the scheduled push on Aug 3.**
| 1.0 | Update text for developer profile notification box "news and events" - Brian Smith just advised that we revise the opt-in language from "stay up-to-date with news and events relevant to add-on developers" to "stay up-to-date with news and events relevant to add-on developers (including the about:addons newsletter).
Any chance we could get this patched by Aug 2 (next issue send date)?
**11:11am PST edit: No need for an unscheduled push -- it's ok if this goes through with the scheduled push on Aug 3.**
| priority | update text for developer profile notification box news and events brian smith just advised that we revise the opt in language from stay up to date with news and events relevant to add on developers to stay up to date with news and events relevant to add on developers including the about addons newsletter any chance we could get this patched by aug next issue send date pst edit no need for an unscheduled push it s ok if this goes through with the scheduled push on aug | 1 |
110,719 | 16,987,015,824 | IssuesEvent | 2021-06-30 15:25:52 | samuelteixeiras/caite | https://api.github.com/repos/samuelteixeiras/caite | opened | WS-2014-0005 (High) detected in qs-0.6.5.tgz, qs-0.5.6.tgz | security vulnerability | ## WS-2014-0005 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>qs-0.6.5.tgz</b>, <b>qs-0.5.6.tgz</b></p></summary>
<p>
<details><summary><b>qs-0.6.5.tgz</b></p></summary>
<p>querystring parser</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.5.tgz">https://registry.npmjs.org/qs/-/qs-0.6.5.tgz</a></p>
<p>Path to dependency file: caite/package.json</p>
<p>Path to vulnerable library: caite/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- grunt-contrib-connect-0.5.0.tgz (Root Library)
- connect-2.7.11.tgz
- :x: **qs-0.6.5.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-0.5.6.tgz</b></p></summary>
<p>querystring parser</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.5.6.tgz">https://registry.npmjs.org/qs/-/qs-0.5.6.tgz</a></p>
<p>Path to dependency file: caite/package.json</p>
<p>Path to vulnerable library: caite/node_modules/tiny-lr/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- grunt-contrib-watch-0.5.3.tgz (Root Library)
- tiny-lr-0.0.4.tgz
- :x: **qs-0.5.6.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/samuelteixeiras/caite/commit/cd9951c688404f842b5b42d372e5ac4d387ff367">cd9951c688404f842b5b42d372e5ac4d387ff367</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>
Denial-of-Service Extended Event Loop Blocking.The qs module does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time
<p>Publish Date: 2014-07-31
<p>URL: <a href=https://github.com/ljharb/qs/commit/6667340dd3c7deaa0eb1c27f175faaaf71f19823>WS-2014-0005</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://nodesecurity.io/advisories/qs_dos_extended_event_loop_blocking">https://nodesecurity.io/advisories/qs_dos_extended_event_loop_blocking</a></p>
<p>Release Date: 2014-08-06</p>
<p>Fix Resolution: Update qs to version 1.0.0 or greater</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2014-0005 (High) detected in qs-0.6.5.tgz, qs-0.5.6.tgz - ## WS-2014-0005 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>qs-0.6.5.tgz</b>, <b>qs-0.5.6.tgz</b></p></summary>
<p>
<details><summary><b>qs-0.6.5.tgz</b></p></summary>
<p>querystring parser</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.6.5.tgz">https://registry.npmjs.org/qs/-/qs-0.6.5.tgz</a></p>
<p>Path to dependency file: caite/package.json</p>
<p>Path to vulnerable library: caite/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- grunt-contrib-connect-0.5.0.tgz (Root Library)
- connect-2.7.11.tgz
- :x: **qs-0.6.5.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-0.5.6.tgz</b></p></summary>
<p>querystring parser</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.5.6.tgz">https://registry.npmjs.org/qs/-/qs-0.5.6.tgz</a></p>
<p>Path to dependency file: caite/package.json</p>
<p>Path to vulnerable library: caite/node_modules/tiny-lr/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- grunt-contrib-watch-0.5.3.tgz (Root Library)
- tiny-lr-0.0.4.tgz
- :x: **qs-0.5.6.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/samuelteixeiras/caite/commit/cd9951c688404f842b5b42d372e5ac4d387ff367">cd9951c688404f842b5b42d372e5ac4d387ff367</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>
Denial-of-Service Extended Event Loop Blocking.The qs module does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of time
<p>Publish Date: 2014-07-31
<p>URL: <a href=https://github.com/ljharb/qs/commit/6667340dd3c7deaa0eb1c27f175faaaf71f19823>WS-2014-0005</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://nodesecurity.io/advisories/qs_dos_extended_event_loop_blocking">https://nodesecurity.io/advisories/qs_dos_extended_event_loop_blocking</a></p>
<p>Release Date: 2014-08-06</p>
<p>Fix Resolution: Update qs to version 1.0.0 or greater</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 | ws high detected in qs tgz qs tgz ws high severity vulnerability vulnerable libraries qs tgz qs tgz qs tgz querystring parser library home page a href path to dependency file caite package json path to vulnerable library caite node modules qs package json dependency hierarchy grunt contrib connect tgz root library connect tgz x qs tgz vulnerable library qs tgz querystring parser library home page a href path to dependency file caite package json path to vulnerable library caite node modules tiny lr node modules qs package json dependency hierarchy grunt contrib watch tgz root library tiny lr tgz x qs tgz vulnerable library found in head commit a href found in base branch master vulnerability details denial of service extended event loop blocking the qs module does not have an option or default for specifying object depth and when parsing a string representing a deeply nested object will block the event loop for long periods of 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 suggested fix type upgrade version origin a href release date fix resolution update qs to version or greater step up your open source security game with whitesource | 0 |
753,345 | 26,344,719,575 | IssuesEvent | 2023-01-10 20:53:51 | GoogleCloudPlatform/python-docs-samples | https://api.github.com/repos/GoogleCloudPlatform/python-docs-samples | closed | healthcare.api-client.v1.consent.attribute_definitions_test: test_CRUD_resource_attribute_definition failed | priority: p1 type: bug api: healthcare samples flakybot: issue | Note: #8580 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
----
commit: 66e069f916ffc0c3f19899f5083d32ebc514a8f3
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/fea8fe56-8bef-4375-a365-e791f47ba958), [Sponge](http://sponge2/fea8fe56-8bef-4375-a365-e791f47ba958)
status: failed
<details><summary>Test output</summary><br><pre>Traceback (most recent call last):
File "/workspace/healthcare/api-client/v1/consent/attribute_definitions_test.py", line 59, in test_dataset
create()
File "/workspace/healthcare/api-client/v1/consent/.nox/py-3-11/lib/python3.11/site-packages/backoff/_sync.py", line 110, in retry
ret = target(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^
File "/workspace/healthcare/api-client/v1/consent/attribute_definitions_test.py", line 49, in create
datasets.create_dataset(project_id, location, dataset_id)
File "/workspace/healthcare/api-client/v1/consent/../datasets/datasets.py", line 47, in create_dataset
response = request.execute()
^^^^^^^^^^^^^^^^^
File "/workspace/healthcare/api-client/v1/consent/.nox/py-3-11/lib/python3.11/site-packages/googleapiclient/_helpers.py", line 131, in positional_wrapper
return wrapped(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^
File "/workspace/healthcare/api-client/v1/consent/.nox/py-3-11/lib/python3.11/site-packages/googleapiclient/http.py", line 937, in execute
raise HttpError(resp, content, uri=self.uri)
googleapiclient.errors.HttpError: <HttpError 403 when requesting https://healthcare.googleapis.com/v1/projects/python-docs-samples-tests-311/locations/us-central1/datasets?datasetId=test-dataset-e0232837-ac91-42bc-bc0d-6a9fb062a651&alt=json returned "Cloud Healthcare API has not been used in project 173425378622 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/healthcare.googleapis.com/overview?project=173425378622 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.". Details: "[{'@type': 'type.googleapis.com/google.rpc.Help', 'links': [{'description': 'Google developers console API activation', 'url': 'https://console.developers.google.com/apis/api/healthcare.googleapis.com/overview?project=173425378622'}]}, {'@type': 'type.googleapis.com/google.rpc.ErrorInfo', 'reason': 'SERVICE_DISABLED', 'domain': 'googleapis.com', 'metadata': {'consumer': 'projects/173425378622', 'service': 'healthcare.googleapis.com'}}]"></pre></details> | 1.0 | healthcare.api-client.v1.consent.attribute_definitions_test: test_CRUD_resource_attribute_definition failed - Note: #8580 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
----
commit: 66e069f916ffc0c3f19899f5083d32ebc514a8f3
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/fea8fe56-8bef-4375-a365-e791f47ba958), [Sponge](http://sponge2/fea8fe56-8bef-4375-a365-e791f47ba958)
status: failed
<details><summary>Test output</summary><br><pre>Traceback (most recent call last):
File "/workspace/healthcare/api-client/v1/consent/attribute_definitions_test.py", line 59, in test_dataset
create()
File "/workspace/healthcare/api-client/v1/consent/.nox/py-3-11/lib/python3.11/site-packages/backoff/_sync.py", line 110, in retry
ret = target(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^
File "/workspace/healthcare/api-client/v1/consent/attribute_definitions_test.py", line 49, in create
datasets.create_dataset(project_id, location, dataset_id)
File "/workspace/healthcare/api-client/v1/consent/../datasets/datasets.py", line 47, in create_dataset
response = request.execute()
^^^^^^^^^^^^^^^^^
File "/workspace/healthcare/api-client/v1/consent/.nox/py-3-11/lib/python3.11/site-packages/googleapiclient/_helpers.py", line 131, in positional_wrapper
return wrapped(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^
File "/workspace/healthcare/api-client/v1/consent/.nox/py-3-11/lib/python3.11/site-packages/googleapiclient/http.py", line 937, in execute
raise HttpError(resp, content, uri=self.uri)
googleapiclient.errors.HttpError: <HttpError 403 when requesting https://healthcare.googleapis.com/v1/projects/python-docs-samples-tests-311/locations/us-central1/datasets?datasetId=test-dataset-e0232837-ac91-42bc-bc0d-6a9fb062a651&alt=json returned "Cloud Healthcare API has not been used in project 173425378622 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/healthcare.googleapis.com/overview?project=173425378622 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.". Details: "[{'@type': 'type.googleapis.com/google.rpc.Help', 'links': [{'description': 'Google developers console API activation', 'url': 'https://console.developers.google.com/apis/api/healthcare.googleapis.com/overview?project=173425378622'}]}, {'@type': 'type.googleapis.com/google.rpc.ErrorInfo', 'reason': 'SERVICE_DISABLED', 'domain': 'googleapis.com', 'metadata': {'consumer': 'projects/173425378622', 'service': 'healthcare.googleapis.com'}}]"></pre></details> | priority | healthcare api client consent attribute definitions test test crud resource attribute definition failed note was also for this test but it was closed more than days ago so i didn t mark it flaky commit buildurl status failed test output traceback most recent call last file workspace healthcare api client consent attribute definitions test py line in test dataset create file workspace healthcare api client consent nox py lib site packages backoff sync py line in retry ret target args kwargs file workspace healthcare api client consent attribute definitions test py line in create datasets create dataset project id location dataset id file workspace healthcare api client consent datasets datasets py line in create dataset response request execute file workspace healthcare api client consent nox py lib site packages googleapiclient helpers py line in positional wrapper return wrapped args kwargs file workspace healthcare api client consent nox py lib site packages googleapiclient http py line in execute raise httperror resp content uri self uri googleapiclient errors httperror | 1 |
512,523 | 14,899,298,887 | IssuesEvent | 2021-01-21 14:11:24 | weaveworks/eksctl | https://api.github.com/repos/weaveworks/eksctl | closed | block service account access to k8s APIs by exposing automountServiceAccountToken flag | kind/feature priority/backlog stale | **Why do you want this feature?**
In almost all cases, application service accounts do not need access to kubernetes APIs.
Blocking pods access to those APIs is good practice in terms of security.
**What feature/behavior/change do you want?**
Since kubernetes 1.6, there is a [`automountServiceAccountToken`](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#use-the-default-service-account-to-access-the-api-server) that controls k8s API token generation.
Actually, there is no way to change it on `eksctl` managed service accounts.
The propose is to export this flag in `eksctl` config files / CLI commands for end user.
Example:
config
```yaml
serviceAccounts:
- name: my-service-account
namespace: my-namespace
attachPolicyARNs:
- arn:...
automountServiceAccountToken: false
```
cli
```bash
eksctl create iamserviceaccount \
--cluster=<clusterName>\
--name=my-service-account\
--namespace=my-namespace
--attach-policy-arn=arn:...\
--automountServiceAccountToken=false
```
This would create a service account with corresponding flag set:
```yaml
apiVersion: v1
kind: ServiceAccount
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
...
creationTimestamp: "2020-03-20T12:51:02Z"
name: my-service-account
namespace: my-namespace
automountServiceAccountToken: false
``` | 1.0 | block service account access to k8s APIs by exposing automountServiceAccountToken flag - **Why do you want this feature?**
In almost all cases, application service accounts do not need access to kubernetes APIs.
Blocking pods access to those APIs is good practice in terms of security.
**What feature/behavior/change do you want?**
Since kubernetes 1.6, there is a [`automountServiceAccountToken`](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#use-the-default-service-account-to-access-the-api-server) that controls k8s API token generation.
Actually, there is no way to change it on `eksctl` managed service accounts.
The propose is to export this flag in `eksctl` config files / CLI commands for end user.
Example:
config
```yaml
serviceAccounts:
- name: my-service-account
namespace: my-namespace
attachPolicyARNs:
- arn:...
automountServiceAccountToken: false
```
cli
```bash
eksctl create iamserviceaccount \
--cluster=<clusterName>\
--name=my-service-account\
--namespace=my-namespace
--attach-policy-arn=arn:...\
--automountServiceAccountToken=false
```
This would create a service account with corresponding flag set:
```yaml
apiVersion: v1
kind: ServiceAccount
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
...
creationTimestamp: "2020-03-20T12:51:02Z"
name: my-service-account
namespace: my-namespace
automountServiceAccountToken: false
``` | priority | block service account access to apis by exposing automountserviceaccounttoken flag why do you want this feature in almost all cases application service accounts do not need access to kubernetes apis blocking pods access to those apis is good practice in terms of security what feature behavior change do you want since kubernetes there is a that controls api token generation actually there is no way to change it on eksctl managed service accounts the propose is to export this flag in eksctl config files cli commands for end user example config yaml serviceaccounts name my service account namespace my namespace attachpolicyarns arn automountserviceaccounttoken false cli bash eksctl create iamserviceaccount cluster name my service account namespace my namespace attach policy arn arn automountserviceaccounttoken false this would create a service account with corresponding flag set yaml apiversion kind serviceaccount metadata annotations kubectl kubernetes io last applied configuration creationtimestamp name my service account namespace my namespace automountserviceaccounttoken false | 1 |
547,937 | 16,049,755,926 | IssuesEvent | 2021-04-22 17:35:51 | OpenNebula/one | https://api.github.com/repos/OpenNebula/one | closed | Role VMs actions buttons should respect VM state | Category: Sunstone Priority: Normal Type: Feature | **Description**
If there is a running service with a role and this **role VMs** are shutdown all not possible buttons/functions should be disabled.
**Interface Changes**
<!--////////////////////////////////////////////-->
<!-- THIS SECTION IS FOR THE DEVELOPMENT TEAM -->
<!-- BOTH FOR BUGS AND ENHANCEMENT REQUESTS -->
<!-- PROGRESS WILL BE REFLECTED HERE -->
<!--////////////////////////////////////////////-->
## Progress Status
- [x] Branch created
- [x] Code committed to development branch
- [ ] Testing - QA
- [x] Documentation
- [x] Release notes - resolved issues, compatibility, known issues
- [ ] Code committed to upstream release/hotfix branches
- [ ] Documentation committed to upstream release/hotfix branches
| 1.0 | Role VMs actions buttons should respect VM state - **Description**
If there is a running service with a role and this **role VMs** are shutdown all not possible buttons/functions should be disabled.
**Interface Changes**
<!--////////////////////////////////////////////-->
<!-- THIS SECTION IS FOR THE DEVELOPMENT TEAM -->
<!-- BOTH FOR BUGS AND ENHANCEMENT REQUESTS -->
<!-- PROGRESS WILL BE REFLECTED HERE -->
<!--////////////////////////////////////////////-->
## Progress Status
- [x] Branch created
- [x] Code committed to development branch
- [ ] Testing - QA
- [x] Documentation
- [x] Release notes - resolved issues, compatibility, known issues
- [ ] Code committed to upstream release/hotfix branches
- [ ] Documentation committed to upstream release/hotfix branches
| priority | role vms actions buttons should respect vm state description if there is a running service with a role and this role vms are shutdown all not possible buttons functions should be disabled interface changes progress status branch created code committed to development branch testing qa documentation release notes resolved issues compatibility known issues code committed to upstream release hotfix branches documentation committed to upstream release hotfix branches | 1 |
305,788 | 9,377,065,184 | IssuesEvent | 2019-04-04 09:26:58 | projectacrn/acrn-hypervisor | https://api.github.com/repos/projectacrn/acrn-hypervisor | closed | Pass ACRN E820 map to OVMF | priority: P2-High status: implemented type: feature | ACRN currently uses [4GB, 5GB) as its 64-bit PCI host aperture. This is inconsistent with OVMF's assumption of its platform's memory layout, because it fetches the size of high memory from RTC CMOS.
Pass ACRN's E820 map to OVMF so it can correctly pass ACRN's memory configuration to UOS. | 1.0 | Pass ACRN E820 map to OVMF - ACRN currently uses [4GB, 5GB) as its 64-bit PCI host aperture. This is inconsistent with OVMF's assumption of its platform's memory layout, because it fetches the size of high memory from RTC CMOS.
Pass ACRN's E820 map to OVMF so it can correctly pass ACRN's memory configuration to UOS. | priority | pass acrn map to ovmf acrn currently uses as its bit pci host aperture this is inconsistent with ovmf s assumption of its platform s memory layout because it fetches the size of high memory from rtc cmos pass acrn s map to ovmf so it can correctly pass acrn s memory configuration to uos | 1 |
17,981 | 5,540,342,969 | IssuesEvent | 2017-03-22 09:52:20 | ArcticaProject/nx-libs | https://api.github.com/repos/ArcticaProject/nx-libs | opened | in libNX_X11: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] | code cleanup | ```
gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/mike/MyDocuments/4projects/arctica-upstream/nx-libs.upstream/nx-libs.36=. -fstack-protector-strong -Wformat -Werror=format-security -g -std=c99 -Wall -Wpedantic -Wpointer-arith -Wundef -I../.. -I../../exports/include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_DEFAULT_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DHAVE_SETITIMER=1 -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -DMALLOC_0_RETURNS_NULL -DHAS_SNPRINTF -DLIBX11 -DPOSTLOCALELIBDIR=\"lib\" -I../../../nxcomp -DNX_TRANS_SOCKET -DNX_TRANS_EXIT -DXCMS -DUSE_XCB=0 -DHAS_SHM -DXF86BIGFONT -fPIC Font.c
Font.c: In function '_XQueryFont':
Font.c:235:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
fs->min_bounds = * (XCharStruct *) &reply.minBounds;
^~
Font.c:236:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
fs->max_bounds = * (XCharStruct *) &reply.maxBounds;
^~
Font.c: In function '_XF86BigfontQueryFont':
Font.c:479:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
fs->min_bounds = * (XCharStruct *) &reply.minBounds;
^~
Font.c:480:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
fs->max_bounds = * (XCharStruct *) &reply.maxBounds;
^~
[...]
gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/mike/MyDocuments/4projects/arctica-upstream/nx-libs.upstream/nx-libs.36=. -fstack-protector-strong -Wformat -Werror=format-security -g -std=c99 -Wall -Wpedantic -Wpointer-arith -Wundef -I../.. -I../../exports/include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_DEFAULT_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DHAVE_SETITIMER=1 -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -DMALLOC_0_RETURNS_NULL -DHAS_SNPRINTF -DLIBX11 -DPOSTLOCALELIBDIR=\"lib\" -I../../../nxcomp -DNX_TRANS_SOCKET -DNX_TRANS_EXIT -DXCMS -DUSE_XCB=0 -DHAS_SHM -DXF86BIGFONT -fPIC FontInfo.c
FontInfo.c: In function 'XListFontsWithInfo':
FontInfo.c:131:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
fs->min_bounds = * (XCharStruct *) &reply.minBounds;
^~
FontInfo.c:132:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
fs->max_bounds = * (XCharStruct *) &reply.maxBounds;
^~
[...]
gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/mike/MyDocuments/4projects/arctica-upstream/nx-libs.upstream/nx-libs.36=. -fstack-protector-strong -Wformat -Werror=format-security -g -std=c99 -Wall -Wpedantic -Wpointer-arith -Wundef -I../.. -I../../exports/include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_DEFAULT_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DHAVE_SETITIMER=1 -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -DMALLOC_0_RETURNS_NULL -DHAS_SNPRINTF -DLIBX11 -DPOSTLOCALELIBDIR=\"lib\" -I../../../nxcomp -DNX_TRANS_SOCKET -DNX_TRANS_EXIT -DXCMS -DUSE_XCB=0 -fPIC InitExt.c
InitExt.c: In function 'XEHeadOfExtensionList':
InitExt.c:100:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
return *(XExtData ***)&object;
^~~~~~
[...]
gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/mike/MyDocuments/4projects/arctica-upstream/nx-libs.upstream/nx-libs.36=. -fstack-protector-strong -Wformat -Werror=format-security -g -std=c99 -Wall -Wpedantic -Wpointer-arith -Wundef -I../.. -I../../exports/include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_DEFAULT_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DHAVE_SETITIMER=1 -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -DMALLOC_0_RETURNS_NULL -DHAS_SNPRINTF -DLIBX11 -DPOSTLOCALELIBDIR=\"lib\" -I../../../nxcomp -DNX_TRANS_SOCKET -DNX_TRANS_EXIT -DXCMS -DUSE_XCB=0 -fPIC QuKeybd.c
QuKeybd.c: In function 'XQueryKeymap':
QuKeybd.c:48:38: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
*(struct kmap *) keys = *(struct kmap *)rep.map; /* faster than memcpy */
^~~~
[...]
gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/mike/MyDocuments/4projects/arctica-upstream/nx-libs.upstream/nx-libs.36=. -fstack-protector-strong -Wformat -Werror=format-security -g -std=c99 -Wall -Wpedantic -Wpointer-arith -Wundef -I../.. -I../../exports/include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_DEFAULT_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DHAVE_SETITIMER=1 -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -DMALLOC_0_RETURNS_NULL -DHAS_SNPRINTF -DLIBX11 -DPOSTLOCALELIBDIR=\"lib\" -I../../../nxcomp -DNX_TRANS_SOCKET -DNX_TRANS_EXIT -DXCMS -DUSE_XCB=0 -DXKB -fPIC imConv.c
imConv.c: In function '_XimGetCharCode':
imConv.c:116:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
*(ucstocsConvProc**) (&cvt) = (void *)ucs_conv;
^
[...]
gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/mike/MyDocuments/4projects/arctica-upstream/nx-libs.upstream/nx-libs.36=. -fstack-protector-strong -Wformat -Werror=format-security -g -std=c99 -Wall -Wpedantic -Wpointer-arith -Wundef -I../.. -I../../exports/include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_DEFAULT_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DHAVE_SETITIMER=1 -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -DMALLOC_0_RETURNS_NULL -DHAS_SNPRINTF -DLIBX11 -DPOSTLOCALELIBDIR=\"lib\" -I../../../nxcomp -DNX_TRANS_SOCKET -DNX_TRANS_EXIT -DXCMS -DUSE_XCB=0 -fPIC imCallbk.c
imCallbk.c: In function '_XimPreeditCaretCallback':
imCallbk.c:632:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
*(CARD16*)&buf[p] = (CARD16)im->private.proto.imid; p += sz_CARD16;
^
imCallbk.c:633:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
*(CARD16*)&buf[p] = (CARD16)ic->private.proto.icid; p += sz_CARD16;
^
imCallbk.c:634:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
*(CARD32*)&buf[p] = (CARD32)cbs.position;
^
``` | 1.0 | in libNX_X11: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] - ```
gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/mike/MyDocuments/4projects/arctica-upstream/nx-libs.upstream/nx-libs.36=. -fstack-protector-strong -Wformat -Werror=format-security -g -std=c99 -Wall -Wpedantic -Wpointer-arith -Wundef -I../.. -I../../exports/include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_DEFAULT_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DHAVE_SETITIMER=1 -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -DMALLOC_0_RETURNS_NULL -DHAS_SNPRINTF -DLIBX11 -DPOSTLOCALELIBDIR=\"lib\" -I../../../nxcomp -DNX_TRANS_SOCKET -DNX_TRANS_EXIT -DXCMS -DUSE_XCB=0 -DHAS_SHM -DXF86BIGFONT -fPIC Font.c
Font.c: In function '_XQueryFont':
Font.c:235:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
fs->min_bounds = * (XCharStruct *) &reply.minBounds;
^~
Font.c:236:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
fs->max_bounds = * (XCharStruct *) &reply.maxBounds;
^~
Font.c: In function '_XF86BigfontQueryFont':
Font.c:479:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
fs->min_bounds = * (XCharStruct *) &reply.minBounds;
^~
Font.c:480:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
fs->max_bounds = * (XCharStruct *) &reply.maxBounds;
^~
[...]
gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/mike/MyDocuments/4projects/arctica-upstream/nx-libs.upstream/nx-libs.36=. -fstack-protector-strong -Wformat -Werror=format-security -g -std=c99 -Wall -Wpedantic -Wpointer-arith -Wundef -I../.. -I../../exports/include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_DEFAULT_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DHAVE_SETITIMER=1 -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -DMALLOC_0_RETURNS_NULL -DHAS_SNPRINTF -DLIBX11 -DPOSTLOCALELIBDIR=\"lib\" -I../../../nxcomp -DNX_TRANS_SOCKET -DNX_TRANS_EXIT -DXCMS -DUSE_XCB=0 -DHAS_SHM -DXF86BIGFONT -fPIC FontInfo.c
FontInfo.c: In function 'XListFontsWithInfo':
FontInfo.c:131:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
fs->min_bounds = * (XCharStruct *) &reply.minBounds;
^~
FontInfo.c:132:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
fs->max_bounds = * (XCharStruct *) &reply.maxBounds;
^~
[...]
gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/mike/MyDocuments/4projects/arctica-upstream/nx-libs.upstream/nx-libs.36=. -fstack-protector-strong -Wformat -Werror=format-security -g -std=c99 -Wall -Wpedantic -Wpointer-arith -Wundef -I../.. -I../../exports/include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_DEFAULT_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DHAVE_SETITIMER=1 -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -DMALLOC_0_RETURNS_NULL -DHAS_SNPRINTF -DLIBX11 -DPOSTLOCALELIBDIR=\"lib\" -I../../../nxcomp -DNX_TRANS_SOCKET -DNX_TRANS_EXIT -DXCMS -DUSE_XCB=0 -fPIC InitExt.c
InitExt.c: In function 'XEHeadOfExtensionList':
InitExt.c:100:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
return *(XExtData ***)&object;
^~~~~~
[...]
gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/mike/MyDocuments/4projects/arctica-upstream/nx-libs.upstream/nx-libs.36=. -fstack-protector-strong -Wformat -Werror=format-security -g -std=c99 -Wall -Wpedantic -Wpointer-arith -Wundef -I../.. -I../../exports/include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_DEFAULT_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DHAVE_SETITIMER=1 -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -DMALLOC_0_RETURNS_NULL -DHAS_SNPRINTF -DLIBX11 -DPOSTLOCALELIBDIR=\"lib\" -I../../../nxcomp -DNX_TRANS_SOCKET -DNX_TRANS_EXIT -DXCMS -DUSE_XCB=0 -fPIC QuKeybd.c
QuKeybd.c: In function 'XQueryKeymap':
QuKeybd.c:48:38: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
*(struct kmap *) keys = *(struct kmap *)rep.map; /* faster than memcpy */
^~~~
[...]
gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/mike/MyDocuments/4projects/arctica-upstream/nx-libs.upstream/nx-libs.36=. -fstack-protector-strong -Wformat -Werror=format-security -g -std=c99 -Wall -Wpedantic -Wpointer-arith -Wundef -I../.. -I../../exports/include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_DEFAULT_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DHAVE_SETITIMER=1 -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -DMALLOC_0_RETURNS_NULL -DHAS_SNPRINTF -DLIBX11 -DPOSTLOCALELIBDIR=\"lib\" -I../../../nxcomp -DNX_TRANS_SOCKET -DNX_TRANS_EXIT -DXCMS -DUSE_XCB=0 -DXKB -fPIC imConv.c
imConv.c: In function '_XimGetCharCode':
imConv.c:116:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
*(ucstocsConvProc**) (&cvt) = (void *)ucs_conv;
^
[...]
gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/home/mike/MyDocuments/4projects/arctica-upstream/nx-libs.upstream/nx-libs.36=. -fstack-protector-strong -Wformat -Werror=format-security -g -std=c99 -Wall -Wpedantic -Wpointer-arith -Wundef -I../.. -I../../exports/include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_DEFAULT_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DHAVE_SETITIMER=1 -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -DMALLOC_0_RETURNS_NULL -DHAS_SNPRINTF -DLIBX11 -DPOSTLOCALELIBDIR=\"lib\" -I../../../nxcomp -DNX_TRANS_SOCKET -DNX_TRANS_EXIT -DXCMS -DUSE_XCB=0 -fPIC imCallbk.c
imCallbk.c: In function '_XimPreeditCaretCallback':
imCallbk.c:632:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
*(CARD16*)&buf[p] = (CARD16)im->private.proto.imid; p += sz_CARD16;
^
imCallbk.c:633:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
*(CARD16*)&buf[p] = (CARD16)ic->private.proto.icid; p += sz_CARD16;
^
imCallbk.c:634:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
*(CARD32*)&buf[p] = (CARD32)cbs.position;
^
``` | non_priority | in libnx warning dereferencing type punned pointer will break strict aliasing rules gcc c wdate time d fortify source g fdebug prefix map home mike mydocuments arctica upstream nx libs upstream nx libs fstack protector strong wformat werror format security g std wall wpedantic wpointer arith wundef i i exports include dlinux d d posix c source d posix source d xopen source d default source d largefile source d file offset bits d gnu source dhave setitimer dfuncproto dnarrowproto dxthreads d reentrant dxuse mtsafe api dmalloc returns null dhas snprintf dpostlocalelibdir lib i nxcomp dnx trans socket dnx trans exit dxcms duse xcb dhas shm fpic font c font c in function xqueryfont font c warning dereferencing type punned pointer will break strict aliasing rules fs min bounds xcharstruct reply minbounds font c warning dereferencing type punned pointer will break strict aliasing rules fs max bounds xcharstruct reply maxbounds font c in function font c warning dereferencing type punned pointer will break strict aliasing rules fs min bounds xcharstruct reply minbounds font c warning dereferencing type punned pointer will break strict aliasing rules fs max bounds xcharstruct reply maxbounds gcc c wdate time d fortify source g fdebug prefix map home mike mydocuments arctica upstream nx libs upstream nx libs fstack protector strong wformat werror format security g std wall wpedantic wpointer arith wundef i i exports include dlinux d d posix c source d posix source d xopen source d default source d largefile source d file offset bits d gnu source dhave setitimer dfuncproto dnarrowproto dxthreads d reentrant dxuse mtsafe api dmalloc returns null dhas snprintf dpostlocalelibdir lib i nxcomp dnx trans socket dnx trans exit dxcms duse xcb dhas shm fpic fontinfo c fontinfo c in function xlistfontswithinfo fontinfo c warning dereferencing type punned pointer will break strict aliasing rules fs min bounds xcharstruct reply minbounds fontinfo c warning dereferencing type punned pointer will break strict aliasing rules fs max bounds xcharstruct reply maxbounds gcc c wdate time d fortify source g fdebug prefix map home mike mydocuments arctica upstream nx libs upstream nx libs fstack protector strong wformat werror format security g std wall wpedantic wpointer arith wundef i i exports include dlinux d d posix c source d posix source d xopen source d default source d largefile source d file offset bits d gnu source dhave setitimer dfuncproto dnarrowproto dxthreads d reentrant dxuse mtsafe api dmalloc returns null dhas snprintf dpostlocalelibdir lib i nxcomp dnx trans socket dnx trans exit dxcms duse xcb fpic initext c initext c in function xeheadofextensionlist initext c warning dereferencing type punned pointer will break strict aliasing rules return xextdata object gcc c wdate time d fortify source g fdebug prefix map home mike mydocuments arctica upstream nx libs upstream nx libs fstack protector strong wformat werror format security g std wall wpedantic wpointer arith wundef i i exports include dlinux d d posix c source d posix source d xopen source d default source d largefile source d file offset bits d gnu source dhave setitimer dfuncproto dnarrowproto dxthreads d reentrant dxuse mtsafe api dmalloc returns null dhas snprintf dpostlocalelibdir lib i nxcomp dnx trans socket dnx trans exit dxcms duse xcb fpic qukeybd c qukeybd c in function xquerykeymap qukeybd c warning dereferencing type punned pointer will break strict aliasing rules struct kmap keys struct kmap rep map faster than memcpy gcc c wdate time d fortify source g fdebug prefix map home mike mydocuments arctica upstream nx libs upstream nx libs fstack protector strong wformat werror format security g std wall wpedantic wpointer arith wundef i i exports include dlinux d d posix c source d posix source d xopen source d default source d largefile source d file offset bits d gnu source dhave setitimer dfuncproto dnarrowproto dxthreads d reentrant dxuse mtsafe api dmalloc returns null dhas snprintf dpostlocalelibdir lib i nxcomp dnx trans socket dnx trans exit dxcms duse xcb dxkb fpic imconv c imconv c in function ximgetcharcode imconv c warning dereferencing type punned pointer will break strict aliasing rules ucstocsconvproc cvt void ucs conv gcc c wdate time d fortify source g fdebug prefix map home mike mydocuments arctica upstream nx libs upstream nx libs fstack protector strong wformat werror format security g std wall wpedantic wpointer arith wundef i i exports include dlinux d d posix c source d posix source d xopen source d default source d largefile source d file offset bits d gnu source dhave setitimer dfuncproto dnarrowproto dxthreads d reentrant dxuse mtsafe api dmalloc returns null dhas snprintf dpostlocalelibdir lib i nxcomp dnx trans socket dnx trans exit dxcms duse xcb fpic imcallbk c imcallbk c in function ximpreeditcaretcallback imcallbk c warning dereferencing type punned pointer will break strict aliasing rules buf im private proto imid p sz imcallbk c warning dereferencing type punned pointer will break strict aliasing rules buf ic private proto icid p sz imcallbk c warning dereferencing type punned pointer will break strict aliasing rules buf cbs position | 0 |
350,588 | 10,492,576,869 | IssuesEvent | 2019-09-25 13:32:40 | geosolutions-it/MapStore2 | https://api.github.com/repos/geosolutions-it/MapStore2 | opened | [Proposal] TOC Plugin Container | Priority: High enhancement | ### Description
Currently the TOC interacts with different plugins and sometimes they are directly [hardcoded](https://github.com/geosolutions-it/MapStore2/blob/master/web/client/components/TOC/Toolbar.jsx#L190-L314) in the component.
This could cause some configuration issues:
eg: https://github.com/geosolutions-it/MapStore2/issues/2759
The aim of this proposal is to improve the TOC by adding a way to add buttons and panels from other plugin.
here a first implementation:
https://github.com/geosolutions-it/MapStore2/commit/4c6aa2982396fafc49e5c8ec2643feaf8fbe8611
use case:
Style Editor Plugin
```js
function TOCButtonComponent({ status, enabled, onToggle, ...props }) {
return !enabled && status === 'LAYER'
? <Button {...props} onClick={() => onToggle()}>
<Glyphicon glyph="dropper" />
</Button>
: null;
}
const TOCButton = connect(
createSelector([ enabledSelector ], (enabled) => ({ enabled })),
{ onToggle: enablePluginAction }
)(TOCButtonComponent);
export default createPlugin('StyleEditor', {
component: StyleEditorPlugin,
containers: {
TOC: {
priority: 1,
tool: TOCButton, // component connected to the state
panel: true // shows the plugin near the TOC if true, false shows only the button
}
}
});
```
### Other useful information (optional):
| 1.0 | [Proposal] TOC Plugin Container - ### Description
Currently the TOC interacts with different plugins and sometimes they are directly [hardcoded](https://github.com/geosolutions-it/MapStore2/blob/master/web/client/components/TOC/Toolbar.jsx#L190-L314) in the component.
This could cause some configuration issues:
eg: https://github.com/geosolutions-it/MapStore2/issues/2759
The aim of this proposal is to improve the TOC by adding a way to add buttons and panels from other plugin.
here a first implementation:
https://github.com/geosolutions-it/MapStore2/commit/4c6aa2982396fafc49e5c8ec2643feaf8fbe8611
use case:
Style Editor Plugin
```js
function TOCButtonComponent({ status, enabled, onToggle, ...props }) {
return !enabled && status === 'LAYER'
? <Button {...props} onClick={() => onToggle()}>
<Glyphicon glyph="dropper" />
</Button>
: null;
}
const TOCButton = connect(
createSelector([ enabledSelector ], (enabled) => ({ enabled })),
{ onToggle: enablePluginAction }
)(TOCButtonComponent);
export default createPlugin('StyleEditor', {
component: StyleEditorPlugin,
containers: {
TOC: {
priority: 1,
tool: TOCButton, // component connected to the state
panel: true // shows the plugin near the TOC if true, false shows only the button
}
}
});
```
### Other useful information (optional):
| priority | toc plugin container description currently the toc interacts with different plugins and sometimes they are directly in the component this could cause some configuration issues eg the aim of this proposal is to improve the toc by adding a way to add buttons and panels from other plugin here a first implementation use case style editor plugin js function tocbuttoncomponent status enabled ontoggle props return enabled status layer ontoggle null const tocbutton connect createselector enabled enabled ontoggle enablepluginaction tocbuttoncomponent export default createplugin styleeditor component styleeditorplugin containers toc priority tool tocbutton component connected to the state panel true shows the plugin near the toc if true false shows only the button other useful information optional | 1 |
172,882 | 27,347,694,016 | IssuesEvent | 2023-02-27 06:59:08 | starplanter93/The_Garden_of_Musicsheet | https://api.github.com/repos/starplanter93/The_Garden_of_Musicsheet | opened | Design: 모바일 반응형 작업 | Design | ## Description
뷰포트 390px~767px의 모바일 반응형 작업
## Todo
- [ ] 악기 페이지
- [ ] 악기 상세페이지
- [ ] 곡 상세페이지 | 1.0 | Design: 모바일 반응형 작업 - ## Description
뷰포트 390px~767px의 모바일 반응형 작업
## Todo
- [ ] 악기 페이지
- [ ] 악기 상세페이지
- [ ] 곡 상세페이지 | non_priority | design 모바일 반응형 작업 description 뷰포트 모바일 반응형 작업 todo 악기 페이지 악기 상세페이지 곡 상세페이지 | 0 |
405,058 | 11,866,754,104 | IssuesEvent | 2020-03-26 04:50:06 | cuberite/cuberite | https://api.github.com/repos/cuberite/cuberite | closed | Segmentation Fault on RPi4 AlpineLinux | crash priority/important | Client version: 1.12.2
Server OS: Alpine Linux v3.11 armv7l
Cuberite Commit id: [09:13:20] from commit id: approx: 8154bde116df2b0ff2fe535ed1bb87d00a009b52 built at: approx: 2020-03-24 21:16:54 +0000
Sorry for my bad english.
### Expected behavior
Server should start succesfully.
### Actual behavior
Server got segmentation fault.
### Steps to reproduce the behavior
- Build cuberite on RPi 4 "Alpine Linux v3.11 armv7l" with CXXFLAGS="-march=native -O3 -pipe"
- Profit!!
### Server log
```
Starting program: /root/cuberite/Release/Server/Cuberite
[New LWP 8344]
[New LWP 8345]
[09:19:28] --- Started Log ---
[09:19:28] Cuberite local build build id: Unknown
[09:19:28] from commit id: approx: 8154bde116df2b0ff2fe535ed1bb87d00a009b52 built at: approx: 2020-03-24 21:16:54 +0000
[09:19:28] Creating new server instance...
[09:19:28] Reading server config...
[09:19:28] Regenerating settings.ini, all settings will be reset
[09:19:28] Starting server...
[09:19:28] Loading UpgradeBlockTypePalette...
[09:19:28] Loading per-protocol palettes...
[09:19:29] Loaded palettes for protocol versions: 1.13, 1.14.4
[New LWP 8346]
[09:19:29] Compatible clients: 1.8.x, 1.9.x, 1.10.x, 1.11.x, 1.12.x
[09:19:29] Compatible protocol versions 47, 107, 108, 109, 110, 210, 315, 316, 335, 338, 340
[09:19:29] WebServer: The server will run in unsecured HTTP mode.
[09:19:29] Put a valid HTTPS certificate in file 'webadmin/httpscert.crt' and its corresponding private key to 'webadmin/httpskey.pem' (without any password) to enable HTTPS support
[09:19:29] Loaded 755 crafting recipes
[09:19:29] Loaded 67 furnace recipes and 66 fuels
[09:19:29] Loaded 88 brewing recipes
[09:19:29] -- Loading Plugins --
[09:19:29] Initialised Core v.16
[09:19:29] Initialized ChatLog v.3
[09:19:29] -- Loaded 2 Plugins --
[New LWP 8347]
[New LWP 8348]
[New LWP 8349]
[New LWP 8350]
[New LWP 8351]
[New LWP 8352]
Thread 8 "Cuberite" received signal SIGSEGV, Segmentation fault.
[Switching to LWP 8350]
0xb6ee7c22 in operator new(unsigned int) () from /usr/lib/libstdc++.so.6
```
| 1.0 | Segmentation Fault on RPi4 AlpineLinux - Client version: 1.12.2
Server OS: Alpine Linux v3.11 armv7l
Cuberite Commit id: [09:13:20] from commit id: approx: 8154bde116df2b0ff2fe535ed1bb87d00a009b52 built at: approx: 2020-03-24 21:16:54 +0000
Sorry for my bad english.
### Expected behavior
Server should start succesfully.
### Actual behavior
Server got segmentation fault.
### Steps to reproduce the behavior
- Build cuberite on RPi 4 "Alpine Linux v3.11 armv7l" with CXXFLAGS="-march=native -O3 -pipe"
- Profit!!
### Server log
```
Starting program: /root/cuberite/Release/Server/Cuberite
[New LWP 8344]
[New LWP 8345]
[09:19:28] --- Started Log ---
[09:19:28] Cuberite local build build id: Unknown
[09:19:28] from commit id: approx: 8154bde116df2b0ff2fe535ed1bb87d00a009b52 built at: approx: 2020-03-24 21:16:54 +0000
[09:19:28] Creating new server instance...
[09:19:28] Reading server config...
[09:19:28] Regenerating settings.ini, all settings will be reset
[09:19:28] Starting server...
[09:19:28] Loading UpgradeBlockTypePalette...
[09:19:28] Loading per-protocol palettes...
[09:19:29] Loaded palettes for protocol versions: 1.13, 1.14.4
[New LWP 8346]
[09:19:29] Compatible clients: 1.8.x, 1.9.x, 1.10.x, 1.11.x, 1.12.x
[09:19:29] Compatible protocol versions 47, 107, 108, 109, 110, 210, 315, 316, 335, 338, 340
[09:19:29] WebServer: The server will run in unsecured HTTP mode.
[09:19:29] Put a valid HTTPS certificate in file 'webadmin/httpscert.crt' and its corresponding private key to 'webadmin/httpskey.pem' (without any password) to enable HTTPS support
[09:19:29] Loaded 755 crafting recipes
[09:19:29] Loaded 67 furnace recipes and 66 fuels
[09:19:29] Loaded 88 brewing recipes
[09:19:29] -- Loading Plugins --
[09:19:29] Initialised Core v.16
[09:19:29] Initialized ChatLog v.3
[09:19:29] -- Loaded 2 Plugins --
[New LWP 8347]
[New LWP 8348]
[New LWP 8349]
[New LWP 8350]
[New LWP 8351]
[New LWP 8352]
Thread 8 "Cuberite" received signal SIGSEGV, Segmentation fault.
[Switching to LWP 8350]
0xb6ee7c22 in operator new(unsigned int) () from /usr/lib/libstdc++.so.6
```
| priority | segmentation fault on alpinelinux client version server os alpine linux cuberite commit id from commit id approx built at approx sorry for my bad english expected behavior server should start succesfully actual behavior server got segmentation fault steps to reproduce the behavior build cuberite on rpi alpine linux with cxxflags march native pipe profit server log starting program root cuberite release server cuberite started log cuberite local build build id unknown from commit id approx built at approx creating new server instance reading server config regenerating settings ini all settings will be reset starting server loading upgradeblocktypepalette loading per protocol palettes loaded palettes for protocol versions compatible clients x x x x x compatible protocol versions webserver the server will run in unsecured http mode put a valid https certificate in file webadmin httpscert crt and its corresponding private key to webadmin httpskey pem without any password to enable https support loaded crafting recipes loaded furnace recipes and fuels loaded brewing recipes loading plugins initialised core v initialized chatlog v loaded plugins thread cuberite received signal sigsegv segmentation fault in operator new unsigned int from usr lib libstdc so | 1 |
74,322 | 20,117,257,929 | IssuesEvent | 2022-02-07 20:57:26 | JVoiceXML/JVoiceXML | https://api.github.com/repos/JVoiceXML/JVoiceXML | closed | Upgrade junit to 4.13.2 | build-system | In preparation to cleaning up junit tests, junit should be upgraded to the latest version 4.13.2. upgrading to junit 5 should be done afterwards. | 1.0 | Upgrade junit to 4.13.2 - In preparation to cleaning up junit tests, junit should be upgraded to the latest version 4.13.2. upgrading to junit 5 should be done afterwards. | non_priority | upgrade junit to in preparation to cleaning up junit tests junit should be upgraded to the latest version upgrading to junit should be done afterwards | 0 |
98,969 | 30,241,012,676 | IssuesEvent | 2023-07-06 13:31:39 | vitessio/vitess | https://api.github.com/repos/vitessio/vitess | closed | Flaky Test: vipersync.TestPersistConfig | Type: Bug Component: Build/CI Type: Testing | ### Overview of the Issue
The `vipersync.TestPersistConfig` tests are _extremely_ flaky in CI, and slightly less so on a local machine.
We've skipped them for now, but we need to rewrite these tests to re-enable them, as that code is currently untested.
### Reproduction Steps
go test -race run "TestPersistConfig" ./go/viperutil/internal/vipersync
### Binary Version
```sh
main
```
### Operating System and Environment details
```sh
N/A
```
### Log Fragments
_No response_ | 1.0 | Flaky Test: vipersync.TestPersistConfig - ### Overview of the Issue
The `vipersync.TestPersistConfig` tests are _extremely_ flaky in CI, and slightly less so on a local machine.
We've skipped them for now, but we need to rewrite these tests to re-enable them, as that code is currently untested.
### Reproduction Steps
go test -race run "TestPersistConfig" ./go/viperutil/internal/vipersync
### Binary Version
```sh
main
```
### Operating System and Environment details
```sh
N/A
```
### Log Fragments
_No response_ | non_priority | flaky test vipersync testpersistconfig overview of the issue the vipersync testpersistconfig tests are extremely flaky in ci and slightly less so on a local machine we ve skipped them for now but we need to rewrite these tests to re enable them as that code is currently untested reproduction steps go test race run testpersistconfig go viperutil internal vipersync binary version sh main operating system and environment details sh n a log fragments no response | 0 |
207,698 | 7,132,652,186 | IssuesEvent | 2018-01-22 15:14:38 | metasfresh/metasfresh-webui-api | https://api.github.com/repos/metasfresh/metasfresh-webui-api | opened | Allow Filtering for Table References and show table identifier | priority:high | ### Is this a bug or feature request?
Feature Request
### What is the current behavior?
Currently, it's not possible to add a Label Field as Filter Element which does not point to a reference list, but to a Table ID.
#### Which are the steps to reproduce?
Check Testcase for Location in Business partner window. Open the Filter and Try last Filter entry.
### What is the expected or desired behavior?
Shall work. | 1.0 | Allow Filtering for Table References and show table identifier - ### Is this a bug or feature request?
Feature Request
### What is the current behavior?
Currently, it's not possible to add a Label Field as Filter Element which does not point to a reference list, but to a Table ID.
#### Which are the steps to reproduce?
Check Testcase for Location in Business partner window. Open the Filter and Try last Filter entry.
### What is the expected or desired behavior?
Shall work. | priority | allow filtering for table references and show table identifier is this a bug or feature request feature request what is the current behavior currently it s not possible to add a label field as filter element which does not point to a reference list but to a table id which are the steps to reproduce check testcase for location in business partner window open the filter and try last filter entry what is the expected or desired behavior shall work | 1 |
401,251 | 11,787,912,645 | IssuesEvent | 2020-03-17 14:46:21 | OregonDigital/OD2 | https://api.github.com/repos/OregonDigital/OD2 | closed | Source Updates for Help Text and Form Label | Features Priority - High | ### Descriptive summary
- [x] Shelf Location Help Text missing
| 1.0 | Source Updates for Help Text and Form Label - ### Descriptive summary
- [x] Shelf Location Help Text missing
| priority | source updates for help text and form label descriptive summary shelf location help text missing | 1 |
418,776 | 12,203,185,987 | IssuesEvent | 2020-04-30 10:10:11 | MHRA/products | https://api.github.com/repos/MHRA/products | closed | Delete can remove document from search index but not storage, making it impossible for Sentinel to delete it | BUG :bug: HIGH PRIORITY :arrow_double_up: | From @TimboTambo:
> There were around 30 errors from the batch run test last week that occurred with deleting files. Seems like in all cases the doc to delete was found in the search index, removed from the search index, failed when removing from the storage container, was retried and then the doc could no longer be found in the search index so was set to Error(: Cannot find document with ID …)
The following Azure log query brings up an example of this happening:
```
let correlationId = "bd582bbf-6a76-4708-9440-10aefc726d89";
let timeframeFrom = totimespan(6d);
let timeframeTo = totimespan(4d);
let clusterId = '/subscriptions/bec11470-1346-4cdd-af2e-ce1f360671a1/resourceGroups/adazr-rg-1001/providers/Microsoft.ContainerService/managedClusters/non-prod';
let ContainerIdList = KubePodInventory
| where TimeGenerated > now() - timeframeFrom and TimeGenerated < now() - timeframeTo
| where ContainerName contains 'doc-index-updater'
| where ClusterId =~ clusterId
| distinct ContainerID;
ContainerLog
| where TimeGenerated > now() - timeframeFrom and TimeGenerated < now() - timeframeTo
| where ContainerID in (ContainerIdList)
| project LogEntrySource, LogEntry, TimeGenerated, Computer, Image, Name, ContainerID
| order by TimeGenerated desc
| render table
| extend message_ = tostring(parse_json(tostring(parse_json(LogEntry).fields)).message)
| where parse_json(tostring(parse_json(LogEntry).span)).correlation_id == correlationId
```
| 1.0 | Delete can remove document from search index but not storage, making it impossible for Sentinel to delete it - From @TimboTambo:
> There were around 30 errors from the batch run test last week that occurred with deleting files. Seems like in all cases the doc to delete was found in the search index, removed from the search index, failed when removing from the storage container, was retried and then the doc could no longer be found in the search index so was set to Error(: Cannot find document with ID …)
The following Azure log query brings up an example of this happening:
```
let correlationId = "bd582bbf-6a76-4708-9440-10aefc726d89";
let timeframeFrom = totimespan(6d);
let timeframeTo = totimespan(4d);
let clusterId = '/subscriptions/bec11470-1346-4cdd-af2e-ce1f360671a1/resourceGroups/adazr-rg-1001/providers/Microsoft.ContainerService/managedClusters/non-prod';
let ContainerIdList = KubePodInventory
| where TimeGenerated > now() - timeframeFrom and TimeGenerated < now() - timeframeTo
| where ContainerName contains 'doc-index-updater'
| where ClusterId =~ clusterId
| distinct ContainerID;
ContainerLog
| where TimeGenerated > now() - timeframeFrom and TimeGenerated < now() - timeframeTo
| where ContainerID in (ContainerIdList)
| project LogEntrySource, LogEntry, TimeGenerated, Computer, Image, Name, ContainerID
| order by TimeGenerated desc
| render table
| extend message_ = tostring(parse_json(tostring(parse_json(LogEntry).fields)).message)
| where parse_json(tostring(parse_json(LogEntry).span)).correlation_id == correlationId
```
| priority | delete can remove document from search index but not storage making it impossible for sentinel to delete it from timbotambo there were around errors from the batch run test last week that occurred with deleting files seems like in all cases the doc to delete was found in the search index removed from the search index failed when removing from the storage container was retried and then the doc could no longer be found in the search index so was set to error cannot find document with id … the following azure log query brings up an example of this happening let correlationid let timeframefrom totimespan let timeframeto totimespan let clusterid subscriptions resourcegroups adazr rg providers microsoft containerservice managedclusters non prod let containeridlist kubepodinventory where timegenerated now timeframefrom and timegenerated now timeframeto where containername contains doc index updater where clusterid clusterid distinct containerid containerlog where timegenerated now timeframefrom and timegenerated now timeframeto where containerid in containeridlist project logentrysource logentry timegenerated computer image name containerid order by timegenerated desc render table extend message tostring parse json tostring parse json logentry fields message where parse json tostring parse json logentry span correlation id correlationid | 1 |
241,676 | 7,822,049,524 | IssuesEvent | 2018-06-14 00:00:21 | tidepool-org/chrome-uploader | https://api.github.com/repos/tidepool-org/chrome-uploader | closed | Large basal schedules cause upload failure | bug: development priority: medium severity: major | ### Description
When a 600-series pump has a large basal schedule (tested with 1 per hour), pump download fails.
### Steps to Reproduce
1. Create a new basal schedule on the pump with a different basal rate every hour
1. Attempt to download data from pump
### Environment
**Uploader version**: 0.310.0-alpha.11.135.gb0298b2e
**OS**: macOS | 1.0 | Large basal schedules cause upload failure - ### Description
When a 600-series pump has a large basal schedule (tested with 1 per hour), pump download fails.
### Steps to Reproduce
1. Create a new basal schedule on the pump with a different basal rate every hour
1. Attempt to download data from pump
### Environment
**Uploader version**: 0.310.0-alpha.11.135.gb0298b2e
**OS**: macOS | priority | large basal schedules cause upload failure description when a series pump has a large basal schedule tested with per hour pump download fails steps to reproduce create a new basal schedule on the pump with a different basal rate every hour attempt to download data from pump environment uploader version alpha os macos | 1 |
175,561 | 6,552,277,584 | IssuesEvent | 2017-09-05 17:40:41 | washingtonstateuniversity/WSU-People-Directory | https://api.github.com/repos/washingtonstateuniversity/WSU-People-Directory | reopened | Introduce a base person object that provides consistent profile data | enhancement priority:medium | It should be possible to write `$person = get_wsu_person( 123 );` or similar and get back a `WSU_Person` object (or similar) and then reference stuff like:
```
First Name: <?php echo esc_html( $person->ad_first_name ); ?>
Last Name: <?php echo esc_html( $person->ad_last_name ); ?>
```
This can probably allow for easy extension by others in the future. It should also help us avoid rewriting similar code in many places to capture all of the various fields associated with a person.
I don't think this is time critical, but could come in handy soon. | 1.0 | Introduce a base person object that provides consistent profile data - It should be possible to write `$person = get_wsu_person( 123 );` or similar and get back a `WSU_Person` object (or similar) and then reference stuff like:
```
First Name: <?php echo esc_html( $person->ad_first_name ); ?>
Last Name: <?php echo esc_html( $person->ad_last_name ); ?>
```
This can probably allow for easy extension by others in the future. It should also help us avoid rewriting similar code in many places to capture all of the various fields associated with a person.
I don't think this is time critical, but could come in handy soon. | priority | introduce a base person object that provides consistent profile data it should be possible to write person get wsu person or similar and get back a wsu person object or similar and then reference stuff like first name ad first name last name ad last name this can probably allow for easy extension by others in the future it should also help us avoid rewriting similar code in many places to capture all of the various fields associated with a person i don t think this is time critical but could come in handy soon | 1 |
198,874 | 22,674,173,260 | IssuesEvent | 2022-07-04 01:24:21 | Souparnee/WebGoat2_20022020 | https://api.github.com/repos/Souparnee/WebGoat2_20022020 | opened | CVE-2021-23440 (High) detected in set-value-0.4.3.tgz, set-value-2.0.0.tgz | security vulnerability | ## CVE-2021-23440 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>set-value-0.4.3.tgz</b>, <b>set-value-2.0.0.tgz</b></p></summary>
<p>
<details><summary><b>set-value-0.4.3.tgz</b></p></summary>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-0.4.3.tgz">https://registry.npmjs.org/set-value/-/set-value-0.4.3.tgz</a></p>
<p>Path to dependency file: /docs/package.json</p>
<p>Path to vulnerable library: /docs/node_modules/union-value/node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- browser-sync-2.26.3.tgz (Root Library)
- chokidar-2.0.4.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- union-value-1.0.0.tgz
- :x: **set-value-0.4.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>set-value-2.0.0.tgz</b></p></summary>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-2.0.0.tgz">https://registry.npmjs.org/set-value/-/set-value-2.0.0.tgz</a></p>
<p>Path to dependency file: /docs/package.json</p>
<p>Path to vulnerable library: /docs/node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- browser-sync-2.26.3.tgz (Root Library)
- chokidar-2.0.4.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- :x: **set-value-2.0.0.tgz** (Vulnerable Library)
</details>
</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 set-value before <2.0.1, >=3.0.0 <4.0.1. A type confusion vulnerability can lead to a bypass of CVE-2019-10747 when the user-provided keys used in the path parameter are arrays.
<p>Publish Date: 2021-09-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23440>CVE-2021-23440</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-2021-23440">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23440</a></p>
<p>Release Date: 2021-09-12</p>
<p>Fix Resolution (set-value): 2.0.1</p>
<p>Direct dependency fix Resolution (browser-sync): 2.26.4</p><p>Fix Resolution (set-value): 2.0.1</p>
<p>Direct dependency fix Resolution (browser-sync): 2.26.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-2021-23440 (High) detected in set-value-0.4.3.tgz, set-value-2.0.0.tgz - ## CVE-2021-23440 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>set-value-0.4.3.tgz</b>, <b>set-value-2.0.0.tgz</b></p></summary>
<p>
<details><summary><b>set-value-0.4.3.tgz</b></p></summary>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-0.4.3.tgz">https://registry.npmjs.org/set-value/-/set-value-0.4.3.tgz</a></p>
<p>Path to dependency file: /docs/package.json</p>
<p>Path to vulnerable library: /docs/node_modules/union-value/node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- browser-sync-2.26.3.tgz (Root Library)
- chokidar-2.0.4.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- union-value-1.0.0.tgz
- :x: **set-value-0.4.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>set-value-2.0.0.tgz</b></p></summary>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-2.0.0.tgz">https://registry.npmjs.org/set-value/-/set-value-2.0.0.tgz</a></p>
<p>Path to dependency file: /docs/package.json</p>
<p>Path to vulnerable library: /docs/node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- browser-sync-2.26.3.tgz (Root Library)
- chokidar-2.0.4.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- :x: **set-value-2.0.0.tgz** (Vulnerable Library)
</details>
</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 set-value before <2.0.1, >=3.0.0 <4.0.1. A type confusion vulnerability can lead to a bypass of CVE-2019-10747 when the user-provided keys used in the path parameter are arrays.
<p>Publish Date: 2021-09-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23440>CVE-2021-23440</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-2021-23440">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23440</a></p>
<p>Release Date: 2021-09-12</p>
<p>Fix Resolution (set-value): 2.0.1</p>
<p>Direct dependency fix Resolution (browser-sync): 2.26.4</p><p>Fix Resolution (set-value): 2.0.1</p>
<p>Direct dependency fix Resolution (browser-sync): 2.26.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 set value tgz set value tgz cve high severity vulnerability vulnerable libraries set value tgz set value tgz set value tgz create nested values and any intermediaries using dot notation a b c paths library home page a href path to dependency file docs package json path to vulnerable library docs node modules union value node modules set value package json dependency hierarchy browser sync tgz root library chokidar tgz braces tgz snapdragon tgz base tgz cache base tgz union value tgz x set value tgz vulnerable library set value tgz create nested values and any intermediaries using dot notation a b c paths library home page a href path to dependency file docs package json path to vulnerable library docs node modules set value package json dependency hierarchy browser sync tgz root library chokidar tgz braces tgz snapdragon tgz base tgz cache base tgz x set value tgz vulnerable library vulnerability details this affects the package set value before a type confusion vulnerability can lead to a bypass of cve when the user provided keys used in the path parameter are arrays 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 set value direct dependency fix resolution browser sync fix resolution set value direct dependency fix resolution browser sync step up your open source security game with mend | 0 |
162,707 | 20,241,925,025 | IssuesEvent | 2022-02-14 10:06:04 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | reopened | security: add support for "SCIM" user to provision accounts | C-enhancement A-security T-sql-experience | This is a common pattern for companies using Kerberos, and that it would be a common requirement from financial institutions.
Here's why this is necessary; a "SCIM" user does not have access to the data itself and also should not have the ability to add credentials to new accounts. Because Kerberos is handling account credentials outside of the database, users will be able to properly authenticate without the SCIM user defining passwords for their accounts. Therefore, if the SCIM user is compromised and a bad actor creates a new account with privileges to read/write arbitrary data, they will not actually be able to log into the account they created without properly authenticating through Kerberos.
**Jira**: [CRDB-1663](https://cockroachlabs.atlassian.net/browse/CRDB-1663)
**Zendesk**: [6720](https://cockroachdb.zendesk.com/agent/tickets/6720)
The main pieces of work we've identified would be to:
- Allow users/roles to grant access to and grant usage of schema objects without having usage privileges themselves
- Allow users/roles to create accounts without assigning credentials to the account
gz#6720 | True | security: add support for "SCIM" user to provision accounts - This is a common pattern for companies using Kerberos, and that it would be a common requirement from financial institutions.
Here's why this is necessary; a "SCIM" user does not have access to the data itself and also should not have the ability to add credentials to new accounts. Because Kerberos is handling account credentials outside of the database, users will be able to properly authenticate without the SCIM user defining passwords for their accounts. Therefore, if the SCIM user is compromised and a bad actor creates a new account with privileges to read/write arbitrary data, they will not actually be able to log into the account they created without properly authenticating through Kerberos.
**Jira**: [CRDB-1663](https://cockroachlabs.atlassian.net/browse/CRDB-1663)
**Zendesk**: [6720](https://cockroachdb.zendesk.com/agent/tickets/6720)
The main pieces of work we've identified would be to:
- Allow users/roles to grant access to and grant usage of schema objects without having usage privileges themselves
- Allow users/roles to create accounts without assigning credentials to the account
gz#6720 | non_priority | security add support for scim user to provision accounts this is a common pattern for companies using kerberos and that it would be a common requirement from financial institutions here s why this is necessary a scim user does not have access to the data itself and also should not have the ability to add credentials to new accounts because kerberos is handling account credentials outside of the database users will be able to properly authenticate without the scim user defining passwords for their accounts therefore if the scim user is compromised and a bad actor creates a new account with privileges to read write arbitrary data they will not actually be able to log into the account they created without properly authenticating through kerberos jira zendesk the main pieces of work we ve identified would be to allow users roles to grant access to and grant usage of schema objects without having usage privileges themselves allow users roles to create accounts without assigning credentials to the account gz | 0 |
55,836 | 11,470,627,894 | IssuesEvent | 2020-02-09 04:52:55 | talonos2/FinalWinterBugs | https://api.github.com/repos/talonos2/FinalWinterBugs | closed | running out of time during combat locks controls | bug code | after running out of time during a combat (even using "m" key) the player returns to town and is unable to move. They can start the next dungeon run, but will still be unable to move or talk (day 6 NPC is standing next to you), and will still be unable to move when returning to town from that (death by "m" key). This even persists when you exit to the main menu and then load the game.
If you exit the game completely, open it, and then load your file the character will respond to commands again. | 1.0 | running out of time during combat locks controls - after running out of time during a combat (even using "m" key) the player returns to town and is unable to move. They can start the next dungeon run, but will still be unable to move or talk (day 6 NPC is standing next to you), and will still be unable to move when returning to town from that (death by "m" key). This even persists when you exit to the main menu and then load the game.
If you exit the game completely, open it, and then load your file the character will respond to commands again. | non_priority | running out of time during combat locks controls after running out of time during a combat even using m key the player returns to town and is unable to move they can start the next dungeon run but will still be unable to move or talk day npc is standing next to you and will still be unable to move when returning to town from that death by m key this even persists when you exit to the main menu and then load the game if you exit the game completely open it and then load your file the character will respond to commands again | 0 |
369,712 | 25,864,948,381 | IssuesEvent | 2022-12-13 20:01:33 | fga-eps-mds/2022-2-QuantiFGA | https://api.github.com/repos/fga-eps-mds/2022-2-QuantiFGA | closed | Determinação de Requisitos | documentation | ### Descrição
- Realização do UML e do Requisitos de Software
### Objetivo
- Criar um arquivo para o UML do projeto e todos os requisitos de software (funcionais, não funcionais, de dados e execução)
### Tarefas
- [x] Fazer os requisitos
- [x] Fazer o UML
### Comentários
- Arquivo UML em formato de .png e requisitos em formato .pdf | 1.0 | Determinação de Requisitos - ### Descrição
- Realização do UML e do Requisitos de Software
### Objetivo
- Criar um arquivo para o UML do projeto e todos os requisitos de software (funcionais, não funcionais, de dados e execução)
### Tarefas
- [x] Fazer os requisitos
- [x] Fazer o UML
### Comentários
- Arquivo UML em formato de .png e requisitos em formato .pdf | non_priority | determinação de requisitos descrição realização do uml e do requisitos de software objetivo criar um arquivo para o uml do projeto e todos os requisitos de software funcionais não funcionais de dados e execução tarefas fazer os requisitos fazer o uml comentários arquivo uml em formato de png e requisitos em formato pdf | 0 |
139,342 | 5,367,718,770 | IssuesEvent | 2017-02-22 05:46:46 | fossasia/open-event-webapp | https://api.github.com/repos/fossasia/open-event-webapp | opened | Session information unreadable - avoid shadows and gray colors. | bug Priority: Urgent | The session information shows shadows and gray colors. Previously it was readable easily, but it was changed at some point.
Please change the font to be easily readable again:
* Take out shadows
* Use black font for all components
| 1.0 | Session information unreadable - avoid shadows and gray colors. - The session information shows shadows and gray colors. Previously it was readable easily, but it was changed at some point.
Please change the font to be easily readable again:
* Take out shadows
* Use black font for all components
| priority | session information unreadable avoid shadows and gray colors the session information shows shadows and gray colors previously it was readable easily but it was changed at some point please change the font to be easily readable again take out shadows use black font for all components | 1 |
75,647 | 3,470,548,826 | IssuesEvent | 2015-12-23 09:18:00 | YetiForceCompany/YetiForceCRM | https://api.github.com/repos/YetiForceCompany/YetiForceCRM | closed | [Bug] Accounts - Switching between tabs is very slow | Label::Module Priority::#3 High Type::Bug | I tested on this record: https://gitdeveloper.yetiforce.com/index.php?module=Accounts&view=Detail&record=115&mode=showDetailViewByMode&requestMode=summary&tab_label=Summary
Developer 2.3.808
Click: Summary, Detail, Products&Services, Comments and then again P&S and then Detail etc. About every third time you have to wait a few seconds before page updates. The record I tested was related to two products: One in section "Interested in products" and one in section "Products outsourced". | 1.0 | [Bug] Accounts - Switching between tabs is very slow - I tested on this record: https://gitdeveloper.yetiforce.com/index.php?module=Accounts&view=Detail&record=115&mode=showDetailViewByMode&requestMode=summary&tab_label=Summary
Developer 2.3.808
Click: Summary, Detail, Products&Services, Comments and then again P&S and then Detail etc. About every third time you have to wait a few seconds before page updates. The record I tested was related to two products: One in section "Interested in products" and one in section "Products outsourced". | priority | accounts switching between tabs is very slow i tested on this record developer click summary detail products services comments and then again p s and then detail etc about every third time you have to wait a few seconds before page updates the record i tested was related to two products one in section interested in products and one in section products outsourced | 1 |
696,626 | 23,908,365,242 | IssuesEvent | 2022-09-09 05:01:20 | Gilded-Games/The-Aether | https://api.github.com/repos/Gilded-Games/The-Aether | closed | Feature: JEI compatibility | priority/medium status/pending-review type/compatibility type/feature version/1.19 status/dependent | - [x] Altar and Freezer recipes, with support for displaying custom fuels.
- [x] Incubators should have support to display eggs that can be incubated. | 1.0 | Feature: JEI compatibility - - [x] Altar and Freezer recipes, with support for displaying custom fuels.
- [x] Incubators should have support to display eggs that can be incubated. | priority | feature jei compatibility altar and freezer recipes with support for displaying custom fuels incubators should have support to display eggs that can be incubated | 1 |
125,596 | 26,694,089,280 | IssuesEvent | 2023-01-27 08:48:48 | wso2/ballerina-plugin-vscode | https://api.github.com/repos/wso2/ballerina-plugin-vscode | closed | Lowcode diagram does not load in codespaces | Type/Bug Priority/Highest Area/LowCode | **Description:**
Lowcode diagram does not load in codespaces
**Steps to reproduce:**
https://user-images.githubusercontent.com/36252572/214781305-74ec3cef-3421-467d-9103-3c0cb10b0752.MOV
**Affected Versions:**
**OS, DB, other environment details and versions:**
**Related Issues (optional):**
<!-- Any related issues such as sub tasks, issues reported in other repositories (e.g component repositories), similar problems, etc. -->
**Suggested Labels (optional):**
<!-- Optional comma separated list of suggested labels. Non committers can’t assign labels to issues, so this will help issue creators who are not a committer to suggest possible labels-->
**Suggested Assignees (optional):**
<!--Optional comma separated list of suggested team members who should attend the issue. Non committers can’t assign issues to assignees, so this will help issue creators who are not a committer to suggest possible assignees-->
| 1.0 | Lowcode diagram does not load in codespaces - **Description:**
Lowcode diagram does not load in codespaces
**Steps to reproduce:**
https://user-images.githubusercontent.com/36252572/214781305-74ec3cef-3421-467d-9103-3c0cb10b0752.MOV
**Affected Versions:**
**OS, DB, other environment details and versions:**
**Related Issues (optional):**
<!-- Any related issues such as sub tasks, issues reported in other repositories (e.g component repositories), similar problems, etc. -->
**Suggested Labels (optional):**
<!-- Optional comma separated list of suggested labels. Non committers can’t assign labels to issues, so this will help issue creators who are not a committer to suggest possible labels-->
**Suggested Assignees (optional):**
<!--Optional comma separated list of suggested team members who should attend the issue. Non committers can’t assign issues to assignees, so this will help issue creators who are not a committer to suggest possible assignees-->
| non_priority | lowcode diagram does not load in codespaces description lowcode diagram does not load in codespaces steps to reproduce affected versions os db other environment details and versions related issues optional suggested labels optional suggested assignees optional | 0 |
21,152 | 4,683,130,331 | IssuesEvent | 2016-10-09 16:39:34 | wtfblub/NetspherePirates | https://api.github.com/repos/wtfblub/NetspherePirates | reopened | SQLite to MySQL - guide request | Documentation Question | Add guide for change and port base SQLite to MySQL.
Or add base MySQL files with guide. | 1.0 | SQLite to MySQL - guide request - Add guide for change and port base SQLite to MySQL.
Or add base MySQL files with guide. | non_priority | sqlite to mysql guide request add guide for change and port base sqlite to mysql or add base mysql files with guide | 0 |
18,171 | 3,031,492,051 | IssuesEvent | 2015-08-04 23:21:15 | googlei18n/noto-fonts | https://api.github.com/repos/googlei18n/noto-fonts | opened | Inscriptional Parthian: ligatures missing | Script-Parthian Type-Defect | Imported from Google Code issue #15 created by roozbeh@google.com on 2013-11-14T03:01:51.000Z:
The Unicode standard’s section on Inscriptional Parthian calls for nine standard ligatures. Of those, only Nun-Daleth works in the font. The other eight should also be supported. | 1.0 | Inscriptional Parthian: ligatures missing - Imported from Google Code issue #15 created by roozbeh@google.com on 2013-11-14T03:01:51.000Z:
The Unicode standard’s section on Inscriptional Parthian calls for nine standard ligatures. Of those, only Nun-Daleth works in the font. The other eight should also be supported. | non_priority | inscriptional parthian ligatures missing imported from google code issue created by roozbeh google com on the unicode standard’s section on inscriptional parthian calls for nine standard ligatures of those only nun daleth works in the font the other eight should also be supported | 0 |
65,743 | 8,838,372,793 | IssuesEvent | 2019-01-05 16:34:30 | kirill-grouchnikov/radiance | https://api.github.com/repos/kirill-grouchnikov/radiance | opened | [Substance] Add documentation on renderers | Documentation | The "old" list, table and tree renderers + the new panel list renderer. | 1.0 | [Substance] Add documentation on renderers - The "old" list, table and tree renderers + the new panel list renderer. | non_priority | add documentation on renderers the old list table and tree renderers the new panel list renderer | 0 |
142,475 | 5,475,616,507 | IssuesEvent | 2017-03-11 13:07:06 | cyberpwnn/GlacialRealms | https://api.github.com/repos/cyberpwnn/GlacialRealms | closed | /stats suggestion | 20 Minute ETA cosmetic enhancement low priority stale static | currently in /stats it displays your time online in the highest "category" you have reached. if you have no more than 24hrs it will display in hours, no more than 30d and it will display in days, and then it starts displaying in months, only increasing to the next month every 30d of game time. this is extremely annoying when trying to find your ingame time. i propose that time online be displayed in Years:days:hours format. | 1.0 | /stats suggestion - currently in /stats it displays your time online in the highest "category" you have reached. if you have no more than 24hrs it will display in hours, no more than 30d and it will display in days, and then it starts displaying in months, only increasing to the next month every 30d of game time. this is extremely annoying when trying to find your ingame time. i propose that time online be displayed in Years:days:hours format. | priority | stats suggestion currently in stats it displays your time online in the highest category you have reached if you have no more than it will display in hours no more than and it will display in days and then it starts displaying in months only increasing to the next month every of game time this is extremely annoying when trying to find your ingame time i propose that time online be displayed in years days hours format | 1 |
68,477 | 13,144,895,456 | IssuesEvent | 2020-08-08 00:35:38 | rathena/rathena | https://api.github.com/repos/rathena/rathena | closed | Removes waitingroom check for Maya Purple hackfix | component:script mode:prerenewal mode:renewal priority:low status:code-review type:bug | <!-- NOTE: Anything within these brackets will be hidden on the preview of the Issue. -->
* **rAthena Hash**: 9991b09
* **Client Date**: 2018
* **Server Mode**: renewal
<!-- Which mode does your server use: Pre-Renewal or Renewal? -->
* **Description of Issue**: Job quest Waiting rooms are gone
* Result: while doing job quests, the waiting room above NPCs are gone and players cant progress during the job change quest
* Expected Result: waiting room should be there
* How to Reproduce: do knight or assassin job quest
i believe its related to this https://github.com/rathena/rathena/commit/1c6270f96ac3c56fa0e41349977f73a40a229a39 | 1.0 | Removes waitingroom check for Maya Purple hackfix - <!-- NOTE: Anything within these brackets will be hidden on the preview of the Issue. -->
* **rAthena Hash**: 9991b09
* **Client Date**: 2018
* **Server Mode**: renewal
<!-- Which mode does your server use: Pre-Renewal or Renewal? -->
* **Description of Issue**: Job quest Waiting rooms are gone
* Result: while doing job quests, the waiting room above NPCs are gone and players cant progress during the job change quest
* Expected Result: waiting room should be there
* How to Reproduce: do knight or assassin job quest
i believe its related to this https://github.com/rathena/rathena/commit/1c6270f96ac3c56fa0e41349977f73a40a229a39 | non_priority | removes waitingroom check for maya purple hackfix rathena hash client date server mode renewal description of issue job quest waiting rooms are gone result while doing job quests the waiting room above npcs are gone and players cant progress during the job change quest expected result waiting room should be there how to reproduce do knight or assassin job quest i believe its related to this | 0 |
743,210 | 25,891,385,042 | IssuesEvent | 2022-12-14 18:14:48 | ramp4-pcar4/ramp4-pcar4 | https://api.github.com/repos/ramp4-pcar4/ramp4-pcar4 | opened | Geosearch service is dead | flavour: bug priority: must type: corrective | Geosearch no longer works 👎
The service returns a code 500 (internal server error) and the following message is in the console:
> Failed to load resource: the server responded with a status of 500 (Internal Server Error)
I guess we can't really do much about about the service. But if the URL breaks, we should have some sort of error message in our UI instead of the results loading perpetually and the dropdown menus empty. | 1.0 | Geosearch service is dead - Geosearch no longer works 👎
The service returns a code 500 (internal server error) and the following message is in the console:
> Failed to load resource: the server responded with a status of 500 (Internal Server Error)
I guess we can't really do much about about the service. But if the URL breaks, we should have some sort of error message in our UI instead of the results loading perpetually and the dropdown menus empty. | priority | geosearch service is dead geosearch no longer works 👎 the service returns a code internal server error and the following message is in the console failed to load resource the server responded with a status of internal server error i guess we can t really do much about about the service but if the url breaks we should have some sort of error message in our ui instead of the results loading perpetually and the dropdown menus empty | 1 |
815,462 | 30,556,190,628 | IssuesEvent | 2023-07-20 11:52:42 | ubiquity/ubiquibot | https://api.github.com/repos/ubiquity/ubiquibot | closed | Query User Information (Wallet Address, Multiplier) | Time: <1 Hour Priority: 1 (Medium) Price: 37.5 USD | I have been doing some manual payouts lately and realized that sometimes it's nice to be able to quickly identify a user's `multiplier` and `wallet` address without superuser access to the global bot database!
We should have a new command to view a user's settings.
`/query @user`
Unless there is a better, more expressive command name than "query"
---
> I'll need to send some xDAI to both participants because this was my fault for not ensuring that the bounty is valid.
> https://gnosisscan.io/tx/0x3162608e9e18f71b4b29b0780904b664d160d0d79b0f761569f0d590b5f16044 @me505
> https://gnosisscan.io/tx/0xbb9e74ab8951f5cc45fb38dd1d56f7e04e3c0ba6db98bfbaf58bfe63043d950a @AnakinSkywalkeer
_Originally posted by @pavlovcik in https://github.com/ubiquity/ubiquity-dollar/issues/562#issuecomment-1630854865_
| 1.0 | Query User Information (Wallet Address, Multiplier) - I have been doing some manual payouts lately and realized that sometimes it's nice to be able to quickly identify a user's `multiplier` and `wallet` address without superuser access to the global bot database!
We should have a new command to view a user's settings.
`/query @user`
Unless there is a better, more expressive command name than "query"
---
> I'll need to send some xDAI to both participants because this was my fault for not ensuring that the bounty is valid.
> https://gnosisscan.io/tx/0x3162608e9e18f71b4b29b0780904b664d160d0d79b0f761569f0d590b5f16044 @me505
> https://gnosisscan.io/tx/0xbb9e74ab8951f5cc45fb38dd1d56f7e04e3c0ba6db98bfbaf58bfe63043d950a @AnakinSkywalkeer
_Originally posted by @pavlovcik in https://github.com/ubiquity/ubiquity-dollar/issues/562#issuecomment-1630854865_
| priority | query user information wallet address multiplier i have been doing some manual payouts lately and realized that sometimes it s nice to be able to quickly identify a user s multiplier and wallet address without superuser access to the global bot database we should have a new command to view a user s settings query user unless there is a better more expressive command name than query i ll need to send some xdai to both participants because this was my fault for not ensuring that the bounty is valid anakinskywalkeer originally posted by pavlovcik in | 1 |
36,449 | 2,799,355,455 | IssuesEvent | 2015-05-12 23:58:54 | osulp/primo | https://api.github.com/repos/osulp/primo | reopened | Fix indenting issue when visiting a permalinked page | High Priority | The record is displayed on the right half of the page, leaving a large open area to the left.
Example:
http://search.library.oregonstate.edu/OSU:CP71137462960001451 | 1.0 | Fix indenting issue when visiting a permalinked page - The record is displayed on the right half of the page, leaving a large open area to the left.
Example:
http://search.library.oregonstate.edu/OSU:CP71137462960001451 | priority | fix indenting issue when visiting a permalinked page the record is displayed on the right half of the page leaving a large open area to the left example | 1 |
762,800 | 26,731,034,862 | IssuesEvent | 2023-01-30 04:31:35 | wso2/product-apim | https://api.github.com/repos/wso2/product-apim | closed | read only user for the APIM Publisher portal | Type/New Feature Priority/Normal 4.x.x | ### Describe your problem(s)
The requirement is:
A user (internal developer) who has permission to only view the API details in the Publisher portal. The user should not be able to edit/create/publish APIs. The user should only be able to view the API configurations. And only "privileged users" (internal developers they decide) will have permission to edit/create/publish APIs as it is possible right now.
Currently, It kind of work but need to improve some places by doing error handling and hiding some UI components
https://www.youtube.com/watch?v=UwbNoQluH_o
### Related issue
https://github.com/wso2/product-apim/issues/8812
| 1.0 | read only user for the APIM Publisher portal - ### Describe your problem(s)
The requirement is:
A user (internal developer) who has permission to only view the API details in the Publisher portal. The user should not be able to edit/create/publish APIs. The user should only be able to view the API configurations. And only "privileged users" (internal developers they decide) will have permission to edit/create/publish APIs as it is possible right now.
Currently, It kind of work but need to improve some places by doing error handling and hiding some UI components
https://www.youtube.com/watch?v=UwbNoQluH_o
### Related issue
https://github.com/wso2/product-apim/issues/8812
| priority | read only user for the apim publisher portal describe your problem s the requirement is a user internal developer who has permission to only view the api details in the publisher portal the user should not be able to edit create publish apis the user should only be able to view the api configurations and only privileged users internal developers they decide will have permission to edit create publish apis as it is possible right now currently it kind of work but need to improve some places by doing error handling and hiding some ui components related issue | 1 |
784,150 | 27,559,699,829 | IssuesEvent | 2023-03-07 20:52:36 | Vladyslav-Team/backend | https://api.github.com/repos/Vladyslav-Team/backend | opened | Add the ability to edit fields and save or delete changes only your account | lowPriority database backEnd | User must be authorized to change it's account
| 1.0 | Add the ability to edit fields and save or delete changes only your account - User must be authorized to change it's account
| priority | add the ability to edit fields and save or delete changes only your account user must be authorized to change it s account | 1 |
700,875 | 24,076,438,531 | IssuesEvent | 2022-09-18 21:21:56 | svelascodimate/demo | https://api.github.com/repos/svelascodimate/demo | opened | Create Project Structure | High Priority New Feature | # User Story
As a Project Lead, want to have a basic project structure on the repository so that Development Team could start making changes in the code.
# List of tasks
- [ ] Update Python
- [ ] Install nbdev on local machine
- [ ] Run command nbdev_new
- [ ] Modify settings.init
- [ ] Create Docker File
- [ ] Create Notebook with Project Description
# Definition of Done
- [ ] The project must be uploaded to gitlab
- [ ] All students understand the project-logistics | 1.0 | Create Project Structure - # User Story
As a Project Lead, want to have a basic project structure on the repository so that Development Team could start making changes in the code.
# List of tasks
- [ ] Update Python
- [ ] Install nbdev on local machine
- [ ] Run command nbdev_new
- [ ] Modify settings.init
- [ ] Create Docker File
- [ ] Create Notebook with Project Description
# Definition of Done
- [ ] The project must be uploaded to gitlab
- [ ] All students understand the project-logistics | priority | create project structure user story as a project lead want to have a basic project structure on the repository so that development team could start making changes in the code list of tasks update python install nbdev on local machine run command nbdev new modify settings init create docker file create notebook with project description definition of done the project must be uploaded to gitlab all students understand the project logistics | 1 |
69,769 | 15,030,909,188 | IssuesEvent | 2021-02-02 08:12:23 | NixOS/nixpkgs | https://api.github.com/repos/NixOS/nixpkgs | closed | Vulnerability roundup 98: gdk-pixbuf-2.40.0: 1 advisory [5.5] | 1.severity: security | [search](https://search.nix.gsc.io/?q=gdk-pixbuf&i=fosho&repos=NixOS-nixpkgs), [files](https://github.com/NixOS/nixpkgs/search?utf8=%E2%9C%93&q=gdk-pixbuf+in%3Apath&type=Code)
* [ ] [CVE-2020-29385](https://nvd.nist.gov/vuln/detail/CVE-2020-29385) CVSSv3=5.5 (nixos-20.09)
Scanned versions: nixos-20.09: aa5b9cd16b9.
Cc @dasj19
Cc @edolstra
Cc @hedning
Cc @jtojnar
Cc @worldofpeace
| True | Vulnerability roundup 98: gdk-pixbuf-2.40.0: 1 advisory [5.5] - [search](https://search.nix.gsc.io/?q=gdk-pixbuf&i=fosho&repos=NixOS-nixpkgs), [files](https://github.com/NixOS/nixpkgs/search?utf8=%E2%9C%93&q=gdk-pixbuf+in%3Apath&type=Code)
* [ ] [CVE-2020-29385](https://nvd.nist.gov/vuln/detail/CVE-2020-29385) CVSSv3=5.5 (nixos-20.09)
Scanned versions: nixos-20.09: aa5b9cd16b9.
Cc @dasj19
Cc @edolstra
Cc @hedning
Cc @jtojnar
Cc @worldofpeace
| non_priority | vulnerability roundup gdk pixbuf advisory nixos scanned versions nixos cc cc edolstra cc hedning cc jtojnar cc worldofpeace | 0 |
453,208 | 13,066,561,936 | IssuesEvent | 2020-07-30 21:58:53 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.anilibria.tv - Switching the video to full-screen mode is faulty | browser-firefox-mobile engine-gecko priority-normal severity-important | <!-- @browser: Firefox Mobile 80.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:80.0) Gecko/80.0 Firefox/80.0 -->
<!-- @reported_with: desktop-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/56022 -->
**URL**: https://www.anilibria.tv/release/black-clover.html
**Browser / Version**: Firefox Mobile 80.0
**Operating System**: Android
**Tested Another Browser**: Yes Chrome
**Problem type**: Something else
**Description**: The video on the website is not displayed correctly in full screen mode.
**Steps to Reproduce**:
The "anilibria.tv" website does not display correctly when watching videos in full screen. Full screen mode does not fill the entire screen, and there is an empty space.
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2020/7/0fa7f3ad-7556-4cdc-ad54-2a0901c20d3e.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20200727095125</li><li>channel: nightly</li><li>hasTouchScreen: true</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.anilibria.tv - Switching the video to full-screen mode is faulty - <!-- @browser: Firefox Mobile 80.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:80.0) Gecko/80.0 Firefox/80.0 -->
<!-- @reported_with: desktop-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/56022 -->
**URL**: https://www.anilibria.tv/release/black-clover.html
**Browser / Version**: Firefox Mobile 80.0
**Operating System**: Android
**Tested Another Browser**: Yes Chrome
**Problem type**: Something else
**Description**: The video on the website is not displayed correctly in full screen mode.
**Steps to Reproduce**:
The "anilibria.tv" website does not display correctly when watching videos in full screen. Full screen mode does not fill the entire screen, and there is an empty space.
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2020/7/0fa7f3ad-7556-4cdc-ad54-2a0901c20d3e.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20200727095125</li><li>channel: nightly</li><li>hasTouchScreen: true</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | switching the video to full screen mode is faulty url browser version firefox mobile operating system android tested another browser yes chrome problem type something else description the video on the website is not displayed correctly in full screen mode steps to reproduce the anilibria tv website does not display correctly when watching videos in full screen full screen mode does not fill the entire screen and there is an empty space view the screenshot img alt screenshot src browser configuration gfx webrender all false gfx webrender blob images true gfx webrender enabled false image mem shared true buildid channel nightly hastouchscreen true from with ❤️ | 1 |
235,643 | 18,054,111,268 | IssuesEvent | 2021-09-20 05:01:26 | bstudios/adam-rms | https://api.github.com/repos/bstudios/adam-rms | opened | [DOCS] Various Documentation updates | documentation | ### What would you like the training to cover?
- [ ] Interface introduction (what do Icons mean etc)
- [ ] User account pages
- [ ] Linked asset documentation (child vs parent)
- [ ] Public Site
### Is this already partially covered elsewhere?
No
### Anything else?
_No response_ | 1.0 | [DOCS] Various Documentation updates - ### What would you like the training to cover?
- [ ] Interface introduction (what do Icons mean etc)
- [ ] User account pages
- [ ] Linked asset documentation (child vs parent)
- [ ] Public Site
### Is this already partially covered elsewhere?
No
### Anything else?
_No response_ | non_priority | various documentation updates what would you like the training to cover interface introduction what do icons mean etc user account pages linked asset documentation child vs parent public site is this already partially covered elsewhere no anything else no response | 0 |
121,406 | 10,167,709,551 | IssuesEvent | 2019-08-07 18:54:16 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | [test-failed]: X-Pack Chromium API Reporting Tests.x-pack/test/reporting/api/usage·js - chromium reporting usage from new jobs posted print_layout pdf | failed-test test-darwin | **Version: 7.3**
**Class: X-Pack Chromium API Reporting Tests.x-pack/test/reporting/api/usage·js**
**Stack Trace:**
[Error: Timeout of 360000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.]
_Platform: darwin_
_Build Num: 36_ | 2.0 | [test-failed]: X-Pack Chromium API Reporting Tests.x-pack/test/reporting/api/usage·js - chromium reporting usage from new jobs posted print_layout pdf - **Version: 7.3**
**Class: X-Pack Chromium API Reporting Tests.x-pack/test/reporting/api/usage·js**
**Stack Trace:**
[Error: Timeout of 360000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.]
_Platform: darwin_
_Build Num: 36_ | non_priority | x pack chromium api reporting tests x pack test reporting api usage·js chromium reporting usage from new jobs posted print layout pdf version class x pack chromium api reporting tests x pack test reporting api usage·js stack trace platform darwin build num | 0 |
39,143 | 8,584,399,671 | IssuesEvent | 2018-11-13 22:39:10 | sourcegraph/sourcegraph | https://api.github.com/repos/sourcegraph/sourcegraph | opened | Cross-language API/IDL support (GraphQL, Thrift, Protobuf) | feature:code-intel roadmap | We will be adding support for cross-language API/IDL systems to Sourcegraph, in order of priority:
- [GraphQL](https://sourcegraph.com/github.com/sourcegraph/about/-/blob/projects/graphql-sourcegraph-extension.md) (partially done)
- Thrift
- Protobuf
You will be able to see hovers with documentation, go to definition, find references, etc., in API/IDL definition *and* code that is generated from them.
Details TBD. | 1.0 | Cross-language API/IDL support (GraphQL, Thrift, Protobuf) - We will be adding support for cross-language API/IDL systems to Sourcegraph, in order of priority:
- [GraphQL](https://sourcegraph.com/github.com/sourcegraph/about/-/blob/projects/graphql-sourcegraph-extension.md) (partially done)
- Thrift
- Protobuf
You will be able to see hovers with documentation, go to definition, find references, etc., in API/IDL definition *and* code that is generated from them.
Details TBD. | non_priority | cross language api idl support graphql thrift protobuf we will be adding support for cross language api idl systems to sourcegraph in order of priority partially done thrift protobuf you will be able to see hovers with documentation go to definition find references etc in api idl definition and code that is generated from them details tbd | 0 |
163,722 | 6,204,494,252 | IssuesEvent | 2017-07-06 14:20:10 | qutebrowser/qutebrowser | https://api.github.com/repos/qutebrowser/qutebrowser | closed | Clear temporary settings | component: config config revolution priority: 1 - middle | It would be nice to have a command to clear temporary settings (`set -t`) without having to restart the browser.
| 1.0 | Clear temporary settings - It would be nice to have a command to clear temporary settings (`set -t`) without having to restart the browser.
| priority | clear temporary settings it would be nice to have a command to clear temporary settings set t without having to restart the browser | 1 |
73,135 | 3,407,811,118 | IssuesEvent | 2015-12-04 06:26:59 | JukkaL/mypy | https://api.github.com/repos/JukkaL/mypy | closed | super() and multiple inheritance | bug priority | Mypy gives bogus complaints about missing attributes when using `super()` in a class with multiple bases. | 1.0 | super() and multiple inheritance - Mypy gives bogus complaints about missing attributes when using `super()` in a class with multiple bases. | priority | super and multiple inheritance mypy gives bogus complaints about missing attributes when using super in a class with multiple bases | 1 |
397,672 | 11,731,172,764 | IssuesEvent | 2020-03-10 23:16:19 | openforcefield/openforcefield | https://api.github.com/repos/openforcefield/openforcefield | closed | Constrain H-bond lengths by default in appropriate OFFXML files | effort:low priority:high | Per @cbayly13 's post: https://openforcefieldgroup.slack.com/archives/C9NGV68BY/p1548376758135600 :
> Given the provenance of SMIRNOFF99Frosst, being from amber-type simulation force fields routinely employing constraints on bonds to hydrogen, I think that should be the default for SMIRNOFF99Frosst too.
This should certainly be applied to `openforcefield/data/forcefield/smirnoff99Frosst.offxml`. I'm on the fence about other `offxml`s, as they've already been used to generate data, so it might be best to leave them as they are for provenance.
I do not think that constraining _all_ H-bonds should be default behavior for the toolkit at this time, as we don't have a keyword for _not_ constraining something, therefore there wouldn't be a way for users to specify non-constrained hydrogen bonds. | 1.0 | Constrain H-bond lengths by default in appropriate OFFXML files - Per @cbayly13 's post: https://openforcefieldgroup.slack.com/archives/C9NGV68BY/p1548376758135600 :
> Given the provenance of SMIRNOFF99Frosst, being from amber-type simulation force fields routinely employing constraints on bonds to hydrogen, I think that should be the default for SMIRNOFF99Frosst too.
This should certainly be applied to `openforcefield/data/forcefield/smirnoff99Frosst.offxml`. I'm on the fence about other `offxml`s, as they've already been used to generate data, so it might be best to leave them as they are for provenance.
I do not think that constraining _all_ H-bonds should be default behavior for the toolkit at this time, as we don't have a keyword for _not_ constraining something, therefore there wouldn't be a way for users to specify non-constrained hydrogen bonds. | priority | constrain h bond lengths by default in appropriate offxml files per s post given the provenance of being from amber type simulation force fields routinely employing constraints on bonds to hydrogen i think that should be the default for too this should certainly be applied to openforcefield data forcefield offxml i m on the fence about other offxml s as they ve already been used to generate data so it might be best to leave them as they are for provenance i do not think that constraining all h bonds should be default behavior for the toolkit at this time as we don t have a keyword for not constraining something therefore there wouldn t be a way for users to specify non constrained hydrogen bonds | 1 |
638,803 | 20,738,735,084 | IssuesEvent | 2022-03-14 15:48:13 | LLK/scratchjr | https://api.github.com/repos/LLK/scratchjr | closed | Can't add reshape points to sharp triangle upper right border in the paint editor | priority 3 High Severity Low Impact Jira needed | ### Expected Behavior
Should add points where the mouse is up
### Actual Behavior
The paint editor add a point to the upper left border
### Steps to Reproduce
1. open the painter to create a new sprite
2. select the `triangle` shape tool
3. draw a sharp triangle, the angle of top corner is less than 30 degree, the sharper the better
4. change to the `select` mode
5. click the upper right border near the top to add a reshape point
### Device and Operating System
This can be reproduced on Android, iOS and macOS
| 1.0 | Can't add reshape points to sharp triangle upper right border in the paint editor - ### Expected Behavior
Should add points where the mouse is up
### Actual Behavior
The paint editor add a point to the upper left border
### Steps to Reproduce
1. open the painter to create a new sprite
2. select the `triangle` shape tool
3. draw a sharp triangle, the angle of top corner is less than 30 degree, the sharper the better
4. change to the `select` mode
5. click the upper right border near the top to add a reshape point
### Device and Operating System
This can be reproduced on Android, iOS and macOS
| priority | can t add reshape points to sharp triangle upper right border in the paint editor expected behavior should add points where the mouse is up actual behavior the paint editor add a point to the upper left border steps to reproduce open the painter to create a new sprite select the triangle shape tool draw a sharp triangle the angle of top corner is less than degree the sharper the better change to the select mode click the upper right border near the top to add a reshape point device and operating system this can be reproduced on android ios and macos | 1 |
791,860 | 27,880,304,732 | IssuesEvent | 2023-03-21 18:51:40 | Parritz/LuaCompact | https://api.github.com/repos/Parritz/LuaCompact | opened | Add help command | enhancement low priority | **Is your feature request related to a problem? Please describe.**
There is currently no help command for people who don't remember a command.
**Describe the solution you'd like**
There should be a help command that describes what commands do, their arguments (if any), and their flags (if any). | 1.0 | Add help command - **Is your feature request related to a problem? Please describe.**
There is currently no help command for people who don't remember a command.
**Describe the solution you'd like**
There should be a help command that describes what commands do, their arguments (if any), and their flags (if any). | priority | add help command is your feature request related to a problem please describe there is currently no help command for people who don t remember a command describe the solution you d like there should be a help command that describes what commands do their arguments if any and their flags if any | 1 |
832,096 | 32,072,174,530 | IssuesEvent | 2023-09-25 08:43:58 | libre-tube/LibreTube | https://api.github.com/repos/libre-tube/LibreTube | closed | Lower quality when video isn't full screen | enhancement priority: low | ### Describe your suggested feature
The official YouTube app has an option to decrease video quality when a video it is not in full screen (usually this is portrait mode). This would be a worth while feature since it significantly reduces stress on Piped instances and users' personal data usage.
### Other details
_No response_
### Acknowledgements
- [X] I have searched the existing issues and this is a new ticket, **NOT** a duplicate or related to another open issue.
- [X] I have written a short but informative title.
- [X] I will fill out all of the requested information in this form. | 1.0 | Lower quality when video isn't full screen - ### Describe your suggested feature
The official YouTube app has an option to decrease video quality when a video it is not in full screen (usually this is portrait mode). This would be a worth while feature since it significantly reduces stress on Piped instances and users' personal data usage.
### Other details
_No response_
### Acknowledgements
- [X] I have searched the existing issues and this is a new ticket, **NOT** a duplicate or related to another open issue.
- [X] I have written a short but informative title.
- [X] I will fill out all of the requested information in this form. | priority | lower quality when video isn t full screen describe your suggested feature the official youtube app has an option to decrease video quality when a video it is not in full screen usually this is portrait mode this would be a worth while feature since it significantly reduces stress on piped instances and users personal data usage other details no response acknowledgements i have searched the existing issues and this is a new ticket not a duplicate or related to another open issue i have written a short but informative title i will fill out all of the requested information in this form | 1 |
76,404 | 9,437,708,232 | IssuesEvent | 2019-04-13 17:15:28 | whiteyhat/Lightning-Network-Simulator | https://api.github.com/repos/whiteyhat/Lightning-Network-Simulator | closed | Create UML Diagrams | Design enhancement | Design behavioural and structural diagrams using the UML standard. The diagrams should contain enough design insights about the internal architecture of the lightning network simulator.
### Structural UML Diagrams
- [x] UML Class Diagram
- [ ] UML Object Diagram
### Behavioural UML Diagrams
- [x] UML Use Case Diagram
- [ ] UML Sequence Diagram
### Pseudo code
- [x] Pseudo code diagrams | 1.0 | Create UML Diagrams - Design behavioural and structural diagrams using the UML standard. The diagrams should contain enough design insights about the internal architecture of the lightning network simulator.
### Structural UML Diagrams
- [x] UML Class Diagram
- [ ] UML Object Diagram
### Behavioural UML Diagrams
- [x] UML Use Case Diagram
- [ ] UML Sequence Diagram
### Pseudo code
- [x] Pseudo code diagrams | non_priority | create uml diagrams design behavioural and structural diagrams using the uml standard the diagrams should contain enough design insights about the internal architecture of the lightning network simulator structural uml diagrams uml class diagram uml object diagram behavioural uml diagrams uml use case diagram uml sequence diagram pseudo code pseudo code diagrams | 0 |
632,711 | 20,205,134,614 | IssuesEvent | 2022-02-11 19:24:14 | googleapis/gapic-generator-python | https://api.github.com/repos/googleapis/gapic-generator-python | opened | Refactor unit test templates | type: feature request priority: p3 | Currently, unit tests in templates code are all concentrated in a single file `test_%service.py.j2`. The file has 3K lines and should be refactored.
One idea is to refactor across two dimensions: transport and sync/async (cc @software-dov). It's a big effort, so perhaps a smaller task is to first identify the common boilerplate code in the existing test file and lift it to a separate file.
| 1.0 | Refactor unit test templates - Currently, unit tests in templates code are all concentrated in a single file `test_%service.py.j2`. The file has 3K lines and should be refactored.
One idea is to refactor across two dimensions: transport and sync/async (cc @software-dov). It's a big effort, so perhaps a smaller task is to first identify the common boilerplate code in the existing test file and lift it to a separate file.
| priority | refactor unit test templates currently unit tests in templates code are all concentrated in a single file test service py the file has lines and should be refactored one idea is to refactor across two dimensions transport and sync async cc software dov it s a big effort so perhaps a smaller task is to first identify the common boilerplate code in the existing test file and lift it to a separate file | 1 |
168,453 | 20,764,218,919 | IssuesEvent | 2022-03-15 19:02:09 | husnuljahneer/next-js-cartio | https://api.github.com/repos/husnuljahneer/next-js-cartio | opened | next-11.0.1.tgz: 6 vulnerabilities (highest severity is: 7.5) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>next-11.0.1.tgz</b></p></summary>
<p>The React Framework</p>
<p>Library home page: <a href="https://registry.npmjs.org/next/-/next-11.0.1.tgz">https://registry.npmjs.org/next/-/next-11.0.1.tgz</a></p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/husnuljahneer/next-js-cartio/commit/ee921e28068816f78400670e9e3b1987bdbf9514">ee921e28068816f78400670e9e3b1987bdbf9514</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2021-3807](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3807) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | ansi-regex-5.0.0.tgz | Transitive | 11.0.2-canary.0 | ❌ |
| [CVE-2022-23646](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23646) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | next-11.0.1.tgz | Direct | next - 12.1.0 | ❌ |
| [CVE-2021-43803](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43803) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | next-11.0.1.tgz | Direct | 11.1.2-canary.0 | ❌ |
| [CVE-2021-37699](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37699) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | next-11.0.1.tgz | Direct | 11.0.2-canary.0 | ❌ |
| [CVE-2022-0235](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0235) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | node-fetch-2.6.1.tgz | Transitive | 11.1.4 | ❌ |
| [CVE-2021-23566](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23566) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | nanoid-3.1.23.tgz | Transitive | 11.0.2-canary.0 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-3807</summary>
### Vulnerable Library - <b>ansi-regex-5.0.0.tgz</b></p>
<p>Regular expression for matching ANSI escape codes</p>
<p>Library home page: <a href="https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.0.tgz">https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.0.tgz</a></p>
<p>
Dependency Hierarchy:
- next-11.0.1.tgz (Root Library)
- react-dev-overlay-11.0.1.tgz
- strip-ansi-6.0.0.tgz
- :x: **ansi-regex-5.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/husnuljahneer/next-js-cartio/commit/ee921e28068816f78400670e9e3b1987bdbf9514">ee921e28068816f78400670e9e3b1987bdbf9514</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
ansi-regex is vulnerable to Inefficient Regular Expression Complexity
<p>Publish Date: 2021-09-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3807>CVE-2021-3807</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994/">https://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994/</a></p>
<p>Release Date: 2021-09-17</p>
<p>Fix Resolution (ansi-regex): 5.0.1</p>
<p>Direct dependency fix Resolution (next): 11.0.2-canary.0</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-23646</summary>
### Vulnerable Library - <b>next-11.0.1.tgz</b></p>
<p>The React Framework</p>
<p>Library home page: <a href="https://registry.npmjs.org/next/-/next-11.0.1.tgz">https://registry.npmjs.org/next/-/next-11.0.1.tgz</a></p>
<p>
Dependency Hierarchy:
- :x: **next-11.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/husnuljahneer/next-js-cartio/commit/ee921e28068816f78400670e9e3b1987bdbf9514">ee921e28068816f78400670e9e3b1987bdbf9514</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Next.js is a React framework. Starting with version 10.0.0 and prior to version 12.1.0, Next.js is vulnerable to User Interface (UI) Misrepresentation of Critical Information. In order to be affected, the `next.config.js` file must have an `images.domains` array assigned and the image host assigned in `images.domains` must allow user-provided SVG. If the `next.config.js` file has `images.loader` assigned to something other than default, the instance is not affected. Version 12.1.0 contains a patch for this issue. As a workaround, change `next.config.js` to use a different `loader configuration` other than the default.
<p>Publish Date: 2022-02-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23646>CVE-2022-23646</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23646">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23646</a></p>
<p>Release Date: 2022-02-17</p>
<p>Fix Resolution: next - 12.1.0</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-43803</summary>
### Vulnerable Library - <b>next-11.0.1.tgz</b></p>
<p>The React Framework</p>
<p>Library home page: <a href="https://registry.npmjs.org/next/-/next-11.0.1.tgz">https://registry.npmjs.org/next/-/next-11.0.1.tgz</a></p>
<p>
Dependency Hierarchy:
- :x: **next-11.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/husnuljahneer/next-js-cartio/commit/ee921e28068816f78400670e9e3b1987bdbf9514">ee921e28068816f78400670e9e3b1987bdbf9514</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Next.js is a React framework. In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5, Node.js above 15.0.0, and next start or a custom server. Deployments on Vercel are not affected, along with similar environments where invalid requests are filtered before reaching Next.js. Versions 12.0.5 and 11.1.3 contain patches for this issue.
<p>Publish Date: 2021-12-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43803>CVE-2021-43803</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/vercel/next.js/security/advisories/GHSA-25mp-g6fv-mqxx">https://github.com/vercel/next.js/security/advisories/GHSA-25mp-g6fv-mqxx</a></p>
<p>Release Date: 2021-12-10</p>
<p>Fix Resolution: 11.1.2-canary.0</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-37699</summary>
### Vulnerable Library - <b>next-11.0.1.tgz</b></p>
<p>The React Framework</p>
<p>Library home page: <a href="https://registry.npmjs.org/next/-/next-11.0.1.tgz">https://registry.npmjs.org/next/-/next-11.0.1.tgz</a></p>
<p>
Dependency Hierarchy:
- :x: **next-11.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/husnuljahneer/next-js-cartio/commit/ee921e28068816f78400670e9e3b1987bdbf9514">ee921e28068816f78400670e9e3b1987bdbf9514</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Next.js is an open source website development framework to be used with the React library. In affected versions specially encoded paths could be used when pages/_error.js was statically generated allowing an open redirect to occur to an external site. In general, this redirect does not directly harm users although can allow for phishing attacks by redirecting to an attacker's domain from a trusted domain. We recommend everyone to upgrade regardless of whether you can reproduce the issue or not. The issue has been patched in release 11.1.0.
<p>Publish Date: 2021-08-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37699>CVE-2021-37699</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/vercel/next.js/security/advisories/GHSA-vxf5-wxwp-m7g9">https://github.com/vercel/next.js/security/advisories/GHSA-vxf5-wxwp-m7g9</a></p>
<p>Release Date: 2021-08-12</p>
<p>Fix Resolution: 11.0.2-canary.0</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-0235</summary>
### Vulnerable Library - <b>node-fetch-2.6.1.tgz</b></p>
<p>A light-weight module that brings window.fetch to node.js</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.1.tgz">https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.1.tgz</a></p>
<p>
Dependency Hierarchy:
- next-11.0.1.tgz (Root Library)
- :x: **node-fetch-2.6.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/husnuljahneer/next-js-cartio/commit/ee921e28068816f78400670e9e3b1987bdbf9514">ee921e28068816f78400670e9e3b1987bdbf9514</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor
<p>Publish Date: 2022-01-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0235>CVE-2022-0235</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-r683-j2x4-v87g">https://github.com/advisories/GHSA-r683-j2x4-v87g</a></p>
<p>Release Date: 2022-01-16</p>
<p>Fix Resolution (node-fetch): 2.6.7</p>
<p>Direct dependency fix Resolution (next): 11.1.4</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-23566</summary>
### Vulnerable Library - <b>nanoid-3.1.23.tgz</b></p>
<p>A tiny (108 bytes), secure URL-friendly unique string ID generator</p>
<p>Library home page: <a href="https://registry.npmjs.org/nanoid/-/nanoid-3.1.23.tgz">https://registry.npmjs.org/nanoid/-/nanoid-3.1.23.tgz</a></p>
<p>
Dependency Hierarchy:
- next-11.0.1.tgz (Root Library)
- postcss-8.2.13.tgz
- :x: **nanoid-3.1.23.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/husnuljahneer/next-js-cartio/commit/ee921e28068816f78400670e9e3b1987bdbf9514">ee921e28068816f78400670e9e3b1987bdbf9514</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The package nanoid from 3.0.0 and before 3.1.31 are vulnerable to Information Exposure via the valueOf() function which allows to reproduce the last id generated.
<p>Publish Date: 2022-01-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23566>CVE-2021-23566</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<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: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/ai/nanoid/pull/328">https://github.com/ai/nanoid/pull/328</a></p>
<p>Release Date: 2022-01-14</p>
<p>Fix Resolution (nanoid): 3.1.31</p>
<p>Direct dependency fix Resolution (next): 11.0.2-canary.0</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details>
<!-- <REMEDIATE>[{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"next","packageVersion":"11.0.1","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"next:11.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"11.0.2-canary.0","isBinary":true}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2021-3807","vulnerabilityDetails":"ansi-regex is vulnerable to Inefficient Regular Expression Complexity","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3807","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"next","packageVersion":"11.0.1","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"next:11.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"next - 12.1.0","isBinary":true}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2022-23646","vulnerabilityDetails":"Next.js is a React framework. Starting with version 10.0.0 and prior to version 12.1.0, Next.js is vulnerable to User Interface (UI) Misrepresentation of Critical Information. In order to be affected, the `next.config.js` file must have an `images.domains` array assigned and the image host assigned in `images.domains` must allow user-provided SVG. If the `next.config.js` file has `images.loader` assigned to something other than default, the instance is not affected. Version 12.1.0 contains a patch for this issue. As a workaround, change `next.config.js` to use a different `loader configuration` other than the default.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23646","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"next","packageVersion":"11.0.1","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"next:11.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"11.1.2-canary.0","isBinary":true}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2021-43803","vulnerabilityDetails":"Next.js is a React framework. In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5, Node.js above 15.0.0, and next start or a custom server. Deployments on Vercel are not affected, along with similar environments where invalid requests are filtered before reaching Next.js. Versions 12.0.5 and 11.1.3 contain patches for this issue.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43803","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"next","packageVersion":"11.0.1","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"next:11.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"11.0.2-canary.0","isBinary":true}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2021-37699","vulnerabilityDetails":"Next.js is an open source website development framework to be used with the React library. In affected versions specially encoded paths could be used when pages/_error.js was statically generated allowing an open redirect to occur to an external site. In general, this redirect does not directly harm users although can allow for phishing attacks by redirecting to an attacker\u0027s domain from a trusted domain. We recommend everyone to upgrade regardless of whether you can reproduce the issue or not. The issue has been patched in release 11.1.0.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37699","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}},{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"next","packageVersion":"11.0.1","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"next:11.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"11.1.4","isBinary":true}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2022-0235","vulnerabilityDetails":"node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0235","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}},{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"next","packageVersion":"11.0.1","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"next:11.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"11.0.2-canary.0","isBinary":true}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2021-23566","vulnerabilityDetails":"The package nanoid from 3.0.0 and before 3.1.31 are vulnerable to Information Exposure via the valueOf() function which allows to reproduce the last id generated.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23566","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Local","I":"None"},"extraData":{}}]</REMEDIATE> --> | True | next-11.0.1.tgz: 6 vulnerabilities (highest severity is: 7.5) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>next-11.0.1.tgz</b></p></summary>
<p>The React Framework</p>
<p>Library home page: <a href="https://registry.npmjs.org/next/-/next-11.0.1.tgz">https://registry.npmjs.org/next/-/next-11.0.1.tgz</a></p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/husnuljahneer/next-js-cartio/commit/ee921e28068816f78400670e9e3b1987bdbf9514">ee921e28068816f78400670e9e3b1987bdbf9514</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2021-3807](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3807) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | ansi-regex-5.0.0.tgz | Transitive | 11.0.2-canary.0 | ❌ |
| [CVE-2022-23646](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23646) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | next-11.0.1.tgz | Direct | next - 12.1.0 | ❌ |
| [CVE-2021-43803](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43803) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | next-11.0.1.tgz | Direct | 11.1.2-canary.0 | ❌ |
| [CVE-2021-37699](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37699) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | next-11.0.1.tgz | Direct | 11.0.2-canary.0 | ❌ |
| [CVE-2022-0235](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0235) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | node-fetch-2.6.1.tgz | Transitive | 11.1.4 | ❌ |
| [CVE-2021-23566](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23566) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | nanoid-3.1.23.tgz | Transitive | 11.0.2-canary.0 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-3807</summary>
### Vulnerable Library - <b>ansi-regex-5.0.0.tgz</b></p>
<p>Regular expression for matching ANSI escape codes</p>
<p>Library home page: <a href="https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.0.tgz">https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.0.tgz</a></p>
<p>
Dependency Hierarchy:
- next-11.0.1.tgz (Root Library)
- react-dev-overlay-11.0.1.tgz
- strip-ansi-6.0.0.tgz
- :x: **ansi-regex-5.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/husnuljahneer/next-js-cartio/commit/ee921e28068816f78400670e9e3b1987bdbf9514">ee921e28068816f78400670e9e3b1987bdbf9514</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
ansi-regex is vulnerable to Inefficient Regular Expression Complexity
<p>Publish Date: 2021-09-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3807>CVE-2021-3807</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994/">https://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994/</a></p>
<p>Release Date: 2021-09-17</p>
<p>Fix Resolution (ansi-regex): 5.0.1</p>
<p>Direct dependency fix Resolution (next): 11.0.2-canary.0</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-23646</summary>
### Vulnerable Library - <b>next-11.0.1.tgz</b></p>
<p>The React Framework</p>
<p>Library home page: <a href="https://registry.npmjs.org/next/-/next-11.0.1.tgz">https://registry.npmjs.org/next/-/next-11.0.1.tgz</a></p>
<p>
Dependency Hierarchy:
- :x: **next-11.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/husnuljahneer/next-js-cartio/commit/ee921e28068816f78400670e9e3b1987bdbf9514">ee921e28068816f78400670e9e3b1987bdbf9514</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Next.js is a React framework. Starting with version 10.0.0 and prior to version 12.1.0, Next.js is vulnerable to User Interface (UI) Misrepresentation of Critical Information. In order to be affected, the `next.config.js` file must have an `images.domains` array assigned and the image host assigned in `images.domains` must allow user-provided SVG. If the `next.config.js` file has `images.loader` assigned to something other than default, the instance is not affected. Version 12.1.0 contains a patch for this issue. As a workaround, change `next.config.js` to use a different `loader configuration` other than the default.
<p>Publish Date: 2022-02-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23646>CVE-2022-23646</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23646">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23646</a></p>
<p>Release Date: 2022-02-17</p>
<p>Fix Resolution: next - 12.1.0</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-43803</summary>
### Vulnerable Library - <b>next-11.0.1.tgz</b></p>
<p>The React Framework</p>
<p>Library home page: <a href="https://registry.npmjs.org/next/-/next-11.0.1.tgz">https://registry.npmjs.org/next/-/next-11.0.1.tgz</a></p>
<p>
Dependency Hierarchy:
- :x: **next-11.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/husnuljahneer/next-js-cartio/commit/ee921e28068816f78400670e9e3b1987bdbf9514">ee921e28068816f78400670e9e3b1987bdbf9514</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Next.js is a React framework. In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5, Node.js above 15.0.0, and next start or a custom server. Deployments on Vercel are not affected, along with similar environments where invalid requests are filtered before reaching Next.js. Versions 12.0.5 and 11.1.3 contain patches for this issue.
<p>Publish Date: 2021-12-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43803>CVE-2021-43803</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/vercel/next.js/security/advisories/GHSA-25mp-g6fv-mqxx">https://github.com/vercel/next.js/security/advisories/GHSA-25mp-g6fv-mqxx</a></p>
<p>Release Date: 2021-12-10</p>
<p>Fix Resolution: 11.1.2-canary.0</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-37699</summary>
### Vulnerable Library - <b>next-11.0.1.tgz</b></p>
<p>The React Framework</p>
<p>Library home page: <a href="https://registry.npmjs.org/next/-/next-11.0.1.tgz">https://registry.npmjs.org/next/-/next-11.0.1.tgz</a></p>
<p>
Dependency Hierarchy:
- :x: **next-11.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/husnuljahneer/next-js-cartio/commit/ee921e28068816f78400670e9e3b1987bdbf9514">ee921e28068816f78400670e9e3b1987bdbf9514</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Next.js is an open source website development framework to be used with the React library. In affected versions specially encoded paths could be used when pages/_error.js was statically generated allowing an open redirect to occur to an external site. In general, this redirect does not directly harm users although can allow for phishing attacks by redirecting to an attacker's domain from a trusted domain. We recommend everyone to upgrade regardless of whether you can reproduce the issue or not. The issue has been patched in release 11.1.0.
<p>Publish Date: 2021-08-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37699>CVE-2021-37699</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/vercel/next.js/security/advisories/GHSA-vxf5-wxwp-m7g9">https://github.com/vercel/next.js/security/advisories/GHSA-vxf5-wxwp-m7g9</a></p>
<p>Release Date: 2021-08-12</p>
<p>Fix Resolution: 11.0.2-canary.0</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-0235</summary>
### Vulnerable Library - <b>node-fetch-2.6.1.tgz</b></p>
<p>A light-weight module that brings window.fetch to node.js</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.1.tgz">https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.1.tgz</a></p>
<p>
Dependency Hierarchy:
- next-11.0.1.tgz (Root Library)
- :x: **node-fetch-2.6.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/husnuljahneer/next-js-cartio/commit/ee921e28068816f78400670e9e3b1987bdbf9514">ee921e28068816f78400670e9e3b1987bdbf9514</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor
<p>Publish Date: 2022-01-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0235>CVE-2022-0235</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-r683-j2x4-v87g">https://github.com/advisories/GHSA-r683-j2x4-v87g</a></p>
<p>Release Date: 2022-01-16</p>
<p>Fix Resolution (node-fetch): 2.6.7</p>
<p>Direct dependency fix Resolution (next): 11.1.4</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-23566</summary>
### Vulnerable Library - <b>nanoid-3.1.23.tgz</b></p>
<p>A tiny (108 bytes), secure URL-friendly unique string ID generator</p>
<p>Library home page: <a href="https://registry.npmjs.org/nanoid/-/nanoid-3.1.23.tgz">https://registry.npmjs.org/nanoid/-/nanoid-3.1.23.tgz</a></p>
<p>
Dependency Hierarchy:
- next-11.0.1.tgz (Root Library)
- postcss-8.2.13.tgz
- :x: **nanoid-3.1.23.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/husnuljahneer/next-js-cartio/commit/ee921e28068816f78400670e9e3b1987bdbf9514">ee921e28068816f78400670e9e3b1987bdbf9514</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The package nanoid from 3.0.0 and before 3.1.31 are vulnerable to Information Exposure via the valueOf() function which allows to reproduce the last id generated.
<p>Publish Date: 2022-01-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23566>CVE-2021-23566</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<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: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/ai/nanoid/pull/328">https://github.com/ai/nanoid/pull/328</a></p>
<p>Release Date: 2022-01-14</p>
<p>Fix Resolution (nanoid): 3.1.31</p>
<p>Direct dependency fix Resolution (next): 11.0.2-canary.0</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details>
<!-- <REMEDIATE>[{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"next","packageVersion":"11.0.1","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"next:11.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"11.0.2-canary.0","isBinary":true}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2021-3807","vulnerabilityDetails":"ansi-regex is vulnerable to Inefficient Regular Expression Complexity","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3807","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"next","packageVersion":"11.0.1","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"next:11.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"next - 12.1.0","isBinary":true}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2022-23646","vulnerabilityDetails":"Next.js is a React framework. Starting with version 10.0.0 and prior to version 12.1.0, Next.js is vulnerable to User Interface (UI) Misrepresentation of Critical Information. In order to be affected, the `next.config.js` file must have an `images.domains` array assigned and the image host assigned in `images.domains` must allow user-provided SVG. If the `next.config.js` file has `images.loader` assigned to something other than default, the instance is not affected. Version 12.1.0 contains a patch for this issue. As a workaround, change `next.config.js` to use a different `loader configuration` other than the default.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23646","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"next","packageVersion":"11.0.1","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"next:11.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"11.1.2-canary.0","isBinary":true}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2021-43803","vulnerabilityDetails":"Next.js is a React framework. In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5, Node.js above 15.0.0, and next start or a custom server. Deployments on Vercel are not affected, along with similar environments where invalid requests are filtered before reaching Next.js. Versions 12.0.5 and 11.1.3 contain patches for this issue.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43803","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"next","packageVersion":"11.0.1","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"next:11.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"11.0.2-canary.0","isBinary":true}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2021-37699","vulnerabilityDetails":"Next.js is an open source website development framework to be used with the React library. In affected versions specially encoded paths could be used when pages/_error.js was statically generated allowing an open redirect to occur to an external site. In general, this redirect does not directly harm users although can allow for phishing attacks by redirecting to an attacker\u0027s domain from a trusted domain. We recommend everyone to upgrade regardless of whether you can reproduce the issue or not. The issue has been patched in release 11.1.0.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37699","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}},{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"next","packageVersion":"11.0.1","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"next:11.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"11.1.4","isBinary":true}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2022-0235","vulnerabilityDetails":"node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0235","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}},{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"next","packageVersion":"11.0.1","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"next:11.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"11.0.2-canary.0","isBinary":true}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2021-23566","vulnerabilityDetails":"The package nanoid from 3.0.0 and before 3.1.31 are vulnerable to Information Exposure via the valueOf() function which allows to reproduce the last id generated.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23566","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Local","I":"None"},"extraData":{}}]</REMEDIATE> --> | non_priority | next tgz vulnerabilities highest severity is vulnerable library next tgz the react framework library home page a href found in head commit a href vulnerabilities cve severity cvss dependency type fixed in remediation available high ansi regex tgz transitive canary high next tgz direct next high next tgz direct canary medium next tgz direct canary medium node fetch tgz transitive medium nanoid tgz transitive canary details cve vulnerable library ansi regex tgz regular expression for matching ansi escape codes library home page a href dependency hierarchy next tgz root library react dev overlay tgz strip ansi tgz x ansi regex tgz vulnerable library found in head commit a href found in base branch main vulnerability details ansi regex is vulnerable to inefficient regular expression complexity publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution ansi regex direct dependency fix resolution next canary step up your open source security game with whitesource cve vulnerable library next tgz the react framework library home page a href dependency hierarchy x next tgz vulnerable library found in head commit a href found in base branch main vulnerability details next js is a react framework starting with version and prior to version next js is vulnerable to user interface ui misrepresentation of critical information in order to be affected the next config js file must have an images domains array assigned and the image host assigned in images domains must allow user provided svg if the next config js file has images loader assigned to something other than default the instance is not affected version contains a patch for this issue as a workaround change next config js to use a different loader configuration other than the default publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution next step up your open source security game with whitesource cve vulnerable library next tgz the react framework library home page a href dependency hierarchy x next tgz vulnerable library found in head commit a href found in base branch main vulnerability details next js is a react framework in versions of next js prior to or invalid or malformed urls could lead to a server crash in order to be affected by this issue the deployment must use next js versions above and below node js above and next start or a custom server deployments on vercel are not affected along with similar environments where invalid requests are filtered before reaching next js versions and contain patches for this issue 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 canary step up your open source security game with whitesource cve vulnerable library next tgz the react framework library home page a href dependency hierarchy x next tgz vulnerable library found in head commit a href found in base branch main vulnerability details next js is an open source website development framework to be used with the react library in affected versions specially encoded paths could be used when pages error js was statically generated allowing an open redirect to occur to an external site in general this redirect does not directly harm users although can allow for phishing attacks by redirecting to an attacker s domain from a trusted domain we recommend everyone to upgrade regardless of whether you can reproduce the issue or not the issue has been patched in release publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed 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 canary step up your open source security game with whitesource cve vulnerable library node fetch tgz a light weight module that brings window fetch to node js library home page a href dependency hierarchy next tgz root library x node fetch tgz vulnerable library found in head commit a href found in base branch main vulnerability details node fetch is vulnerable to exposure of sensitive information to an unauthorized actor publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed 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 node fetch direct dependency fix resolution next step up your open source security game with whitesource cve vulnerable library nanoid tgz a tiny bytes secure url friendly unique string id generator library home page a href dependency hierarchy next tgz root library postcss tgz x nanoid tgz vulnerable library found in head commit a href found in base branch main vulnerability details the package nanoid from and before are vulnerable to information exposure via the valueof function which allows to reproduce the last id generated 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 none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution nanoid direct dependency fix resolution next canary step up your open source security game with whitesource istransitivedependency false dependencytree next isminimumfixversionavailable true minimumfixversion canary isbinary true basebranches vulnerabilityidentifier cve vulnerabilitydetails ansi regex is vulnerable to inefficient regular expression complexity vulnerabilityurl istransitivedependency false dependencytree next isminimumfixversionavailable true minimumfixversion next isbinary true basebranches vulnerabilityidentifier cve vulnerabilitydetails next js is a react framework starting with version and prior to version next js is vulnerable to user interface ui misrepresentation of critical information in order to be affected the next config js file must have an images domains array assigned and the image host assigned in images domains must allow user provided svg if the next config js file has images loader assigned to something other than default the instance is not affected version contains a patch for this issue as a workaround change next config js to use a different loader configuration other than the default vulnerabilityurl istransitivedependency false dependencytree next isminimumfixversionavailable true minimumfixversion canary isbinary true basebranches vulnerabilityidentifier cve vulnerabilitydetails next js is a react framework in versions of next js prior to or invalid or malformed urls could lead to a server crash in order to be affected by this issue the deployment must use next js versions above and below node js above and next start or a custom server deployments on vercel are not affected along with similar environments where invalid requests are filtered before reaching next js versions and contain patches for this issue vulnerabilityurl istransitivedependency false dependencytree next isminimumfixversionavailable true minimumfixversion canary isbinary true basebranches vulnerabilityidentifier cve vulnerabilitydetails next js is an open source website development framework to be used with the react library in affected versions specially encoded paths could be used when pages error js was statically generated allowing an open redirect to occur to an external site in general this redirect does not directly harm users although can allow for phishing attacks by redirecting to an attacker domain from a trusted domain we recommend everyone to upgrade regardless of whether you can reproduce the issue or not the issue has been patched in release vulnerabilityurl istransitivedependency false dependencytree next isminimumfixversionavailable true minimumfixversion isbinary true basebranches vulnerabilityidentifier cve vulnerabilitydetails node fetch is vulnerable to exposure of sensitive information to an unauthorized actor vulnerabilityurl istransitivedependency false dependencytree next isminimumfixversionavailable true minimumfixversion canary isbinary true basebranches vulnerabilityidentifier cve vulnerabilitydetails the package nanoid from and before are vulnerable to information exposure via the valueof function which allows to reproduce the last id generated vulnerabilityurl | 0 |
210,902 | 16,389,505,355 | IssuesEvent | 2021-05-17 14:30:38 | kubernetes/sig-release | https://api.github.com/repos/kubernetes/sig-release | closed | Cut v1.19.11 release | area/release-eng kind/documentation priority/important-soon sig/release | ## Scheduled to happen: Wed, 2021-05-12
## Release Blocking Issues
<!--
Make a list of anything preventing the release to start
(failing tests, pending image bumps, etc) and link them
to the relevant GitHub issues:
- [ ] Issue 1
- [ ] Issue 2
-->
<!--
Release Process Steps:
======================
- Add/Remove items of the checklist as you see fit
- Post bumps or issues encountered along the way
Hints and pointers to docs for each step of the release process:
Screenshot Testgrid Boards:
Use `krel testgridshot` to automatically create the screenshots
http://bit.ly/relmanagers-handbook#testgrid-screenshots
Stage and Release (mock and nomock):
Use `krel stage` && `krel release` see the handbook for more:
http://bit.ly/relmanagers-handbook#releases-management
Image promotion:
Use `krel promote images` to create a pull request
http://bit.ly/k8s-image-promotion
Notify #release-management on Slack:
Announce the release in a message in the Channel and paste the link
Direct link to slack: https://kubernetes.slack.com/messages/CJH2GBF7Y
Build & publish packages: ← Skip for prereleases
Coordinate with @google-build-admin before starting. Once the
NoMock Release is done and **before sending the announcement**
notify @google-build-admin to start building the packages.
Send notification:
Use `krel announce` using your Sendgrid token
http://bit.ly/relmanagers-handbook#sending-mail
Collect Metrics:
Run krel history --branch release-1.mm --date-from 2021-mm-dd
http://bit.ly/relmanagers-handbook#adding-data-about-the-cloud-build-jobs
Help? Ring @release-managers on slack!
-->
## Release Steps
- [x] Screenshot unhealthy release branch testgrid boards
- Mock Run
- [x] Stage
- [x] Release
- NoMock Run
- [x] Stage
- [x] Image Promotion: https://github.com/kubernetes/k8s.io/pull/2035 https://github.com/kubernetes/k8s.io/pull/2036
- [x] Release
- [x] Build & publish packages (debs & rpms) <!-- REMOVE THIS STEP FOR PRE-RELEASES -->
- [x] Notify [#release-management](https://kubernetes.slack.com/messages/CJH2GBF7Y): https://kubernetes.slack.com/archives/C2C40FMNF/p1620858369386700
- [x] Send notification: https://groups.google.com/u/1/g/kubernetes-dev/c/xy4a7U0z8d4
- [x] Collect metrics and add them to the `Release steps` table below
## Release Tools Version
<!-- Replace with output of `krel version` -->
```
GitVersion: v0.8.0
GitCommit: d04de43201662f7ad4f68771bb34258af8fc7ead
GitTreeState: clean
BuildDate: 2021-05-12T09:12:03Z
GoVersion: go1.16.4
Compiler: gc
Platform: linux/amd64
```
## Release Jobs History
<!-- The following table can be automatically generated using krel --history -->
| Step | Command | Link | Start | Duration | Succeeded? |
| --- | --- | --- | --- | --- | --- |
| `mock stage` | `krel stage --type official --branch release-1.19 --build-version v1.19.11-rc.0.45+0657e7d45a5c2d` | https://console.cloud.google.com/cloud-build/builds/d30bbe93-7c20-49d2-99af-c572abf0f4c0?project=648026197307 | 2021-05-12T09:27:59.389416692Z | 00:01:40 | No |
| `mock stage` | `krel stage --type official --branch release-1.19 --build-version v1.19.11-rc.0.45+0657e7d45a5c2d` | https://console.cloud.google.com/cloud-build/builds/f2c2ad73-9d47-48cd-8f8f-09413ab65dfd?project=648026197307 | 2021-05-12T10:43:57.049145675Z | 01:15:55 | Yes |
| `mock release` | `krel release --type official --branch release-1.19 --build-version v1.19.11-rc.0.45+0657e7d45a5c2d` | https://console.cloud.google.com/cloud-build/builds/ece5b689-7d38-46df-bafb-008afd7059dc?project=648026197307 | 2021-05-12T12:03:45.225175642Z | 00:05:55 | Yes |
| `stage` | `krel stage --type official --branch release-1.19 --build-version v1.19.11-rc.0.45+0657e7d45a5c2d --nomock` | https://console.cloud.google.com/cloud-build/builds/9fe50f6c-05ae-4b7d-8d06-e2fa6ada3b52?project=648026197307 | 2021-05-12T12:13:14.764027576Z | 01:13:47 | Yes |
| `release` | `krel release --type official --branch release-1.19 --build-version v1.19.11-rc.0.45+0657e7d45a5c2d --nomock` | https://console.cloud.google.com/cloud-build/builds/0b1511c9-31a3-40cd-9fec-2fff894eaabb?project=648026197307 | 2021-05-12T20:26:46.010396950Z | 00:05:31 | Yes |
## Action Items
<!--
During the release, you may find a few things that require updates
(process changes, documentation updates, fixes to release tooling).
Please list them here.
It will be your responsibility to open issues/PRs to resolve these
issues/improvements. Keep this issue open until these action items
are complete.
- [ ] Item 1
- [ ] Item 2
- [ ] Item 3
-->
## Open Questions
<!--
During the release, you may have a few questions that you can't
answer yourself or may require group discussion.
Please list them here.
Follow up with Branch Managers/Patch Release Team/Release Engineering
subproject owners to get these questions answered.
- [ ] Item 1
- [ ] Item 2
- [ ] Item 3
-->
/milestone v1.19
/assign @cpanato @puerco
/cc @kubernetes/release-managers
/priority important-soon
/kind documentation
| 1.0 | Cut v1.19.11 release - ## Scheduled to happen: Wed, 2021-05-12
## Release Blocking Issues
<!--
Make a list of anything preventing the release to start
(failing tests, pending image bumps, etc) and link them
to the relevant GitHub issues:
- [ ] Issue 1
- [ ] Issue 2
-->
<!--
Release Process Steps:
======================
- Add/Remove items of the checklist as you see fit
- Post bumps or issues encountered along the way
Hints and pointers to docs for each step of the release process:
Screenshot Testgrid Boards:
Use `krel testgridshot` to automatically create the screenshots
http://bit.ly/relmanagers-handbook#testgrid-screenshots
Stage and Release (mock and nomock):
Use `krel stage` && `krel release` see the handbook for more:
http://bit.ly/relmanagers-handbook#releases-management
Image promotion:
Use `krel promote images` to create a pull request
http://bit.ly/k8s-image-promotion
Notify #release-management on Slack:
Announce the release in a message in the Channel and paste the link
Direct link to slack: https://kubernetes.slack.com/messages/CJH2GBF7Y
Build & publish packages: ← Skip for prereleases
Coordinate with @google-build-admin before starting. Once the
NoMock Release is done and **before sending the announcement**
notify @google-build-admin to start building the packages.
Send notification:
Use `krel announce` using your Sendgrid token
http://bit.ly/relmanagers-handbook#sending-mail
Collect Metrics:
Run krel history --branch release-1.mm --date-from 2021-mm-dd
http://bit.ly/relmanagers-handbook#adding-data-about-the-cloud-build-jobs
Help? Ring @release-managers on slack!
-->
## Release Steps
- [x] Screenshot unhealthy release branch testgrid boards
- Mock Run
- [x] Stage
- [x] Release
- NoMock Run
- [x] Stage
- [x] Image Promotion: https://github.com/kubernetes/k8s.io/pull/2035 https://github.com/kubernetes/k8s.io/pull/2036
- [x] Release
- [x] Build & publish packages (debs & rpms) <!-- REMOVE THIS STEP FOR PRE-RELEASES -->
- [x] Notify [#release-management](https://kubernetes.slack.com/messages/CJH2GBF7Y): https://kubernetes.slack.com/archives/C2C40FMNF/p1620858369386700
- [x] Send notification: https://groups.google.com/u/1/g/kubernetes-dev/c/xy4a7U0z8d4
- [x] Collect metrics and add them to the `Release steps` table below
## Release Tools Version
<!-- Replace with output of `krel version` -->
```
GitVersion: v0.8.0
GitCommit: d04de43201662f7ad4f68771bb34258af8fc7ead
GitTreeState: clean
BuildDate: 2021-05-12T09:12:03Z
GoVersion: go1.16.4
Compiler: gc
Platform: linux/amd64
```
## Release Jobs History
<!-- The following table can be automatically generated using krel --history -->
| Step | Command | Link | Start | Duration | Succeeded? |
| --- | --- | --- | --- | --- | --- |
| `mock stage` | `krel stage --type official --branch release-1.19 --build-version v1.19.11-rc.0.45+0657e7d45a5c2d` | https://console.cloud.google.com/cloud-build/builds/d30bbe93-7c20-49d2-99af-c572abf0f4c0?project=648026197307 | 2021-05-12T09:27:59.389416692Z | 00:01:40 | No |
| `mock stage` | `krel stage --type official --branch release-1.19 --build-version v1.19.11-rc.0.45+0657e7d45a5c2d` | https://console.cloud.google.com/cloud-build/builds/f2c2ad73-9d47-48cd-8f8f-09413ab65dfd?project=648026197307 | 2021-05-12T10:43:57.049145675Z | 01:15:55 | Yes |
| `mock release` | `krel release --type official --branch release-1.19 --build-version v1.19.11-rc.0.45+0657e7d45a5c2d` | https://console.cloud.google.com/cloud-build/builds/ece5b689-7d38-46df-bafb-008afd7059dc?project=648026197307 | 2021-05-12T12:03:45.225175642Z | 00:05:55 | Yes |
| `stage` | `krel stage --type official --branch release-1.19 --build-version v1.19.11-rc.0.45+0657e7d45a5c2d --nomock` | https://console.cloud.google.com/cloud-build/builds/9fe50f6c-05ae-4b7d-8d06-e2fa6ada3b52?project=648026197307 | 2021-05-12T12:13:14.764027576Z | 01:13:47 | Yes |
| `release` | `krel release --type official --branch release-1.19 --build-version v1.19.11-rc.0.45+0657e7d45a5c2d --nomock` | https://console.cloud.google.com/cloud-build/builds/0b1511c9-31a3-40cd-9fec-2fff894eaabb?project=648026197307 | 2021-05-12T20:26:46.010396950Z | 00:05:31 | Yes |
## Action Items
<!--
During the release, you may find a few things that require updates
(process changes, documentation updates, fixes to release tooling).
Please list them here.
It will be your responsibility to open issues/PRs to resolve these
issues/improvements. Keep this issue open until these action items
are complete.
- [ ] Item 1
- [ ] Item 2
- [ ] Item 3
-->
## Open Questions
<!--
During the release, you may have a few questions that you can't
answer yourself or may require group discussion.
Please list them here.
Follow up with Branch Managers/Patch Release Team/Release Engineering
subproject owners to get these questions answered.
- [ ] Item 1
- [ ] Item 2
- [ ] Item 3
-->
/milestone v1.19
/assign @cpanato @puerco
/cc @kubernetes/release-managers
/priority important-soon
/kind documentation
| non_priority | cut release scheduled to happen wed release blocking issues make a list of anything preventing the release to start failing tests pending image bumps etc and link them to the relevant github issues issue issue release process steps add remove items of the checklist as you see fit post bumps or issues encountered along the way hints and pointers to docs for each step of the release process screenshot testgrid boards use krel testgridshot to automatically create the screenshots stage and release mock and nomock use krel stage krel release see the handbook for more image promotion use krel promote images to create a pull request notify release management on slack announce the release in a message in the channel and paste the link direct link to slack build publish packages ← skip for prereleases coordinate with google build admin before starting once the nomock release is done and before sending the announcement notify google build admin to start building the packages send notification use krel announce using your sendgrid token collect metrics run krel history branch release mm date from mm dd help ring release managers on slack release steps screenshot unhealthy release branch testgrid boards mock run stage release nomock run stage image promotion release build publish packages debs rpms notify send notification collect metrics and add them to the release steps table below release tools version gitversion gitcommit gittreestate clean builddate goversion compiler gc platform linux release jobs history step command link start duration succeeded mock stage krel stage type official branch release build version rc no mock stage krel stage type official branch release build version rc yes mock release krel release type official branch release build version rc yes stage krel stage type official branch release build version rc nomock yes release krel release type official branch release build version rc nomock yes action items during the release you may find a few things that require updates process changes documentation updates fixes to release tooling please list them here it will be your responsibility to open issues prs to resolve these issues improvements keep this issue open until these action items are complete item item item open questions during the release you may have a few questions that you can t answer yourself or may require group discussion please list them here follow up with branch managers patch release team release engineering subproject owners to get these questions answered item item item milestone assign cpanato puerco cc kubernetes release managers priority important soon kind documentation | 0 |
613,997 | 19,103,217,493 | IssuesEvent | 2021-11-30 02:17:18 | hadialaddin/crypto-genie | https://api.github.com/repos/hadialaddin/crypto-genie | closed | Enforce Take Profits feature | enhancement high-priority | Set Profit ratios at which to close partial position size (ratio). Bot should automatically calculate the quantity in real-time based on up-to-date position size, and auto adjust TP size and price levels should position change its size or entry price (so should react to manual take profit or loss).
Allow Tolerance which is the ratio of how far the level is considered valid to place a TP at (if too close, skip to move to the next level, to avoid repetition if price is volatile). | 1.0 | Enforce Take Profits feature - Set Profit ratios at which to close partial position size (ratio). Bot should automatically calculate the quantity in real-time based on up-to-date position size, and auto adjust TP size and price levels should position change its size or entry price (so should react to manual take profit or loss).
Allow Tolerance which is the ratio of how far the level is considered valid to place a TP at (if too close, skip to move to the next level, to avoid repetition if price is volatile). | priority | enforce take profits feature set profit ratios at which to close partial position size ratio bot should automatically calculate the quantity in real time based on up to date position size and auto adjust tp size and price levels should position change its size or entry price so should react to manual take profit or loss allow tolerance which is the ratio of how far the level is considered valid to place a tp at if too close skip to move to the next level to avoid repetition if price is volatile | 1 |
262,167 | 8,251,778,307 | IssuesEvent | 2018-09-12 08:52:48 | orbs-network/orbs-network-go | https://api.github.com/repos/orbs-network/orbs-network-go | closed | System gets choked up after a "long" time of running | bug help wanted high priority | System gets stuck after a while when running full steam on idle
### To see it in E2E:
Add the line
```
time.Sleep(10 * time.Second)
```
right before e2e is sending the 3 transactions.
The system in e2e should close an empty block every ~ 1 second (config setting `ConsensusContextMinimalBlockDelay`).
During the sleep, the system closes only 5 empty blocks and then stops closing blocks.. consensus stuck somehow.
| 1.0 | System gets choked up after a "long" time of running - System gets stuck after a while when running full steam on idle
### To see it in E2E:
Add the line
```
time.Sleep(10 * time.Second)
```
right before e2e is sending the 3 transactions.
The system in e2e should close an empty block every ~ 1 second (config setting `ConsensusContextMinimalBlockDelay`).
During the sleep, the system closes only 5 empty blocks and then stops closing blocks.. consensus stuck somehow.
| priority | system gets choked up after a long time of running system gets stuck after a while when running full steam on idle to see it in add the line time sleep time second right before is sending the transactions the system in should close an empty block every second config setting consensuscontextminimalblockdelay during the sleep the system closes only empty blocks and then stops closing blocks consensus stuck somehow | 1 |
421,394 | 12,256,550,090 | IssuesEvent | 2020-05-06 12:17:47 | HabitRPG/habitica | https://api.github.com/repos/HabitRPG/habitica | closed | Reset should unassign Stat Points (previously known as Attribute Points) | good first issue priority: medium section: Settings status: issue: in progress | When you use [Reset Account](https://habitica.fandom.com/wiki/Settings#Reset_Account) (from User Icon > Settings > "Danger Zone" section), it correctly sets your Level to 1 but it does not reset your Stat Points. It should reset them as described below.
Ideally we'd fix this with the generic function described at https://github.com/HabitRPG/habitica/issues/6482 but that requires a large body of work and no one has taken it up yet. Doing a fix for Reset alone will be much simpler and will bring immediate benefits (e.g., for new players who were experimenting with Habitica and want a fresh start).
I'm marking this as "good first issue" although it's larger than we'd normally use that label for. The information below should help a new contributor though and you can comment here if you have any questions.
Stat Points are stored in a user's account like this:
```
{
"stats": {
"lvl": 14,
"points": 2,
"str": 3,
"con": 3,
"int": 3,
"per": 3
}
}
```
That's a user at level 14. They have 3 points allocated to each of the Stats (STRength, CONstitution, INTelligence, PERception), and they have 2 points unassigned.
After using Reset currently, the player's account will look like this, which is wrong:
```
{
"stats": {
"lvl": 1,
"points": 2,
"str": 3,
"con": 3,
"int": 3,
"per": 3
}
}
```
It **should** look like this:
```
{
"stats": {
"lvl": 1,
"points": 1,
"str": 0,
"con": 0,
"int": 0,
"per": 0
}
}
```
I.e., `stats.points` should the same as `stats.lvl` (1, the user's level) and the individual Stats should be set to 0.
This is where Reset sets the level to 1 so it would be a good place to reset the Stat Points:
https://github.com/HabitRPG/habitica/blob/d03e5e93b09f5a16598ed63b911c074d28c62368/website/common/script/ops/reset.js#L4-L9
We would want tests for this too. Below is the test for how Reset changes the level to 1. Tests for setting `stats.points` to 1 and the individual stats to 0 should be in the same file and can use similar code.
https://github.com/HabitRPG/habitica/blob/d03e5e93b09f5a16598ed63b911c074d28c62368/test/common/ops/reset.js#L47-L53
| 1.0 | Reset should unassign Stat Points (previously known as Attribute Points) - When you use [Reset Account](https://habitica.fandom.com/wiki/Settings#Reset_Account) (from User Icon > Settings > "Danger Zone" section), it correctly sets your Level to 1 but it does not reset your Stat Points. It should reset them as described below.
Ideally we'd fix this with the generic function described at https://github.com/HabitRPG/habitica/issues/6482 but that requires a large body of work and no one has taken it up yet. Doing a fix for Reset alone will be much simpler and will bring immediate benefits (e.g., for new players who were experimenting with Habitica and want a fresh start).
I'm marking this as "good first issue" although it's larger than we'd normally use that label for. The information below should help a new contributor though and you can comment here if you have any questions.
Stat Points are stored in a user's account like this:
```
{
"stats": {
"lvl": 14,
"points": 2,
"str": 3,
"con": 3,
"int": 3,
"per": 3
}
}
```
That's a user at level 14. They have 3 points allocated to each of the Stats (STRength, CONstitution, INTelligence, PERception), and they have 2 points unassigned.
After using Reset currently, the player's account will look like this, which is wrong:
```
{
"stats": {
"lvl": 1,
"points": 2,
"str": 3,
"con": 3,
"int": 3,
"per": 3
}
}
```
It **should** look like this:
```
{
"stats": {
"lvl": 1,
"points": 1,
"str": 0,
"con": 0,
"int": 0,
"per": 0
}
}
```
I.e., `stats.points` should the same as `stats.lvl` (1, the user's level) and the individual Stats should be set to 0.
This is where Reset sets the level to 1 so it would be a good place to reset the Stat Points:
https://github.com/HabitRPG/habitica/blob/d03e5e93b09f5a16598ed63b911c074d28c62368/website/common/script/ops/reset.js#L4-L9
We would want tests for this too. Below is the test for how Reset changes the level to 1. Tests for setting `stats.points` to 1 and the individual stats to 0 should be in the same file and can use similar code.
https://github.com/HabitRPG/habitica/blob/d03e5e93b09f5a16598ed63b911c074d28c62368/test/common/ops/reset.js#L47-L53
| priority | reset should unassign stat points previously known as attribute points when you use from user icon settings danger zone section it correctly sets your level to but it does not reset your stat points it should reset them as described below ideally we d fix this with the generic function described at but that requires a large body of work and no one has taken it up yet doing a fix for reset alone will be much simpler and will bring immediate benefits e g for new players who were experimenting with habitica and want a fresh start i m marking this as good first issue although it s larger than we d normally use that label for the information below should help a new contributor though and you can comment here if you have any questions stat points are stored in a user s account like this stats lvl points str con int per that s a user at level they have points allocated to each of the stats strength constitution intelligence perception and they have points unassigned after using reset currently the player s account will look like this which is wrong stats lvl points str con int per it should look like this stats lvl points str con int per i e stats points should the same as stats lvl the user s level and the individual stats should be set to this is where reset sets the level to so it would be a good place to reset the stat points we would want tests for this too below is the test for how reset changes the level to tests for setting stats points to and the individual stats to should be in the same file and can use similar code | 1 |
4,576 | 3,872,817,592 | IssuesEvent | 2016-04-11 15:01:50 | lionheart/openradar-mirror | https://api.github.com/repos/lionheart/openradar-mirror | opened | 22497026: SFSafariViewController should tint progress bar | classification:ui/usability reproducible:always status:open | #### Description
SFSafariViewController nicely tints the button colors if a tint color is configured.. However, the progress bar is always blue. This doesn't fit well.
-
Product Version: 9.0 beta 5
Created: 2015-08-31T08:38:49.673270
Originated: 2015-08-31T11:38:00
Open Radar Link: http://www.openradar.me/22497026 | True | 22497026: SFSafariViewController should tint progress bar - #### Description
SFSafariViewController nicely tints the button colors if a tint color is configured.. However, the progress bar is always blue. This doesn't fit well.
-
Product Version: 9.0 beta 5
Created: 2015-08-31T08:38:49.673270
Originated: 2015-08-31T11:38:00
Open Radar Link: http://www.openradar.me/22497026 | non_priority | sfsafariviewcontroller should tint progress bar description sfsafariviewcontroller nicely tints the button colors if a tint color is configured however the progress bar is always blue this doesn t fit well product version beta created originated open radar link | 0 |
573,097 | 17,023,589,158 | IssuesEvent | 2021-07-03 02:48:25 | tomhughes/trac-tickets | https://api.github.com/repos/tomhughes/trac-tickets | closed | Prevent duplicate posting on diary comments | Component: website Priority: trivial Resolution: wontfix Type: enhancement | **[Submitted to the original trac issue database at 3.24pm, Wednesday, 12th May 2010]**
Loads of people post duplicate diary comments. I'm sure there will be a funky thing in rails to either prevent duplicate submissions, or we should just prevent people from posting the same text anyway | 1.0 | Prevent duplicate posting on diary comments - **[Submitted to the original trac issue database at 3.24pm, Wednesday, 12th May 2010]**
Loads of people post duplicate diary comments. I'm sure there will be a funky thing in rails to either prevent duplicate submissions, or we should just prevent people from posting the same text anyway | priority | prevent duplicate posting on diary comments loads of people post duplicate diary comments i m sure there will be a funky thing in rails to either prevent duplicate submissions or we should just prevent people from posting the same text anyway | 1 |
596,007 | 18,094,129,014 | IssuesEvent | 2021-09-22 07:05:39 | gardener/gardener | https://api.github.com/repos/gardener/gardener | closed | `botanist.WaitUntilTunnelConnectionExists` step is failing right away on transient errors | kind/bug area/quality priority/3 | **How to categorize this issue?**
<!--
Please select area, kind, and priority for this issue. This helps the community categorizing it.
Replace below TODOs or exchange the existing identifiers with those that fit best in your opinion.
If multiple identifiers make sense you can also state the commands multiple times, e.g.
/area control-plane
/area auto-scaling
...
"/area" identifiers: audit-logging|auto-scaling|backup|certification|control-plane-migration|control-plane|cost|delivery|dev-productivity|disaster-recovery|documentation|high-availability|logging|metering|monitoring|networking|open-source|ops-productivity|os|performance|quality|robustness|scalability|security|storage|testing|usability|user-management
"/kind" identifiers: api-change|bug|cleanup|discussion|enhancement|epic|impediment|poc|post-mortem|question|regression|task|technical-debt|test
"/priority" identifiers: 1|2|3|4|5 (ordered from greatest to least)
-->
/area quality
/kind bug
/priority 3
**What happened**:
We observe high amount of transient errors on Shoot creation that usually self-heal after several minutes. Few examples:
```
task "Waiting until the Kubernetes API server can connect to the Shoot workers" failed: could not forward to vpn-shoot pod: port forward connection could not be established within five seconds
-> Events:
* service-controller reported 3m48s ago (x5 over 5m3s): There are no available nodes for LoadBalancer
* service-controller reported 3m48s ago (x5 over 5m3s): Error syncing load balancer: failed to ensure load balancer: there are no available nodes for LoadBalancer service kube-system/vpn-shoot
```
```
task "Waiting until the Kubernetes API server can connect to the Shoot workers" failed: no running vpn-shoot pod found yet in the shoot cluster
-> Events:
* service-controller reported 3m10s ago: There are no available nodes for LoadBalancer
```
It seems that before https://github.com/gardener/gardener/pull/4183, we were retrying with timeout 15min until the tunnel connection is established.
https://github.com/gardener/gardener/blob/0c0a17e8b091bfac3c90ccd9d52055a7cb10e285/pkg/operation/botanist/waiter.go#L155-L166
After https://github.com/gardener/gardener/pull/4183, the func looks like
https://github.com/gardener/gardener/blob/694a812212c962073ca732fb056953e1258b7cb0/pkg/operation/botanist/waiter.go#L53-L95
Currently if the first check for a tunnel connection fails, the func will check for vpn-shoot LoadBalancer events of type Warning, and if there are any, it will return err (fail the step).
**What you expected to happen**:
gardenlet to retry the check for a tunnel connection for 15min, and return an error only after the timeout is exceeded.
**How to reproduce it (as minimally and precisely as possible)**:
See above.
**Environment**:
- Gardener version: v1.31.3
- Kubernetes version (use `kubectl version`):
- Cloud provider or hardware configuration:
- Others:
| 1.0 | `botanist.WaitUntilTunnelConnectionExists` step is failing right away on transient errors - **How to categorize this issue?**
<!--
Please select area, kind, and priority for this issue. This helps the community categorizing it.
Replace below TODOs or exchange the existing identifiers with those that fit best in your opinion.
If multiple identifiers make sense you can also state the commands multiple times, e.g.
/area control-plane
/area auto-scaling
...
"/area" identifiers: audit-logging|auto-scaling|backup|certification|control-plane-migration|control-plane|cost|delivery|dev-productivity|disaster-recovery|documentation|high-availability|logging|metering|monitoring|networking|open-source|ops-productivity|os|performance|quality|robustness|scalability|security|storage|testing|usability|user-management
"/kind" identifiers: api-change|bug|cleanup|discussion|enhancement|epic|impediment|poc|post-mortem|question|regression|task|technical-debt|test
"/priority" identifiers: 1|2|3|4|5 (ordered from greatest to least)
-->
/area quality
/kind bug
/priority 3
**What happened**:
We observe high amount of transient errors on Shoot creation that usually self-heal after several minutes. Few examples:
```
task "Waiting until the Kubernetes API server can connect to the Shoot workers" failed: could not forward to vpn-shoot pod: port forward connection could not be established within five seconds
-> Events:
* service-controller reported 3m48s ago (x5 over 5m3s): There are no available nodes for LoadBalancer
* service-controller reported 3m48s ago (x5 over 5m3s): Error syncing load balancer: failed to ensure load balancer: there are no available nodes for LoadBalancer service kube-system/vpn-shoot
```
```
task "Waiting until the Kubernetes API server can connect to the Shoot workers" failed: no running vpn-shoot pod found yet in the shoot cluster
-> Events:
* service-controller reported 3m10s ago: There are no available nodes for LoadBalancer
```
It seems that before https://github.com/gardener/gardener/pull/4183, we were retrying with timeout 15min until the tunnel connection is established.
https://github.com/gardener/gardener/blob/0c0a17e8b091bfac3c90ccd9d52055a7cb10e285/pkg/operation/botanist/waiter.go#L155-L166
After https://github.com/gardener/gardener/pull/4183, the func looks like
https://github.com/gardener/gardener/blob/694a812212c962073ca732fb056953e1258b7cb0/pkg/operation/botanist/waiter.go#L53-L95
Currently if the first check for a tunnel connection fails, the func will check for vpn-shoot LoadBalancer events of type Warning, and if there are any, it will return err (fail the step).
**What you expected to happen**:
gardenlet to retry the check for a tunnel connection for 15min, and return an error only after the timeout is exceeded.
**How to reproduce it (as minimally and precisely as possible)**:
See above.
**Environment**:
- Gardener version: v1.31.3
- Kubernetes version (use `kubectl version`):
- Cloud provider or hardware configuration:
- Others:
| priority | botanist waituntiltunnelconnectionexists step is failing right away on transient errors how to categorize this issue please select area kind and priority for this issue this helps the community categorizing it replace below todos or exchange the existing identifiers with those that fit best in your opinion if multiple identifiers make sense you can also state the commands multiple times e g area control plane area auto scaling area identifiers audit logging auto scaling backup certification control plane migration control plane cost delivery dev productivity disaster recovery documentation high availability logging metering monitoring networking open source ops productivity os performance quality robustness scalability security storage testing usability user management kind identifiers api change bug cleanup discussion enhancement epic impediment poc post mortem question regression task technical debt test priority identifiers ordered from greatest to least area quality kind bug priority what happened we observe high amount of transient errors on shoot creation that usually self heal after several minutes few examples task waiting until the kubernetes api server can connect to the shoot workers failed could not forward to vpn shoot pod port forward connection could not be established within five seconds events service controller reported ago over there are no available nodes for loadbalancer service controller reported ago over error syncing load balancer failed to ensure load balancer there are no available nodes for loadbalancer service kube system vpn shoot task waiting until the kubernetes api server can connect to the shoot workers failed no running vpn shoot pod found yet in the shoot cluster events service controller reported ago there are no available nodes for loadbalancer it seems that before we were retrying with timeout until the tunnel connection is established after the func looks like currently if the first check for a tunnel connection fails the func will check for vpn shoot loadbalancer events of type warning and if there are any it will return err fail the step what you expected to happen gardenlet to retry the check for a tunnel connection for and return an error only after the timeout is exceeded how to reproduce it as minimally and precisely as possible see above environment gardener version kubernetes version use kubectl version cloud provider or hardware configuration others | 1 |
85,128 | 3,686,858,991 | IssuesEvent | 2016-02-25 04:07:03 | SoylentNews/rehash | https://api.github.com/repos/SoylentNews/rehash | closed | Poll page title incorrect | Bug: Non-Critical Priority: Normal | _From @cc158981bce50e050022f4ab8f113ece on July 27, 2014 22:49_
Some polls have the wrong <title>. At first I thought it was the most recent poll's title or the last visited poll's title but it appears to be random. Some kind of caching problem?
To recreate visit http://dev.soylentnews.org/pollBooth.pl, click on a poll. The page <title>s seem to be random. If you click [Results] you can also get an incorrect title.
Refreshing (Ctrl-F5) the page can lead to a different title. Visiting other polls can show the same title or a different title.
_Copied from original issue: SoylentNews/slashcode#261_ | 1.0 | Poll page title incorrect - _From @cc158981bce50e050022f4ab8f113ece on July 27, 2014 22:49_
Some polls have the wrong <title>. At first I thought it was the most recent poll's title or the last visited poll's title but it appears to be random. Some kind of caching problem?
To recreate visit http://dev.soylentnews.org/pollBooth.pl, click on a poll. The page <title>s seem to be random. If you click [Results] you can also get an incorrect title.
Refreshing (Ctrl-F5) the page can lead to a different title. Visiting other polls can show the same title or a different title.
_Copied from original issue: SoylentNews/slashcode#261_ | priority | poll page title incorrect from on july some polls have the wrong lt title gt at first i thought it was the most recent poll s title or the last visited poll s title but it appears to be random some kind of caching problem to recreate visit click on a poll the page lt title gt s seem to be random if you click you can also get an incorrect title refreshing ctrl the page can lead to a different title visiting other polls can show the same title or a different title copied from original issue soylentnews slashcode | 1 |
19,996 | 26,470,032,388 | IssuesEvent | 2023-01-17 06:10:33 | nion-software/nionswift | https://api.github.com/repos/nion-software/nionswift | opened | Processing data should also retain some graphic properties | type - enhancement f - user-interface f - processing | BPS 2021-06-17: I think things would go smoother if the display properties (log display, color map) are maintained on a new data item that is generated from applying a function.
CM note: I'm not sure this can happen in all cases, but like metadata, there should be a defined set of processing operations where it does apply.
- #915 | 1.0 | Processing data should also retain some graphic properties - BPS 2021-06-17: I think things would go smoother if the display properties (log display, color map) are maintained on a new data item that is generated from applying a function.
CM note: I'm not sure this can happen in all cases, but like metadata, there should be a defined set of processing operations where it does apply.
- #915 | non_priority | processing data should also retain some graphic properties bps i think things would go smoother if the display properties log display color map are maintained on a new data item that is generated from applying a function cm note i m not sure this can happen in all cases but like metadata there should be a defined set of processing operations where it does apply | 0 |
234,399 | 19,178,636,123 | IssuesEvent | 2021-12-04 02:16:40 | itzg/docker-minecraft-server | https://api.github.com/repos/itzg/docker-minecraft-server | closed | multiarch-latest fails to run | status/ready to test status/stale | Hi,
2021.20.0-multiarch-latest is running fine, after update the server does not run anymore:
`Downloading minecraft_server.[0.003s][error][cds]_Unable_to_map_CDS_archive_--_os::vm_allocation_granularity()_expected:_4096_actual:_65536`
Any ideas what is going on?
Best regards,
hansnull | 1.0 | multiarch-latest fails to run - Hi,
2021.20.0-multiarch-latest is running fine, after update the server does not run anymore:
`Downloading minecraft_server.[0.003s][error][cds]_Unable_to_map_CDS_archive_--_os::vm_allocation_granularity()_expected:_4096_actual:_65536`
Any ideas what is going on?
Best regards,
hansnull | non_priority | multiarch latest fails to run hi multiarch latest is running fine after update the server does not run anymore downloading minecraft server unable to map cds archive os vm allocation granularity expected actual any ideas what is going on best regards hansnull | 0 |
173,739 | 14,435,986,301 | IssuesEvent | 2020-12-07 09:30:59 | kinvolk/lokomotive | https://api.github.com/repos/kinvolk/lokomotive | opened | Linkerd and Istio PSP docs | area/components area/security kind/documentation | Apps that are meshed by either of the above service mesh components need elevated permissions. So document that if a user is meshing their application they should also add following PSP config:
```yaml
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
name: appname
spec:
allowPrivilegeEscalation: false
fsGroup:
ranges:
- max: 65535
min: 1337
rule: MustRunAs
readOnlyRootFilesystem: false
allowedCapabilities:
- NET_ADMIN
- NET_RAW
- NET_BIND_SERVICE
requiredDropCapabilities:
- ALL
runAsUser:
rule: RunAsAny
seLinux:
rule: RunAsAny
supplementalGroups:
ranges:
- max: 65535
min: 10001
rule: MustRunAs
volumes:
- configMap
- emptyDir
- projected
- secret
- downwardAPI
- persistentVolumeClaim
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
name: appname-psp
namespace: appns
rules:
- apiGroups: ['policy','extensions']
resources: ['podsecuritypolicies']
verbs: ['use']
resourceNames: ['appname']
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: appname-psp
namespace: appns
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: appname-psp
subjects:
- kind: ServiceAccount
name: webapp
namespace: appns
``` | 1.0 | Linkerd and Istio PSP docs - Apps that are meshed by either of the above service mesh components need elevated permissions. So document that if a user is meshing their application they should also add following PSP config:
```yaml
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
name: appname
spec:
allowPrivilegeEscalation: false
fsGroup:
ranges:
- max: 65535
min: 1337
rule: MustRunAs
readOnlyRootFilesystem: false
allowedCapabilities:
- NET_ADMIN
- NET_RAW
- NET_BIND_SERVICE
requiredDropCapabilities:
- ALL
runAsUser:
rule: RunAsAny
seLinux:
rule: RunAsAny
supplementalGroups:
ranges:
- max: 65535
min: 10001
rule: MustRunAs
volumes:
- configMap
- emptyDir
- projected
- secret
- downwardAPI
- persistentVolumeClaim
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
name: appname-psp
namespace: appns
rules:
- apiGroups: ['policy','extensions']
resources: ['podsecuritypolicies']
verbs: ['use']
resourceNames: ['appname']
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: appname-psp
namespace: appns
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: appname-psp
subjects:
- kind: ServiceAccount
name: webapp
namespace: appns
``` | non_priority | linkerd and istio psp docs apps that are meshed by either of the above service mesh components need elevated permissions so document that if a user is meshing their application they should also add following psp config yaml apiversion policy kind podsecuritypolicy metadata name appname spec allowprivilegeescalation false fsgroup ranges max min rule mustrunas readonlyrootfilesystem false allowedcapabilities net admin net raw net bind service requireddropcapabilities all runasuser rule runasany selinux rule runasany supplementalgroups ranges max min rule mustrunas volumes configmap emptydir projected secret downwardapi persistentvolumeclaim apiversion rbac authorization io kind role metadata name appname psp namespace appns rules apigroups resources verbs resourcenames apiversion rbac authorization io kind rolebinding metadata name appname psp namespace appns roleref apigroup rbac authorization io kind role name appname psp subjects kind serviceaccount name webapp namespace appns | 0 |
772,689 | 27,132,166,714 | IssuesEvent | 2023-02-16 10:32:51 | oceanprotocol/ocean.py | https://api.github.com/repos/oceanprotocol/ocean.py | closed | Document bundled asset creation + pricing schema in readmes | Type: Enhancement Priority: Mid | As part of #1166 we introduced the option of creating assets + pricing schemas. I bundled NFT+ERC20 either way for `create_<type>_asset` functions, which will save gas and do just one transaction, but the pricing schema part is optional and not that visible unless users find it in the tests.
We need to showcase these options in readmes. | 1.0 | Document bundled asset creation + pricing schema in readmes - As part of #1166 we introduced the option of creating assets + pricing schemas. I bundled NFT+ERC20 either way for `create_<type>_asset` functions, which will save gas and do just one transaction, but the pricing schema part is optional and not that visible unless users find it in the tests.
We need to showcase these options in readmes. | priority | document bundled asset creation pricing schema in readmes as part of we introduced the option of creating assets pricing schemas i bundled nft either way for create asset functions which will save gas and do just one transaction but the pricing schema part is optional and not that visible unless users find it in the tests we need to showcase these options in readmes | 1 |
236,976 | 18,149,039,199 | IssuesEvent | 2021-09-26 00:49:15 | element-plus/element-plus | https://api.github.com/repos/element-plus/element-plus | closed | [Feature Request] Select V2 virtualized does not support case insensitive | documentation | <!-- generated by https://elementui.github.io/issue-generator DO NOT REMOVE -->
### Existing Component
Yes
### Component Name
el-select-v2
### Description
This component is supported the filterable with case sensitive, I think it should support case insensitive like v1 or could we have a custom filter method?
<!-- generated by https://elementui.github.io/issue-generator DO NOT REMOVE -->
| 1.0 | [Feature Request] Select V2 virtualized does not support case insensitive - <!-- generated by https://elementui.github.io/issue-generator DO NOT REMOVE -->
### Existing Component
Yes
### Component Name
el-select-v2
### Description
This component is supported the filterable with case sensitive, I think it should support case insensitive like v1 or could we have a custom filter method?
<!-- generated by https://elementui.github.io/issue-generator DO NOT REMOVE -->
| non_priority | select virtualized does not support case insensitive existing component yes component name el select description this component is supported the filterable with case sensitive i think it should support case insensitive like or could we have a custom filter method | 0 |
100,184 | 16,486,679,572 | IssuesEvent | 2021-05-24 19:05:12 | CrazyKidJack/WebGoat_2.0_clone | https://api.github.com/repos/CrazyKidJack/WebGoat_2.0_clone | opened | CVE-2019-11358 (Medium) detected in multiple libraries | security vulnerability | ## CVE-2019-11358 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-2.1.4.min.js</b>, <b>jquery-3.3.1.tgz</b>, <b>jquery-2.2.3.js</b></p></summary>
<p>
<details><summary><b>jquery-2.1.4.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js</a></p>
<p>Path to dependency file: WebGoat_2.0_clone/docs/node_modules/jquery.easing/example/example.html</p>
<p>Path to vulnerable library: WebGoat_2.0_clone/webgoat-container/target/classes/static/js/libs/jquery-2.1.4.min.js,WebGoat_2.0_clone/docs/node_modules/jquery.easing/example/example.html,WebGoat_2.0_clone/webgoat-container/src/main/resources/static/js/libs/jquery-2.1.4.min.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-2.1.4.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-3.3.1.tgz</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://registry.npmjs.org/jquery/-/jquery-3.3.1.tgz">https://registry.npmjs.org/jquery/-/jquery-3.3.1.tgz</a></p>
<p>Path to dependency file: WebGoat_2.0_clone/docs/package.json</p>
<p>Path to vulnerable library: WebGoat_2.0_clone/docs/node_modules/jquery/package.json</p>
<p>
Dependency Hierarchy:
- :x: **jquery-3.3.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>jquery-2.2.3.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.3/jquery.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.3/jquery.js</a></p>
<p>Path to dependency file: WebGoat_2.0_clone/docs/node_modules/jquery.easing/example/verify.html</p>
<p>Path to vulnerable library: WebGoat_2.0_clone/docs/node_modules/jquery.easing/example/verify.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-2.2.3.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://api.github.com/repos/CrazyKidJack/WebGoat_2.0_clone/commits/bf2e3239dd01ebad5bdcf3161aa931ddd47755ff">bf2e3239dd01ebad5bdcf3161aa931ddd47755ff</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>
jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.
<p>Publish Date: 2019-04-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-11358>CVE-2019-11358</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11358">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11358</a></p>
<p>Release Date: 2019-04-20</p>
<p>Fix Resolution: 3.4.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"JavaScript","packageName":"jquery","packageVersion":"2.1.4","packageFilePaths":["/docs/node_modules/jquery.easing/example/example.html"],"isTransitiveDependency":false,"dependencyTree":"jquery:2.1.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"3.4.0"},{"packageType":"javascript/Node.js","packageName":"jquery","packageVersion":"3.3.1","packageFilePaths":["/docs/package.json"],"isTransitiveDependency":false,"dependencyTree":"jquery:3.3.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"3.4.0"},{"packageType":"JavaScript","packageName":"jquery","packageVersion":"2.2.3","packageFilePaths":["/docs/node_modules/jquery.easing/example/verify.html"],"isTransitiveDependency":false,"dependencyTree":"jquery:2.2.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"3.4.0"}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2019-11358","vulnerabilityDetails":"jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-11358","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | True | CVE-2019-11358 (Medium) detected in multiple libraries - ## CVE-2019-11358 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-2.1.4.min.js</b>, <b>jquery-3.3.1.tgz</b>, <b>jquery-2.2.3.js</b></p></summary>
<p>
<details><summary><b>jquery-2.1.4.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js</a></p>
<p>Path to dependency file: WebGoat_2.0_clone/docs/node_modules/jquery.easing/example/example.html</p>
<p>Path to vulnerable library: WebGoat_2.0_clone/webgoat-container/target/classes/static/js/libs/jquery-2.1.4.min.js,WebGoat_2.0_clone/docs/node_modules/jquery.easing/example/example.html,WebGoat_2.0_clone/webgoat-container/src/main/resources/static/js/libs/jquery-2.1.4.min.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-2.1.4.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-3.3.1.tgz</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://registry.npmjs.org/jquery/-/jquery-3.3.1.tgz">https://registry.npmjs.org/jquery/-/jquery-3.3.1.tgz</a></p>
<p>Path to dependency file: WebGoat_2.0_clone/docs/package.json</p>
<p>Path to vulnerable library: WebGoat_2.0_clone/docs/node_modules/jquery/package.json</p>
<p>
Dependency Hierarchy:
- :x: **jquery-3.3.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>jquery-2.2.3.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.3/jquery.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.3/jquery.js</a></p>
<p>Path to dependency file: WebGoat_2.0_clone/docs/node_modules/jquery.easing/example/verify.html</p>
<p>Path to vulnerable library: WebGoat_2.0_clone/docs/node_modules/jquery.easing/example/verify.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-2.2.3.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://api.github.com/repos/CrazyKidJack/WebGoat_2.0_clone/commits/bf2e3239dd01ebad5bdcf3161aa931ddd47755ff">bf2e3239dd01ebad5bdcf3161aa931ddd47755ff</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>
jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.
<p>Publish Date: 2019-04-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-11358>CVE-2019-11358</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11358">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11358</a></p>
<p>Release Date: 2019-04-20</p>
<p>Fix Resolution: 3.4.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"JavaScript","packageName":"jquery","packageVersion":"2.1.4","packageFilePaths":["/docs/node_modules/jquery.easing/example/example.html"],"isTransitiveDependency":false,"dependencyTree":"jquery:2.1.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"3.4.0"},{"packageType":"javascript/Node.js","packageName":"jquery","packageVersion":"3.3.1","packageFilePaths":["/docs/package.json"],"isTransitiveDependency":false,"dependencyTree":"jquery:3.3.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"3.4.0"},{"packageType":"JavaScript","packageName":"jquery","packageVersion":"2.2.3","packageFilePaths":["/docs/node_modules/jquery.easing/example/verify.html"],"isTransitiveDependency":false,"dependencyTree":"jquery:2.2.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"3.4.0"}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2019-11358","vulnerabilityDetails":"jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-11358","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries jquery min js jquery tgz jquery js jquery min js javascript library for dom operations library home page a href path to dependency file webgoat clone docs node modules jquery easing example example html path to vulnerable library webgoat clone webgoat container target classes static js libs jquery min js webgoat clone docs node modules jquery easing example example html webgoat clone webgoat container src main resources static js libs jquery min js dependency hierarchy x jquery min js vulnerable library jquery tgz javascript library for dom operations library home page a href path to dependency file webgoat clone docs package json path to vulnerable library webgoat clone docs node modules jquery package json dependency hierarchy x jquery tgz vulnerable library jquery js javascript library for dom operations library home page a href path to dependency file webgoat clone docs node modules jquery easing example verify html path to vulnerable library webgoat clone docs node modules jquery easing example verify html dependency hierarchy x jquery js vulnerable library found in head commit a href vulnerability details jquery before as used in drupal backdrop cms and other products mishandles jquery extend true because of object prototype pollution if an unsanitized source object contained an enumerable proto property it could extend the native object prototype publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed 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 isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree jquery isminimumfixversionavailable true minimumfixversion packagetype javascript node js packagename jquery packageversion packagefilepaths istransitivedependency false dependencytree jquery isminimumfixversionavailable true minimumfixversion packagetype javascript packagename jquery packageversion packagefilepaths istransitivedependency false dependencytree jquery isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier cve vulnerabilitydetails jquery before as used in drupal backdrop cms and other products mishandles jquery extend true because of object prototype pollution if an unsanitized source object contained an enumerable proto property it could extend the native object prototype vulnerabilityurl | 0 |
548,196 | 16,060,005,734 | IssuesEvent | 2021-04-23 11:08:10 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.bbc.com - site is not usable | browser-safari os-mac priority-critical | <!-- @browser: Safari 13.1 -->
<!-- @ua_header: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1 Safari/605.1.15 -->
<!-- @reported_with: mobile-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/71159 -->
**URL**: https://www.bbc.com/future/bespoke/follow-the-food/the-farms-being-run-from-space/
**Browser / Version**: Safari 13.1
**Operating System**: Mac OS X 10.15.4
**Tested Another Browser**: Yes Other
**Problem type**: Site is not usable
**Description**: Browser unsupported
**Steps to Reproduce**:
It annoy be opened, and there was only a picture of a loading c
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2021/4/77ab6969-e492-4f02-b223-4ef19d5132de.jpg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.bbc.com - site is not usable - <!-- @browser: Safari 13.1 -->
<!-- @ua_header: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1 Safari/605.1.15 -->
<!-- @reported_with: mobile-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/71159 -->
**URL**: https://www.bbc.com/future/bespoke/follow-the-food/the-farms-being-run-from-space/
**Browser / Version**: Safari 13.1
**Operating System**: Mac OS X 10.15.4
**Tested Another Browser**: Yes Other
**Problem type**: Site is not usable
**Description**: Browser unsupported
**Steps to Reproduce**:
It annoy be opened, and there was only a picture of a loading c
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2021/4/77ab6969-e492-4f02-b223-4ef19d5132de.jpg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | site is not usable url browser version safari operating system mac os x tested another browser yes other problem type site is not usable description browser unsupported steps to reproduce it annoy be opened and there was only a picture of a loading c view the screenshot img alt screenshot src browser configuration none from with ❤️ | 1 |
75,735 | 14,517,546,830 | IssuesEvent | 2020-12-13 20:02:58 | sanskrit-lexicon/csl-pywork | https://api.github.com/repos/sanskrit-lexicon/csl-pywork | closed | templates and constants | code-cleanup documentation | This comment begins my review and extension of the initial classification work for the modules of pywork.
The idea of csl-pywork is similar to that of csl-websanlexicon. The repository should contain programs and data files required to regenerate the pywork directories for the individual dictionaries. Thus, the individual pywork directories can be managed in the central location of csl-pywork.
This particular work is being done in a 'v01' directory, which currently is NOT part of the repository; it resides only in the Cologne server. When the dust settles, it is anticipated that 'v01' will be added to the repository.
The files managed by csl-pywork are classified as either:
* `constants` -- files that are identical for each dictionary.
* `templates` -- files that are different for each dictionary, but whose differences can easily be captured by a few parameters in a template file. When the values of the template parameters are substituted into the template, the resulting rendered template is what is needed for the particular dictionary's pywork directory.
* `idiosycratics` -- these files are quite different for each dictionary. For example, the abbreviation expansions would be such a file (for those dictionaries which have abbreviation markup).
This comment pertains only to the `constants` and `templates`. The `idiosyncratics` will be discussed in other issues.
## computed pywork files
An example of a computed file would be xxx.xml, the xml version of a dictionary digitization.
We do not contemplate inclusion of computed files as part of this csl-pywork repository. Rather, full initialization (or updating) of an individual pywork directory will be done in two steps:
* transferring files from this csl-pywork to the individual pywork directory -- a 'generate' program in csl-pywork will do this step
* computing additional files within the individual pywork directory. For example, a redo_hw.sh script in the individual pywork directory will be run to compute xxxhw.txt.
| 1.0 | templates and constants - This comment begins my review and extension of the initial classification work for the modules of pywork.
The idea of csl-pywork is similar to that of csl-websanlexicon. The repository should contain programs and data files required to regenerate the pywork directories for the individual dictionaries. Thus, the individual pywork directories can be managed in the central location of csl-pywork.
This particular work is being done in a 'v01' directory, which currently is NOT part of the repository; it resides only in the Cologne server. When the dust settles, it is anticipated that 'v01' will be added to the repository.
The files managed by csl-pywork are classified as either:
* `constants` -- files that are identical for each dictionary.
* `templates` -- files that are different for each dictionary, but whose differences can easily be captured by a few parameters in a template file. When the values of the template parameters are substituted into the template, the resulting rendered template is what is needed for the particular dictionary's pywork directory.
* `idiosycratics` -- these files are quite different for each dictionary. For example, the abbreviation expansions would be such a file (for those dictionaries which have abbreviation markup).
This comment pertains only to the `constants` and `templates`. The `idiosyncratics` will be discussed in other issues.
## computed pywork files
An example of a computed file would be xxx.xml, the xml version of a dictionary digitization.
We do not contemplate inclusion of computed files as part of this csl-pywork repository. Rather, full initialization (or updating) of an individual pywork directory will be done in two steps:
* transferring files from this csl-pywork to the individual pywork directory -- a 'generate' program in csl-pywork will do this step
* computing additional files within the individual pywork directory. For example, a redo_hw.sh script in the individual pywork directory will be run to compute xxxhw.txt.
| non_priority | templates and constants this comment begins my review and extension of the initial classification work for the modules of pywork the idea of csl pywork is similar to that of csl websanlexicon the repository should contain programs and data files required to regenerate the pywork directories for the individual dictionaries thus the individual pywork directories can be managed in the central location of csl pywork this particular work is being done in a directory which currently is not part of the repository it resides only in the cologne server when the dust settles it is anticipated that will be added to the repository the files managed by csl pywork are classified as either constants files that are identical for each dictionary templates files that are different for each dictionary but whose differences can easily be captured by a few parameters in a template file when the values of the template parameters are substituted into the template the resulting rendered template is what is needed for the particular dictionary s pywork directory idiosycratics these files are quite different for each dictionary for example the abbreviation expansions would be such a file for those dictionaries which have abbreviation markup this comment pertains only to the constants and templates the idiosyncratics will be discussed in other issues computed pywork files an example of a computed file would be xxx xml the xml version of a dictionary digitization we do not contemplate inclusion of computed files as part of this csl pywork repository rather full initialization or updating of an individual pywork directory will be done in two steps transferring files from this csl pywork to the individual pywork directory a generate program in csl pywork will do this step computing additional files within the individual pywork directory for example a redo hw sh script in the individual pywork directory will be run to compute xxxhw txt | 0 |
334,791 | 24,438,228,277 | IssuesEvent | 2022-10-06 13:00:25 | Aditya-Gupta1/job-application-cli | https://api.github.com/repos/Aditya-Gupta1/job-application-cli | closed | Add a custom badge for SQLAlchemy in README's tech stack section | documentation good first issue hacktoberfest | Create a badge for SQLAlchemy using its logo and put it under the `Tech Stack` section.
Image: https://www.sqlalchemy.org/img/sqla_logo.png
Tools like shields.io or any other relevant tools can be used to create a custom badge (Just like already mentioned in the README)
Steps:
1. Go to https://shields.io/
2. Scroll below to the `Your Badge` Section.
3. Leave the `label` field empty.
4. Populate the `message` as `SQLAlchemy`
5. Use the colour **blue**.
6. Click on the `make badge` button.
7. You'll get a URL for the badge.
8. Add it to the README's tech stack section below the already existing Badges there. | 1.0 | Add a custom badge for SQLAlchemy in README's tech stack section - Create a badge for SQLAlchemy using its logo and put it under the `Tech Stack` section.
Image: https://www.sqlalchemy.org/img/sqla_logo.png
Tools like shields.io or any other relevant tools can be used to create a custom badge (Just like already mentioned in the README)
Steps:
1. Go to https://shields.io/
2. Scroll below to the `Your Badge` Section.
3. Leave the `label` field empty.
4. Populate the `message` as `SQLAlchemy`
5. Use the colour **blue**.
6. Click on the `make badge` button.
7. You'll get a URL for the badge.
8. Add it to the README's tech stack section below the already existing Badges there. | non_priority | add a custom badge for sqlalchemy in readme s tech stack section create a badge for sqlalchemy using its logo and put it under the tech stack section image tools like shields io or any other relevant tools can be used to create a custom badge just like already mentioned in the readme steps go to scroll below to the your badge section leave the label field empty populate the message as sqlalchemy use the colour blue click on the make badge button you ll get a url for the badge add it to the readme s tech stack section below the already existing badges there | 0 |
75,307 | 9,220,326,003 | IssuesEvent | 2019-03-11 17:14:57 | OpenEnergyPlatform/oeplatform | https://api.github.com/repos/OpenEnergyPlatform/oeplatform | opened | Create a sympathetic mascot for the OEP | Content Minor Time-S Urgency-S design/layout enhancement | We decided for the [Platypus](https://en.wikipedia.org/wiki/Platypus). Because it is super sweet and the names match. | 1.0 | Create a sympathetic mascot for the OEP - We decided for the [Platypus](https://en.wikipedia.org/wiki/Platypus). Because it is super sweet and the names match. | non_priority | create a sympathetic mascot for the oep we decided for the because it is super sweet and the names match | 0 |
12,455 | 7,882,621,720 | IssuesEvent | 2018-06-26 23:44:40 | bitshares/bitshares-core | https://api.github.com/repos/bitshares/bitshares-core | opened | Performance improvement: object database query caching? | 1a Epic 2a Discussion Needed 6 Performance performance | Most of data stored in the object database is in a red-black tree. Currently, every query searches from the root to the leaf, the complexity is `O(log(n))`. Generally, some data is much hotter than others, so it makes sense to cache the hottest results (pointers or addresses) to avoid searching from root to leaf for same data again and again.
Things to be done:
- [ ] profiling / query pattern analysis : find out what's being queried the most, whether a cache would help
- [ ] caching design
Thoughts?
| True | Performance improvement: object database query caching? - Most of data stored in the object database is in a red-black tree. Currently, every query searches from the root to the leaf, the complexity is `O(log(n))`. Generally, some data is much hotter than others, so it makes sense to cache the hottest results (pointers or addresses) to avoid searching from root to leaf for same data again and again.
Things to be done:
- [ ] profiling / query pattern analysis : find out what's being queried the most, whether a cache would help
- [ ] caching design
Thoughts?
| non_priority | performance improvement object database query caching most of data stored in the object database is in a red black tree currently every query searches from the root to the leaf the complexity is o log n generally some data is much hotter than others so it makes sense to cache the hottest results pointers or addresses to avoid searching from root to leaf for same data again and again things to be done profiling query pattern analysis find out what s being queried the most whether a cache would help caching design thoughts | 0 |
621,146 | 19,578,814,970 | IssuesEvent | 2022-01-04 18:24:18 | mskcc/pluto-cwl | https://api.github.com/repos/mskcc/pluto-cwl | opened | need to update samples fillout workflow output | high priority | - need to update all portal files to include data for all new DMP samples included in output
@timosong @svural | 1.0 | need to update samples fillout workflow output - - need to update all portal files to include data for all new DMP samples included in output
@timosong @svural | priority | need to update samples fillout workflow output need to update all portal files to include data for all new dmp samples included in output timosong svural | 1 |
60,848 | 17,023,538,631 | IssuesEvent | 2021-07-03 02:32:22 | tomhughes/trac-tickets | https://api.github.com/repos/tomhughes/trac-tickets | closed | Search for street with number doesn't work if there is no number entry | Component: nominatim Priority: minor Resolution: fixed Type: defect | **[Submitted to the original trac issue database at 10.47am, Wednesday, 13th January 2010]**
If you search for the street and the house number you don't get a result cause there is no entry for the number. If this fails you should just search for the street that you get at least a result on the map. | 1.0 | Search for street with number doesn't work if there is no number entry - **[Submitted to the original trac issue database at 10.47am, Wednesday, 13th January 2010]**
If you search for the street and the house number you don't get a result cause there is no entry for the number. If this fails you should just search for the street that you get at least a result on the map. | non_priority | search for street with number doesn t work if there is no number entry if you search for the street and the house number you don t get a result cause there is no entry for the number if this fails you should just search for the street that you get at least a result on the map | 0 |
55,439 | 23,470,761,726 | IssuesEvent | 2022-08-16 21:33:30 | hashicorp/terraform-provider-aws | https://api.github.com/repos/hashicorp/terraform-provider-aws | closed | AWS Opsworks Errors on 'apply' when updating custom json | bug service/opsworks | I'm opening this to resurrect: https://github.com/hashicorp/terraform-provider-aws/issues/376. Please see the original ticket description below.
I've been able to reproduce this using terraform v1.0.2 and v3.49.0 of the aws provider. It's important to note that the issue is only encountered when making an update to the opsworks custom json. Initial creation of the opsworks stack works just fine.
There's a potential fix for the issue outlined here: https://github.com/hashicorp/terraform-provider-aws/pull/7743
>Hi All,
>
>I have an issue when creating Windows Opsworks stacks and get the error when running an apply (possible bug):
>
>aws_opsworks_stack.mystack: ValidationException: Agent Version: can only be set for Chef 11.10 and Chef 12
>I’ve been speaking to AWS who said:
>
>Hi Simon,
>Thank you very much for your reply. This certainly pointed me in the right direction.
>
>For Windows stacks, the only supported Chef version is 12.2 (vs. 12, 11.10 and older for Linux stacks). When specifying Chef 12.2 as the configuration manager, the AgentVersion API parameter is invalid, as you can see here in this CLI example:
>```
>$ aws opsworks describe-agent-versions --configuration-manager Name=Chef,Version=12.2
>{
>"AgentVersions": [
>{
>"Version": "71200020150603135521",
>"ConfigurationManager": {
>"Version": "12.2",
>"Name": "Chef"
>}
>},
>{
>"Version": "71300020150612113504",
>"ConfigurationManager": {
>"Version": "12.2",
>"Name": "Chef"
>}
>},
>{
>"Version": "71400020160128114716",
>"ConfigurationManager": {
>"Version": "12.2",
>"Name": "Chef"
>}
>},
>{
>"Version": "71500020160927200752",
>"ConfigurationManager": {
>"Version": "12.2",
>"Name": "Chef"
>}
>}
>]
>}
>$
>$ aws opsworks create-stack --name test122
>--service-role-arn arn:aws:iam::123412341234:role/aws-opsworks-service-role
>--default-instance-profile-arn arn:aws:iam::123412341234:instance-profile/aws-opsworks-ec2-role
>--stack-region us-east-1
>--configuration-manager Name=Chef,Version=12.2
>--agent-version 71500020160927200752
>--default-os "Microsoft Windows Server 2012 R2 Base"
>
>An error occurred (ValidationException) when calling the CreateStack operation: Agent Version: can only be set for Chef 11.10 and Chef 12
>$
>$ aws opsworks create-stack --name test122
>--service-role-arn arn:aws:iam::123412341234:role/aws-opsworks-service-role
>--default-instance-profile-arn arn:aws:iam::123412341234:instance-profile/aws-opsworks-ec2-role
>--stack-region us-east-1
>--configuration-manager Name=Chef,Version=12.2
>--agent-version LATEST
>--default-os "Microsoft Windows Server 2012 R2 Base"
>
>An error occurred (ValidationException) when calling the CreateStack operation: Agent Version: can only be set for Chef 11.10 and Chef 12
>$
>```
>
>In this case, apparently Terraform is trying to pass the AgentVersion API parameter to CreateStack [1] (I assume this is the call being performed), which is invalid for Chef 12.2 stacks. If I remove the "--agent-version" parameter from the CLI examples above, it creates the stack.
>I tried to find a bug report for Terraform for this issue but I was not able to, so you may need to report it. Removing the Agent Version from the resource definition (leaving it blank will default to LATEST) may also work, depending on the way Terraform crafts the API calls. I have already reported this issue to the OpsWorks documentation team in order for them to update the public documents with this requirement.
>
>I’ve tried removing the agent_version from the stack and it still errors:
>
>```
>resource "aws_opsworks_stack" "mystack" {
> name = "${var.environment_name}-mystack"
> region = "eu-west-1"
> service_role_arn = "${aws_iam_role.aws-opsworks-service-role.arn}"
> default_instance_profile_arn = "${aws_iam_instance_profile.aws-opsworks-ec2-instance-role.arn}"
> #agent_version = "LATEST"
> configuration_manager_name = "Chef"
> configuration_manager_version = "12.2"
> default_os = "Microsoft Windows Server 2012 R2 Base"
> vpc_id = "${aws_vpc.default.id}"
> default_subnet_id = "${aws_subnet.zone-a.id}"
> hostname_theme = "Legendary_creatures_from_Japan"
> color = "rgb(100, 131, 57)"
> default_root_device_type = "ebs"
> use_opsworks_security_groups = "false"
> manage_berkshelf = "false"
> use_custom_cookbooks = "true"
> default_ssh_key_name = "${var.key_name}"
> custom_cookbooks_source {
> type = "git"
> url = "https://mygit/my.git"
> }
> custom_json = <<EOT
>{
>"mysettings": {
> "test": "test"
> }
>}
>EOT
>}
>```
>I’m running Terraform v0.7.10 if that helps.
>
>Does anyone have any ideas?
>
>Cheers,
>Simon.
| 1.0 | AWS Opsworks Errors on 'apply' when updating custom json - I'm opening this to resurrect: https://github.com/hashicorp/terraform-provider-aws/issues/376. Please see the original ticket description below.
I've been able to reproduce this using terraform v1.0.2 and v3.49.0 of the aws provider. It's important to note that the issue is only encountered when making an update to the opsworks custom json. Initial creation of the opsworks stack works just fine.
There's a potential fix for the issue outlined here: https://github.com/hashicorp/terraform-provider-aws/pull/7743
>Hi All,
>
>I have an issue when creating Windows Opsworks stacks and get the error when running an apply (possible bug):
>
>aws_opsworks_stack.mystack: ValidationException: Agent Version: can only be set for Chef 11.10 and Chef 12
>I’ve been speaking to AWS who said:
>
>Hi Simon,
>Thank you very much for your reply. This certainly pointed me in the right direction.
>
>For Windows stacks, the only supported Chef version is 12.2 (vs. 12, 11.10 and older for Linux stacks). When specifying Chef 12.2 as the configuration manager, the AgentVersion API parameter is invalid, as you can see here in this CLI example:
>```
>$ aws opsworks describe-agent-versions --configuration-manager Name=Chef,Version=12.2
>{
>"AgentVersions": [
>{
>"Version": "71200020150603135521",
>"ConfigurationManager": {
>"Version": "12.2",
>"Name": "Chef"
>}
>},
>{
>"Version": "71300020150612113504",
>"ConfigurationManager": {
>"Version": "12.2",
>"Name": "Chef"
>}
>},
>{
>"Version": "71400020160128114716",
>"ConfigurationManager": {
>"Version": "12.2",
>"Name": "Chef"
>}
>},
>{
>"Version": "71500020160927200752",
>"ConfigurationManager": {
>"Version": "12.2",
>"Name": "Chef"
>}
>}
>]
>}
>$
>$ aws opsworks create-stack --name test122
>--service-role-arn arn:aws:iam::123412341234:role/aws-opsworks-service-role
>--default-instance-profile-arn arn:aws:iam::123412341234:instance-profile/aws-opsworks-ec2-role
>--stack-region us-east-1
>--configuration-manager Name=Chef,Version=12.2
>--agent-version 71500020160927200752
>--default-os "Microsoft Windows Server 2012 R2 Base"
>
>An error occurred (ValidationException) when calling the CreateStack operation: Agent Version: can only be set for Chef 11.10 and Chef 12
>$
>$ aws opsworks create-stack --name test122
>--service-role-arn arn:aws:iam::123412341234:role/aws-opsworks-service-role
>--default-instance-profile-arn arn:aws:iam::123412341234:instance-profile/aws-opsworks-ec2-role
>--stack-region us-east-1
>--configuration-manager Name=Chef,Version=12.2
>--agent-version LATEST
>--default-os "Microsoft Windows Server 2012 R2 Base"
>
>An error occurred (ValidationException) when calling the CreateStack operation: Agent Version: can only be set for Chef 11.10 and Chef 12
>$
>```
>
>In this case, apparently Terraform is trying to pass the AgentVersion API parameter to CreateStack [1] (I assume this is the call being performed), which is invalid for Chef 12.2 stacks. If I remove the "--agent-version" parameter from the CLI examples above, it creates the stack.
>I tried to find a bug report for Terraform for this issue but I was not able to, so you may need to report it. Removing the Agent Version from the resource definition (leaving it blank will default to LATEST) may also work, depending on the way Terraform crafts the API calls. I have already reported this issue to the OpsWorks documentation team in order for them to update the public documents with this requirement.
>
>I’ve tried removing the agent_version from the stack and it still errors:
>
>```
>resource "aws_opsworks_stack" "mystack" {
> name = "${var.environment_name}-mystack"
> region = "eu-west-1"
> service_role_arn = "${aws_iam_role.aws-opsworks-service-role.arn}"
> default_instance_profile_arn = "${aws_iam_instance_profile.aws-opsworks-ec2-instance-role.arn}"
> #agent_version = "LATEST"
> configuration_manager_name = "Chef"
> configuration_manager_version = "12.2"
> default_os = "Microsoft Windows Server 2012 R2 Base"
> vpc_id = "${aws_vpc.default.id}"
> default_subnet_id = "${aws_subnet.zone-a.id}"
> hostname_theme = "Legendary_creatures_from_Japan"
> color = "rgb(100, 131, 57)"
> default_root_device_type = "ebs"
> use_opsworks_security_groups = "false"
> manage_berkshelf = "false"
> use_custom_cookbooks = "true"
> default_ssh_key_name = "${var.key_name}"
> custom_cookbooks_source {
> type = "git"
> url = "https://mygit/my.git"
> }
> custom_json = <<EOT
>{
>"mysettings": {
> "test": "test"
> }
>}
>EOT
>}
>```
>I’m running Terraform v0.7.10 if that helps.
>
>Does anyone have any ideas?
>
>Cheers,
>Simon.
| non_priority | aws opsworks errors on apply when updating custom json i m opening this to resurrect please see the original ticket description below i ve been able to reproduce this using terraform and of the aws provider it s important to note that the issue is only encountered when making an update to the opsworks custom json initial creation of the opsworks stack works just fine there s a potential fix for the issue outlined here hi all i have an issue when creating windows opsworks stacks and get the error when running an apply possible bug aws opsworks stack mystack validationexception agent version can only be set for chef and chef i’ve been speaking to aws who said hi simon thank you very much for your reply this certainly pointed me in the right direction for windows stacks the only supported chef version is vs and older for linux stacks when specifying chef as the configuration manager the agentversion api parameter is invalid as you can see here in this cli example aws opsworks describe agent versions configuration manager name chef version agentversions version configurationmanager version name chef version configurationmanager version name chef version configurationmanager version name chef version configurationmanager version name chef aws opsworks create stack name service role arn arn aws iam role aws opsworks service role default instance profile arn arn aws iam instance profile aws opsworks role stack region us east configuration manager name chef version agent version default os microsoft windows server base an error occurred validationexception when calling the createstack operation agent version can only be set for chef and chef aws opsworks create stack name service role arn arn aws iam role aws opsworks service role default instance profile arn arn aws iam instance profile aws opsworks role stack region us east configuration manager name chef version agent version latest default os microsoft windows server base an error occurred validationexception when calling the createstack operation agent version can only be set for chef and chef in this case apparently terraform is trying to pass the agentversion api parameter to createstack i assume this is the call being performed which is invalid for chef stacks if i remove the agent version parameter from the cli examples above it creates the stack i tried to find a bug report for terraform for this issue but i was not able to so you may need to report it removing the agent version from the resource definition leaving it blank will default to latest may also work depending on the way terraform crafts the api calls i have already reported this issue to the opsworks documentation team in order for them to update the public documents with this requirement i’ve tried removing the agent version from the stack and it still errors resource aws opsworks stack mystack name var environment name mystack region eu west service role arn aws iam role aws opsworks service role arn default instance profile arn aws iam instance profile aws opsworks instance role arn agent version latest configuration manager name chef configuration manager version default os microsoft windows server base vpc id aws vpc default id default subnet id aws subnet zone a id hostname theme legendary creatures from japan color rgb default root device type ebs use opsworks security groups false manage berkshelf false use custom cookbooks true default ssh key name var key name custom cookbooks source type git url custom json eot mysettings test test eot i’m running terraform if that helps does anyone have any ideas cheers simon | 0 |
3,117 | 2,665,569,835 | IssuesEvent | 2015-03-20 21:26:22 | dotnet/roslyn | https://api.github.com/repos/dotnet/roslyn | closed | VB SemanticModel.GetEnclosingSymbol doesn't work correctly with lambda parameters/headers | 4 - In Review Area-Compilers Bug Resolution-By Design | Consider code
```VB
Imports System
Class C
Sub F()
Dim f1 = New Func(Of Integer, Integer, Integer)(
Function(a1, a2)
Return a1
End Function)
End Sub
End Class
```
SemanticModel.GetEnclosingSymbol(span start of ParameterSyntax "a1" )
returns Sub F. It should return the declaring lambda (C# does).
<!---
@huboard:{"order":474.5,"milestone_order":1290,"custom_state":""}
-->
| 1.0 | VB SemanticModel.GetEnclosingSymbol doesn't work correctly with lambda parameters/headers - Consider code
```VB
Imports System
Class C
Sub F()
Dim f1 = New Func(Of Integer, Integer, Integer)(
Function(a1, a2)
Return a1
End Function)
End Sub
End Class
```
SemanticModel.GetEnclosingSymbol(span start of ParameterSyntax "a1" )
returns Sub F. It should return the declaring lambda (C# does).
<!---
@huboard:{"order":474.5,"milestone_order":1290,"custom_state":""}
-->
| non_priority | vb semanticmodel getenclosingsymbol doesn t work correctly with lambda parameters headers consider code vb imports system class c sub f dim new func of integer integer integer function return end function end sub end class semanticmodel getenclosingsymbol span start of parametersyntax returns sub f it should return the declaring lambda c does huboard order milestone order custom state | 0 |
413,325 | 12,065,070,260 | IssuesEvent | 2020-04-16 09:21:14 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.loteriasonline.caixa.gov.br - see bug description | browser-focus-geckoview engine-gecko priority-important | <!-- @browser: Firefox Mobile 75.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 7.1.1; Mobile; rv:75.0) Gecko/75.0 Firefox/75.0 -->
<!-- @reported_with: -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/51685 -->
<!-- @extra_labels: browser-focus-geckoview -->
**URL**: https://www.loteriasonline.caixa.gov.br/silce-web/
**Browser / Version**: Firefox Mobile 75.0
**Operating System**: Android 7.1.1
**Tested Another Browser**: Yes Chrome
**Problem type**: Something else
**Description**: blank page
**Steps to Reproduce**:
i Just tried tô access the site.
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
Submitted in the name of `@paulofgo`
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.loteriasonline.caixa.gov.br - see bug description - <!-- @browser: Firefox Mobile 75.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 7.1.1; Mobile; rv:75.0) Gecko/75.0 Firefox/75.0 -->
<!-- @reported_with: -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/51685 -->
<!-- @extra_labels: browser-focus-geckoview -->
**URL**: https://www.loteriasonline.caixa.gov.br/silce-web/
**Browser / Version**: Firefox Mobile 75.0
**Operating System**: Android 7.1.1
**Tested Another Browser**: Yes Chrome
**Problem type**: Something else
**Description**: blank page
**Steps to Reproduce**:
i Just tried tô access the site.
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
Submitted in the name of `@paulofgo`
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | see bug description url browser version firefox mobile operating system android tested another browser yes chrome problem type something else description blank page steps to reproduce i just tried tô access the site browser configuration none submitted in the name of paulofgo from with ❤️ | 1 |
230,837 | 7,620,151,415 | IssuesEvent | 2018-05-03 00:45:50 | StrangeLoopGames/EcoIssues | https://api.github.com/repos/StrangeLoopGames/EcoIssues | closed | Crash while harvesting | High Priority | Der Wert darf nicht NULL sein.
The value can not be NULL.
Parametername: key
bei System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument)
bei System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
bei System.Collections.Generic.Dictionary`2.TryGetValue(TKey key, TValue& value)
bei Eco.Gameplay.Items.ItemAttribute.Get[T](Type itemType)
bei Eco.Gameplay.Plants.PlantEntity.TryHarvest(Player player, Boolean picked)
bei Eco.Mods.TechTree.ScytheItem.OnActLeft(InteractionContext context)
bei Eco.Gameplay.Interactions.InteractionExtensions.ExecuteUntilSuccess(IEnumerable`1 results)
bei Eco.Gameplay.Players.Player.PlayerInteract(InteractionInfo info) | 1.0 | Crash while harvesting - Der Wert darf nicht NULL sein.
The value can not be NULL.
Parametername: key
bei System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument)
bei System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
bei System.Collections.Generic.Dictionary`2.TryGetValue(TKey key, TValue& value)
bei Eco.Gameplay.Items.ItemAttribute.Get[T](Type itemType)
bei Eco.Gameplay.Plants.PlantEntity.TryHarvest(Player player, Boolean picked)
bei Eco.Mods.TechTree.ScytheItem.OnActLeft(InteractionContext context)
bei Eco.Gameplay.Interactions.InteractionExtensions.ExecuteUntilSuccess(IEnumerable`1 results)
bei Eco.Gameplay.Players.Player.PlayerInteract(InteractionInfo info) | priority | crash while harvesting der wert darf nicht null sein the value can not be null parametername key bei system throwhelper throwargumentnullexception exceptionargument argument bei system collections generic dictionary findentry tkey key bei system collections generic dictionary trygetvalue tkey key tvalue value bei eco gameplay items itemattribute get type itemtype bei eco gameplay plants plantentity tryharvest player player boolean picked bei eco mods techtree scytheitem onactleft interactioncontext context bei eco gameplay interactions interactionextensions executeuntilsuccess ienumerable results bei eco gameplay players player playerinteract interactioninfo info | 1 |
549,417 | 16,092,313,670 | IssuesEvent | 2021-04-26 18:18:25 | microsoft/CSS-Exchange | https://api.github.com/repos/microsoft/CSS-Exchange | opened | ExchangeLogCollector - Build out a table for DAG information | Exchange Log Collector Low Priority Need Investigation enhancement | Build out a nice table view of DAG information
DAG Name:
FSW:
FSW IP Address:
FSW Site:
NODES/Members
ServerName | IP Addresses | Site
Maybe even do a path ping from the node to the FSW and a node in the other site/subnet. | 1.0 | ExchangeLogCollector - Build out a table for DAG information - Build out a nice table view of DAG information
DAG Name:
FSW:
FSW IP Address:
FSW Site:
NODES/Members
ServerName | IP Addresses | Site
Maybe even do a path ping from the node to the FSW and a node in the other site/subnet. | priority | exchangelogcollector build out a table for dag information build out a nice table view of dag information dag name fsw fsw ip address fsw site nodes members servername ip addresses site maybe even do a path ping from the node to the fsw and a node in the other site subnet | 1 |
153,415 | 5,891,879,972 | IssuesEvent | 2017-05-17 18:08:10 | facebook/prepack | https://api.github.com/repos/facebook/prepack | closed | Support serialization of DataView, ArrayBuffer | help wanted high priority serializer | Make serialization work for the related cluster of DataView, ArrayBuffer, and all typed arrays.
Add individual test cases for the different required aspects.
Look at #505 for an example of how to add serialization capabilities for typed arrays. | 1.0 | Support serialization of DataView, ArrayBuffer - Make serialization work for the related cluster of DataView, ArrayBuffer, and all typed arrays.
Add individual test cases for the different required aspects.
Look at #505 for an example of how to add serialization capabilities for typed arrays. | priority | support serialization of dataview arraybuffer make serialization work for the related cluster of dataview arraybuffer and all typed arrays add individual test cases for the different required aspects look at for an example of how to add serialization capabilities for typed arrays | 1 |
784,362 | 27,567,749,342 | IssuesEvent | 2023-03-08 06:13:50 | DeadlyBossMods/DBM-Dungeons | https://api.github.com/repos/DeadlyBossMods/DBM-Dungeons | closed | Add warning for 'Shadow Prison' spell in Cataclysm Blackrock Caverns | 🛠 Feature Request Low Priority | Hi! While this is not a super important thing but I think putting a very loud warning for [Shadow Prison](https://www.wowhead.com/spell=76686) spell would be good cause currently this ability is one-shotting people if they move out of the barely visible prison. DBM does not warn about this spell at all so a lot of people dies 'out of nowhere' while doing this dungeon on leveling or timewalking. It would be nice to have this added so people can know what is going on. | 1.0 | Add warning for 'Shadow Prison' spell in Cataclysm Blackrock Caverns - Hi! While this is not a super important thing but I think putting a very loud warning for [Shadow Prison](https://www.wowhead.com/spell=76686) spell would be good cause currently this ability is one-shotting people if they move out of the barely visible prison. DBM does not warn about this spell at all so a lot of people dies 'out of nowhere' while doing this dungeon on leveling or timewalking. It would be nice to have this added so people can know what is going on. | priority | add warning for shadow prison spell in cataclysm blackrock caverns hi while this is not a super important thing but i think putting a very loud warning for spell would be good cause currently this ability is one shotting people if they move out of the barely visible prison dbm does not warn about this spell at all so a lot of people dies out of nowhere while doing this dungeon on leveling or timewalking it would be nice to have this added so people can know what is going on | 1 |
17,083 | 22,587,525,965 | IssuesEvent | 2022-06-28 16:29:15 | GoogleCloudPlatform/emblem | https://api.github.com/repos/GoogleCloudPlatform/emblem | opened | New Process: Merger verifies staging | type: process priority: p0 persona: maintainer | Adopt & document a new process that either the PR author or merger must verify a change is shipped to staging as expected, or reopen / create an issue to mark that a change didn't deploy as expected.
This will ensure changes ship as expected, indicating the implementation is complete. | 1.0 | New Process: Merger verifies staging - Adopt & document a new process that either the PR author or merger must verify a change is shipped to staging as expected, or reopen / create an issue to mark that a change didn't deploy as expected.
This will ensure changes ship as expected, indicating the implementation is complete. | non_priority | new process merger verifies staging adopt document a new process that either the pr author or merger must verify a change is shipped to staging as expected or reopen create an issue to mark that a change didn t deploy as expected this will ensure changes ship as expected indicating the implementation is complete | 0 |
34,323 | 6,311,205,850 | IssuesEvent | 2017-07-23 17:24:45 | marienfressinaud/project-zero | https://api.github.com/repos/marienfressinaud/project-zero | closed | Document new release | P: Medium T: Documentation | - open a new ticket (such as https://github.com/marienfressinaud/project-zero/issues/59)
- Generate lines with:
```bash
$ git log --pretty=format:%s --first-parent --reverse [last tag]..HEAD | grep add:
$ git log --pretty=format:%s --first-parent --reverse [last tag]..HEAD | grep fix:
$ git log --pretty=format:%s --first-parent --reverse [last tag]..HEAD | grep doc:
```
- Create links to GitHub issues
- ? | 1.0 | Document new release - - open a new ticket (such as https://github.com/marienfressinaud/project-zero/issues/59)
- Generate lines with:
```bash
$ git log --pretty=format:%s --first-parent --reverse [last tag]..HEAD | grep add:
$ git log --pretty=format:%s --first-parent --reverse [last tag]..HEAD | grep fix:
$ git log --pretty=format:%s --first-parent --reverse [last tag]..HEAD | grep doc:
```
- Create links to GitHub issues
- ? | non_priority | document new release open a new ticket such as generate lines with bash git log pretty format s first parent reverse head grep add git log pretty format s first parent reverse head grep fix git log pretty format s first parent reverse head grep doc create links to github issues | 0 |
21,363 | 2,639,601,682 | IssuesEvent | 2015-03-11 03:40:21 | cs2103jan2015-w13-4j/main | https://api.github.com/repos/cs2103jan2015-w13-4j/main | closed | As an advanced user, I can link other GTD tools to the program | priority.low type.story | ... so that I can have one centralized tool without adding all previous tasks | 1.0 | As an advanced user, I can link other GTD tools to the program - ... so that I can have one centralized tool without adding all previous tasks | priority | as an advanced user i can link other gtd tools to the program so that i can have one centralized tool without adding all previous tasks | 1 |
159,510 | 20,068,288,812 | IssuesEvent | 2022-02-04 01:07:52 | emilwareus/spring-boot | https://api.github.com/repos/emilwareus/spring-boot | opened | CVE-2022-23437 (Medium) detected in xercesImpl-2.12.0.jar | security vulnerability | ## CVE-2022-23437 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xercesImpl-2.12.0.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. The Apache Xerces2 parser is
the reference implementation of XNI but other parser components, configurations, and parsers can be written
using the Xerces Native Interface. For complete design and implementation documents, refer to the XNI Manual.
Xerces2 is a fully conforming XML Schema 1.0 processor. A partial experimental implementation of the XML Schema
1.1 Structures and Datatypes Working Drafts (December 2009) and an experimental implementation of the XML Schema
Definition Language (XSD): Component Designators (SCD) Candidate Recommendation (January 2010) are provided for
evaluation. For more information, refer to the XML Schema page. Xerces2 also provides a complete implementation
of the Document Object Model Level 3 Core and Load/Save W3C Recommendations and provides a complete
implementation of the XML Inclusions (XInclude) W3C Recommendation. It also provides support for OASIS XML
Catalogs v1.1. Xerces2 is able to parse documents written according to the XML 1.1 Recommendation, except that
it does not yet provide an option to enable normalization checking as described in section 2.13 of this
specification. It also handles namespaces according to the XML Namespaces 1.1 Recommendation, and will correctly
serialize XML 1.1 documents if the DOM level 3 load/save APIs are in use.</p>
<p>Library home page: <a href="https://xerces.apache.org/xerces2-j/">https://xerces.apache.org/xerces2-j/</a></p>
<p>Path to dependency file: /spring-boot/spring-boot-project/spring-boot-test-autoconfigure/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/xerces/xercesImpl/2.12.0/xercesImpl-2.12.0.jar,/root/.m2/repository/xerces/xercesImpl/2.12.0/xercesImpl-2.12.0.jar,/root/.m2/repository/xerces/xercesImpl/2.12.0/xercesImpl-2.12.0.jar</p>
<p>
Dependency Hierarchy:
- htmlunit-2.35.0.jar (Root Library)
- neko-htmlunit-2.35.0.jar
- :x: **xercesImpl-2.12.0.jar** (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>
There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads. This causes, the XercesJ XML parser to wait in an infinite loop, which may sometimes consume system resources for prolonged duration. This vulnerability is present within XercesJ version 2.12.1 and the previous versions.
<p>Publish Date: 2022-01-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437>CVE-2022-23437</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: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-h65f-jvqw-m9fj">https://github.com/advisories/GHSA-h65f-jvqw-m9fj</a></p>
<p>Release Date: 2022-01-24</p>
<p>Fix Resolution: xerces:xercesImpl:2.12.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-23437 (Medium) detected in xercesImpl-2.12.0.jar - ## CVE-2022-23437 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xercesImpl-2.12.0.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. The Apache Xerces2 parser is
the reference implementation of XNI but other parser components, configurations, and parsers can be written
using the Xerces Native Interface. For complete design and implementation documents, refer to the XNI Manual.
Xerces2 is a fully conforming XML Schema 1.0 processor. A partial experimental implementation of the XML Schema
1.1 Structures and Datatypes Working Drafts (December 2009) and an experimental implementation of the XML Schema
Definition Language (XSD): Component Designators (SCD) Candidate Recommendation (January 2010) are provided for
evaluation. For more information, refer to the XML Schema page. Xerces2 also provides a complete implementation
of the Document Object Model Level 3 Core and Load/Save W3C Recommendations and provides a complete
implementation of the XML Inclusions (XInclude) W3C Recommendation. It also provides support for OASIS XML
Catalogs v1.1. Xerces2 is able to parse documents written according to the XML 1.1 Recommendation, except that
it does not yet provide an option to enable normalization checking as described in section 2.13 of this
specification. It also handles namespaces according to the XML Namespaces 1.1 Recommendation, and will correctly
serialize XML 1.1 documents if the DOM level 3 load/save APIs are in use.</p>
<p>Library home page: <a href="https://xerces.apache.org/xerces2-j/">https://xerces.apache.org/xerces2-j/</a></p>
<p>Path to dependency file: /spring-boot/spring-boot-project/spring-boot-test-autoconfigure/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/xerces/xercesImpl/2.12.0/xercesImpl-2.12.0.jar,/root/.m2/repository/xerces/xercesImpl/2.12.0/xercesImpl-2.12.0.jar,/root/.m2/repository/xerces/xercesImpl/2.12.0/xercesImpl-2.12.0.jar</p>
<p>
Dependency Hierarchy:
- htmlunit-2.35.0.jar (Root Library)
- neko-htmlunit-2.35.0.jar
- :x: **xercesImpl-2.12.0.jar** (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>
There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads. This causes, the XercesJ XML parser to wait in an infinite loop, which may sometimes consume system resources for prolonged duration. This vulnerability is present within XercesJ version 2.12.1 and the previous versions.
<p>Publish Date: 2022-01-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437>CVE-2022-23437</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: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-h65f-jvqw-m9fj">https://github.com/advisories/GHSA-h65f-jvqw-m9fj</a></p>
<p>Release Date: 2022-01-24</p>
<p>Fix Resolution: xerces:xercesImpl:2.12.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in xercesimpl jar 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 the apache parser is the reference implementation of xni but other parser components configurations and parsers can be written using the xerces native interface for complete design and implementation documents refer to the xni manual is a fully conforming xml schema processor a partial experimental implementation of the xml schema structures and datatypes working drafts december and an experimental implementation of the xml schema definition language xsd component designators scd candidate recommendation january are provided for evaluation for more information refer to the xml schema page also provides a complete implementation of the document object model level core and load save recommendations and provides a complete implementation of the xml inclusions xinclude recommendation it also provides support for oasis xml catalogs is able to parse documents written according to the xml recommendation except that it does not yet provide an option to enable normalization checking as described in section of this specification it also handles namespaces according to the xml namespaces recommendation and will correctly serialize xml documents if the dom level load save apis are in use library home page a href path to dependency file spring boot spring boot project spring boot test autoconfigure pom xml path to vulnerable library root repository xerces xercesimpl xercesimpl jar root repository xerces xercesimpl xercesimpl jar root repository xerces xercesimpl xercesimpl jar dependency hierarchy htmlunit jar root library neko htmlunit jar x xercesimpl jar vulnerable library vulnerability details there s a vulnerability within the apache xerces java xercesj xml parser when handling specially crafted xml document payloads this causes the xercesj xml parser to wait in an infinite loop which may sometimes consume system resources for prolonged duration this vulnerability is present within xercesj version and the previous versions publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required 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 xerces xercesimpl step up your open source security game with whitesource | 0 |
267,359 | 8,388,127,615 | IssuesEvent | 2018-10-09 04:36:16 | WP-for-Church/Sermon-Manager | https://api.github.com/repos/WP-for-Church/Sermon-Manager | opened | Books not importing with SB sermons | [Priority] Standard [Type] Enhancement | And that's because those fields don't exist in SB.
Client's idea: Try to guess the book based on scripture. | 1.0 | Books not importing with SB sermons - And that's because those fields don't exist in SB.
Client's idea: Try to guess the book based on scripture. | priority | books not importing with sb sermons and that s because those fields don t exist in sb client s idea try to guess the book based on scripture | 1 |
290,681 | 8,902,604,605 | IssuesEvent | 2019-01-17 08:08:03 | canonical-websites/snapcraft.io | https://api.github.com/repos/canonical-websites/snapcraft.io | closed | Release UI: HTML errors result in JSON parse error | Priority: High | Sometimes API calls for release return HTML instead of JSON (for example in case of gateway timeout, etc). This causes release UI to show weird and unhelpful JSON parse error.
<img width="1663" alt="screen shot 2018-10-03 at 12 58 45" src="https://user-images.githubusercontent.com/83575/46406577-4a024d80-c70c-11e8-9f32-3541e573779f.png">
### Expected behaviour
We should show better error message when HTML error is returned.
| 1.0 | Release UI: HTML errors result in JSON parse error - Sometimes API calls for release return HTML instead of JSON (for example in case of gateway timeout, etc). This causes release UI to show weird and unhelpful JSON parse error.
<img width="1663" alt="screen shot 2018-10-03 at 12 58 45" src="https://user-images.githubusercontent.com/83575/46406577-4a024d80-c70c-11e8-9f32-3541e573779f.png">
### Expected behaviour
We should show better error message when HTML error is returned.
| priority | release ui html errors result in json parse error sometimes api calls for release return html instead of json for example in case of gateway timeout etc this causes release ui to show weird and unhelpful json parse error img width alt screen shot at src expected behaviour we should show better error message when html error is returned | 1 |
263,342 | 28,029,995,804 | IssuesEvent | 2023-03-28 11:45:29 | RG4421/ampere-centos-kernel | https://api.github.com/repos/RG4421/ampere-centos-kernel | reopened | CVE-2021-3411 (Medium) detected in linux-yocto-devv5.3 | Mend: dependency security vulnerability | ## CVE-2021-3411 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yocto-devv5.3</b></p></summary>
<p>
<p>Linux Embedded Kernel - tracks the next mainline release</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto-dev>https://git.yoctoproject.org/git/linux-yocto-dev</a></p>
<p>Found in base branch: <b>amp-centos-8.0-kernel</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>/arch/x86/kernel/kprobes/opt.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/arch/x86/kernel/kprobes/opt.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/arch/x86/kernel/kprobes/opt.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>
A flaw was found in the Linux kernel in versions prior to 5.10. A violation of memory access was found while detecting a padding of int3 in the linking state. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
<p>Publish Date: 2021-03-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-3411>CVE-2021-3411</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.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- 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://www.linuxkernelcves.com/cves/CVE-2021-3411">https://www.linuxkernelcves.com/cves/CVE-2021-3411</a></p>
<p>Release Date: 2021-03-09</p>
<p>Fix Resolution: v5.9.15, v5.10</p>
</p>
</details>
<p></p>
| True | CVE-2021-3411 (Medium) detected in linux-yocto-devv5.3 - ## CVE-2021-3411 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yocto-devv5.3</b></p></summary>
<p>
<p>Linux Embedded Kernel - tracks the next mainline release</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto-dev>https://git.yoctoproject.org/git/linux-yocto-dev</a></p>
<p>Found in base branch: <b>amp-centos-8.0-kernel</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>/arch/x86/kernel/kprobes/opt.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/arch/x86/kernel/kprobes/opt.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/arch/x86/kernel/kprobes/opt.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>
A flaw was found in the Linux kernel in versions prior to 5.10. A violation of memory access was found while detecting a padding of int3 in the linking state. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
<p>Publish Date: 2021-03-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-3411>CVE-2021-3411</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.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- 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://www.linuxkernelcves.com/cves/CVE-2021-3411">https://www.linuxkernelcves.com/cves/CVE-2021-3411</a></p>
<p>Release Date: 2021-03-09</p>
<p>Fix Resolution: v5.9.15, v5.10</p>
</p>
</details>
<p></p>
| non_priority | cve medium detected in linux yocto cve medium severity vulnerability vulnerable library linux yocto linux embedded kernel tracks the next mainline release library home page a href found in base branch amp centos kernel vulnerable source files arch kernel kprobes opt c arch kernel kprobes opt c arch kernel kprobes opt c vulnerability details a flaw was found in the linux kernel in versions prior to a violation of memory access was found while detecting a padding of in the linking state the highest threat from this vulnerability is to data confidentiality and integrity as well as system availability publish date url a href cvss score details base score metrics exploitability metrics attack vector local 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 | 0 |
55,537 | 13,638,836,019 | IssuesEvent | 2020-09-25 09:59:20 | TerryCavanagh/diceydungeonsbeta | https://api.github.com/repos/TerryCavanagh/diceydungeonsbeta | closed | Rethink Gym Leader in Parallel Universe | v0.5: 21st June Build | This one's not so bad, but an extra 6 damage isn't really interesting to fight against in the way the Weaken 3 is. | 1.0 | Rethink Gym Leader in Parallel Universe - This one's not so bad, but an extra 6 damage isn't really interesting to fight against in the way the Weaken 3 is. | non_priority | rethink gym leader in parallel universe this one s not so bad but an extra damage isn t really interesting to fight against in the way the weaken is | 0 |
699,386 | 24,015,258,402 | IssuesEvent | 2022-09-14 23:32:48 | bats-core/bats-core | https://api.github.com/repos/bats-core/bats-core | closed | setup_suite: exported variables are gone | Type: Bug Component: Docs Priority: Critical Status: Confirmed Size: Small | **Describe the bug**
exported environment variables from setup_suite are not available on setup or `@test`
**To Reproduce**
```bash
setup_suite() {
{
export SETUP_SUITE="1"
} >&2
}
setup_file() {
{
export SETUP_FILE="1"
} >&2
}
setup() {
{
export SETUP_TEST="1"
} >&2
}
@test "env" {
run echo "${SETUP_TEST}"
[ "$output" = "1" ]
run echo "${SETUP_FILE}"
[ "$output" = "1" ]
run echo "${SETUP_SUITE}"
[ "$output" = "1" ]
}
```
**Expected behavior**
exported variables from setup_suite should be available on test like exported variables from setup_file.
**Environment (please complete the following information):**
- Bats Version: c97b3a1
- OS: MacOS
- Bash version: 3.2.57(1)-release
**Additional context**
Add any other context about the problem here.
| 1.0 | setup_suite: exported variables are gone - **Describe the bug**
exported environment variables from setup_suite are not available on setup or `@test`
**To Reproduce**
```bash
setup_suite() {
{
export SETUP_SUITE="1"
} >&2
}
setup_file() {
{
export SETUP_FILE="1"
} >&2
}
setup() {
{
export SETUP_TEST="1"
} >&2
}
@test "env" {
run echo "${SETUP_TEST}"
[ "$output" = "1" ]
run echo "${SETUP_FILE}"
[ "$output" = "1" ]
run echo "${SETUP_SUITE}"
[ "$output" = "1" ]
}
```
**Expected behavior**
exported variables from setup_suite should be available on test like exported variables from setup_file.
**Environment (please complete the following information):**
- Bats Version: c97b3a1
- OS: MacOS
- Bash version: 3.2.57(1)-release
**Additional context**
Add any other context about the problem here.
| priority | setup suite exported variables are gone describe the bug exported environment variables from setup suite are not available on setup or test to reproduce bash setup suite export setup suite setup file export setup file setup export setup test test env run echo setup test run echo setup file run echo setup suite expected behavior exported variables from setup suite should be available on test like exported variables from setup file environment please complete the following information bats version os macos bash version release additional context add any other context about the problem here | 1 |
152,821 | 12,127,219,872 | IssuesEvent | 2020-04-22 18:21:00 | rancher/rancher | https://api.github.com/repos/rancher/rancher | closed | Rancher 2 Master gets OOM killed | [zube]: To Test internal kind/bug | **What kind of request is this (question/bug/enhancement/feature request): Bug
**Steps to reproduce (least amount of steps as possible):
The rancher master does take about 1.75 GB/s RAM per hour and get killed by the kernel OOM. Only the master is affected, other rancher pods running have a normal memory usage. We already upgraded to 16 GB RAM, but the issue still persists.
We guess it could have been related to cluster-monitoring, as we find data in memory dumps done with GDB. Is the management layer caching cluster-monitoring data?
```
/proc/PID/smaps:
+c084000000-c08c000000 rw-p 00000000 00:00 0
+Size: 131072 kB
+Rss: 131072 kB
+Pss: 131072 kB
+Shared_Clean: 0 kB
+Shared_Dirty: 0 kB
+Private_Clean: 0 kB
+Private_Dirty: 131072 kB
+Referenced: 131072 kB
+Anonymous: 131072 kB
+AnonHugePages: 0 kB
+Shared_Hugetlb: 0 kB
+Private_Hugetlb: 0 kB
+Swap: 0 kB
+SwapPss: 0 kB
+KernelPageSize: 4 kB
+MMUPageSize: 4 kB
+Locked: 0 kB
+VmFlags: rd wr mr mw me ac sd
{"metadata":{"name":"cluster-monitoring.v341","namespace":"cattle-prometheus","selfLink":"/api/v1/namespaces/cattle-prometheus/configmaps/cluster-monitoring.v341","uid":"de760c13-7bb7-11e9-b87e-005056832c45","resourceVersion":"884046","creationTimestamp":"2019-05-21T11:02:05Z","labels":{"MODIFIED_AT":"1558437104","NAME":"cluster-monitoring","OWNER":"TILLER","STATUS":"SUPERSEDED","VERSION":"340"}},"data":{"release":"...
```
Are there any suggestions, how to find the sub component in Rancher allocating the memory?
**Environment information**
- Rancher version: v2.2.4
- Installation option (single install/HA): HA
**Cluster information**
- Cluster type: Imported rke cluster
- Machine specifications (CPU/memory): 6 vCPUs, 16 GB RAM
- Docker version:
```
# docker version
Client:
Version: 18.09.7
API version: 1.39
Go version: go1.10.8
Git commit: 2d0083d
Built: Thu Jun 27 17:56:17 2019
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 18.09.7
API version: 1.39 (minimum version 1.12)
Go version: go1.10.8
Git commit: 2d0083d
Built: Thu Jun 27 17:23:02 2019
OS/Arch: linux/amd64
Experimental: false
``` | 1.0 | Rancher 2 Master gets OOM killed - **What kind of request is this (question/bug/enhancement/feature request): Bug
**Steps to reproduce (least amount of steps as possible):
The rancher master does take about 1.75 GB/s RAM per hour and get killed by the kernel OOM. Only the master is affected, other rancher pods running have a normal memory usage. We already upgraded to 16 GB RAM, but the issue still persists.
We guess it could have been related to cluster-monitoring, as we find data in memory dumps done with GDB. Is the management layer caching cluster-monitoring data?
```
/proc/PID/smaps:
+c084000000-c08c000000 rw-p 00000000 00:00 0
+Size: 131072 kB
+Rss: 131072 kB
+Pss: 131072 kB
+Shared_Clean: 0 kB
+Shared_Dirty: 0 kB
+Private_Clean: 0 kB
+Private_Dirty: 131072 kB
+Referenced: 131072 kB
+Anonymous: 131072 kB
+AnonHugePages: 0 kB
+Shared_Hugetlb: 0 kB
+Private_Hugetlb: 0 kB
+Swap: 0 kB
+SwapPss: 0 kB
+KernelPageSize: 4 kB
+MMUPageSize: 4 kB
+Locked: 0 kB
+VmFlags: rd wr mr mw me ac sd
{"metadata":{"name":"cluster-monitoring.v341","namespace":"cattle-prometheus","selfLink":"/api/v1/namespaces/cattle-prometheus/configmaps/cluster-monitoring.v341","uid":"de760c13-7bb7-11e9-b87e-005056832c45","resourceVersion":"884046","creationTimestamp":"2019-05-21T11:02:05Z","labels":{"MODIFIED_AT":"1558437104","NAME":"cluster-monitoring","OWNER":"TILLER","STATUS":"SUPERSEDED","VERSION":"340"}},"data":{"release":"...
```
Are there any suggestions, how to find the sub component in Rancher allocating the memory?
**Environment information**
- Rancher version: v2.2.4
- Installation option (single install/HA): HA
**Cluster information**
- Cluster type: Imported rke cluster
- Machine specifications (CPU/memory): 6 vCPUs, 16 GB RAM
- Docker version:
```
# docker version
Client:
Version: 18.09.7
API version: 1.39
Go version: go1.10.8
Git commit: 2d0083d
Built: Thu Jun 27 17:56:17 2019
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 18.09.7
API version: 1.39 (minimum version 1.12)
Go version: go1.10.8
Git commit: 2d0083d
Built: Thu Jun 27 17:23:02 2019
OS/Arch: linux/amd64
Experimental: false
``` | non_priority | rancher master gets oom killed what kind of request is this question bug enhancement feature request bug steps to reproduce least amount of steps as possible the rancher master does take about gb s ram per hour and get killed by the kernel oom only the master is affected other rancher pods running have a normal memory usage we already upgraded to gb ram but the issue still persists we guess it could have been related to cluster monitoring as we find data in memory dumps done with gdb is the management layer caching cluster monitoring data proc pid smaps rw p size kb rss kb pss kb shared clean kb shared dirty kb private clean kb private dirty kb referenced kb anonymous kb anonhugepages kb shared hugetlb kb private hugetlb kb swap kb swappss kb kernelpagesize kb mmupagesize kb locked kb vmflags rd wr mr mw me ac sd metadata name cluster monitoring namespace cattle prometheus selflink api namespaces cattle prometheus configmaps cluster monitoring uid resourceversion creationtimestamp labels modified at name cluster monitoring owner tiller status superseded version data release are there any suggestions how to find the sub component in rancher allocating the memory environment information rancher version installation option single install ha ha cluster information cluster type imported rke cluster machine specifications cpu memory vcpus gb ram docker version docker version client version api version go version git commit built thu jun os arch linux experimental false server docker engine community engine version api version minimum version go version git commit built thu jun os arch linux experimental false | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.