Unnamed: 0
int64 3
832k
| id
float64 2.49B
32.1B
| type
stringclasses 1
value | created_at
stringlengths 19
19
| repo
stringlengths 7
112
| repo_url
stringlengths 36
141
| action
stringclasses 3
values | title
stringlengths 2
742
| labels
stringlengths 4
431
| body
stringlengths 5
239k
| index
stringclasses 10
values | text_combine
stringlengths 96
240k
| label
stringclasses 2
values | text
stringlengths 96
200k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
20,901
| 16,187,864,456
|
IssuesEvent
|
2021-05-04 01:26:38
|
phseiff/github-flavored-markdown-to-html
|
https://api.github.com/repos/phseiff/github-flavored-markdown-to-html
|
opened
|
Try to remove the warning that occurs when g`gh-md-to-html` is run from the command line.
|
enhancement usability
|
See https://github.com/phseiff/github-flavored-markdown-to-html/issues/39#issuecomment-830831571 and (from the same issue) my explanation https://github.com/phseiff/github-flavored-markdown-to-html/issues/39#issuecomment-830831954.
|
True
|
Try to remove the warning that occurs when g`gh-md-to-html` is run from the command line. - See https://github.com/phseiff/github-flavored-markdown-to-html/issues/39#issuecomment-830831571 and (from the same issue) my explanation https://github.com/phseiff/github-flavored-markdown-to-html/issues/39#issuecomment-830831954.
|
usab
|
try to remove the warning that occurs when g gh md to html is run from the command line see and from the same issue my explanation
| 1
|
73,340
| 15,253,644,706
|
IssuesEvent
|
2021-02-20 08:38:14
|
gsylvie/madness
|
https://api.github.com/repos/gsylvie/madness
|
closed
|
CVE-2017-3523 (High) detected in mysql-connector-java-5.1.6.jar - autoclosed
|
security vulnerability
|
## CVE-2017-3523 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mysql-connector-java-5.1.6.jar</b></p></summary>
<p>MySQL JDBC Type 4 driver</p>
<p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p>
<p>Path to vulnerable library: madness/sub1/target/madness-sub1-2019.02.01/WEB-INF/lib/mysql-connector-java-5.1.6.jar,canner/.m2/repository/mysql/mysql-connector-java/5.1.6/mysql-connector-java-5.1.6.jar</p>
<p>
Dependency Hierarchy:
- :x: **mysql-connector-java-5.1.6.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/gsylvie/madness/commit/032e0bc50a6a45a60e9aed1a5aae9530ad02548a">032e0bc50a6a45a60e9aed1a5aae9530ad02548a</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 5.1.40 and earlier. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Connectors. While the vulnerability is in MySQL Connectors, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 8.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H).
<p>Publish Date: 2017-04-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-3523>CVE-2017-3523</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>8.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html">https://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html</a></p>
<p>Release Date: 2017-04-24</p>
<p>Fix Resolution: 5.1.41</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2017-3523 (High) detected in mysql-connector-java-5.1.6.jar - autoclosed - ## CVE-2017-3523 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mysql-connector-java-5.1.6.jar</b></p></summary>
<p>MySQL JDBC Type 4 driver</p>
<p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p>
<p>Path to vulnerable library: madness/sub1/target/madness-sub1-2019.02.01/WEB-INF/lib/mysql-connector-java-5.1.6.jar,canner/.m2/repository/mysql/mysql-connector-java/5.1.6/mysql-connector-java-5.1.6.jar</p>
<p>
Dependency Hierarchy:
- :x: **mysql-connector-java-5.1.6.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/gsylvie/madness/commit/032e0bc50a6a45a60e9aed1a5aae9530ad02548a">032e0bc50a6a45a60e9aed1a5aae9530ad02548a</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 5.1.40 and earlier. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Connectors. While the vulnerability is in MySQL Connectors, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 8.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H).
<p>Publish Date: 2017-04-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-3523>CVE-2017-3523</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>8.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html">https://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html</a></p>
<p>Release Date: 2017-04-24</p>
<p>Fix Resolution: 5.1.41</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_usab
|
cve high detected in mysql connector java jar autoclosed cve high severity vulnerability vulnerable library mysql connector java jar mysql jdbc type driver library home page a href path to vulnerable library madness target madness web inf lib mysql connector java jar canner repository mysql mysql connector java mysql connector java jar dependency hierarchy x mysql connector java jar vulnerable library found in head commit a href vulnerability details vulnerability in the mysql connectors component of oracle mysql subcomponent connector j supported versions that are affected are and earlier difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise mysql connectors while the vulnerability is in mysql connectors attacks may significantly impact additional products successful attacks of this vulnerability can result in takeover of mysql connectors cvss base score confidentiality integrity and availability impacts cvss vector cvss av n ac h pr l ui n s c c h i h a h publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
13,180
| 8,343,120,821
|
IssuesEvent
|
2018-09-30 00:09:03
|
ekaterinailin/AltaiPony
|
https://api.github.com/repos/ekaterinailin/AltaiPony
|
opened
|
Rewrite the structure description in a short and accessible way for new users.
|
usability
|
<!-- Fill in the information below before opening an issue. -->
#### What needs to be created or improved?
<!-- Provide a clear and concise description of the issue. -->
#### Can you provide an example?
<!-- Provide a link or minimal code snippet that demonstrates the issue. -->
- top level modules - FlareLightCurve, _wrapper_ places
- core functions - flare finding, injection/recovery, analysis
- helper modules - IO, MAST caller
#### What is the goal / expected behaviour?
<!-- Describe the behavior you expected and how it differs from the behavior observed in the example. -->
Regardless of verb-y and descriptive module names the code structure can remain opaque to users or my future self. To prevent this, note your current idea that the code's structure represents.
|
True
|
Rewrite the structure description in a short and accessible way for new users. - <!-- Fill in the information below before opening an issue. -->
#### What needs to be created or improved?
<!-- Provide a clear and concise description of the issue. -->
#### Can you provide an example?
<!-- Provide a link or minimal code snippet that demonstrates the issue. -->
- top level modules - FlareLightCurve, _wrapper_ places
- core functions - flare finding, injection/recovery, analysis
- helper modules - IO, MAST caller
#### What is the goal / expected behaviour?
<!-- Describe the behavior you expected and how it differs from the behavior observed in the example. -->
Regardless of verb-y and descriptive module names the code structure can remain opaque to users or my future self. To prevent this, note your current idea that the code's structure represents.
|
usab
|
rewrite the structure description in a short and accessible way for new users what needs to be created or improved can you provide an example top level modules flarelightcurve wrapper places core functions flare finding injection recovery analysis helper modules io mast caller what is the goal expected behaviour regardless of verb y and descriptive module names the code structure can remain opaque to users or my future self to prevent this note your current idea that the code s structure represents
| 1
|
8,373
| 5,636,992,025
|
IssuesEvent
|
2017-04-06 07:55:13
|
zaproxy/zaproxy
|
https://api.github.com/repos/zaproxy/zaproxy
|
closed
|
Enhancement: Additional Global Exclude default patterns
|
enhancement Usability
|
Food for thought ... re: <sub>https://github.com/zaproxy/zaproxy/blob/efce236ddf6f89516de6cd0592e22372149e0e05/src/org/zaproxy/zap/extension/globalexcludeurl/GlobalExcludeURLParam.java#L63</sub>
- [x] `^https?://detectportal\.firefox\.com.*$` Firefox mechanism for detecting captive portals.
- [x] `^https?://www\.google-analytics\.com.*$` Google analytics....nuff said.
- [x] `^https?://ciscobinary\.openh264\.org.*$` Firefox codec download (https://support.mozilla.org/t5/Firefox/Where-is-a-check-that-http-ciscobinary-openh264-org-openh264-is/m-p/1316497#M1005892)
- [x] `^https?://fonts.*$` This might be too generic, I built it broadly after seeing fonts.googleapis.com and fonts.gstatic.com used...
|
True
|
Enhancement: Additional Global Exclude default patterns - Food for thought ... re: <sub>https://github.com/zaproxy/zaproxy/blob/efce236ddf6f89516de6cd0592e22372149e0e05/src/org/zaproxy/zap/extension/globalexcludeurl/GlobalExcludeURLParam.java#L63</sub>
- [x] `^https?://detectportal\.firefox\.com.*$` Firefox mechanism for detecting captive portals.
- [x] `^https?://www\.google-analytics\.com.*$` Google analytics....nuff said.
- [x] `^https?://ciscobinary\.openh264\.org.*$` Firefox codec download (https://support.mozilla.org/t5/Firefox/Where-is-a-check-that-http-ciscobinary-openh264-org-openh264-is/m-p/1316497#M1005892)
- [x] `^https?://fonts.*$` This might be too generic, I built it broadly after seeing fonts.googleapis.com and fonts.gstatic.com used...
|
usab
|
enhancement additional global exclude default patterns food for thought re https detectportal firefox com firefox mechanism for detecting captive portals https www google analytics com google analytics nuff said https ciscobinary org firefox codec download https fonts this might be too generic i built it broadly after seeing fonts googleapis com and fonts gstatic com used
| 1
|
209,536
| 7,176,995,979
|
IssuesEvent
|
2018-01-31 12:02:39
|
fusetools/fuselibs-public
|
https://api.github.com/repos/fusetools/fuselibs-public
|
closed
|
Attempted to detach child that is not attached to us
|
Priority: High Severity: Bug
|
In my [Dice app](https://github.com/mortoray/dice) I can predictably get the below error with these steps:
1. Add New Set Twice (button at bottom)
2. Delete Second set (swipe left, press Dleete)
3. Delete another set
```
Error: Fuse.Scripting.ScriptException: Uncaught Error: Internal error: Attempted to detach child that is not attached to us
Name: Error: Internal error: Attempted to detach child that is not attached to us
File name: FuseJS/Internal/zone.js
Line number: 196
Script stack trace: Error: Internal error: Attempted to detach child that is not attached to us
at removeAsParentFrom (FuseJS/Internal/Model.js:320:12)
at removeRange (FuseJS/Internal/Model.js:441:5)
at Object.meta.diff (FuseJS/Internal/Model.js:246:7)
at update (FuseJS/Internal/Model.js:392:15)
at Object.meta.diff (FuseJS/Internal/Model.js:266:6)
at FuseJS/Internal/Model.js:212:11
at ZoneDelegate.invokeTask (FuseJS/Internal/zone.js:425:31)
at Zone.runTask (FuseJS/Internal/zone.js:192:47)
at ZoneTask.invokeTask (FuseJS/Internal/zone.js:499:34)
at ZoneTask.invoke (FuseJS/Internal/zone.js:488:48)
```
I'll see if I can find a smaller reproduction.
High priority because it's a common use-case involving only basic behavior.
|
1.0
|
Attempted to detach child that is not attached to us - In my [Dice app](https://github.com/mortoray/dice) I can predictably get the below error with these steps:
1. Add New Set Twice (button at bottom)
2. Delete Second set (swipe left, press Dleete)
3. Delete another set
```
Error: Fuse.Scripting.ScriptException: Uncaught Error: Internal error: Attempted to detach child that is not attached to us
Name: Error: Internal error: Attempted to detach child that is not attached to us
File name: FuseJS/Internal/zone.js
Line number: 196
Script stack trace: Error: Internal error: Attempted to detach child that is not attached to us
at removeAsParentFrom (FuseJS/Internal/Model.js:320:12)
at removeRange (FuseJS/Internal/Model.js:441:5)
at Object.meta.diff (FuseJS/Internal/Model.js:246:7)
at update (FuseJS/Internal/Model.js:392:15)
at Object.meta.diff (FuseJS/Internal/Model.js:266:6)
at FuseJS/Internal/Model.js:212:11
at ZoneDelegate.invokeTask (FuseJS/Internal/zone.js:425:31)
at Zone.runTask (FuseJS/Internal/zone.js:192:47)
at ZoneTask.invokeTask (FuseJS/Internal/zone.js:499:34)
at ZoneTask.invoke (FuseJS/Internal/zone.js:488:48)
```
I'll see if I can find a smaller reproduction.
High priority because it's a common use-case involving only basic behavior.
|
non_usab
|
attempted to detach child that is not attached to us in my i can predictably get the below error with these steps add new set twice button at bottom delete second set swipe left press dleete delete another set error fuse scripting scriptexception uncaught error internal error attempted to detach child that is not attached to us name error internal error attempted to detach child that is not attached to us file name fusejs internal zone js line number script stack trace error internal error attempted to detach child that is not attached to us at removeasparentfrom fusejs internal model js at removerange fusejs internal model js at object meta diff fusejs internal model js at update fusejs internal model js at object meta diff fusejs internal model js at fusejs internal model js at zonedelegate invoketask fusejs internal zone js at zone runtask fusejs internal zone js at zonetask invoketask fusejs internal zone js at zonetask invoke fusejs internal zone js i ll see if i can find a smaller reproduction high priority because it s a common use case involving only basic behavior
| 0
|
401,142
| 11,786,268,547
|
IssuesEvent
|
2020-03-17 11:56:36
|
vector-im/riot-web
|
https://api.github.com/repos/vector-im/riot-web
|
closed
|
Hide video and phone call buttons in composer when config option set
|
release-blocker type:voip 🔔 Priority 🔔
|
No changes by default. We would support a new config.json option that would hide the video and phone call buttons for situations where it is more confusing than helpful.
|
1.0
|
Hide video and phone call buttons in composer when config option set - No changes by default. We would support a new config.json option that would hide the video and phone call buttons for situations where it is more confusing than helpful.
|
non_usab
|
hide video and phone call buttons in composer when config option set no changes by default we would support a new config json option that would hide the video and phone call buttons for situations where it is more confusing than helpful
| 0
|
234,257
| 25,810,786,865
|
IssuesEvent
|
2022-12-11 20:48:11
|
argoproj/argo-cd
|
https://api.github.com/repos/argoproj/argo-cd
|
closed
|
"Deny sources" for Projects
|
enhancement security
|
# Summary
Now that we have "deny destinations" on Projects (#9652), it would be natural for this to be extended to application sources as well.
# Motivation
We have a use case where we have a quite restricted `AppProject`, which only has a restricted number of repos and destinations which it is allowed to use. The dual of this is that we have a more liberal `AppProject` where we now use deny destinations, but it'd also be nice to add restrictions on which repos are _not_ allowed to be used.
# Proposal
In order to be consistent with the deny destinations feature, we'd also allow sources to be prefixed with `!`, which would negate the source value if it has been matched. The implementation would pretty much look like this:
```go
func (proj AppProject) IsSourcePermitted(src ApplicationSource) bool {
srcNormalized := git.NormalizeGitURL(src.RepoURL)
var normalized string
anySourceMatched := false
noDenySourcesMatched := true
for _, repoURL := range proj.Spec.SourceRepos {
if isDenyPattern(repoURL) {
normalized = "!" + git.NormalizeGitURL(strings.TrimPrefix("!", repoURL))
} else {
normalized = git.NormalizeGitURL(repoURL)
}
matched := globMatch(normalized, srcNormalized, true, '/')
if matched {
anySourceMatched = true
} else if !matched && isDenyPattern(normalized) {
noDenySourcesMatched = false
}
}
return anySourceMatched && noDenySourcesMatched
}
```
As with deny destinations we would check that if there are any sources that are matched _and_ check that there are no deny sources matched.
|
True
|
"Deny sources" for Projects - # Summary
Now that we have "deny destinations" on Projects (#9652), it would be natural for this to be extended to application sources as well.
# Motivation
We have a use case where we have a quite restricted `AppProject`, which only has a restricted number of repos and destinations which it is allowed to use. The dual of this is that we have a more liberal `AppProject` where we now use deny destinations, but it'd also be nice to add restrictions on which repos are _not_ allowed to be used.
# Proposal
In order to be consistent with the deny destinations feature, we'd also allow sources to be prefixed with `!`, which would negate the source value if it has been matched. The implementation would pretty much look like this:
```go
func (proj AppProject) IsSourcePermitted(src ApplicationSource) bool {
srcNormalized := git.NormalizeGitURL(src.RepoURL)
var normalized string
anySourceMatched := false
noDenySourcesMatched := true
for _, repoURL := range proj.Spec.SourceRepos {
if isDenyPattern(repoURL) {
normalized = "!" + git.NormalizeGitURL(strings.TrimPrefix("!", repoURL))
} else {
normalized = git.NormalizeGitURL(repoURL)
}
matched := globMatch(normalized, srcNormalized, true, '/')
if matched {
anySourceMatched = true
} else if !matched && isDenyPattern(normalized) {
noDenySourcesMatched = false
}
}
return anySourceMatched && noDenySourcesMatched
}
```
As with deny destinations we would check that if there are any sources that are matched _and_ check that there are no deny sources matched.
|
non_usab
|
deny sources for projects summary now that we have deny destinations on projects it would be natural for this to be extended to application sources as well motivation we have a use case where we have a quite restricted appproject which only has a restricted number of repos and destinations which it is allowed to use the dual of this is that we have a more liberal appproject where we now use deny destinations but it d also be nice to add restrictions on which repos are not allowed to be used proposal in order to be consistent with the deny destinations feature we d also allow sources to be prefixed with which would negate the source value if it has been matched the implementation would pretty much look like this go func proj appproject issourcepermitted src applicationsource bool srcnormalized git normalizegiturl src repourl var normalized string anysourcematched false nodenysourcesmatched true for repourl range proj spec sourcerepos if isdenypattern repourl normalized git normalizegiturl strings trimprefix repourl else normalized git normalizegiturl repourl matched globmatch normalized srcnormalized true if matched anysourcematched true else if matched isdenypattern normalized nodenysourcesmatched false return anysourcematched nodenysourcesmatched as with deny destinations we would check that if there are any sources that are matched and check that there are no deny sources matched
| 0
|
10,682
| 6,875,259,750
|
IssuesEvent
|
2017-11-19 11:49:53
|
webanno/webanno
|
https://api.github.com/repos/webanno/webanno
|
closed
|
Bulk import leads to bulk messages
|
enhancement usability
|
Bulk import leads to bulk messages. these do not go away when changing tab and hide everything after.
Browser: Chrome
Versions: 3.3.x and SNAPSHOT
Tested by: @ChrisBieTUDA
|
True
|
Bulk import leads to bulk messages -
Bulk import leads to bulk messages. these do not go away when changing tab and hide everything after.
Browser: Chrome
Versions: 3.3.x and SNAPSHOT
Tested by: @ChrisBieTUDA
|
usab
|
bulk import leads to bulk messages bulk import leads to bulk messages these do not go away when changing tab and hide everything after browser chrome versions x and snapshot tested by chrisbietuda
| 1
|
673,939
| 23,034,492,892
|
IssuesEvent
|
2022-07-22 17:06:30
|
apexcharts/apexcharts.js
|
https://api.github.com/repos/apexcharts/apexcharts.js
|
closed
|
column width bug when colors are functions
|
bug high-priority
|
# Bug report
## Codepen
https://codepen.io/RomRider/pen/NWbNbdO
## Explanation
- What is the behavior you expect?
When using color functions to determine the color of a column vs using a plain color string, only the color should change.
In the codepen:
--> top chart: using color functions, width is weird
--> bottom chart: using plain color, width is normal
- What is happening instead?
When using plain color, the columns widths are fine, when using color functions, the width of each bar gets reduced
- What error message are you getting?
None
|
1.0
|
column width bug when colors are functions - # Bug report
## Codepen
https://codepen.io/RomRider/pen/NWbNbdO
## Explanation
- What is the behavior you expect?
When using color functions to determine the color of a column vs using a plain color string, only the color should change.
In the codepen:
--> top chart: using color functions, width is weird
--> bottom chart: using plain color, width is normal
- What is happening instead?
When using plain color, the columns widths are fine, when using color functions, the width of each bar gets reduced
- What error message are you getting?
None
|
non_usab
|
column width bug when colors are functions bug report codepen explanation what is the behavior you expect when using color functions to determine the color of a column vs using a plain color string only the color should change in the codepen top chart using color functions width is weird bottom chart using plain color width is normal what is happening instead when using plain color the columns widths are fine when using color functions the width of each bar gets reduced what error message are you getting none
| 0
|
143,112
| 19,142,917,626
|
IssuesEvent
|
2021-12-02 02:20:00
|
arohablue/skill-india-backend
|
https://api.github.com/repos/arohablue/skill-india-backend
|
opened
|
CVE-2020-10969 (High) detected in jackson-databind-2.9.8.jar
|
security vulnerability
|
## CVE-2020-10969 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.8.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /skill-india-backend/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.8/jackson-databind-2.9.8.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.1.2.RELEASE.jar (Root Library)
- spring-boot-starter-json-2.1.2.RELEASE.jar
- :x: **jackson-databind-2.9.8.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to javax.swing.JEditorPane.
<p>Publish Date: 2020-03-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-10969>CVE-2020-10969</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>8.8</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: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10969">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10969</a></p>
<p>Release Date: 2020-03-26</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.8.11.6;com.fasterxml.jackson.core:jackson-databind:2.7.9.7</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-10969 (High) detected in jackson-databind-2.9.8.jar - ## CVE-2020-10969 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.8.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /skill-india-backend/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.8/jackson-databind-2.9.8.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.1.2.RELEASE.jar (Root Library)
- spring-boot-starter-json-2.1.2.RELEASE.jar
- :x: **jackson-databind-2.9.8.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to javax.swing.JEditorPane.
<p>Publish Date: 2020-03-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-10969>CVE-2020-10969</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>8.8</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: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10969">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10969</a></p>
<p>Release Date: 2020-03-26</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.8.11.6;com.fasterxml.jackson.core:jackson-databind:2.7.9.7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_usab
|
cve high detected in jackson databind jar cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file skill india backend pom xml path to vulnerable library root repository com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy spring boot starter web release jar root library spring boot starter json release jar x jackson databind jar vulnerable library vulnerability details fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to javax swing jeditorpane 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 high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution com fasterxml jackson core jackson databind com fasterxml jackson core jackson databind step up your open source security game with whitesource
| 0
|
12,058
| 7,661,700,051
|
IssuesEvent
|
2018-05-11 15:01:31
|
rhoneyager/libicedb
|
https://api.github.com/repos/rhoneyager/libicedb
|
opened
|
Negative dipole coordinates
|
Usability
|
At the moment the code only accepts positive integers as dipole coordinates (uint64_t). When parsing shapefiles if a negative coordinate -x is encountered this is automatically transformed to x
I have a lot of shapefiles centered around the origin which then includes negative coordinates.
Are there good reasons to not assume signed integers as dipole coordinates?
|
True
|
Negative dipole coordinates - At the moment the code only accepts positive integers as dipole coordinates (uint64_t). When parsing shapefiles if a negative coordinate -x is encountered this is automatically transformed to x
I have a lot of shapefiles centered around the origin which then includes negative coordinates.
Are there good reasons to not assume signed integers as dipole coordinates?
|
usab
|
negative dipole coordinates at the moment the code only accepts positive integers as dipole coordinates t when parsing shapefiles if a negative coordinate x is encountered this is automatically transformed to x i have a lot of shapefiles centered around the origin which then includes negative coordinates are there good reasons to not assume signed integers as dipole coordinates
| 1
|
25,138
| 24,782,501,835
|
IssuesEvent
|
2022-10-24 06:58:26
|
eclipse/dirigible
|
https://api.github.com/repos/eclipse/dirigible
|
opened
|
[Templates] Integrate Email Templates
|
enhancement API usability component-template edm component-resources
|
Integrate enhanced email templates like Sendwithus in Dirigible:
- https://github.com/sendwithus/templates
Applicable for use cases of BPMN, EDM, API level or in samples:
- https://www.dirigible.io/api/documents/pdf
```javascript
const pdfDocuments = require("documents/v4/pdf");
let data = {
title: "Lorem Ipsum",
description: "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vivamus lacinia fermentum magna, sit amet accumsan felis auctor ac.",
columns: [{
name: "Id",
key: "id"
}, {
name: "First Name",
key: "firstName",
}, {
name: "Last Name",
key: "lastName"
}, {
name: "Age",
key: "age"
}],
rows: [{
id: 1001,
firstName: "John",
lastName: "Doe",
age: 29
}, {
id: 1002,
firstName: "Jane",
lastName: "Doe",
age: 26
}]
};
let pdf = pdfDocuments.generateTable(data);
```
|
True
|
[Templates] Integrate Email Templates - Integrate enhanced email templates like Sendwithus in Dirigible:
- https://github.com/sendwithus/templates
Applicable for use cases of BPMN, EDM, API level or in samples:
- https://www.dirigible.io/api/documents/pdf
```javascript
const pdfDocuments = require("documents/v4/pdf");
let data = {
title: "Lorem Ipsum",
description: "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vivamus lacinia fermentum magna, sit amet accumsan felis auctor ac.",
columns: [{
name: "Id",
key: "id"
}, {
name: "First Name",
key: "firstName",
}, {
name: "Last Name",
key: "lastName"
}, {
name: "Age",
key: "age"
}],
rows: [{
id: 1001,
firstName: "John",
lastName: "Doe",
age: 29
}, {
id: 1002,
firstName: "Jane",
lastName: "Doe",
age: 26
}]
};
let pdf = pdfDocuments.generateTable(data);
```
|
usab
|
integrate email templates integrate enhanced email templates like sendwithus in dirigible applicable for use cases of bpmn edm api level or in samples javascript const pdfdocuments require documents pdf let data title lorem ipsum description lorem ipsum dolor sit amet consectetur adipiscing elit vivamus lacinia fermentum magna sit amet accumsan felis auctor ac columns name id key id name first name key firstname name last name key lastname name age key age rows id firstname john lastname doe age id firstname jane lastname doe age let pdf pdfdocuments generatetable data
| 1
|
20,240
| 15,172,241,381
|
IssuesEvent
|
2021-02-13 08:00:27
|
microsoft/win32metadata
|
https://api.github.com/repos/microsoft/win32metadata
|
closed
|
Typedefs appear to be lost in the translation
|
usability
|
Hey all,
I was looking at the Win32 metadata in ILSpy, and the first thing that jumped at me is that many typedefs are missing from the new representation. To give just one example among many others: `MsiSetPropertyW`' is defined in the headers as:
```c
UINT WINAPI MsiSetPropertyW(MSIHANDLE hInstall,
LPCWSTR szName, // property identifier, case-sensitive
LPCWSTR szValue); // property value, null to undefine property
```
But in the WinMD file, it is defined as:
```cs
[DllImport("msi", ExactSpelling = true)]
public unsafe static extern uint MsiSetPropertyW(uint hInstall, [Const][NativeTypeInfo(UnmanagedType.LPWStr, IsNullTerminated = true)] ushort* szName, [Const][NativeTypeInfo(UnmanagedType.LPWStr, IsNullTerminated = true)] ushort* szValue);
```
Notice that hInstall is defined as simply being an `uint`. The typedefs here gives some nice information about the provenance of the handle, and could in theory be used to generate wrappers that wrap the uint into a struct to provide RAII semantics for instance.
|
True
|
Typedefs appear to be lost in the translation - Hey all,
I was looking at the Win32 metadata in ILSpy, and the first thing that jumped at me is that many typedefs are missing from the new representation. To give just one example among many others: `MsiSetPropertyW`' is defined in the headers as:
```c
UINT WINAPI MsiSetPropertyW(MSIHANDLE hInstall,
LPCWSTR szName, // property identifier, case-sensitive
LPCWSTR szValue); // property value, null to undefine property
```
But in the WinMD file, it is defined as:
```cs
[DllImport("msi", ExactSpelling = true)]
public unsafe static extern uint MsiSetPropertyW(uint hInstall, [Const][NativeTypeInfo(UnmanagedType.LPWStr, IsNullTerminated = true)] ushort* szName, [Const][NativeTypeInfo(UnmanagedType.LPWStr, IsNullTerminated = true)] ushort* szValue);
```
Notice that hInstall is defined as simply being an `uint`. The typedefs here gives some nice information about the provenance of the handle, and could in theory be used to generate wrappers that wrap the uint into a struct to provide RAII semantics for instance.
|
usab
|
typedefs appear to be lost in the translation hey all i was looking at the metadata in ilspy and the first thing that jumped at me is that many typedefs are missing from the new representation to give just one example among many others msisetpropertyw is defined in the headers as c uint winapi msisetpropertyw msihandle hinstall lpcwstr szname property identifier case sensitive lpcwstr szvalue property value null to undefine property but in the winmd file it is defined as cs public unsafe static extern uint msisetpropertyw uint hinstall ushort szname ushort szvalue notice that hinstall is defined as simply being an uint the typedefs here gives some nice information about the provenance of the handle and could in theory be used to generate wrappers that wrap the uint into a struct to provide raii semantics for instance
| 1
|
3,465
| 3,462,118,217
|
IssuesEvent
|
2015-12-20 17:23:56
|
tgstation/-tg-station
|
https://api.github.com/repos/tgstation/-tg-station
|
closed
|
Ventcrawling through pumps makes it impossible to see the atmos pipes you can move through
|
Bug Usability
|
Repro:
- Play as drone (or any other ventcrawling creature
- Head for atmos and crawl through any of the pumps
- Be unable to see where you can go, unless you enter a vent again
|
True
|
Ventcrawling through pumps makes it impossible to see the atmos pipes you can move through - Repro:
- Play as drone (or any other ventcrawling creature
- Head for atmos and crawl through any of the pumps
- Be unable to see where you can go, unless you enter a vent again
|
usab
|
ventcrawling through pumps makes it impossible to see the atmos pipes you can move through repro play as drone or any other ventcrawling creature head for atmos and crawl through any of the pumps be unable to see where you can go unless you enter a vent again
| 1
|
2,483
| 3,079,347,700
|
IssuesEvent
|
2015-08-21 15:46:01
|
piwik/piwik
|
https://api.github.com/repos/piwik/piwik
|
closed
|
core:archive output is sometimes too verbose eg. "0 visits in last last260 weeks,"
|
c: Usability
|
Our goal is to make Piwik the easiest possible to use and manage. This includes our console commands which should output messages that make sense to everyone.
Recently we've made several improvements to the `core:archive` command messages in #7723 #7536 #8214 and in this issue we'll make the output a little better.
Currently it looks like this:
```
INFO CoreConsole[2014-12-15 23:18:29] [9369d] Archived website id = 14, period = week, 0 visits in last last260 weeks, 0 visits this week, Time elapsed: 15.551s
INFO CoreConsole[2014-12-15 23:18:35] [9369d] Archived website id = 14, period = month, 0 visits in last last52 months,
```
I suggest we simply remove the part ` visits in last last260 weeks, ` / `0 visits in last last52 months,` as it is not useful, and is confusing to some users. This small change was requested by Piwik PRO team.
|
True
|
core:archive output is sometimes too verbose eg. "0 visits in last last260 weeks," - Our goal is to make Piwik the easiest possible to use and manage. This includes our console commands which should output messages that make sense to everyone.
Recently we've made several improvements to the `core:archive` command messages in #7723 #7536 #8214 and in this issue we'll make the output a little better.
Currently it looks like this:
```
INFO CoreConsole[2014-12-15 23:18:29] [9369d] Archived website id = 14, period = week, 0 visits in last last260 weeks, 0 visits this week, Time elapsed: 15.551s
INFO CoreConsole[2014-12-15 23:18:35] [9369d] Archived website id = 14, period = month, 0 visits in last last52 months,
```
I suggest we simply remove the part ` visits in last last260 weeks, ` / `0 visits in last last52 months,` as it is not useful, and is confusing to some users. This small change was requested by Piwik PRO team.
|
usab
|
core archive output is sometimes too verbose eg visits in last weeks our goal is to make piwik the easiest possible to use and manage this includes our console commands which should output messages that make sense to everyone recently we ve made several improvements to the core archive command messages in and in this issue we ll make the output a little better currently it looks like this info coreconsole archived website id period week visits in last weeks visits this week time elapsed info coreconsole archived website id period month visits in last months i suggest we simply remove the part visits in last weeks visits in last months as it is not useful and is confusing to some users this small change was requested by piwik pro team
| 1
|
1,495
| 2,862,962,623
|
IssuesEvent
|
2015-06-04 09:08:52
|
MISP/MISP
|
https://api.github.com/repos/MISP/MISP
|
closed
|
Freetext import tool - deduplicate parsed IOCs
|
enhancement usability
|
When importing a long list of IOCs, or copy/pasting text from a report, sometimes the same IOCs is presented at different places.
It would be really nice if the freetext import tool could deduplicate the list of parsed imported results before presenting it to the user for editing before creating attributes in the event.
|
True
|
Freetext import tool - deduplicate parsed IOCs - When importing a long list of IOCs, or copy/pasting text from a report, sometimes the same IOCs is presented at different places.
It would be really nice if the freetext import tool could deduplicate the list of parsed imported results before presenting it to the user for editing before creating attributes in the event.
|
usab
|
freetext import tool deduplicate parsed iocs when importing a long list of iocs or copy pasting text from a report sometimes the same iocs is presented at different places it would be really nice if the freetext import tool could deduplicate the list of parsed imported results before presenting it to the user for editing before creating attributes in the event
| 1
|
24,187
| 23,457,365,801
|
IssuesEvent
|
2022-08-16 10:02:34
|
WordPress/gutenberg
|
https://api.github.com/repos/WordPress/gutenberg
|
opened
|
Synced blocks: Define them as such in the Inspector
|
[Feature] Reusable Blocks [Block] Template Part
|
Related to https://github.com/WordPress/gutenberg/issues/42482 and https://github.com/WordPress/gutenberg/issues/32163.
When you select a template part or reusable block, it might be nice to clarify their global / synced nature – and perhaps outline usage – in the Inspector.
|
True
|
Synced blocks: Define them as such in the Inspector - Related to https://github.com/WordPress/gutenberg/issues/42482 and https://github.com/WordPress/gutenberg/issues/32163.
When you select a template part or reusable block, it might be nice to clarify their global / synced nature – and perhaps outline usage – in the Inspector.
|
usab
|
synced blocks define them as such in the inspector related to and when you select a template part or reusable block it might be nice to clarify their global synced nature – and perhaps outline usage – in the inspector
| 1
|
21,468
| 17,112,367,925
|
IssuesEvent
|
2021-07-10 15:43:07
|
lutzhamel/asteroid
|
https://api.github.com/repos/lutzhamel/asteroid
|
opened
|
File I/O
|
enhancement usability
|
Currently, Asteroid lacks any file input/output functionality.
Asteroids base IO module, io.ast, only provides methods for writing to stdout, reading from stdin, and reading/writing from the console.
|
True
|
File I/O - Currently, Asteroid lacks any file input/output functionality.
Asteroids base IO module, io.ast, only provides methods for writing to stdout, reading from stdin, and reading/writing from the console.
|
usab
|
file i o currently asteroid lacks any file input output functionality asteroids base io module io ast only provides methods for writing to stdout reading from stdin and reading writing from the console
| 1
|
27,553
| 29,510,549,690
|
IssuesEvent
|
2023-06-03 21:53:05
|
tailscale/tailscale
|
https://api.github.com/repos/tailscale/tailscale
|
closed
|
Tailscale hangs indefinitely on misbehaving DNS
|
L1 Very few P2 Aggravating T5 Usability bug
|
### What is the issue?
Sometimes when I try to go log into tailscale, I get this weird behaviour where running `sudo tailscale up` freezes. Seems like the login flow goes ok until `control: creating new noise client` comes up and then fails with `Received error: register request: Post "https://controlplane.tailscale.com/machine/register": connection attempts aborted by context: context deadline exceeded`
See logs below
```Oct 28 13:51:27 carbon tailscaled[7554]: ipnserver: conn2: connection from userid 0; root has access
Oct 28 13:51:27 carbon tailscaled[7554]: Start
Oct 28 13:51:27 carbon tailscaled[7554]: control: client.Shutdown()
Oct 28 13:51:27 carbon tailscaled[7554]: control: client.Shutdown: inSendStatus=0
Oct 28 13:51:27 carbon tailscaled[7554]: control: mapRoutine: quit
Oct 28 13:51:27 carbon tailscaled[7554]: control: Client.Shutdown done.
Oct 28 13:51:27 carbon tailscaled[7554]: using backend prefs for "_daemon": Prefs{ra=false dns=true want=true routes=[] nf=on Persist=nil}
Oct 28 13:51:27 carbon tailscaled[7554]: Backend: logs: be:495a217121ba33adf5c90d17c7138fb21263e9d8d9900b113a00357307310882 fe:
Oct 28 13:51:27 carbon tailscaled[7554]: Switching ipn state NoState -> NeedsLogin (WantRunning=true, nm=false)
Oct 28 13:51:27 carbon tailscaled[7554]: blockEngineUpdates(true)
Oct 28 13:51:27 carbon tailscaled[7554]: Reconfig(down): no changes made to Engine config
Oct 28 13:51:27 carbon tailscaled[7554]: StartLoginInteractive: url=false
Oct 28 13:51:27 carbon tailscaled[7554]: control: client.Login(false, 2)
Oct 28 13:51:27 carbon tailscaled[7554]: control: LoginInteractive -> regen=true
Oct 28 13:51:27 carbon tailscaled[7554]: control: doLogin(regen=true, hasUrl=false)
Oct 28 13:51:37 carbon tailscaled[7554]: trying bootstrapDNS("derp12c.tailscale.com", "149.28.119.105") for "controlplane.tailscale.com" ...
Oct 28 13:51:37 carbon tailscaled[7554]: bootstrapDNS("derp12c.tailscale.com", "149.28.119.105") for "controlplane.tailscale.com" = [2a05:d014:386:202:24dd:46aa:f98e:9997 2a05:d014:386:203:b7ba:b7d4:9703:6f8a 2a05:d014:386:202:a3e1:5be6:cbb1:1ac9 2a05:d014:386:201:7200:6340:b22f:7df6 2a05:d014:386:203:4535:c15c:9ab:8258 2a05:d014:386:202:6dd4:fc68:35ae:2b80 18.193.143.177 18.156.90.224 18.193.255.254 3.121.104.141 52.29.8.43 18.157.173.201]
Oct 28 13:51:37 carbon tailscaled[7554]: control: control server key from https://controlplane.tailscale.com: ts2021=[fSeS+], legacy=[nlFWp]
Oct 28 13:51:37 carbon tailscaled[7554]: control: Generating a new nodekey.
Oct 28 13:51:37 carbon tailscaled[7554]: control: RegisterReq: onode= node=[at8y+] fup=false
Oct 28 13:51:37 carbon tailscaled[7554]: control: creating new noise client
Oct 28 13:51:47 carbon tailscaled[7554]: Received error: register request: Post "https://controlplane.tailscale.com/machine/register": connection attempts aborted by context: context deadline exceeded
Oct 28 13:51:47 carbon tailscaled[7554]: trying bootstrapDNS("derp1c.tailscale.com", "104.248.8.210") for "controlplane.tailscale.com" ...
Oct 28 13:51:47 carbon tailscaled[7554]: trying bootstrapDNS("derp1c.tailscale.com", "104.248.8.210") for "controlplane.tailscale.com" ...
Oct 28 13:51:47 carbon tailscaled[7554]: control: LoginInteractive -> regen=true
Oct 28 13:51:47 carbon tailscaled[7554]: control: doLogin(regen=true, hasUrl=false)
Oct 28 13:51:47 carbon tailscaled[7554]: control: Generating a new nodekey.
Oct 28 13:51:47 carbon tailscaled[7554]: control: RegisterReq: onode= node=[v3v4A] fup=false
Oct 28 13:51:48 carbon tailscaled[7554]: bootstrapDNS("derp1c.tailscale.com", "104.248.8.210") for "controlplane.tailscale.com" = [2a05:d014:386:202:6dd4:fc68:35ae:2b80 2a05:d014:386:203:b7ba:b7d4:9703:6f8a 2a05:d014:386:201:7200:6340:b22f:7df6 2a05:d014:386:202:24dd:46aa:f98e:9997 2a05:d014:386:202:a3e1:5be6:cbb1:1ac9 2a05:d014:386:203:4535:c15c:9ab:8258 18.156.90.224 18.193.255.254 52.29.8.43 3.121.104.141 18.157.173.201 18.193.143.177]
Oct 28 13:51:48 carbon tailscaled[7554]: bootstrapDNS("derp1c.tailscale.com", "104.248.8.210") for "controlplane.tailscale.com" = [2a05:d014:386:202:6dd4:fc68:35ae:2b80 2a05:d014:386:203:b7ba:b7d4:9703:6f8a 2a05:d014:386:201:7200:6340:b22f:7df6 2a05:d014:386:202:24dd:46aa:f98e:9997 2a05:d014:386:202:a3e1:5be6:cbb1:1ac9 2a05:d014:386:203:4535:c15c:9ab:8258 18.156.90.224 18.193.255.254 52.29.8.43 3.121.104.141 18.157.173.201 18.193.143.177]
Oct 28 13:51:57 carbon tailscaled[7554]: Received error: register request: Post "https://controlplane.tailscale.com/machine/register": connection attempts aborted by context: context deadline exceeded
Oct 28 13:51:57 carbon tailscaled[7554]: trying bootstrapDNS("derp11.tailscale.com", "18.230.97.74") for "controlplane.tailscale.com" ...
Oct 28 13:51:57 carbon tailscaled[7554]: trying bootstrapDNS("derp4e.tailscale.com", "134.122.74.153") for "controlplane.tailscale.com" ...
Oct 28 13:51:57 carbon tailscaled[7554]: control: LoginInteractive -> regen=true
Oct 28 13:51:57 carbon tailscaled[7554]: control: doLogin(regen=true, hasUrl=false)
Oct 28 13:51:57 carbon tailscaled[7554]: control: Generating a new nodekey.
Oct 28 13:51:57 carbon tailscaled[7554]: control: RegisterReq: onode= node=[p2yph] fup=false
Oct 28 13:51:57 carbon tailscaled[7554]: bootstrapDNS("derp4e.tailscale.com", "134.122.74.153") for "controlplane.tailscale.com" = [2a05:d014:386:202:6dd4:fc68:35ae:2b80 2a05:d014:386:202:a3e1:5be6:cbb1:1ac9 2a05:d014:386:202:24dd:46aa:f98e:9997 2a05:d014:386:203:4535:c15c:9ab:8258 2a05:d014:386:201:7200:6340:b22f:7df6 2a05:d014:386:203:b7ba:b7d4:9703:6f8a 18.193.255.254 18.157.173.201 52.29.8.43 3.121.104.141 18.156.90.224 18.193.143.177]
Oct 28 13:51:58 carbon tailscaled[7554]: bootstrapDNS("derp11.tailscale.com", "18.230.97.74") for "controlplane.tailscale.com" = [2a05:d014:386:202:24dd:46aa:f98e:9997 2a05:d014:386:202:6dd4:fc68:35ae:2b80 2a05:d014:386:203:4535:c15c:9ab:8258 2a05:d014:386:201:7200:6340:b22f:7df6 2a05:d014:386:203:b7ba:b7d4:9703:6f8a 2a05:d014:386:202:a3e1:5be6:cbb1:1ac9 18.193.255.254 18.156.90.224 3.121.104.141 18.193.143.177 18.157.173.201 52.29.8.43]
Oct 28 13:52:07 carbon tailscaled[7554]: Received error: register request: Post "https://controlplane.tailscale.com/machine/register": connection attempts aborted by context: context deadline exceeded
```
### Steps to reproduce
Run `tailscale down` or `tailscale logout` and try to login again
I have tried resetting the tailscale client and reinstalling the package. I have also cleared `/var/lib/tailscale/` manually to get rid of old state
### Are there any recent changes that introduced the issue?
No, this behaviour seems completely random
### OS
Linux
### OS version
Arch Linux kernel 6.0.2-arch
### Tailscale version
1.32.1
### Bug report
BUG-495a217121ba33adf5c90d17c7138fb21263e9d8d9900b113a00357307310882-20221028105730Z-fb4af2b507a9d037
|
True
|
Tailscale hangs indefinitely on misbehaving DNS - ### What is the issue?
Sometimes when I try to go log into tailscale, I get this weird behaviour where running `sudo tailscale up` freezes. Seems like the login flow goes ok until `control: creating new noise client` comes up and then fails with `Received error: register request: Post "https://controlplane.tailscale.com/machine/register": connection attempts aborted by context: context deadline exceeded`
See logs below
```Oct 28 13:51:27 carbon tailscaled[7554]: ipnserver: conn2: connection from userid 0; root has access
Oct 28 13:51:27 carbon tailscaled[7554]: Start
Oct 28 13:51:27 carbon tailscaled[7554]: control: client.Shutdown()
Oct 28 13:51:27 carbon tailscaled[7554]: control: client.Shutdown: inSendStatus=0
Oct 28 13:51:27 carbon tailscaled[7554]: control: mapRoutine: quit
Oct 28 13:51:27 carbon tailscaled[7554]: control: Client.Shutdown done.
Oct 28 13:51:27 carbon tailscaled[7554]: using backend prefs for "_daemon": Prefs{ra=false dns=true want=true routes=[] nf=on Persist=nil}
Oct 28 13:51:27 carbon tailscaled[7554]: Backend: logs: be:495a217121ba33adf5c90d17c7138fb21263e9d8d9900b113a00357307310882 fe:
Oct 28 13:51:27 carbon tailscaled[7554]: Switching ipn state NoState -> NeedsLogin (WantRunning=true, nm=false)
Oct 28 13:51:27 carbon tailscaled[7554]: blockEngineUpdates(true)
Oct 28 13:51:27 carbon tailscaled[7554]: Reconfig(down): no changes made to Engine config
Oct 28 13:51:27 carbon tailscaled[7554]: StartLoginInteractive: url=false
Oct 28 13:51:27 carbon tailscaled[7554]: control: client.Login(false, 2)
Oct 28 13:51:27 carbon tailscaled[7554]: control: LoginInteractive -> regen=true
Oct 28 13:51:27 carbon tailscaled[7554]: control: doLogin(regen=true, hasUrl=false)
Oct 28 13:51:37 carbon tailscaled[7554]: trying bootstrapDNS("derp12c.tailscale.com", "149.28.119.105") for "controlplane.tailscale.com" ...
Oct 28 13:51:37 carbon tailscaled[7554]: bootstrapDNS("derp12c.tailscale.com", "149.28.119.105") for "controlplane.tailscale.com" = [2a05:d014:386:202:24dd:46aa:f98e:9997 2a05:d014:386:203:b7ba:b7d4:9703:6f8a 2a05:d014:386:202:a3e1:5be6:cbb1:1ac9 2a05:d014:386:201:7200:6340:b22f:7df6 2a05:d014:386:203:4535:c15c:9ab:8258 2a05:d014:386:202:6dd4:fc68:35ae:2b80 18.193.143.177 18.156.90.224 18.193.255.254 3.121.104.141 52.29.8.43 18.157.173.201]
Oct 28 13:51:37 carbon tailscaled[7554]: control: control server key from https://controlplane.tailscale.com: ts2021=[fSeS+], legacy=[nlFWp]
Oct 28 13:51:37 carbon tailscaled[7554]: control: Generating a new nodekey.
Oct 28 13:51:37 carbon tailscaled[7554]: control: RegisterReq: onode= node=[at8y+] fup=false
Oct 28 13:51:37 carbon tailscaled[7554]: control: creating new noise client
Oct 28 13:51:47 carbon tailscaled[7554]: Received error: register request: Post "https://controlplane.tailscale.com/machine/register": connection attempts aborted by context: context deadline exceeded
Oct 28 13:51:47 carbon tailscaled[7554]: trying bootstrapDNS("derp1c.tailscale.com", "104.248.8.210") for "controlplane.tailscale.com" ...
Oct 28 13:51:47 carbon tailscaled[7554]: trying bootstrapDNS("derp1c.tailscale.com", "104.248.8.210") for "controlplane.tailscale.com" ...
Oct 28 13:51:47 carbon tailscaled[7554]: control: LoginInteractive -> regen=true
Oct 28 13:51:47 carbon tailscaled[7554]: control: doLogin(regen=true, hasUrl=false)
Oct 28 13:51:47 carbon tailscaled[7554]: control: Generating a new nodekey.
Oct 28 13:51:47 carbon tailscaled[7554]: control: RegisterReq: onode= node=[v3v4A] fup=false
Oct 28 13:51:48 carbon tailscaled[7554]: bootstrapDNS("derp1c.tailscale.com", "104.248.8.210") for "controlplane.tailscale.com" = [2a05:d014:386:202:6dd4:fc68:35ae:2b80 2a05:d014:386:203:b7ba:b7d4:9703:6f8a 2a05:d014:386:201:7200:6340:b22f:7df6 2a05:d014:386:202:24dd:46aa:f98e:9997 2a05:d014:386:202:a3e1:5be6:cbb1:1ac9 2a05:d014:386:203:4535:c15c:9ab:8258 18.156.90.224 18.193.255.254 52.29.8.43 3.121.104.141 18.157.173.201 18.193.143.177]
Oct 28 13:51:48 carbon tailscaled[7554]: bootstrapDNS("derp1c.tailscale.com", "104.248.8.210") for "controlplane.tailscale.com" = [2a05:d014:386:202:6dd4:fc68:35ae:2b80 2a05:d014:386:203:b7ba:b7d4:9703:6f8a 2a05:d014:386:201:7200:6340:b22f:7df6 2a05:d014:386:202:24dd:46aa:f98e:9997 2a05:d014:386:202:a3e1:5be6:cbb1:1ac9 2a05:d014:386:203:4535:c15c:9ab:8258 18.156.90.224 18.193.255.254 52.29.8.43 3.121.104.141 18.157.173.201 18.193.143.177]
Oct 28 13:51:57 carbon tailscaled[7554]: Received error: register request: Post "https://controlplane.tailscale.com/machine/register": connection attempts aborted by context: context deadline exceeded
Oct 28 13:51:57 carbon tailscaled[7554]: trying bootstrapDNS("derp11.tailscale.com", "18.230.97.74") for "controlplane.tailscale.com" ...
Oct 28 13:51:57 carbon tailscaled[7554]: trying bootstrapDNS("derp4e.tailscale.com", "134.122.74.153") for "controlplane.tailscale.com" ...
Oct 28 13:51:57 carbon tailscaled[7554]: control: LoginInteractive -> regen=true
Oct 28 13:51:57 carbon tailscaled[7554]: control: doLogin(regen=true, hasUrl=false)
Oct 28 13:51:57 carbon tailscaled[7554]: control: Generating a new nodekey.
Oct 28 13:51:57 carbon tailscaled[7554]: control: RegisterReq: onode= node=[p2yph] fup=false
Oct 28 13:51:57 carbon tailscaled[7554]: bootstrapDNS("derp4e.tailscale.com", "134.122.74.153") for "controlplane.tailscale.com" = [2a05:d014:386:202:6dd4:fc68:35ae:2b80 2a05:d014:386:202:a3e1:5be6:cbb1:1ac9 2a05:d014:386:202:24dd:46aa:f98e:9997 2a05:d014:386:203:4535:c15c:9ab:8258 2a05:d014:386:201:7200:6340:b22f:7df6 2a05:d014:386:203:b7ba:b7d4:9703:6f8a 18.193.255.254 18.157.173.201 52.29.8.43 3.121.104.141 18.156.90.224 18.193.143.177]
Oct 28 13:51:58 carbon tailscaled[7554]: bootstrapDNS("derp11.tailscale.com", "18.230.97.74") for "controlplane.tailscale.com" = [2a05:d014:386:202:24dd:46aa:f98e:9997 2a05:d014:386:202:6dd4:fc68:35ae:2b80 2a05:d014:386:203:4535:c15c:9ab:8258 2a05:d014:386:201:7200:6340:b22f:7df6 2a05:d014:386:203:b7ba:b7d4:9703:6f8a 2a05:d014:386:202:a3e1:5be6:cbb1:1ac9 18.193.255.254 18.156.90.224 3.121.104.141 18.193.143.177 18.157.173.201 52.29.8.43]
Oct 28 13:52:07 carbon tailscaled[7554]: Received error: register request: Post "https://controlplane.tailscale.com/machine/register": connection attempts aborted by context: context deadline exceeded
```
### Steps to reproduce
Run `tailscale down` or `tailscale logout` and try to login again
I have tried resetting the tailscale client and reinstalling the package. I have also cleared `/var/lib/tailscale/` manually to get rid of old state
### Are there any recent changes that introduced the issue?
No, this behaviour seems completely random
### OS
Linux
### OS version
Arch Linux kernel 6.0.2-arch
### Tailscale version
1.32.1
### Bug report
BUG-495a217121ba33adf5c90d17c7138fb21263e9d8d9900b113a00357307310882-20221028105730Z-fb4af2b507a9d037
|
usab
|
tailscale hangs indefinitely on misbehaving dns what is the issue sometimes when i try to go log into tailscale i get this weird behaviour where running sudo tailscale up freezes seems like the login flow goes ok until control creating new noise client comes up and then fails with received error register request post connection attempts aborted by context context deadline exceeded see logs below oct carbon tailscaled ipnserver connection from userid root has access oct carbon tailscaled start oct carbon tailscaled control client shutdown oct carbon tailscaled control client shutdown insendstatus oct carbon tailscaled control maproutine quit oct carbon tailscaled control client shutdown done oct carbon tailscaled using backend prefs for daemon prefs ra false dns true want true routes nf on persist nil oct carbon tailscaled backend logs be fe oct carbon tailscaled switching ipn state nostate needslogin wantrunning true nm false oct carbon tailscaled blockengineupdates true oct carbon tailscaled reconfig down no changes made to engine config oct carbon tailscaled startlogininteractive url false oct carbon tailscaled control client login false oct carbon tailscaled control logininteractive regen true oct carbon tailscaled control dologin regen true hasurl false oct carbon tailscaled trying bootstrapdns tailscale com for controlplane tailscale com oct carbon tailscaled bootstrapdns tailscale com for controlplane tailscale com oct carbon tailscaled control control server key from legacy oct carbon tailscaled control generating a new nodekey oct carbon tailscaled control registerreq onode node fup false oct carbon tailscaled control creating new noise client oct carbon tailscaled received error register request post connection attempts aborted by context context deadline exceeded oct carbon tailscaled trying bootstrapdns tailscale com for controlplane tailscale com oct carbon tailscaled trying bootstrapdns tailscale com for controlplane tailscale com oct carbon tailscaled control logininteractive regen true oct carbon tailscaled control dologin regen true hasurl false oct carbon tailscaled control generating a new nodekey oct carbon tailscaled control registerreq onode node fup false oct carbon tailscaled bootstrapdns tailscale com for controlplane tailscale com oct carbon tailscaled bootstrapdns tailscale com for controlplane tailscale com oct carbon tailscaled received error register request post connection attempts aborted by context context deadline exceeded oct carbon tailscaled trying bootstrapdns tailscale com for controlplane tailscale com oct carbon tailscaled trying bootstrapdns tailscale com for controlplane tailscale com oct carbon tailscaled control logininteractive regen true oct carbon tailscaled control dologin regen true hasurl false oct carbon tailscaled control generating a new nodekey oct carbon tailscaled control registerreq onode node fup false oct carbon tailscaled bootstrapdns tailscale com for controlplane tailscale com oct carbon tailscaled bootstrapdns tailscale com for controlplane tailscale com oct carbon tailscaled received error register request post connection attempts aborted by context context deadline exceeded steps to reproduce run tailscale down or tailscale logout and try to login again i have tried resetting the tailscale client and reinstalling the package i have also cleared var lib tailscale manually to get rid of old state are there any recent changes that introduced the issue no this behaviour seems completely random os linux os version arch linux kernel arch tailscale version bug report bug
| 1
|
16,312
| 10,760,213,740
|
IssuesEvent
|
2019-10-31 18:07:27
|
OctopusDeploy/Issues
|
https://api.github.com/repos/OctopusDeploy/Issues
|
opened
|
Edit Environment screen acts as though there are changes if Jira Environment Type is not set
|
area/usability kind/bug
|
# Prerequisites
- [x] I have verified the problem exists in the latest version
- [x] I have searched [open](https://github.com/OctopusDeploy/Issues/issues) and [closed](https://github.com/OctopusDeploy/Issues/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed) issues to make sure it isn't already reported
- [x] I have written a descriptive issue title
- [ ] I have linked the original source of this report
- [x] I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)
# The bug
If the Jira Environment Type field is available but empty on the Edit Environment screen, the page will ask you to save or discard your changes even if you haven't made any.
## What I expected to happen
I don't expect the Unsaved Changes dialog if I haven't made any changes.
## Steps to reproduce
1. Enable Jira Issue Tracker in Configuration > Settings
2. Edit any environment that doesn't have the Jira Environment Type set
3. Try to leave the page
4. See Unsaved Changes dialog
### Screen capture
## Affected versions
**Octopus Server:** 2019.10.1
## Workarounds
Set the Jira Environment Type to unmapped and save the environment.
|
True
|
Edit Environment screen acts as though there are changes if Jira Environment Type is not set - # Prerequisites
- [x] I have verified the problem exists in the latest version
- [x] I have searched [open](https://github.com/OctopusDeploy/Issues/issues) and [closed](https://github.com/OctopusDeploy/Issues/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed) issues to make sure it isn't already reported
- [x] I have written a descriptive issue title
- [ ] I have linked the original source of this report
- [x] I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)
# The bug
If the Jira Environment Type field is available but empty on the Edit Environment screen, the page will ask you to save or discard your changes even if you haven't made any.
## What I expected to happen
I don't expect the Unsaved Changes dialog if I haven't made any changes.
## Steps to reproduce
1. Enable Jira Issue Tracker in Configuration > Settings
2. Edit any environment that doesn't have the Jira Environment Type set
3. Try to leave the page
4. See Unsaved Changes dialog
### Screen capture
## Affected versions
**Octopus Server:** 2019.10.1
## Workarounds
Set the Jira Environment Type to unmapped and save the environment.
|
usab
|
edit environment screen acts as though there are changes if jira environment type is not set prerequisites i have verified the problem exists in the latest version i have searched and issues to make sure it isn t already reported i have written a descriptive issue title i have linked the original source of this report i have tagged the issue appropriately area kind bug tag regression the bug if the jira environment type field is available but empty on the edit environment screen the page will ask you to save or discard your changes even if you haven t made any what i expected to happen i don t expect the unsaved changes dialog if i haven t made any changes steps to reproduce enable jira issue tracker in configuration settings edit any environment that doesn t have the jira environment type set try to leave the page see unsaved changes dialog screen capture affected versions octopus server workarounds set the jira environment type to unmapped and save the environment
| 1
|
160,461
| 12,512,549,157
|
IssuesEvent
|
2020-06-02 23:07:44
|
mapbox/mapbox-navigation-android
|
https://api.github.com/repos/mapbox/mapbox-navigation-android
|
closed
|
SoundButton shows wrong color in CustomUIComponentStyleActivity
|
bug test app
|
<!--
Hello and thanks for contributing! To help us diagnose your problem quickly, please:
- Include a minimal demonstration of the bug, including code, logs, and screenshots.
- Ensure you can reproduce the bug using the latest release.
- Only post to report a bug or request a feature; direct all other questions to: https://stackoverflow.com/questions/tagged/mapbox
-->
**Android API:** Any
**Mapbox Navigation SDK version:** UI SDK 1.0
### Steps to trigger behavior
1. Launch `example` app
2. Launch `CustomUIComponentStyleActivity` example in Navigation UI SDK
3. Start a navigation
4. Click the `SoundButton`
### Expected behavior
The `SoundButton` should show whatever it's before step 4
### Actual behavior
After step 4, the `SoundButton` stays black and doesn't change to the correct color even click it again.
|
1.0
|
SoundButton shows wrong color in CustomUIComponentStyleActivity - <!--
Hello and thanks for contributing! To help us diagnose your problem quickly, please:
- Include a minimal demonstration of the bug, including code, logs, and screenshots.
- Ensure you can reproduce the bug using the latest release.
- Only post to report a bug or request a feature; direct all other questions to: https://stackoverflow.com/questions/tagged/mapbox
-->
**Android API:** Any
**Mapbox Navigation SDK version:** UI SDK 1.0
### Steps to trigger behavior
1. Launch `example` app
2. Launch `CustomUIComponentStyleActivity` example in Navigation UI SDK
3. Start a navigation
4. Click the `SoundButton`
### Expected behavior
The `SoundButton` should show whatever it's before step 4
### Actual behavior
After step 4, the `SoundButton` stays black and doesn't change to the correct color even click it again.
|
non_usab
|
soundbutton shows wrong color in customuicomponentstyleactivity hello and thanks for contributing to help us diagnose your problem quickly please include a minimal demonstration of the bug including code logs and screenshots ensure you can reproduce the bug using the latest release only post to report a bug or request a feature direct all other questions to android api any mapbox navigation sdk version ui sdk steps to trigger behavior launch example app launch customuicomponentstyleactivity example in navigation ui sdk start a navigation click the soundbutton expected behavior the soundbutton should show whatever it s before step actual behavior after step the soundbutton stays black and doesn t change to the correct color even click it again
| 0
|
57,496
| 14,136,424,879
|
IssuesEvent
|
2020-11-10 04:15:54
|
streamnative/pulsar
|
https://api.github.com/repos/streamnative/pulsar
|
closed
|
ISSUE-7312: pulsar-2.6.0 cpp client build error
|
component/build triage/week-26 type/bug workflow::todo
|
Original Issue: apache/pulsar#7312
---
**Describe the bug**
build error
**To Reproduce**
Steps to reproduce the behavior:
[root@VM_72_166_tlinux /data/commlibsrc/pulsar-2.6.0/pulsar-client-cpp/build]# cmake ..
-- ARCHITECTURE: x86_64
-- BUILD_TESTS: ON
-- BUILD_PYTHON_WRAPPER: ON
-- LINK_STATIC: OFF
-- USE_LOG4CXX: OFF
-- CMAKE_BUILD_TYPE: RelWithDebInfo
-- Found Boost: /usr/local/include (found version "1.54.0") found components: program_options regex system
-- PYTHON: 2.7.10
-- Found Boost: /usr/local/include (found version "1.54.0") found components: python
-- HAS_ZSTD: 0
-- HAS_SNAPPY: 1
-- Using Boost Python libs: /usr/local/lib/libboost_python.so
clang-tidy not found
clang-format not found
-- Configuring done
-- Generating done
-- Build files have been written to: /data/commlibsrc/pulsar-2.6.0/pulsar-client-cpp/build
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- linux 3.10.106
**Additional context**
/data/commlibsrc/pulsar-2.6.0/pulsar-client-cpp/lib/CompressionCodecSnappy.cc: In member function 'virtual bool pulsar::CompressionCodecSnappy::decode(const pulsar::SharedBuffer&, uint32_t, pulsar::SharedBuffer&)':
/data/commlibsrc/pulsar-2.6.0/pulsar-client-cpp/lib/CompressionCodecSnappy.cc:43:42: error: cannot convert 'snappy::ByteArraySource*' to 'const char*' for argument '1' to 'bool snappy::Uncompress(const char*, size_t, snappy::string*)'
if (snappy::Uncompress(&source, &sink)) {
^
make[2]: *** [lib/CMakeFiles/pulsarShared.dir/CompressionCodecSnappy.cc.o] Error 1
make[1]: *** [lib/CMakeFiles/pulsarShared.dir/all] Error 2
|
1.0
|
ISSUE-7312: pulsar-2.6.0 cpp client build error - Original Issue: apache/pulsar#7312
---
**Describe the bug**
build error
**To Reproduce**
Steps to reproduce the behavior:
[root@VM_72_166_tlinux /data/commlibsrc/pulsar-2.6.0/pulsar-client-cpp/build]# cmake ..
-- ARCHITECTURE: x86_64
-- BUILD_TESTS: ON
-- BUILD_PYTHON_WRAPPER: ON
-- LINK_STATIC: OFF
-- USE_LOG4CXX: OFF
-- CMAKE_BUILD_TYPE: RelWithDebInfo
-- Found Boost: /usr/local/include (found version "1.54.0") found components: program_options regex system
-- PYTHON: 2.7.10
-- Found Boost: /usr/local/include (found version "1.54.0") found components: python
-- HAS_ZSTD: 0
-- HAS_SNAPPY: 1
-- Using Boost Python libs: /usr/local/lib/libboost_python.so
clang-tidy not found
clang-format not found
-- Configuring done
-- Generating done
-- Build files have been written to: /data/commlibsrc/pulsar-2.6.0/pulsar-client-cpp/build
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- linux 3.10.106
**Additional context**
/data/commlibsrc/pulsar-2.6.0/pulsar-client-cpp/lib/CompressionCodecSnappy.cc: In member function 'virtual bool pulsar::CompressionCodecSnappy::decode(const pulsar::SharedBuffer&, uint32_t, pulsar::SharedBuffer&)':
/data/commlibsrc/pulsar-2.6.0/pulsar-client-cpp/lib/CompressionCodecSnappy.cc:43:42: error: cannot convert 'snappy::ByteArraySource*' to 'const char*' for argument '1' to 'bool snappy::Uncompress(const char*, size_t, snappy::string*)'
if (snappy::Uncompress(&source, &sink)) {
^
make[2]: *** [lib/CMakeFiles/pulsarShared.dir/CompressionCodecSnappy.cc.o] Error 1
make[1]: *** [lib/CMakeFiles/pulsarShared.dir/all] Error 2
|
non_usab
|
issue pulsar cpp client build error original issue apache pulsar describe the bug build error to reproduce steps to reproduce the behavior cmake architecture build tests on build python wrapper on link static off use off cmake build type relwithdebinfo found boost usr local include found version found components program options regex system python found boost usr local include found version found components python has zstd has snappy using boost python libs usr local lib libboost python so clang tidy not found clang format not found configuring done generating done build files have been written to data commlibsrc pulsar pulsar client cpp build expected behavior a clear and concise description of what you expected to happen screenshots if applicable add screenshots to help explain your problem desktop please complete the following information linux additional context data commlibsrc pulsar pulsar client cpp lib compressioncodecsnappy cc in member function virtual bool pulsar compressioncodecsnappy decode const pulsar sharedbuffer t pulsar sharedbuffer data commlibsrc pulsar pulsar client cpp lib compressioncodecsnappy cc error cannot convert snappy bytearraysource to const char for argument to bool snappy uncompress const char size t snappy string if snappy uncompress source sink make error make error
| 0
|
21,826
| 17,837,042,086
|
IssuesEvent
|
2021-09-03 03:40:28
|
simonw/datasette-app
|
https://api.github.com/repos/simonw/datasette-app
|
closed
|
Show error messages when open CSV/database fails
|
electron-wrapper usability
|
Currently it fails silently and logs to the console.
|
True
|
Show error messages when open CSV/database fails - Currently it fails silently and logs to the console.
|
usab
|
show error messages when open csv database fails currently it fails silently and logs to the console
| 1
|
376,294
| 26,193,872,194
|
IssuesEvent
|
2023-01-03 11:37:50
|
arturo-lang/arturo
|
https://api.github.com/repos/arturo-lang/arturo
|
closed
|
[Sockets/unplug] add documentation example
|
documentation library todo easy
|
[Sockets/unplug] add documentation example
https://github.com/arturo-lang/arturo/blob/a7209b1e5afa19379d5ef718f8384ce18a8b3159/src/library/Sockets.nim#L233
```text
## The main Sockets module
## (part of the standard library)
#=======================================
# Pragmas
#=======================================
{.used.}
#=======================================
# Libraries
#=======================================
when not defined(WEB):
import std/net as netsock except Socket
import nativesockets
import vm/values/custom/[vsocket]
import vm/lib
when not defined(WEB):
import vm/errors
#=======================================
# Methods
#=======================================
# TODO(Sockets) Verify the whole module & check for missing functionality
# obviously this cannot be done with unit-tests as easily as with other modules, but
# we'd still have to verify it works as expected and track down possibly-missing
# features
# labels: open discussion
proc defineSymbols*() =
when not defined(WEB):
builtin "accept",
alias = unaliased,
rule = PrefixPrecedence,
description = "accept incoming connection and return corresponding socket",
args = {
"server" : {Socket}
},
attrs = NoAttrs,
returns = {Socket},
# TODO(Sockets/accept) add documentation example
# labels: library, documentation, easy
example = """
""":
#=======================================================
when defined(SAFE): RuntimeError_OperationNotPermitted("accept")
var client: netsock.Socket
x.sock.socket.accept(client)
let (address,port) = getPeerAddr(client)
let socket = initSocket(client, proto=x.sock.protocol, address=address, port=port)
push newSocket(socket)
builtin "connect",
alias = unaliased,
rule = PrefixPrecedence,
description = "create new socket connection to given server port",
args = {
"port" : {Integer}
},
attrs = {
"to" : ({String},"set socket address"),
"udp" : ({Logical},"use UDP instead of TCP")
},
returns = {Socket},
# TODO(Sockets/connect) add documentation example
# labels: library, documentation, easy
example = """
""":
#=======================================================
when defined(SAFE): RuntimeError_OperationNotPermitted("connect")
let isUDP = hadAttr("udp")
let protocol =
if isUDP: IPPROTO_UDP
else: IPPROTO_TCP
var toAddress: string
if checkAttr("to"):
toAddress = aTo.s
else:
toAddress = "0.0.0.0"
var port = Port(x.i)
var sock: netsock.Socket = netsock.newSocket(protocol=protocol)
if not isUDP:
sock.connect(toAddress, port)
let socket = initSocket(sock, proto=protocol, address=toAddress, port=port)
push newSocket(socket)
builtin "listen",
alias = unaliased,
rule = PrefixPrecedence,
description = "start listening on given port and return new socket",
args = {
"port" : {Integer}
},
attrs = {
"blocking" : ({String},"set blocking mode (default: false)"),
"udp" : ({Logical},"use UDP instead of TCP")
},
returns = {Socket},
# TODO(Sockets/listen) add documentation example
# labels: library, documentation, easy
example = """
""":
#=======================================================
when defined(SAFE): RuntimeError_OperationNotPermitted("listen")
let blocking = hadAttr("blocking")
let protocol =
if hadAttr("udp"): IPPROTO_UDP
else: IPPROTO_TCP
var sock: netsock.Socket = netsock.newSocket(protocol=protocol)
sock.setSockOpt(OptReuseAddr, true)
sock.getFd().setBlocking(blocking)
sock.bindAddr(Port(x.i))
sock.listen()
let (address,port) = getLocalAddr(sock)
let socket = initSocket(sock, proto=protocol, address=address, port=port)
push newSocket(socket)
builtin "receive",
alias = unaliased,
rule = PrefixPrecedence,
description = "receive line of data from selected socket",
args = {
"origin" : {Socket}
},
attrs = {
"size" : ({Integer},"set maximum size of received data"),
"timeout" : ({Integer},"set timeout (in milliseconds)")
},
returns = {String},
# TODO(Sockets/receive) add documentation example
# labels: library, documentation, easy
example = """
""":
#=======================================================
when defined(SAFE): RuntimeError_OperationNotPermitted("receive")
var size = MaxLineLength
if checkAttr("size"):
size = aSize.i
var timeout = -1
if checkAttr("timeout"):
timeout = aTimeout.i
push newString(x.sock.socket.recvLine(timeout=timeout, maxLength=size))
builtin "send",
alias = unaliased,
rule = PrefixPrecedence,
description = "send given message to selected socket",
args = {
"destination" : {Socket},
"message" : {String}
},
attrs = {
"chunk" : ({Logical},"don't send data as a line of data")
},
returns = {Nothing},
# TODO(Sockets/send) add documentation example
# labels: library, documentation, easy
example = """
""":
#=======================================================
when defined(SAFE): RuntimeError_OperationNotPermitted("send")
let asChunk = hadAttr("chunk")
let message =
if asChunk: y.s
else: y.s & "\r\L"
x.sock.socket.send(message)
builtin "send?",
alias = unaliased,
rule = PrefixPrecedence,
description = "send given message to selected socket and return true if successful",
args = {
"destination" : {Socket},
"message" : {String}
},
attrs = NoAttrs,
returns = {Logical},
# TODO(Sockets/send?) add documentation example
# labels: library, documentation, easy
example = """
""":
#=======================================================
when defined(SAFE): RuntimeError_OperationNotPermitted("send?")
push newLogical(x.sock.socket.trySend(y.s))
builtin "unplug",
alias = unaliased,
rule = PrefixPrecedence,
description = "close given socket",
args = {
"socket" : {Socket}
},
attrs = NoAttrs,
returns = {Nothing},
# TODO(Sockets/unplug) add documentation example
# labels: library, documentation, easy
example = """
""":
#=======================================================
when defined(SAFE): RuntimeError_OperationNotPermitted("unplug")
x.sock.socket.close()
else:
discard
#=======================================
# Add Library
#=======================================
Libraries.add(defineSymbols)
ndex fd9afdfc2..7555eeebc 100644
++ b/src/library/System.nim
```
e787a4c0139eeb43ec42731ba666ce131e656c62
|
1.0
|
[Sockets/unplug] add documentation example - [Sockets/unplug] add documentation example
https://github.com/arturo-lang/arturo/blob/a7209b1e5afa19379d5ef718f8384ce18a8b3159/src/library/Sockets.nim#L233
```text
## The main Sockets module
## (part of the standard library)
#=======================================
# Pragmas
#=======================================
{.used.}
#=======================================
# Libraries
#=======================================
when not defined(WEB):
import std/net as netsock except Socket
import nativesockets
import vm/values/custom/[vsocket]
import vm/lib
when not defined(WEB):
import vm/errors
#=======================================
# Methods
#=======================================
# TODO(Sockets) Verify the whole module & check for missing functionality
# obviously this cannot be done with unit-tests as easily as with other modules, but
# we'd still have to verify it works as expected and track down possibly-missing
# features
# labels: open discussion
proc defineSymbols*() =
when not defined(WEB):
builtin "accept",
alias = unaliased,
rule = PrefixPrecedence,
description = "accept incoming connection and return corresponding socket",
args = {
"server" : {Socket}
},
attrs = NoAttrs,
returns = {Socket},
# TODO(Sockets/accept) add documentation example
# labels: library, documentation, easy
example = """
""":
#=======================================================
when defined(SAFE): RuntimeError_OperationNotPermitted("accept")
var client: netsock.Socket
x.sock.socket.accept(client)
let (address,port) = getPeerAddr(client)
let socket = initSocket(client, proto=x.sock.protocol, address=address, port=port)
push newSocket(socket)
builtin "connect",
alias = unaliased,
rule = PrefixPrecedence,
description = "create new socket connection to given server port",
args = {
"port" : {Integer}
},
attrs = {
"to" : ({String},"set socket address"),
"udp" : ({Logical},"use UDP instead of TCP")
},
returns = {Socket},
# TODO(Sockets/connect) add documentation example
# labels: library, documentation, easy
example = """
""":
#=======================================================
when defined(SAFE): RuntimeError_OperationNotPermitted("connect")
let isUDP = hadAttr("udp")
let protocol =
if isUDP: IPPROTO_UDP
else: IPPROTO_TCP
var toAddress: string
if checkAttr("to"):
toAddress = aTo.s
else:
toAddress = "0.0.0.0"
var port = Port(x.i)
var sock: netsock.Socket = netsock.newSocket(protocol=protocol)
if not isUDP:
sock.connect(toAddress, port)
let socket = initSocket(sock, proto=protocol, address=toAddress, port=port)
push newSocket(socket)
builtin "listen",
alias = unaliased,
rule = PrefixPrecedence,
description = "start listening on given port and return new socket",
args = {
"port" : {Integer}
},
attrs = {
"blocking" : ({String},"set blocking mode (default: false)"),
"udp" : ({Logical},"use UDP instead of TCP")
},
returns = {Socket},
# TODO(Sockets/listen) add documentation example
# labels: library, documentation, easy
example = """
""":
#=======================================================
when defined(SAFE): RuntimeError_OperationNotPermitted("listen")
let blocking = hadAttr("blocking")
let protocol =
if hadAttr("udp"): IPPROTO_UDP
else: IPPROTO_TCP
var sock: netsock.Socket = netsock.newSocket(protocol=protocol)
sock.setSockOpt(OptReuseAddr, true)
sock.getFd().setBlocking(blocking)
sock.bindAddr(Port(x.i))
sock.listen()
let (address,port) = getLocalAddr(sock)
let socket = initSocket(sock, proto=protocol, address=address, port=port)
push newSocket(socket)
builtin "receive",
alias = unaliased,
rule = PrefixPrecedence,
description = "receive line of data from selected socket",
args = {
"origin" : {Socket}
},
attrs = {
"size" : ({Integer},"set maximum size of received data"),
"timeout" : ({Integer},"set timeout (in milliseconds)")
},
returns = {String},
# TODO(Sockets/receive) add documentation example
# labels: library, documentation, easy
example = """
""":
#=======================================================
when defined(SAFE): RuntimeError_OperationNotPermitted("receive")
var size = MaxLineLength
if checkAttr("size"):
size = aSize.i
var timeout = -1
if checkAttr("timeout"):
timeout = aTimeout.i
push newString(x.sock.socket.recvLine(timeout=timeout, maxLength=size))
builtin "send",
alias = unaliased,
rule = PrefixPrecedence,
description = "send given message to selected socket",
args = {
"destination" : {Socket},
"message" : {String}
},
attrs = {
"chunk" : ({Logical},"don't send data as a line of data")
},
returns = {Nothing},
# TODO(Sockets/send) add documentation example
# labels: library, documentation, easy
example = """
""":
#=======================================================
when defined(SAFE): RuntimeError_OperationNotPermitted("send")
let asChunk = hadAttr("chunk")
let message =
if asChunk: y.s
else: y.s & "\r\L"
x.sock.socket.send(message)
builtin "send?",
alias = unaliased,
rule = PrefixPrecedence,
description = "send given message to selected socket and return true if successful",
args = {
"destination" : {Socket},
"message" : {String}
},
attrs = NoAttrs,
returns = {Logical},
# TODO(Sockets/send?) add documentation example
# labels: library, documentation, easy
example = """
""":
#=======================================================
when defined(SAFE): RuntimeError_OperationNotPermitted("send?")
push newLogical(x.sock.socket.trySend(y.s))
builtin "unplug",
alias = unaliased,
rule = PrefixPrecedence,
description = "close given socket",
args = {
"socket" : {Socket}
},
attrs = NoAttrs,
returns = {Nothing},
# TODO(Sockets/unplug) add documentation example
# labels: library, documentation, easy
example = """
""":
#=======================================================
when defined(SAFE): RuntimeError_OperationNotPermitted("unplug")
x.sock.socket.close()
else:
discard
#=======================================
# Add Library
#=======================================
Libraries.add(defineSymbols)
ndex fd9afdfc2..7555eeebc 100644
++ b/src/library/System.nim
```
e787a4c0139eeb43ec42731ba666ce131e656c62
|
non_usab
|
add documentation example add documentation example text the main sockets module part of the standard library pragmas used libraries when not defined web import std net as netsock except socket import nativesockets import vm values custom import vm lib when not defined web import vm errors methods todo sockets verify the whole module check for missing functionality obviously this cannot be done with unit tests as easily as with other modules but we d still have to verify it works as expected and track down possibly missing features labels open discussion proc definesymbols when not defined web builtin accept alias unaliased rule prefixprecedence description accept incoming connection and return corresponding socket args server socket attrs noattrs returns socket todo sockets accept add documentation example labels library documentation easy example when defined safe runtimeerror operationnotpermitted accept var client netsock socket x sock socket accept client let address port getpeeraddr client let socket initsocket client proto x sock protocol address address port port push newsocket socket builtin connect alias unaliased rule prefixprecedence description create new socket connection to given server port args port integer attrs to string set socket address udp logical use udp instead of tcp returns socket todo sockets connect add documentation example labels library documentation easy example when defined safe runtimeerror operationnotpermitted connect let isudp hadattr udp let protocol if isudp ipproto udp else ipproto tcp var toaddress string if checkattr to toaddress ato s else toaddress var port port x i var sock netsock socket netsock newsocket protocol protocol if not isudp sock connect toaddress port let socket initsocket sock proto protocol address toaddress port port push newsocket socket builtin listen alias unaliased rule prefixprecedence description start listening on given port and return new socket args port integer attrs blocking string set blocking mode default false udp logical use udp instead of tcp returns socket todo sockets listen add documentation example labels library documentation easy example when defined safe runtimeerror operationnotpermitted listen let blocking hadattr blocking let protocol if hadattr udp ipproto udp else ipproto tcp var sock netsock socket netsock newsocket protocol protocol sock setsockopt optreuseaddr true sock getfd setblocking blocking sock bindaddr port x i sock listen let address port getlocaladdr sock let socket initsocket sock proto protocol address address port port push newsocket socket builtin receive alias unaliased rule prefixprecedence description receive line of data from selected socket args origin socket attrs size integer set maximum size of received data timeout integer set timeout in milliseconds returns string todo sockets receive add documentation example labels library documentation easy example when defined safe runtimeerror operationnotpermitted receive var size maxlinelength if checkattr size size asize i var timeout if checkattr timeout timeout atimeout i push newstring x sock socket recvline timeout timeout maxlength size builtin send alias unaliased rule prefixprecedence description send given message to selected socket args destination socket message string attrs chunk logical don t send data as a line of data returns nothing todo sockets send add documentation example labels library documentation easy example when defined safe runtimeerror operationnotpermitted send let aschunk hadattr chunk let message if aschunk y s else y s r l x sock socket send message builtin send alias unaliased rule prefixprecedence description send given message to selected socket and return true if successful args destination socket message string attrs noattrs returns logical todo sockets send add documentation example labels library documentation easy example when defined safe runtimeerror operationnotpermitted send push newlogical x sock socket trysend y s builtin unplug alias unaliased rule prefixprecedence description close given socket args socket socket attrs noattrs returns nothing todo sockets unplug add documentation example labels library documentation easy example when defined safe runtimeerror operationnotpermitted unplug x sock socket close else discard add library libraries add definesymbols ndex b src library system nim
| 0
|
6,458
| 4,295,646,892
|
IssuesEvent
|
2016-07-19 08:04:26
|
Tiendil/the-tale
|
https://api.github.com/repos/Tiendil/the-tale
|
opened
|
Увеличить максимум энергии для подписчиков
|
comp_game_logic cont_usability est_simple type_improvement
|
Чтобы не требовалось заходить несколько раз в день для траты её по рассписанию.
Лучше иметь запас на 1.5-2 дня
|
True
|
Увеличить максимум энергии для подписчиков - Чтобы не требовалось заходить несколько раз в день для траты её по рассписанию.
Лучше иметь запас на 1.5-2 дня
|
usab
|
увеличить максимум энергии для подписчиков чтобы не требовалось заходить несколько раз в день для траты её по рассписанию лучше иметь запас на дня
| 1
|
16,537
| 11,035,856,243
|
IssuesEvent
|
2019-12-07 16:36:23
|
godotengine/godot
|
https://api.github.com/repos/godotengine/godot
|
closed
|
parameter Hints in autocompletion preview - to show expected type of variable and other info
|
enhancement topic:editor topic:gdscript usability
|
1. The editor and gdscript are not consistent with the value type they take for rotations
A hint about set_rot() type of expected variable would have helped me avoid a bit of confusion here:
https://github.com/godotengine/godot/issues/4516#issuecomment-217423197
This is an example of how in some cases your code might parse successfully, but not do what you expect.
2. In order to know the type of variable that is expected in a function or a method, you need to search the class api documentation explicitly.
In game maker, the auto - completion gives hints like this:
So no need to search for this, the actual autocompletion is showing you immediately what type of value or syntax it expects!
Godot has no hints whatsoever.
To make this even more awesome than godot, gamemaker users can write hints for their own functions parameters. Defining a hint is as simple as:
http://gamemakerblog.com/2014/01/02/how-to-add-intelligent-code-completion-to-scripts/
This is a common feature of many other code editors.
Look at how nice it is in superpowers game engine:
This makes them easier to learn or transition to!
|
True
|
parameter Hints in autocompletion preview - to show expected type of variable and other info - 1. The editor and gdscript are not consistent with the value type they take for rotations
A hint about set_rot() type of expected variable would have helped me avoid a bit of confusion here:
https://github.com/godotengine/godot/issues/4516#issuecomment-217423197
This is an example of how in some cases your code might parse successfully, but not do what you expect.
2. In order to know the type of variable that is expected in a function or a method, you need to search the class api documentation explicitly.
In game maker, the auto - completion gives hints like this:
So no need to search for this, the actual autocompletion is showing you immediately what type of value or syntax it expects!
Godot has no hints whatsoever.
To make this even more awesome than godot, gamemaker users can write hints for their own functions parameters. Defining a hint is as simple as:
http://gamemakerblog.com/2014/01/02/how-to-add-intelligent-code-completion-to-scripts/
This is a common feature of many other code editors.
Look at how nice it is in superpowers game engine:
This makes them easier to learn or transition to!
|
usab
|
parameter hints in autocompletion preview to show expected type of variable and other info the editor and gdscript are not consistent with the value type they take for rotations a hint about set rot type of expected variable would have helped me avoid a bit of confusion here this is an example of how in some cases your code might parse successfully but not do what you expect in order to know the type of variable that is expected in a function or a method you need to search the class api documentation explicitly in game maker the auto completion gives hints like this so no need to search for this the actual autocompletion is showing you immediately what type of value or syntax it expects godot has no hints whatsoever to make this even more awesome than godot gamemaker users can write hints for their own functions parameters defining a hint is as simple as this is a common feature of many other code editors look at how nice it is in superpowers game engine this makes them easier to learn or transition to
| 1
|
338,872
| 24,602,500,544
|
IssuesEvent
|
2022-10-14 13:37:39
|
brndnmtthws/conky
|
https://api.github.com/repos/brndnmtthws/conky
|
closed
|
Please remove pandoc
|
documentation
|
### What happened?
I'm running Slackware 15.0 and when I tried to compile 1.14.0 and I get this message at the term;
CMake Error at cmake/ConkyPlatformChecks.cmake:485 (message):
Unable to find program 'pandoc'
Call Stack (most recent call first):
CMakeLists.txt:35 (include)
I see in the doc README.md, pandoc listed.
So I'm not looking Slackware biased here, look at Arch Linux for pandoc; (Dependencies (74))
https://archlinux.org/packages/community/x86_64/pandoc/
74 dependencies needed for pandoc.
I guess for now I'm going to have to use -DBUILD_DOCS=OFF if I want to use this version, but I would like to have docs installed.
Can we please get this changed, since pandoc has an extreme amount of Haskell dependencies. I don't understand why from version 1.13.1 to 1.14.0 this had to change and now include this extreme amount of Haskell dependency just for docs.
THANKS
### Version
1.14.0
### Which OS/distro are you seeing the problem on?
Slackware 15.0
```P.S. Didn't mean to post this as an actual bug report, sorry.```
|
1.0
|
Please remove pandoc - ### What happened?
I'm running Slackware 15.0 and when I tried to compile 1.14.0 and I get this message at the term;
CMake Error at cmake/ConkyPlatformChecks.cmake:485 (message):
Unable to find program 'pandoc'
Call Stack (most recent call first):
CMakeLists.txt:35 (include)
I see in the doc README.md, pandoc listed.
So I'm not looking Slackware biased here, look at Arch Linux for pandoc; (Dependencies (74))
https://archlinux.org/packages/community/x86_64/pandoc/
74 dependencies needed for pandoc.
I guess for now I'm going to have to use -DBUILD_DOCS=OFF if I want to use this version, but I would like to have docs installed.
Can we please get this changed, since pandoc has an extreme amount of Haskell dependencies. I don't understand why from version 1.13.1 to 1.14.0 this had to change and now include this extreme amount of Haskell dependency just for docs.
THANKS
### Version
1.14.0
### Which OS/distro are you seeing the problem on?
Slackware 15.0
```P.S. Didn't mean to post this as an actual bug report, sorry.```
|
non_usab
|
please remove pandoc what happened i m running slackware and when i tried to compile and i get this message at the term cmake error at cmake conkyplatformchecks cmake message unable to find program pandoc call stack most recent call first cmakelists txt include i see in the doc readme md pandoc listed so i m not looking slackware biased here look at arch linux for pandoc dependencies dependencies needed for pandoc i guess for now i m going to have to use dbuild docs off if i want to use this version but i would like to have docs installed can we please get this changed since pandoc has an extreme amount of haskell dependencies i don t understand why from version to this had to change and now include this extreme amount of haskell dependency just for docs thanks version which os distro are you seeing the problem on slackware p s didn t mean to post this as an actual bug report sorry
| 0
|
44,730
| 18,169,784,608
|
IssuesEvent
|
2021-09-27 18:32:02
|
hashicorp/terraform-provider-aws
|
https://api.github.com/repos/hashicorp/terraform-provider-aws
|
closed
|
Data Source for aws_kinesis_firehose_delivery_stream
|
new-data-source service/firehose
|
It would be helpful to have a way to lookup an `aws_kinesis_firehose_delivery_stream` by name to get the ARN and other attributes. Usually Data Sources are used for this, but it seems to have been left out of the original implementation.
Side note: I'd argue that most new resources should probably have corresponding data sources made at time they are added to this provider. Just saying...
|
1.0
|
Data Source for aws_kinesis_firehose_delivery_stream - It would be helpful to have a way to lookup an `aws_kinesis_firehose_delivery_stream` by name to get the ARN and other attributes. Usually Data Sources are used for this, but it seems to have been left out of the original implementation.
Side note: I'd argue that most new resources should probably have corresponding data sources made at time they are added to this provider. Just saying...
|
non_usab
|
data source for aws kinesis firehose delivery stream it would be helpful to have a way to lookup an aws kinesis firehose delivery stream by name to get the arn and other attributes usually data sources are used for this but it seems to have been left out of the original implementation side note i d argue that most new resources should probably have corresponding data sources made at time they are added to this provider just saying
| 0
|
75,874
| 9,335,148,456
|
IssuesEvent
|
2019-03-28 17:52:13
|
GSA/pra.gov
|
https://api.github.com/repos/GSA/pra.gov
|
opened
|
Refer to OIRA/OMB consistently throughout the site
|
content design
|
Denote that OIRA and OMB are the same organization or use one or the other consistently throughout the site. Going back and forth between the two was confusing to users during testing.
|
1.0
|
Refer to OIRA/OMB consistently throughout the site - Denote that OIRA and OMB are the same organization or use one or the other consistently throughout the site. Going back and forth between the two was confusing to users during testing.
|
non_usab
|
refer to oira omb consistently throughout the site denote that oira and omb are the same organization or use one or the other consistently throughout the site going back and forth between the two was confusing to users during testing
| 0
|
22,322
| 30,884,968,413
|
IssuesEvent
|
2023-08-03 20:52:15
|
bazelbuild/bazel
|
https://api.github.com/repos/bazelbuild/bazel
|
opened
|
Release 6.3.2 - Aug 2023
|
P1 type: process release team-OSS
|
# Status of Bazel 6.3.2
- Expected first release candidate date: 2023-08-03
- Expected release date: 2023-08-07
- [List of release blockers](https://github.com/bazelbuild/bazel/milestone/59)
To report a release-blocking bug, please add a comment with the text `@bazel-io flag` to the issue. A release manager will triage it and add it to the milestone.
To cherry-pick a mainline commit into 6.3.2, simply send a PR against the `release-6.3.2` branch.
**Task list:**
<!-- The first item is only needed for major releases (X.0.0) -->
- [ ] Create release candidate: 6.3.2
- [ ] Check downstream projects
- [ ] Create [draft release announcement](https://docs.google.com/document/d/1pu2ARPweOCTxPsRR8snoDtkC9R51XWRyBXeiC6Ql5so/edit) <!-- Note that there should be a new Bazel Release Announcement document for every major release. For minor and patch releases, use the latest open doc. -->
- [ ] Push the blog post: [link to blog post] <!-- Only for major releases. -->
- [ ] Update the [release page](https://github.com/bazelbuild/bazel/releases/)
|
1.0
|
Release 6.3.2 - Aug 2023 - # Status of Bazel 6.3.2
- Expected first release candidate date: 2023-08-03
- Expected release date: 2023-08-07
- [List of release blockers](https://github.com/bazelbuild/bazel/milestone/59)
To report a release-blocking bug, please add a comment with the text `@bazel-io flag` to the issue. A release manager will triage it and add it to the milestone.
To cherry-pick a mainline commit into 6.3.2, simply send a PR against the `release-6.3.2` branch.
**Task list:**
<!-- The first item is only needed for major releases (X.0.0) -->
- [ ] Create release candidate: 6.3.2
- [ ] Check downstream projects
- [ ] Create [draft release announcement](https://docs.google.com/document/d/1pu2ARPweOCTxPsRR8snoDtkC9R51XWRyBXeiC6Ql5so/edit) <!-- Note that there should be a new Bazel Release Announcement document for every major release. For minor and patch releases, use the latest open doc. -->
- [ ] Push the blog post: [link to blog post] <!-- Only for major releases. -->
- [ ] Update the [release page](https://github.com/bazelbuild/bazel/releases/)
|
non_usab
|
release aug status of bazel expected first release candidate date expected release date to report a release blocking bug please add a comment with the text bazel io flag to the issue a release manager will triage it and add it to the milestone to cherry pick a mainline commit into simply send a pr against the release branch task list create release candidate check downstream projects create push the blog post update the
| 0
|
16,584
| 11,095,274,224
|
IssuesEvent
|
2019-12-16 08:44:13
|
gama-platform/gama
|
https://api.github.com/repos/gama-platform/gama
|
closed
|
The interactive console return buggy value
|
Concerns Simulations OS All Version Git 🖥 Display All 😅* Workaround 😱 > Bug 🙅🏻♂️ Affects Usability
|
**Describe the bug**
For somehow reasons, the interactive console (in the simulation perspective) returns some buggy results (results from previous command, nonsense results, etc).
The bug seems to be created when the console is looking across some large lists of agents or when copy-pasting text on it. However, the bug does not reproduce every time.
**To Reproduce**
Totally random 🙊🙈🤷
**Expected behavior**
Returning agents / properties requested every time
**Screenshots**
_The command in the black box is a copy/paste which bugged, the intended text is the command just below_
_I've restart the simulation after the screenshot above, wrote the first 3 lines by hand and just pressed the ⬆ arrow 1 time and execute the code displayed (which is the real code executed, but not the code displayed at the execution)_
**Desktop (please complete the following information):**
- OS: Ubuntu 18.04.3 🐧 / macOS Mojave 🍎
- PC Model: Asus Republic of Gamers / MacBook Pro
- GAMA version: git (probably all but not tested)
- Java version: OpenJDK 1.8 / Oracle JDK 1.8
- Graphics cards / Display system: NVIDIA GeForce GTX 1050 Ti Mobile
**Workaround**
The code executed is the previous line of code executed like below :
```
[1] gaml> corridor[2192].shape
nil
[2] gaml> corridor[2711].agents_on
polyline ([{748.278338593198,207.89073161548004,0.0},{724.1182492005173,273.08670051489025,0.0}])
^--- Result from the previous command (code 1)
[3] gaml> length(corridor[2711].agents_on)
[people(89)]
^--- Result from the previous command (code 2)
[4] gaml> fieohezhiofezhi
1
^--- Result from the previous command (code 3)
[5] gaml> corridor[2711].agents_on
> Error: Block definition does not begin or end correctly
^--- Error from the previous command (code 4)
```
So, it's the most annoying workaround ever, but it's possible to get some results that way
**Additional context**
The problem is not a memory bug I'm starting GAMA with 4Go of RAM (to 10Go max) and the software never fill that init amount.
Also I'm using the ESCAPE Project when I'm talking about "large lists of agents"
_EDIT_ : Add screenshots & workaround
|
True
|
The interactive console return buggy value - **Describe the bug**
For somehow reasons, the interactive console (in the simulation perspective) returns some buggy results (results from previous command, nonsense results, etc).
The bug seems to be created when the console is looking across some large lists of agents or when copy-pasting text on it. However, the bug does not reproduce every time.
**To Reproduce**
Totally random 🙊🙈🤷
**Expected behavior**
Returning agents / properties requested every time
**Screenshots**
_The command in the black box is a copy/paste which bugged, the intended text is the command just below_
_I've restart the simulation after the screenshot above, wrote the first 3 lines by hand and just pressed the ⬆ arrow 1 time and execute the code displayed (which is the real code executed, but not the code displayed at the execution)_
**Desktop (please complete the following information):**
- OS: Ubuntu 18.04.3 🐧 / macOS Mojave 🍎
- PC Model: Asus Republic of Gamers / MacBook Pro
- GAMA version: git (probably all but not tested)
- Java version: OpenJDK 1.8 / Oracle JDK 1.8
- Graphics cards / Display system: NVIDIA GeForce GTX 1050 Ti Mobile
**Workaround**
The code executed is the previous line of code executed like below :
```
[1] gaml> corridor[2192].shape
nil
[2] gaml> corridor[2711].agents_on
polyline ([{748.278338593198,207.89073161548004,0.0},{724.1182492005173,273.08670051489025,0.0}])
^--- Result from the previous command (code 1)
[3] gaml> length(corridor[2711].agents_on)
[people(89)]
^--- Result from the previous command (code 2)
[4] gaml> fieohezhiofezhi
1
^--- Result from the previous command (code 3)
[5] gaml> corridor[2711].agents_on
> Error: Block definition does not begin or end correctly
^--- Error from the previous command (code 4)
```
So, it's the most annoying workaround ever, but it's possible to get some results that way
**Additional context**
The problem is not a memory bug I'm starting GAMA with 4Go of RAM (to 10Go max) and the software never fill that init amount.
Also I'm using the ESCAPE Project when I'm talking about "large lists of agents"
_EDIT_ : Add screenshots & workaround
|
usab
|
the interactive console return buggy value describe the bug for somehow reasons the interactive console in the simulation perspective returns some buggy results results from previous command nonsense results etc the bug seems to be created when the console is looking across some large lists of agents or when copy pasting text on it however the bug does not reproduce every time to reproduce totally random 🙊🙈🤷 expected behavior returning agents properties requested every time screenshots the command in the black box is a copy paste which bugged the intended text is the command just below i ve restart the simulation after the screenshot above wrote the first lines by hand and just pressed the ⬆ arrow time and execute the code displayed which is the real code executed but not the code displayed at the execution desktop please complete the following information os ubuntu 🐧 macos mojave 🍎 pc model asus republic of gamers macbook pro gama version git probably all but not tested java version openjdk oracle jdk graphics cards display system nvidia geforce gtx ti mobile workaround the code executed is the previous line of code executed like below gaml corridor shape nil gaml corridor agents on polyline result from the previous command code gaml length corridor agents on result from the previous command code gaml fieohezhiofezhi result from the previous command code gaml corridor agents on error block definition does not begin or end correctly error from the previous command code so it s the most annoying workaround ever but it s possible to get some results that way additional context the problem is not a memory bug i m starting gama with of ram to max and the software never fill that init amount also i m using the escape project when i m talking about large lists of agents edit add screenshots workaround
| 1
|
117,190
| 17,439,346,374
|
IssuesEvent
|
2021-08-05 01:05:29
|
rsoreq/lodash
|
https://api.github.com/repos/rsoreq/lodash
|
opened
|
CVE-2021-32804 (High) detected in tar-4.4.8.tgz
|
security vulnerability
|
## CVE-2021-32804 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tar-4.4.8.tgz</b></p></summary>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-4.4.8.tgz">https://registry.npmjs.org/tar/-/tar-4.4.8.tgz</a></p>
<p>
Dependency Hierarchy:
- qunitjs-2.4.1.tgz (Root Library)
- chokidar-1.6.1.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- :x: **tar-4.4.8.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The npm package "tar" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.
<p>Publish Date: 2021-08-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32804>CVE-2021-32804</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>8.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: N/A
- Attack Complexity: N/A
- Privileges Required: N/A
- User Interaction: N/A
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9">https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9</a></p>
<p>Release Date: 2021-08-03</p>
<p>Fix Resolution: tar - 3.2.2, 4.4.14, 5.0.6, 6.1.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"tar","packageVersion":"4.4.8","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"qunitjs:2.4.1;chokidar:1.6.1;fsevents:1.2.9;node-pre-gyp:0.12.0;tar:4.4.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"tar - 3.2.2, 4.4.14, 5.0.6, 6.1.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-32804","vulnerabilityDetails":"The npm package \"tar\" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32804","cvss3Severity":"high","cvss3Score":"8.2","cvss3Metrics":{"A":"N/A","AC":"N/A","PR":"N/A","S":"N/A","C":"N/A","UI":"N/A","AV":"N/A","I":"N/A"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2021-32804 (High) detected in tar-4.4.8.tgz - ## CVE-2021-32804 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tar-4.4.8.tgz</b></p></summary>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-4.4.8.tgz">https://registry.npmjs.org/tar/-/tar-4.4.8.tgz</a></p>
<p>
Dependency Hierarchy:
- qunitjs-2.4.1.tgz (Root Library)
- chokidar-1.6.1.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- :x: **tar-4.4.8.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The npm package "tar" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.
<p>Publish Date: 2021-08-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32804>CVE-2021-32804</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>8.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: N/A
- Attack Complexity: N/A
- Privileges Required: N/A
- User Interaction: N/A
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9">https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9</a></p>
<p>Release Date: 2021-08-03</p>
<p>Fix Resolution: tar - 3.2.2, 4.4.14, 5.0.6, 6.1.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"tar","packageVersion":"4.4.8","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"qunitjs:2.4.1;chokidar:1.6.1;fsevents:1.2.9;node-pre-gyp:0.12.0;tar:4.4.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"tar - 3.2.2, 4.4.14, 5.0.6, 6.1.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-32804","vulnerabilityDetails":"The npm package \"tar\" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32804","cvss3Severity":"high","cvss3Score":"8.2","cvss3Metrics":{"A":"N/A","AC":"N/A","PR":"N/A","S":"N/A","C":"N/A","UI":"N/A","AV":"N/A","I":"N/A"},"extraData":{}}</REMEDIATE> -->
|
non_usab
|
cve high detected in tar tgz cve high severity vulnerability vulnerable library tar tgz tar for node library home page a href dependency hierarchy qunitjs tgz root library chokidar tgz fsevents tgz node pre gyp tgz x tar tgz vulnerable library found in base branch master vulnerability details the npm package tar aka node tar before versions and has a arbitrary file creation overwrite vulnerability due to insufficient absolute path sanitization node tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the preservepaths flag is not set to true this is achieved by stripping the absolute path root from any absolute file paths contained in a tar file for example home user bashrc would turn into home user bashrc this logic was insufficient when file paths contained repeated path roots such as home user bashrc node tar would only strip a single path root from such paths when given an absolute file path with repeating path roots the resulting path e g home user bashrc would still resolve to an absolute path thus allowing arbitrary file creation and overwrite this issue was addressed in releases and users may work around this vulnerability without upgrading by creating a custom onentry method which sanitizes the entry path or a filter method which removes entries with absolute paths see referenced github advisory for details be aware of cve which fixes a similar bug in later versions of tar publish date url a href cvss score details base score metrics exploitability metrics attack vector n a attack complexity n a privileges required n a user interaction n a scope n a impact metrics confidentiality impact n a integrity impact n a availability impact n a for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tar isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree qunitjs chokidar fsevents node pre gyp tar isminimumfixversionavailable true minimumfixversion tar basebranches vulnerabilityidentifier cve vulnerabilitydetails the npm package tar aka node tar before versions and has a arbitrary file creation overwrite vulnerability due to insufficient absolute path sanitization node tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the preservepaths flag is not set to true this is achieved by stripping the absolute path root from any absolute file paths contained in a tar file for example home user bashrc would turn into home user bashrc this logic was insufficient when file paths contained repeated path roots such as home user bashrc node tar would only strip a single path root from such paths when given an absolute file path with repeating path roots the resulting path e g home user bashrc would still resolve to an absolute path thus allowing arbitrary file creation and overwrite this issue was addressed in releases and users may work around this vulnerability without upgrading by creating a custom onentry method which sanitizes the entry path or a filter method which removes entries with absolute paths see referenced github advisory for details be aware of cve which fixes a similar bug in later versions of tar vulnerabilityurl
| 0
|
264,503
| 23,121,208,219
|
IssuesEvent
|
2022-07-27 21:44:29
|
nrwl/nx
|
https://api.github.com/repos/nrwl/nx
|
closed
|
TypeError: Cannot read properties of null (reading 'constructor')
|
type: bug blocked: retry with latest stale scope: react-native
|
## Current Behavior
<img width="1103" alt="Screen Shot 2022-06-21 at 08 39 47" src="https://user-images.githubusercontent.com/27006656/174704841-3fdc7418-543a-430c-8ab6-3986edc10537.png">
50/50 in ci/cd pipeline (gitlab) build with @nrwl/expo break but nx think build is succesfull
## Expected Behavior
1. Successful build
2. If can't build throw error
## Steps to Reproduce
@nrwl/expo build-web
|
1.0
|
TypeError: Cannot read properties of null (reading 'constructor') - ## Current Behavior
<img width="1103" alt="Screen Shot 2022-06-21 at 08 39 47" src="https://user-images.githubusercontent.com/27006656/174704841-3fdc7418-543a-430c-8ab6-3986edc10537.png">
50/50 in ci/cd pipeline (gitlab) build with @nrwl/expo break but nx think build is succesfull
## Expected Behavior
1. Successful build
2. If can't build throw error
## Steps to Reproduce
@nrwl/expo build-web
|
non_usab
|
typeerror cannot read properties of null reading constructor current behavior img width alt screen shot at src in ci cd pipeline gitlab build with nrwl expo break but nx think build is succesfull expected behavior successful build if can t build throw error steps to reproduce nrwl expo build web
| 0
|
194,539
| 14,681,130,624
|
IssuesEvent
|
2020-12-31 12:17:02
|
promitor/charts
|
https://api.github.com/repos/promitor/charts
|
opened
|
Push CI image to CI Helm registry for Scraper agent
|
agents:scraper enhancement testing
|
Push CI image to CI Helm registry for Scraper agent once deployment succeeds.
|
1.0
|
Push CI image to CI Helm registry for Scraper agent - Push CI image to CI Helm registry for Scraper agent once deployment succeeds.
|
non_usab
|
push ci image to ci helm registry for scraper agent push ci image to ci helm registry for scraper agent once deployment succeeds
| 0
|
16,283
| 10,722,130,217
|
IssuesEvent
|
2019-10-27 09:33:46
|
brycx/orion
|
https://api.github.com/repos/brycx/orion
|
closed
|
Making the public API more familiar
|
Breaking change question usability
|
The public API for streaming structs and newtypes could be made more familiar to users that come from other Rust crypto libraries.
In continuation of trying to make the streaming API more consistent (https://github.com/brycx/orion/pull/87) the general approach seems to be that all one-shot functions are also part of the struct (an example of this is the RustCrypto `Digest` trait). Maybe the current should be changed to:
- `module::one_shot_function()` -> `module::Ctx::one_shot_function()`
- `module::verify()` -> `module::Ctx::verify()`
For the newtypes API, to be more consitent with types throughout Rust, we chould change:
- `get_length` -> `len`
Changing the newtype API seems worthwhile, but it's debatable whether changing the straming struct API will make a noticable difference in usability.
|
True
|
Making the public API more familiar - The public API for streaming structs and newtypes could be made more familiar to users that come from other Rust crypto libraries.
In continuation of trying to make the streaming API more consistent (https://github.com/brycx/orion/pull/87) the general approach seems to be that all one-shot functions are also part of the struct (an example of this is the RustCrypto `Digest` trait). Maybe the current should be changed to:
- `module::one_shot_function()` -> `module::Ctx::one_shot_function()`
- `module::verify()` -> `module::Ctx::verify()`
For the newtypes API, to be more consitent with types throughout Rust, we chould change:
- `get_length` -> `len`
Changing the newtype API seems worthwhile, but it's debatable whether changing the straming struct API will make a noticable difference in usability.
|
usab
|
making the public api more familiar the public api for streaming structs and newtypes could be made more familiar to users that come from other rust crypto libraries in continuation of trying to make the streaming api more consistent the general approach seems to be that all one shot functions are also part of the struct an example of this is the rustcrypto digest trait maybe the current should be changed to module one shot function module ctx one shot function module verify module ctx verify for the newtypes api to be more consitent with types throughout rust we chould change get length len changing the newtype api seems worthwhile but it s debatable whether changing the straming struct api will make a noticable difference in usability
| 1
|
308,306
| 23,242,963,864
|
IssuesEvent
|
2022-08-03 17:14:38
|
BCDevOps/developer-experience
|
https://api.github.com/repos/BCDevOps/developer-experience
|
opened
|
Notes for RHEL image build changes
|
automation documentation enhancement team/DXC ops and shared services
|
**Describe the issue**
Create a brief notes for **Build with RHEL Base Images**.
- RedHat's build entitlement subscription method has been changed to **SCA (Simple Content Access)**, which requires developers to use RH build entitlements as a volume and allows them to remove the build entitlement file copy command from their Dockerfile.
**Additional context**
- [#2915](https://app.zenhub.com/workspaces/platform-experience-5bb7c5ab4b5806bc2beb9d15/issues/bcdevops/developer-experience/2915)
- [#2642](https://app.zenhub.com/workspaces/platform-experience-5bb7c5ab4b5806bc2beb9d15/issues/bcdevops/developer-experience/2642)
**How does this benefit the users of our platform?**
- Simplified they way of using [Red Hat Enterprise Linux (RHEL) based images](https://catalog.redhat.com/software/containers/search?p=1&architecture=amd64&vendor_name=Red%20Hat%7CRed%20Hat%2C%20Inc.)
**Definition of done**
- Create a note and email to Olena
|
1.0
|
Notes for RHEL image build changes - **Describe the issue**
Create a brief notes for **Build with RHEL Base Images**.
- RedHat's build entitlement subscription method has been changed to **SCA (Simple Content Access)**, which requires developers to use RH build entitlements as a volume and allows them to remove the build entitlement file copy command from their Dockerfile.
**Additional context**
- [#2915](https://app.zenhub.com/workspaces/platform-experience-5bb7c5ab4b5806bc2beb9d15/issues/bcdevops/developer-experience/2915)
- [#2642](https://app.zenhub.com/workspaces/platform-experience-5bb7c5ab4b5806bc2beb9d15/issues/bcdevops/developer-experience/2642)
**How does this benefit the users of our platform?**
- Simplified they way of using [Red Hat Enterprise Linux (RHEL) based images](https://catalog.redhat.com/software/containers/search?p=1&architecture=amd64&vendor_name=Red%20Hat%7CRed%20Hat%2C%20Inc.)
**Definition of done**
- Create a note and email to Olena
|
non_usab
|
notes for rhel image build changes describe the issue create a brief notes for build with rhel base images redhat s build entitlement subscription method has been changed to sca simple content access which requires developers to use rh build entitlements as a volume and allows them to remove the build entitlement file copy command from their dockerfile additional context how does this benefit the users of our platform simplified they way of using definition of done create a note and email to olena
| 0
|
360
| 2,582,904,710
|
IssuesEvent
|
2015-02-15 19:42:45
|
cambridge-alpha-team/unvisual-frontend
|
https://api.github.com/repos/cambridge-alpha-team/unvisual-frontend
|
opened
|
Announce range of choices
|
usability
|
Theo suggested announcing the range of choices.
For example, expanding "play 60" would indicate the minimum and maximum values allowed.
Relevant to #10
|
True
|
Announce range of choices - Theo suggested announcing the range of choices.
For example, expanding "play 60" would indicate the minimum and maximum values allowed.
Relevant to #10
|
usab
|
announce range of choices theo suggested announcing the range of choices for example expanding play would indicate the minimum and maximum values allowed relevant to
| 1
|
332,280
| 29,202,071,324
|
IssuesEvent
|
2023-05-21 00:03:09
|
WordPress/gutenberg
|
https://api.github.com/repos/WordPress/gutenberg
|
closed
|
[Flaky Test] allows shift tabbing to the block toolbar from the first block
|
[Status] Stale [Type] Flaky Test
|
<!-- __META_DATA__:{} -->
**Flaky test detected. This is an auto-generated issue by GitHub Actions. Please do NOT edit this manually.**
## Test title
allows shift tabbing to the block toolbar from the first block
## Test path
`/test/e2e/specs/site-editor/writing-flow.spec.js`
## Errors
<!-- __TEST_RESULTS_LIST__ -->
<!-- __TEST_RESULT__ --><time datetime="2023-03-13T12:53:34.347Z"><code>[2023-03-13T12:53:34.347Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4404789928"><code>remove/lodash-set-core-data</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-14T01:46:16.054Z"><code>[2023-03-14T01:46:16.054Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4411129007"><code>try/grid-layout</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-14T19:43:09.734Z"><code>[2023-03-14T19:43:09.734Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4419341518"><code>tweak/latest-posts-panel-labels</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-15T02:20:42.977Z"><code>[2023-03-15T02:20:42.977Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4421941166"><code>refactor/block-json-selectors-api</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-15T13:50:37.924Z"><code>[2023-03-15T13:50:37.924Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4426740940"><code>refactor/ctx-get-styled-cn-lodash</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-15T16:43:28.576Z"><code>[2023-03-15T16:43:28.576Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4428441677"><code>update/svg-filter-frontend-output</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-15T16:51:16.106Z"><code>[2023-03-15T16:51:16.106Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4428532118"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-15T18:13:53.808Z"><code>[2023-03-15T18:13:53.808Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4429208252"><code>release/15.4</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-16T03:46:26.584Z"><code>[2023-03-16T03:46:26.584Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4433171734"><code>add/position-label-to-block-title-in-list-view</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-16T04:03:55.161Z"><code>[2023-03-16T04:03:55.161Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4433302468"><code>add/more-cover-block-unit-tests</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-16T20:27:02.718Z"><code>[2023-03-16T20:27:02.718Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4441104420"><code>update/svg-filter-frontend-output</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-16T23:52:19.720Z"><code>[2023-03-16T23:52:19.720Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4442524072"><code>add/more-cover-block-unit-tests</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T05:36:23.383Z"><code>[2023-03-17T05:36:23.383Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4444392341"><code>try/affix-knob-angle-picker-control</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T06:32:26.381Z"><code>[2023-03-17T06:32:26.381Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4444662512"><code>try/affix-knob-angle-picker-control</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T10:27:33.462Z"><code>[2023-03-17T10:27:33.462Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4446315177"><code>update/no-store-double-register</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T15:33:46.479Z"><code>[2023-03-17T15:33:46.479Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4448835977"><code>refactor/CustomGradientPicker-typescript</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T16:12:51.784Z"><code>[2023-03-17T16:12:51.784Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4449184008"><code>fix/color-picker-updates-in-gradients</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T16:14:58.068Z"><code>[2023-03-17T16:14:58.068Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4449187594"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T16:33:19.252Z"><code>[2023-03-17T16:33:19.252Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4449389586"><code>update/svg-filter-frontend-output</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T17:01:00.891Z"><code>[2023-03-17T17:01:00.891Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4449587331"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T18:38:17.661Z"><code>[2023-03-17T18:38:17.661Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4450374242"><code>try/affix-knob-angle-picker-control</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-19T08:11:08.957Z"><code>[2023-03-19T08:11:08.957Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4459563169"><code>remove/edit-navigation-leftovers</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-19T16:00:43.822Z"><code>[2023-03-19T16:00:43.822Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4461392032"><code>fix/textarea-input-block</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-20T08:36:34.497Z"><code>[2023-03-20T08:36:34.497Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4466009153"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-20T08:41:22.291Z"><code>[2023-03-20T08:41:22.291Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4466014209"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-20T08:44:56.711Z"><code>[2023-03-20T08:44:56.711Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4465986717"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-20T09:15:37.838Z"><code>[2023-03-20T09:15:37.838Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4466240362"><code>fix-39946</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-20T11:11:44.691Z"><code>[2023-03-20T11:11:44.691Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4467213059"><code>add-caption-gs-ui-take2</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-20T11:58:46.640Z"><code>[2023-03-20T11:58:46.640Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4467667901"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-20T14:38:30.740Z"><code>[2023-03-20T14:38:30.740Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4468704939"><code>fix/group-block-deprecation</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-20T17:35:05.153Z"><code>[2023-03-20T17:35:05.153Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4470878928"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-21T08:01:55.627Z"><code>[2023-03-21T08:01:55.627Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4476519200"><code>rnmobile/add-reassure-pt-2</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-21T11:03:41.799Z"><code>[2023-03-21T11:03:41.799Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4478040074"><code>update/consolidate-safari-scripts</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-21T11:30:48.733Z"><code>[2023-03-21T11:30:48.733Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4478251864"><code>add/color-panel</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-21T17:38:04.162Z"><code>[2023-03-21T17:38:04.162Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4481791515"><code>fix/48586</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-21T21:33:55.042Z"><code>[2023-03-21T21:33:55.042Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4483811946"><code>try/resolution-not-image-size</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-21T23:56:20.573Z"><code>[2023-03-21T23:56:20.573Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4483811946"><code>try/resolution-not-image-size</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T03:54:41.706Z"><code>[2023-03-22T03:54:41.706Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4486127277"><code>try/grid-layout</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T06:20:12.049Z"><code>[2023-03-22T06:20:12.049Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4486800784"><code>fix/image-dont-render-empty</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T09:26:40.761Z"><code>[2023-03-22T09:26:40.761Z]</code></time> Test passed after 2 failed attempts on <a href="https://github.com/WordPress/gutenberg/actions/runs/4487981160"><code>add/typography-support-to-time-to-read-block</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T10:19:01.003Z"><code>[2023-03-22T10:19:01.003Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4488486177"><code>fonts-api/remove-parameter</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T10:32:43.469Z"><code>[2023-03-22T10:32:43.469Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4488580734"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T12:48:55.071Z"><code>[2023-03-22T12:48:55.071Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4489732565"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T14:56:34.315Z"><code>[2023-03-22T14:56:34.315Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4490916635"><code>move-filters-out-of-colors-section</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T16:50:56.970Z"><code>[2023-03-22T16:50:56.970Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4492099207"><code>refactor/GradientPicker-typescript</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T20:46:21.977Z"><code>[2023-03-22T20:46:21.977Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4494093026"><code>fix/48586</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T23:07:07.544Z"><code>[2023-03-22T23:07:07.544Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4495066470"><code>add/more-cover-block-unit-tests</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-23T05:47:47.024Z"><code>[2023-03-23T05:47:47.024Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4497336703"><code>try/grid-layout</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-23T08:21:29.215Z"><code>[2023-03-23T08:21:29.215Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4498197419"><code>rnmobile/add-reassure-pt-2</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-23T09:56:23.509Z"><code>[2023-03-23T09:56:23.509Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4483811946"><code>try/resolution-not-image-size</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-23T12:04:13.148Z"><code>[2023-03-23T12:04:13.148Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4500070080"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-23T13:08:10.823Z"><code>[2023-03-23T13:08:10.823Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4500604660"><code>remove/mobile-custom-waitfor</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-23T14:48:23.243Z"><code>[2023-03-23T14:48:23.243Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4501513054"><code>try/resolution-not-image-size</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-23T17:05:45.951Z"><code>[2023-03-23T17:05:45.951Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4502924413"><code>try/use-dedicated-rest-to-get-nav-fallbacks</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-23T18:35:07.831Z"><code>[2023-03-23T18:35:07.831Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4503717638"><code>refactor/ColorPicker-typescript</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-24T06:07:37.992Z"><code>[2023-03-24T06:07:37.992Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4508136757"><code>update/preformatted-spacing</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-24T11:40:06.945Z"><code>[2023-03-24T11:40:06.945Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4510509364"><code>fix/start-template-options-missing-focus-style</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-24T12:35:31.967Z"><code>[2023-03-24T12:35:31.967Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4510509364"><code>fix/start-template-options-missing-focus-style</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-24T13:19:00.457Z"><code>[2023-03-24T13:19:00.457Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4511342470"><code>schema/stiky-minheight</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-24T15:51:38.645Z"><code>[2023-03-24T15:51:38.645Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4512708200"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-27T07:12:54.840Z"><code>[2023-03-27T07:12:54.840Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4529492370"><code>rnmobile/add-reassure-pt-2</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-27T08:25:16.302Z"><code>[2023-03-27T08:25:16.302Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4530015379"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-27T23:49:39.046Z"><code>[2023-03-27T23:49:39.046Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4537466114"><code>fix/unstable-disable-layout-classnames-in-group-block</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-28T00:21:17.643Z"><code>[2023-03-28T00:21:17.643Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4537707599"><code>fix/grid-in-classic-themes</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-28T08:00:22.863Z"><code>[2023-03-28T08:00:22.863Z]</code></time> Test passed after 2 failed attempts on <a href="https://github.com/WordPress/gutenberg/actions/runs/4540405026"><code>update/list-view-more-menu</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-28T10:53:07.550Z"><code>[2023-03-28T10:53:07.550Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4541874680"><code>add/commands</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-28T16:23:35.654Z"><code>[2023-03-28T16:23:35.654Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4545070030"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-29T05:42:48.273Z"><code>[2023-03-29T05:42:48.273Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4550419545"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-29T09:31:55.182Z"><code>[2023-03-29T09:31:55.182Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4552194692"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-29T09:33:18.351Z"><code>[2023-03-29T09:33:18.351Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4552110263"><code>add/commands</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-29T11:31:52.407Z"><code>[2023-03-29T11:31:52.407Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4553206755"><code>try/block-tools-marry-document-tools</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-29T17:17:57.354Z"><code>[2023-03-29T17:17:57.354Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4555764795"><code>refactor/perf-tests-tmp-folder</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-29T17:19:19.323Z"><code>[2023-03-29T17:19:19.323Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4555754701"><code>try/block-tools-marry-document-tools</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-30T09:48:26.099Z"><code>[2023-03-30T09:48:26.099Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4562651740"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-30T09:57:12.737Z"><code>[2023-03-30T09:57:12.737Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4562710990"><code>fix/show-ui-to-change-custom-links-on-sidebar-navigation</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-30T13:04:48.315Z"><code>[2023-03-30T13:04:48.315Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4564006697"><code>update/block-supports-dependencies</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-30T14:12:51.983Z"><code>[2023-03-30T14:12:51.983Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4565008524"><code>rnmobile/release_1.92.0</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-30T14:38:42.531Z"><code>[2023-03-30T14:38:42.531Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4565255936"><code>try/use-dedicated-rest-to-get-nav-fallbacks</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-30T15:09:12.380Z"><code>[2023-03-30T15:09:12.380Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4565631389"><code>update/file-block-text-formatting</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-30T15:46:34.731Z"><code>[2023-03-30T15:46:34.731Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4566033750"><code>update/template-title-in-sidebar</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-30T19:07:49.424Z"><code>[2023-03-30T19:07:49.424Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4567826409"><code>fix/selectors-api-use-in-duotone</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-31T03:01:55.500Z"><code>[2023-03-31T03:01:55.500Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4570919779"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-31T03:02:18.126Z"><code>[2023-03-31T03:02:18.126Z]</code></time> Test passed after 2 failed attempts on <a href="https://github.com/WordPress/gutenberg/actions/runs/4570941202"><code>add/color-options-to-time-to-read-block</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-31T04:54:18.626Z"><code>[2023-03-31T04:54:18.626Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4571513210"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-31T06:17:59.703Z"><code>[2023-03-31T06:17:59.703Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4572008043"><code>try/list-view-allow-drag-to-parent-level</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-31T06:38:35.187Z"><code>[2023-03-31T06:38:35.187Z]</code></time> Test passed after 2 failed attempts on <a href="https://github.com/WordPress/gutenberg/actions/runs/4572068177"><code>add/details-summary-block</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-31T07:20:10.817Z"><code>[2023-03-31T07:20:10.817Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4572345163"><code>add/details-summary-block</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-31T18:44:55.146Z"><code>[2023-03-31T18:44:55.146Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4577931577"><code>add/commands</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-01T14:28:30.860Z"><code>[2023-04-01T14:28:30.860Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4583536972"><code>columns/prevent-removal-column</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-01T17:01:32.535Z"><code>[2023-04-01T17:01:32.535Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4584150055"><code>fix/build-comments</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-02T07:57:40.983Z"><code>[2023-04-02T07:57:40.983Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4587535171"><code>media-text/fix-deprecation-v2</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-03T03:50:57.314Z"><code>[2023-04-03T03:50:57.314Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4592581935"><code>try/minimal-margin</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-03T05:35:43.398Z"><code>[2023-04-03T05:35:43.398Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4593111001"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-03T06:12:20.047Z"><code>[2023-04-03T06:12:20.047Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4593271554"><code>columns/prevent-removal-column</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-03T08:24:09.145Z"><code>[2023-04-03T08:24:09.145Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4594182993"><code>fix/start-template-options-missing-focus-style</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-03T09:06:53.705Z"><code>[2023-04-03T09:06:53.705Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4594182993"><code>fix/start-template-options-missing-focus-style</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-03T10:25:31.459Z"><code>[2023-04-03T10:25:31.459Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4595244702"><code>rnmobile/support-post-request</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-03T17:14:59.469Z"><code>[2023-04-03T17:14:59.469Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4599193444"><code>fix/avoid-empty-gallery-block-error</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-03T17:39:20.292Z"><code>[2023-04-03T17:39:20.292Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4580712698"><code>tweak/simplify-remove-block-label</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-04T04:55:25.291Z"><code>[2023-04-04T04:55:25.291Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4603905724"><code>add/details-summary-block</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-04T10:36:57.029Z"><code>[2023-04-04T10:36:57.029Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4606520962"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-04T15:18:42.265Z"><code>[2023-04-04T15:18:42.265Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4609083229"><code>try/block-tools-marry-document-tools</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-04T16:58:04.647Z"><code>[2023-04-04T16:58:04.647Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4610017682"><code>try/radix-dropdown</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-04T18:40:34.486Z"><code>[2023-04-04T18:40:34.486Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4610949613"><code>chore/components-changelog</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-05T05:24:17.099Z"><code>[2023-04-05T05:24:17.099Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4615028665"><code>update/remove-wp-block-level-preset-style-filters</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-06T02:51:42.055Z"><code>[2023-04-06T02:51:42.055Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4624780477"><code>add/root-client-id-to-list-view</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-06T04:13:26.703Z"><code>[2023-04-06T04:13:26.703Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4624780477"><code>add/root-client-id-to-list-view</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-06T08:01:51.752Z"><code>[2023-04-06T08:01:51.752Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4626561168"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-06T09:56:29.143Z"><code>[2023-04-06T09:56:29.143Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4627378477"><code>add/commands</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-06T14:24:06.634Z"><code>[2023-04-06T14:24:06.634Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4629651383"><code>update-boding-guidelines-experimental</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-07T00:20:18.217Z"><code>[2023-04-07T00:20:18.217Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4633977499"><code>publish-plugin-types</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-07T11:52:15.443Z"><code>[2023-04-07T11:52:15.443Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4637763867"><code>try/block-tools-invade-document-tools</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-07T12:39:54.446Z"><code>[2023-04-07T12:39:54.446Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4638016563"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-09T14:36:58.568Z"><code>[2023-04-09T14:36:58.568Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4650901329"><code>add/image-drop-html</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-10T14:52:49.610Z"><code>[2023-04-10T14:52:49.610Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4658263501"><code>component-changelog-check-exclude-mobile</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-10T15:02:10.699Z"><code>[2023-04-10T15:02:10.699Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4658311504"><code>test-changelog-ci-changes</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-10T17:16:41.963Z"><code>[2023-04-10T17:16:41.963Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4659330461"><code>test-changelog-ci-changes</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-10T18:32:14.010Z"><code>[2023-04-10T18:32:14.010Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4659841409"><code>rnmobil/add-viewport-props-to-sandbox</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-10T19:39:40.610Z"><code>[2023-04-10T19:39:40.610Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4660074886"><code>rnmobile/release_1.92.1</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-10T19:55:46.712Z"><code>[2023-04-10T19:55:46.712Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4660074886"><code>rnmobile/release_1.92.1</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-11T01:09:56.548Z"><code>[2023-04-11T01:09:56.548Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4662592870"><code>release/15.5</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-11T02:24:37.934Z"><code>[2023-04-11T02:24:37.934Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4662975713"><code>fix/time-to-read-translate</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-11T02:36:16.797Z"><code>[2023-04-11T02:36:16.797Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4663065367"><code>fix/refactor-group-duotone-output</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-11T06:10:22.490Z"><code>[2023-04-11T06:10:22.490Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4664239454"><code>try/user-global-styles-revisions</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-11T10:09:07.382Z"><code>[2023-04-11T10:09:07.382Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4666114531"><code>remove/smart-border-behavior</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-11T18:42:17.489Z"><code>[2023-04-11T18:42:17.489Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4670693174"><code>update/html-api-updates-from-core-self-closing-flag</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-11T20:11:35.553Z"><code>[2023-04-11T20:11:35.553Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4671340364"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-12T09:21:14.384Z"><code>[2023-04-12T09:21:14.384Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4676450651"><code>fix/block-toolbar-height</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-12T12:58:43.351Z"><code>[2023-04-12T12:58:43.351Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4677956393"><code>try/block-tools-invade-document-tools</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-12T17:11:20.919Z"><code>[2023-04-12T17:11:20.919Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4678658140"><code>fix/flaky-site-editor-writing-flow-tests</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-12T19:20:16.167Z"><code>[2023-04-12T19:20:16.167Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4681812586"><code>add/site-icon-animation-in-frame</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-13T03:13:48.871Z"><code>[2023-04-13T03:13:48.871Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4684959383"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-19T17:00:45.371Z"><code>[2023-04-19T17:00:45.371Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4745657883"><code>release/15.6</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><details>
<summary>
<time datetime="2023-04-19T23:19:55.068Z"><code>[2023-04-19T23:19:55.068Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4748567456"><code>release/15.6</code></a>.
</summary>
```
Error: Timed out 5000ms waiting for expect(received).toBeFocused()
Call log:
- expect.toBeFocused with timeout 5000ms
- waiting for locator('role=toolbar[name="Block tools"i]').locator('role=button[name="Site Title"i]')
- waiting for locator('role=toolbar[name="Block tools"i]').locator('role=button[name="Site Title"i]')
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/writing-flow.spec.js:40:38
```
</details><!-- /__TEST_RESULT__ -->
<!-- /__TEST_RESULTS_LIST__ -->
|
1.0
|
[Flaky Test] allows shift tabbing to the block toolbar from the first block - <!-- __META_DATA__:{} -->
**Flaky test detected. This is an auto-generated issue by GitHub Actions. Please do NOT edit this manually.**
## Test title
allows shift tabbing to the block toolbar from the first block
## Test path
`/test/e2e/specs/site-editor/writing-flow.spec.js`
## Errors
<!-- __TEST_RESULTS_LIST__ -->
<!-- __TEST_RESULT__ --><time datetime="2023-03-13T12:53:34.347Z"><code>[2023-03-13T12:53:34.347Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4404789928"><code>remove/lodash-set-core-data</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-14T01:46:16.054Z"><code>[2023-03-14T01:46:16.054Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4411129007"><code>try/grid-layout</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-14T19:43:09.734Z"><code>[2023-03-14T19:43:09.734Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4419341518"><code>tweak/latest-posts-panel-labels</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-15T02:20:42.977Z"><code>[2023-03-15T02:20:42.977Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4421941166"><code>refactor/block-json-selectors-api</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-15T13:50:37.924Z"><code>[2023-03-15T13:50:37.924Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4426740940"><code>refactor/ctx-get-styled-cn-lodash</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-15T16:43:28.576Z"><code>[2023-03-15T16:43:28.576Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4428441677"><code>update/svg-filter-frontend-output</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-15T16:51:16.106Z"><code>[2023-03-15T16:51:16.106Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4428532118"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-15T18:13:53.808Z"><code>[2023-03-15T18:13:53.808Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4429208252"><code>release/15.4</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-16T03:46:26.584Z"><code>[2023-03-16T03:46:26.584Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4433171734"><code>add/position-label-to-block-title-in-list-view</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-16T04:03:55.161Z"><code>[2023-03-16T04:03:55.161Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4433302468"><code>add/more-cover-block-unit-tests</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-16T20:27:02.718Z"><code>[2023-03-16T20:27:02.718Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4441104420"><code>update/svg-filter-frontend-output</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-16T23:52:19.720Z"><code>[2023-03-16T23:52:19.720Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4442524072"><code>add/more-cover-block-unit-tests</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T05:36:23.383Z"><code>[2023-03-17T05:36:23.383Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4444392341"><code>try/affix-knob-angle-picker-control</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T06:32:26.381Z"><code>[2023-03-17T06:32:26.381Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4444662512"><code>try/affix-knob-angle-picker-control</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T10:27:33.462Z"><code>[2023-03-17T10:27:33.462Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4446315177"><code>update/no-store-double-register</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T15:33:46.479Z"><code>[2023-03-17T15:33:46.479Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4448835977"><code>refactor/CustomGradientPicker-typescript</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T16:12:51.784Z"><code>[2023-03-17T16:12:51.784Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4449184008"><code>fix/color-picker-updates-in-gradients</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T16:14:58.068Z"><code>[2023-03-17T16:14:58.068Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4449187594"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T16:33:19.252Z"><code>[2023-03-17T16:33:19.252Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4449389586"><code>update/svg-filter-frontend-output</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T17:01:00.891Z"><code>[2023-03-17T17:01:00.891Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4449587331"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-17T18:38:17.661Z"><code>[2023-03-17T18:38:17.661Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4450374242"><code>try/affix-knob-angle-picker-control</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-19T08:11:08.957Z"><code>[2023-03-19T08:11:08.957Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4459563169"><code>remove/edit-navigation-leftovers</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-19T16:00:43.822Z"><code>[2023-03-19T16:00:43.822Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4461392032"><code>fix/textarea-input-block</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-20T08:36:34.497Z"><code>[2023-03-20T08:36:34.497Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4466009153"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-20T08:41:22.291Z"><code>[2023-03-20T08:41:22.291Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4466014209"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-20T08:44:56.711Z"><code>[2023-03-20T08:44:56.711Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4465986717"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-20T09:15:37.838Z"><code>[2023-03-20T09:15:37.838Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4466240362"><code>fix-39946</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-20T11:11:44.691Z"><code>[2023-03-20T11:11:44.691Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4467213059"><code>add-caption-gs-ui-take2</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-20T11:58:46.640Z"><code>[2023-03-20T11:58:46.640Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4467667901"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-20T14:38:30.740Z"><code>[2023-03-20T14:38:30.740Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4468704939"><code>fix/group-block-deprecation</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-20T17:35:05.153Z"><code>[2023-03-20T17:35:05.153Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4470878928"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-21T08:01:55.627Z"><code>[2023-03-21T08:01:55.627Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4476519200"><code>rnmobile/add-reassure-pt-2</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-21T11:03:41.799Z"><code>[2023-03-21T11:03:41.799Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4478040074"><code>update/consolidate-safari-scripts</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-21T11:30:48.733Z"><code>[2023-03-21T11:30:48.733Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4478251864"><code>add/color-panel</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-21T17:38:04.162Z"><code>[2023-03-21T17:38:04.162Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4481791515"><code>fix/48586</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-21T21:33:55.042Z"><code>[2023-03-21T21:33:55.042Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4483811946"><code>try/resolution-not-image-size</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-21T23:56:20.573Z"><code>[2023-03-21T23:56:20.573Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4483811946"><code>try/resolution-not-image-size</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T03:54:41.706Z"><code>[2023-03-22T03:54:41.706Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4486127277"><code>try/grid-layout</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T06:20:12.049Z"><code>[2023-03-22T06:20:12.049Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4486800784"><code>fix/image-dont-render-empty</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T09:26:40.761Z"><code>[2023-03-22T09:26:40.761Z]</code></time> Test passed after 2 failed attempts on <a href="https://github.com/WordPress/gutenberg/actions/runs/4487981160"><code>add/typography-support-to-time-to-read-block</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T10:19:01.003Z"><code>[2023-03-22T10:19:01.003Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4488486177"><code>fonts-api/remove-parameter</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T10:32:43.469Z"><code>[2023-03-22T10:32:43.469Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4488580734"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T12:48:55.071Z"><code>[2023-03-22T12:48:55.071Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4489732565"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T14:56:34.315Z"><code>[2023-03-22T14:56:34.315Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4490916635"><code>move-filters-out-of-colors-section</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T16:50:56.970Z"><code>[2023-03-22T16:50:56.970Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4492099207"><code>refactor/GradientPicker-typescript</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T20:46:21.977Z"><code>[2023-03-22T20:46:21.977Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4494093026"><code>fix/48586</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-22T23:07:07.544Z"><code>[2023-03-22T23:07:07.544Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4495066470"><code>add/more-cover-block-unit-tests</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-23T05:47:47.024Z"><code>[2023-03-23T05:47:47.024Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4497336703"><code>try/grid-layout</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-23T08:21:29.215Z"><code>[2023-03-23T08:21:29.215Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4498197419"><code>rnmobile/add-reassure-pt-2</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-23T09:56:23.509Z"><code>[2023-03-23T09:56:23.509Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4483811946"><code>try/resolution-not-image-size</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-23T12:04:13.148Z"><code>[2023-03-23T12:04:13.148Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4500070080"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-23T13:08:10.823Z"><code>[2023-03-23T13:08:10.823Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4500604660"><code>remove/mobile-custom-waitfor</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-23T14:48:23.243Z"><code>[2023-03-23T14:48:23.243Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4501513054"><code>try/resolution-not-image-size</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-23T17:05:45.951Z"><code>[2023-03-23T17:05:45.951Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4502924413"><code>try/use-dedicated-rest-to-get-nav-fallbacks</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-23T18:35:07.831Z"><code>[2023-03-23T18:35:07.831Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4503717638"><code>refactor/ColorPicker-typescript</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-24T06:07:37.992Z"><code>[2023-03-24T06:07:37.992Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4508136757"><code>update/preformatted-spacing</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-24T11:40:06.945Z"><code>[2023-03-24T11:40:06.945Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4510509364"><code>fix/start-template-options-missing-focus-style</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-24T12:35:31.967Z"><code>[2023-03-24T12:35:31.967Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4510509364"><code>fix/start-template-options-missing-focus-style</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-24T13:19:00.457Z"><code>[2023-03-24T13:19:00.457Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4511342470"><code>schema/stiky-minheight</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-24T15:51:38.645Z"><code>[2023-03-24T15:51:38.645Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4512708200"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-27T07:12:54.840Z"><code>[2023-03-27T07:12:54.840Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4529492370"><code>rnmobile/add-reassure-pt-2</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-27T08:25:16.302Z"><code>[2023-03-27T08:25:16.302Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4530015379"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-27T23:49:39.046Z"><code>[2023-03-27T23:49:39.046Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4537466114"><code>fix/unstable-disable-layout-classnames-in-group-block</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-28T00:21:17.643Z"><code>[2023-03-28T00:21:17.643Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4537707599"><code>fix/grid-in-classic-themes</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-28T08:00:22.863Z"><code>[2023-03-28T08:00:22.863Z]</code></time> Test passed after 2 failed attempts on <a href="https://github.com/WordPress/gutenberg/actions/runs/4540405026"><code>update/list-view-more-menu</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-28T10:53:07.550Z"><code>[2023-03-28T10:53:07.550Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4541874680"><code>add/commands</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-28T16:23:35.654Z"><code>[2023-03-28T16:23:35.654Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4545070030"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-29T05:42:48.273Z"><code>[2023-03-29T05:42:48.273Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4550419545"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-29T09:31:55.182Z"><code>[2023-03-29T09:31:55.182Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4552194692"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-29T09:33:18.351Z"><code>[2023-03-29T09:33:18.351Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4552110263"><code>add/commands</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-29T11:31:52.407Z"><code>[2023-03-29T11:31:52.407Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4553206755"><code>try/block-tools-marry-document-tools</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-29T17:17:57.354Z"><code>[2023-03-29T17:17:57.354Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4555764795"><code>refactor/perf-tests-tmp-folder</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-29T17:19:19.323Z"><code>[2023-03-29T17:19:19.323Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4555754701"><code>try/block-tools-marry-document-tools</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-30T09:48:26.099Z"><code>[2023-03-30T09:48:26.099Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4562651740"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-30T09:57:12.737Z"><code>[2023-03-30T09:57:12.737Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4562710990"><code>fix/show-ui-to-change-custom-links-on-sidebar-navigation</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-30T13:04:48.315Z"><code>[2023-03-30T13:04:48.315Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4564006697"><code>update/block-supports-dependencies</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-30T14:12:51.983Z"><code>[2023-03-30T14:12:51.983Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4565008524"><code>rnmobile/release_1.92.0</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-30T14:38:42.531Z"><code>[2023-03-30T14:38:42.531Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4565255936"><code>try/use-dedicated-rest-to-get-nav-fallbacks</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-30T15:09:12.380Z"><code>[2023-03-30T15:09:12.380Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4565631389"><code>update/file-block-text-formatting</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-30T15:46:34.731Z"><code>[2023-03-30T15:46:34.731Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4566033750"><code>update/template-title-in-sidebar</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-30T19:07:49.424Z"><code>[2023-03-30T19:07:49.424Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4567826409"><code>fix/selectors-api-use-in-duotone</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-31T03:01:55.500Z"><code>[2023-03-31T03:01:55.500Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4570919779"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-31T03:02:18.126Z"><code>[2023-03-31T03:02:18.126Z]</code></time> Test passed after 2 failed attempts on <a href="https://github.com/WordPress/gutenberg/actions/runs/4570941202"><code>add/color-options-to-time-to-read-block</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-31T04:54:18.626Z"><code>[2023-03-31T04:54:18.626Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4571513210"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-31T06:17:59.703Z"><code>[2023-03-31T06:17:59.703Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4572008043"><code>try/list-view-allow-drag-to-parent-level</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-31T06:38:35.187Z"><code>[2023-03-31T06:38:35.187Z]</code></time> Test passed after 2 failed attempts on <a href="https://github.com/WordPress/gutenberg/actions/runs/4572068177"><code>add/details-summary-block</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-31T07:20:10.817Z"><code>[2023-03-31T07:20:10.817Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4572345163"><code>add/details-summary-block</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-03-31T18:44:55.146Z"><code>[2023-03-31T18:44:55.146Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4577931577"><code>add/commands</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-01T14:28:30.860Z"><code>[2023-04-01T14:28:30.860Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4583536972"><code>columns/prevent-removal-column</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-01T17:01:32.535Z"><code>[2023-04-01T17:01:32.535Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4584150055"><code>fix/build-comments</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-02T07:57:40.983Z"><code>[2023-04-02T07:57:40.983Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4587535171"><code>media-text/fix-deprecation-v2</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-03T03:50:57.314Z"><code>[2023-04-03T03:50:57.314Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4592581935"><code>try/minimal-margin</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-03T05:35:43.398Z"><code>[2023-04-03T05:35:43.398Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4593111001"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-03T06:12:20.047Z"><code>[2023-04-03T06:12:20.047Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4593271554"><code>columns/prevent-removal-column</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-03T08:24:09.145Z"><code>[2023-04-03T08:24:09.145Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4594182993"><code>fix/start-template-options-missing-focus-style</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-03T09:06:53.705Z"><code>[2023-04-03T09:06:53.705Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4594182993"><code>fix/start-template-options-missing-focus-style</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-03T10:25:31.459Z"><code>[2023-04-03T10:25:31.459Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4595244702"><code>rnmobile/support-post-request</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-03T17:14:59.469Z"><code>[2023-04-03T17:14:59.469Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4599193444"><code>fix/avoid-empty-gallery-block-error</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-03T17:39:20.292Z"><code>[2023-04-03T17:39:20.292Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4580712698"><code>tweak/simplify-remove-block-label</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-04T04:55:25.291Z"><code>[2023-04-04T04:55:25.291Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4603905724"><code>add/details-summary-block</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-04T10:36:57.029Z"><code>[2023-04-04T10:36:57.029Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4606520962"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-04T15:18:42.265Z"><code>[2023-04-04T15:18:42.265Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4609083229"><code>try/block-tools-marry-document-tools</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-04T16:58:04.647Z"><code>[2023-04-04T16:58:04.647Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4610017682"><code>try/radix-dropdown</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-04T18:40:34.486Z"><code>[2023-04-04T18:40:34.486Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4610949613"><code>chore/components-changelog</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-05T05:24:17.099Z"><code>[2023-04-05T05:24:17.099Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4615028665"><code>update/remove-wp-block-level-preset-style-filters</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-06T02:51:42.055Z"><code>[2023-04-06T02:51:42.055Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4624780477"><code>add/root-client-id-to-list-view</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-06T04:13:26.703Z"><code>[2023-04-06T04:13:26.703Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4624780477"><code>add/root-client-id-to-list-view</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-06T08:01:51.752Z"><code>[2023-04-06T08:01:51.752Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4626561168"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-06T09:56:29.143Z"><code>[2023-04-06T09:56:29.143Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4627378477"><code>add/commands</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-06T14:24:06.634Z"><code>[2023-04-06T14:24:06.634Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4629651383"><code>update-boding-guidelines-experimental</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-07T00:20:18.217Z"><code>[2023-04-07T00:20:18.217Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4633977499"><code>publish-plugin-types</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-07T11:52:15.443Z"><code>[2023-04-07T11:52:15.443Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4637763867"><code>try/block-tools-invade-document-tools</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-07T12:39:54.446Z"><code>[2023-04-07T12:39:54.446Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4638016563"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-09T14:36:58.568Z"><code>[2023-04-09T14:36:58.568Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4650901329"><code>add/image-drop-html</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-10T14:52:49.610Z"><code>[2023-04-10T14:52:49.610Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4658263501"><code>component-changelog-check-exclude-mobile</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-10T15:02:10.699Z"><code>[2023-04-10T15:02:10.699Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4658311504"><code>test-changelog-ci-changes</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-10T17:16:41.963Z"><code>[2023-04-10T17:16:41.963Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4659330461"><code>test-changelog-ci-changes</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-10T18:32:14.010Z"><code>[2023-04-10T18:32:14.010Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4659841409"><code>rnmobil/add-viewport-props-to-sandbox</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-10T19:39:40.610Z"><code>[2023-04-10T19:39:40.610Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4660074886"><code>rnmobile/release_1.92.1</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-10T19:55:46.712Z"><code>[2023-04-10T19:55:46.712Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4660074886"><code>rnmobile/release_1.92.1</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-11T01:09:56.548Z"><code>[2023-04-11T01:09:56.548Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4662592870"><code>release/15.5</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-11T02:24:37.934Z"><code>[2023-04-11T02:24:37.934Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4662975713"><code>fix/time-to-read-translate</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-11T02:36:16.797Z"><code>[2023-04-11T02:36:16.797Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4663065367"><code>fix/refactor-group-duotone-output</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-11T06:10:22.490Z"><code>[2023-04-11T06:10:22.490Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4664239454"><code>try/user-global-styles-revisions</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-11T10:09:07.382Z"><code>[2023-04-11T10:09:07.382Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4666114531"><code>remove/smart-border-behavior</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-11T18:42:17.489Z"><code>[2023-04-11T18:42:17.489Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4670693174"><code>update/html-api-updates-from-core-self-closing-flag</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-11T20:11:35.553Z"><code>[2023-04-11T20:11:35.553Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4671340364"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-12T09:21:14.384Z"><code>[2023-04-12T09:21:14.384Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4676450651"><code>fix/block-toolbar-height</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-12T12:58:43.351Z"><code>[2023-04-12T12:58:43.351Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4677956393"><code>try/block-tools-invade-document-tools</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-12T17:11:20.919Z"><code>[2023-04-12T17:11:20.919Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4678658140"><code>fix/flaky-site-editor-writing-flow-tests</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-12T19:20:16.167Z"><code>[2023-04-12T19:20:16.167Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4681812586"><code>add/site-icon-animation-in-frame</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-13T03:13:48.871Z"><code>[2023-04-13T03:13:48.871Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4684959383"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-04-19T17:00:45.371Z"><code>[2023-04-19T17:00:45.371Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4745657883"><code>release/15.6</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><details>
<summary>
<time datetime="2023-04-19T23:19:55.068Z"><code>[2023-04-19T23:19:55.068Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4748567456"><code>release/15.6</code></a>.
</summary>
```
Error: Timed out 5000ms waiting for expect(received).toBeFocused()
Call log:
- expect.toBeFocused with timeout 5000ms
- waiting for locator('role=toolbar[name="Block tools"i]').locator('role=button[name="Site Title"i]')
- waiting for locator('role=toolbar[name="Block tools"i]').locator('role=button[name="Site Title"i]')
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/writing-flow.spec.js:40:38
```
</details><!-- /__TEST_RESULT__ -->
<!-- /__TEST_RESULTS_LIST__ -->
|
non_usab
|
allows shift tabbing to the block toolbar from the first block flaky test detected this is an auto generated issue by github actions please do not edit this manually test title allows shift tabbing to the block toolbar from the first block test path test specs site editor writing flow spec js errors test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempts on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempts on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempts on test passed after failed attempt on test passed after failed attempt on test passed after failed attempts on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on a href error timed out waiting for expect received tobefocused call log expect tobefocused with timeout waiting for locator role toolbar locator role button waiting for locator role toolbar locator role button at home runner work gutenberg gutenberg test specs site editor writing flow spec js
| 0
|
14,640
| 9,382,099,335
|
IssuesEvent
|
2019-04-04 21:21:52
|
TheCacophonyProject/cacophonometer
|
https://api.github.com/repos/TheCacophonyProject/cacophonometer
|
closed
|
Buttons are hard to read in poor light conditions
|
usability
|
I was setting up the phone with a bright light - similar to outside and I found the midgreen button with black text particularly hard to read. The white text is slightly better but not great. I think we need to make sure we have high contrasting colour scheme, so that the app works well out side.
Also there is a problem with the "OK" on the help screens - I totally didn't see it and couldn't work out how to close this dialog. It might be more consistent with android gui to have an X at the top right of the dialog. Make it much bolder as it's really annoying when you don't know how to close it.
|
True
|
Buttons are hard to read in poor light conditions - I was setting up the phone with a bright light - similar to outside and I found the midgreen button with black text particularly hard to read. The white text is slightly better but not great. I think we need to make sure we have high contrasting colour scheme, so that the app works well out side.
Also there is a problem with the "OK" on the help screens - I totally didn't see it and couldn't work out how to close this dialog. It might be more consistent with android gui to have an X at the top right of the dialog. Make it much bolder as it's really annoying when you don't know how to close it.
|
usab
|
buttons are hard to read in poor light conditions i was setting up the phone with a bright light similar to outside and i found the midgreen button with black text particularly hard to read the white text is slightly better but not great i think we need to make sure we have high contrasting colour scheme so that the app works well out side also there is a problem with the ok on the help screens i totally didn t see it and couldn t work out how to close this dialog it might be more consistent with android gui to have an x at the top right of the dialog make it much bolder as it s really annoying when you don t know how to close it
| 1
|
4,136
| 6,725,260,915
|
IssuesEvent
|
2017-10-17 04:05:06
|
bwsw/cloudstack-ui
|
https://api.github.com/repos/bwsw/cloudstack-ui
|
closed
|
Add "Save VM password for all VMs" option
|
Epic requirement
|
Create a modal dialog "Save for all VMs" on save password to avoid further questions.
Add "Save VM password by default" section to Settings to set and unset this option
Acceptance criteria:
1. There is a SAVE button near a password
- in the "After VM creation" dialog (Epic #2)
- in the password resetting dialog for VM
2. Clicking on SAVE button opens a dialog (over another one that was opened) with a suggestion to save a password for all VMs (see the 1st mockup attached).
3. There are two options depending on what a user clicks:
- If NO was clicked - This dialog appears every time a user clicks a save password button.
- If YES was clicked - A save password button disappears and passwords for VM are saved automatically.
4. After YES or NO was clicked, the dialog closes and a user gets back to the previous dialog.
5. There should be "Save VM password by default" section in Settings (Security (see the 2nd mockup attached). User should have a possibility to set and unset this option there (so the button will appear and disappear in the dialogs)
Mockup
|
1.0
|
Add "Save VM password for all VMs" option - Create a modal dialog "Save for all VMs" on save password to avoid further questions.
Add "Save VM password by default" section to Settings to set and unset this option
Acceptance criteria:
1. There is a SAVE button near a password
- in the "After VM creation" dialog (Epic #2)
- in the password resetting dialog for VM
2. Clicking on SAVE button opens a dialog (over another one that was opened) with a suggestion to save a password for all VMs (see the 1st mockup attached).
3. There are two options depending on what a user clicks:
- If NO was clicked - This dialog appears every time a user clicks a save password button.
- If YES was clicked - A save password button disappears and passwords for VM are saved automatically.
4. After YES or NO was clicked, the dialog closes and a user gets back to the previous dialog.
5. There should be "Save VM password by default" section in Settings (Security (see the 2nd mockup attached). User should have a possibility to set and unset this option there (so the button will appear and disappear in the dialogs)
Mockup
|
non_usab
|
add save vm password for all vms option create a modal dialog save for all vms on save password to avoid further questions add save vm password by default section to settings to set and unset this option acceptance criteria there is a save button near a password in the after vm creation dialog epic in the password resetting dialog for vm clicking on save button opens a dialog over another one that was opened with a suggestion to save a password for all vms see the mockup attached there are two options depending on what a user clicks if no was clicked this dialog appears every time a user clicks a save password button if yes was clicked a save password button disappears and passwords for vm are saved automatically after yes or no was clicked the dialog closes and a user gets back to the previous dialog there should be save vm password by default section in settings security see the mockup attached user should have a possibility to set and unset this option there so the button will appear and disappear in the dialogs mockup
| 0
|
65,921
| 16,505,359,008
|
IssuesEvent
|
2021-05-25 18:35:12
|
LLNL/serac
|
https://api.github.com/repos/LLNL/serac
|
closed
|
Guard Code Checks
|
CS bug build
|
This should not be run by our customers so we should be guarding this against whether the individual executables are found:
https://github.com/LLNL/serac/blob/b5191c08fbf2cb106491489bce40ecfde0d41b6f/CMakeLists.txt#L87-L89
@goxberry ran into an issue when Serac is installed via Spack.
|
1.0
|
Guard Code Checks - This should not be run by our customers so we should be guarding this against whether the individual executables are found:
https://github.com/LLNL/serac/blob/b5191c08fbf2cb106491489bce40ecfde0d41b6f/CMakeLists.txt#L87-L89
@goxberry ran into an issue when Serac is installed via Spack.
|
non_usab
|
guard code checks this should not be run by our customers so we should be guarding this against whether the individual executables are found goxberry ran into an issue when serac is installed via spack
| 0
|
16,620
| 11,141,416,445
|
IssuesEvent
|
2019-12-21 22:36:06
|
godotengine/godot
|
https://api.github.com/repos/godotengine/godot
|
closed
|
Rigidbody. Number of contacts reported < 0?
|
bug topic:editor usability
|
**Godot version:**
3.X
**OS/device including version:**
Any?
**Issue description:**
It can be set -1? Or in editor settings not set min-max value?
This not critical, but ... strange.
Or if it set -1, then one substract from contacts reported? (Don`t know how ^_^)
If it set -X... unpredicteble logick results.
|
True
|
Rigidbody. Number of contacts reported < 0? - **Godot version:**
3.X
**OS/device including version:**
Any?
**Issue description:**
It can be set -1? Or in editor settings not set min-max value?
This not critical, but ... strange.
Or if it set -1, then one substract from contacts reported? (Don`t know how ^_^)
If it set -X... unpredicteble logick results.
|
usab
|
rigidbody number of contacts reported godot version x os device including version any issue description it can be set or in editor settings not set min max value this not critical but strange or if it set then one substract from contacts reported don t know how if it set x unpredicteble logick results
| 1
|
77,971
| 15,569,907,612
|
IssuesEvent
|
2021-03-17 01:16:17
|
Killy85/game_ai_trainer
|
https://api.github.com/repos/Killy85/game_ai_trainer
|
opened
|
WS-2021-0011 (Medium) detected in bleach-3.1.0-py2.py3-none-any.whl
|
security vulnerability
|
## WS-2021-0011 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bleach-3.1.0-py2.py3-none-any.whl</b></p></summary>
<p>An easy safelist-based HTML-sanitizing tool.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/ab/05/27e1466475e816d3001efb6e0a85a819be17411420494a1e602c36f8299d/bleach-3.1.0-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/ab/05/27e1466475e816d3001efb6e0a85a819be17411420494a1e602c36f8299d/bleach-3.1.0-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /game_ai_trainer/requirements.txt</p>
<p>Path to vulnerable library: teSource-ArchiveExtractor_da03aa19-8c81-4d9c-9496-c373589d1ea2/20190506071543_44724/20190506071259_depth_0/59/bleach-3.1.0-py2.py3-none-any/bleach</p>
<p>
Dependency Hierarchy:
- :x: **bleach-3.1.0-py2.py3-none-any.whl** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Mozilla Bleach before 3.3.0, a mutation XSS in bleach.clean when p, br, style, title, noscript, script, textarea, noframes, iframe, or xmp and either svg or math tags are whitelisted and the keyword argument strip_comments=False.
<p>Publish Date: 2021-02-01
<p>URL: <a href=https://github.com/mozilla/bleach/commit/79b7a3c5e56a09d1d323a5006afa59b56162eb13>WS-2021-0011</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-vv2x-vrpj-qqpq">https://github.com/advisories/GHSA-vv2x-vrpj-qqpq</a></p>
<p>Release Date: 2021-02-01</p>
<p>Fix Resolution: bleach - 3.3.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
WS-2021-0011 (Medium) detected in bleach-3.1.0-py2.py3-none-any.whl - ## WS-2021-0011 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bleach-3.1.0-py2.py3-none-any.whl</b></p></summary>
<p>An easy safelist-based HTML-sanitizing tool.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/ab/05/27e1466475e816d3001efb6e0a85a819be17411420494a1e602c36f8299d/bleach-3.1.0-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/ab/05/27e1466475e816d3001efb6e0a85a819be17411420494a1e602c36f8299d/bleach-3.1.0-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /game_ai_trainer/requirements.txt</p>
<p>Path to vulnerable library: teSource-ArchiveExtractor_da03aa19-8c81-4d9c-9496-c373589d1ea2/20190506071543_44724/20190506071259_depth_0/59/bleach-3.1.0-py2.py3-none-any/bleach</p>
<p>
Dependency Hierarchy:
- :x: **bleach-3.1.0-py2.py3-none-any.whl** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Mozilla Bleach before 3.3.0, a mutation XSS in bleach.clean when p, br, style, title, noscript, script, textarea, noframes, iframe, or xmp and either svg or math tags are whitelisted and the keyword argument strip_comments=False.
<p>Publish Date: 2021-02-01
<p>URL: <a href=https://github.com/mozilla/bleach/commit/79b7a3c5e56a09d1d323a5006afa59b56162eb13>WS-2021-0011</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-vv2x-vrpj-qqpq">https://github.com/advisories/GHSA-vv2x-vrpj-qqpq</a></p>
<p>Release Date: 2021-02-01</p>
<p>Fix Resolution: bleach - 3.3.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_usab
|
ws medium detected in bleach none any whl ws medium severity vulnerability vulnerable library bleach none any whl an easy safelist based html sanitizing tool library home page a href path to dependency file game ai trainer requirements txt path to vulnerable library tesource archiveextractor depth bleach none any bleach dependency hierarchy x bleach none any whl vulnerable library vulnerability details in mozilla bleach before a mutation xss in bleach clean when p br style title noscript script textarea noframes iframe or xmp and either svg or math tags are whitelisted and the keyword argument strip comments false publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution bleach step up your open source security game with whitesource
| 0
|
130,404
| 18,070,688,509
|
IssuesEvent
|
2021-09-21 02:18:55
|
arendst/Tasmota
|
https://api.github.com/repos/arendst/Tasmota
|
closed
|
Unable to update the Topic Field - reverts to default
|
duplicated troubleshooting as designed
|
<!-- Thanks for reporting a problem for this project. READ THIS FIRST:
This issue template is meant to REPORT Tasmota software PROBLEMS ONLY
Please DO NOT OPEN AN ISSUE:
- If your Tasmota version is not the latest from the development branch, please update your device before submitting your issue. Your problem might already be solved. The latest precompiled binaries of Tasmota can be downloaded from http://ota.tasmota.com/tasmota/
- If you have an issue when flashing was done via Tuya Convert, please address it to Tuya Convert Team
- If your issue is a flashing issue, please address it to the [Tasmota Support Chat](https://discord.gg/Ks2Kzd4)
- If your issue is compilation problem, please address it to the [Tasmota Support Chat](https://discord.gg/Ks2Kzd4)
- If your issue has been addressed before (i.e., duplicated issue), please ask in the original issue
- If your issue is a Wi-Fi problem or MQTT problem, please try the steps provided in the [FAQ](https://tasmota.github.io/docs/FAQ) and [Troubleshooting](https://tasmota.github.io/docs/Troubleshooting)
Please take a few minutes to complete the requested information below. Our ability to provide assistance is greatly hampered without it. The details requested potentially affect which options to pursue. The small amount of time you spend completing the template will also help the volunteers providing the assistance to you to reduce the time required to help you.
DO NOT DELETE ANY TEXT from this template! Otherwise the issue will be auto-closed.
-->
### PROBLEM DESCRIPTION
_A clear and concise description of what the problem is._
I a unable to update the Topic Field on Versions 9.5.0.0 and 9.5.0.8
The field is reset back to default I am trying to set topic as P81_BenchLamp or P1-BenchLamp.
Changing the topic to sexybeast DOES WORK. But that DOESN'T work for me.
### REQUESTED INFORMATION
_Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!_
- [ ] Read the [Contributing Guide and Policy](https://github.com/arendst/Tasmota/blob/development/CONTRIBUTING.md) and [the Code of Conduct](https://github.com/arendst/Tasmota/blob/development/CODE_OF_CONDUCT.md)
- [ ] Searched the problem in [issues](https://github.com/arendst/Tasmota/issues)
- [ ] Searched the problem in [discussions](https://github.com/arendst/Tasmota/discussions)
- [ ] Searched the problem in the [docs](https://tasmota.github.io/docs/FAQ)
- [ ] Searched the problem in the [chat](https://discord.gg/Ks2Kzd4)
- [ ] Device used (e.g., Sonoff Basic): _LITESUN LA-WF7____
- [ ] Tasmota binary firmware version number used: 9.5.0 also 9.5.0.8_____
- [ ] Pre-compiled YES
- [ ] Self-compiled
- [ ] Flashing tools used: _____
- [ ] Provide the output of command: `Backlog Template; Module; GPIO 255`:
```lua
Configuration output here:
06:03:49.896 MQT: stat/sexybeast/RESULT = {"NAME":"LITESUN LA-WF7","GPIO":[0,320,0,32,2720,2656,0,0,2624,321,224,0,0,0],"FLAG":0,"BASE":18}
06:03:50.105 MQT: stat/sexybeast/RESULT = {"Module":{"0":"LITESUN LA-WF7"}}
06:03:50.361 MQT: stat/sexybeast/RESULT = {"GPIO0":{"0":"None"},"GPIO1":{"320":"Led_i1"},"GPIO2":{"0":"None"},"GPIO3":{"32":"Button1"},"GPIO4":{"2720":"BL0937 CF"},"GPIO5":{"2656":"HLWBL CF1"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO12":{"2624":"HLWBL SEL_i"},"GPIO13":{"321":"Led_i2"},"GPIO14":{"224":"Relay1"},"GPIO15":{"0":"None"},"GPIO16":{"0":"None"},"GPIO17":{"0":"None"}}
```
- [ ] If using rules, provide the output of this command: `Backlog Rule1; Rule2; Rule3`:
```lua
Rules output here:
```
- [ ] Provide the output of this command: `Status 0`:
```lua
STATUS 0 output here:
05:53:44.516 CMD: Status 0`: ```lua
05:53:44.524 MQT: stat/tasmota_B10C83/STATUS = {"Status":{"Module":0,"DeviceName":"P81_BenchLamp","FriendlyName":["P81_BenchLamp"],"Topic":"tasmota_B10C83","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":0,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0}}
05:53:44.529 MQT: stat/tasmota_B10C83/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/tasmota.bin.gz","RestartReason":"Software/System restart","Uptime":"0T00:04:47","StartupUTC":"2021-09-19T04:48:57","Sleep":50,"CfgHolder":4617,"BootCount":204,"BCResetTime":"2020-08-03T07:01:19","SaveCount":1062,"SaveAddress":"F8000"}}
05:53:44.534 MQT: stat/tasmota_B10C83/STATUS2 = {"StatusFWR":{"Version":"9.5.0(tasmota)","BuildDateTime":"2021-06-17T08:26:35","Boot":31,"Core":"2_7_4_9","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8285","CR":"382/699"}}
05:53:44.539 MQT: stat/tasmota_B10C83/STATUS3 = {"StatusLOG":{"SerialLog":0,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["ToEjAm","Step31"],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00008009","2805C8000100060000005A0A000000000000","00000080","00006000","00004000"]}}
05:53:44.552 MQT: stat/tasmota_B10C83/STATUS4 = {"StatusMEM":{"ProgramSize":607,"Free":396,"Heap":24,"ProgramFlashSize":1024,"FlashSize":1024,"FlashChipId":"144051","FlashFrequency":40,"FlashMode":3,"Features":["00000809","8FDAC787","04368001","000000CF","010013C0","C000F981","00004004","00001000","00000020"],"Drivers":"1,2,3,4,5,6,7,8,9,10,12,16,18,19,20,21,22,24,26,27,29,30,35,37,45","Sensors":"1,2,3,4,5,6"}}
05:53:44.562 MQT: stat/tasmota_B10C83/STATUS5 = {"StatusNET":{"Hostname":"P81_BenchLamp","IPAddress":"192.168.1.81","Gateway":"192.168.1.254","Subnetmask":"255.255.255.0","DNSServer":"192.168.1.254","Mac":"DC:4F:22:B1:0C:83","Webserver":2,"WifiConfig":2,"WifiPower":17.0}}
05:53:44.568 MQT: stat/tasmota_B10C83/STATUS6 = {"StatusMQT":{"MqttHost":"192.168.1.126","MqttPort":1883,"MqttClientMask":"P81_BenchLamp","MqttClient":"P81_BenchLamp","MqttUser":"DVES_USER","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
05:53:44.574 MQT: stat/tasmota_B10C83/STATUS7 = {"StatusTIM":{"UTC":"2021-09-19T04:53:44","Local":"2021-09-19T05:53:44","StartDST":"2021-03-28T02:00:00","EndDST":"2021-10-31T03:00:00","Timezone":"+01:00","Sunrise":"06:33","Sunset":"18:54"}}
05:53:44.579 MQT: stat/tasmota_B10C83/STATUS9 = {"StatusPTH":{"PowerDelta":[0,0,0],"PowerLow":0,"PowerHigh":0,"VoltageLow":0,"VoltageHigh":0,"CurrentLow":0,"CurrentHigh":0}}
05:53:44.586 MQT: stat/tasmota_B10C83/STATUS10 = {"StatusSNS":{"Time":"2021-09-19T05:53:44","ENERGY":{"TotalStartTime":"2020-07-25T05:45:47","Total":10.048,"Yesterday":0.000,"Today":0.000,"Power":0,"ApparentPower":0,"ReactivePower":0,"Factor":0.00,"Voltage":0,"Current":0.000}}}
05:53:44.592 MQT: stat/tasmota_B10C83/STATUS11 = {"StatusSTS":{"Time":"2021-09-19T05:53:44","Uptime":"0T00:04:47","UptimeSec":287,"Heap":24,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":29,"MqttCount":1,"POWER":"OFF","Wifi":{"AP":1,"SSId":"ToEjAm","BSSId":"24:5A:4C:1A:66:59","Channel":6,"Mode":"11n","RSSI":62,"Signal":-69,"LinkCount":1,"Downtime":"0T00:00:04"}}}
```
- [ ] Set `weblog` to 4 and then, when you experience your issue, provide the output of the Console log:
```lua
Console output here:
```
### TO REPRODUCE
_Steps to reproduce the behavior:_
update the MQTT Topic field to something with an underscore, or a dash and caps
the result is field reset to default
### EXPECTED BEHAVIOUR
_A clear and concise description of what you expected to happen._
I expected to be able to use the device name as the topic. If the device name is legal then it should also be fine for topic. I was using P81_BenchLamp as topic. It conveys to me that it is a Plug Module at 192.168.1.81 with a friendly name.
tasmota_2a4d13 is not useful when configuring subscriptions.
### SCREENSHOTS
_If applicable, add screenshots to help explain your problem._
### ADDITIONAL CONTEXT
_Add any other context about the problem here._
I am using this in Homeseer as well as Home Assistant
Thanks for the great work ! Even though I am bitchin I am grateful for your talents.
**(Please, remember to close the issue when the problem has been addressed)**
|
1.0
|
Unable to update the Topic Field - reverts to default - <!-- Thanks for reporting a problem for this project. READ THIS FIRST:
This issue template is meant to REPORT Tasmota software PROBLEMS ONLY
Please DO NOT OPEN AN ISSUE:
- If your Tasmota version is not the latest from the development branch, please update your device before submitting your issue. Your problem might already be solved. The latest precompiled binaries of Tasmota can be downloaded from http://ota.tasmota.com/tasmota/
- If you have an issue when flashing was done via Tuya Convert, please address it to Tuya Convert Team
- If your issue is a flashing issue, please address it to the [Tasmota Support Chat](https://discord.gg/Ks2Kzd4)
- If your issue is compilation problem, please address it to the [Tasmota Support Chat](https://discord.gg/Ks2Kzd4)
- If your issue has been addressed before (i.e., duplicated issue), please ask in the original issue
- If your issue is a Wi-Fi problem or MQTT problem, please try the steps provided in the [FAQ](https://tasmota.github.io/docs/FAQ) and [Troubleshooting](https://tasmota.github.io/docs/Troubleshooting)
Please take a few minutes to complete the requested information below. Our ability to provide assistance is greatly hampered without it. The details requested potentially affect which options to pursue. The small amount of time you spend completing the template will also help the volunteers providing the assistance to you to reduce the time required to help you.
DO NOT DELETE ANY TEXT from this template! Otherwise the issue will be auto-closed.
-->
### PROBLEM DESCRIPTION
_A clear and concise description of what the problem is._
I a unable to update the Topic Field on Versions 9.5.0.0 and 9.5.0.8
The field is reset back to default I am trying to set topic as P81_BenchLamp or P1-BenchLamp.
Changing the topic to sexybeast DOES WORK. But that DOESN'T work for me.
### REQUESTED INFORMATION
_Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!_
- [ ] Read the [Contributing Guide and Policy](https://github.com/arendst/Tasmota/blob/development/CONTRIBUTING.md) and [the Code of Conduct](https://github.com/arendst/Tasmota/blob/development/CODE_OF_CONDUCT.md)
- [ ] Searched the problem in [issues](https://github.com/arendst/Tasmota/issues)
- [ ] Searched the problem in [discussions](https://github.com/arendst/Tasmota/discussions)
- [ ] Searched the problem in the [docs](https://tasmota.github.io/docs/FAQ)
- [ ] Searched the problem in the [chat](https://discord.gg/Ks2Kzd4)
- [ ] Device used (e.g., Sonoff Basic): _LITESUN LA-WF7____
- [ ] Tasmota binary firmware version number used: 9.5.0 also 9.5.0.8_____
- [ ] Pre-compiled YES
- [ ] Self-compiled
- [ ] Flashing tools used: _____
- [ ] Provide the output of command: `Backlog Template; Module; GPIO 255`:
```lua
Configuration output here:
06:03:49.896 MQT: stat/sexybeast/RESULT = {"NAME":"LITESUN LA-WF7","GPIO":[0,320,0,32,2720,2656,0,0,2624,321,224,0,0,0],"FLAG":0,"BASE":18}
06:03:50.105 MQT: stat/sexybeast/RESULT = {"Module":{"0":"LITESUN LA-WF7"}}
06:03:50.361 MQT: stat/sexybeast/RESULT = {"GPIO0":{"0":"None"},"GPIO1":{"320":"Led_i1"},"GPIO2":{"0":"None"},"GPIO3":{"32":"Button1"},"GPIO4":{"2720":"BL0937 CF"},"GPIO5":{"2656":"HLWBL CF1"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO12":{"2624":"HLWBL SEL_i"},"GPIO13":{"321":"Led_i2"},"GPIO14":{"224":"Relay1"},"GPIO15":{"0":"None"},"GPIO16":{"0":"None"},"GPIO17":{"0":"None"}}
```
- [ ] If using rules, provide the output of this command: `Backlog Rule1; Rule2; Rule3`:
```lua
Rules output here:
```
- [ ] Provide the output of this command: `Status 0`:
```lua
STATUS 0 output here:
05:53:44.516 CMD: Status 0`: ```lua
05:53:44.524 MQT: stat/tasmota_B10C83/STATUS = {"Status":{"Module":0,"DeviceName":"P81_BenchLamp","FriendlyName":["P81_BenchLamp"],"Topic":"tasmota_B10C83","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":0,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0}}
05:53:44.529 MQT: stat/tasmota_B10C83/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/tasmota.bin.gz","RestartReason":"Software/System restart","Uptime":"0T00:04:47","StartupUTC":"2021-09-19T04:48:57","Sleep":50,"CfgHolder":4617,"BootCount":204,"BCResetTime":"2020-08-03T07:01:19","SaveCount":1062,"SaveAddress":"F8000"}}
05:53:44.534 MQT: stat/tasmota_B10C83/STATUS2 = {"StatusFWR":{"Version":"9.5.0(tasmota)","BuildDateTime":"2021-06-17T08:26:35","Boot":31,"Core":"2_7_4_9","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8285","CR":"382/699"}}
05:53:44.539 MQT: stat/tasmota_B10C83/STATUS3 = {"StatusLOG":{"SerialLog":0,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["ToEjAm","Step31"],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00008009","2805C8000100060000005A0A000000000000","00000080","00006000","00004000"]}}
05:53:44.552 MQT: stat/tasmota_B10C83/STATUS4 = {"StatusMEM":{"ProgramSize":607,"Free":396,"Heap":24,"ProgramFlashSize":1024,"FlashSize":1024,"FlashChipId":"144051","FlashFrequency":40,"FlashMode":3,"Features":["00000809","8FDAC787","04368001","000000CF","010013C0","C000F981","00004004","00001000","00000020"],"Drivers":"1,2,3,4,5,6,7,8,9,10,12,16,18,19,20,21,22,24,26,27,29,30,35,37,45","Sensors":"1,2,3,4,5,6"}}
05:53:44.562 MQT: stat/tasmota_B10C83/STATUS5 = {"StatusNET":{"Hostname":"P81_BenchLamp","IPAddress":"192.168.1.81","Gateway":"192.168.1.254","Subnetmask":"255.255.255.0","DNSServer":"192.168.1.254","Mac":"DC:4F:22:B1:0C:83","Webserver":2,"WifiConfig":2,"WifiPower":17.0}}
05:53:44.568 MQT: stat/tasmota_B10C83/STATUS6 = {"StatusMQT":{"MqttHost":"192.168.1.126","MqttPort":1883,"MqttClientMask":"P81_BenchLamp","MqttClient":"P81_BenchLamp","MqttUser":"DVES_USER","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
05:53:44.574 MQT: stat/tasmota_B10C83/STATUS7 = {"StatusTIM":{"UTC":"2021-09-19T04:53:44","Local":"2021-09-19T05:53:44","StartDST":"2021-03-28T02:00:00","EndDST":"2021-10-31T03:00:00","Timezone":"+01:00","Sunrise":"06:33","Sunset":"18:54"}}
05:53:44.579 MQT: stat/tasmota_B10C83/STATUS9 = {"StatusPTH":{"PowerDelta":[0,0,0],"PowerLow":0,"PowerHigh":0,"VoltageLow":0,"VoltageHigh":0,"CurrentLow":0,"CurrentHigh":0}}
05:53:44.586 MQT: stat/tasmota_B10C83/STATUS10 = {"StatusSNS":{"Time":"2021-09-19T05:53:44","ENERGY":{"TotalStartTime":"2020-07-25T05:45:47","Total":10.048,"Yesterday":0.000,"Today":0.000,"Power":0,"ApparentPower":0,"ReactivePower":0,"Factor":0.00,"Voltage":0,"Current":0.000}}}
05:53:44.592 MQT: stat/tasmota_B10C83/STATUS11 = {"StatusSTS":{"Time":"2021-09-19T05:53:44","Uptime":"0T00:04:47","UptimeSec":287,"Heap":24,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":29,"MqttCount":1,"POWER":"OFF","Wifi":{"AP":1,"SSId":"ToEjAm","BSSId":"24:5A:4C:1A:66:59","Channel":6,"Mode":"11n","RSSI":62,"Signal":-69,"LinkCount":1,"Downtime":"0T00:00:04"}}}
```
- [ ] Set `weblog` to 4 and then, when you experience your issue, provide the output of the Console log:
```lua
Console output here:
```
### TO REPRODUCE
_Steps to reproduce the behavior:_
update the MQTT Topic field to something with an underscore, or a dash and caps
the result is field reset to default
### EXPECTED BEHAVIOUR
_A clear and concise description of what you expected to happen._
I expected to be able to use the device name as the topic. If the device name is legal then it should also be fine for topic. I was using P81_BenchLamp as topic. It conveys to me that it is a Plug Module at 192.168.1.81 with a friendly name.
tasmota_2a4d13 is not useful when configuring subscriptions.
### SCREENSHOTS
_If applicable, add screenshots to help explain your problem._
### ADDITIONAL CONTEXT
_Add any other context about the problem here._
I am using this in Homeseer as well as Home Assistant
Thanks for the great work ! Even though I am bitchin I am grateful for your talents.
**(Please, remember to close the issue when the problem has been addressed)**
|
non_usab
|
unable to update the topic field reverts to default thanks for reporting a problem for this project read this first this issue template is meant to report tasmota software problems only please do not open an issue if your tasmota version is not the latest from the development branch please update your device before submitting your issue your problem might already be solved the latest precompiled binaries of tasmota can be downloaded from if you have an issue when flashing was done via tuya convert please address it to tuya convert team if your issue is a flashing issue please address it to the if your issue is compilation problem please address it to the if your issue has been addressed before i e duplicated issue please ask in the original issue if your issue is a wi fi problem or mqtt problem please try the steps provided in the and please take a few minutes to complete the requested information below our ability to provide assistance is greatly hampered without it the details requested potentially affect which options to pursue the small amount of time you spend completing the template will also help the volunteers providing the assistance to you to reduce the time required to help you do not delete any text from this template otherwise the issue will be auto closed problem description a clear and concise description of what the problem is i a unable to update the topic field on versions and the field is reset back to default i am trying to set topic as benchlamp or benchlamp changing the topic to sexybeast does work but that doesn t work for me requested information make sure your have performed every step and checked the applicable boxes before submitting your issue thank you read the and searched the problem in searched the problem in searched the problem in the searched the problem in the device used e g sonoff basic litesun la tasmota binary firmware version number used also pre compiled yes self compiled flashing tools used provide the output of command backlog template module gpio lua configuration output here mqt stat sexybeast result name litesun la gpio flag base mqt stat sexybeast result module litesun la mqt stat sexybeast result none led none cf hlwbl none none hlwbl sel i led none none none if using rules provide the output of this command backlog lua rules output here provide the output of this command status lua status output here cmd status lua mqt stat tasmota status status module devicename benchlamp friendlyname topic tasmota buttontopic power poweronstate ledstate ledmask ffff savedata savestate switchtopic switchmode buttonretain switchretain sensorretain powerretain inforetain stateretain mqt stat tasmota statusprm baudrate serialconfig grouptopic tasmotas otaurl restart uptime startuputc sleep cfgholder bootcount bcresettime savecount saveaddress mqt stat tasmota statusfwr version tasmota builddatetime boot core sdk dev cpufrequency hardware cr mqt stat tasmota statuslog seriallog weblog mqttlog syslog loghost logport ssid teleperiod resolution setoption mqt stat tasmota statusmem programsize free heap programflashsize flashsize flashchipid flashfrequency flashmode features drivers sensors mqt stat tasmota statusnet hostname benchlamp ipaddress gateway subnetmask dnsserver mac dc webserver wificonfig wifipower mqt stat tasmota statusmqt mqtthost mqttport mqttclientmask benchlamp mqttclient benchlamp mqttuser dves user mqttcount max packet size keepalive socket timeout mqt stat tasmota statustim utc local startdst enddst timezone sunrise sunset mqt stat tasmota statuspth powerdelta powerlow powerhigh voltagelow voltagehigh currentlow currenthigh mqt stat tasmota statussns time energy totalstarttime total yesterday today power apparentpower reactivepower factor voltage current mqt stat tasmota statussts time uptime uptimesec heap sleepmode dynamic sleep loadavg mqttcount power off wifi ap ssid toejam bssid channel mode rssi signal linkcount downtime set weblog to and then when you experience your issue provide the output of the console log lua console output here to reproduce steps to reproduce the behavior update the mqtt topic field to something with an underscore or a dash and caps the result is field reset to default expected behaviour a clear and concise description of what you expected to happen i expected to be able to use the device name as the topic if the device name is legal then it should also be fine for topic i was using benchlamp as topic it conveys to me that it is a plug module at with a friendly name tasmota is not useful when configuring subscriptions screenshots if applicable add screenshots to help explain your problem additional context add any other context about the problem here i am using this in homeseer as well as home assistant thanks for the great work even though i am bitchin i am grateful for your talents please remember to close the issue when the problem has been addressed
| 0
|
8,130
| 5,425,281,843
|
IssuesEvent
|
2017-03-03 05:19:17
|
bengreenier/Unity-MenuStack
|
https://api.github.com/repos/bengreenier/Unity-MenuStack
|
closed
|
Swap MenuRoot.DisableRuntimeTagging default
|
api-change enhancement usability-change
|
The perf-forward default here is probably dumb. We should focus on usability first, and perf later (which imo aligns with what unity is all about). Let's turn that 😦 upside down 😄 (ie: swap the default value from `true` to `false`)
|
True
|
Swap MenuRoot.DisableRuntimeTagging default - The perf-forward default here is probably dumb. We should focus on usability first, and perf later (which imo aligns with what unity is all about). Let's turn that 😦 upside down 😄 (ie: swap the default value from `true` to `false`)
|
usab
|
swap menuroot disableruntimetagging default the perf forward default here is probably dumb we should focus on usability first and perf later which imo aligns with what unity is all about let s turn that 😦 upside down 😄 ie swap the default value from true to false
| 1
|
110,853
| 16,993,386,224
|
IssuesEvent
|
2021-07-01 01:03:06
|
jtimberlake/jazz
|
https://api.github.com/repos/jtimberlake/jazz
|
opened
|
CVE-2021-29059 (High) detected in is-svg-2.1.0.tgz
|
security vulnerability
|
## CVE-2021-29059 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>is-svg-2.1.0.tgz</b></p></summary>
<p>Check if a string or buffer is SVG</p>
<p>Library home page: <a href="https://registry.npmjs.org/is-svg/-/is-svg-2.1.0.tgz">https://registry.npmjs.org/is-svg/-/is-svg-2.1.0.tgz</a></p>
<p>Path to dependency file: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/package.json</p>
<p>Path to vulnerable library: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/is-svg/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.0.0-rc.0.tgz (Root Library)
- cssnano-3.10.0.tgz
- postcss-svgo-2.1.6.tgz
- :x: **is-svg-2.1.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A vulnerability was discovered in IS-SVG version 4.3.1 and below where a Regular Expression Denial of Service (ReDOS) occurs if the application is provided and checks a crafted invalid SVG string.
<p>Publish Date: 2021-06-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29059>CVE-2021-29059</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"is-svg","packageVersion":"2.1.0","packageFilePaths":["/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/package.json"],"isTransitiveDependency":true,"dependencyTree":"@angular/cli:1.0.0-rc.0;cssnano:3.10.0;postcss-svgo:2.1.6;is-svg:2.1.0","isMinimumFixVersionAvailable":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-29059","vulnerabilityDetails":"A vulnerability was discovered in IS-SVG version 4.3.1 and below where a Regular Expression Denial of Service (ReDOS) occurs if the application is provided and checks a crafted invalid SVG string.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29059","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2021-29059 (High) detected in is-svg-2.1.0.tgz - ## CVE-2021-29059 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>is-svg-2.1.0.tgz</b></p></summary>
<p>Check if a string or buffer is SVG</p>
<p>Library home page: <a href="https://registry.npmjs.org/is-svg/-/is-svg-2.1.0.tgz">https://registry.npmjs.org/is-svg/-/is-svg-2.1.0.tgz</a></p>
<p>Path to dependency file: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/package.json</p>
<p>Path to vulnerable library: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/is-svg/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.0.0-rc.0.tgz (Root Library)
- cssnano-3.10.0.tgz
- postcss-svgo-2.1.6.tgz
- :x: **is-svg-2.1.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A vulnerability was discovered in IS-SVG version 4.3.1 and below where a Regular Expression Denial of Service (ReDOS) occurs if the application is provided and checks a crafted invalid SVG string.
<p>Publish Date: 2021-06-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29059>CVE-2021-29059</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"is-svg","packageVersion":"2.1.0","packageFilePaths":["/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/package.json"],"isTransitiveDependency":true,"dependencyTree":"@angular/cli:1.0.0-rc.0;cssnano:3.10.0;postcss-svgo:2.1.6;is-svg:2.1.0","isMinimumFixVersionAvailable":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-29059","vulnerabilityDetails":"A vulnerability was discovered in IS-SVG version 4.3.1 and below where a Regular Expression Denial of Service (ReDOS) occurs if the application is provided and checks a crafted invalid SVG string.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29059","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->
|
non_usab
|
cve high detected in is svg tgz cve high severity vulnerability vulnerable library is svg tgz check if a string or buffer is svg library home page a href path to dependency file jazz core jazz ui src app primary components daterange picker datepicker package json path to vulnerable library jazz core jazz ui src app primary components daterange picker datepicker node modules is svg package json dependency hierarchy cli rc tgz root library cssnano tgz postcss svgo tgz x is svg tgz vulnerable library found in base branch master vulnerability details a vulnerability was discovered in is svg version and below where a regular expression denial of service redos occurs if the application is provided and checks a crafted invalid svg string publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree angular cli rc cssnano postcss svgo is svg isminimumfixversionavailable false basebranches vulnerabilityidentifier cve vulnerabilitydetails a vulnerability was discovered in is svg version and below where a regular expression denial of service redos occurs if the application is provided and checks a crafted invalid svg string vulnerabilityurl
| 0
|
11,823
| 7,476,813,681
|
IssuesEvent
|
2018-04-04 05:37:00
|
gama-platform/gama
|
https://api.github.com/repos/gama-platform/gama
|
opened
|
Export GAML templates
|
> Enhancement Affects Usability Concerns GAML Concerns Interface
|
GAML templates are very useful especially when teaching new students or for my personal use on complex snippets that i borrow from the forum. However, it is no possible to export my customized templates to another machine and this negates the very purpose of templates.
i would like to request a possibility to a) export templates b) restore original templates.
thank u
Srirama
|
True
|
Export GAML templates - GAML templates are very useful especially when teaching new students or for my personal use on complex snippets that i borrow from the forum. However, it is no possible to export my customized templates to another machine and this negates the very purpose of templates.
i would like to request a possibility to a) export templates b) restore original templates.
thank u
Srirama
|
usab
|
export gaml templates gaml templates are very useful especially when teaching new students or for my personal use on complex snippets that i borrow from the forum however it is no possible to export my customized templates to another machine and this negates the very purpose of templates i would like to request a possibility to a export templates b restore original templates thank u srirama
| 1
|
18,781
| 13,100,384,715
|
IssuesEvent
|
2020-08-04 00:20:44
|
google/iree
|
https://api.github.com/repos/google/iree
|
closed
|
Move IREE to be GitHub first
|
infrastructure
|
As announced in https://groups.google.com/d/topic/iree-discuss/F07vsG9Ah4o/discussion
IREE will be trying out a flow where we merge directly on GitHub and also have a separate branch that tracks the internal Google source repository. Frequent merges between branches will be used to propagate changes.
This will allow us to hide some of the complexity of syncing with our internal source repository and get it out of the way of everyday developer flows.
Internal tracking bug http://b/159492658
|
1.0
|
Move IREE to be GitHub first - As announced in https://groups.google.com/d/topic/iree-discuss/F07vsG9Ah4o/discussion
IREE will be trying out a flow where we merge directly on GitHub and also have a separate branch that tracks the internal Google source repository. Frequent merges between branches will be used to propagate changes.
This will allow us to hide some of the complexity of syncing with our internal source repository and get it out of the way of everyday developer flows.
Internal tracking bug http://b/159492658
|
non_usab
|
move iree to be github first as announced in iree will be trying out a flow where we merge directly on github and also have a separate branch that tracks the internal google source repository frequent merges between branches will be used to propagate changes this will allow us to hide some of the complexity of syncing with our internal source repository and get it out of the way of everyday developer flows internal tracking bug
| 0
|
19,620
| 14,345,827,223
|
IssuesEvent
|
2020-11-28 21:00:27
|
rugk/unicodify
|
https://api.github.com/repos/rugk/unicodify
|
opened
|
Ctrl+Z support
|
enhancement usability/UX
|
## Background
<!-- Is your feature request related to a problem? Please describe. -->
<!-- A clear and concise description of what the problem is. E.g.: "I'm always frustrated when […]" -->
For usability reasons, I would also like to use <kbd>Ctrl</kbd>+<kbd>Z</kbd> to reverse a replacement done by this add-on.
I know currently <kbd>backspace</kbd> is possible, but <kbd>Ctrl</kbd>+<kbd>Z</kbd> is another well-known command for that.
And if you try that with normal text, all of them support <kbd>Ctrl</kbd>+<kbd>Z</kbd>.
**Attention:** If we support <kbd>Ctrl</kbd>+<kbd>Z</kbd>, we should also support <kbd>Ctrl</kbd>+<kbd>Shiftkbd>+<kbd>Z</kbd> to re-add the text/”reverse” that decision.
## Proposed solution
<!-- Describe the solution you'd like. -->
<!-- A clear and concise description of what you want to happen. ⟶
We need to listen to these keys again. I’M not sure whether this is easily possible, given that this is more of a system hotkey, but well… it’s an idea at least.
## Alternatives
<!-- Describe alternatives you've considered. -->
<!-- A clear and concise description of any alternative solutions or features you've considered. ⟶
No one.
## Additional context
<!-- Add any other context or screenshots about the feature request here. -->
AFAIK other websiites (e.g. Wikipedia’s VisualEditor) also support this, so it seems to be possible to overwrite.
|
True
|
Ctrl+Z support - ## Background
<!-- Is your feature request related to a problem? Please describe. -->
<!-- A clear and concise description of what the problem is. E.g.: "I'm always frustrated when […]" -->
For usability reasons, I would also like to use <kbd>Ctrl</kbd>+<kbd>Z</kbd> to reverse a replacement done by this add-on.
I know currently <kbd>backspace</kbd> is possible, but <kbd>Ctrl</kbd>+<kbd>Z</kbd> is another well-known command for that.
And if you try that with normal text, all of them support <kbd>Ctrl</kbd>+<kbd>Z</kbd>.
**Attention:** If we support <kbd>Ctrl</kbd>+<kbd>Z</kbd>, we should also support <kbd>Ctrl</kbd>+<kbd>Shiftkbd>+<kbd>Z</kbd> to re-add the text/”reverse” that decision.
## Proposed solution
<!-- Describe the solution you'd like. -->
<!-- A clear and concise description of what you want to happen. ⟶
We need to listen to these keys again. I’M not sure whether this is easily possible, given that this is more of a system hotkey, but well… it’s an idea at least.
## Alternatives
<!-- Describe alternatives you've considered. -->
<!-- A clear and concise description of any alternative solutions or features you've considered. ⟶
No one.
## Additional context
<!-- Add any other context or screenshots about the feature request here. -->
AFAIK other websiites (e.g. Wikipedia’s VisualEditor) also support this, so it seems to be possible to overwrite.
|
usab
|
ctrl z support background for usability reasons i would also like to use ctrl z to reverse a replacement done by this add on i know currently backspace is possible but ctrl z is another well known command for that and if you try that with normal text all of them support ctrl z attention if we support ctrl z we should also support ctrl shiftkbd z to re add the text ”reverse” that decision proposed solution a clear and concise description of what you want to happen ⟶ we need to listen to these keys again i’m not sure whether this is easily possible given that this is more of a system hotkey but well… it’s an idea at least alternatives a clear and concise description of any alternative solutions or features you ve considered ⟶ no one additional context afaik other websiites e g wikipedia’s visualeditor also support this so it seems to be possible to overwrite
| 1
|
259,646
| 27,702,916,257
|
IssuesEvent
|
2023-03-14 09:19:03
|
xinYG/monorepo
|
https://api.github.com/repos/xinYG/monorepo
|
opened
|
CVE-2023-28154 (Medium) detected in webpack-5.70.0.tgz, webpack-5.66.0.tgz
|
Mend: dependency security vulnerability
|
## CVE-2023-28154 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>webpack-5.70.0.tgz</b>, <b>webpack-5.66.0.tgz</b></p></summary>
<p>
<details><summary><b>webpack-5.70.0.tgz</b></p></summary>
<p>Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.</p>
<p>Library home page: <a href="https://registry.npmjs.org/webpack/-/webpack-5.70.0.tgz">https://registry.npmjs.org/webpack/-/webpack-5.70.0.tgz</a></p>
<p>
Dependency Hierarchy:
- @zgriesinger/single-page-app-file:frontend/single-page-app.tgz (Root Library)
- react-scripts-5.0.0.tgz
- :x: **webpack-5.70.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>webpack-5.66.0.tgz</b></p></summary>
<p>Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.</p>
<p>Library home page: <a href="https://registry.npmjs.org/webpack/-/webpack-5.66.0.tgz">https://registry.npmjs.org/webpack/-/webpack-5.66.0.tgz</a></p>
<p>
Dependency Hierarchy:
- @zgriesinger/service-a-file:api/service-a.tgz (Root Library)
- cli-8.2.2.tgz
- :x: **webpack-5.66.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/xinYG/monorepo/commit/484ca86608666d6c5f199d06d30156e2c930c67d">484ca86608666d6c5f199d06d30156e2c930c67d</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Webpack 5 before 5.76.0 does not avoid cross-realm object access. ImportParserPlugin.js mishandles the magic comment feature. An attacker who controls a property of an untrusted object can obtain access to the real global object.
<p>Publish Date: 2023-03-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-28154>CVE-2023-28154</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2023-03-13</p>
<p>Fix Resolution: webpack - 5.76.0</p>
</p>
</details>
<p></p>
|
True
|
CVE-2023-28154 (Medium) detected in webpack-5.70.0.tgz, webpack-5.66.0.tgz - ## CVE-2023-28154 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>webpack-5.70.0.tgz</b>, <b>webpack-5.66.0.tgz</b></p></summary>
<p>
<details><summary><b>webpack-5.70.0.tgz</b></p></summary>
<p>Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.</p>
<p>Library home page: <a href="https://registry.npmjs.org/webpack/-/webpack-5.70.0.tgz">https://registry.npmjs.org/webpack/-/webpack-5.70.0.tgz</a></p>
<p>
Dependency Hierarchy:
- @zgriesinger/single-page-app-file:frontend/single-page-app.tgz (Root Library)
- react-scripts-5.0.0.tgz
- :x: **webpack-5.70.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>webpack-5.66.0.tgz</b></p></summary>
<p>Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.</p>
<p>Library home page: <a href="https://registry.npmjs.org/webpack/-/webpack-5.66.0.tgz">https://registry.npmjs.org/webpack/-/webpack-5.66.0.tgz</a></p>
<p>
Dependency Hierarchy:
- @zgriesinger/service-a-file:api/service-a.tgz (Root Library)
- cli-8.2.2.tgz
- :x: **webpack-5.66.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/xinYG/monorepo/commit/484ca86608666d6c5f199d06d30156e2c930c67d">484ca86608666d6c5f199d06d30156e2c930c67d</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Webpack 5 before 5.76.0 does not avoid cross-realm object access. ImportParserPlugin.js mishandles the magic comment feature. An attacker who controls a property of an untrusted object can obtain access to the real global object.
<p>Publish Date: 2023-03-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-28154>CVE-2023-28154</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2023-03-13</p>
<p>Fix Resolution: webpack - 5.76.0</p>
</p>
</details>
<p></p>
|
non_usab
|
cve medium detected in webpack tgz webpack tgz cve medium severity vulnerability vulnerable libraries webpack tgz webpack tgz webpack tgz packs commonjs amd modules for the browser allows to split your codebase into multiple bundles which can be loaded on demand support loaders to preprocess files i e json jsx css less and your custom stuff library home page a href dependency hierarchy zgriesinger single page app file frontend single page app tgz root library react scripts tgz x webpack tgz vulnerable library webpack tgz packs commonjs amd modules for the browser allows to split your codebase into multiple bundles which can be loaded on demand support loaders to preprocess files i e json jsx css less and your custom stuff library home page a href dependency hierarchy zgriesinger service a file api service a tgz root library cli tgz x webpack tgz vulnerable library found in head commit a href found in base branch main vulnerability details webpack before does not avoid cross realm object access importparserplugin js mishandles the magic comment feature an attacker who controls a property of an untrusted object can obtain access to the real global object publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution webpack
| 0
|
314,056
| 23,504,394,778
|
IssuesEvent
|
2022-08-18 11:18:42
|
rhiannonmcn/the-book-nook
|
https://api.github.com/repos/rhiannonmcn/the-book-nook
|
opened
|
DOCUMENTATION: README.md Update
|
documentation must have
|
- [ ] Finish Future Features section in README.md
- [ ] Finish Technologies used section in README.md
- [ ] Finish Credits section in README.md
- [ ] Finish Acknowledgements section in README.md
|
1.0
|
DOCUMENTATION: README.md Update - - [ ] Finish Future Features section in README.md
- [ ] Finish Technologies used section in README.md
- [ ] Finish Credits section in README.md
- [ ] Finish Acknowledgements section in README.md
|
non_usab
|
documentation readme md update finish future features section in readme md finish technologies used section in readme md finish credits section in readme md finish acknowledgements section in readme md
| 0
|
414,966
| 12,122,080,725
|
IssuesEvent
|
2020-04-22 10:20:41
|
wazuh/wazuh-kibana-app
|
https://api.github.com/repos/wazuh/wazuh-kibana-app
|
closed
|
Allow save searches in the Wazuh App
|
priority/medium question
|
Hi team,
Discover tab allows saving the current search.
Could we do the same inside the app?
Thanks.
|
1.0
|
Allow save searches in the Wazuh App - Hi team,
Discover tab allows saving the current search.
Could we do the same inside the app?
Thanks.
|
non_usab
|
allow save searches in the wazuh app hi team discover tab allows saving the current search could we do the same inside the app thanks
| 0
|
250,807
| 21,337,412,406
|
IssuesEvent
|
2022-04-18 16:09:17
|
hashgraph/hedera-services
|
https://api.github.com/repos/hashgraph/hedera-services
|
closed
|
HTS precompile rollbacks after external reverts
|
Test Development hts-contracts
|
### Problem
We need sample Solidity contract(s) and EETs to validate rollback works when an HTS precompile succeeds; but its parent `MessageFrame` reverts. There are a few scenarios to consider.
- [ ] A successful precompile that transfers ℏ from calling contract account `0.0.X`, and thus causes a Solidity `transfer()` in the same frame to fail due to insufficient balance, has no effect on state.
- [ ] When a top-level message frame makes two message calls, where the first does a successful precompile NFT mint; and the second fails, causing the top-level frame to revert; then the NFT minted by the first nested precompile does not exist (and there is no corresponding `TransactionRecord`).
- [ ] A successful dissociate precompile in a nested frame which then creates a child frame that reverts due to OOG has no effects on state (and no `TransactionRecord`).
### Solution
Write EETs for the above items, extending the recordWith() DSL as necessary to make expressing each type of assertion as simple as possible.
### Alternatives
_No response_
|
1.0
|
HTS precompile rollbacks after external reverts - ### Problem
We need sample Solidity contract(s) and EETs to validate rollback works when an HTS precompile succeeds; but its parent `MessageFrame` reverts. There are a few scenarios to consider.
- [ ] A successful precompile that transfers ℏ from calling contract account `0.0.X`, and thus causes a Solidity `transfer()` in the same frame to fail due to insufficient balance, has no effect on state.
- [ ] When a top-level message frame makes two message calls, where the first does a successful precompile NFT mint; and the second fails, causing the top-level frame to revert; then the NFT minted by the first nested precompile does not exist (and there is no corresponding `TransactionRecord`).
- [ ] A successful dissociate precompile in a nested frame which then creates a child frame that reverts due to OOG has no effects on state (and no `TransactionRecord`).
### Solution
Write EETs for the above items, extending the recordWith() DSL as necessary to make expressing each type of assertion as simple as possible.
### Alternatives
_No response_
|
non_usab
|
hts precompile rollbacks after external reverts problem we need sample solidity contract s and eets to validate rollback works when an hts precompile succeeds but its parent messageframe reverts there are a few scenarios to consider a successful precompile that transfers ℏ from calling contract account x and thus causes a solidity transfer in the same frame to fail due to insufficient balance has no effect on state when a top level message frame makes two message calls where the first does a successful precompile nft mint and the second fails causing the top level frame to revert then the nft minted by the first nested precompile does not exist and there is no corresponding transactionrecord a successful dissociate precompile in a nested frame which then creates a child frame that reverts due to oog has no effects on state and no transactionrecord solution write eets for the above items extending the recordwith dsl as necessary to make expressing each type of assertion as simple as possible alternatives no response
| 0
|
14,092
| 8,823,506,119
|
IssuesEvent
|
2019-01-02 13:54:39
|
gbif/registry-console
|
https://api.github.com/repos/gbif/registry-console
|
closed
|
links in breadcrumb
|
enhancement help wanted usability
|
I like being able to navigate by breadcrumb. Especially on mobile
Should we add links so that
`Dataset` links to dataset search. `Title of Dataset 13.12.2018` links to the dataset details. Similar for others.
|
True
|
links in breadcrumb - I like being able to navigate by breadcrumb. Especially on mobile
Should we add links so that
`Dataset` links to dataset search. `Title of Dataset 13.12.2018` links to the dataset details. Similar for others.
|
usab
|
links in breadcrumb i like being able to navigate by breadcrumb especially on mobile should we add links so that dataset links to dataset search title of dataset links to the dataset details similar for others
| 1
|
22,033
| 18,347,822,387
|
IssuesEvent
|
2021-10-08 08:46:29
|
mimic-sussex/sema
|
https://api.github.com/repos/mimic-sussex/sema
|
closed
|
navigation bar loses correct styling on home, reference and about page
|
usability
|
Correct styling of navigation bar with separation between links and white underscore is sometimes lost when window is resized on both the reference and about page. Issue doesn't happen on both the tutorial or playground which makes me think its probably a minor css consistency issue.
similar cramping of the navigation bar occurs when resizing on the home page.
|
True
|
navigation bar loses correct styling on home, reference and about page - Correct styling of navigation bar with separation between links and white underscore is sometimes lost when window is resized on both the reference and about page. Issue doesn't happen on both the tutorial or playground which makes me think its probably a minor css consistency issue.
similar cramping of the navigation bar occurs when resizing on the home page.
|
usab
|
navigation bar loses correct styling on home reference and about page correct styling of navigation bar with separation between links and white underscore is sometimes lost when window is resized on both the reference and about page issue doesn t happen on both the tutorial or playground which makes me think its probably a minor css consistency issue similar cramping of the navigation bar occurs when resizing on the home page
| 1
|
559,112
| 16,550,192,356
|
IssuesEvent
|
2021-05-28 07:41:19
|
renovatebot/renovate
|
https://api.github.com/repos/renovatebot/renovate
|
closed
|
Migrate Jest to v27
|
priority-3-normal status:in-progress type:refactor
|
Might be a good idea to update our `jest monorepo` and `jest-ts` test stuff once that hits 7 `stabilityDays`.
For easy reference, here's the blog post from Jest themselves explaining the changes.
https://jestjs.io/blog/2021/05/25/jest-27
_Originally posted by @HonkingGoose in https://github.com/renovatebot/renovate/issues/2958#issuecomment-848531328_
|
1.0
|
Migrate Jest to v27 - Might be a good idea to update our `jest monorepo` and `jest-ts` test stuff once that hits 7 `stabilityDays`.
For easy reference, here's the blog post from Jest themselves explaining the changes.
https://jestjs.io/blog/2021/05/25/jest-27
_Originally posted by @HonkingGoose in https://github.com/renovatebot/renovate/issues/2958#issuecomment-848531328_
|
non_usab
|
migrate jest to might be a good idea to update our jest monorepo and jest ts test stuff once that hits stabilitydays for easy reference here s the blog post from jest themselves explaining the changes originally posted by honkinggoose in
| 0
|
23,320
| 21,662,121,970
|
IssuesEvent
|
2022-05-06 20:33:34
|
argoproj/argo-cd
|
https://api.github.com/repos/argoproj/argo-cd
|
closed
|
Please provide SHA256SUMS for releases
|
enhancement type:usability component:distribution
|
**Is your feature request related to a problem? Please describe.**
It is common practice for projects to release hash sums to check data integrity.
**Describe the solution you'd like**
SHA sums are provided for each release.
**Have you thought about contributing yourself?**
The developers should release hash sums.
If you want to get involved, check out the
[contributing guide](https://github.com/argoproj/argo-cd/blob/master/docs/CONTRIBUTING.md), then reach out to us on [Slack](https://argoproj.github.io/community/join-slack) so we can see how to get you started.
|
True
|
Please provide SHA256SUMS for releases - **Is your feature request related to a problem? Please describe.**
It is common practice for projects to release hash sums to check data integrity.
**Describe the solution you'd like**
SHA sums are provided for each release.
**Have you thought about contributing yourself?**
The developers should release hash sums.
If you want to get involved, check out the
[contributing guide](https://github.com/argoproj/argo-cd/blob/master/docs/CONTRIBUTING.md), then reach out to us on [Slack](https://argoproj.github.io/community/join-slack) so we can see how to get you started.
|
usab
|
please provide for releases is your feature request related to a problem please describe it is common practice for projects to release hash sums to check data integrity describe the solution you d like sha sums are provided for each release have you thought about contributing yourself the developers should release hash sums if you want to get involved check out the then reach out to us on so we can see how to get you started
| 1
|
16,213
| 10,667,722,967
|
IssuesEvent
|
2019-10-19 14:31:03
|
rugk/awesome-emoji-picker
|
https://api.github.com/repos/rugk/awesome-emoji-picker
|
opened
|
RTL: overlap in bottom panel/skin selector
|
UI/usability/UX bug i18n/l10n
|
## Bug description
<!-- A short summary of the issue. You can also explain how it affected you or explain some background of the story. -->
As reported by @shanirub in https://github.com/rugk/awesome-emoji-picker/pull/62#issue-329930736:
> The small circle that represents the skin tone overlaps the text "Awesome Emoji" [in a RTL language].
## Steps to reproduce
<!-- Describe what steps you did/can do to reproduce the problem. Also mention if it is not always reproducible. If applicable, add screenshots to help explain your problem. -->
1. (Use a version with the Hebrew or another RTL language translation.)
2. Choose that language in the settings of Firefox.
3. Restart Firefox.
4. Open emoji picker.
### Actual behavior
<!-- The behavior you experienced. -->
### Expected behavior
<!-- A clear and concise description of what you expected to happen. -->
* emoji should be at the right
* skin selector should be on the left
## System
<!-- Add some information about your system. You can omit values if you think they are really not necessary. -->
Operating system and version: Fedora 30
Browser and version: Firefox 69
Add-on version: dev (master)
## Possible solution
<!-- Add references to other issues/docs/websites here or look into the code to find the potential causes of the problem or how to fix it. Omit this, if you don't know what to write here. -->
likely CSS
|
True
|
RTL: overlap in bottom panel/skin selector - ## Bug description
<!-- A short summary of the issue. You can also explain how it affected you or explain some background of the story. -->
As reported by @shanirub in https://github.com/rugk/awesome-emoji-picker/pull/62#issue-329930736:
> The small circle that represents the skin tone overlaps the text "Awesome Emoji" [in a RTL language].
## Steps to reproduce
<!-- Describe what steps you did/can do to reproduce the problem. Also mention if it is not always reproducible. If applicable, add screenshots to help explain your problem. -->
1. (Use a version with the Hebrew or another RTL language translation.)
2. Choose that language in the settings of Firefox.
3. Restart Firefox.
4. Open emoji picker.
### Actual behavior
<!-- The behavior you experienced. -->
### Expected behavior
<!-- A clear and concise description of what you expected to happen. -->
* emoji should be at the right
* skin selector should be on the left
## System
<!-- Add some information about your system. You can omit values if you think they are really not necessary. -->
Operating system and version: Fedora 30
Browser and version: Firefox 69
Add-on version: dev (master)
## Possible solution
<!-- Add references to other issues/docs/websites here or look into the code to find the potential causes of the problem or how to fix it. Omit this, if you don't know what to write here. -->
likely CSS
|
usab
|
rtl overlap in bottom panel skin selector bug description as reported by shanirub in the small circle that represents the skin tone overlaps the text awesome emoji steps to reproduce use a version with the hebrew or another rtl language translation choose that language in the settings of firefox restart firefox open emoji picker actual behavior expected behavior emoji should be at the right skin selector should be on the left system operating system and version fedora browser and version firefox add on version dev master possible solution likely css
| 1
|
255,953
| 8,126,600,550
|
IssuesEvent
|
2018-08-17 03:16:59
|
aowen87/BAR
|
https://api.github.com/repos/aowen87/BAR
|
closed
|
provide ubuntu release with built in MPI
|
Expected Use: 3 - Occasional Feature Impact: 3 - Medium Priority: Normal
|
Request from Salvador Portillo on the users list for ubuntu LTS 14 that has mpich built in
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 3052
Status: Resolved
Project: VisIt
Tracker: Feature
Priority: Normal
Subject: provide ubuntu release with built in MPI
Assigned to: Eric Brugger
Category:
Target version: 2.13.1
Author: Cyrus Harrison
Start: 03/29/2018
Due date:
% Done: 100
Estimated time: 4.0
Created: 03/29/2018 12:58 am
Updated: 04/09/2018 06:41 pm
Likelihood:
Severity:
Found in version: trunk
Impact: 3 - Medium
Expected Use: 3 - Occasional
OS: Linux
Support Group: Any
Description:
Request from Salvador Portillo on the users list for ubuntu LTS 14 that has mpich built in
Comments:
I modified the visit-build-open script to build a parallel version. I included Ubuntu executables with the parallel version in the 2.13.1 release directory.
|
1.0
|
provide ubuntu release with built in MPI - Request from Salvador Portillo on the users list for ubuntu LTS 14 that has mpich built in
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 3052
Status: Resolved
Project: VisIt
Tracker: Feature
Priority: Normal
Subject: provide ubuntu release with built in MPI
Assigned to: Eric Brugger
Category:
Target version: 2.13.1
Author: Cyrus Harrison
Start: 03/29/2018
Due date:
% Done: 100
Estimated time: 4.0
Created: 03/29/2018 12:58 am
Updated: 04/09/2018 06:41 pm
Likelihood:
Severity:
Found in version: trunk
Impact: 3 - Medium
Expected Use: 3 - Occasional
OS: Linux
Support Group: Any
Description:
Request from Salvador Portillo on the users list for ubuntu LTS 14 that has mpich built in
Comments:
I modified the visit-build-open script to build a parallel version. I included Ubuntu executables with the parallel version in the 2.13.1 release directory.
|
non_usab
|
provide ubuntu release with built in mpi request from salvador portillo on the users list for ubuntu lts that has mpich built in redmine migration this ticket was migrated from redmine as such not all information was able to be captured in the transition below is a complete record of the original redmine ticket ticket number status resolved project visit tracker feature priority normal subject provide ubuntu release with built in mpi assigned to eric brugger category target version author cyrus harrison start due date done estimated time created am updated pm likelihood severity found in version trunk impact medium expected use occasional os linux support group any description request from salvador portillo on the users list for ubuntu lts that has mpich built in comments i modified the visit build open script to build a parallel version i included ubuntu executables with the parallel version in the release directory
| 0
|
18,151
| 12,602,506,519
|
IssuesEvent
|
2020-06-11 11:51:25
|
Camelcade/Perl5-IDEA
|
https://api.github.com/repos/Camelcade/Perl5-IDEA
|
opened
|
Do not show variables fqn in completion when qualifier specified
|
Autocompletion Usability problem
|
Case:
```
package Foo::Bar;
our $VAR;
Foo::Bar::<caret>
```
Should show `$VAR` with type specifier `Foo::Bar`, not `$Foo::Bar::VAR`
|
True
|
Do not show variables fqn in completion when qualifier specified - Case:
```
package Foo::Bar;
our $VAR;
Foo::Bar::<caret>
```
Should show `$VAR` with type specifier `Foo::Bar`, not `$Foo::Bar::VAR`
|
usab
|
do not show variables fqn in completion when qualifier specified case package foo bar our var foo bar should show var with type specifier foo bar not foo bar var
| 1
|
154,027
| 13,533,721,884
|
IssuesEvent
|
2020-09-16 03:46:12
|
TechCafeFreedom/Wantum-server
|
https://api.github.com/repos/TechCafeFreedom/Wantum-server
|
closed
|
ユーザ作成APIのドキュメントを仕様通りに修正
|
documentation
|
## 概要
現状JWTトークンをHeaderに受け取り、ユーザを作成しているが、ユーザが入力したプロフィール情報も含めてリクエストされるという仕様に変更されたため、下記のAPI定義を修正する必要がある。
https://stoplight.io/p/docs/gh/techcafefreedom/wantum-server/docs/reference/wantum.v1.0.0.yaml/paths/~1auth~1signup/get?srn=gh/techcafefreedom/wantum-server/docs/reference/wantum.v1.0.0.yaml/paths/~1auth~1signup/get&group=develop
|
1.0
|
ユーザ作成APIのドキュメントを仕様通りに修正 - ## 概要
現状JWTトークンをHeaderに受け取り、ユーザを作成しているが、ユーザが入力したプロフィール情報も含めてリクエストされるという仕様に変更されたため、下記のAPI定義を修正する必要がある。
https://stoplight.io/p/docs/gh/techcafefreedom/wantum-server/docs/reference/wantum.v1.0.0.yaml/paths/~1auth~1signup/get?srn=gh/techcafefreedom/wantum-server/docs/reference/wantum.v1.0.0.yaml/paths/~1auth~1signup/get&group=develop
|
non_usab
|
ユーザ作成apiのドキュメントを仕様通りに修正 概要 現状jwtトークンをheaderに受け取り、ユーザを作成しているが、ユーザが入力したプロフィール情報も含めてリクエストされるという仕様に変更されたため、下記のapi定義を修正する必要がある。
| 0
|
500,998
| 14,518,285,508
|
IssuesEvent
|
2020-12-13 23:01:28
|
bounswe/bounswe2020group5
|
https://api.github.com/repos/bounswe/bounswe2020group5
|
closed
|
frontend/ Product Page
|
Priority: Medium Status: In Progress frontend
|
First template of the product page will be implemented. (static/visual)
After the product endpoints are ready, backend connection will be established.
|
1.0
|
frontend/ Product Page - First template of the product page will be implemented. (static/visual)
After the product endpoints are ready, backend connection will be established.
|
non_usab
|
frontend product page first template of the product page will be implemented static visual after the product endpoints are ready backend connection will be established
| 0
|
14,411
| 9,166,352,993
|
IssuesEvent
|
2019-03-02 02:29:30
|
Microsoft/AzureStorageExplorer
|
https://api.github.com/repos/Microsoft/AzureStorageExplorer
|
opened
|
It is unclear that the dropdown for Azure Environment is associated with the Add an Azure Account radio button in the connection dialog (NVDA)
|
:beetle: bug :gear: usability b grade
|
**Storage Explorer Version**: 1.7.0
**Platform/OS**: All
**Architecture**: All
**Regression From**: No
**Bug description**
As the title says. Visually we also need an indentation for the combo box. Screen reader should associate the combobox to the "Add an Azure Account" radio button.
|
True
|
It is unclear that the dropdown for Azure Environment is associated with the Add an Azure Account radio button in the connection dialog (NVDA) - **Storage Explorer Version**: 1.7.0
**Platform/OS**: All
**Architecture**: All
**Regression From**: No
**Bug description**
As the title says. Visually we also need an indentation for the combo box. Screen reader should associate the combobox to the "Add an Azure Account" radio button.
|
usab
|
it is unclear that the dropdown for azure environment is associated with the add an azure account radio button in the connection dialog nvda storage explorer version platform os all architecture all regression from no bug description as the title says visually we also need an indentation for the combo box screen reader should associate the combobox to the add an azure account radio button
| 1
|
64,402
| 26,714,868,966
|
IssuesEvent
|
2023-01-28 11:15:47
|
microsoft/vscode-cpptools
|
https://api.github.com/repos/microsoft/vscode-cpptools
|
closed
|
Intellisense language version selection arbitrariness
|
Language Service more info needed
|
### Environment
- OS and Version: MS Windows 10
- VS Code Version: 1.70.2
- C/C++ Extension Version: 1.12.4
- Other extensions you installed (and if the issue persists after disabling them): C++ Extension Pack v1.2.0; CMake v0.0.17 with inferiors; Intellicode v1.2.24; Makefile tools v0.6.0
- If using SSH remote, specify OS of remote machine: Ubuntu 20.04
After last VSCode restart, warnings about forced selection of higher language level started appearing in output window. If these warnings are really describing the plugin logic, its decision to force newer language versions is improper.
I don't know what versions were before restart, due to automatic upgrade during restarts.
The project is single-directory of what is edited in vscode, with external directories of dependence projects (not to be controlled).
The project is makefile-based with own making logic and docker-based compilation. Code analysis alleviation is defined using `includePath` and `defines` in plugin settings.
### Bug Summary and Steps to Reproduce
Bug Summary:
The following messages started appearing in "output" window:
[9/1/2022, 9:23:34 AM] For C source files, the cStandard was changed from "c99" to "c17" based on compiler args and querying compilerPath: "/usr/bin/g++"
[9/1/2022, 9:23:40 AM] For C++ source files, the cppStandard was changed from "gnu++11" to "c++23" based on compiler args and querying compilerPath: "/usr/bin/g++"
Required language level as C99 and gnu++11 are explicitly specified in project settings (c_cpp_properties.json).
Despite the present compiler aptitude, the project shall be restricted to C99 and C++11 due to special target compilation.
Steps to reproduce:
Reopen the project folder and check contents of "output" window.
### Expected behavior
No arbitrary selection of language version.
### Code sample and Logs
```shell
c_cpp_properties.json:
{
"configurations": [
{
"name": "Linux",
"includePath": [
"/usr/lib/gcc/x86_64-linux-gnu/9/include/",
"${workspaceFolder}/**",
"${workspaceFolder}/common/include",
"${workspaceFolder}/include",
],
"defines": [
<... lots of project-specific definitions...>
],
"compilerPath": "/usr/bin/g++",
"cStandard": "c99",
"cppStandard": "gnu++11",
"intelliSenseMode": "linux-gcc-x64",
"configurationProvider": "ms-vscode.makefile-tools",
"compilerArgs": [
"-g -O -std=c++11 -DARCH_X86_64"
]
}
],
"version": 4
}
From log diagnostics:
-------- Diagnostics - 9/1/2022, 9:54:17 AM
Version: 1.12.4
Current Configuration:
{
"name": "Linux",
"includePath": [
"/usr/lib/gcc/x86_64-linux-gnu/9/include/",
"${workspaceFolder}/**",
"${workspaceFolder}/common/include",
"${workspaceFolder}/include",
],
"defines": [
<... skipped as above ...>
],
"compilerPath": "/usr/bin/g++",
"cStandard": "c99",
"cppStandard": "gnu++11",
"intelliSenseMode": "linux-gcc-x64",
"configurationProvider": "ms-vscode.makefile-tools",
"compilerArgs": [
"-g -O -std=c++11 -DARCH_X86_64"
],
"compilerPathIsExplicit": true,
"cStandardIsExplicit": true,
"cppStandardIsExplicit": true,
"intelliSenseModeIsExplicit": true,
"mergeConfigurations": false,
"browse": {
"path": [
"/usr/lib/gcc/x86_64-linux-gnu/9/include/",
"${workspaceFolder}/**",
"${workspaceFolder}/common/include",
"${workspaceFolder}/include",
],
"limitSymbolsToIncludedHeaders": true
}
}
Custom browse configuration:
{
"browsePath": []
}
No active translation units.
```
### Screenshots
### Additional context
_No response_
|
1.0
|
Intellisense language version selection arbitrariness - ### Environment
- OS and Version: MS Windows 10
- VS Code Version: 1.70.2
- C/C++ Extension Version: 1.12.4
- Other extensions you installed (and if the issue persists after disabling them): C++ Extension Pack v1.2.0; CMake v0.0.17 with inferiors; Intellicode v1.2.24; Makefile tools v0.6.0
- If using SSH remote, specify OS of remote machine: Ubuntu 20.04
After last VSCode restart, warnings about forced selection of higher language level started appearing in output window. If these warnings are really describing the plugin logic, its decision to force newer language versions is improper.
I don't know what versions were before restart, due to automatic upgrade during restarts.
The project is single-directory of what is edited in vscode, with external directories of dependence projects (not to be controlled).
The project is makefile-based with own making logic and docker-based compilation. Code analysis alleviation is defined using `includePath` and `defines` in plugin settings.
### Bug Summary and Steps to Reproduce
Bug Summary:
The following messages started appearing in "output" window:
[9/1/2022, 9:23:34 AM] For C source files, the cStandard was changed from "c99" to "c17" based on compiler args and querying compilerPath: "/usr/bin/g++"
[9/1/2022, 9:23:40 AM] For C++ source files, the cppStandard was changed from "gnu++11" to "c++23" based on compiler args and querying compilerPath: "/usr/bin/g++"
Required language level as C99 and gnu++11 are explicitly specified in project settings (c_cpp_properties.json).
Despite the present compiler aptitude, the project shall be restricted to C99 and C++11 due to special target compilation.
Steps to reproduce:
Reopen the project folder and check contents of "output" window.
### Expected behavior
No arbitrary selection of language version.
### Code sample and Logs
```shell
c_cpp_properties.json:
{
"configurations": [
{
"name": "Linux",
"includePath": [
"/usr/lib/gcc/x86_64-linux-gnu/9/include/",
"${workspaceFolder}/**",
"${workspaceFolder}/common/include",
"${workspaceFolder}/include",
],
"defines": [
<... lots of project-specific definitions...>
],
"compilerPath": "/usr/bin/g++",
"cStandard": "c99",
"cppStandard": "gnu++11",
"intelliSenseMode": "linux-gcc-x64",
"configurationProvider": "ms-vscode.makefile-tools",
"compilerArgs": [
"-g -O -std=c++11 -DARCH_X86_64"
]
}
],
"version": 4
}
From log diagnostics:
-------- Diagnostics - 9/1/2022, 9:54:17 AM
Version: 1.12.4
Current Configuration:
{
"name": "Linux",
"includePath": [
"/usr/lib/gcc/x86_64-linux-gnu/9/include/",
"${workspaceFolder}/**",
"${workspaceFolder}/common/include",
"${workspaceFolder}/include",
],
"defines": [
<... skipped as above ...>
],
"compilerPath": "/usr/bin/g++",
"cStandard": "c99",
"cppStandard": "gnu++11",
"intelliSenseMode": "linux-gcc-x64",
"configurationProvider": "ms-vscode.makefile-tools",
"compilerArgs": [
"-g -O -std=c++11 -DARCH_X86_64"
],
"compilerPathIsExplicit": true,
"cStandardIsExplicit": true,
"cppStandardIsExplicit": true,
"intelliSenseModeIsExplicit": true,
"mergeConfigurations": false,
"browse": {
"path": [
"/usr/lib/gcc/x86_64-linux-gnu/9/include/",
"${workspaceFolder}/**",
"${workspaceFolder}/common/include",
"${workspaceFolder}/include",
],
"limitSymbolsToIncludedHeaders": true
}
}
Custom browse configuration:
{
"browsePath": []
}
No active translation units.
```
### Screenshots
### Additional context
_No response_
|
non_usab
|
intellisense language version selection arbitrariness environment os and version ms windows vs code version c c extension version other extensions you installed and if the issue persists after disabling them c extension pack cmake with inferiors intellicode makefile tools if using ssh remote specify os of remote machine ubuntu after last vscode restart warnings about forced selection of higher language level started appearing in output window if these warnings are really describing the plugin logic its decision to force newer language versions is improper i don t know what versions were before restart due to automatic upgrade during restarts the project is single directory of what is edited in vscode with external directories of dependence projects not to be controlled the project is makefile based with own making logic and docker based compilation code analysis alleviation is defined using includepath and defines in plugin settings bug summary and steps to reproduce bug summary the following messages started appearing in output window for c source files the cstandard was changed from to based on compiler args and querying compilerpath usr bin g for c source files the cppstandard was changed from gnu to c based on compiler args and querying compilerpath usr bin g required language level as and gnu are explicitly specified in project settings c cpp properties json despite the present compiler aptitude the project shall be restricted to and c due to special target compilation steps to reproduce reopen the project folder and check contents of output window expected behavior no arbitrary selection of language version code sample and logs shell c cpp properties json configurations name linux includepath usr lib gcc linux gnu include workspacefolder workspacefolder common include workspacefolder include defines compilerpath usr bin g cstandard cppstandard gnu intellisensemode linux gcc configurationprovider ms vscode makefile tools compilerargs g o std c darch version from log diagnostics diagnostics am version current configuration name linux includepath usr lib gcc linux gnu include workspacefolder workspacefolder common include workspacefolder include defines compilerpath usr bin g cstandard cppstandard gnu intellisensemode linux gcc configurationprovider ms vscode makefile tools compilerargs g o std c darch compilerpathisexplicit true cstandardisexplicit true cppstandardisexplicit true intellisensemodeisexplicit true mergeconfigurations false browse path usr lib gcc linux gnu include workspacefolder workspacefolder common include workspacefolder include limitsymbolstoincludedheaders true custom browse configuration browsepath no active translation units screenshots additional context no response
| 0
|
112,787
| 14,288,949,551
|
IssuesEvent
|
2020-11-23 18:28:22
|
carbon-design-system/carbon-for-ibm-dotcom-website
|
https://api.github.com/repos/carbon-design-system/carbon-for-ibm-dotcom-website
|
closed
|
Content Publishing - Guidelines (04 Style model list and definitions)
|
Airtable Done content design website: Carbon for ibm.com
|
@JennySanchez commented on [Thu Sep 10 2020](https://github.com/carbon-design-system/ibm-dotcom-library/issues/3914)
#### User Story
> As an IBM.com Library components adopter,
> I need a way to learn more about the IBM.com Library,
> so that I can learn the detail through the guidelines and adopter IBM.com Library to my day to day work properly.
#### Additional information
- Work on the content by following the [publishing process](https://ibm.box.com/s/6oiqsvhxtchi1lfozyuw1soje67unbmj) as much as possible and as needed.
- Create the website design with the Sketch App as needed and the Sketch publishing template can be found on the [BOX folder](https://ibm.box.com/s/ma72t84m75fvd3qqkyz8cm6gfx9b7vou). Once complete, save the revised Sketch file in the Guideline folder / sub-folder [here](https://ibm.box.com/s/40lbqd2bfxwm1qv8k6dy8qwyq48qd6xg).
- Once the content is reviewed (with stakholders or SME of the topic) and finalized.
- Copy the content from the Sketch file into the .mdx file for the markdown publishing process to start.
- Once complete, create the Pull Request and review, using the Preview link, to be sure it matches the Sketch file design
- When ready to deploy, include Jenny as a PR Reviewer and Approver.
- Jenny will review and merge the PR
#### Acceptance criteria
- [ ] Content crafting is done.
- [ ] Asset image creation is done (if needed)
- [ ] Page design is done (if needed)
- [ ] Publishing with markdowns is done.
- [ ] QA'd by Jenny
- [ ] Web page preview is approved by Linda, Jeff, and Wonil
- [ ] Web page is published
|
1.0
|
Content Publishing - Guidelines (04 Style model list and definitions) - @JennySanchez commented on [Thu Sep 10 2020](https://github.com/carbon-design-system/ibm-dotcom-library/issues/3914)
#### User Story
> As an IBM.com Library components adopter,
> I need a way to learn more about the IBM.com Library,
> so that I can learn the detail through the guidelines and adopter IBM.com Library to my day to day work properly.
#### Additional information
- Work on the content by following the [publishing process](https://ibm.box.com/s/6oiqsvhxtchi1lfozyuw1soje67unbmj) as much as possible and as needed.
- Create the website design with the Sketch App as needed and the Sketch publishing template can be found on the [BOX folder](https://ibm.box.com/s/ma72t84m75fvd3qqkyz8cm6gfx9b7vou). Once complete, save the revised Sketch file in the Guideline folder / sub-folder [here](https://ibm.box.com/s/40lbqd2bfxwm1qv8k6dy8qwyq48qd6xg).
- Once the content is reviewed (with stakholders or SME of the topic) and finalized.
- Copy the content from the Sketch file into the .mdx file for the markdown publishing process to start.
- Once complete, create the Pull Request and review, using the Preview link, to be sure it matches the Sketch file design
- When ready to deploy, include Jenny as a PR Reviewer and Approver.
- Jenny will review and merge the PR
#### Acceptance criteria
- [ ] Content crafting is done.
- [ ] Asset image creation is done (if needed)
- [ ] Page design is done (if needed)
- [ ] Publishing with markdowns is done.
- [ ] QA'd by Jenny
- [ ] Web page preview is approved by Linda, Jeff, and Wonil
- [ ] Web page is published
|
non_usab
|
content publishing guidelines style model list and definitions jennysanchez commented on user story as an ibm com library components adopter i need a way to learn more about the ibm com library so that i can learn the detail through the guidelines and adopter ibm com library to my day to day work properly additional information work on the content by following the as much as possible and as needed create the website design with the sketch app as needed and the sketch publishing template can be found on the once complete save the revised sketch file in the guideline folder sub folder once the content is reviewed with stakholders or sme of the topic and finalized copy the content from the sketch file into the mdx file for the markdown publishing process to start once complete create the pull request and review using the preview link to be sure it matches the sketch file design when ready to deploy include jenny as a pr reviewer and approver jenny will review and merge the pr acceptance criteria content crafting is done asset image creation is done if needed page design is done if needed publishing with markdowns is done qa d by jenny web page preview is approved by linda jeff and wonil web page is published
| 0
|
26,314
| 26,689,608,525
|
IssuesEvent
|
2023-01-27 02:39:14
|
ZcashFoundation/zebra
|
https://api.github.com/repos/ZcashFoundation/zebra
|
closed
|
ci: snapshot a VM when a workflow job fails
|
A-devops C-enhancement S-needs-triage I-usability P-Optional :sparkles:
|
## Motivation
Sometimes is hard to diagnose the behavior of a specific VM if we don't have information from the internal VM logs (not exported in GitHub Actions nor GCP logs explorer)
### Designs
This could be a _snapshot_ but we could take other approaches:
- Exporting the logs to GitHub Actions as artifacts (to download and further investigate)
- Have a step to show (cat) the logs of sshd, syslog, etc in the GitHub console
|
True
|
ci: snapshot a VM when a workflow job fails - ## Motivation
Sometimes is hard to diagnose the behavior of a specific VM if we don't have information from the internal VM logs (not exported in GitHub Actions nor GCP logs explorer)
### Designs
This could be a _snapshot_ but we could take other approaches:
- Exporting the logs to GitHub Actions as artifacts (to download and further investigate)
- Have a step to show (cat) the logs of sshd, syslog, etc in the GitHub console
|
usab
|
ci snapshot a vm when a workflow job fails motivation sometimes is hard to diagnose the behavior of a specific vm if we don t have information from the internal vm logs not exported in github actions nor gcp logs explorer designs this could be a snapshot but we could take other approaches exporting the logs to github actions as artifacts to download and further investigate have a step to show cat the logs of sshd syslog etc in the github console
| 1
|
10,251
| 6,651,186,565
|
IssuesEvent
|
2017-09-28 19:05:10
|
naturenet/naturenet-www
|
https://api.github.com/repos/naturenet/naturenet-www
|
closed
|
Human-friendly error messages
|
question usability
|
Input validation is fairly friendly but most exceptions print the raw error message. We need a general "oops, something went wrong, try again later" kind of message for unpredictable exceptions, and maybe a "there's something wrong with this item" message for badly formatted data.
|
True
|
Human-friendly error messages - Input validation is fairly friendly but most exceptions print the raw error message. We need a general "oops, something went wrong, try again later" kind of message for unpredictable exceptions, and maybe a "there's something wrong with this item" message for badly formatted data.
|
usab
|
human friendly error messages input validation is fairly friendly but most exceptions print the raw error message we need a general oops something went wrong try again later kind of message for unpredictable exceptions and maybe a there s something wrong with this item message for badly formatted data
| 1
|
26,339
| 26,715,992,024
|
IssuesEvent
|
2023-01-28 14:16:46
|
bevyengine/bevy
|
https://api.github.com/repos/bevyengine/bevy
|
opened
|
Consider promoting `bevy::render::primitives::Aabb` to `bevy_math` for interop
|
C-Enhancement D-Good-First-Issue C-Usability A-Math
|
## What problem does this solve or what need does it fill?
This is similar to #5575 which was already merged, but this time for the 3D counterpart. There is no common `Aabb` type that can be easily reused and shared among crates, like `Vec3` or other math types. The current `bevy::render::primitives::Aabb` is in the render module, but it's generic enough to be used elsewhere.
## What solution would you like?
Either or all of, in order of priority:
1. "Promote" `bevy::render::primitives::Aabb`, which is a center-half-extent AABB with SIMD support (`Vec3A`) so is fairly general, to the `bevy_math` crate for sharing and reuse, without having to depend on an optional part of Bevy.
2. Add useful methods similar to what was done for `Rect` on #5575.
3. Evaluate if the center-half-extent is the best option. Min-max is an alternative with other nice properties. See for example https://fgiesen.wordpress.com/2013/01/14/min-max-under-negation-and-an-aabb-trick/ -- note that if changing the representation, we _might_ have to keep a render-only copy if the render library requires the current representation for optimization purpose.
## What alternative(s) have you considered?
Roll my own :'( -- see also #5575, same concerns.
|
True
|
Consider promoting `bevy::render::primitives::Aabb` to `bevy_math` for interop - ## What problem does this solve or what need does it fill?
This is similar to #5575 which was already merged, but this time for the 3D counterpart. There is no common `Aabb` type that can be easily reused and shared among crates, like `Vec3` or other math types. The current `bevy::render::primitives::Aabb` is in the render module, but it's generic enough to be used elsewhere.
## What solution would you like?
Either or all of, in order of priority:
1. "Promote" `bevy::render::primitives::Aabb`, which is a center-half-extent AABB with SIMD support (`Vec3A`) so is fairly general, to the `bevy_math` crate for sharing and reuse, without having to depend on an optional part of Bevy.
2. Add useful methods similar to what was done for `Rect` on #5575.
3. Evaluate if the center-half-extent is the best option. Min-max is an alternative with other nice properties. See for example https://fgiesen.wordpress.com/2013/01/14/min-max-under-negation-and-an-aabb-trick/ -- note that if changing the representation, we _might_ have to keep a render-only copy if the render library requires the current representation for optimization purpose.
## What alternative(s) have you considered?
Roll my own :'( -- see also #5575, same concerns.
|
usab
|
consider promoting bevy render primitives aabb to bevy math for interop what problem does this solve or what need does it fill this is similar to which was already merged but this time for the counterpart there is no common aabb type that can be easily reused and shared among crates like or other math types the current bevy render primitives aabb is in the render module but it s generic enough to be used elsewhere what solution would you like either or all of in order of priority promote bevy render primitives aabb which is a center half extent aabb with simd support so is fairly general to the bevy math crate for sharing and reuse without having to depend on an optional part of bevy add useful methods similar to what was done for rect on evaluate if the center half extent is the best option min max is an alternative with other nice properties see for example note that if changing the representation we might have to keep a render only copy if the render library requires the current representation for optimization purpose what alternative s have you considered roll my own see also same concerns
| 1
|
195,619
| 22,349,858,336
|
IssuesEvent
|
2022-06-15 11:03:12
|
turkdevops/atom
|
https://api.github.com/repos/turkdevops/atom
|
closed
|
CVE-2015-9251 (Medium) detected in jquery-2.2.4.tgz - autoclosed
|
security vulnerability
|
## CVE-2015-9251 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-2.2.4.tgz</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://registry.npmjs.org/jquery/-/jquery-2.2.4.tgz">https://registry.npmjs.org/jquery/-/jquery-2.2.4.tgz</a></p>
<p>Path to dependency file: /repo-with-submodules/You-Dont-Need-jQuery/package.json</p>
<p>Path to vulnerable library: /spec/fixtures/git/repo-with-submodules/You-Dont-Need-jQuery/node_modules/jquery/package.json</p>
<p>
Dependency Hierarchy:
- :x: **jquery-2.2.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/atom/commit/808ed16784ca49c0e5810becefba198982d2916e">808ed16784ca49c0e5810becefba198982d2916e</a></p>
<p>Found in base branch: <b>electron-upgrade</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>
jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.
<p>Publish Date: 2018-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-9251>CVE-2015-9251</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-9251">https://nvd.nist.gov/vuln/detail/CVE-2015-9251</a></p>
<p>Release Date: 2018-01-18</p>
<p>Fix Resolution: 3.0.0-alpha1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2015-9251 (Medium) detected in jquery-2.2.4.tgz - autoclosed - ## CVE-2015-9251 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-2.2.4.tgz</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://registry.npmjs.org/jquery/-/jquery-2.2.4.tgz">https://registry.npmjs.org/jquery/-/jquery-2.2.4.tgz</a></p>
<p>Path to dependency file: /repo-with-submodules/You-Dont-Need-jQuery/package.json</p>
<p>Path to vulnerable library: /spec/fixtures/git/repo-with-submodules/You-Dont-Need-jQuery/node_modules/jquery/package.json</p>
<p>
Dependency Hierarchy:
- :x: **jquery-2.2.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/atom/commit/808ed16784ca49c0e5810becefba198982d2916e">808ed16784ca49c0e5810becefba198982d2916e</a></p>
<p>Found in base branch: <b>electron-upgrade</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>
jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.
<p>Publish Date: 2018-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-9251>CVE-2015-9251</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-9251">https://nvd.nist.gov/vuln/detail/CVE-2015-9251</a></p>
<p>Release Date: 2018-01-18</p>
<p>Fix Resolution: 3.0.0-alpha1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_usab
|
cve medium detected in jquery tgz autoclosed cve medium severity vulnerability vulnerable library jquery tgz javascript library for dom operations library home page a href path to dependency file repo with submodules you dont need jquery package json path to vulnerable library spec fixtures git repo with submodules you dont need jquery node modules jquery package json dependency hierarchy x jquery tgz vulnerable library found in head commit a href found in base branch electron upgrade vulnerability details jquery before is vulnerable to cross site scripting xss attacks when a cross domain ajax request is performed without the datatype option causing text javascript responses to be executed publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend
| 0
|
6,466
| 4,308,038,486
|
IssuesEvent
|
2016-07-21 11:23:42
|
coreos/rkt
|
https://api.github.com/repos/coreos/rkt
|
opened
|
`rkt enter` for fly doesn't work, misleading error message
|
area/usability component/fly kind/friction low hanging fruit
|
When you `rkt enter` in to a pod running on fly, it fails. This is as intended. However, the error message should be improved.
Currently it is: `enter: not doing anything here!`. Ideally, it would just work. Less ideal but helpful would be to generate a copy-and-pasteable chroot command.
|
True
|
`rkt enter` for fly doesn't work, misleading error message - When you `rkt enter` in to a pod running on fly, it fails. This is as intended. However, the error message should be improved.
Currently it is: `enter: not doing anything here!`. Ideally, it would just work. Less ideal but helpful would be to generate a copy-and-pasteable chroot command.
|
usab
|
rkt enter for fly doesn t work misleading error message when you rkt enter in to a pod running on fly it fails this is as intended however the error message should be improved currently it is enter not doing anything here ideally it would just work less ideal but helpful would be to generate a copy and pasteable chroot command
| 1
|
8,558
| 5,823,836,875
|
IssuesEvent
|
2017-05-07 06:34:28
|
godotengine/godot
|
https://api.github.com/repos/godotengine/godot
|
opened
|
New Theme: Tree drag&drop visual helper is barely visible.
|
enhancement topic:editor usability
|
**Operating system or device - Godot version:**
Linux - Master
**Issue description:**
Dragging a Node around the SceneTree draws very thin black lines/boxes which are hard to spot.
|
True
|
New Theme: Tree drag&drop visual helper is barely visible. - **Operating system or device - Godot version:**
Linux - Master
**Issue description:**
Dragging a Node around the SceneTree draws very thin black lines/boxes which are hard to spot.
|
usab
|
new theme tree drag drop visual helper is barely visible operating system or device godot version linux master issue description dragging a node around the scenetree draws very thin black lines boxes which are hard to spot
| 1
|
138,112
| 20,329,601,582
|
IssuesEvent
|
2022-02-18 09:25:55
|
Altinn/altinn-studio
|
https://api.github.com/repos/Altinn/altinn-studio
|
closed
|
Implemented språk-page with react
|
kind/feature-request area/language solution/studio/designer status/draft Epic
|
## Description
Currently the språk-page is a razor page.
Design should probably also be revisited as there is little feedback to the user when text are updated and saved.
## Acceptance criteria
> Describe criteria here (i.e. What is allowed/not allowed (negative tesing), validations, error messages and warnings etc.)
## Tasks
- [ ] Specify design for the page
- [ ] Implement frontent for page
- [ ] Manual test
- [ ] Automated test
|
1.0
|
Implemented språk-page with react - ## Description
Currently the språk-page is a razor page.
Design should probably also be revisited as there is little feedback to the user when text are updated and saved.
## Acceptance criteria
> Describe criteria here (i.e. What is allowed/not allowed (negative tesing), validations, error messages and warnings etc.)
## Tasks
- [ ] Specify design for the page
- [ ] Implement frontent for page
- [ ] Manual test
- [ ] Automated test
|
non_usab
|
implemented språk page with react description currently the språk page is a razor page design should probably also be revisited as there is little feedback to the user when text are updated and saved acceptance criteria describe criteria here i e what is allowed not allowed negative tesing validations error messages and warnings etc tasks specify design for the page implement frontent for page manual test automated test
| 0
|
27,551
| 29,510,479,527
|
IssuesEvent
|
2023-06-03 21:39:14
|
tailscale/tailscale
|
https://api.github.com/repos/tailscale/tailscale
|
closed
|
Windows system assigning 169.254.x.y to Tailscale interface
|
OS-windows L1 Very few P3 Can't get started T5 Usability bug
|
### What is the issue?
After upgrading to 1.32.2, I cannot use tailscale and clash at the same time.This problem did not exist in previous versions.
### Steps to reproduce
1. Turn on the computer
2. Clash starts automatically
3. The tailscale starts automatically
4. Tailscale fault
### Are there any recent changes that introduced the issue?
Upgrade to 1.32.2
### OS
Windows
### OS version
Windows 11
### Tailscale version
1.32.2
### Bug report
BUG-74125bd68196d21869f61957f8a397b52da29f72d25d05139c8442854120384d-20221027051956Z-f9b252de146014e9
|
True
|
Windows system assigning 169.254.x.y to Tailscale interface - ### What is the issue?
After upgrading to 1.32.2, I cannot use tailscale and clash at the same time.This problem did not exist in previous versions.
### Steps to reproduce
1. Turn on the computer
2. Clash starts automatically
3. The tailscale starts automatically
4. Tailscale fault
### Are there any recent changes that introduced the issue?
Upgrade to 1.32.2
### OS
Windows
### OS version
Windows 11
### Tailscale version
1.32.2
### Bug report
BUG-74125bd68196d21869f61957f8a397b52da29f72d25d05139c8442854120384d-20221027051956Z-f9b252de146014e9
|
usab
|
windows system assigning x y to tailscale interface what is the issue after upgrading to i cannot use tailscale and clash at the same time this problem did not exist in previous versions steps to reproduce turn on the computer clash starts automatically the tailscale starts automatically tailscale fault are there any recent changes that introduced the issue upgrade to os windows os version windows tailscale version bug report bug
| 1
|
607
| 2,609,178,570
|
IssuesEvent
|
2015-02-26 13:05:47
|
cambridge-alpha-team/unvisual-frontend
|
https://api.github.com/repos/cambridge-alpha-team/unvisual-frontend
|
closed
|
Redesign menu structure
|
discuss-this usability wontfix
|
Our user testing showed the following:
- keeping track of where we are in the tree is hard.
- nesting is a Bad Thing, and makes getting lost even easier.
So it's important that the menu system is **simple**, and that we have as **few levels** of nesting as possible.
In our current design, there is a direct mapping between the structure of the menu system and the Sonic Pi code. I believe we should divorce the two.
In particular, the way synths/effects are handled is very difficult to manage. In Ruby, they are *nested* control structures:
```ruby
live_loop :foo do
with_fx :ixi_techno do
with_fx :reverb, amp: 3, room: 0.8, damp: 0.5 do
with_fx :distortion do
sample :loop_amen
sleep sample_duration :loop_amen
end
end
end
end
```
Adding nested control structures such as `with_fx` to the tree is confusing:
- It's not clear where they will be added.
- It's not clear where the user will end up (discussed in #6).
- There's no way to add them **around** a set of notes, nor is it clear how we could facilitate this.
- There's no way to **rearrange** them—eg. if above we wanted the `reverb` to come before the `distortion`, which would produce a different musical effect—and again, this would be non-obvious to design and confusing to use.
- They **increase nesting**—to an unbounded number of levels.
The thing is, adding an effect *around* a set of statements—usually, the entire body of the loop—is the most common thing to want to do!
I propose that these control structures—`use_synth`, `with_fx`—should *not* be nested. Instead, since lists are much easier to manage than nesting, we should have a **list of effects**. (Probably, this should be separate from the main body of the loop: maybe have two lists, one with effects and one with statements? Either way, removing nested control structures is important.)
I believe doing this will also allow us greater flexibility when adding support for cubelets. For example, to change parameters on a note while it's playing—which we certainly want—you need to generate extra pieces of Sonic Pi code that run `control` instructions several times a second to update the synth parameter. For example (taken from the demo in London):
```ruby
live_loop :bar do
use_synth :prophet
scale = scale(:C, :minor_pentatonic)
note = scale.choose
s = play note, amp: test / 255.0, release: 3
10.times do
if dist != 0 then
control s, note: (dist / 5) + 64
end
control s, cutoff: knob * 70 / 255.0 + 50
sleep 0.1
end
end
```
I believe making the menu system different and simpler from Sonic Pi code will make things like generating `control` instructions easier to implement.
Our menu system is already different from Sonic Pi code: the text on the nodes is not exactly the same, for example. And it's already clear that we need to change the names further, since the ones in Sonic Pi are confusing (see #19). We're abstracting away names, and I'd argue we need to abstract away the structure as well.
Our tree structure should be its own language, distinct from and simpler than Sonic Pi.
---
> Relevant to: #20, #13
|
True
|
Redesign menu structure - Our user testing showed the following:
- keeping track of where we are in the tree is hard.
- nesting is a Bad Thing, and makes getting lost even easier.
So it's important that the menu system is **simple**, and that we have as **few levels** of nesting as possible.
In our current design, there is a direct mapping between the structure of the menu system and the Sonic Pi code. I believe we should divorce the two.
In particular, the way synths/effects are handled is very difficult to manage. In Ruby, they are *nested* control structures:
```ruby
live_loop :foo do
with_fx :ixi_techno do
with_fx :reverb, amp: 3, room: 0.8, damp: 0.5 do
with_fx :distortion do
sample :loop_amen
sleep sample_duration :loop_amen
end
end
end
end
```
Adding nested control structures such as `with_fx` to the tree is confusing:
- It's not clear where they will be added.
- It's not clear where the user will end up (discussed in #6).
- There's no way to add them **around** a set of notes, nor is it clear how we could facilitate this.
- There's no way to **rearrange** them—eg. if above we wanted the `reverb` to come before the `distortion`, which would produce a different musical effect—and again, this would be non-obvious to design and confusing to use.
- They **increase nesting**—to an unbounded number of levels.
The thing is, adding an effect *around* a set of statements—usually, the entire body of the loop—is the most common thing to want to do!
I propose that these control structures—`use_synth`, `with_fx`—should *not* be nested. Instead, since lists are much easier to manage than nesting, we should have a **list of effects**. (Probably, this should be separate from the main body of the loop: maybe have two lists, one with effects and one with statements? Either way, removing nested control structures is important.)
I believe doing this will also allow us greater flexibility when adding support for cubelets. For example, to change parameters on a note while it's playing—which we certainly want—you need to generate extra pieces of Sonic Pi code that run `control` instructions several times a second to update the synth parameter. For example (taken from the demo in London):
```ruby
live_loop :bar do
use_synth :prophet
scale = scale(:C, :minor_pentatonic)
note = scale.choose
s = play note, amp: test / 255.0, release: 3
10.times do
if dist != 0 then
control s, note: (dist / 5) + 64
end
control s, cutoff: knob * 70 / 255.0 + 50
sleep 0.1
end
end
```
I believe making the menu system different and simpler from Sonic Pi code will make things like generating `control` instructions easier to implement.
Our menu system is already different from Sonic Pi code: the text on the nodes is not exactly the same, for example. And it's already clear that we need to change the names further, since the ones in Sonic Pi are confusing (see #19). We're abstracting away names, and I'd argue we need to abstract away the structure as well.
Our tree structure should be its own language, distinct from and simpler than Sonic Pi.
---
> Relevant to: #20, #13
|
usab
|
redesign menu structure our user testing showed the following keeping track of where we are in the tree is hard nesting is a bad thing and makes getting lost even easier so it s important that the menu system is simple and that we have as few levels of nesting as possible in our current design there is a direct mapping between the structure of the menu system and the sonic pi code i believe we should divorce the two in particular the way synths effects are handled is very difficult to manage in ruby they are nested control structures ruby live loop foo do with fx ixi techno do with fx reverb amp room damp do with fx distortion do sample loop amen sleep sample duration loop amen end end end end adding nested control structures such as with fx to the tree is confusing it s not clear where they will be added it s not clear where the user will end up discussed in there s no way to add them around a set of notes nor is it clear how we could facilitate this there s no way to rearrange them—eg if above we wanted the reverb to come before the distortion which would produce a different musical effect—and again this would be non obvious to design and confusing to use they increase nesting —to an unbounded number of levels the thing is adding an effect around a set of statements—usually the entire body of the loop—is the most common thing to want to do i propose that these control structures— use synth with fx —should not be nested instead since lists are much easier to manage than nesting we should have a list of effects probably this should be separate from the main body of the loop maybe have two lists one with effects and one with statements either way removing nested control structures is important i believe doing this will also allow us greater flexibility when adding support for cubelets for example to change parameters on a note while it s playing—which we certainly want—you need to generate extra pieces of sonic pi code that run control instructions several times a second to update the synth parameter for example taken from the demo in london ruby live loop bar do use synth prophet scale scale c minor pentatonic note scale choose s play note amp test release times do if dist then control s note dist end control s cutoff knob sleep end end i believe making the menu system different and simpler from sonic pi code will make things like generating control instructions easier to implement our menu system is already different from sonic pi code the text on the nodes is not exactly the same for example and it s already clear that we need to change the names further since the ones in sonic pi are confusing see we re abstracting away names and i d argue we need to abstract away the structure as well our tree structure should be its own language distinct from and simpler than sonic pi relevant to
| 1
|
378,183
| 26,286,258,413
|
IssuesEvent
|
2023-01-07 21:39:25
|
mlfoundations/open_clip
|
https://api.github.com/repos/mlfoundations/open_clip
|
closed
|
braceexpand has unexpected (non-bash-like) behavior with multiple expansions
|
documentation
|
If you provide bash a command like "foo{0..5} bar{1..6}" it will expand each of the brace expansions separately, give you a list of length 10. Braceexpand will do the cross product here though, and give a list of length 25. This isn't necessarily wrong in general, but in the case of how braceexpand is used in this project I think it's not what's expected.
In particular, if you provide --train-data="/dir1/files{1..10} /dir2/files{1..10}" it ends up trying to include 100 (!!) files. It would probably make more sense to do the bash-like expansion here.
|
1.0
|
braceexpand has unexpected (non-bash-like) behavior with multiple expansions - If you provide bash a command like "foo{0..5} bar{1..6}" it will expand each of the brace expansions separately, give you a list of length 10. Braceexpand will do the cross product here though, and give a list of length 25. This isn't necessarily wrong in general, but in the case of how braceexpand is used in this project I think it's not what's expected.
In particular, if you provide --train-data="/dir1/files{1..10} /dir2/files{1..10}" it ends up trying to include 100 (!!) files. It would probably make more sense to do the bash-like expansion here.
|
non_usab
|
braceexpand has unexpected non bash like behavior with multiple expansions if you provide bash a command like foo bar it will expand each of the brace expansions separately give you a list of length braceexpand will do the cross product here though and give a list of length this isn t necessarily wrong in general but in the case of how braceexpand is used in this project i think it s not what s expected in particular if you provide train data files files it ends up trying to include files it would probably make more sense to do the bash like expansion here
| 0
|
7,829
| 5,241,119,603
|
IssuesEvent
|
2017-01-31 14:58:35
|
github/VisualStudio
|
https://api.github.com/repos/github/VisualStudio
|
closed
|
Inconsistent UI state in PR details view
|
bug usability
|
I tried to pull and got a merge conflict due to the remote branch being force-pushed, which left changed files on the local checkout. I reset the branch on the command line, which caused the ✔️ "Local branch up to date" message to show up, but the "4 uncommitted changes would be overwritten by merge" error never went away.
Steps to repro:
- Checkout a PR branch
- Force-push to the remote branch
- Switch to another branch locally
- Checkout the PR branch again
- Click on pull
- Click on pull again
- Merge error message shows up
- Reset the branch on the command line to match the remote branch. Validate that local merge conflict files are gone and there's no locally changed files on git status
- ✔️ message shows up, error message never goes away.
|
True
|
Inconsistent UI state in PR details view - 
I tried to pull and got a merge conflict due to the remote branch being force-pushed, which left changed files on the local checkout. I reset the branch on the command line, which caused the ✔️ "Local branch up to date" message to show up, but the "4 uncommitted changes would be overwritten by merge" error never went away.
Steps to repro:
- Checkout a PR branch
- Force-push to the remote branch
- Switch to another branch locally
- Checkout the PR branch again
- Click on pull
- Click on pull again
- Merge error message shows up
- Reset the branch on the command line to match the remote branch. Validate that local merge conflict files are gone and there's no locally changed files on git status
- ✔️ message shows up, error message never goes away.
|
usab
|
inconsistent ui state in pr details view i tried to pull and got a merge conflict due to the remote branch being force pushed which left changed files on the local checkout i reset the branch on the command line which caused the ✔️ local branch up to date message to show up but the uncommitted changes would be overwritten by merge error never went away steps to repro checkout a pr branch force push to the remote branch switch to another branch locally checkout the pr branch again click on pull click on pull again merge error message shows up reset the branch on the command line to match the remote branch validate that local merge conflict files are gone and there s no locally changed files on git status ✔️ message shows up error message never goes away
| 1
|
717,975
| 24,698,584,973
|
IssuesEvent
|
2022-10-19 13:50:20
|
Accenture/sfmc-devtools-copado
|
https://api.github.com/repos/Accenture/sfmc-devtools-copado
|
closed
|
[TEST] deploy changes/additions to existing config to 1-n BUs
|
enhancement PRIORITY node.js
|
request by Christine.
this is us testing our #2 pipeline:
1. create multiple changes
2. commit these into separate user stories (sometimes 2 changes, sometimes just 1 per US)
3. promote & deploy to "pre-target"
4. confirm deployment worked (in SFMC); confirm target BU's folder in git master branch (github)
5. try to selectively back-promote 1 user story to 1 prod BU
6. confirm deployment worked (in SFMC); confirm target BU's folder in git master branch (github)
7. try to selectively back-promote 2 user stories at once to 1 prod BU
8. confirm deployment worked (in SFMC); confirm target BU's folder in git master branch (github)
9. try to use mass-backpromote feature to deploy all remaining user stories to both prod BUs
10. confirm deployment worked
|
1.0
|
[TEST] deploy changes/additions to existing config to 1-n BUs - request by Christine.
this is us testing our #2 pipeline:
1. create multiple changes
2. commit these into separate user stories (sometimes 2 changes, sometimes just 1 per US)
3. promote & deploy to "pre-target"
4. confirm deployment worked (in SFMC); confirm target BU's folder in git master branch (github)
5. try to selectively back-promote 1 user story to 1 prod BU
6. confirm deployment worked (in SFMC); confirm target BU's folder in git master branch (github)
7. try to selectively back-promote 2 user stories at once to 1 prod BU
8. confirm deployment worked (in SFMC); confirm target BU's folder in git master branch (github)
9. try to use mass-backpromote feature to deploy all remaining user stories to both prod BUs
10. confirm deployment worked
|
non_usab
|
deploy changes additions to existing config to n bus request by christine this is us testing our pipeline create multiple changes commit these into separate user stories sometimes changes sometimes just per us promote deploy to pre target confirm deployment worked in sfmc confirm target bu s folder in git master branch github try to selectively back promote user story to prod bu confirm deployment worked in sfmc confirm target bu s folder in git master branch github try to selectively back promote user stories at once to prod bu confirm deployment worked in sfmc confirm target bu s folder in git master branch github try to use mass backpromote feature to deploy all remaining user stories to both prod bus confirm deployment worked
| 0
|
14,710
| 9,437,741,841
|
IssuesEvent
|
2019-04-13 17:30:24
|
bird-get/terminal-hud
|
https://api.github.com/repos/bird-get/terminal-hud
|
opened
|
Add extension programs to help output
|
enhancement usability
|
It would be very helpful if the `help` command would output info about extension programs; it would make it easier to see which commands are available.
This requires extension programs to declare a short help message that can be accessed by the help function.
|
True
|
Add extension programs to help output - It would be very helpful if the `help` command would output info about extension programs; it would make it easier to see which commands are available.
This requires extension programs to declare a short help message that can be accessed by the help function.
|
usab
|
add extension programs to help output it would be very helpful if the help command would output info about extension programs it would make it easier to see which commands are available this requires extension programs to declare a short help message that can be accessed by the help function
| 1
|
786,487
| 27,657,055,958
|
IssuesEvent
|
2023-03-12 03:53:12
|
CodeforHawaii/HIERR
|
https://api.github.com/repos/CodeforHawaii/HIERR
|
closed
|
Add option for user to reselect their census tract data
|
High Priority
|
If the user has previously selected their census tract, they should have the option to reselect it if they log in again.
|
1.0
|
Add option for user to reselect their census tract data - If the user has previously selected their census tract, they should have the option to reselect it if they log in again.
|
non_usab
|
add option for user to reselect their census tract data if the user has previously selected their census tract they should have the option to reselect it if they log in again
| 0
|
159,755
| 12,489,787,969
|
IssuesEvent
|
2020-05-31 20:31:20
|
RPTools/maptool
|
https://api.github.com/repos/RPTools/maptool
|
closed
|
getMacroProps returns misnamed property "toolapplyToSelected"
|
bug tested
|
**Describe the bug**
The json returned by `getMacroProps` returns the property `toolapplyToSelected`.
The property name should be `applyToSelected` instead.
**To Reproduce**
Steps to reproduce the behavior:
1. Use `getMacroProps` on a macro.
2. Notice the included property `toolapplyToSelected` and the missing `appyToSelected`
**Expected behavior**
The property is named `appyToSelected`
**MapTool Info**
- Version: 1.7.0
- Install: New
**Desktop (please complete the following information):**
- OS: Windows
- Version: 10
|
1.0
|
getMacroProps returns misnamed property "toolapplyToSelected" - **Describe the bug**
The json returned by `getMacroProps` returns the property `toolapplyToSelected`.
The property name should be `applyToSelected` instead.
**To Reproduce**
Steps to reproduce the behavior:
1. Use `getMacroProps` on a macro.
2. Notice the included property `toolapplyToSelected` and the missing `appyToSelected`
**Expected behavior**
The property is named `appyToSelected`
**MapTool Info**
- Version: 1.7.0
- Install: New
**Desktop (please complete the following information):**
- OS: Windows
- Version: 10
|
non_usab
|
getmacroprops returns misnamed property toolapplytoselected describe the bug the json returned by getmacroprops returns the property toolapplytoselected the property name should be applytoselected instead to reproduce steps to reproduce the behavior use getmacroprops on a macro notice the included property toolapplytoselected and the missing appytoselected expected behavior the property is named appytoselected maptool info version install new desktop please complete the following information os windows version
| 0
|
18,601
| 13,090,116,827
|
IssuesEvent
|
2020-08-03 02:11:23
|
apache/cloudstack-primate
|
https://api.github.com/repos/apache/cloudstack-primate
|
closed
|
[FEATURE] VM deployment suggestion: ask for #num of VMs
|
enhancement feature usability
|
Gist - user report is asking for:
~- Quick view actions in list view~ See #458
- Ability to specify number of VMs in VM deployment form
Original report:
~1) Allow to create a site to site vpn to a regular isolated network instead of just a vpc. right now site-to-site vpn is only allowed to a vpc.~ Not a UI issue
2) action buttons on virtual machines from the instance tab. right now users are only allow to take actions(shutdown, delete, etc) on virtual machines after clicking on the virtual machine.
3) create multiple virtual machines from the VM creation form. ask me how many virtual machines I want to create from a single virtual machine creation form.
apologies if this isnt clear enough. not very good at putting my thoughts in writing.
|
True
|
[FEATURE] VM deployment suggestion: ask for #num of VMs - Gist - user report is asking for:
~- Quick view actions in list view~ See #458
- Ability to specify number of VMs in VM deployment form
Original report:
~1) Allow to create a site to site vpn to a regular isolated network instead of just a vpc. right now site-to-site vpn is only allowed to a vpc.~ Not a UI issue
2) action buttons on virtual machines from the instance tab. right now users are only allow to take actions(shutdown, delete, etc) on virtual machines after clicking on the virtual machine.
3) create multiple virtual machines from the VM creation form. ask me how many virtual machines I want to create from a single virtual machine creation form.
apologies if this isnt clear enough. not very good at putting my thoughts in writing.
|
usab
|
vm deployment suggestion ask for num of vms gist user report is asking for quick view actions in list view see ability to specify number of vms in vm deployment form original report allow to create a site to site vpn to a regular isolated network instead of just a vpc right now site to site vpn is only allowed to a vpc not a ui issue action buttons on virtual machines from the instance tab right now users are only allow to take actions shutdown delete etc on virtual machines after clicking on the virtual machine create multiple virtual machines from the vm creation form ask me how many virtual machines i want to create from a single virtual machine creation form apologies if this isnt clear enough not very good at putting my thoughts in writing
| 1
|
213,849
| 7,260,902,990
|
IssuesEvent
|
2018-02-18 15:26:47
|
PaulL48/SOEN341-SC4
|
https://api.github.com/repos/PaulL48/SOEN341-SC4
|
closed
|
Add answer accepting back-end
|
back-end feature priority: high risk: low sp 3
|
Add or modify a database to store whether an answer is deemed the correct one for a particular question, and a function to mark an answer as the correct one and prevent multiple answers on the same question from being deemed correct.
|
1.0
|
Add answer accepting back-end - Add or modify a database to store whether an answer is deemed the correct one for a particular question, and a function to mark an answer as the correct one and prevent multiple answers on the same question from being deemed correct.
|
non_usab
|
add answer accepting back end add or modify a database to store whether an answer is deemed the correct one for a particular question and a function to mark an answer as the correct one and prevent multiple answers on the same question from being deemed correct
| 0
|
3,081
| 3,322,533,843
|
IssuesEvent
|
2015-11-09 14:56:24
|
QupZilla/qupzilla
|
https://api.github.com/repos/QupZilla/qupzilla
|
closed
|
Feature Request - Please move/copy spell-check dictionary settings to main Preferences panel
|
Usability
|
For new users, it may be difficult to find the spell-check dictionary options by doing "right-click input element -> Languages -> Settings".
Can these settings be moved or duplicated in the main Preferences panel, maybe under the 'General' tab, for easier access?
Thanks :smile:
|
True
|
Feature Request - Please move/copy spell-check dictionary settings to main Preferences panel - For new users, it may be difficult to find the spell-check dictionary options by doing "right-click input element -> Languages -> Settings".
Can these settings be moved or duplicated in the main Preferences panel, maybe under the 'General' tab, for easier access?
Thanks :smile:
|
usab
|
feature request please move copy spell check dictionary settings to main preferences panel for new users it may be difficult to find the spell check dictionary options by doing right click input element languages settings can these settings be moved or duplicated in the main preferences panel maybe under the general tab for easier access thanks smile
| 1
|
16,413
| 10,886,722,803
|
IssuesEvent
|
2019-11-18 13:11:43
|
peeringdb/peeringdb
|
https://api.github.com/repos/peeringdb/peeringdb
|
closed
|
Better error message when user tries to add a record (basically network) with status "deleted"
|
AC Minor usability
|
PDB does not really delete network records but simply flags them as deleted. If a user tries to add such a network s/he gets the error message
"network with this asn already exists"
Please change this to
"network has been deleted. Please contact support@peeringdb.com"
|
True
|
Better error message when user tries to add a record (basically network) with status "deleted" - PDB does not really delete network records but simply flags them as deleted. If a user tries to add such a network s/he gets the error message
"network with this asn already exists"
Please change this to
"network has been deleted. Please contact support@peeringdb.com"
|
usab
|
better error message when user tries to add a record basically network with status deleted pdb does not really delete network records but simply flags them as deleted if a user tries to add such a network s he gets the error message network with this asn already exists please change this to network has been deleted please contact support peeringdb com
| 1
|
25,244
| 24,917,871,162
|
IssuesEvent
|
2022-10-30 16:14:16
|
tailscale/tailscale
|
https://api.github.com/repos/tailscale/tailscale
|
closed
|
exit-node-allow-lan-access doesn't handle VLANs
|
OS-linux L1 Very few P2 Aggravating T5 Usability exit-node
|
Did we break `--exit-node-allow-lan-access`? It's not working on Linux in 1.20.1.
Sorry, screenshot, as I'm console'd into a remote machine I lost ssh to:
<img width="1321" alt="Screen Shot 2022-01-17 at 8 54 55 AM" src="https://user-images.githubusercontent.com/2621/149810220-2a316380-a4ff-47b9-b718-061ffeae4f95.png">
/cc @danderson @maisem
|
True
|
exit-node-allow-lan-access doesn't handle VLANs - Did we break `--exit-node-allow-lan-access`? It's not working on Linux in 1.20.1.
Sorry, screenshot, as I'm console'd into a remote machine I lost ssh to:
<img width="1321" alt="Screen Shot 2022-01-17 at 8 54 55 AM" src="https://user-images.githubusercontent.com/2621/149810220-2a316380-a4ff-47b9-b718-061ffeae4f95.png">
/cc @danderson @maisem
|
usab
|
exit node allow lan access doesn t handle vlans did we break exit node allow lan access it s not working on linux in sorry screenshot as i m console d into a remote machine i lost ssh to img width alt screen shot at am src cc danderson maisem
| 1
|
2,983
| 3,274,858,818
|
IssuesEvent
|
2015-10-26 13:15:47
|
grafana/grafana
|
https://api.github.com/repos/grafana/grafana
|
closed
|
Add Move Row to Top or Bottom
|
comp: dashboard type: ui/usability
|
Currently there is a Move Up and Move Down command for rows. Add two more options that will move the row all the way to the top or bottom on the page.
|
True
|
Add Move Row to Top or Bottom - Currently there is a Move Up and Move Down command for rows. Add two more options that will move the row all the way to the top or bottom on the page.
|
usab
|
add move row to top or bottom currently there is a move up and move down command for rows add two more options that will move the row all the way to the top or bottom on the page
| 1
|
110,998
| 4,446,383,406
|
IssuesEvent
|
2016-08-20 16:54:13
|
enviPath/enviPath
|
https://api.github.com/repos/enviPath/enviPath
|
closed
|
Remove editing option from pathway when no write permissions
|
high priority
|
If the user has no writing permissions, he still seed the the editing options, this should be removed, similar to the other objects.
|
1.0
|
Remove editing option from pathway when no write permissions - If the user has no writing permissions, he still seed the the editing options, this should be removed, similar to the other objects.
|
non_usab
|
remove editing option from pathway when no write permissions if the user has no writing permissions he still seed the the editing options this should be removed similar to the other objects
| 0
|
227,434
| 17,382,659,911
|
IssuesEvent
|
2021-08-01 02:32:09
|
ultraq/thymeleaf-layout-dialect
|
https://api.github.com/repos/ultraq/thymeleaf-layout-dialect
|
closed
|
Deprecations/deletions for version 3
|
breaking change documentation
|
Deprecated things to delete and document in a migration guide for version 3:
- [x] `DecoratorProcessor` for `layout:decorator`, replaced by `layout:decorate`, #95
- [x] `$DECORATOR_TITLE` from the `layout:title-pattern` processor, replaced by `$LAYOUT_TITLE`, #95
- [x] `AppendingStrategy` for processing `<head>` sections, replaced by `AppendingRespectLayoutTitleStrategy` which will be renamed to take its place, #177
- [x] `GroupingStrategy` for processing `<head>` sections, replaced by `GroupingRespectLayoutTitleStrategy` which will be renamed to take its place, #177
New deprecations for version 3:
- [x] `CollectFragmentProcessor` for `layout:collect`, with no replacement, #166
Deprecations that will remain for version 3:
- `IncludeProcessor` for `layout:include`, was targeting a release of Thymeleaf 3.1+
|
1.0
|
Deprecations/deletions for version 3 - Deprecated things to delete and document in a migration guide for version 3:
- [x] `DecoratorProcessor` for `layout:decorator`, replaced by `layout:decorate`, #95
- [x] `$DECORATOR_TITLE` from the `layout:title-pattern` processor, replaced by `$LAYOUT_TITLE`, #95
- [x] `AppendingStrategy` for processing `<head>` sections, replaced by `AppendingRespectLayoutTitleStrategy` which will be renamed to take its place, #177
- [x] `GroupingStrategy` for processing `<head>` sections, replaced by `GroupingRespectLayoutTitleStrategy` which will be renamed to take its place, #177
New deprecations for version 3:
- [x] `CollectFragmentProcessor` for `layout:collect`, with no replacement, #166
Deprecations that will remain for version 3:
- `IncludeProcessor` for `layout:include`, was targeting a release of Thymeleaf 3.1+
|
non_usab
|
deprecations deletions for version deprecated things to delete and document in a migration guide for version decoratorprocessor for layout decorator replaced by layout decorate decorator title from the layout title pattern processor replaced by layout title appendingstrategy for processing sections replaced by appendingrespectlayouttitlestrategy which will be renamed to take its place groupingstrategy for processing sections replaced by groupingrespectlayouttitlestrategy which will be renamed to take its place new deprecations for version collectfragmentprocessor for layout collect with no replacement deprecations that will remain for version includeprocessor for layout include was targeting a release of thymeleaf
| 0
|
370,065
| 25,885,066,685
|
IssuesEvent
|
2022-12-14 14:01:38
|
equinor/ert
|
https://api.github.com/repos/equinor/ert
|
closed
|
Document polynomial
|
documentation ert3
|
Make `README` in the polynomial example that explains how to run it and why it is as it is.
|
1.0
|
Document polynomial - Make `README` in the polynomial example that explains how to run it and why it is as it is.
|
non_usab
|
document polynomial make readme in the polynomial example that explains how to run it and why it is as it is
| 0
|
2,835
| 2,717,354,287
|
IssuesEvent
|
2015-04-11 06:15:15
|
zenparsing/esparse
|
https://api.github.com/repos/zenparsing/esparse
|
closed
|
User's Guide
|
documentation
|
Create a user's guide which will contain:
- An API reference
- An AST reference
- Installation and basic usage instructions for Node, browser, etc.
|
1.0
|
User's Guide - Create a user's guide which will contain:
- An API reference
- An AST reference
- Installation and basic usage instructions for Node, browser, etc.
|
non_usab
|
user s guide create a user s guide which will contain an api reference an ast reference installation and basic usage instructions for node browser etc
| 0
|
20,141
| 15,077,824,446
|
IssuesEvent
|
2021-02-05 07:41:33
|
argoproj/argo-cd
|
https://api.github.com/repos/argoproj/argo-cd
|
closed
|
Send Access-Control-Allow-Origin: * response headers for status badges
|
component:api enhancement type:usability
|
# Summary
Currently, status badges cannot be fetched via XHR (fetch requests) from frontend applications without running into CORS issues. If an `Access-Control-Allow-Origin: *` response header was present for status badges, custom logic could be added to frontend applications e.g. only displaying badges if Argo CD is reachable.
# Motivation
If Argo CD runs behind a VPN connection, it might not be reachable from a user’s browser if no connection to the VPN is established. Currently, the only way to embed badges is by directly adding `<img src="<badgeUrl>"`. If Argo CD is not reachable, this would lead to a broken image. If CORS was possible, one could nicely handle this case using JavaScript.
Even though this header could be added by an Ingress, Application Load Balancer, ... it would be nice if it was provided out of the box.
# Proposal
* Send `Access-Control-Allow-Origin: *` response header for status badges
* *Optional*: Make it configurable whether this header should be sent
|
True
|
Send Access-Control-Allow-Origin: * response headers for status badges - # Summary
Currently, status badges cannot be fetched via XHR (fetch requests) from frontend applications without running into CORS issues. If an `Access-Control-Allow-Origin: *` response header was present for status badges, custom logic could be added to frontend applications e.g. only displaying badges if Argo CD is reachable.
# Motivation
If Argo CD runs behind a VPN connection, it might not be reachable from a user’s browser if no connection to the VPN is established. Currently, the only way to embed badges is by directly adding `<img src="<badgeUrl>"`. If Argo CD is not reachable, this would lead to a broken image. If CORS was possible, one could nicely handle this case using JavaScript.
Even though this header could be added by an Ingress, Application Load Balancer, ... it would be nice if it was provided out of the box.
# Proposal
* Send `Access-Control-Allow-Origin: *` response header for status badges
* *Optional*: Make it configurable whether this header should be sent
|
usab
|
send access control allow origin response headers for status badges summary currently status badges cannot be fetched via xhr fetch requests from frontend applications without running into cors issues if an access control allow origin response header was present for status badges custom logic could be added to frontend applications e g only displaying badges if argo cd is reachable motivation if argo cd runs behind a vpn connection it might not be reachable from a user’s browser if no connection to the vpn is established currently the only way to embed badges is by directly adding if argo cd is not reachable this would lead to a broken image if cors was possible one could nicely handle this case using javascript even though this header could be added by an ingress application load balancer it would be nice if it was provided out of the box proposal send access control allow origin response header for status badges optional make it configurable whether this header should be sent
| 1
|
20,115
| 15,029,337,502
|
IssuesEvent
|
2021-02-02 05:19:15
|
ryanclark/karma-webpack
|
https://api.github.com/repos/ryanclark/karma-webpack
|
closed
|
Improve Error Message: Module not found: Error: Cannot resolve 'file' or 'directory'
|
hotlist: usability
|
Hi There,
Can you guys please help me fixing this issue.
I have two .jsx files one imported under another one.
Lets say,
A.jsx(Inside A.jsx I have imported the B.jsx)
B.jsx
When both the files are written under same file in that case unit test cases working fine. The moment I am separating it out, still the component is working fine but the unit test cases are not running. Webpack karma throwing an error saying
`
ERROR in ./src/components/thpfooter/index.jsx
Module not found: Error: Cannot resolve 'file' or 'directory' ./ThpFooterList in /Users/zi02/projects/creps_ui_components_library/src/components/thpfooter
@ ./src/components/thpfooter/index.jsx 9:1725-1751
`
Thanks,
Kshirodra
|
True
|
Improve Error Message: Module not found: Error: Cannot resolve 'file' or 'directory' - Hi There,
Can you guys please help me fixing this issue.
I have two .jsx files one imported under another one.
Lets say,
A.jsx(Inside A.jsx I have imported the B.jsx)
B.jsx
When both the files are written under same file in that case unit test cases working fine. The moment I am separating it out, still the component is working fine but the unit test cases are not running. Webpack karma throwing an error saying
`
ERROR in ./src/components/thpfooter/index.jsx
Module not found: Error: Cannot resolve 'file' or 'directory' ./ThpFooterList in /Users/zi02/projects/creps_ui_components_library/src/components/thpfooter
@ ./src/components/thpfooter/index.jsx 9:1725-1751
`
Thanks,
Kshirodra
|
usab
|
improve error message module not found error cannot resolve file or directory hi there can you guys please help me fixing this issue i have two jsx files one imported under another one lets say a jsx inside a jsx i have imported the b jsx b jsx when both the files are written under same file in that case unit test cases working fine the moment i am separating it out still the component is working fine but the unit test cases are not running webpack karma throwing an error saying error in src components thpfooter index jsx module not found error cannot resolve file or directory thpfooterlist in users projects creps ui components library src components thpfooter src components thpfooter index jsx thanks kshirodra
| 1
|
9,607
| 6,412,074,659
|
IssuesEvent
|
2017-08-08 01:36:37
|
FReBOmusic/FReBO
|
https://api.github.com/repos/FReBOmusic/FReBO
|
opened
|
Instructions
|
Usability
|
In the event that the user navigates to the Login Screen.
**Expected Response**: Instructions for how to login should be displayed on the Login Screen.
|
True
|
Instructions - In the event that the user navigates to the Login Screen.
**Expected Response**: Instructions for how to login should be displayed on the Login Screen.
|
usab
|
instructions in the event that the user navigates to the login screen expected response instructions for how to login should be displayed on the login screen
| 1
|
22,883
| 20,425,363,446
|
IssuesEvent
|
2022-02-24 02:50:44
|
microsoft/win32metadata
|
https://api.github.com/repos/microsoft/win32metadata
|
closed
|
`SetICMMode` and `ICM_ON` use different types
|
usability
|
These `ICM_*` constants are meant to be used with `SetICMMode` but they're the wrong type.
|
True
|
`SetICMMode` and `ICM_ON` use different types - These `ICM_*` constants are meant to be used with `SetICMMode` but they're the wrong type.
|
usab
|
seticmmode and icm on use different types these icm constants are meant to be used with seticmmode but they re the wrong type
| 1
|
6,765
| 9,888,280,189
|
IssuesEvent
|
2019-06-25 11:09:59
|
linnovate/root
|
https://api.github.com/repos/linnovate/root
|
closed
|
search office :can not click folder and signature
|
2.0.7 Fixed Process bug Search
|
go to offices
open new office
go to search and search for this office
Click on the office, and then click Folder or Signature
result : clicking on a signature or folder does not work
go to offices
open new office:
go to search and search for this office
Click on the office, and then click Folder or Signature
|
1.0
|
search office :can not click folder and signature - go to offices
open new office
go to search and search for this office
Click on the office, and then click Folder or Signature
result : clicking on a signature or folder does not work
go to offices
open new office:
go to search and search for this office
Click on the office, and then click Folder or Signature
|
non_usab
|
search office can not click folder and signature go to offices open new office go to search and search for this office click on the office and then click folder or signature result clicking on a signature or folder does not work go to offices open new office go to search and search for this office click on the office and then click folder or signature
| 0
|
25,767
| 25,852,606,508
|
IssuesEvent
|
2022-12-13 11:26:32
|
gardener/gardener
|
https://api.github.com/repos/gardener/gardener
|
closed
|
The maintenance controller in GCM to keep track of the last maintenance operation in the shoot status
|
kind/enhancement area/ops-productivity area/usability area/robustness
|
**How to categorize this issue?**
<!--
Please select area, kind, and priority for this issue. This helps the community categorizing it.
Replace below TODOs or exchange the existing identifiers with those that fit best in your opinion.
If multiple identifiers make sense you can also state the commands multiple times, e.g.
/area control-plane
/area auto-scaling
...
"/area" identifiers: audit-logging|auto-scaling|backup|certification|control-plane-migration|control-plane|cost|delivery|dev-productivity|disaster-recovery|documentation|high-availability|logging|metering|monitoring|networking|open-source|ops-productivity|os|performance|quality|robustness|scalability|security|storage|testing|usability|user-management
"/kind" identifiers: api-change|bug|cleanup|discussion|enhancement|epic|impediment|poc|post-mortem|question|regression|task|technical-debt|test
-->
/area ops-productivity robustness usability
/kind enhancement
**What would you like to be added**:
The maintenance controller in GCM to keep track of the last maintenance operation in the shoot status - it could be either a condition or a new field similar to `lastOperation`.
**Why is this needed**:
1. To have the timestamp of the last maintenance operation.
2. Any failed maintenance operations to be made visible to the shoot owner and gardener operators with reason/error message.
3. It would be nice to have summary of what was changed in the shoot spec during the last maintenance, e.g. OS/k8s version.
|
True
|
The maintenance controller in GCM to keep track of the last maintenance operation in the shoot status - **How to categorize this issue?**
<!--
Please select area, kind, and priority for this issue. This helps the community categorizing it.
Replace below TODOs or exchange the existing identifiers with those that fit best in your opinion.
If multiple identifiers make sense you can also state the commands multiple times, e.g.
/area control-plane
/area auto-scaling
...
"/area" identifiers: audit-logging|auto-scaling|backup|certification|control-plane-migration|control-plane|cost|delivery|dev-productivity|disaster-recovery|documentation|high-availability|logging|metering|monitoring|networking|open-source|ops-productivity|os|performance|quality|robustness|scalability|security|storage|testing|usability|user-management
"/kind" identifiers: api-change|bug|cleanup|discussion|enhancement|epic|impediment|poc|post-mortem|question|regression|task|technical-debt|test
-->
/area ops-productivity robustness usability
/kind enhancement
**What would you like to be added**:
The maintenance controller in GCM to keep track of the last maintenance operation in the shoot status - it could be either a condition or a new field similar to `lastOperation`.
**Why is this needed**:
1. To have the timestamp of the last maintenance operation.
2. Any failed maintenance operations to be made visible to the shoot owner and gardener operators with reason/error message.
3. It would be nice to have summary of what was changed in the shoot spec during the last maintenance, e.g. OS/k8s version.
|
usab
|
the maintenance controller in gcm to keep track of the last maintenance operation in the shoot status how to categorize this issue please select area kind and priority for this issue this helps the community categorizing it replace below todos or exchange the existing identifiers with those that fit best in your opinion if multiple identifiers make sense you can also state the commands multiple times e g area control plane area auto scaling area identifiers audit logging auto scaling backup certification control plane migration control plane cost delivery dev productivity disaster recovery documentation high availability logging metering monitoring networking open source ops productivity os performance quality robustness scalability security storage testing usability user management kind identifiers api change bug cleanup discussion enhancement epic impediment poc post mortem question regression task technical debt test area ops productivity robustness usability kind enhancement what would you like to be added the maintenance controller in gcm to keep track of the last maintenance operation in the shoot status it could be either a condition or a new field similar to lastoperation why is this needed to have the timestamp of the last maintenance operation any failed maintenance operations to be made visible to the shoot owner and gardener operators with reason error message it would be nice to have summary of what was changed in the shoot spec during the last maintenance e g os version
| 1
|
12,462
| 7,890,440,299
|
IssuesEvent
|
2018-06-28 08:50:16
|
brycx/orion
|
https://api.github.com/repos/brycx/orion
|
closed
|
Missing docs on "info" parameter for HKDF functions
|
usability
|
In regards to [/u/protestor's feedback](https://old.reddit.com/r/rust/comments/8tkeqh/feedback_on_usability_of_experimental_crypto_lib/), there is missing documentation on the info parameter for the HKDF functions. It should also be considered to add descriptions for all other parameters for all other functions.
|
True
|
Missing docs on "info" parameter for HKDF functions - In regards to [/u/protestor's feedback](https://old.reddit.com/r/rust/comments/8tkeqh/feedback_on_usability_of_experimental_crypto_lib/), there is missing documentation on the info parameter for the HKDF functions. It should also be considered to add descriptions for all other parameters for all other functions.
|
usab
|
missing docs on info parameter for hkdf functions in regards to there is missing documentation on the info parameter for the hkdf functions it should also be considered to add descriptions for all other parameters for all other functions
| 1
|
207,552
| 15,822,199,996
|
IssuesEvent
|
2021-04-05 21:49:46
|
YCPRadioTelescope/YCP-RT-ControlRoom
|
https://api.github.com/repos/YCPRadioTelescope/YCP-RT-ControlRoom
|
opened
|
Verify the production Weather Station still works
|
Testing
|
We haven't tested the Weather Station in a long time, so we need to make sure that it is still working correctly. In order to do this, the assignee of this issue will need to grab it from room 118, and then test it on the latest control room build (in Development).
Refer to the general documentation regarding details about the Weather Station. If the details there are found to be insufficient, then we will need to update them.
|
1.0
|
Verify the production Weather Station still works - We haven't tested the Weather Station in a long time, so we need to make sure that it is still working correctly. In order to do this, the assignee of this issue will need to grab it from room 118, and then test it on the latest control room build (in Development).
Refer to the general documentation regarding details about the Weather Station. If the details there are found to be insufficient, then we will need to update them.
|
non_usab
|
verify the production weather station still works we haven t tested the weather station in a long time so we need to make sure that it is still working correctly in order to do this the assignee of this issue will need to grab it from room and then test it on the latest control room build in development refer to the general documentation regarding details about the weather station if the details there are found to be insufficient then we will need to update them
| 0
|
17,930
| 12,438,924,803
|
IssuesEvent
|
2020-05-26 09:14:47
|
godotengine/godot
|
https://api.github.com/repos/godotengine/godot
|
closed
|
Copy, Cut, Paste scene nodes
|
feature proposal topic:editor usability
|
Copy / Cut, Paste nodes would be a tremendous time saver.
Right now I have to add my components ( sub-scenes ) and re-enter script variables in Property Editor over and over. If I could copy / paste selected node trees between scenes, I would be very happy.
I'm sure many other users miss this ability.
|
True
|
Copy, Cut, Paste scene nodes - Copy / Cut, Paste nodes would be a tremendous time saver.
Right now I have to add my components ( sub-scenes ) and re-enter script variables in Property Editor over and over. If I could copy / paste selected node trees between scenes, I would be very happy.
I'm sure many other users miss this ability.
|
usab
|
copy cut paste scene nodes copy cut paste nodes would be a tremendous time saver right now i have to add my components sub scenes and re enter script variables in property editor over and over if i could copy paste selected node trees between scenes i would be very happy i m sure many other users miss this ability
| 1
|
136,672
| 5,287,515,222
|
IssuesEvent
|
2017-02-08 12:36:33
|
FAC9/centrepoint
|
https://api.github.com/repos/FAC9/centrepoint
|
opened
|
Create form for logged-in user to fill in
|
priority-2 technical
|
Addresses user stories #7 and #8
- User should be able to select any or all of the following information types that they would like to receive:
- Address history with Centrepoint
- Rental arrears report
- Rental reference
- User should be clear that they will get an email with the information they want within 24 hours (can this be promised on weekends? Or is this weekdays only?)
- User should be clear that they can elect to have a letter posted to them and requested to fill in a form with an address. It should be made clear that this will take more than 24 hours to receive
**OR**
- User should be presented with the option to get an email or a letter posted to them (and asked to fill in email or address details depending on what they select)
|
1.0
|
Create form for logged-in user to fill in - Addresses user stories #7 and #8
- User should be able to select any or all of the following information types that they would like to receive:
- Address history with Centrepoint
- Rental arrears report
- Rental reference
- User should be clear that they will get an email with the information they want within 24 hours (can this be promised on weekends? Or is this weekdays only?)
- User should be clear that they can elect to have a letter posted to them and requested to fill in a form with an address. It should be made clear that this will take more than 24 hours to receive
**OR**
- User should be presented with the option to get an email or a letter posted to them (and asked to fill in email or address details depending on what they select)
|
non_usab
|
create form for logged in user to fill in addresses user stories and user should be able to select any or all of the following information types that they would like to receive address history with centrepoint rental arrears report rental reference user should be clear that they will get an email with the information they want within hours can this be promised on weekends or is this weekdays only user should be clear that they can elect to have a letter posted to them and requested to fill in a form with an address it should be made clear that this will take more than hours to receive or user should be presented with the option to get an email or a letter posted to them and asked to fill in email or address details depending on what they select
| 0
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.