Unnamed: 0
int64 0
832k
| id
float64 2.49B
32.1B
| type
stringclasses 1
value | created_at
stringlengths 19
19
| repo
stringlengths 4
112
| repo_url
stringlengths 33
141
| action
stringclasses 3
values | title
stringlengths 1
1.02k
| labels
stringlengths 4
1.54k
| body
stringlengths 1
262k
| index
stringclasses 17
values | text_combine
stringlengths 95
262k
| label
stringclasses 2
values | text
stringlengths 96
252k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
153,921
| 12,168,626,007
|
IssuesEvent
|
2020-04-27 12:59:37
|
WoWManiaUK/Redemption
|
https://api.github.com/repos/WoWManiaUK/Redemption
|
closed
|
[NPC] Blood Prince Council - Crimson Hall doors
|
Fix - Ready to Test
|
**What is Happening:**
ones the raid in ICC kills 1st group of trash mobs on way Crimson Hall and the doors for room of Blood Prince Council open , players can enter room clear trash in it and engage Blood Prince Council to fight what will make doors to enter room close , how ever if the raid wipes on Blood Prince Council fight release spirit and runs back to Crimson Hall they will find doors to enter room where you fight closed, what leads to them needing to make ticket and wait for Gm to open the doors. what leads to waste of Gm time and unhappy players, there is no other way to open the doors
**What Should happen:**
Doors to enter Crimson Hall form upper spire in ICC should open ones whole raid wipes and fight reset
|
1.0
|
[NPC] Blood Prince Council - Crimson Hall doors - **What is Happening:**
ones the raid in ICC kills 1st group of trash mobs on way Crimson Hall and the doors for room of Blood Prince Council open , players can enter room clear trash in it and engage Blood Prince Council to fight what will make doors to enter room close , how ever if the raid wipes on Blood Prince Council fight release spirit and runs back to Crimson Hall they will find doors to enter room where you fight closed, what leads to them needing to make ticket and wait for Gm to open the doors. what leads to waste of Gm time and unhappy players, there is no other way to open the doors
**What Should happen:**
Doors to enter Crimson Hall form upper spire in ICC should open ones whole raid wipes and fight reset
|
test
|
blood prince council crimson hall doors what is happening ones the raid in icc kills group of trash mobs on way crimson hall and the doors for room of blood prince council open players can enter room clear trash in it and engage blood prince council to fight what will make doors to enter room close how ever if the raid wipes on blood prince council fight release spirit and runs back to crimson hall they will find doors to enter room where you fight closed what leads to them needing to make ticket and wait for gm to open the doors what leads to waste of gm time and unhappy players there is no other way to open the doors what should happen doors to enter crimson hall form upper spire in icc should open ones whole raid wipes and fight reset
| 1
|
79,460
| 7,716,456,444
|
IssuesEvent
|
2018-05-23 10:44:20
|
Caphyon/clang-power-tools
|
https://api.github.com/repos/Caphyon/clang-power-tools
|
closed
|
Use Pester for PowerShell unit tests
|
in progress test
|
[Pester](https://github.com/pester/Pester) is de-facto standard unit test framework for writing PowerShell unit tests.
[msbuild_translation_tests.ps1](../blob/master/ClangPowerTools/ClangPowerTools/msbuild_translation_tests.ps1) should be rewritten with the help of this framework.
|
1.0
|
Use Pester for PowerShell unit tests - [Pester](https://github.com/pester/Pester) is de-facto standard unit test framework for writing PowerShell unit tests.
[msbuild_translation_tests.ps1](../blob/master/ClangPowerTools/ClangPowerTools/msbuild_translation_tests.ps1) should be rewritten with the help of this framework.
|
test
|
use pester for powershell unit tests is de facto standard unit test framework for writing powershell unit tests blob master clangpowertools clangpowertools msbuild translation tests should be rewritten with the help of this framework
| 1
|
58,354
| 14,271,303,946
|
IssuesEvent
|
2020-11-21 11:48:20
|
LibreHealthIO/lh-ehr
|
https://api.github.com/repos/LibreHealthIO/lh-ehr
|
reopened
|
A lot of vulnerabilities in OpenEMR disclosed
|
Web Security
|
I found a report with [a decently sized list of vulnerabilities in OpenEMR](https://github.com/zeropwn/vulnerability-reports-and-pocs/blob/master/OpenEMR%20-%20Vulnerability%20Report.pdf) published on May 1<sup>st</sup> of this year.
Not sure if these exist in our code, but we should check.
|
True
|
A lot of vulnerabilities in OpenEMR disclosed - I found a report with [a decently sized list of vulnerabilities in OpenEMR](https://github.com/zeropwn/vulnerability-reports-and-pocs/blob/master/OpenEMR%20-%20Vulnerability%20Report.pdf) published on May 1<sup>st</sup> of this year.
Not sure if these exist in our code, but we should check.
|
non_test
|
a lot of vulnerabilities in openemr disclosed i found a report with published on may st of this year not sure if these exist in our code but we should check
| 0
|
46,919
| 13,056,002,298
|
IssuesEvent
|
2020-07-30 03:21:31
|
icecube-trac/tix2
|
https://api.github.com/repos/icecube-trac/tix2
|
opened
|
[phys-services] Delete I3TRandom (Trac #2137)
|
Incomplete Migration Migrated from Trac combo core defect
|
Migrated from https://code.icecube.wisc.edu/ticket/2137
```json
{
"status": "closed",
"changetime": "2019-02-13T14:14:43",
"description": "nobody uses it",
"reporter": "kjmeagher",
"cc": "",
"resolution": "fixed",
"_ts": "1550067283824229",
"component": "combo core",
"summary": "[phys-services] Delete I3TRandom",
"priority": "normal",
"keywords": "",
"time": "2018-02-14T22:13:51",
"milestone": "",
"owner": "kjmeagher",
"type": "defect"
}
```
|
1.0
|
[phys-services] Delete I3TRandom (Trac #2137) - Migrated from https://code.icecube.wisc.edu/ticket/2137
```json
{
"status": "closed",
"changetime": "2019-02-13T14:14:43",
"description": "nobody uses it",
"reporter": "kjmeagher",
"cc": "",
"resolution": "fixed",
"_ts": "1550067283824229",
"component": "combo core",
"summary": "[phys-services] Delete I3TRandom",
"priority": "normal",
"keywords": "",
"time": "2018-02-14T22:13:51",
"milestone": "",
"owner": "kjmeagher",
"type": "defect"
}
```
|
non_test
|
delete trac migrated from json status closed changetime description nobody uses it reporter kjmeagher cc resolution fixed ts component combo core summary delete priority normal keywords time milestone owner kjmeagher type defect
| 0
|
176,324
| 13,636,121,746
|
IssuesEvent
|
2020-09-25 04:58:08
|
jakeegan/Blink-Controlled-Speech-Synthesizer
|
https://api.github.com/repos/jakeegan/Blink-Controlled-Speech-Synthesizer
|
opened
|
Test word predictor
|
Test
|
Test word predictor on a testing dataset and report accuracy, recall, and precision.
|
1.0
|
Test word predictor - Test word predictor on a testing dataset and report accuracy, recall, and precision.
|
test
|
test word predictor test word predictor on a testing dataset and report accuracy recall and precision
| 1
|
268,907
| 28,932,260,479
|
IssuesEvent
|
2023-05-09 01:06:49
|
developerone12/WebGoat-WhiteSource-Bolt
|
https://api.github.com/repos/developerone12/WebGoat-WhiteSource-Bolt
|
opened
|
CVE-2022-25869 (Medium) detected in angular-1.2.16.js, angular-1.2.16.min.js
|
Mend: dependency security vulnerability
|
## CVE-2022-25869 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>angular-1.2.16.js</b>, <b>angular-1.2.16.min.js</b></p></summary>
<p>
<details><summary><b>angular-1.2.16.js</b></p></summary>
<p>AngularJS is an MVC framework for building web applications. The core features include HTML enhanced with custom component and data-binding capabilities, dependency injection and strong focus on simplicity, testability, maintainability and boiler-plate reduction.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.2.16/angular.js">https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.2.16/angular.js</a></p>
<p>Path to vulnerable library: /src/main/webapp/js/angular/angular.js</p>
<p>
Dependency Hierarchy:
- :x: **angular-1.2.16.js** (Vulnerable Library)
</details>
<details><summary><b>angular-1.2.16.min.js</b></p></summary>
<p>AngularJS is an MVC framework for building web applications. The core features include HTML enhanced with custom component and data-binding capabilities, dependency injection and strong focus on simplicity, testability, maintainability and boiler-plate reduction.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.2.16/angular.min.js">https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.2.16/angular.min.js</a></p>
<p>Path to vulnerable library: /src/main/webapp/js/angular/angular.min.js</p>
<p>
Dependency Hierarchy:
- :x: **angular-1.2.16.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/developerone12/WebGoat-WhiteSource-Bolt/commit/c42e663814e4b88294ff90339ad577ca1afcf531">c42e663814e4b88294ff90339ad577ca1afcf531</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
All versions of package angular are vulnerable to Cross-site Scripting (XSS) due to insecure page caching in the Internet Explorer browser, which allows interpolation of <textarea> elements.
<p>Publish Date: 2022-07-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-25869>CVE-2022-25869</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>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2022-25869 (Medium) detected in angular-1.2.16.js, angular-1.2.16.min.js - ## CVE-2022-25869 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>angular-1.2.16.js</b>, <b>angular-1.2.16.min.js</b></p></summary>
<p>
<details><summary><b>angular-1.2.16.js</b></p></summary>
<p>AngularJS is an MVC framework for building web applications. The core features include HTML enhanced with custom component and data-binding capabilities, dependency injection and strong focus on simplicity, testability, maintainability and boiler-plate reduction.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.2.16/angular.js">https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.2.16/angular.js</a></p>
<p>Path to vulnerable library: /src/main/webapp/js/angular/angular.js</p>
<p>
Dependency Hierarchy:
- :x: **angular-1.2.16.js** (Vulnerable Library)
</details>
<details><summary><b>angular-1.2.16.min.js</b></p></summary>
<p>AngularJS is an MVC framework for building web applications. The core features include HTML enhanced with custom component and data-binding capabilities, dependency injection and strong focus on simplicity, testability, maintainability and boiler-plate reduction.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.2.16/angular.min.js">https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.2.16/angular.min.js</a></p>
<p>Path to vulnerable library: /src/main/webapp/js/angular/angular.min.js</p>
<p>
Dependency Hierarchy:
- :x: **angular-1.2.16.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/developerone12/WebGoat-WhiteSource-Bolt/commit/c42e663814e4b88294ff90339ad577ca1afcf531">c42e663814e4b88294ff90339ad577ca1afcf531</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
All versions of package angular are vulnerable to Cross-site Scripting (XSS) due to insecure page caching in the Internet Explorer browser, which allows interpolation of <textarea> elements.
<p>Publish Date: 2022-07-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-25869>CVE-2022-25869</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>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve medium detected in angular js angular min js cve medium severity vulnerability vulnerable libraries angular js angular min js angular js angularjs is an mvc framework for building web applications the core features include html enhanced with custom component and data binding capabilities dependency injection and strong focus on simplicity testability maintainability and boiler plate reduction library home page a href path to vulnerable library src main webapp js angular angular js dependency hierarchy x angular js vulnerable library angular min js angularjs is an mvc framework for building web applications the core features include html enhanced with custom component and data binding capabilities dependency injection and strong focus on simplicity testability maintainability and boiler plate reduction library home page a href path to vulnerable library src main webapp js angular angular min js dependency hierarchy x angular min js vulnerable library found in head commit a href found in base branch master vulnerability details all versions of package angular are vulnerable to cross site scripting xss due to insecure page caching in the internet explorer browser which allows interpolation of elements 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 step up your open source security game with mend
| 0
|
184,679
| 14,289,809,779
|
IssuesEvent
|
2020-11-23 19:51:47
|
github-vet/rangeclosure-findings
|
https://api.github.com/repos/github-vet/rangeclosure-findings
|
closed
|
blugelabs/bluge: search/searcher/search_match_all_test.go; 34 LoC
|
fresh small test
|
Found a possible issue in [blugelabs/bluge](https://www.github.com/blugelabs/bluge) at [search/searcher/search_match_all_test.go](https://github.com/blugelabs/bluge/blob/c304a6733af6b14a0e57acb8085f7e88bae98560/search/searcher/search_match_all_test.go#L95-L128)
The below snippet of Go code triggered static analysis which searches for goroutines and/or defer statements
which capture loop variables.
[Click here to see the code in its original context.](https://github.com/blugelabs/bluge/blob/c304a6733af6b14a0e57acb8085f7e88bae98560/search/searcher/search_match_all_test.go#L95-L128)
<details>
<summary>Click here to show the 34 line(s) of Go which triggered the analyzer.</summary>
```go
for testIndex, test := range tests {
defer func() {
err := test.searcher.Close()
if err != nil {
t.Fatal(err)
}
}()
ctx := &search.Context{
DocumentMatchPool: search.NewDocumentMatchPool(test.searcher.DocumentMatchPoolSize(), 0),
}
next, err := test.searcher.Next(ctx)
i := 0
for err == nil && next != nil {
if i < len(test.results) {
if next.Number != test.results[i].Number {
t.Errorf("expected result %d to have number %d got %d for test %d", i, test.results[i].Number, next.Number, testIndex)
}
if !scoresCloseEnough(next.Score, test.results[i].Score) {
t.Errorf("expected result %d to have score %v got %v for test %d", i, test.results[i].Score, next.Score, testIndex)
t.Logf("scoring explanation: %s", next.Explanation)
}
}
ctx.DocumentMatchPool.Put(next)
next, err = test.searcher.Next(ctx)
i++
}
if err != nil {
t.Fatalf("error iterating searcher: %v for test %d", err, testIndex)
}
if len(test.results) != i {
t.Errorf("expected %d results got %d for test %d", len(test.results), i, testIndex)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: c304a6733af6b14a0e57acb8085f7e88bae98560
|
1.0
|
blugelabs/bluge: search/searcher/search_match_all_test.go; 34 LoC -
Found a possible issue in [blugelabs/bluge](https://www.github.com/blugelabs/bluge) at [search/searcher/search_match_all_test.go](https://github.com/blugelabs/bluge/blob/c304a6733af6b14a0e57acb8085f7e88bae98560/search/searcher/search_match_all_test.go#L95-L128)
The below snippet of Go code triggered static analysis which searches for goroutines and/or defer statements
which capture loop variables.
[Click here to see the code in its original context.](https://github.com/blugelabs/bluge/blob/c304a6733af6b14a0e57acb8085f7e88bae98560/search/searcher/search_match_all_test.go#L95-L128)
<details>
<summary>Click here to show the 34 line(s) of Go which triggered the analyzer.</summary>
```go
for testIndex, test := range tests {
defer func() {
err := test.searcher.Close()
if err != nil {
t.Fatal(err)
}
}()
ctx := &search.Context{
DocumentMatchPool: search.NewDocumentMatchPool(test.searcher.DocumentMatchPoolSize(), 0),
}
next, err := test.searcher.Next(ctx)
i := 0
for err == nil && next != nil {
if i < len(test.results) {
if next.Number != test.results[i].Number {
t.Errorf("expected result %d to have number %d got %d for test %d", i, test.results[i].Number, next.Number, testIndex)
}
if !scoresCloseEnough(next.Score, test.results[i].Score) {
t.Errorf("expected result %d to have score %v got %v for test %d", i, test.results[i].Score, next.Score, testIndex)
t.Logf("scoring explanation: %s", next.Explanation)
}
}
ctx.DocumentMatchPool.Put(next)
next, err = test.searcher.Next(ctx)
i++
}
if err != nil {
t.Fatalf("error iterating searcher: %v for test %d", err, testIndex)
}
if len(test.results) != i {
t.Errorf("expected %d results got %d for test %d", len(test.results), i, testIndex)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: c304a6733af6b14a0e57acb8085f7e88bae98560
|
test
|
blugelabs bluge search searcher search match all test go loc found a possible issue in at the below snippet of go code triggered static analysis which searches for goroutines and or defer statements which capture loop variables click here to show the line s of go which triggered the analyzer go for testindex test range tests defer func err test searcher close if err nil t fatal err ctx search context documentmatchpool search newdocumentmatchpool test searcher documentmatchpoolsize next err test searcher next ctx i for err nil next nil if i len test results if next number test results number t errorf expected result d to have number d got d for test d i test results number next number testindex if scorescloseenough next score test results score t errorf expected result d to have score v got v for test d i test results score next score testindex t logf scoring explanation s next explanation ctx documentmatchpool put next next err test searcher next ctx i if err nil t fatalf error iterating searcher v for test d err testindex if len test results i t errorf expected d results got d for test d len test results i testindex leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id
| 1
|
413,322
| 12,065,004,892
|
IssuesEvent
|
2020-04-16 09:14:38
|
ShortTechDE/ingenious
|
https://api.github.com/repos/ShortTechDE/ingenious
|
opened
|
Infinite infinite scrolling when link is not plain
|
bug priority
|
An example would be [shorttech.de/#](https://shorttech.de/#). Could be solved with Regex etc.
|
1.0
|
Infinite infinite scrolling when link is not plain - An example would be [shorttech.de/#](https://shorttech.de/#). Could be solved with Regex etc.
|
non_test
|
infinite infinite scrolling when link is not plain an example would be could be solved with regex etc
| 0
|
487,296
| 14,021,814,805
|
IssuesEvent
|
2020-10-29 21:58:38
|
Pemigrade/Acorn
|
https://api.github.com/repos/Pemigrade/Acorn
|
closed
|
Display mute reasons to players who are muted
|
Feature Request High Priority
|
**Brief Description**
<!-- A clear and concise description of what you want to happen. -->
Players should be given the permission node that allows them to see when they are muted, and why.
**Why do you want the feature?**
<!-- The reasons why you want to see the feature implemented. -->
A lot of the time when some players are muted, they are confused and ask a staff member to explain for them what they were muted for. If mute reasons were shown to the player when they are muted, it would reduce confusion and conflict, and staff members wouldn't always have to explain a mute to the player.
**Additional context**
<!-- Add any other context or screenshots about the feature request here. If you're suggesting a plugin, please provide a link to its download page. Most users can ignore this section. -->
|
1.0
|
Display mute reasons to players who are muted - **Brief Description**
<!-- A clear and concise description of what you want to happen. -->
Players should be given the permission node that allows them to see when they are muted, and why.
**Why do you want the feature?**
<!-- The reasons why you want to see the feature implemented. -->
A lot of the time when some players are muted, they are confused and ask a staff member to explain for them what they were muted for. If mute reasons were shown to the player when they are muted, it would reduce confusion and conflict, and staff members wouldn't always have to explain a mute to the player.
**Additional context**
<!-- Add any other context or screenshots about the feature request here. If you're suggesting a plugin, please provide a link to its download page. Most users can ignore this section. -->
|
non_test
|
display mute reasons to players who are muted brief description players should be given the permission node that allows them to see when they are muted and why why do you want the feature a lot of the time when some players are muted they are confused and ask a staff member to explain for them what they were muted for if mute reasons were shown to the player when they are muted it would reduce confusion and conflict and staff members wouldn t always have to explain a mute to the player additional context
| 0
|
301,883
| 26,107,229,187
|
IssuesEvent
|
2022-12-27 14:43:24
|
status-im/status-mobile
|
https://api.github.com/repos/status-im/status-mobile
|
opened
|
No aceessibility label on mention suggest list
|
e2e test blocker
|
# Bug Report
## Problem
No way to locate a particular element
On UI 1.20 it was the part of //*[@content-desc='suggestions-list']
## Acceptance criteria
accessibility id for suggestion list in input field
|
1.0
|
No aceessibility label on mention suggest list - # Bug Report
## Problem
No way to locate a particular element
On UI 1.20 it was the part of //*[@content-desc='suggestions-list']
## Acceptance criteria
accessibility id for suggestion list in input field
|
test
|
no aceessibility label on mention suggest list bug report problem no way to locate a particular element on ui it was the part of acceptance criteria accessibility id for suggestion list in input field
| 1
|
195,806
| 6,918,578,178
|
IssuesEvent
|
2017-11-29 12:44:40
|
htpcBeginner/AtoMiC-ToolKit
|
https://api.github.com/repos/htpcBeginner/AtoMiC-ToolKit
|
closed
|
Feature Request - OpenVPN
|
Enhancement Priority: Low
|
Hi!
I'd like to respectfully request an OpenVPN feature that ties into whatever VPN provider we use - perhaps PIA initially for simplicity. It'd be even cooler if this somehow tied into whatever torrent client we use so that P2P traffic could be encrypted. Thanks!
**** UPDATE From Tom ****
- [X] Added [OpenVPN](https://openvpn.net)
- [X] Added [Private Internet Access VPN DESKTOP Client](https://www.privateinternetaccess.com/pages/downloads)
- [ ] TODO [Private Internet Access VPN HEADLESS Client](https://www.privateinternetaccess.com)
|
1.0
|
Feature Request - OpenVPN - Hi!
I'd like to respectfully request an OpenVPN feature that ties into whatever VPN provider we use - perhaps PIA initially for simplicity. It'd be even cooler if this somehow tied into whatever torrent client we use so that P2P traffic could be encrypted. Thanks!
**** UPDATE From Tom ****
- [X] Added [OpenVPN](https://openvpn.net)
- [X] Added [Private Internet Access VPN DESKTOP Client](https://www.privateinternetaccess.com/pages/downloads)
- [ ] TODO [Private Internet Access VPN HEADLESS Client](https://www.privateinternetaccess.com)
|
non_test
|
feature request openvpn hi i d like to respectfully request an openvpn feature that ties into whatever vpn provider we use perhaps pia initially for simplicity it d be even cooler if this somehow tied into whatever torrent client we use so that traffic could be encrypted thanks update from tom added added todo
| 0
|
537
| 2,511,426,086
|
IssuesEvent
|
2015-01-14 07:36:32
|
OpenConext/OpenConext-dashboard
|
https://api.github.com/repos/OpenConext/OpenConext-dashboard
|
closed
|
Design tweaks
|
Design
|
User feedback reveals some design tweaks:
- Recently used filter is unclear -> Used in last 3 months / Never used is better
- Dropdown list of ISPs is unclear
- Line height can be less to accommodate more content on the apps overview page
- Label 'Added' is unclear. -> Application added to SURFconext (or better)
- Statistics as function in the top row is unclear
- Adding a connect column in the apps overview will improve usage
- The column License is unclear: Is a license present or needed? What about the option unknown or not required.
- Service attributes also on the connect page
|
1.0
|
Design tweaks - User feedback reveals some design tweaks:
- Recently used filter is unclear -> Used in last 3 months / Never used is better
- Dropdown list of ISPs is unclear
- Line height can be less to accommodate more content on the apps overview page
- Label 'Added' is unclear. -> Application added to SURFconext (or better)
- Statistics as function in the top row is unclear
- Adding a connect column in the apps overview will improve usage
- The column License is unclear: Is a license present or needed? What about the option unknown or not required.
- Service attributes also on the connect page
|
non_test
|
design tweaks user feedback reveals some design tweaks recently used filter is unclear used in last months never used is better dropdown list of isps is unclear line height can be less to accommodate more content on the apps overview page label added is unclear application added to surfconext or better statistics as function in the top row is unclear adding a connect column in the apps overview will improve usage the column license is unclear is a license present or needed what about the option unknown or not required service attributes also on the connect page
| 0
|
216,628
| 16,777,665,807
|
IssuesEvent
|
2021-06-15 00:43:46
|
quarkusio/quarkus
|
https://api.github.com/repos/quarkusio/quarkus
|
closed
|
quarkus:dev displays exception (warning) for @Disabled tests
|
area/continuous-testing kind/bug
|
## Describe the bug
The current version `2.0.0.CR3` of `quarkus:dev` displays warnings with exception stacktraces for tests classes that are annotated with `@Disabled`.
## To reproduce
- Have the following test:
```java
@Disabled
public class CoffeeIT {
@Test
void testHello() {
// ...
}
}
```
- run `quarkus:dev` with version `2.0.0.CR3`
- activate output [`o`] and re-run tests [`r`]
Results in:
```
2021-06-10 10:21:55,230 INFO [io.qua.dep.dev.tes.TestSupport] (Aesh InputStream Reader) Test output enabled
2021-06-10 10:22:04,036 INFO [io.qua.dep.dev.RuntimeUpdatesProcessor] (Quarkus Test Watcher - 0) Changed source files detected, recompiling CoffeeIT.java
2021-06-10 10:22:06,112 WARNING [org.jun.pla.lau.cor.TestExecutionListenerRegistry] (Test runner thread) TestExecutionListener [io.quarkus.deployment.dev.testing.JunitTestRunner$3] threw exception for method: executionFinished(TestIdentifier [uniqueId = '[engine:junit-jupiter]', parentId = null, displayName = 'JUnit Jupiter', legacyReportingName = 'JUnit Jupiter', source = null, tags = [], type = CONTAINER], TestExecutionResult [status = SUCCESSFUL, throwable = null]): java.util.NoSuchElementException
at java.base/java.util.concurrent.LinkedBlockingDeque.removeFirst(LinkedBlockingDeque.java:446)
at java.base/java.util.concurrent.LinkedBlockingDeque.pop(LinkedBlockingDeque.java:769)
at io.quarkus.deployment.dev.testing.JunitTestRunner$3.executionFinished(JunitTestRunner.java:282)
at org.junit.platform.launcher.core.TestExecutionListenerRegistry$CompositeTestExecutionListener.lambda$executionFinished$10(TestExecutionListenerRegistry.java:109)
at org.junit.platform.launcher.core.TestExecutionListenerRegistry$CompositeTestExecutionListener$$Lambda$1098/0x0000000014cf1908.accept(Unknown Source)
at org.junit.platform.launcher.core.TestExecutionListenerRegistry.lambda$notifyEach$1(TestExecutionListenerRegistry.java:67)
at org.junit.platform.launcher.core.TestExecutionListenerRegistry$$Lambda$878/0x00000000149e3d30.accept(Unknown Source)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at org.junit.platform.launcher.core.TestExecutionListenerRegistry.notifyEach(TestExecutionListenerRegistry.java:65)
at org.junit.platform.launcher.core.TestExecutionListenerRegistry.access$200(TestExecutionListenerRegistry.java:32)
at org.junit.platform.launcher.core.TestExecutionListenerRegistry$CompositeTestExecutionListener.executionFinished(TestExecutionListenerRegistry.java:108)
at org.junit.platform.launcher.core.ExecutionListenerAdapter.executionFinished(ExecutionListenerAdapter.java:56)
at org.junit.platform.launcher.core.DelegatingEngineExecutionListener.executionFinished(DelegatingEngineExecutionListener.java:46)
at org.junit.platform.launcher.core.OutcomeDelayingEngineExecutionListener.reportEngineOutcome(OutcomeDelayingEngineExecutionListener.java:69)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:109)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:88)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.lambda$execute$0(EngineExecutionOrchestrator.java:54)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator$$Lambda$872/0x00000000149df878.accept(Unknown Source)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.withInterceptedStreams(EngineExecutionOrchestrator.java:67)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:52)
at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:96)
at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:84)
at io.quarkus.deployment.dev.testing.JunitTestRunner.runTests(JunitTestRunner.java:214)
at io.quarkus.deployment.dev.testing.TestRunner.runInternal(TestRunner.java:248)
at io.quarkus.deployment.dev.testing.TestRunner$1.run(TestRunner.java:127)
at java.base/java.lang.Thread.run(Thread.java:853)
```
This is only a warning and has no effect, however we might want to fix it :)
|
1.0
|
quarkus:dev displays exception (warning) for @Disabled tests - ## Describe the bug
The current version `2.0.0.CR3` of `quarkus:dev` displays warnings with exception stacktraces for tests classes that are annotated with `@Disabled`.
## To reproduce
- Have the following test:
```java
@Disabled
public class CoffeeIT {
@Test
void testHello() {
// ...
}
}
```
- run `quarkus:dev` with version `2.0.0.CR3`
- activate output [`o`] and re-run tests [`r`]
Results in:
```
2021-06-10 10:21:55,230 INFO [io.qua.dep.dev.tes.TestSupport] (Aesh InputStream Reader) Test output enabled
2021-06-10 10:22:04,036 INFO [io.qua.dep.dev.RuntimeUpdatesProcessor] (Quarkus Test Watcher - 0) Changed source files detected, recompiling CoffeeIT.java
2021-06-10 10:22:06,112 WARNING [org.jun.pla.lau.cor.TestExecutionListenerRegistry] (Test runner thread) TestExecutionListener [io.quarkus.deployment.dev.testing.JunitTestRunner$3] threw exception for method: executionFinished(TestIdentifier [uniqueId = '[engine:junit-jupiter]', parentId = null, displayName = 'JUnit Jupiter', legacyReportingName = 'JUnit Jupiter', source = null, tags = [], type = CONTAINER], TestExecutionResult [status = SUCCESSFUL, throwable = null]): java.util.NoSuchElementException
at java.base/java.util.concurrent.LinkedBlockingDeque.removeFirst(LinkedBlockingDeque.java:446)
at java.base/java.util.concurrent.LinkedBlockingDeque.pop(LinkedBlockingDeque.java:769)
at io.quarkus.deployment.dev.testing.JunitTestRunner$3.executionFinished(JunitTestRunner.java:282)
at org.junit.platform.launcher.core.TestExecutionListenerRegistry$CompositeTestExecutionListener.lambda$executionFinished$10(TestExecutionListenerRegistry.java:109)
at org.junit.platform.launcher.core.TestExecutionListenerRegistry$CompositeTestExecutionListener$$Lambda$1098/0x0000000014cf1908.accept(Unknown Source)
at org.junit.platform.launcher.core.TestExecutionListenerRegistry.lambda$notifyEach$1(TestExecutionListenerRegistry.java:67)
at org.junit.platform.launcher.core.TestExecutionListenerRegistry$$Lambda$878/0x00000000149e3d30.accept(Unknown Source)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at org.junit.platform.launcher.core.TestExecutionListenerRegistry.notifyEach(TestExecutionListenerRegistry.java:65)
at org.junit.platform.launcher.core.TestExecutionListenerRegistry.access$200(TestExecutionListenerRegistry.java:32)
at org.junit.platform.launcher.core.TestExecutionListenerRegistry$CompositeTestExecutionListener.executionFinished(TestExecutionListenerRegistry.java:108)
at org.junit.platform.launcher.core.ExecutionListenerAdapter.executionFinished(ExecutionListenerAdapter.java:56)
at org.junit.platform.launcher.core.DelegatingEngineExecutionListener.executionFinished(DelegatingEngineExecutionListener.java:46)
at org.junit.platform.launcher.core.OutcomeDelayingEngineExecutionListener.reportEngineOutcome(OutcomeDelayingEngineExecutionListener.java:69)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:109)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:88)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.lambda$execute$0(EngineExecutionOrchestrator.java:54)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator$$Lambda$872/0x00000000149df878.accept(Unknown Source)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.withInterceptedStreams(EngineExecutionOrchestrator.java:67)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:52)
at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:96)
at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:84)
at io.quarkus.deployment.dev.testing.JunitTestRunner.runTests(JunitTestRunner.java:214)
at io.quarkus.deployment.dev.testing.TestRunner.runInternal(TestRunner.java:248)
at io.quarkus.deployment.dev.testing.TestRunner$1.run(TestRunner.java:127)
at java.base/java.lang.Thread.run(Thread.java:853)
```
This is only a warning and has no effect, however we might want to fix it :)
|
test
|
quarkus dev displays exception warning for disabled tests describe the bug the current version of quarkus dev displays warnings with exception stacktraces for tests classes that are annotated with disabled to reproduce have the following test java disabled public class coffeeit test void testhello run quarkus dev with version activate output and re run tests results in info aesh inputstream reader test output enabled info quarkus test watcher changed source files detected recompiling coffeeit java warning test runner thread testexecutionlistener threw exception for method executionfinished testidentifier parentid null displayname junit jupiter legacyreportingname junit jupiter source null tags type container testexecutionresult java util nosuchelementexception at java base java util concurrent linkedblockingdeque removefirst linkedblockingdeque java at java base java util concurrent linkedblockingdeque pop linkedblockingdeque java at io quarkus deployment dev testing junittestrunner executionfinished junittestrunner java at org junit platform launcher core testexecutionlistenerregistry compositetestexecutionlistener lambda executionfinished testexecutionlistenerregistry java at org junit platform launcher core testexecutionlistenerregistry compositetestexecutionlistener lambda accept unknown source at org junit platform launcher core testexecutionlistenerregistry lambda notifyeach testexecutionlistenerregistry java at org junit platform launcher core testexecutionlistenerregistry lambda accept unknown source at java base java util arraylist foreach arraylist java at org junit platform launcher core testexecutionlistenerregistry notifyeach testexecutionlistenerregistry java at org junit platform launcher core testexecutionlistenerregistry access testexecutionlistenerregistry java at org junit platform launcher core testexecutionlistenerregistry compositetestexecutionlistener executionfinished testexecutionlistenerregistry java at org junit platform launcher core executionlisteneradapter executionfinished executionlisteneradapter java at org junit platform launcher core delegatingengineexecutionlistener executionfinished delegatingengineexecutionlistener java at org junit platform launcher core outcomedelayingengineexecutionlistener reportengineoutcome outcomedelayingengineexecutionlistener java at org junit platform launcher core engineexecutionorchestrator execute engineexecutionorchestrator java at org junit platform launcher core engineexecutionorchestrator execute engineexecutionorchestrator java at org junit platform launcher core engineexecutionorchestrator lambda execute engineexecutionorchestrator java at org junit platform launcher core engineexecutionorchestrator lambda accept unknown source at org junit platform launcher core engineexecutionorchestrator withinterceptedstreams engineexecutionorchestrator java at org junit platform launcher core engineexecutionorchestrator execute engineexecutionorchestrator java at org junit platform launcher core defaultlauncher execute defaultlauncher java at org junit platform launcher core defaultlauncher execute defaultlauncher java at io quarkus deployment dev testing junittestrunner runtests junittestrunner java at io quarkus deployment dev testing testrunner runinternal testrunner java at io quarkus deployment dev testing testrunner run testrunner java at java base java lang thread run thread java this is only a warning and has no effect however we might want to fix it
| 1
|
250,876
| 21,367,444,042
|
IssuesEvent
|
2022-04-20 04:21:55
|
Uuvana-Studios/longvinter-windows-client
|
https://api.github.com/repos/Uuvana-Studios/longvinter-windows-client
|
closed
|
Electricity Bug
|
Bug Not Tested
|
**Describe the bug**
Despite fully upgrading house and having a total of 80 energy and allowing 3 turrets. The electricity amount always changes back down to 60 and deactivating a turret as a result.
**Screenshot**
**Desktop (please complete the following information):**
- OS: Windows
- Game Version 1.0.3
- Steam Version 1.0.3
|
1.0
|
Electricity Bug - **Describe the bug**
Despite fully upgrading house and having a total of 80 energy and allowing 3 turrets. The electricity amount always changes back down to 60 and deactivating a turret as a result.
**Screenshot**
**Desktop (please complete the following information):**
- OS: Windows
- Game Version 1.0.3
- Steam Version 1.0.3
|
test
|
electricity bug describe the bug despite fully upgrading house and having a total of energy and allowing turrets the electricity amount always changes back down to and deactivating a turret as a result screenshot desktop please complete the following information os windows game version steam version
| 1
|
275,520
| 23,919,933,213
|
IssuesEvent
|
2022-09-09 15:51:36
|
dtcenter/MET
|
https://api.github.com/repos/dtcenter/MET
|
closed
|
Update the MET Dockerfile to install Python 3.8.6 from source
|
component: testing type: task requestor: METplus Team MET: Python Embedding priority: high
|
## Describe the Task ##
Update the MET Dockerfile to install Python 3.8.6 from source.
See https://vinodpandey.com/how-to-install-python3-on-centos-7/#installing-python-38-on-centos-7 for an example.
If this does not work well, refer to METplus’s use of conda for installing 3.8.6.
As part of this work, a new repository was created - METbaseimage - in order to handle separate versioning for the base image. This task corresponds to work on [METbaseimage Issue #1](https://github.com/dtcenter/METbaseimage/issues/1) and [METbaseimage Issue #3](https://github.com/dtcenter/METbaseimage/issues/3).
### Time Estimate ###
1-3 days of work
### Sub-Issues ###
Consider breaking the task down into sub-issues.
- [ ] *Add a checkbox for each sub-issue here.*
### Relevant Deadlines ###
MET-11.0.0-beta3 (9/14/22)
### Funding Source ###
2702691
## Define the Metadata ##
### Assignee ###
- [x] Select **engineer(s)** or **no engineer** required
- [ ] Select **scientist(s)** or **no scientist** required
### Labels ###
- [x] Select **component(s)**
- [x] Select **priority**
- [x] Select **requestor(s)**
### Projects and Milestone ###
- [x] Select **Repository** and/or **Organization** level **Project(s)** or add **alert: NEED PROJECT ASSIGNMENT** label
- [x] Select **Milestone** as the next official version or **Future Versions**
## Define Related Issue(s) ##
Consider the impact to the other METplus components.
- [x] [METplus](https://github.com/dtcenter/METplus/issues/new/choose), [MET](https://github.com/dtcenter/MET/issues/new/choose), [METdatadb](https://github.com/dtcenter/METdatadb/issues/new/choose), [METviewer](https://github.com/dtcenter/METviewer/issues/new/choose), [METexpress](https://github.com/dtcenter/METexpress/issues/new/choose), [METcalcpy](https://github.com/dtcenter/METcalcpy/issues/new/choose), [METplotpy](https://github.com/dtcenter/METplotpy/issues/new/choose)
## Task Checklist ##
See the [METplus Workflow](https://metplus.readthedocs.io/en/latest/Contributors_Guide/github_workflow.html) for details.
- [x] Complete the issue definition above, including the **Time Estimate** and **Funding Source**.
- [ ] Fork this repository or create a branch of **develop**.
Branch name: `feature_<Issue Number>_<Description>`
- [ ] Complete the development and test your changes.
- [ ] Add/update log messages for easier debugging.
- [ ] Add/update unit tests.
- [ ] Add/update documentation.
- [ ] Push local changes to GitHub.
- [ ] Submit a pull request to merge into **develop**.
Pull request: `feature <Issue Number> <Description>`
- [ ] Define the pull request metadata, as permissions allow.
Select: **Reviewer(s)** and **Linked issues**
Select: **Repository** level development cycle **Project** for the next official release
Select: **Milestone** as the next official version
- [ ] Iterate until the reviewer(s) accept and merge your changes.
- [ ] Delete your fork or branch.
- [ ] Close this issue.
|
1.0
|
Update the MET Dockerfile to install Python 3.8.6 from source - ## Describe the Task ##
Update the MET Dockerfile to install Python 3.8.6 from source.
See https://vinodpandey.com/how-to-install-python3-on-centos-7/#installing-python-38-on-centos-7 for an example.
If this does not work well, refer to METplus’s use of conda for installing 3.8.6.
As part of this work, a new repository was created - METbaseimage - in order to handle separate versioning for the base image. This task corresponds to work on [METbaseimage Issue #1](https://github.com/dtcenter/METbaseimage/issues/1) and [METbaseimage Issue #3](https://github.com/dtcenter/METbaseimage/issues/3).
### Time Estimate ###
1-3 days of work
### Sub-Issues ###
Consider breaking the task down into sub-issues.
- [ ] *Add a checkbox for each sub-issue here.*
### Relevant Deadlines ###
MET-11.0.0-beta3 (9/14/22)
### Funding Source ###
2702691
## Define the Metadata ##
### Assignee ###
- [x] Select **engineer(s)** or **no engineer** required
- [ ] Select **scientist(s)** or **no scientist** required
### Labels ###
- [x] Select **component(s)**
- [x] Select **priority**
- [x] Select **requestor(s)**
### Projects and Milestone ###
- [x] Select **Repository** and/or **Organization** level **Project(s)** or add **alert: NEED PROJECT ASSIGNMENT** label
- [x] Select **Milestone** as the next official version or **Future Versions**
## Define Related Issue(s) ##
Consider the impact to the other METplus components.
- [x] [METplus](https://github.com/dtcenter/METplus/issues/new/choose), [MET](https://github.com/dtcenter/MET/issues/new/choose), [METdatadb](https://github.com/dtcenter/METdatadb/issues/new/choose), [METviewer](https://github.com/dtcenter/METviewer/issues/new/choose), [METexpress](https://github.com/dtcenter/METexpress/issues/new/choose), [METcalcpy](https://github.com/dtcenter/METcalcpy/issues/new/choose), [METplotpy](https://github.com/dtcenter/METplotpy/issues/new/choose)
## Task Checklist ##
See the [METplus Workflow](https://metplus.readthedocs.io/en/latest/Contributors_Guide/github_workflow.html) for details.
- [x] Complete the issue definition above, including the **Time Estimate** and **Funding Source**.
- [ ] Fork this repository or create a branch of **develop**.
Branch name: `feature_<Issue Number>_<Description>`
- [ ] Complete the development and test your changes.
- [ ] Add/update log messages for easier debugging.
- [ ] Add/update unit tests.
- [ ] Add/update documentation.
- [ ] Push local changes to GitHub.
- [ ] Submit a pull request to merge into **develop**.
Pull request: `feature <Issue Number> <Description>`
- [ ] Define the pull request metadata, as permissions allow.
Select: **Reviewer(s)** and **Linked issues**
Select: **Repository** level development cycle **Project** for the next official release
Select: **Milestone** as the next official version
- [ ] Iterate until the reviewer(s) accept and merge your changes.
- [ ] Delete your fork or branch.
- [ ] Close this issue.
|
test
|
update the met dockerfile to install python from source describe the task update the met dockerfile to install python from source see for an example if this does not work well refer to metplus’s use of conda for installing as part of this work a new repository was created metbaseimage in order to handle separate versioning for the base image this task corresponds to work on and time estimate days of work sub issues consider breaking the task down into sub issues add a checkbox for each sub issue here relevant deadlines met funding source define the metadata assignee select engineer s or no engineer required select scientist s or no scientist required labels select component s select priority select requestor s projects and milestone select repository and or organization level project s or add alert need project assignment label select milestone as the next official version or future versions define related issue s consider the impact to the other metplus components task checklist see the for details complete the issue definition above including the time estimate and funding source fork this repository or create a branch of develop branch name feature complete the development and test your changes add update log messages for easier debugging add update unit tests add update documentation push local changes to github submit a pull request to merge into develop pull request feature define the pull request metadata as permissions allow select reviewer s and linked issues select repository level development cycle project for the next official release select milestone as the next official version iterate until the reviewer s accept and merge your changes delete your fork or branch close this issue
| 1
|
123,018
| 10,244,678,505
|
IssuesEvent
|
2019-08-20 11:01:19
|
CARTAvis/carta-backend
|
https://api.github.com/repos/CARTAvis/carta-backend
|
closed
|
spectral profile from a point region is not stoppable
|
backport critical bug ready to test
|
with dev as of July 31, 2019
the backend keeps sending updates of a point region spectral profile even if the user switches to another region.
UPDATE: same for cursor region.
|
1.0
|
spectral profile from a point region is not stoppable - with dev as of July 31, 2019
the backend keeps sending updates of a point region spectral profile even if the user switches to another region.
UPDATE: same for cursor region.
|
test
|
spectral profile from a point region is not stoppable with dev as of july the backend keeps sending updates of a point region spectral profile even if the user switches to another region update same for cursor region
| 1
|
233,171
| 18,952,008,935
|
IssuesEvent
|
2021-11-18 16:02:59
|
gergopokol/renate-od
|
https://api.github.com/repos/gergopokol/renate-od
|
closed
|
Testing implementation for atomic ceiling
|
testing
|
Extend unit testing of AtomicDB to include atomic ceing. Should be implemented after Neutral DB.
|
1.0
|
Testing implementation for atomic ceiling - Extend unit testing of AtomicDB to include atomic ceing. Should be implemented after Neutral DB.
|
test
|
testing implementation for atomic ceiling extend unit testing of atomicdb to include atomic ceing should be implemented after neutral db
| 1
|
448,932
| 31,818,620,123
|
IssuesEvent
|
2023-09-13 23:05:22
|
chromium/subspace
|
https://api.github.com/repos/chromium/subspace
|
opened
|
Subdoc Bugs exposed by libjxl
|
documentation
|
# https://old.lucaversari.it/jpeg_xl_data/docs/JxlColorProfile.html
- Here there's a data member `icc` whose type is `::(unnamed struct at /fast-data/libjxl/lib/include/jxl/cms_interface.h:47:3)`
- The struct fields links don't know the path to the struct's page, and are linking to `.html`
|
1.0
|
Subdoc Bugs exposed by libjxl - # https://old.lucaversari.it/jpeg_xl_data/docs/JxlColorProfile.html
- Here there's a data member `icc` whose type is `::(unnamed struct at /fast-data/libjxl/lib/include/jxl/cms_interface.h:47:3)`
- The struct fields links don't know the path to the struct's page, and are linking to `.html`
|
non_test
|
subdoc bugs exposed by libjxl here there s a data member icc whose type is unnamed struct at fast data libjxl lib include jxl cms interface h the struct fields links don t know the path to the struct s page and are linking to html
| 0
|
7,792
| 3,606,214,736
|
IssuesEvent
|
2016-02-04 10:14:45
|
hpi-swt2/wimi-portal
|
https://api.github.com/repos/hpi-swt2/wimi-portal
|
closed
|
Stundenzettel
|
bug Priorität 1 ready-for-code-review
|
**Aktuell**
1. Wenn ich als Nutzer den Link auf einen Stundenzettel habe, so kann ich diesen einreichen, obwohl es nicht mein eigener ist.
2. Es gibt zwei unterschiedliche Stundenzettel Seiten
3. Fremde Nutzer können meine Stundenzettel sehen
4. Als FG-Beauftragter gibt es eine Auflistung der Hiwis unter 'Research Groups' und hinter jedem Hiwi einen Eintrag 'Show Timesheets'. Dieser macht jedoch aktuell nichts!
https://wimi-portal-dev.herokuapp.com/work_days?month=1&user_id=3&year=2016
Anzeige dieser Seite nicht nötig!
https://wimi-portal-dev.herokuapp.com/work_days?month=12&project=5&user_id=3&year=2015
**Erwartetes Verhalten**
1. Wenn ich einem Projekt (https://wimi-portal-dev.herokuapp.com/projects/5) auf 'Show Working Hours' klicke, dann möchte ich auf eine Seite geleitet werden, die die Arbeitsstunden dieses Projekts auflistet (siehe Bild 1)
2. Eine Auflistung aller Arbeitsstunden in einem Monat ist nicht nötig und kann entfernt werden
3. Es ist nicht möglich fremde Stundenzettel einzusehen/einzuhändigen
3.1. Einsehen ist nur möglich, wenn ich Wimi des Projekts bin in dem der Hiwi ist und der Hiwi den Stundenzettel eingehändigt hat
4. Erstellt man einen neuen Stundenzetteleintrag so soll für das Datum bereits 'Datum von heute' vorausgefüllt sein. Dies kann man aber auch ändern.
5. Wenn bei 'edit' eines Stundenzettels auf 'Back' gedrückt wird, so landet man wieder bei (siehe Bild 1)
6. 'Show Timesheets' wird entfernt (außer Funktionalität davon ist schon irgendwo implementiert, dann korrekt verlinken und alle PO benachrichtigen)
7. Es soll die Summe aller bis jetzt eingetragenen Stunden angezeigt werden. Oberhalb von 'Add Signature' (siehe Bild 1)
|
1.0
|
Stundenzettel - **Aktuell**
1. Wenn ich als Nutzer den Link auf einen Stundenzettel habe, so kann ich diesen einreichen, obwohl es nicht mein eigener ist.
2. Es gibt zwei unterschiedliche Stundenzettel Seiten
3. Fremde Nutzer können meine Stundenzettel sehen
4. Als FG-Beauftragter gibt es eine Auflistung der Hiwis unter 'Research Groups' und hinter jedem Hiwi einen Eintrag 'Show Timesheets'. Dieser macht jedoch aktuell nichts!
https://wimi-portal-dev.herokuapp.com/work_days?month=1&user_id=3&year=2016
Anzeige dieser Seite nicht nötig!
https://wimi-portal-dev.herokuapp.com/work_days?month=12&project=5&user_id=3&year=2015
**Erwartetes Verhalten**
1. Wenn ich einem Projekt (https://wimi-portal-dev.herokuapp.com/projects/5) auf 'Show Working Hours' klicke, dann möchte ich auf eine Seite geleitet werden, die die Arbeitsstunden dieses Projekts auflistet (siehe Bild 1)
2. Eine Auflistung aller Arbeitsstunden in einem Monat ist nicht nötig und kann entfernt werden
3. Es ist nicht möglich fremde Stundenzettel einzusehen/einzuhändigen
3.1. Einsehen ist nur möglich, wenn ich Wimi des Projekts bin in dem der Hiwi ist und der Hiwi den Stundenzettel eingehändigt hat
4. Erstellt man einen neuen Stundenzetteleintrag so soll für das Datum bereits 'Datum von heute' vorausgefüllt sein. Dies kann man aber auch ändern.
5. Wenn bei 'edit' eines Stundenzettels auf 'Back' gedrückt wird, so landet man wieder bei (siehe Bild 1)
6. 'Show Timesheets' wird entfernt (außer Funktionalität davon ist schon irgendwo implementiert, dann korrekt verlinken und alle PO benachrichtigen)
7. Es soll die Summe aller bis jetzt eingetragenen Stunden angezeigt werden. Oberhalb von 'Add Signature' (siehe Bild 1)
|
non_test
|
stundenzettel aktuell wenn ich als nutzer den link auf einen stundenzettel habe so kann ich diesen einreichen obwohl es nicht mein eigener ist es gibt zwei unterschiedliche stundenzettel seiten fremde nutzer können meine stundenzettel sehen als fg beauftragter gibt es eine auflistung der hiwis unter research groups und hinter jedem hiwi einen eintrag show timesheets dieser macht jedoch aktuell nichts anzeige dieser seite nicht nötig erwartetes verhalten wenn ich einem projekt auf show working hours klicke dann möchte ich auf eine seite geleitet werden die die arbeitsstunden dieses projekts auflistet siehe bild eine auflistung aller arbeitsstunden in einem monat ist nicht nötig und kann entfernt werden es ist nicht möglich fremde stundenzettel einzusehen einzuhändigen einsehen ist nur möglich wenn ich wimi des projekts bin in dem der hiwi ist und der hiwi den stundenzettel eingehändigt hat erstellt man einen neuen stundenzetteleintrag so soll für das datum bereits datum von heute vorausgefüllt sein dies kann man aber auch ändern wenn bei edit eines stundenzettels auf back gedrückt wird so landet man wieder bei siehe bild show timesheets wird entfernt außer funktionalität davon ist schon irgendwo implementiert dann korrekt verlinken und alle po benachrichtigen es soll die summe aller bis jetzt eingetragenen stunden angezeigt werden oberhalb von add signature siehe bild
| 0
|
78,423
| 7,641,200,173
|
IssuesEvent
|
2018-05-08 03:19:14
|
Azure/azure-powershell
|
https://api.github.com/repos/Azure/azure-powershell
|
closed
|
Normalize Test Logging
|
Azure PS Team Engineering Test Tsar
|
### Description
Normalize test logging across scenario and unit tests to:
- [ ] Use a consistent logging mechanism across xunit tests
- [ ] Write logs to a separate file per test
- [ ] Do not retain logs for tests that pass
- [ ] Ensure that logs contain full debug messages
### Cost: 8
|
1.0
|
Normalize Test Logging - ### Description
Normalize test logging across scenario and unit tests to:
- [ ] Use a consistent logging mechanism across xunit tests
- [ ] Write logs to a separate file per test
- [ ] Do not retain logs for tests that pass
- [ ] Ensure that logs contain full debug messages
### Cost: 8
|
test
|
normalize test logging description normalize test logging across scenario and unit tests to use a consistent logging mechanism across xunit tests write logs to a separate file per test do not retain logs for tests that pass ensure that logs contain full debug messages cost
| 1
|
43,007
| 17,388,412,767
|
IssuesEvent
|
2021-08-02 01:44:07
|
Azure/azure-libraries-for-java
|
https://api.github.com/repos/Azure/azure-libraries-for-java
|
closed
|
Add VM extension fails as additional PATCH request sent and VM purchase plan cannot be updated
|
ARM Mgmt Service Attention
|
I followed the sample to add a VM extension but this fails with my set up. The reason is reported as failure to update purchase plan. On inspection is appears that a PATCH is sent to update the VM, before the add extension API call. As the PATCH on the VM fails the VM extension call never gets processed.
If however you call this from the CLI the VM PATCH request is not sent and the extension is successful added. It appears the PATCH is sent in case something about the VM changed, which in this case it didn't. But as the backend believes we are trying up update something about the purchase plan the API fails.
The only way I found to work around this is to use reflection to access the ComputeManaged and then use ComputeManager.inner().virtualMachineExtensions() to achieve what I want.
This the REST call that is made, the error received and the body of the request sent.
`Request{method=PATCH, url=https://management.azure.com/subscriptions/XXX/resourceGroups/XXX/providers/Microsoft.Compute/virtualMachines/XXX=2018-06-01, tags={}}`
` The resource '<id>' of type 'Microsoft.Compute/virtualMachines' does not support updates to the purchase plan.`
` {
"plan": {
"name": "hourly",
"publisher": "barracudanetworks",
"product": "barracuda-ng-firewall"
},
"properties": {
"hardwareProfile": {
"vmSize": "Standard_B1ms"
},
"storageProfile": {
"imageReference": {
"publisher": "barracudanetworks",
"offer": "barracuda-ng-firewall",
"sku": "hourly",
"version": "7.2.205701"
},
"osDisk": {
"osType": "Linux",
"name": "XXX",
"caching": "ReadWrite",
"createOption": "FromImage",
"diskSizeGB": 80,
"managedDisk": {
"id": "/subscriptions/XXX/resourceGroups/XXX/providers/Microsoft.Compute/disks/XXX",
"storageAccountType": "Standard_LRS"
}
},
"dataDisks": []
},
"osProfile": {
"computerName": "XXX",
"adminUsername": "will-be-replaced-by-root",
"linuxConfiguration": {
"disablePasswordAuthentication": false
},
"secrets": []
},
"networkProfile": {
"networkInterfaces": [{
"id": "/subscriptions/XXX/resourceGroups/XXX/providers/Microsoft.Network/networkInterfaces/XXX"
}]
}
}
}`
This is the image that I was trying to add the VM extension to:
https://aws.amazon.com/marketplace/pp/B010GKMEKW?qid=1540380168759&sr=0-2&ref_=srh_res_product_title
This is the guide that I followed:
https://github.com/Azure-Samples/compute-java-manage-virtual-machine-using-vm-extensions/blob/master/src/main/java/com/microsoft/azure/management/compute/samples/ManageVirtualMachineExtension.java
CLI output is show below
`az vm extension set --debug --name OmsAgentForLinux --publisher Microsoft.EnterpriseCloud.Monitoring --resource-group XXX --vm-name XXX --protected-settings '{"workspaceKey":"XXX"}' --settings '{"workspaceId":"XXX"}'`
`https://management.azure.com/subscriptions/XXX/resourceGroups/XXX/providers/Microsoft.Compute/virtualMachines/XXX/extensions/OmsAgentForLinux?api-version=2018-10-01`
`{
"location": "ukwest",
"properties": {
"publisher": "Microsoft.EnterpriseCloud.Monitoring",
"type": "OmsAgentForLinux",
"typeHandlerVersion": "1.7",
"autoUpgradeMinorVersion": true,
"settings": {
"workspaceId": "XXX"
},
"protectedSettings": {
"workspaceKey": "XXX"
}
}
}`
|
1.0
|
Add VM extension fails as additional PATCH request sent and VM purchase plan cannot be updated - I followed the sample to add a VM extension but this fails with my set up. The reason is reported as failure to update purchase plan. On inspection is appears that a PATCH is sent to update the VM, before the add extension API call. As the PATCH on the VM fails the VM extension call never gets processed.
If however you call this from the CLI the VM PATCH request is not sent and the extension is successful added. It appears the PATCH is sent in case something about the VM changed, which in this case it didn't. But as the backend believes we are trying up update something about the purchase plan the API fails.
The only way I found to work around this is to use reflection to access the ComputeManaged and then use ComputeManager.inner().virtualMachineExtensions() to achieve what I want.
This the REST call that is made, the error received and the body of the request sent.
`Request{method=PATCH, url=https://management.azure.com/subscriptions/XXX/resourceGroups/XXX/providers/Microsoft.Compute/virtualMachines/XXX=2018-06-01, tags={}}`
` The resource '<id>' of type 'Microsoft.Compute/virtualMachines' does not support updates to the purchase plan.`
` {
"plan": {
"name": "hourly",
"publisher": "barracudanetworks",
"product": "barracuda-ng-firewall"
},
"properties": {
"hardwareProfile": {
"vmSize": "Standard_B1ms"
},
"storageProfile": {
"imageReference": {
"publisher": "barracudanetworks",
"offer": "barracuda-ng-firewall",
"sku": "hourly",
"version": "7.2.205701"
},
"osDisk": {
"osType": "Linux",
"name": "XXX",
"caching": "ReadWrite",
"createOption": "FromImage",
"diskSizeGB": 80,
"managedDisk": {
"id": "/subscriptions/XXX/resourceGroups/XXX/providers/Microsoft.Compute/disks/XXX",
"storageAccountType": "Standard_LRS"
}
},
"dataDisks": []
},
"osProfile": {
"computerName": "XXX",
"adminUsername": "will-be-replaced-by-root",
"linuxConfiguration": {
"disablePasswordAuthentication": false
},
"secrets": []
},
"networkProfile": {
"networkInterfaces": [{
"id": "/subscriptions/XXX/resourceGroups/XXX/providers/Microsoft.Network/networkInterfaces/XXX"
}]
}
}
}`
This is the image that I was trying to add the VM extension to:
https://aws.amazon.com/marketplace/pp/B010GKMEKW?qid=1540380168759&sr=0-2&ref_=srh_res_product_title
This is the guide that I followed:
https://github.com/Azure-Samples/compute-java-manage-virtual-machine-using-vm-extensions/blob/master/src/main/java/com/microsoft/azure/management/compute/samples/ManageVirtualMachineExtension.java
CLI output is show below
`az vm extension set --debug --name OmsAgentForLinux --publisher Microsoft.EnterpriseCloud.Monitoring --resource-group XXX --vm-name XXX --protected-settings '{"workspaceKey":"XXX"}' --settings '{"workspaceId":"XXX"}'`
`https://management.azure.com/subscriptions/XXX/resourceGroups/XXX/providers/Microsoft.Compute/virtualMachines/XXX/extensions/OmsAgentForLinux?api-version=2018-10-01`
`{
"location": "ukwest",
"properties": {
"publisher": "Microsoft.EnterpriseCloud.Monitoring",
"type": "OmsAgentForLinux",
"typeHandlerVersion": "1.7",
"autoUpgradeMinorVersion": true,
"settings": {
"workspaceId": "XXX"
},
"protectedSettings": {
"workspaceKey": "XXX"
}
}
}`
|
non_test
|
add vm extension fails as additional patch request sent and vm purchase plan cannot be updated i followed the sample to add a vm extension but this fails with my set up the reason is reported as failure to update purchase plan on inspection is appears that a patch is sent to update the vm before the add extension api call as the patch on the vm fails the vm extension call never gets processed if however you call this from the cli the vm patch request is not sent and the extension is successful added it appears the patch is sent in case something about the vm changed which in this case it didn t but as the backend believes we are trying up update something about the purchase plan the api fails the only way i found to work around this is to use reflection to access the computemanaged and then use computemanager inner virtualmachineextensions to achieve what i want this the rest call that is made the error received and the body of the request sent request method patch url tags the resource of type microsoft compute virtualmachines does not support updates to the purchase plan plan name hourly publisher barracudanetworks product barracuda ng firewall properties hardwareprofile vmsize standard storageprofile imagereference publisher barracudanetworks offer barracuda ng firewall sku hourly version osdisk ostype linux name xxx caching readwrite createoption fromimage disksizegb manageddisk id subscriptions xxx resourcegroups xxx providers microsoft compute disks xxx storageaccounttype standard lrs datadisks osprofile computername xxx adminusername will be replaced by root linuxconfiguration disablepasswordauthentication false secrets networkprofile networkinterfaces id subscriptions xxx resourcegroups xxx providers microsoft network networkinterfaces xxx this is the image that i was trying to add the vm extension to this is the guide that i followed cli output is show below az vm extension set debug name omsagentforlinux publisher microsoft enterprisecloud monitoring resource group xxx vm name xxx protected settings workspacekey xxx settings workspaceid xxx location ukwest properties publisher microsoft enterprisecloud monitoring type omsagentforlinux typehandlerversion autoupgrademinorversion true settings workspaceid xxx protectedsettings workspacekey xxx
| 0
|
50,150
| 6,062,207,110
|
IssuesEvent
|
2017-06-14 08:51:47
|
mattbearman/lime
|
https://api.github.com/repos/mattbearman/lime
|
opened
|
test
|
question test
|
## [View in BugMuncher Control Panel](https://app.bugmuncher.com/websites/a53d1139bceee3b3730c237aff8217d824ad1ccc/feedback/990b6796b1670dde25216fef582f1425c20f1d7b) ##
## Details ##
**Submitted:** June 14, 2017 08:51
**Category:** Question
**Sender Email:**
**Website:** BugMuncher
**URL:** https://www.bugmuncher.com/
**Operating System:** Linux
**Browser:** Firefox 53.0
**Browser Size:** 1301 x 673
**User Agent:**
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0
**Description:**
## Screenshot ##
1. fuck this
## Browser Plugins ##
Shockwave Flash
|
1.0
|
test - ## [View in BugMuncher Control Panel](https://app.bugmuncher.com/websites/a53d1139bceee3b3730c237aff8217d824ad1ccc/feedback/990b6796b1670dde25216fef582f1425c20f1d7b) ##
## Details ##
**Submitted:** June 14, 2017 08:51
**Category:** Question
**Sender Email:**
**Website:** BugMuncher
**URL:** https://www.bugmuncher.com/
**Operating System:** Linux
**Browser:** Firefox 53.0
**Browser Size:** 1301 x 673
**User Agent:**
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0
**Description:**
## Screenshot ##
1. fuck this
## Browser Plugins ##
Shockwave Flash
|
test
|
test details submitted june category question sender email website bugmuncher url operating system linux browser firefox browser size x user agent mozilla ubuntu linux rv gecko firefox description screenshot fuck this browser plugins shockwave flash
| 1
|
323,627
| 27,741,238,394
|
IssuesEvent
|
2023-03-15 14:25:10
|
ntop/ntopng
|
https://api.github.com/repos/ntop/ntopng
|
closed
|
modification of max char length in Client Server columnt - IPv6 address length cut and replaced with … - for better search possibility
|
Ready to Test
|
We suggest the possibility of changing the width of the Client or Server column width to accommodate the length of IPv6 addresses. So they don't get cut and are searchable by browser search function.
|
1.0
|
modification of max char length in Client Server columnt - IPv6 address length cut and replaced with … - for better search possibility - We suggest the possibility of changing the width of the Client or Server column width to accommodate the length of IPv6 addresses. So they don't get cut and are searchable by browser search function.
|
test
|
modification of max char length in client server columnt address length cut and replaced with … for better search possibility we suggest the possibility of changing the width of the client or server column width to accommodate the length of addresses so they don t get cut and are searchable by browser search function
| 1
|
224,234
| 17,673,411,210
|
IssuesEvent
|
2021-08-23 09:16:53
|
jac-uk/admin
|
https://api.github.com/repos/jac-uk/admin
|
closed
|
'About the role' html editor exposes site to XSS
|
enhancement Pen Test
|
Pen test result:
"It is also possible to store javascript (stored xss) on the job listiing page by using the javascript URL handler. See the following page and click on the click me : https://apply-staging.judicialappointments.digital/vacancy/WmISjsHC7bokFK5qupsC/"
|
1.0
|
'About the role' html editor exposes site to XSS - Pen test result:
"It is also possible to store javascript (stored xss) on the job listiing page by using the javascript URL handler. See the following page and click on the click me : https://apply-staging.judicialappointments.digital/vacancy/WmISjsHC7bokFK5qupsC/"
|
test
|
about the role html editor exposes site to xss pen test result it is also possible to store javascript stored xss on the job listiing page by using the javascript url handler see the following page and click on the click me
| 1
|
205,458
| 15,615,433,489
|
IssuesEvent
|
2021-03-19 19:11:20
|
ThatGuySam/doesitarm
|
https://api.github.com/repos/ThatGuySam/doesitarm
|
closed
|
QGIS, Needs M1 Testing
|
Needs M1 Testing Needs Reported Status New App Request
|
**The official name of the app**
QGIS
**Is there a supported build available on a public/release channel?**
Yes
**Proposed App Status**
Unknown
**Proposed App Category**
Geospatial mapping
**Related Issue Tracker Link or discussion**
https://www.reddit.com/r/QGIS/comments/hgsfv1/qgis_for_apple_silicon_macs/
**An Official App Download Link**
https://qgis.org/en/site/forusers/download.html
**Additional context**
**Screenshot with Activity Monitor(if self reporting)**
|
1.0
|
QGIS, Needs M1 Testing -
**The official name of the app**
QGIS
**Is there a supported build available on a public/release channel?**
Yes
**Proposed App Status**
Unknown
**Proposed App Category**
Geospatial mapping
**Related Issue Tracker Link or discussion**
https://www.reddit.com/r/QGIS/comments/hgsfv1/qgis_for_apple_silicon_macs/
**An Official App Download Link**
https://qgis.org/en/site/forusers/download.html
**Additional context**
**Screenshot with Activity Monitor(if self reporting)**
|
test
|
qgis needs testing the official name of the app qgis is there a supported build available on a public release channel yes proposed app status unknown proposed app category geospatial mapping related issue tracker link or discussion an official app download link additional context screenshot with activity monitor if self reporting
| 1
|
104,587
| 8,982,863,572
|
IssuesEvent
|
2019-01-31 04:12:53
|
danleyb2/helpdesk
|
https://api.github.com/repos/danleyb2/helpdesk
|
opened
|
property creation and support email configuration
|
testing
|
testing / bug fixing of
- [ ] Creation of Properties
- [ ] Support Email Configuration and Editing
|
1.0
|
property creation and support email configuration - testing / bug fixing of
- [ ] Creation of Properties
- [ ] Support Email Configuration and Editing
|
test
|
property creation and support email configuration testing bug fixing of creation of properties support email configuration and editing
| 1
|
49,556
| 13,454,367,221
|
IssuesEvent
|
2020-09-09 03:30:47
|
ErezDasa/RB2
|
https://api.github.com/repos/ErezDasa/RB2
|
opened
|
CVE-2020-5405 (Medium) detected in spring-cloud-config-client-2.0.1.RELEASE.jar
|
security vulnerability
|
## CVE-2020-5405 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-cloud-config-client-2.0.1.RELEASE.jar</b></p></summary>
<p>This project is a Spring configuration client.</p>
<p>Library home page: <a href="https://spring.io">https://spring.io</a></p>
<p>Path to dependency file: /tmp/ws-scm/RB2/infra_github/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/cloud/spring-cloud-config-client/2.0.1.RELEASE/spring-cloud-config-client-2.0.1.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-cloud-starter-config-2.0.3.RELEASE.jar (Root Library)
- :x: **spring-cloud-config-client-2.0.1.RELEASE.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ErezDasa/RB2/commit/76c9fcc27c447880699d2960c8688c59736444af">76c9fcc27c447880699d2960c8688c59736444af</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>
Spring Cloud Config, versions 2.2.x prior to 2.2.2, versions 2.1.x prior to 2.1.7, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead a directory traversal attack.
<p>Publish Date: 2020-03-05
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-5405>CVE-2020-5405</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: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5405">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5405</a></p>
<p>Release Date: 2020-03-05</p>
<p>Fix Resolution: org.springframework.cloud:spring-cloud-config-client:2.1.7.RELEASE,2.2.2.RELEASE;org.springframework.cloud:spring-cloud-config-server:2.1.7.RELEASE,2.2.2.RELEASE</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2020-5405 (Medium) detected in spring-cloud-config-client-2.0.1.RELEASE.jar - ## CVE-2020-5405 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-cloud-config-client-2.0.1.RELEASE.jar</b></p></summary>
<p>This project is a Spring configuration client.</p>
<p>Library home page: <a href="https://spring.io">https://spring.io</a></p>
<p>Path to dependency file: /tmp/ws-scm/RB2/infra_github/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/cloud/spring-cloud-config-client/2.0.1.RELEASE/spring-cloud-config-client-2.0.1.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-cloud-starter-config-2.0.3.RELEASE.jar (Root Library)
- :x: **spring-cloud-config-client-2.0.1.RELEASE.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ErezDasa/RB2/commit/76c9fcc27c447880699d2960c8688c59736444af">76c9fcc27c447880699d2960c8688c59736444af</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>
Spring Cloud Config, versions 2.2.x prior to 2.2.2, versions 2.1.x prior to 2.1.7, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead a directory traversal attack.
<p>Publish Date: 2020-03-05
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-5405>CVE-2020-5405</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: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5405">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5405</a></p>
<p>Release Date: 2020-03-05</p>
<p>Fix Resolution: org.springframework.cloud:spring-cloud-config-client:2.1.7.RELEASE,2.2.2.RELEASE;org.springframework.cloud:spring-cloud-config-server:2.1.7.RELEASE,2.2.2.RELEASE</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve medium detected in spring cloud config client release jar cve medium severity vulnerability vulnerable library spring cloud config client release jar this project is a spring configuration client library home page a href path to dependency file tmp ws scm infra github pom xml path to vulnerable library home wss scanner repository org springframework cloud spring cloud config client release spring cloud config client release jar dependency hierarchy spring cloud starter config release jar root library x spring cloud config client release jar vulnerable library found in head commit a href vulnerability details spring cloud config versions x prior to versions x prior to and older unsupported versions allow applications to serve arbitrary configuration files through the spring cloud config server module a malicious user or attacker can send a request using a specially crafted url that can lead a directory traversal attack 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 high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org springframework cloud spring cloud config client release release org springframework cloud spring cloud config server release release step up your open source security game with whitesource
| 0
|
162,363
| 12,652,753,338
|
IssuesEvent
|
2020-06-17 04:38:17
|
ansible/awx
|
https://api.github.com/repos/ansible/awx
|
closed
|
Unable to Sync Inventory Source - Ansible Tower
|
component:api priority:high state:needs_test type:bug
|
##### ISSUE TYPE
- Bug Report
##### SUMMARY
An inventory configured with inventory source Ansible Tower is unable to sync
##### ENVIRONMENT
* AWX version: 11.2.0
* AWX install method: docker on linux
* Ansible version: 2.9.9
* Operating System: RHEL7
* Web Browser: Chrome
##### STEPS TO REPRODUCE
NOTE: need to have an existing AWX node that hosts the inventory data
1. Pull the latest commit of AWX
2. build a local AWX container image
3. Create an Ansible Tower kind credential to be used in the inventory source
4. Create an inventory with inventory source Ansible Tower, connect to the existing AWX
##### EXPECTED RESULTS
AWX should be able to sync host and groups from inventory source from Ansible Tower
##### ACTUAL RESULTS
```
2.579 INFO Updating inventory 2: FO
3.167 INFO Reading Ansible inventory source: /tmp/awx_11578_f30pyq46/tower.yml
3.171 INFO Using VIRTUAL_ENV: /var/lib/awx/venv/ansible
3.171 INFO Using PATH: /var/lib/awx/venv/ansible/bin:/var/lib/awx/venv/awx/bin:/usr/pgsql-10/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
3.171 INFO Using PYTHONPATH: /var/lib/awx/venv/ansible/lib/python3.6/site-packages:
Traceback (most recent call last):
File "/var/lib/awx/venv/awx/bin/awx-manage", line 8, in <module>
sys.exit(manage())
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/awx/__init__.py", line 154, in manage
execute_from_command_line(sys.argv)
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
utility.execute()
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/django/core/management/__init__.py", line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/django/core/management/base.py", line 323, in run_from_argv
self.execute(*args, **cmd_options)
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/django/core/management/base.py", line 364, in execute
output = self.handle(*args, **options)
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/awx/main/management/commands/inventory_import.py", line 1139, in handle
raise exc
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/awx/main/management/commands/inventory_import.py", line 1029, in handle
venv_path=venv_path, verbosity=self.verbosity).load()
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/awx/main/management/commands/inventory_import.py", line 215, in load
return self.command_to_json(base_args + ['--list'])
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/awx/main/management/commands/inventory_import.py", line 198, in command_to_json
self.method, proc.returncode, stdout, stderr))
RuntimeError: ansible-inventory failed (rc=1) with stdout:
stderr:
ansible-inventory 2.9.9
config file = /etc/ansible/ansible.cfg
configured module search path = ['/var/lib/awx/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python3.6/site-packages/ansible
executable location = /usr/bin/ansible-inventory
python version = 3.6.8 (default, Nov 21 2019, 19:31:34) [GCC 8.3.1 20190507 (Red Hat 8.3.1-4)]
Using /etc/ansible/ansible.cfg as config file
[WARNING]: * Failed to parse /tmp/awx_11578_f30pyq46/tower.yml with auto
plugin: inventory config '/tmp/awx_11578_f30pyq46/tower.yml' specifies unknown
plugin 'awx.awx.tower'
File "/usr/lib/python3.6/site-packages/ansible/inventory/manager.py", line 280, in parse_source
plugin.parse(self._inventory, self._loader, source, cache=cache)
File "/usr/lib/python3.6/site-packages/ansible/plugins/inventory/auto.py", line 53, in parse
raise AnsibleParserError("inventory config '{0}' specifies unknown plugin '{1}'".format(path, plugin_name))
[WARNING]: Unable to parse /tmp/awx_11578_f30pyq46/tower.yml as an inventory
source
ERROR! No inventory was parsed, please check your configuration and options.
```
##### ADDITIONAL INFORMATION
<!-- Include any links to sosreport, database dumps, screenshots or other
information. -->
|
1.0
|
Unable to Sync Inventory Source - Ansible Tower - ##### ISSUE TYPE
- Bug Report
##### SUMMARY
An inventory configured with inventory source Ansible Tower is unable to sync
##### ENVIRONMENT
* AWX version: 11.2.0
* AWX install method: docker on linux
* Ansible version: 2.9.9
* Operating System: RHEL7
* Web Browser: Chrome
##### STEPS TO REPRODUCE
NOTE: need to have an existing AWX node that hosts the inventory data
1. Pull the latest commit of AWX
2. build a local AWX container image
3. Create an Ansible Tower kind credential to be used in the inventory source
4. Create an inventory with inventory source Ansible Tower, connect to the existing AWX
##### EXPECTED RESULTS
AWX should be able to sync host and groups from inventory source from Ansible Tower
##### ACTUAL RESULTS
```
2.579 INFO Updating inventory 2: FO
3.167 INFO Reading Ansible inventory source: /tmp/awx_11578_f30pyq46/tower.yml
3.171 INFO Using VIRTUAL_ENV: /var/lib/awx/venv/ansible
3.171 INFO Using PATH: /var/lib/awx/venv/ansible/bin:/var/lib/awx/venv/awx/bin:/usr/pgsql-10/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
3.171 INFO Using PYTHONPATH: /var/lib/awx/venv/ansible/lib/python3.6/site-packages:
Traceback (most recent call last):
File "/var/lib/awx/venv/awx/bin/awx-manage", line 8, in <module>
sys.exit(manage())
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/awx/__init__.py", line 154, in manage
execute_from_command_line(sys.argv)
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
utility.execute()
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/django/core/management/__init__.py", line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/django/core/management/base.py", line 323, in run_from_argv
self.execute(*args, **cmd_options)
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/django/core/management/base.py", line 364, in execute
output = self.handle(*args, **options)
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/awx/main/management/commands/inventory_import.py", line 1139, in handle
raise exc
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/awx/main/management/commands/inventory_import.py", line 1029, in handle
venv_path=venv_path, verbosity=self.verbosity).load()
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/awx/main/management/commands/inventory_import.py", line 215, in load
return self.command_to_json(base_args + ['--list'])
File "/var/lib/awx/venv/awx/lib/python3.6/site-packages/awx/main/management/commands/inventory_import.py", line 198, in command_to_json
self.method, proc.returncode, stdout, stderr))
RuntimeError: ansible-inventory failed (rc=1) with stdout:
stderr:
ansible-inventory 2.9.9
config file = /etc/ansible/ansible.cfg
configured module search path = ['/var/lib/awx/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python3.6/site-packages/ansible
executable location = /usr/bin/ansible-inventory
python version = 3.6.8 (default, Nov 21 2019, 19:31:34) [GCC 8.3.1 20190507 (Red Hat 8.3.1-4)]
Using /etc/ansible/ansible.cfg as config file
[WARNING]: * Failed to parse /tmp/awx_11578_f30pyq46/tower.yml with auto
plugin: inventory config '/tmp/awx_11578_f30pyq46/tower.yml' specifies unknown
plugin 'awx.awx.tower'
File "/usr/lib/python3.6/site-packages/ansible/inventory/manager.py", line 280, in parse_source
plugin.parse(self._inventory, self._loader, source, cache=cache)
File "/usr/lib/python3.6/site-packages/ansible/plugins/inventory/auto.py", line 53, in parse
raise AnsibleParserError("inventory config '{0}' specifies unknown plugin '{1}'".format(path, plugin_name))
[WARNING]: Unable to parse /tmp/awx_11578_f30pyq46/tower.yml as an inventory
source
ERROR! No inventory was parsed, please check your configuration and options.
```
##### ADDITIONAL INFORMATION
<!-- Include any links to sosreport, database dumps, screenshots or other
information. -->
|
test
|
unable to sync inventory source ansible tower issue type bug report summary an inventory configured with inventory source ansible tower is unable to sync environment awx version awx install method docker on linux ansible version operating system web browser chrome steps to reproduce note need to have an existing awx node that hosts the inventory data pull the latest commit of awx build a local awx container image create an ansible tower kind credential to be used in the inventory source create an inventory with inventory source ansible tower connect to the existing awx expected results awx should be able to sync host and groups from inventory source from ansible tower actual results info updating inventory fo info reading ansible inventory source tmp awx tower yml info using virtual env var lib awx venv ansible info using path var lib awx venv ansible bin var lib awx venv awx bin usr pgsql bin usr local sbin usr local bin usr sbin usr bin sbin bin info using pythonpath var lib awx venv ansible lib site packages traceback most recent call last file var lib awx venv awx bin awx manage line in sys exit manage file var lib awx venv awx lib site packages awx init py line in manage execute from command line sys argv file var lib awx venv awx lib site packages django core management init py line in execute from command line utility execute file var lib awx venv awx lib site packages django core management init py line in execute self fetch command subcommand run from argv self argv file var lib awx venv awx lib site packages django core management base py line in run from argv self execute args cmd options file var lib awx venv awx lib site packages django core management base py line in execute output self handle args options file var lib awx venv awx lib site packages awx main management commands inventory import py line in handle raise exc file var lib awx venv awx lib site packages awx main management commands inventory import py line in handle venv path venv path verbosity self verbosity load file var lib awx venv awx lib site packages awx main management commands inventory import py line in load return self command to json base args file var lib awx venv awx lib site packages awx main management commands inventory import py line in command to json self method proc returncode stdout stderr runtimeerror ansible inventory failed rc with stdout stderr ansible inventory config file etc ansible ansible cfg configured module search path ansible python module location usr lib site packages ansible executable location usr bin ansible inventory python version default nov using etc ansible ansible cfg as config file failed to parse tmp awx tower yml with auto plugin inventory config tmp awx tower yml specifies unknown plugin awx awx tower file usr lib site packages ansible inventory manager py line in parse source plugin parse self inventory self loader source cache cache file usr lib site packages ansible plugins inventory auto py line in parse raise ansibleparsererror inventory config specifies unknown plugin format path plugin name unable to parse tmp awx tower yml as an inventory source error no inventory was parsed please check your configuration and options additional information include any links to sosreport database dumps screenshots or other information
| 1
|
66,629
| 7,008,869,222
|
IssuesEvent
|
2017-12-19 17:01:50
|
elastic/elasticsearch
|
https://api.github.com/repos/elastic/elasticsearch
|
closed
|
[CI] TruncateTranslogIT#testCorruptTranslogTruncation fails
|
:Translog jenkins test
|
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+multijob-darwin-compatibility/365/console.
```
TruncateTranslogIT.testCorruptTranslogTruncation <<< FAILURES!
> Throwable #1: java.lang.AssertionError: all shards should be failed due to a corrupted translog
> at __randomizedtesting.SeedInfo.seed([BE82146795DBD816:2A70E3779E1B3BE]:0)
> at org.elasticsearch.index.translog.TruncateTranslogIT.testCorruptTranslogTruncation(TruncateTranslogIT.java:171)
> at java.lang.Thread.run(Thread.java:748)
1> [2017-11-27T13:32:12,883][INFO ][o.e.n.Node ] [node_s0] stopping ...
1> [2017-11-27T13:32:12,884][INFO ][o.e.n.Node ] [node_s0] stopped
1> [2017-11-27T13:32:12,884][INFO ][o.e.n.Node ] [node_s0] closing ...
1> [2017-11-27T13:32:12,887][INFO ][o.e.n.Node ] [node_s0] closed
```
Unable to reproduce locally:
```
gradle :core:integTest \
-Dtests.seed=BE82146795DBD816 \
-Dtests.class=org.elasticsearch.index.translog.TruncateTranslogIT \
-Dtests.method="testCorruptTranslogTruncation" \
-Dtests.security.manager=true \
-Dtests.locale=sr-ME \
-Dtests.timezone=Africa/Khartoum
```
Log: [consoleText.txt](https://github.com/elastic/elasticsearch/files/1505971/consoleText.txt)
|
1.0
|
[CI] TruncateTranslogIT#testCorruptTranslogTruncation fails - https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+multijob-darwin-compatibility/365/console.
```
TruncateTranslogIT.testCorruptTranslogTruncation <<< FAILURES!
> Throwable #1: java.lang.AssertionError: all shards should be failed due to a corrupted translog
> at __randomizedtesting.SeedInfo.seed([BE82146795DBD816:2A70E3779E1B3BE]:0)
> at org.elasticsearch.index.translog.TruncateTranslogIT.testCorruptTranslogTruncation(TruncateTranslogIT.java:171)
> at java.lang.Thread.run(Thread.java:748)
1> [2017-11-27T13:32:12,883][INFO ][o.e.n.Node ] [node_s0] stopping ...
1> [2017-11-27T13:32:12,884][INFO ][o.e.n.Node ] [node_s0] stopped
1> [2017-11-27T13:32:12,884][INFO ][o.e.n.Node ] [node_s0] closing ...
1> [2017-11-27T13:32:12,887][INFO ][o.e.n.Node ] [node_s0] closed
```
Unable to reproduce locally:
```
gradle :core:integTest \
-Dtests.seed=BE82146795DBD816 \
-Dtests.class=org.elasticsearch.index.translog.TruncateTranslogIT \
-Dtests.method="testCorruptTranslogTruncation" \
-Dtests.security.manager=true \
-Dtests.locale=sr-ME \
-Dtests.timezone=Africa/Khartoum
```
Log: [consoleText.txt](https://github.com/elastic/elasticsearch/files/1505971/consoleText.txt)
|
test
|
truncatetranslogit testcorrupttranslogtruncation fails truncatetranslogit testcorrupttranslogtruncation failures throwable java lang assertionerror all shards should be failed due to a corrupted translog at randomizedtesting seedinfo seed at org elasticsearch index translog truncatetranslogit testcorrupttranslogtruncation truncatetranslogit java at java lang thread run thread java stopping stopped closing closed unable to reproduce locally gradle core integtest dtests seed dtests class org elasticsearch index translog truncatetranslogit dtests method testcorrupttranslogtruncation dtests security manager true dtests locale sr me dtests timezone africa khartoum log
| 1
|
131,008
| 10,678,140,330
|
IssuesEvent
|
2019-10-21 16:41:24
|
kubernetes/sig-release
|
https://api.github.com/repos/kubernetes/sig-release
|
closed
|
Implement release blocking job criteria
|
priority/important-longterm sig/release sig/testing
|
This is an umbrella issue for followup work to https://github.com/kubernetes/sig-release/pull/346
That PR describes aspirational release blocking job criteria. This issue is intended to track the followup work, including:
- ~assignment of owners to all jobs~
- ~descriptions added to all release-master-blocking jobs~
- ~propose the creation of sig-foo-alerts@googlegroups.com or reuse of sig-foo-test-failures for all sigs that need to be responsive to test failures~
- ~the creation of the release-informing dashboard, and moving jobs out of release-master-blocking to that dashboard~
- a bigquery run that generates metrics for jobs currently on the release-master-blocking dashboard
/sig release
this is sig-release policy
/sig testing
this will be assisted by sig-testing tooling
EDIT 2019-07-23: AFAIK metrics is the only thing that remains to close this out
|
1.0
|
Implement release blocking job criteria - This is an umbrella issue for followup work to https://github.com/kubernetes/sig-release/pull/346
That PR describes aspirational release blocking job criteria. This issue is intended to track the followup work, including:
- ~assignment of owners to all jobs~
- ~descriptions added to all release-master-blocking jobs~
- ~propose the creation of sig-foo-alerts@googlegroups.com or reuse of sig-foo-test-failures for all sigs that need to be responsive to test failures~
- ~the creation of the release-informing dashboard, and moving jobs out of release-master-blocking to that dashboard~
- a bigquery run that generates metrics for jobs currently on the release-master-blocking dashboard
/sig release
this is sig-release policy
/sig testing
this will be assisted by sig-testing tooling
EDIT 2019-07-23: AFAIK metrics is the only thing that remains to close this out
|
test
|
implement release blocking job criteria this is an umbrella issue for followup work to that pr describes aspirational release blocking job criteria this issue is intended to track the followup work including assignment of owners to all jobs descriptions added to all release master blocking jobs propose the creation of sig foo alerts googlegroups com or reuse of sig foo test failures for all sigs that need to be responsive to test failures the creation of the release informing dashboard and moving jobs out of release master blocking to that dashboard a bigquery run that generates metrics for jobs currently on the release master blocking dashboard sig release this is sig release policy sig testing this will be assisted by sig testing tooling edit afaik metrics is the only thing that remains to close this out
| 1
|
302,345
| 26,139,958,532
|
IssuesEvent
|
2022-12-29 16:57:39
|
w3c/csswg-drafts
|
https://api.github.com/repos/w3c/csswg-drafts
|
closed
|
[css-pseudo] ::first-line and line-height
|
css-inline-3 css-pseudo-4 Closed Accepted by CSSWG Resolution Needs Testcase (WPT)
|
Specs: https://www.w3.org/TR/css-pseudo-4/#first-line-pseudo
The part of the specs related to the issue raised:
```
The ::first-line pseudo-element’s generated box behaves similar to that of an inline-level element, but with certain restrictions. The following CSS properties apply to a ::first-line pseudo-element:
- all font properties (see [CSS3-FONTS])
- the color and opacity properties (see [CSS3COLOR])
- all background properties (see [CSS3BG])
- any typesetting properties that apply to inline elements (see [CSS3TEXT])
- all text decoration properties (see [CSS3-TEXT-DECOR])
- any inline layout properties that apply to inline elements (see [CSS3LINE])
- any other properties defined to apply to ::first-line by their respective specifications
```
I'm opening this ticket because I've recently used the `::first-line` pseudo element and realized that the `line-height` property for that pseudo element:
- is implemented in a different way in each browser
- doesn't behave as I was expecting (inline VS block)
A short code sample to explain: https://codepen.io/OxyDesign/pen/bc9238f85b871ba1059bc43c953c7a46
(The pseudo element `::first-line` has a smaller `line-height`)
- Chrome (63) applies the reduced `line-height`
- Firefox (58) doesn't apply the reduced `line-height`
- Safari (10) applies the reduced `line-height` but only if the line is not broken with a `<br>`, in that case it doesn't apply the reduced `line-height`
- Internet Explorer (I could only have a quick look at 9, 10 and 11) seems to follow the same logic as Chrome
So that might not be really clear on that point because each browser seems to have its own interpretation.
The second point is that the specs says that it should "behaves similar to that of an inline-level element". I was expecting this to behave as a block-level element. I understand that `::first-letter` should behave as an inline-element as it's part of the text content of a block and is just a part of the line. But `::first-line` is clearly supposed to use the whole width available. Anything that is on this line is included in the `::first-line` definition, therefore should behave like a block in my humble opinion.
The code samples shows that the first line has a smaller `font-size`, so indeed I wanted to apply a smaller `line-height` which is not applied by FF and (partially) by Safari because as an inline-level element it shouldn't. But I think this behavior would make only sense for the `::first-letter` as it's part of a line and we don't want the line to be shrink by the `::first-letter`'s `line-height`. But in the `::first-line` case there is no possibility that any other content would be in the same line without being a part of the `::first-line` pseudo element so that shouldn't behave like that I think.
|
1.0
|
[css-pseudo] ::first-line and line-height - Specs: https://www.w3.org/TR/css-pseudo-4/#first-line-pseudo
The part of the specs related to the issue raised:
```
The ::first-line pseudo-element’s generated box behaves similar to that of an inline-level element, but with certain restrictions. The following CSS properties apply to a ::first-line pseudo-element:
- all font properties (see [CSS3-FONTS])
- the color and opacity properties (see [CSS3COLOR])
- all background properties (see [CSS3BG])
- any typesetting properties that apply to inline elements (see [CSS3TEXT])
- all text decoration properties (see [CSS3-TEXT-DECOR])
- any inline layout properties that apply to inline elements (see [CSS3LINE])
- any other properties defined to apply to ::first-line by their respective specifications
```
I'm opening this ticket because I've recently used the `::first-line` pseudo element and realized that the `line-height` property for that pseudo element:
- is implemented in a different way in each browser
- doesn't behave as I was expecting (inline VS block)
A short code sample to explain: https://codepen.io/OxyDesign/pen/bc9238f85b871ba1059bc43c953c7a46
(The pseudo element `::first-line` has a smaller `line-height`)
- Chrome (63) applies the reduced `line-height`
- Firefox (58) doesn't apply the reduced `line-height`
- Safari (10) applies the reduced `line-height` but only if the line is not broken with a `<br>`, in that case it doesn't apply the reduced `line-height`
- Internet Explorer (I could only have a quick look at 9, 10 and 11) seems to follow the same logic as Chrome
So that might not be really clear on that point because each browser seems to have its own interpretation.
The second point is that the specs says that it should "behaves similar to that of an inline-level element". I was expecting this to behave as a block-level element. I understand that `::first-letter` should behave as an inline-element as it's part of the text content of a block and is just a part of the line. But `::first-line` is clearly supposed to use the whole width available. Anything that is on this line is included in the `::first-line` definition, therefore should behave like a block in my humble opinion.
The code samples shows that the first line has a smaller `font-size`, so indeed I wanted to apply a smaller `line-height` which is not applied by FF and (partially) by Safari because as an inline-level element it shouldn't. But I think this behavior would make only sense for the `::first-letter` as it's part of a line and we don't want the line to be shrink by the `::first-letter`'s `line-height`. But in the `::first-line` case there is no possibility that any other content would be in the same line without being a part of the `::first-line` pseudo element so that shouldn't behave like that I think.
|
test
|
first line and line height specs the part of the specs related to the issue raised the first line pseudo element’s generated box behaves similar to that of an inline level element but with certain restrictions the following css properties apply to a first line pseudo element all font properties see the color and opacity properties see all background properties see any typesetting properties that apply to inline elements see all text decoration properties see any inline layout properties that apply to inline elements see any other properties defined to apply to first line by their respective specifications i m opening this ticket because i ve recently used the first line pseudo element and realized that the line height property for that pseudo element is implemented in a different way in each browser doesn t behave as i was expecting inline vs block a short code sample to explain the pseudo element first line has a smaller line height chrome applies the reduced line height firefox doesn t apply the reduced line height safari applies the reduced line height but only if the line is not broken with a in that case it doesn t apply the reduced line height internet explorer i could only have a quick look at and seems to follow the same logic as chrome so that might not be really clear on that point because each browser seems to have its own interpretation the second point is that the specs says that it should behaves similar to that of an inline level element i was expecting this to behave as a block level element i understand that first letter should behave as an inline element as it s part of the text content of a block and is just a part of the line but first line is clearly supposed to use the whole width available anything that is on this line is included in the first line definition therefore should behave like a block in my humble opinion the code samples shows that the first line has a smaller font size so indeed i wanted to apply a smaller line height which is not applied by ff and partially by safari because as an inline level element it shouldn t but i think this behavior would make only sense for the first letter as it s part of a line and we don t want the line to be shrink by the first letter s line height but in the first line case there is no possibility that any other content would be in the same line without being a part of the first line pseudo element so that shouldn t behave like that i think
| 1
|
82,699
| 10,270,721,819
|
IssuesEvent
|
2019-08-23 12:25:37
|
Automattic/wp-calypso
|
https://api.github.com/repos/Automattic/wp-calypso
|
opened
|
Importer: Handle longer author names better
|
Design Import Site Importer [Type] Enhancement
|
We should find a better way to display super long author names like the one below:
<img width="784" alt="Screenshot 2019-08-23 at 17 49 46" src="https://user-images.githubusercontent.com/18581859/63592380-199afa80-c5cf-11e9-8ab6-7e1ea31ce7dd.png">
<img width="747" alt="Screenshot 2019-08-23 at 17 53 00" src="https://user-images.githubusercontent.com/18581859/63592381-199afa80-c5cf-11e9-9e25-32b5f3de60de.png">
Noticed when reporting https://github.com/Automattic/wp-calypso/issues/35730
|
1.0
|
Importer: Handle longer author names better - We should find a better way to display super long author names like the one below:
<img width="784" alt="Screenshot 2019-08-23 at 17 49 46" src="https://user-images.githubusercontent.com/18581859/63592380-199afa80-c5cf-11e9-8ab6-7e1ea31ce7dd.png">
<img width="747" alt="Screenshot 2019-08-23 at 17 53 00" src="https://user-images.githubusercontent.com/18581859/63592381-199afa80-c5cf-11e9-9e25-32b5f3de60de.png">
Noticed when reporting https://github.com/Automattic/wp-calypso/issues/35730
|
non_test
|
importer handle longer author names better we should find a better way to display super long author names like the one below img width alt screenshot at src img width alt screenshot at src noticed when reporting
| 0
|
156,239
| 12,302,281,375
|
IssuesEvent
|
2020-05-11 16:42:57
|
MathiasMen/FreeFit
|
https://api.github.com/repos/MathiasMen/FreeFit
|
closed
|
ExerciseEditor: Create test to verify deletion of Exercise works
|
Testing
|
Extend `ExerciseEditorValidator`.
|
1.0
|
ExerciseEditor: Create test to verify deletion of Exercise works - Extend `ExerciseEditorValidator`.
|
test
|
exerciseeditor create test to verify deletion of exercise works extend exerciseeditorvalidator
| 1
|
144,536
| 11,623,382,907
|
IssuesEvent
|
2020-02-27 08:50:39
|
elastic/kibana
|
https://api.github.com/repos/elastic/kibana
|
opened
|
Failing test: X-Pack Saved Object API Integration Tests -- security_and_spaces.x-pack/test/saved_object_api_integration/security_and_spaces/apis/find·ts - saved objects security and spaces enabled find user with no access within the space_1 space "after all" hook for "finding a hiddentype should return 403 with forbidden find hiddentype message"
|
failed-test
|
A test failed on a tracked branch
```
Error: [GET http://elastic:changeme@localhost:6151/api/status] request failed (attempt=5/5) -- and ran out of retries
at KbnClientRequester.request (/dev/shm/workspace/kibana/packages/kbn-dev-utils/target/kbn_client/kbn_client_requester.js:99:23)
at process._tickCallback (internal/process/next_tick.js:68:7)
```
First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+master/3248/)
<!-- kibanaCiData = {"failed-test":{"test.class":"X-Pack Saved Object API Integration Tests -- security_and_spaces.x-pack/test/saved_object_api_integration/security_and_spaces/apis/find·ts","test.name":"saved objects security and spaces enabled find user with no access within the space_1 space \"after all\" hook for \"finding a hiddentype should return 403 with forbidden find hiddentype message\"","test.failCount":1}} -->
|
1.0
|
Failing test: X-Pack Saved Object API Integration Tests -- security_and_spaces.x-pack/test/saved_object_api_integration/security_and_spaces/apis/find·ts - saved objects security and spaces enabled find user with no access within the space_1 space "after all" hook for "finding a hiddentype should return 403 with forbidden find hiddentype message" - A test failed on a tracked branch
```
Error: [GET http://elastic:changeme@localhost:6151/api/status] request failed (attempt=5/5) -- and ran out of retries
at KbnClientRequester.request (/dev/shm/workspace/kibana/packages/kbn-dev-utils/target/kbn_client/kbn_client_requester.js:99:23)
at process._tickCallback (internal/process/next_tick.js:68:7)
```
First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+master/3248/)
<!-- kibanaCiData = {"failed-test":{"test.class":"X-Pack Saved Object API Integration Tests -- security_and_spaces.x-pack/test/saved_object_api_integration/security_and_spaces/apis/find·ts","test.name":"saved objects security and spaces enabled find user with no access within the space_1 space \"after all\" hook for \"finding a hiddentype should return 403 with forbidden find hiddentype message\"","test.failCount":1}} -->
|
test
|
failing test x pack saved object api integration tests security and spaces x pack test saved object api integration security and spaces apis find·ts saved objects security and spaces enabled find user with no access within the space space after all hook for finding a hiddentype should return with forbidden find hiddentype message a test failed on a tracked branch error request failed attempt and ran out of retries at kbnclientrequester request dev shm workspace kibana packages kbn dev utils target kbn client kbn client requester js at process tickcallback internal process next tick js first failure
| 1
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.