Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1
value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3
values | title stringlengths 1 1k | labels stringlengths 4 1.38k | body stringlengths 1 262k | index stringclasses 16
values | text_combine stringlengths 96 262k | label stringclasses 2
values | text stringlengths 96 252k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
452,084 | 32,049,445,667 | IssuesEvent | 2023-09-23 11:29:58 | hxijxe/ict-inf2001-p3-6 | https://api.github.com/repos/hxijxe/ict-inf2001-p3-6 | closed | #Task 1.3.2: Detailed Use Case Description (UC-5 to UC-7) | documentation | Task title ID: https://github.com/hxijxe/ict-inf2001-p3-6/issues/12
What is the task about? Please describe in detail.
The task involves creating detailed use case descriptions for Use Cases 5, 6 and 7, which are "Manage Shift", "Manage Shift Location" and "Manage Shift Preference" respectively.
What are the goals of the task? Please describe in detail.
The primary goals of this task are to create clear, well-structured use case descriptions for Use Cases 5, 6 and 7, ensuring alignment with project objectives, comprehensiveness, accuracy, and documentation quality. These descriptions will serve as valuable references for project stakeholders and developers, enhancing the management of work shifts and their corresponding locations within the system.
Success or completion criteria. Please describe in detail.
Completion of use case descriptions
Allocated time
7 Days
Start date and end date of the issue/task
13/09/23 - 19/09/23
Who is the owner? The owner is the person in-charge of the task and the task should be created and maintained by the owner.
@avintech
The status of the task. This is usually "To-Do" initially.
Completed
What is the Priority of the task?
Medium | 1.0 | #Task 1.3.2: Detailed Use Case Description (UC-5 to UC-7) - Task title ID: https://github.com/hxijxe/ict-inf2001-p3-6/issues/12
What is the task about? Please describe in detail.
The task involves creating detailed use case descriptions for Use Cases 5, 6 and 7, which are "Manage Shift", "Manage Shift Location" and "Manage Shift Preference" respectively.
What are the goals of the task? Please describe in detail.
The primary goals of this task are to create clear, well-structured use case descriptions for Use Cases 5, 6 and 7, ensuring alignment with project objectives, comprehensiveness, accuracy, and documentation quality. These descriptions will serve as valuable references for project stakeholders and developers, enhancing the management of work shifts and their corresponding locations within the system.
Success or completion criteria. Please describe in detail.
Completion of use case descriptions
Allocated time
7 Days
Start date and end date of the issue/task
13/09/23 - 19/09/23
Who is the owner? The owner is the person in-charge of the task and the task should be created and maintained by the owner.
@avintech
The status of the task. This is usually "To-Do" initially.
Completed
What is the Priority of the task?
Medium | non_priority | task detailed use case description uc to uc task title id what is the task about please describe in detail the task involves creating detailed use case descriptions for use cases and which are manage shift manage shift location and manage shift preference respectively what are the goals of the task please describe in detail the primary goals of this task are to create clear well structured use case descriptions for use cases and ensuring alignment with project objectives comprehensiveness accuracy and documentation quality these descriptions will serve as valuable references for project stakeholders and developers enhancing the management of work shifts and their corresponding locations within the system success or completion criteria please describe in detail completion of use case descriptions allocated time days start date and end date of the issue task who is the owner the owner is the person in charge of the task and the task should be created and maintained by the owner avintech the status of the task this is usually to do initially completed what is the priority of the task medium | 0 |
486,810 | 14,014,986,467 | IssuesEvent | 2020-10-29 12:43:51 | geosolutions-it/austrocontrol-C125 | https://api.github.com/repos/geosolutions-it/austrocontrol-C125 | closed | Responsive Design - Info Box - Update of the WYSIWYG | Accepted Priority: Medium Project: C125 | Update of the WYSIWYG used by the current Details tool to allow aligning and resizing images.
Use the new WYSIWYG editor implemented for Stories (draftJS editor). This means not only adapting the new Text editor to the existing Details tool, but also readapting it in order to include and manage additional utilities to allow operations on images, that are available only using the new WYSIWYG (the [Image](https://www.draft-js-plugins.com/plugin/image) and other plugins that allows to align images, **_the example Alignment + Resize + Focus + Drag’n’drop_** seems near to the desired behaviour). The most part of the estimate reported in the tasklist is needed to accomplish this specific task.
 | 1.0 | Responsive Design - Info Box - Update of the WYSIWYG - Update of the WYSIWYG used by the current Details tool to allow aligning and resizing images.
Use the new WYSIWYG editor implemented for Stories (draftJS editor). This means not only adapting the new Text editor to the existing Details tool, but also readapting it in order to include and manage additional utilities to allow operations on images, that are available only using the new WYSIWYG (the [Image](https://www.draft-js-plugins.com/plugin/image) and other plugins that allows to align images, **_the example Alignment + Resize + Focus + Drag’n’drop_** seems near to the desired behaviour). The most part of the estimate reported in the tasklist is needed to accomplish this specific task.
 | priority | responsive design info box update of the wysiwyg update of the wysiwyg used by the current details tool to allow aligning and resizing images use the new wysiwyg editor implemented for stories draftjs editor this means not only adapting the new text editor to the existing details tool but also readapting it in order to include and manage additional utilities to allow operations on images that are available only using the new wysiwyg the and other plugins that allows to align images the example alignment resize focus drag’n’drop seems near to the desired behaviour the most part of the estimate reported in the tasklist is needed to accomplish this specific task | 1 |
477,822 | 13,768,920,478 | IssuesEvent | 2020-10-07 17:48:49 | zephyrproject-rtos/zephyr | https://api.github.com/repos/zephyrproject-rtos/zephyr | opened | [Coverity CID :214875] Dereference after null check in subsys/emul/spi/emul_bmi160.c | Coverity bug priority: low |
Static code scan issues found in file:
https://github.com/zephyrproject-rtos/zephyr/tree/master/subsys/emul/spi/emul_bmi160.c
Category: Null pointer dereferences
Function: `bmi160_emul_io`
Component: Other
CID: [214875](https://scan9.coverity.com/reports.htm#v29726/p12996/mergedDefectId=214875)
Please fix or provide comments in coverity using the link:
https://scan9.coverity.com/reports.htm#v32951/p12996.
Note: This issue was created automatically. Priority was set based on classification
of the file affected and the impact field in coverity. Assignees were set using the CODEOWNERS file.
| 1.0 | [Coverity CID :214875] Dereference after null check in subsys/emul/spi/emul_bmi160.c -
Static code scan issues found in file:
https://github.com/zephyrproject-rtos/zephyr/tree/master/subsys/emul/spi/emul_bmi160.c
Category: Null pointer dereferences
Function: `bmi160_emul_io`
Component: Other
CID: [214875](https://scan9.coverity.com/reports.htm#v29726/p12996/mergedDefectId=214875)
Please fix or provide comments in coverity using the link:
https://scan9.coverity.com/reports.htm#v32951/p12996.
Note: This issue was created automatically. Priority was set based on classification
of the file affected and the impact field in coverity. Assignees were set using the CODEOWNERS file.
| priority | dereference after null check in subsys emul spi emul c static code scan issues found in file category null pointer dereferences function emul io component other cid please fix or provide comments in coverity using the link note this issue was created automatically priority was set based on classification of the file affected and the impact field in coverity assignees were set using the codeowners file | 1 |
28,361 | 5,242,753,496 | IssuesEvent | 2017-01-31 18:53:55 | bridgedotnet/Bridge | https://api.github.com/repos/bridgedotnet/Bridge | closed | Can't resolve generic alias in method<TA> from within Action<TB<TC>> | defect in progress | ### Steps To Reproduce
http://deck.net/7c9c1ee892b60cdcd72febeeb3b3c078
```c#
public struct V2<TA, TB>
{
public TA a;
public TB b;
}
public interface IThing<TC,TD>
{
void MyMethod();
}
public class BugTest<TX>
{
IThing<V2<TX,double>,V2<double,double>> _MyThing;
public void DoStuff()
{
Action<V2<TX, double>> func = v => _MyThing.MyMethod();
}
}
```
### Expected Result
```js
??
```
### Actual Result
```js
var func = Bridge.fn.bind(this, function (v) {
this._MyThing["ClassLibrary1$IThing$2$ClassLibrary1$V2$2$" + Bridge.getTypeAlias(TX) + "$System$Double"$ClassLibrary1$V2$2$System$Double$System$Double$myMethod"]();
});
```
Related:
* http://forums.bridge.net/forum/bridge-net-pro/bugs/3379-javascript-can-t-resolve-call-to-method-ta-from-within-action-tb-tc
| 1.0 | Can't resolve generic alias in method<TA> from within Action<TB<TC>> - ### Steps To Reproduce
http://deck.net/7c9c1ee892b60cdcd72febeeb3b3c078
```c#
public struct V2<TA, TB>
{
public TA a;
public TB b;
}
public interface IThing<TC,TD>
{
void MyMethod();
}
public class BugTest<TX>
{
IThing<V2<TX,double>,V2<double,double>> _MyThing;
public void DoStuff()
{
Action<V2<TX, double>> func = v => _MyThing.MyMethod();
}
}
```
### Expected Result
```js
??
```
### Actual Result
```js
var func = Bridge.fn.bind(this, function (v) {
this._MyThing["ClassLibrary1$IThing$2$ClassLibrary1$V2$2$" + Bridge.getTypeAlias(TX) + "$System$Double"$ClassLibrary1$V2$2$System$Double$System$Double$myMethod"]();
});
```
Related:
* http://forums.bridge.net/forum/bridge-net-pro/bugs/3379-javascript-can-t-resolve-call-to-method-ta-from-within-action-tb-tc
| non_priority | can t resolve generic alias in method from within action steps to reproduce c public struct public ta a public tb b public interface ithing void mymethod public class bugtest ithing mything public void dostuff action func v mything mymethod expected result js actual result js var func bridge fn bind this function v this mything related | 0 |
41,625 | 21,796,761,320 | IssuesEvent | 2022-05-15 18:54:05 | antlr/antlr4 | https://api.github.com/repos/antlr/antlr4 | opened | ANTLR tool takes 6s to process 1772 line parser grammar | atn-analysis grammars comp:performance | [issue was identified in plugin](https://github.com/antlr/intellij-plugin-v4/issues/553) by @KitsuneAlex
This [FerrousParser.g4](https://git.karmakrafts.dev/kk/ferrous-project/vanadium/-/blob/master/src/main/antlr/FerrousParser.g4) takes 6s to process with antlr tool. It seems to be stuck in SLL(1) static analysis. Could be murmur hash.
@sharwell This likely affects your optimized fork as well.
Simple test rig:
```java
import org.antlr.runtime.ANTLRFileStream;
import org.antlr.runtime.ANTLRStringStream;
import org.antlr.v4.Tool;
import org.antlr.v4.tool.Grammar;
import org.antlr.v4.tool.ast.GrammarRootAST;
import java.io.IOException;
public class TestANTLRParse {
public static void main(String[] args) throws IOException {
long start = System.nanoTime();
runANTLR(args[0]);
long time_ns = System.nanoTime() - start;
double parseTimeMS = time_ns/(1000.0*1000.0);
System.err.println("Exec time to process "+args[0]+": "+parseTimeMS+"ms");
}
private static void runANTLR(String grammarFileName) throws IOException {
Tool antlr = new Tool();
ANTLRStringStream in = new ANTLRFileStream(grammarFileName);
GrammarRootAST grammarRootAST = antlr.parse(grammarFileName, in);
// Create a grammar from the AST so we can figure out what type it is
Grammar g = antlr.createGrammar(grammarRootAST);
antlr.process(g, false);
}
}
```
I see this on M1 mac mini:
```
Exec time to process /Users/parrt/tmp/FerrousParser.g4: 5984.826209ms
``` | True | ANTLR tool takes 6s to process 1772 line parser grammar - [issue was identified in plugin](https://github.com/antlr/intellij-plugin-v4/issues/553) by @KitsuneAlex
This [FerrousParser.g4](https://git.karmakrafts.dev/kk/ferrous-project/vanadium/-/blob/master/src/main/antlr/FerrousParser.g4) takes 6s to process with antlr tool. It seems to be stuck in SLL(1) static analysis. Could be murmur hash.
@sharwell This likely affects your optimized fork as well.
Simple test rig:
```java
import org.antlr.runtime.ANTLRFileStream;
import org.antlr.runtime.ANTLRStringStream;
import org.antlr.v4.Tool;
import org.antlr.v4.tool.Grammar;
import org.antlr.v4.tool.ast.GrammarRootAST;
import java.io.IOException;
public class TestANTLRParse {
public static void main(String[] args) throws IOException {
long start = System.nanoTime();
runANTLR(args[0]);
long time_ns = System.nanoTime() - start;
double parseTimeMS = time_ns/(1000.0*1000.0);
System.err.println("Exec time to process "+args[0]+": "+parseTimeMS+"ms");
}
private static void runANTLR(String grammarFileName) throws IOException {
Tool antlr = new Tool();
ANTLRStringStream in = new ANTLRFileStream(grammarFileName);
GrammarRootAST grammarRootAST = antlr.parse(grammarFileName, in);
// Create a grammar from the AST so we can figure out what type it is
Grammar g = antlr.createGrammar(grammarRootAST);
antlr.process(g, false);
}
}
```
I see this on M1 mac mini:
```
Exec time to process /Users/parrt/tmp/FerrousParser.g4: 5984.826209ms
``` | non_priority | antlr tool takes to process line parser grammar by kitsunealex this takes to process with antlr tool it seems to be stuck in sll static analysis could be murmur hash sharwell this likely affects your optimized fork as well simple test rig java import org antlr runtime antlrfilestream import org antlr runtime antlrstringstream import org antlr tool import org antlr tool grammar import org antlr tool ast grammarrootast import java io ioexception public class testantlrparse public static void main string args throws ioexception long start system nanotime runantlr args long time ns system nanotime start double parsetimems time ns system err println exec time to process args parsetimems ms private static void runantlr string grammarfilename throws ioexception tool antlr new tool antlrstringstream in new antlrfilestream grammarfilename grammarrootast grammarrootast antlr parse grammarfilename in create a grammar from the ast so we can figure out what type it is grammar g antlr creategrammar grammarrootast antlr process g false i see this on mac mini exec time to process users parrt tmp ferrousparser | 0 |
131,160 | 18,214,761,869 | IssuesEvent | 2021-09-30 01:53:04 | tt9133github/Python | https://api.github.com/repos/tt9133github/Python | opened | CVE-2021-29063 (High) detected in mpmath-1.1.0.tar.gz | security vulnerability | ## CVE-2021-29063 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mpmath-1.1.0.tar.gz</b></p></summary>
<p>Python library for arbitrary-precision floating-point arithmetic</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/ca/63/3384ebb3b51af9610086b23ea976e6d27d6d97bf140a76a365bd77a3eb32/mpmath-1.1.0.tar.gz">https://files.pythonhosted.org/packages/ca/63/3384ebb3b51af9610086b23ea976e6d27d6d97bf140a76a365bd77a3eb32/mpmath-1.1.0.tar.gz</a></p>
<p>Path to dependency file: Python/optimization/requirements.txt</p>
<p>Path to vulnerable library: Python/optimization/requirements.txt,Python/requirements.txt</p>
<p>
Dependency Hierarchy:
- sympy-1.5.1-py2.py3-none-any.whl (Root Library)
- :x: **mpmath-1.1.0.tar.gz** (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>
A Regular Expression Denial of Service (ReDOS) vulnerability was discovered in Mpmath v1.0.0 when the mpmathify function is called.
<p>Publish Date: 2021-06-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29063>CVE-2021-29063</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>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-29063 (High) detected in mpmath-1.1.0.tar.gz - ## CVE-2021-29063 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mpmath-1.1.0.tar.gz</b></p></summary>
<p>Python library for arbitrary-precision floating-point arithmetic</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/ca/63/3384ebb3b51af9610086b23ea976e6d27d6d97bf140a76a365bd77a3eb32/mpmath-1.1.0.tar.gz">https://files.pythonhosted.org/packages/ca/63/3384ebb3b51af9610086b23ea976e6d27d6d97bf140a76a365bd77a3eb32/mpmath-1.1.0.tar.gz</a></p>
<p>Path to dependency file: Python/optimization/requirements.txt</p>
<p>Path to vulnerable library: Python/optimization/requirements.txt,Python/requirements.txt</p>
<p>
Dependency Hierarchy:
- sympy-1.5.1-py2.py3-none-any.whl (Root Library)
- :x: **mpmath-1.1.0.tar.gz** (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>
A Regular Expression Denial of Service (ReDOS) vulnerability was discovered in Mpmath v1.0.0 when the mpmathify function is called.
<p>Publish Date: 2021-06-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29063>CVE-2021-29063</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>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in mpmath tar gz cve high severity vulnerability vulnerable library mpmath tar gz python library for arbitrary precision floating point arithmetic library home page a href path to dependency file python optimization requirements txt path to vulnerable library python optimization requirements txt python requirements txt dependency hierarchy sympy none any whl root library x mpmath tar gz vulnerable library vulnerability details a regular expression denial of service redos vulnerability was discovered in mpmath when the mpmathify function is called 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 step up your open source security game with whitesource | 0 |
7,573 | 2,911,335,793 | IssuesEvent | 2015-06-22 08:52:45 | red/red | https://api.github.com/repos/red/red | closed | length? on tuple! | Red status.built status.tested type.review | red>> length? 1.2.3
*** Script error: length? does not allow tuple for its series argument
*** Where: length?
| 1.0 | length? on tuple! - red>> length? 1.2.3
*** Script error: length? does not allow tuple for its series argument
*** Where: length?
| non_priority | length on tuple red length script error length does not allow tuple for its series argument where length | 0 |
333,116 | 24,364,643,951 | IssuesEvent | 2022-10-03 14:19:24 | r-lib/pak | https://api.github.com/repos/r-lib/pak | closed | `?ignore`d packages is not ignored | documentation | Related to #421, I'm trying to ignore the package `lixoftConnectors` when installing dependencies.
When I used `lixoftConnectors?ignore` in the `extra-packages` list, I got the following error indicating that it was not ignored:
https://github.com/nlmixr2/babelmixr2/actions/runs/3169455077/jobs/5161378366#step:5:109
The instructions I used were:
https://github.com/nlmixr2/babelmixr2/blob/5bd330353cf4ad0b62d0223b656246672119e3b1/.github/workflows/R-CMD-check.yaml#L45-L55
I was trying to follow the instructions here: https://github.com/r-lib/actions/tree/v2-branch/setup-r-dependencies#ignoring-optional-dependencies | 1.0 | `?ignore`d packages is not ignored - Related to #421, I'm trying to ignore the package `lixoftConnectors` when installing dependencies.
When I used `lixoftConnectors?ignore` in the `extra-packages` list, I got the following error indicating that it was not ignored:
https://github.com/nlmixr2/babelmixr2/actions/runs/3169455077/jobs/5161378366#step:5:109
The instructions I used were:
https://github.com/nlmixr2/babelmixr2/blob/5bd330353cf4ad0b62d0223b656246672119e3b1/.github/workflows/R-CMD-check.yaml#L45-L55
I was trying to follow the instructions here: https://github.com/r-lib/actions/tree/v2-branch/setup-r-dependencies#ignoring-optional-dependencies | non_priority | ignore d packages is not ignored related to i m trying to ignore the package lixoftconnectors when installing dependencies when i used lixoftconnectors ignore in the extra packages list i got the following error indicating that it was not ignored the instructions i used were i was trying to follow the instructions here | 0 |
61,174 | 14,942,775,629 | IssuesEvent | 2021-01-25 21:50:58 | quicklisp/quicklisp-projects | https://api.github.com/repos/quicklisp/quicklisp-projects | closed | Please add inheriting-readers | canbuild | inheriting-readers provides a simple yet powerful value inheritance scheme.
Project's home: https://www.hexstreamsoft.com/libraries/inheriting-readers/
GitHub: https://github.com/Hexstream/inheriting-readers
Quicklisp should pull from the tarball: https://tarballs.hexstreamsoft.com/libraries/latest/inheriting-readers_latest.tar.gz | 1.0 | Please add inheriting-readers - inheriting-readers provides a simple yet powerful value inheritance scheme.
Project's home: https://www.hexstreamsoft.com/libraries/inheriting-readers/
GitHub: https://github.com/Hexstream/inheriting-readers
Quicklisp should pull from the tarball: https://tarballs.hexstreamsoft.com/libraries/latest/inheriting-readers_latest.tar.gz | non_priority | please add inheriting readers inheriting readers provides a simple yet powerful value inheritance scheme project s home github quicklisp should pull from the tarball | 0 |
115,740 | 14,882,456,588 | IssuesEvent | 2021-01-20 11:55:55 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | [APM] Discovery - need to re-evaluate implementation of filters and kuery bar across APM UI | Team:apm [zube]: Backlog discuss needs design | **Describe the feature:**
APM already offers various filters on different pages, like environments, hosts, K8s pods, containers, etc.
In 7.8 we started adding cloud metadata to be collected by APM agents.
On top of that some of the filters are used to track integrations across other observability UI into APM.
This issue would be used to perform discovery and design which filters need to be available for each screen, how they would persist when linking from one screen to another, and what would be used when linking from other UI pages into APM.
I suggest we perform this discovery before proceeding with https://github.com/elastic/kibana/issues/49153 | 1.0 | [APM] Discovery - need to re-evaluate implementation of filters and kuery bar across APM UI - **Describe the feature:**
APM already offers various filters on different pages, like environments, hosts, K8s pods, containers, etc.
In 7.8 we started adding cloud metadata to be collected by APM agents.
On top of that some of the filters are used to track integrations across other observability UI into APM.
This issue would be used to perform discovery and design which filters need to be available for each screen, how they would persist when linking from one screen to another, and what would be used when linking from other UI pages into APM.
I suggest we perform this discovery before proceeding with https://github.com/elastic/kibana/issues/49153 | non_priority | discovery need to re evaluate implementation of filters and kuery bar across apm ui describe the feature apm already offers various filters on different pages like environments hosts pods containers etc in we started adding cloud metadata to be collected by apm agents on top of that some of the filters are used to track integrations across other observability ui into apm this issue would be used to perform discovery and design which filters need to be available for each screen how they would persist when linking from one screen to another and what would be used when linking from other ui pages into apm i suggest we perform this discovery before proceeding with | 0 |
231,925 | 17,761,269,412 | IssuesEvent | 2021-08-29 18:43:27 | fuchicorp/main | https://api.github.com/repos/fuchicorp/main | closed | 6. Deploy ELK-Stack to bastion-host | Kubernetes Priority High Bastion Bash Scripting Require Documentation elastic-search kibana basic | We are going to deploy ELK-Stack to our bastion-host so we can understand how it works. Here's the Github repo with documentation to follow!
https://github.com/fuchicorp/elk-stack
Thanks!
Lale | 1.0 | 6. Deploy ELK-Stack to bastion-host - We are going to deploy ELK-Stack to our bastion-host so we can understand how it works. Here's the Github repo with documentation to follow!
https://github.com/fuchicorp/elk-stack
Thanks!
Lale | non_priority | deploy elk stack to bastion host we are going to deploy elk stack to our bastion host so we can understand how it works here s the github repo with documentation to follow thanks lale | 0 |
274,571 | 8,563,113,978 | IssuesEvent | 2018-11-09 13:01:19 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | durington.info - see bug description | browser-firefox priority-normal type-search-hijacking | <!-- @browser: Firefox 64.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:64.0) Gecko/20100101 Firefox/64.0 -->
<!-- @reported_with: desktop-reporter -->
**URL**: https://durington.info/XZEYY?tag_id=715349&sub_id1=59&sub_id2=BF78A1D5-713D-4674-8E18-492B43CFC078&cookie_id=9cedd5fa-dc74-4e95-8463-547442c3e7ef&lp=blank&tb=redirect&allb=redirect&ob=redirect
**Browser / Version**: Firefox 64.0
**Operating System**: Windows 7
**Tested Another Browser**: Yes
**Problem type**: Something else
**Description**: It opens always in background. use cmd prompt. automatic opening of site.. hangs pc.. irritable
**Steps to Reproduce**:
It seems like a work of virus.
[](https://webcompat.com/uploads/2018/11/b6523205-5ccd-4ff2-8f5f-f4472aba587f.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20181105164654</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: false</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: beta</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | durington.info - see bug description - <!-- @browser: Firefox 64.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:64.0) Gecko/20100101 Firefox/64.0 -->
<!-- @reported_with: desktop-reporter -->
**URL**: https://durington.info/XZEYY?tag_id=715349&sub_id1=59&sub_id2=BF78A1D5-713D-4674-8E18-492B43CFC078&cookie_id=9cedd5fa-dc74-4e95-8463-547442c3e7ef&lp=blank&tb=redirect&allb=redirect&ob=redirect
**Browser / Version**: Firefox 64.0
**Operating System**: Windows 7
**Tested Another Browser**: Yes
**Problem type**: Something else
**Description**: It opens always in background. use cmd prompt. automatic opening of site.. hangs pc.. irritable
**Steps to Reproduce**:
It seems like a work of virus.
[](https://webcompat.com/uploads/2018/11/b6523205-5ccd-4ff2-8f5f-f4472aba587f.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20181105164654</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: false</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: beta</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | durington info see bug description url browser version firefox operating system windows tested another browser yes problem type something else description it opens always in background use cmd prompt automatic opening of site hangs pc irritable steps to reproduce it seems like a work of virus browser configuration mixed active content blocked false image mem shared true buildid tracking content blocked false gfx webrender blob images true hastouchscreen false mixed passive content blocked false gfx webrender enabled false gfx webrender all false channel beta from with ❤️ | 1 |
12,942 | 3,103,153,537 | IssuesEvent | 2015-08-31 07:49:14 | osakagamba/7GIQSKRNE5P3AVTZCEFXE3ON | https://api.github.com/repos/osakagamba/7GIQSKRNE5P3AVTZCEFXE3ON | closed | bIHT0vqN8SdqTWLmpVrcP2ptQn9f/r5zfwHcPK5Bi5Jbc6tjAKhtPfVNhyuvf0VVpn3CHe+TRHT9hicK8WovClCK2CorvLKpiXQShxYDhPk+tgNtYW3RtigSXrjmqVs/12SMzG2Dt/ioHl/ZqsiAWkY39nLpWvhd7SzTbK+oMBY= | design | fSS166lCfoE0L/zWHg5ySeyyN7zoU8dIgazEwBHybrI77oJrNZpSxN1DbyM+ZGGKUURPhxnRWARiyiOJorKJAWdQFC3ksbfOgHl6wteiUO0SCGQaNeUA9B5p9gbAYJAHcB35cTVPy6NONuxGywlJVe7KJ1dUhHzMk4cHqkBS6MDb51l8HTHEvpWXtOOwPKPbr0iJSXQO0Ht+TC+b0JUvJdSxry4SiKMjyJiyBzj+z77trt2teMTI6yzQMkj22IR4r0iJSXQO0Ht+TC+b0JUvJVxgQZqyN9vzuf9yHSffgAe5ccrSKRaievUIyJKo/LKDr0iJSXQO0Ht+TC+b0JUvJS0OM6S4KzzMmIDtiS818glQYkXkphHyede4xlCkEi68r0iJSXQO0Ht+TC+b0JUvJQUH+R6RRAoRyV8Q+ujq5yZ9KSYE1bsqYQ74blVAE83TEMs3tnuPBKhgh3rk2PAMvByR3Z7EMc8bFHfAsnCAkollEfGKEhC1I9uBrT3tCBLIOCXLFUMsf7XEJRzwNAvAAK9IiUl0DtB7fkwvm9CVLyUs8vEEW4aPhy7tcr1m49X00AiU5vpfh8R+dlJ38AAFnq9IiUl0DtB7fkwvm9CVLyX8/+LkJPLfRpLFTSiM6xcD5hm37oLaieAPjIoliAdvBwFCGqB6jErGtcAMRF4wc+ppl3fp7P9A+1XwzWWQXw0qRn68g2OPLCGzHsPkR5gJcdDe5kSLYboddq0femHiH/C6354jnshBi/tKgRCWQqIzWDS2NmiRk3v4ef3t8UTCscRVZEgvOpdrp8VOelITvXpBOfu5fe5ZpnoyyUP5INHLVHl9Lp3SsYygEjnVeCAevJB7Lj86o5xOCDgjRxbG248BTQo9EErXzuPhmxGadSEMV4K9fx/0EUMS5g9pK+nLYsiz+kEODRg7rZID7xLWbRAaKXlD/hANHjNWsi1YAaWOFQA5AsNCXL57/xyQXlBkoomYBwrUfhj+cIlqw87gpwJqSsx0EEgRWIsQIBi5g7bg7CYURv3lpozfOlx80+3IgNNBPPK2v5I1d/S74y6soxCvSIlJdA7Qe35ML5vQlS8lR+MWcDd0tIYGSuv990uMEPRpm8YQ4VjImxa7fQwacpCtEUNaTQhjDLC21AGq7wV89m1IOnl96Y6UGShYZSNC/a9IiUl0DtB7fkwvm9CVLyWbcM3mkuJKNr0tm7ZBvxXEC+J3VH+gvXepGdOSe1U3bK9IiUl0DtB7fkwvm9CVLyWnxibe2G94S3QyKCzdr0zDbE8F5TifMdDuQhnyCTTyVqucr9K0lKLgmU2l2vqVi+NOz6wkexrxwAZIZI6SZK+h3uwpoi0BAGQs9VtBnb4YiZC2KUJ8s/VKfImX3A01r8SsFb6YT3YdOTViydxM3xp8qr84fc3WIv6AjaLIkO61iP+AxE4jhaOLjByVEeKXU4CQtilCfLP1SnyJl9wNNa/EUN2wbMRg0nGWWtucW9J1BpZ/ownicmRBvLuOBIg/uXs+sKW8Yk+24+PsaOjezWh5lub/9BHrcNLLhTCS1++ZBcrOCIEX7HTQbHbsbvCnDwrzAN/fAh90RxDvIwpWtk1dF7YcIojwFv4g4AnHSqFciT6/AGSuC4mMVBvltr0OtcnE/HCBaBD5GFsoj1ruuN82 | 1.0 | bIHT0vqN8SdqTWLmpVrcP2ptQn9f/r5zfwHcPK5Bi5Jbc6tjAKhtPfVNhyuvf0VVpn3CHe+TRHT9hicK8WovClCK2CorvLKpiXQShxYDhPk+tgNtYW3RtigSXrjmqVs/12SMzG2Dt/ioHl/ZqsiAWkY39nLpWvhd7SzTbK+oMBY= - fSS166lCfoE0L/zWHg5ySeyyN7zoU8dIgazEwBHybrI77oJrNZpSxN1DbyM+ZGGKUURPhxnRWARiyiOJorKJAWdQFC3ksbfOgHl6wteiUO0SCGQaNeUA9B5p9gbAYJAHcB35cTVPy6NONuxGywlJVe7KJ1dUhHzMk4cHqkBS6MDb51l8HTHEvpWXtOOwPKPbr0iJSXQO0Ht+TC+b0JUvJdSxry4SiKMjyJiyBzj+z77trt2teMTI6yzQMkj22IR4r0iJSXQO0Ht+TC+b0JUvJVxgQZqyN9vzuf9yHSffgAe5ccrSKRaievUIyJKo/LKDr0iJSXQO0Ht+TC+b0JUvJS0OM6S4KzzMmIDtiS818glQYkXkphHyede4xlCkEi68r0iJSXQO0Ht+TC+b0JUvJQUH+R6RRAoRyV8Q+ujq5yZ9KSYE1bsqYQ74blVAE83TEMs3tnuPBKhgh3rk2PAMvByR3Z7EMc8bFHfAsnCAkollEfGKEhC1I9uBrT3tCBLIOCXLFUMsf7XEJRzwNAvAAK9IiUl0DtB7fkwvm9CVLyUs8vEEW4aPhy7tcr1m49X00AiU5vpfh8R+dlJ38AAFnq9IiUl0DtB7fkwvm9CVLyX8/+LkJPLfRpLFTSiM6xcD5hm37oLaieAPjIoliAdvBwFCGqB6jErGtcAMRF4wc+ppl3fp7P9A+1XwzWWQXw0qRn68g2OPLCGzHsPkR5gJcdDe5kSLYboddq0femHiH/C6354jnshBi/tKgRCWQqIzWDS2NmiRk3v4ef3t8UTCscRVZEgvOpdrp8VOelITvXpBOfu5fe5ZpnoyyUP5INHLVHl9Lp3SsYygEjnVeCAevJB7Lj86o5xOCDgjRxbG248BTQo9EErXzuPhmxGadSEMV4K9fx/0EUMS5g9pK+nLYsiz+kEODRg7rZID7xLWbRAaKXlD/hANHjNWsi1YAaWOFQA5AsNCXL57/xyQXlBkoomYBwrUfhj+cIlqw87gpwJqSsx0EEgRWIsQIBi5g7bg7CYURv3lpozfOlx80+3IgNNBPPK2v5I1d/S74y6soxCvSIlJdA7Qe35ML5vQlS8lR+MWcDd0tIYGSuv990uMEPRpm8YQ4VjImxa7fQwacpCtEUNaTQhjDLC21AGq7wV89m1IOnl96Y6UGShYZSNC/a9IiUl0DtB7fkwvm9CVLyWbcM3mkuJKNr0tm7ZBvxXEC+J3VH+gvXepGdOSe1U3bK9IiUl0DtB7fkwvm9CVLyWnxibe2G94S3QyKCzdr0zDbE8F5TifMdDuQhnyCTTyVqucr9K0lKLgmU2l2vqVi+NOz6wkexrxwAZIZI6SZK+h3uwpoi0BAGQs9VtBnb4YiZC2KUJ8s/VKfImX3A01r8SsFb6YT3YdOTViydxM3xp8qr84fc3WIv6AjaLIkO61iP+AxE4jhaOLjByVEeKXU4CQtilCfLP1SnyJl9wNNa/EUN2wbMRg0nGWWtucW9J1BpZ/ownicmRBvLuOBIg/uXs+sKW8Yk+24+PsaOjezWh5lub/9BHrcNLLhTCS1++ZBcrOCIEX7HTQbHbsbvCnDwrzAN/fAh90RxDvIwpWtk1dF7YcIojwFv4g4AnHSqFciT6/AGSuC4mMVBvltr0OtcnE/HCBaBD5GFsoj1ruuN82 | non_priority | iohl omby tc tc tc tc nlysiz xyqxlbkoomybwrufhj ownicmrbvluobig uxs | 0 |
66,017 | 12,702,963,867 | IssuesEvent | 2020-06-22 21:14:09 | kubernetes/kubernetes | https://api.github.com/repos/kubernetes/kubernetes | closed | Document the use of import-boss | area/code-organization kind/bug kind/documentation priority/important-longterm sig/testing | [import-boss](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/code-generator/cmd/import-boss/main.go) is used in our CI tests ([./hack/verify-import-boss.sh](https://github.com/kubernetes/kubernetes/blob/master/hack/verify-import-boss.sh)) to verify import restrictions in various places throughout k/k.
Currently, the only existing documentation is within the script itself and this.
xref: https://github.com/kubernetes/kubernetes/issues/81102 - import-boss ignores import in a _test.go file
xref: https://github.com/kubernetes/kubernetes/issues/81803 - failed to implement verify import restrictions in the e2 test framework.
Seems that import-boss is owned by API machinery
/sig api-machinery
/area code-organization
/kind documentation
/priority important-longterm
/cc @jaypipes | 1.0 | Document the use of import-boss - [import-boss](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/code-generator/cmd/import-boss/main.go) is used in our CI tests ([./hack/verify-import-boss.sh](https://github.com/kubernetes/kubernetes/blob/master/hack/verify-import-boss.sh)) to verify import restrictions in various places throughout k/k.
Currently, the only existing documentation is within the script itself and this.
xref: https://github.com/kubernetes/kubernetes/issues/81102 - import-boss ignores import in a _test.go file
xref: https://github.com/kubernetes/kubernetes/issues/81803 - failed to implement verify import restrictions in the e2 test framework.
Seems that import-boss is owned by API machinery
/sig api-machinery
/area code-organization
/kind documentation
/priority important-longterm
/cc @jaypipes | non_priority | document the use of import boss is used in our ci tests to verify import restrictions in various places throughout k k currently the only existing documentation is within the script itself and this xref import boss ignores import in a test go file xref failed to implement verify import restrictions in the test framework seems that import boss is owned by api machinery sig api machinery area code organization kind documentation priority important longterm cc jaypipes | 0 |
153,926 | 5,906,082,427 | IssuesEvent | 2017-05-19 14:23:53 | swimlane/ngx-charts | https://api.github.com/repos/swimlane/ngx-charts | closed | turn off transition (live data) | Backlog Effort: High Enhancement Priority: Med | **I'm submitting a ...** (check one with "x")
```
[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Please do not submit support request here
```
**Current behavior**
plunkr: [https://plnkr.co/edit/Nij7gO4jgqdN2mNPIFJp](https://plnkr.co/edit/Nij7gO4jgqdN2mNPIFJp)
**Expected behavior**
Shift the points + area left (previous position) without transition. (Only the new point and the corresponding area would use transition or simply appear).
**Reproduction of the problem**
[https://plnkr.co/edit/Nij7gO4jgqdN2mNPIFJp](https://plnkr.co/edit/Nij7gO4jgqdN2mNPIFJp)
**What is the motivation / use case for changing the behavior?**
As shown in the plunkr, it looks strange when the result set is updated with the new value. There is a transition between every point + area. Would be handy if this transition was optional.
**Please tell us about your environment:**
Windows, npm
* **Angular version:** 2.x.x
4.0.1
* **Browser:** [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Chrome Version 57.0.2987.133 (64-bit)
* **Language:** [all | TypeScript X.X | ES6/7 | ES5]
TypeScript 2.3.2 | 1.0 | turn off transition (live data) - **I'm submitting a ...** (check one with "x")
```
[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Please do not submit support request here
```
**Current behavior**
plunkr: [https://plnkr.co/edit/Nij7gO4jgqdN2mNPIFJp](https://plnkr.co/edit/Nij7gO4jgqdN2mNPIFJp)
**Expected behavior**
Shift the points + area left (previous position) without transition. (Only the new point and the corresponding area would use transition or simply appear).
**Reproduction of the problem**
[https://plnkr.co/edit/Nij7gO4jgqdN2mNPIFJp](https://plnkr.co/edit/Nij7gO4jgqdN2mNPIFJp)
**What is the motivation / use case for changing the behavior?**
As shown in the plunkr, it looks strange when the result set is updated with the new value. There is a transition between every point + area. Would be handy if this transition was optional.
**Please tell us about your environment:**
Windows, npm
* **Angular version:** 2.x.x
4.0.1
* **Browser:** [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Chrome Version 57.0.2987.133 (64-bit)
* **Language:** [all | TypeScript X.X | ES6/7 | ES5]
TypeScript 2.3.2 | priority | turn off transition live data i m submitting a check one with x bug report search github for a similar issue or pr before submitting feature request support request please do not submit support request here current behavior plunkr expected behavior shift the points area left previous position without transition only the new point and the corresponding area would use transition or simply appear reproduction of the problem what is the motivation use case for changing the behavior as shown in the plunkr it looks strange when the result set is updated with the new value there is a transition between every point area would be handy if this transition was optional please tell us about your environment windows npm angular version x x browser chrome version bit language typescript | 1 |
646,070 | 21,036,357,246 | IssuesEvent | 2022-03-31 08:13:57 | AY2122S2-CS2103-F11-2/tp | https://api.github.com/repos/AY2122S2-CS2103-F11-2/tp | opened | Update `Help` window | type.Bug priority.Medium Functionality | Currently the help window does not contain all available commands in this version.
Let's update it to contain all commands. | 1.0 | Update `Help` window - Currently the help window does not contain all available commands in this version.
Let's update it to contain all commands. | priority | update help window currently the help window does not contain all available commands in this version let s update it to contain all commands | 1 |
309,691 | 26,672,684,081 | IssuesEvent | 2023-01-26 11:44:00 | MarinoFajardo/ControlaTuGasto | https://api.github.com/repos/MarinoFajardo/ControlaTuGasto | closed | [M2] Es necesario comprobar que el comportamiento de la clase parada es el esperado. | invalid test | En #25 de describen una serie de comportamientos que debe cumplir la clase parada para que su funcionamiento sea el esperado:
- Para comprobar el comportamiento correcto de esta clase, es necesario que si dos paradas tienen el mismo id sean la misma parada, es decir, no puede haber dos paradas que tengan el mismo id y no sean exactamente iguales. Esto es así ya que sino se producirían confusiones con las paradas.
A raíz de estos comportamientos es necesario diseñar los test que comprueben que el comportamiento es el esperado.
* [x] Dos paradas no pueden tener el mismo id.
| 1.0 | [M2] Es necesario comprobar que el comportamiento de la clase parada es el esperado. - En #25 de describen una serie de comportamientos que debe cumplir la clase parada para que su funcionamiento sea el esperado:
- Para comprobar el comportamiento correcto de esta clase, es necesario que si dos paradas tienen el mismo id sean la misma parada, es decir, no puede haber dos paradas que tengan el mismo id y no sean exactamente iguales. Esto es así ya que sino se producirían confusiones con las paradas.
A raíz de estos comportamientos es necesario diseñar los test que comprueben que el comportamiento es el esperado.
* [x] Dos paradas no pueden tener el mismo id.
| non_priority | es necesario comprobar que el comportamiento de la clase parada es el esperado en de describen una serie de comportamientos que debe cumplir la clase parada para que su funcionamiento sea el esperado para comprobar el comportamiento correcto de esta clase es necesario que si dos paradas tienen el mismo id sean la misma parada es decir no puede haber dos paradas que tengan el mismo id y no sean exactamente iguales esto es así ya que sino se producirían confusiones con las paradas a raíz de estos comportamientos es necesario diseñar los test que comprueben que el comportamiento es el esperado dos paradas no pueden tener el mismo id | 0 |
424,872 | 29,181,547,129 | IssuesEvent | 2023-05-19 12:20:15 | awslabs/aws-lambda-powertools-typescript | https://api.github.com/repos/awslabs/aws-lambda-powertools-typescript | closed | Docs: fix inappropriate hilighted lines | area/documentation status/discussing | ### What were you searching in the docs?
Some highlighted lines in the sample code are inappropriate. Some are pointing to the wrong place, others to a line that does not exist.
The most obvious example is the "Example CloudWatch Logs excerpt" in Metric's "Adding metadata". It should be specified by highlighting the metadata on line 31.
### Is this related to an existing documentation section?
https://awslabs.github.io/aws-lambda-powertools-typescript/latest/core/metrics/#adding-metadata
### How can we improve?
Review and fix the highlighted lines in the code sample to ensure that they are correct.
### Got a suggestion in mind?
_No response_
### Acknowledgment
- [X] I understand the final update might be different from my proposed suggestion, or refused. | 1.0 | Docs: fix inappropriate hilighted lines - ### What were you searching in the docs?
Some highlighted lines in the sample code are inappropriate. Some are pointing to the wrong place, others to a line that does not exist.
The most obvious example is the "Example CloudWatch Logs excerpt" in Metric's "Adding metadata". It should be specified by highlighting the metadata on line 31.
### Is this related to an existing documentation section?
https://awslabs.github.io/aws-lambda-powertools-typescript/latest/core/metrics/#adding-metadata
### How can we improve?
Review and fix the highlighted lines in the code sample to ensure that they are correct.
### Got a suggestion in mind?
_No response_
### Acknowledgment
- [X] I understand the final update might be different from my proposed suggestion, or refused. | non_priority | docs fix inappropriate hilighted lines what were you searching in the docs some highlighted lines in the sample code are inappropriate some are pointing to the wrong place others to a line that does not exist the most obvious example is the example cloudwatch logs excerpt in metric s adding metadata it should be specified by highlighting the metadata on line is this related to an existing documentation section how can we improve review and fix the highlighted lines in the code sample to ensure that they are correct got a suggestion in mind no response acknowledgment i understand the final update might be different from my proposed suggestion or refused | 0 |
642,332 | 20,885,321,461 | IssuesEvent | 2022-03-23 04:00:12 | CobeyH/SENG-480A | https://api.github.com/repos/CobeyH/SENG-480A | closed | Icon sizes are too big on Safari | bug A Priority 1 | **Describe the bug**
When creating a group on Safari, the icon profile pictures aren't the correct size.
**To Reproduce**
Steps to reproduce the behavior:
1. Open the app on Safari
2. Create a new group
3. View the "Icon Profile Pictures"
**Expected behavior**
The icons will look the same on Safari and Chrome.
**Screenshots**
| 1.0 | Icon sizes are too big on Safari - **Describe the bug**
When creating a group on Safari, the icon profile pictures aren't the correct size.
**To Reproduce**
Steps to reproduce the behavior:
1. Open the app on Safari
2. Create a new group
3. View the "Icon Profile Pictures"
**Expected behavior**
The icons will look the same on Safari and Chrome.
**Screenshots**
| priority | icon sizes are too big on safari describe the bug when creating a group on safari the icon profile pictures aren t the correct size to reproduce steps to reproduce the behavior open the app on safari create a new group view the icon profile pictures expected behavior the icons will look the same on safari and chrome screenshots | 1 |
314,376 | 9,596,062,469 | IssuesEvent | 2019-05-09 17:37:42 | aiidateam/aiida-quantumespresso | https://api.github.com/repos/aiidateam/aiida-quantumespresso | closed | Bundle all CLI launchers in single click console script | priority/nice to have topic/cli type/accepted feature | Adding a single console script for each calculation and workflow launcher that we would like to make available is not tenable. | 1.0 | Bundle all CLI launchers in single click console script - Adding a single console script for each calculation and workflow launcher that we would like to make available is not tenable. | priority | bundle all cli launchers in single click console script adding a single console script for each calculation and workflow launcher that we would like to make available is not tenable | 1 |
318,085 | 27,284,453,320 | IssuesEvent | 2023-02-23 12:30:51 | cosmos/interchain-security | https://api.github.com/repos/cosmos/interchain-security | closed | Code review: Using ibc-go (cosmos/interchain-security) | testing | - [x] ibc-go team needs to review the code from an IBC perspective | 1.0 | Code review: Using ibc-go (cosmos/interchain-security) - - [x] ibc-go team needs to review the code from an IBC perspective | non_priority | code review using ibc go cosmos interchain security ibc go team needs to review the code from an ibc perspective | 0 |
40,477 | 12,797,753,299 | IssuesEvent | 2020-07-02 12:52:18 | RG4421/react-credit-card-input | https://api.github.com/repos/RG4421/react-credit-card-input | opened | CVE-2020-7660 (High) detected in serialize-javascript-1.9.1.tgz | security vulnerability | ## CVE-2020-7660 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>serialize-javascript-1.9.1.tgz</b></p></summary>
<p>Serialize JavaScript to a superset of JSON that includes regular expressions and functions.</p>
<p>Library home page: <a href="https://registry.npmjs.org/serialize-javascript/-/serialize-javascript-1.9.1.tgz">https://registry.npmjs.org/serialize-javascript/-/serialize-javascript-1.9.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/react-credit-card-input/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/react-credit-card-input/node_modules/serialize-javascript/package.json</p>
<p>
Dependency Hierarchy:
- react-3.4.12.tgz (Root Library)
- uglifyjs-webpack-plugin-1.3.0.tgz
- :x: **serialize-javascript-1.9.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/RG4421/react-credit-card-input/commit/4d1935810e311ceb2334ae5c8f1d6482c84a0dcd">4d1935810e311ceb2334ae5c8f1d6482c84a0dcd</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>
serialize-javascript prior to 3.1.0 allows remote attackers to inject arbitrary code via the function "deleteFunctions" within "index.js".
<p>Publish Date: 2020-06-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7660>CVE-2020-7660</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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-7660">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7660</a></p>
<p>Release Date: 2020-06-01</p>
<p>Fix Resolution: serialize-javascript - 3.1.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"serialize-javascript","packageVersion":"1.9.1","isTransitiveDependency":true,"dependencyTree":"@storybook/react:3.4.12;uglifyjs-webpack-plugin:1.3.0;serialize-javascript:1.9.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"serialize-javascript - 3.1.0"}],"vulnerabilityIdentifier":"CVE-2020-7660","vulnerabilityDetails":"serialize-javascript prior to 3.1.0 allows remote attackers to inject arbitrary code via the function \"deleteFunctions\" within \"index.js\".","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7660","cvss3Severity":"high","cvss3Score":"8.1","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-7660 (High) detected in serialize-javascript-1.9.1.tgz - ## CVE-2020-7660 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>serialize-javascript-1.9.1.tgz</b></p></summary>
<p>Serialize JavaScript to a superset of JSON that includes regular expressions and functions.</p>
<p>Library home page: <a href="https://registry.npmjs.org/serialize-javascript/-/serialize-javascript-1.9.1.tgz">https://registry.npmjs.org/serialize-javascript/-/serialize-javascript-1.9.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/react-credit-card-input/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/react-credit-card-input/node_modules/serialize-javascript/package.json</p>
<p>
Dependency Hierarchy:
- react-3.4.12.tgz (Root Library)
- uglifyjs-webpack-plugin-1.3.0.tgz
- :x: **serialize-javascript-1.9.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/RG4421/react-credit-card-input/commit/4d1935810e311ceb2334ae5c8f1d6482c84a0dcd">4d1935810e311ceb2334ae5c8f1d6482c84a0dcd</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>
serialize-javascript prior to 3.1.0 allows remote attackers to inject arbitrary code via the function "deleteFunctions" within "index.js".
<p>Publish Date: 2020-06-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7660>CVE-2020-7660</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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-7660">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7660</a></p>
<p>Release Date: 2020-06-01</p>
<p>Fix Resolution: serialize-javascript - 3.1.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"serialize-javascript","packageVersion":"1.9.1","isTransitiveDependency":true,"dependencyTree":"@storybook/react:3.4.12;uglifyjs-webpack-plugin:1.3.0;serialize-javascript:1.9.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"serialize-javascript - 3.1.0"}],"vulnerabilityIdentifier":"CVE-2020-7660","vulnerabilityDetails":"serialize-javascript prior to 3.1.0 allows remote attackers to inject arbitrary code via the function \"deleteFunctions\" within \"index.js\".","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7660","cvss3Severity":"high","cvss3Score":"8.1","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in serialize javascript tgz cve high severity vulnerability vulnerable library serialize javascript tgz serialize javascript to a superset of json that includes regular expressions and functions library home page a href path to dependency file tmp ws scm react credit card input package json path to vulnerable library tmp ws scm react credit card input node modules serialize javascript package json dependency hierarchy react tgz root library uglifyjs webpack plugin tgz x serialize javascript tgz vulnerable library found in head commit a href vulnerability details serialize javascript prior to allows remote attackers to inject arbitrary code via the function deletefunctions within index js publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution serialize javascript isopenpronvulnerability true ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails serialize javascript prior to allows remote attackers to inject arbitrary code via the function deletefunctions within index js vulnerabilityurl | 0 |
43,027 | 12,965,164,764 | IssuesEvent | 2020-07-20 21:48:48 | jtimberlake/griffin | https://api.github.com/repos/jtimberlake/griffin | opened | WS-2019-0333 (Medium) detected in handlebars-1.3.0.tgz | security vulnerability | ## WS-2019-0333 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-1.3.0.tgz</b></p></summary>
<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-1.3.0.tgz">https://registry.npmjs.org/handlebars/-/handlebars-1.3.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/griffin/ui/angular/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/griffin/ui/angular/node_modules/handlebars/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.3.0.tgz (Root Library)
- postcss-url-5.1.2.tgz
- directory-encoder-0.7.2.tgz
- :x: **handlebars-1.3.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/jtimberlake/griffin/commit/7b8d4cb53c4eab239eecb18da5b2a6048b2fce60">7b8d4cb53c4eab239eecb18da5b2a6048b2fce60</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prototype Pollution vulnerability found in handlebars 1.0.6 before 4.5.3. It is possible to add or modify properties to the Object prototype through a malicious template. Attacker may crash the application or execute Arbitrary Code in specific conditions.
<p>Publish Date: 2019-11-18
<p>URL: <a href=https://github.com/wycats/handlebars.js/commit/f7f05d7558e674856686b62a00cde5758f3b7a08>WS-2019-0333</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</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.npmjs.com/advisories/1325">https://www.npmjs.com/advisories/1325</a></p>
<p>Release Date: 2019-12-05</p>
<p>Fix Resolution: handlebars - 4.5.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"handlebars","packageVersion":"1.3.0","isTransitiveDependency":true,"dependencyTree":"@angular/cli:1.3.0;postcss-url:5.1.2;directory-encoder:0.7.2;handlebars:1.3.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"handlebars - 4.5.3"}],"vulnerabilityIdentifier":"WS-2019-0333","vulnerabilityDetails":"Prototype Pollution vulnerability found in handlebars 1.0.6 before 4.5.3. It is possible to add or modify properties to the Object prototype through a malicious template. Attacker may crash the application or execute Arbitrary Code in specific conditions.","vulnerabilityUrl":"https://github.com/wycats/handlebars.js/commit/f7f05d7558e674856686b62a00cde5758f3b7a08","cvss2Severity":"medium","cvss2Score":"5.0","extraData":{}}</REMEDIATE> --> | True | WS-2019-0333 (Medium) detected in handlebars-1.3.0.tgz - ## WS-2019-0333 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-1.3.0.tgz</b></p></summary>
<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-1.3.0.tgz">https://registry.npmjs.org/handlebars/-/handlebars-1.3.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/griffin/ui/angular/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/griffin/ui/angular/node_modules/handlebars/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.3.0.tgz (Root Library)
- postcss-url-5.1.2.tgz
- directory-encoder-0.7.2.tgz
- :x: **handlebars-1.3.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/jtimberlake/griffin/commit/7b8d4cb53c4eab239eecb18da5b2a6048b2fce60">7b8d4cb53c4eab239eecb18da5b2a6048b2fce60</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prototype Pollution vulnerability found in handlebars 1.0.6 before 4.5.3. It is possible to add or modify properties to the Object prototype through a malicious template. Attacker may crash the application or execute Arbitrary Code in specific conditions.
<p>Publish Date: 2019-11-18
<p>URL: <a href=https://github.com/wycats/handlebars.js/commit/f7f05d7558e674856686b62a00cde5758f3b7a08>WS-2019-0333</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</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.npmjs.com/advisories/1325">https://www.npmjs.com/advisories/1325</a></p>
<p>Release Date: 2019-12-05</p>
<p>Fix Resolution: handlebars - 4.5.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"handlebars","packageVersion":"1.3.0","isTransitiveDependency":true,"dependencyTree":"@angular/cli:1.3.0;postcss-url:5.1.2;directory-encoder:0.7.2;handlebars:1.3.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"handlebars - 4.5.3"}],"vulnerabilityIdentifier":"WS-2019-0333","vulnerabilityDetails":"Prototype Pollution vulnerability found in handlebars 1.0.6 before 4.5.3. It is possible to add or modify properties to the Object prototype through a malicious template. Attacker may crash the application or execute Arbitrary Code in specific conditions.","vulnerabilityUrl":"https://github.com/wycats/handlebars.js/commit/f7f05d7558e674856686b62a00cde5758f3b7a08","cvss2Severity":"medium","cvss2Score":"5.0","extraData":{}}</REMEDIATE> --> | non_priority | ws medium detected in handlebars tgz ws medium severity vulnerability vulnerable library handlebars tgz handlebars provides the power necessary to let you build semantic templates effectively with no frustration library home page a href path to dependency file tmp ws scm griffin ui angular package json path to vulnerable library tmp ws scm griffin ui angular node modules handlebars package json dependency hierarchy cli tgz root library postcss url tgz directory encoder tgz x handlebars tgz vulnerable library found in head commit a href vulnerability details prototype pollution vulnerability found in handlebars before it is possible to add or modify properties to the object prototype through a malicious template attacker may crash the application or execute arbitrary code in specific conditions publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution handlebars isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier ws vulnerabilitydetails prototype pollution vulnerability found in handlebars before it is possible to add or modify properties to the object prototype through a malicious template attacker may crash the application or execute arbitrary code in specific conditions vulnerabilityurl | 0 |
813,352 | 30,454,740,079 | IssuesEvent | 2023-07-16 18:45:45 | priyankarpal/ProjectsHut | https://api.github.com/repos/priyankarpal/ProjectsHut | closed | feat:Adding hover effect on the links | 🛠 goal: fix ⭐ goal: addition 🟩 priority: low 🏁 status: ready for dev | ### What feature?
addition of the hover effect on the links will look great!!
### Add screenshots
### Record
- [X] I agree to follow this project's Code of Conduct
- [ ] I'm a GSSoC'23 contributor
- [X] I want to work on this issue | 1.0 | feat:Adding hover effect on the links - ### What feature?
addition of the hover effect on the links will look great!!
### Add screenshots
### Record
- [X] I agree to follow this project's Code of Conduct
- [ ] I'm a GSSoC'23 contributor
- [X] I want to work on this issue | priority | feat adding hover effect on the links what feature addition of the hover effect on the links will look great add screenshots record i agree to follow this project s code of conduct i m a gssoc contributor i want to work on this issue | 1 |
548,215 | 16,060,333,621 | IssuesEvent | 2021-04-23 11:37:16 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.samplicio.us - see bug description | browser-fenix engine-gecko ml-needsdiagnosis-false priority-normal | <!-- @browser: Firefox Mobile 88.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.1.0; Mobile; rv:88.0) Gecko/88.0 Firefox/88.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/71450 -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://www.samplicio.us/s/RelevantID.aspx?RVPID=IBD13033769173&RVSID=10961636&RSID=0769b34d-9043-4e0a-a73a-8a32f848aa12&RVTO=8000&SSID=60806584-1e10-378a-0dc4-c3abb2565d60
**Browser / Version**: Firefox Mobile 88.0
**Operating System**: Android 8.1.0
**Tested Another Browser**: Yes Chrome
**Problem type**: Something else
**Description**: Lost connection
**Steps to Reproduce**:
every survey failed loading.Can not connected survey site.
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2021/4/84aa1fb3-15f8-479a-9d64-11aba5f5ff1c.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20210410185959</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2021/4/a29f57e6-e773-4e92-83b2-3eb1676fa486)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.samplicio.us - see bug description - <!-- @browser: Firefox Mobile 88.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.1.0; Mobile; rv:88.0) Gecko/88.0 Firefox/88.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/71450 -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://www.samplicio.us/s/RelevantID.aspx?RVPID=IBD13033769173&RVSID=10961636&RSID=0769b34d-9043-4e0a-a73a-8a32f848aa12&RVTO=8000&SSID=60806584-1e10-378a-0dc4-c3abb2565d60
**Browser / Version**: Firefox Mobile 88.0
**Operating System**: Android 8.1.0
**Tested Another Browser**: Yes Chrome
**Problem type**: Something else
**Description**: Lost connection
**Steps to Reproduce**:
every survey failed loading.Can not connected survey site.
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2021/4/84aa1fb3-15f8-479a-9d64-11aba5f5ff1c.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20210410185959</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2021/4/a29f57e6-e773-4e92-83b2-3eb1676fa486)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | see bug description url browser version firefox mobile operating system android tested another browser yes chrome problem type something else description lost connection steps to reproduce every survey failed loading can not connected survey site view the screenshot img alt screenshot src browser configuration gfx webrender all false gfx webrender blob images true gfx webrender enabled false image mem shared true buildid channel beta hastouchscreen true mixed active content blocked false mixed passive content blocked false tracking content blocked false from with ❤️ | 1 |
171,911 | 21,007,659,465 | IssuesEvent | 2022-03-30 01:16:53 | Satheesh575555/kernel-mm-huge_memory | https://api.github.com/repos/Satheesh575555/kernel-mm-huge_memory | opened | CVE-2021-29154 (High) detected in linuxlinux-4.19.236 | security vulnerability | ## CVE-2021-29154 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.19.236</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
BPF JIT compilers in the Linux kernel through 5.11.12 have incorrect computation of branch displacements, allowing them to execute arbitrary code within the kernel context. This affects arch/x86/net/bpf_jit_comp.c and arch/x86/net/bpf_jit_comp32.c.
<p>Publish Date: 2021-04-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29154>CVE-2021-29154</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2021-29154">https://www.linuxkernelcves.com/cves/CVE-2021-29154</a></p>
<p>Release Date: 2021-04-08</p>
<p>Fix Resolution: v4.4.266, v4.9.266, v4.14.230, v4.19.186, v5.4.111, v5.10.29, v5.11.13</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-29154 (High) detected in linuxlinux-4.19.236 - ## CVE-2021-29154 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.19.236</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
BPF JIT compilers in the Linux kernel through 5.11.12 have incorrect computation of branch displacements, allowing them to execute arbitrary code within the kernel context. This affects arch/x86/net/bpf_jit_comp.c and arch/x86/net/bpf_jit_comp32.c.
<p>Publish Date: 2021-04-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29154>CVE-2021-29154</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2021-29154">https://www.linuxkernelcves.com/cves/CVE-2021-29154</a></p>
<p>Release Date: 2021-04-08</p>
<p>Fix Resolution: v4.4.266, v4.9.266, v4.14.230, v4.19.186, v5.4.111, v5.10.29, v5.11.13</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in linuxlinux cve high severity vulnerability vulnerable library linuxlinux the linux kernel library home page a href found in base branch master vulnerable source files vulnerability details bpf jit compilers in the linux kernel through have incorrect computation of branch displacements allowing them to execute arbitrary code within the kernel context this affects arch net bpf jit comp c and arch net bpf jit c publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
554,631 | 16,435,033,187 | IssuesEvent | 2021-05-20 08:17:49 | StrangeLoopGames/EcoIssues | https://api.github.com/repos/StrangeLoopGames/EcoIssues | closed | 9.3 1966 - Rent currency does not default to what treasury has set | Category: Gameplay Priority: Low Squad: Wild Turkey Type: Bug | As per subject, rent's currency does not default to the currency that the treasury has set.
| 1.0 | 9.3 1966 - Rent currency does not default to what treasury has set - As per subject, rent's currency does not default to the currency that the treasury has set.
| priority | rent currency does not default to what treasury has set as per subject rent s currency does not default to the currency that the treasury has set | 1 |
375,935 | 11,136,165,674 | IssuesEvent | 2019-12-20 15:58:58 | dhenry-KCI/FredCo-Post-Go-Live- | https://api.github.com/repos/dhenry-KCI/FredCo-Post-Go-Live- | opened | Building Permits - Capacity - Spring View Estates Subdivision Fees | Medium Priority | CAPACITY - RESIDENTIAL SINGLE FAMILY DWELLING
AP # 258425
The Spring View Estates subdivision code 041244 needs to automatically add the RESIDENTIAL SEWER FEE 20400 ($7509.00) when it is a residential occupancy type.
Terry manually added these fees to the application in PROD.
| 1.0 | Building Permits - Capacity - Spring View Estates Subdivision Fees - CAPACITY - RESIDENTIAL SINGLE FAMILY DWELLING
AP # 258425
The Spring View Estates subdivision code 041244 needs to automatically add the RESIDENTIAL SEWER FEE 20400 ($7509.00) when it is a residential occupancy type.
Terry manually added these fees to the application in PROD.
| priority | building permits capacity spring view estates subdivision fees capacity residential single family dwelling ap the spring view estates subdivision code needs to automatically add the residential sewer fee when it is a residential occupancy type terry manually added these fees to the application in prod | 1 |
673,443 | 22,969,835,113 | IssuesEvent | 2022-07-20 01:16:33 | stackcollision/Nebulous-BugReporting | https://api.github.com/repos/stackcollision/Nebulous-BugReporting | closed | Sprint stage on hybrid missiles (Cyclone, Atlatl) with max speed settings have sprint stages seperate with insufficient range. | bug branch-modmis incorrect behavior priority high | **Describe the bug**
Sprint stage on hybrid missiles (Cyclone, Atlatl) with max speed settings have sprint stages seperate with insufficient range.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to Missile Designer
2. Create new hybrid missile (Cyclone, Atlatl) and set sprint stage to maximum speed.
3. Stage seperation triggers with insufficient range.
**Expected behavior**
Missile will compensate by shortening stage seperation range.
**Additional context**
None
**Attachments**
| 1.0 | Sprint stage on hybrid missiles (Cyclone, Atlatl) with max speed settings have sprint stages seperate with insufficient range. - **Describe the bug**
Sprint stage on hybrid missiles (Cyclone, Atlatl) with max speed settings have sprint stages seperate with insufficient range.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to Missile Designer
2. Create new hybrid missile (Cyclone, Atlatl) and set sprint stage to maximum speed.
3. Stage seperation triggers with insufficient range.
**Expected behavior**
Missile will compensate by shortening stage seperation range.
**Additional context**
None
**Attachments**
| priority | sprint stage on hybrid missiles cyclone atlatl with max speed settings have sprint stages seperate with insufficient range describe the bug sprint stage on hybrid missiles cyclone atlatl with max speed settings have sprint stages seperate with insufficient range to reproduce steps to reproduce the behavior go to missile designer create new hybrid missile cyclone atlatl and set sprint stage to maximum speed stage seperation triggers with insufficient range expected behavior missile will compensate by shortening stage seperation range additional context none attachments | 1 |
359,951 | 10,682,735,166 | IssuesEvent | 2019-10-22 06:31:05 | bounswe/bounswe2019group8 | https://api.github.com/repos/bounswe/bounswe2019group8 | closed | Add data picker and check valid cases for sign up. | Effort: High Mobile Platform: Mobile Priority: High Status: Done Status: In Progress Type: Feature | **Actions:**
1. Add data picker in sign up.
2. Check valid for iban and id numbers.
3. Check user exists.
**Notes:**
- [x] Add data picker in sign up.
- [x] Check valid for iban and id numbers.
- [x] Check user exists.
**Deadline:** 22.10.2019 - 11.00 | 1.0 | Add data picker and check valid cases for sign up. - **Actions:**
1. Add data picker in sign up.
2. Check valid for iban and id numbers.
3. Check user exists.
**Notes:**
- [x] Add data picker in sign up.
- [x] Check valid for iban and id numbers.
- [x] Check user exists.
**Deadline:** 22.10.2019 - 11.00 | priority | add data picker and check valid cases for sign up actions add data picker in sign up check valid for iban and id numbers check user exists notes add data picker in sign up check valid for iban and id numbers check user exists deadline | 1 |
23,435 | 6,419,940,820 | IssuesEvent | 2017-08-08 22:30:30 | xhqiao89/HydroDesktop_test | https://api.github.com/repos/xhqiao89/HydroDesktop_test | closed | Add a series to a theme (from another theme) | CodePlex | <b>dtarb[CodePlex]</b> <br />I would like to be able to:
Add a series to a theme (from another theme)
this feature can be added as a new context menu item in the series selector menu.
| 1.0 | Add a series to a theme (from another theme) - <b>dtarb[CodePlex]</b> <br />I would like to be able to:
Add a series to a theme (from another theme)
this feature can be added as a new context menu item in the series selector menu.
| non_priority | add a series to a theme from another theme dtarb i would like to be able to add a series to a theme from another theme this feature can be added as a new context menu item in the series selector menu | 0 |
5,482 | 2,576,697,805 | IssuesEvent | 2015-02-12 12:12:52 | olga-jane/prizm | https://api.github.com/repos/olga-jane/prizm | closed | Add file button should be at the left, Close at the right at ExternalFile dialog | Attachments bug bug - UI Coding MEDIUM priority | Add file button should be at the left, Close at the right at ExternalFile dialog.
Now both buttons are at the right. | 1.0 | Add file button should be at the left, Close at the right at ExternalFile dialog - Add file button should be at the left, Close at the right at ExternalFile dialog.
Now both buttons are at the right. | priority | add file button should be at the left close at the right at externalfile dialog add file button should be at the left close at the right at externalfile dialog now both buttons are at the right | 1 |
35,748 | 7,800,527,202 | IssuesEvent | 2018-06-09 10:32:10 | StrikeNP/trac_test | https://api.github.com/repos/StrikeNP/trac_test | closed | Divide integer, public declarations in stats_variables.F90 into smaller blocks in order to avoid ANSI warning (Trac #545) | Migrated from Trac clubb_src defect raut@uwm.edu |
'''Introduction'''
We try to keep CLUBB compatible with ANSI standards in order to enhance portability. ANSI requires that no more than 39 continuation characters (i.e. &) be used for one line. However, when we add new variables to declaration lists, we sometimes exceed 39 continuation characters, thereby triggering a warning. The most recent example occurred on 6 Feb 2013, where [source:/CLUBB/trunk/src/CLUBB_core/stats_variables.F90?rev=6056#L55 this block in stats_variables.F90] exceeded 39 continuations. The resulting error message was:
```text
"/usr/nightly_tests/clubb/compile/../src/CLUBB_core/stats_variables.F90",
Line = 96, Column = 1:
ANSI: More than 39 continuation lines is an extension to the
Fortran standard in free source form.
```
'''Technical spec'''
Let's break the integer, public declaration blocks into smaller declaration blocks with, say, no more than 20 lines, so that the addition of new variables triggers the warning less often. Are there other files with lots of continuations? If so, should we break up those blocks as well?
Attachments:
Migrated from http://carson.math.uwm.edu/trac/clubb/ticket/545
```json
{
"status": "closed",
"changetime": "2014-08-06T23:26:29",
"description": "\n'''Introduction'''\n\nWe try to keep CLUBB compatible with ANSI standards in order to enhance portability. ANSI requires that no more than 39 continuation characters (i.e. &) be used for one line. However, when we add new variables to declaration lists, we sometimes exceed 39 continuation characters, thereby triggering a warning. The most recent example occurred on 6 Feb 2013, where [source:/CLUBB/trunk/src/CLUBB_core/stats_variables.F90?rev=6056#L55 this block in stats_variables.F90] exceeded 39 continuations. The resulting error message was:\n{{{\n\"/usr/nightly_tests/clubb/compile/../src/CLUBB_core/stats_variables.F90\", \nLine = 96, Column = 1: \nANSI: More than 39 continuation lines is an extension to the \nFortran standard in free source form.\n}}}\n\n'''Technical spec'''\n\nLet's break the integer, public declaration blocks into smaller declaration blocks with, say, no more than 20 lines, so that the addition of new variables triggers the warning less often. Are there other files with lots of continuations? If so, should we break up those blocks as well?",
"reporter": "vlarson@uwm.edu",
"cc": "vlarson@uwm.edu, bmg2@uwm.edu",
"resolution": "fixed",
"_ts": "1407367589153596",
"component": "clubb_src",
"summary": "Divide integer, public declarations in stats_variables.F90 into smaller blocks in order to avoid ANSI warning",
"priority": "minor",
"keywords": "",
"time": "2013-02-06T18:01:36",
"milestone": "3. Refactor CLUBB",
"owner": "raut@uwm.edu",
"type": "defect"
}
```
| 1.0 | Divide integer, public declarations in stats_variables.F90 into smaller blocks in order to avoid ANSI warning (Trac #545) -
'''Introduction'''
We try to keep CLUBB compatible with ANSI standards in order to enhance portability. ANSI requires that no more than 39 continuation characters (i.e. &) be used for one line. However, when we add new variables to declaration lists, we sometimes exceed 39 continuation characters, thereby triggering a warning. The most recent example occurred on 6 Feb 2013, where [source:/CLUBB/trunk/src/CLUBB_core/stats_variables.F90?rev=6056#L55 this block in stats_variables.F90] exceeded 39 continuations. The resulting error message was:
```text
"/usr/nightly_tests/clubb/compile/../src/CLUBB_core/stats_variables.F90",
Line = 96, Column = 1:
ANSI: More than 39 continuation lines is an extension to the
Fortran standard in free source form.
```
'''Technical spec'''
Let's break the integer, public declaration blocks into smaller declaration blocks with, say, no more than 20 lines, so that the addition of new variables triggers the warning less often. Are there other files with lots of continuations? If so, should we break up those blocks as well?
Attachments:
Migrated from http://carson.math.uwm.edu/trac/clubb/ticket/545
```json
{
"status": "closed",
"changetime": "2014-08-06T23:26:29",
"description": "\n'''Introduction'''\n\nWe try to keep CLUBB compatible with ANSI standards in order to enhance portability. ANSI requires that no more than 39 continuation characters (i.e. &) be used for one line. However, when we add new variables to declaration lists, we sometimes exceed 39 continuation characters, thereby triggering a warning. The most recent example occurred on 6 Feb 2013, where [source:/CLUBB/trunk/src/CLUBB_core/stats_variables.F90?rev=6056#L55 this block in stats_variables.F90] exceeded 39 continuations. The resulting error message was:\n{{{\n\"/usr/nightly_tests/clubb/compile/../src/CLUBB_core/stats_variables.F90\", \nLine = 96, Column = 1: \nANSI: More than 39 continuation lines is an extension to the \nFortran standard in free source form.\n}}}\n\n'''Technical spec'''\n\nLet's break the integer, public declaration blocks into smaller declaration blocks with, say, no more than 20 lines, so that the addition of new variables triggers the warning less often. Are there other files with lots of continuations? If so, should we break up those blocks as well?",
"reporter": "vlarson@uwm.edu",
"cc": "vlarson@uwm.edu, bmg2@uwm.edu",
"resolution": "fixed",
"_ts": "1407367589153596",
"component": "clubb_src",
"summary": "Divide integer, public declarations in stats_variables.F90 into smaller blocks in order to avoid ANSI warning",
"priority": "minor",
"keywords": "",
"time": "2013-02-06T18:01:36",
"milestone": "3. Refactor CLUBB",
"owner": "raut@uwm.edu",
"type": "defect"
}
```
| non_priority | divide integer public declarations in stats variables into smaller blocks in order to avoid ansi warning trac introduction we try to keep clubb compatible with ansi standards in order to enhance portability ansi requires that no more than continuation characters i e be used for one line however when we add new variables to declaration lists we sometimes exceed continuation characters thereby triggering a warning the most recent example occurred on feb where exceeded continuations the resulting error message was text usr nightly tests clubb compile src clubb core stats variables line column ansi more than continuation lines is an extension to the fortran standard in free source form technical spec let s break the integer public declaration blocks into smaller declaration blocks with say no more than lines so that the addition of new variables triggers the warning less often are there other files with lots of continuations if so should we break up those blocks as well attachments migrated from json status closed changetime description n introduction n nwe try to keep clubb compatible with ansi standards in order to enhance portability ansi requires that no more than continuation characters i e be used for one line however when we add new variables to declaration lists we sometimes exceed continuation characters thereby triggering a warning the most recent example occurred on feb where exceeded continuations the resulting error message was n n usr nightly tests clubb compile src clubb core stats variables nline column nansi more than continuation lines is an extension to the nfortran standard in free source form n n n technical spec n nlet s break the integer public declaration blocks into smaller declaration blocks with say no more than lines so that the addition of new variables triggers the warning less often are there other files with lots of continuations if so should we break up those blocks as well reporter vlarson uwm edu cc vlarson uwm edu uwm edu resolution fixed ts component clubb src summary divide integer public declarations in stats variables into smaller blocks in order to avoid ansi warning priority minor keywords time milestone refactor clubb owner raut uwm edu type defect | 0 |
57,142 | 3,081,243,195 | IssuesEvent | 2015-08-22 14:33:35 | bitfighter/bitfighter | https://api.github.com/repos/bitfighter/bitfighter | closed | Seekers seek teammates in single-team rabbit | 019a bug imported Priority-Medium | _From [buckyballreaction](https://code.google.com/u/buckyballreaction/) on January 07, 2014 11:59:38_
Seekers seek teammates in single-team rabbit
_Original issue: http://code.google.com/p/bitfighter/issues/detail?id=365_ | 1.0 | Seekers seek teammates in single-team rabbit - _From [buckyballreaction](https://code.google.com/u/buckyballreaction/) on January 07, 2014 11:59:38_
Seekers seek teammates in single-team rabbit
_Original issue: http://code.google.com/p/bitfighter/issues/detail?id=365_ | priority | seekers seek teammates in single team rabbit from on january seekers seek teammates in single team rabbit original issue | 1 |
5,633 | 2,577,816,936 | IssuesEvent | 2015-02-12 19:18:42 | phetsims/tasks | https://api.github.com/repos/phetsims/tasks | closed | Update budgets through Jan | Accounting Top Priority | @arnabp Please prioritize updating these budgets through Jan 2015:
Moore NSF DRK12 NSF DRK12 Matching NSF TUES CHEM
Also, your laptop is in F1011 - should hopefully get labeled today. | 1.0 | Update budgets through Jan - @arnabp Please prioritize updating these budgets through Jan 2015:
Moore NSF DRK12 NSF DRK12 Matching NSF TUES CHEM
Also, your laptop is in F1011 - should hopefully get labeled today. | priority | update budgets through jan arnabp please prioritize updating these budgets through jan moore nsf nsf matching nsf tues chem also your laptop is in should hopefully get labeled today | 1 |
82,579 | 15,648,357,771 | IssuesEvent | 2021-03-23 05:33:29 | YJSoft/namuhub | https://api.github.com/repos/YJSoft/namuhub | closed | CVE-2019-16789 (High) detected in waitress-0.8.9.tar.gz - autoclosed | security vulnerability | ## CVE-2019-16789 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>waitress-0.8.9.tar.gz</b></p></summary>
<p>Waitress WSGI server</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/ee/65/fc9dee74a909a1187ca51e4f15ad9c4d35476e4ab5813f73421505c48053/waitress-0.8.9.tar.gz">https://files.pythonhosted.org/packages/ee/65/fc9dee74a909a1187ca51e4f15ad9c4d35476e4ab5813f73421505c48053/waitress-0.8.9.tar.gz</a></p>
<p>Path to dependency file: namuhub/requirements.txt</p>
<p>Path to vulnerable library: namuhub/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **waitress-0.8.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/YJSoft/namuhub/commit/3e2e58c112b34d9d89ec2ec01b44226ffaaf7d87">3e2e58c112b34d9d89ec2ec01b44226ffaaf7d87</a></p>
<p>Found in base branch: <b>develop</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>
In Waitress through version 1.4.0, if a proxy server is used in front of waitress, an invalid request may be sent by an attacker that bypasses the front-end and is parsed differently by waitress leading to a potential for HTTP request smuggling. Specially crafted requests containing special whitespace characters in the Transfer-Encoding header would get parsed by Waitress as being a chunked request, but a front-end server would use the Content-Length instead as the Transfer-Encoding header is considered invalid due to containing invalid characters. If a front-end server does HTTP pipelining to a backend Waitress server this could lead to HTTP request splitting which may lead to potential cache poisoning or unexpected information disclosure. This issue is fixed in Waitress 1.4.1 through more strict HTTP field validation.
<p>Publish Date: 2019-12-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16789>CVE-2019-16789</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: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-m5ff-3wj3-8ph4">https://github.com/advisories/GHSA-m5ff-3wj3-8ph4</a></p>
<p>Release Date: 2019-12-26</p>
<p>Fix Resolution: v1.4.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2019-16789 (High) detected in waitress-0.8.9.tar.gz - autoclosed - ## CVE-2019-16789 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>waitress-0.8.9.tar.gz</b></p></summary>
<p>Waitress WSGI server</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/ee/65/fc9dee74a909a1187ca51e4f15ad9c4d35476e4ab5813f73421505c48053/waitress-0.8.9.tar.gz">https://files.pythonhosted.org/packages/ee/65/fc9dee74a909a1187ca51e4f15ad9c4d35476e4ab5813f73421505c48053/waitress-0.8.9.tar.gz</a></p>
<p>Path to dependency file: namuhub/requirements.txt</p>
<p>Path to vulnerable library: namuhub/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **waitress-0.8.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/YJSoft/namuhub/commit/3e2e58c112b34d9d89ec2ec01b44226ffaaf7d87">3e2e58c112b34d9d89ec2ec01b44226ffaaf7d87</a></p>
<p>Found in base branch: <b>develop</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>
In Waitress through version 1.4.0, if a proxy server is used in front of waitress, an invalid request may be sent by an attacker that bypasses the front-end and is parsed differently by waitress leading to a potential for HTTP request smuggling. Specially crafted requests containing special whitespace characters in the Transfer-Encoding header would get parsed by Waitress as being a chunked request, but a front-end server would use the Content-Length instead as the Transfer-Encoding header is considered invalid due to containing invalid characters. If a front-end server does HTTP pipelining to a backend Waitress server this could lead to HTTP request splitting which may lead to potential cache poisoning or unexpected information disclosure. This issue is fixed in Waitress 1.4.1 through more strict HTTP field validation.
<p>Publish Date: 2019-12-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16789>CVE-2019-16789</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: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-m5ff-3wj3-8ph4">https://github.com/advisories/GHSA-m5ff-3wj3-8ph4</a></p>
<p>Release Date: 2019-12-26</p>
<p>Fix Resolution: v1.4.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in waitress tar gz autoclosed cve high severity vulnerability vulnerable library waitress tar gz waitress wsgi server library home page a href path to dependency file namuhub requirements txt path to vulnerable library namuhub requirements txt dependency hierarchy x waitress tar gz vulnerable library found in head commit a href found in base branch develop vulnerability details in waitress through version if a proxy server is used in front of waitress an invalid request may be sent by an attacker that bypasses the front end and is parsed differently by waitress leading to a potential for http request smuggling specially crafted requests containing special whitespace characters in the transfer encoding header would get parsed by waitress as being a chunked request but a front end server would use the content length instead as the transfer encoding header is considered invalid due to containing invalid characters if a front end server does http pipelining to a backend waitress server this could lead to http request splitting which may lead to potential cache poisoning or unexpected information disclosure this issue is fixed in waitress through more strict http field validation publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
633,805 | 20,266,249,369 | IssuesEvent | 2022-02-15 12:21:41 | HabitRPG/habitica-ios | https://api.github.com/repos/HabitRPG/habitica-ios | closed | Japanese not showing correctly for login incentive rewards | Type: Bug Help wanted Priority: minor | natalie checked the string, and that seems fine. there just seems to be an issue with displaying the characters?
> iOS Version: 15.1
Device: iPhone 8
App Version: 3.4.4 (649)
User ID: e0b0a48b-c8ae-40d1-a1e2-84d3ac821f89
Level: 7
Class: warrior
Is in Inn: false
Uses Costume: false
Custom Day Start: 4 | 1.0 | Japanese not showing correctly for login incentive rewards - natalie checked the string, and that seems fine. there just seems to be an issue with displaying the characters?
> iOS Version: 15.1
Device: iPhone 8
App Version: 3.4.4 (649)
User ID: e0b0a48b-c8ae-40d1-a1e2-84d3ac821f89
Level: 7
Class: warrior
Is in Inn: false
Uses Costume: false
Custom Day Start: 4 | priority | japanese not showing correctly for login incentive rewards natalie checked the string and that seems fine there just seems to be an issue with displaying the characters ios version device iphone app version user id level class warrior is in inn false uses costume false custom day start | 1 |
392,549 | 26,946,996,586 | IssuesEvent | 2023-02-08 08:55:00 | trixi-framework/Trixi.jl | https://api.github.com/repos/trixi-framework/Trixi.jl | opened | Update instructions to build docs locally | documentation | Developing Trixi on a fork may include adding types / function with corresponding docstrings. Previewing the documentation from a fork online is not available for security reasons. To preview the docs with your local documentation changes and updates one needs to use the following commands (taken directly from #668)
```
julia --project=docs/ -e 'using Pkg; Pkg.develop(PackageSpec(path=pwd())); Pkg.instantiate()'
julia --project=docs --color=yes docs/make.jl
```
The current instructions from the Development section of the docs says to use
```
julia --project=docs -e 'using Pkg; Pkg.instantiate(); include("docs/make.jl")'
```
This indeed works, but it build the docs for the current stable release of Trixi and not for the local development changes.
We should update the instructions on building the docs locally such that it is clear for people with forks how to get their docs to build. | 1.0 | Update instructions to build docs locally - Developing Trixi on a fork may include adding types / function with corresponding docstrings. Previewing the documentation from a fork online is not available for security reasons. To preview the docs with your local documentation changes and updates one needs to use the following commands (taken directly from #668)
```
julia --project=docs/ -e 'using Pkg; Pkg.develop(PackageSpec(path=pwd())); Pkg.instantiate()'
julia --project=docs --color=yes docs/make.jl
```
The current instructions from the Development section of the docs says to use
```
julia --project=docs -e 'using Pkg; Pkg.instantiate(); include("docs/make.jl")'
```
This indeed works, but it build the docs for the current stable release of Trixi and not for the local development changes.
We should update the instructions on building the docs locally such that it is clear for people with forks how to get their docs to build. | non_priority | update instructions to build docs locally developing trixi on a fork may include adding types function with corresponding docstrings previewing the documentation from a fork online is not available for security reasons to preview the docs with your local documentation changes and updates one needs to use the following commands taken directly from julia project docs e using pkg pkg develop packagespec path pwd pkg instantiate julia project docs color yes docs make jl the current instructions from the development section of the docs says to use julia project docs e using pkg pkg instantiate include docs make jl this indeed works but it build the docs for the current stable release of trixi and not for the local development changes we should update the instructions on building the docs locally such that it is clear for people with forks how to get their docs to build | 0 |
49,736 | 26,280,927,535 | IssuesEvent | 2023-01-07 09:35:19 | python/cpython | https://api.github.com/repos/python/cpython | opened | Make `copy.deepcopy` faster for `slice` objects | type-feature performance | ## `slice`
Right now `slice` objects are deepcopied using `__reduce__` defined as:
https://github.com/python/cpython/blob/26ff43625ed7bf09542ad8f149cb6af710b41e15/Objects/sliceobject.c#L559-L563
It is one of last branches of `deepcopy` logic:
https://github.com/python/cpython/blob/26ff43625ed7bf09542ad8f149cb6af710b41e15/Lib/copy.py#L120-L157
But, since `slice` is an immutable type, we can optimize its `deepcopy` as:
```python
d[slice] = _deepcopy_atomic
```
Before:
```
» pyperf timeit --setup 'from copy import deepcopy; s = slice(1,10,2)' 'deepcopy(s)'
.....................
Mean +- std dev: 3.46 us +- 0.18 us
```
After:
```
» pyperf timeit --setup 'from copy import deepcopy; s = slice(1,10,2)' 'deepcopy(s)'
.....................
Mean +- std dev: 277 ns +- 3 ns
```
Looks like a good speedup for just a single line!
Noticed while working on #100815
PR is incoming. | True | Make `copy.deepcopy` faster for `slice` objects - ## `slice`
Right now `slice` objects are deepcopied using `__reduce__` defined as:
https://github.com/python/cpython/blob/26ff43625ed7bf09542ad8f149cb6af710b41e15/Objects/sliceobject.c#L559-L563
It is one of last branches of `deepcopy` logic:
https://github.com/python/cpython/blob/26ff43625ed7bf09542ad8f149cb6af710b41e15/Lib/copy.py#L120-L157
But, since `slice` is an immutable type, we can optimize its `deepcopy` as:
```python
d[slice] = _deepcopy_atomic
```
Before:
```
» pyperf timeit --setup 'from copy import deepcopy; s = slice(1,10,2)' 'deepcopy(s)'
.....................
Mean +- std dev: 3.46 us +- 0.18 us
```
After:
```
» pyperf timeit --setup 'from copy import deepcopy; s = slice(1,10,2)' 'deepcopy(s)'
.....................
Mean +- std dev: 277 ns +- 3 ns
```
Looks like a good speedup for just a single line!
Noticed while working on #100815
PR is incoming. | non_priority | make copy deepcopy faster for slice objects slice right now slice objects are deepcopied using reduce defined as it is one of last branches of deepcopy logic but since slice is an immutable type we can optimize its deepcopy as python d deepcopy atomic before » pyperf timeit setup from copy import deepcopy s slice deepcopy s mean std dev us us after » pyperf timeit setup from copy import deepcopy s slice deepcopy s mean std dev ns ns looks like a good speedup for just a single line noticed while working on pr is incoming | 0 |
708,992 | 24,364,446,397 | IssuesEvent | 2022-10-03 14:11:34 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.google.com - site is not usable | priority-critical browser-focus-geckoview engine-gecko | <!-- @browser: Firefox Mobile 105.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 12; Mobile; rv:105.0) Gecko/105.0 Firefox/105.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/111744 -->
<!-- @extra_labels: browser-focus-geckoview -->
**URL**: https://www.google.com/search?q=trustpilot%20reviews&ie=utf-8&oe=utf-8&client=firefox-b-m
**Browser / Version**: Firefox Mobile 105.0
**Operating System**: Android 12
**Tested Another Browser**: No
**Problem type**: Site is not usable
**Description**: Page not loading correctly
**Steps to Reproduce**:
Screen goes black and only refreshes black also tried on android Google
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2022/10/2d17e635-ba72-4e75-8d38-4adb4c8a88a8.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20220915150737</li><li>channel: release</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2022/10/5eacd54b-8992-45f9-b06d-9b5bfafa9845)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.google.com - site is not usable - <!-- @browser: Firefox Mobile 105.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 12; Mobile; rv:105.0) Gecko/105.0 Firefox/105.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/111744 -->
<!-- @extra_labels: browser-focus-geckoview -->
**URL**: https://www.google.com/search?q=trustpilot%20reviews&ie=utf-8&oe=utf-8&client=firefox-b-m
**Browser / Version**: Firefox Mobile 105.0
**Operating System**: Android 12
**Tested Another Browser**: No
**Problem type**: Site is not usable
**Description**: Page not loading correctly
**Steps to Reproduce**:
Screen goes black and only refreshes black also tried on android Google
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2022/10/2d17e635-ba72-4e75-8d38-4adb4c8a88a8.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20220915150737</li><li>channel: release</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2022/10/5eacd54b-8992-45f9-b06d-9b5bfafa9845)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | site is not usable url browser version firefox mobile operating system android tested another browser no problem type site is not usable description page not loading correctly steps to reproduce screen goes black and only refreshes black also tried on android google view the screenshot img alt screenshot src browser configuration gfx webrender all false gfx webrender blob images true gfx webrender enabled false image mem shared true buildid channel release hastouchscreen true mixed active content blocked false mixed passive content blocked false tracking content blocked false from with ❤️ | 1 |
58,303 | 14,359,635,449 | IssuesEvent | 2020-11-30 15:51:55 | acxz/pkgbuilds | https://api.github.com/repos/acxz/pkgbuilds | closed | [openvsp] Missing unzip | build error | ```
==> Entering fakeroot environment...
==> Starting package()...
/startdir/PKGBUILD: line 74: unzip: command not found
==> ERROR: A failure occurred in package().
Aborting...
``` | 1.0 | [openvsp] Missing unzip - ```
==> Entering fakeroot environment...
==> Starting package()...
/startdir/PKGBUILD: line 74: unzip: command not found
==> ERROR: A failure occurred in package().
Aborting...
``` | non_priority | missing unzip entering fakeroot environment starting package startdir pkgbuild line unzip command not found error a failure occurred in package aborting | 0 |
102,867 | 4,161,915,420 | IssuesEvent | 2016-06-17 18:20:32 | ReactiveX/rxjs | https://api.github.com/repos/ReactiveX/rxjs | closed | A method Rx.Observable.when | priority: low status: PRs welcome | Hi all! Exists in plan implementing methods like `Rx.Observable.when` and `Rx.Observable.update`? | 1.0 | A method Rx.Observable.when - Hi all! Exists in plan implementing methods like `Rx.Observable.when` and `Rx.Observable.update`? | priority | a method rx observable when hi all exists in plan implementing methods like rx observable when and rx observable update | 1 |
275,677 | 8,578,773,271 | IssuesEvent | 2018-11-13 06:46:33 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.instagram.com - see bug description | browser-firefox-mobile priority-critical | <!-- @browser: Firefox Mobile 65.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.1.0; Mobile; rv:65.0) Gecko/65.0 Firefox/65.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://www.instagram.com/
**Browser / Version**: Firefox Mobile 65.0
**Operating System**: Android 8.1.0
**Tested Another Browser**: Yes
**Problem type**: Something else
**Description**: Scrolling does not work as it should
**Steps to Reproduce**:
While scrolling the page, (although it is loaded) the images do not load instantly as on chrome
[](https://webcompat.com/uploads/2018/11/3159839f-628c-4ebc-b854-420761c0dd7c.jpg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.instagram.com - see bug description - <!-- @browser: Firefox Mobile 65.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.1.0; Mobile; rv:65.0) Gecko/65.0 Firefox/65.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://www.instagram.com/
**Browser / Version**: Firefox Mobile 65.0
**Operating System**: Android 8.1.0
**Tested Another Browser**: Yes
**Problem type**: Something else
**Description**: Scrolling does not work as it should
**Steps to Reproduce**:
While scrolling the page, (although it is loaded) the images do not load instantly as on chrome
[](https://webcompat.com/uploads/2018/11/3159839f-628c-4ebc-b854-420761c0dd7c.jpg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | see bug description url browser version firefox mobile operating system android tested another browser yes problem type something else description scrolling does not work as it should steps to reproduce while scrolling the page although it is loaded the images do not load instantly as on chrome browser configuration none from with ❤️ | 1 |
802,126 | 28,718,311,306 | IssuesEvent | 2023-04-28 00:04:28 | LiskHQ/lisk-desktop | https://api.github.com/repos/LiskHQ/lisk-desktop | opened | Inaccessible hardware wallet accounts stored in account list | type: bug priority: medium domain: hardware-wallet | ### Expected behavior
Previous selected and unintialized hardware wallet accounts should be removed from the account list after hardware wallet is disconnected
### Actual behavior
Both previously selected and uninitialized hardware wallet accounts remain in account list after hardware wallet is disconnected
### Steps to reproduce
- Connect hardware wallet
- Select "Switch account" from the account dropdown in the top bar
- Select a hardware wallet account
- Disconnect hardware wallet
- Open the switch account modal to see the list of accounts
### Which version(s) does this affect? (Environment, OS, etc...)
All | 1.0 | Inaccessible hardware wallet accounts stored in account list - ### Expected behavior
Previous selected and unintialized hardware wallet accounts should be removed from the account list after hardware wallet is disconnected
### Actual behavior
Both previously selected and uninitialized hardware wallet accounts remain in account list after hardware wallet is disconnected
### Steps to reproduce
- Connect hardware wallet
- Select "Switch account" from the account dropdown in the top bar
- Select a hardware wallet account
- Disconnect hardware wallet
- Open the switch account modal to see the list of accounts
### Which version(s) does this affect? (Environment, OS, etc...)
All | priority | inaccessible hardware wallet accounts stored in account list expected behavior previous selected and unintialized hardware wallet accounts should be removed from the account list after hardware wallet is disconnected actual behavior both previously selected and uninitialized hardware wallet accounts remain in account list after hardware wallet is disconnected steps to reproduce connect hardware wallet select switch account from the account dropdown in the top bar select a hardware wallet account disconnect hardware wallet open the switch account modal to see the list of accounts which version s does this affect environment os etc all | 1 |
104,619 | 16,619,403,257 | IssuesEvent | 2021-06-02 21:30:33 | MythicDrops/MythicDrops | https://api.github.com/repos/MythicDrops/MythicDrops | closed | CVE-2021-27290 (High) detected in ssri-6.0.1.tgz - autoclosed | security vulnerability | ## CVE-2021-27290 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ssri-6.0.1.tgz</b></p></summary>
<p>Standard Subresource Integrity library -- parses, serializes, generates, and verifies integrity metadata according to the SRI spec.</p>
<p>Library home page: <a href="https://registry.npmjs.org/ssri/-/ssri-6.0.1.tgz">https://registry.npmjs.org/ssri/-/ssri-6.0.1.tgz</a></p>
<p>Path to dependency file: MythicDrops/website/package.json</p>
<p>Path to vulnerable library: MythicDrops/website/node_modules/webpack/node_modules/ssri/package.json,MythicDrops/node_modules/npm/node_modules/ssri/package.json</p>
<p>
Dependency Hierarchy:
- semantic-release-17.4.2.tgz (Root Library)
- npm-7.0.10.tgz
- npm-6.14.11.tgz
- :x: **ssri-6.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/MythicDrops/MythicDrops/commit/4c7d8c28d6a410c580066f64b82d37dd7bc9a302">4c7d8c28d6a410c580066f64b82d37dd7bc9a302</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
ssri 5.2.2-8.0.0, fixed in 8.0.1, processes SRIs using a regular expression which is vulnerable to a denial of service. Malicious SRIs could take an extremely long time to process, leading to denial of service. This issue only affects consumers using the strict option.
<p>Publish Date: 2021-03-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-27290>CVE-2021-27290</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27290">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27290</a></p>
<p>Release Date: 2021-03-12</p>
<p>Fix Resolution: ssri - 6.0.2,8.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-27290 (High) detected in ssri-6.0.1.tgz - autoclosed - ## CVE-2021-27290 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ssri-6.0.1.tgz</b></p></summary>
<p>Standard Subresource Integrity library -- parses, serializes, generates, and verifies integrity metadata according to the SRI spec.</p>
<p>Library home page: <a href="https://registry.npmjs.org/ssri/-/ssri-6.0.1.tgz">https://registry.npmjs.org/ssri/-/ssri-6.0.1.tgz</a></p>
<p>Path to dependency file: MythicDrops/website/package.json</p>
<p>Path to vulnerable library: MythicDrops/website/node_modules/webpack/node_modules/ssri/package.json,MythicDrops/node_modules/npm/node_modules/ssri/package.json</p>
<p>
Dependency Hierarchy:
- semantic-release-17.4.2.tgz (Root Library)
- npm-7.0.10.tgz
- npm-6.14.11.tgz
- :x: **ssri-6.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/MythicDrops/MythicDrops/commit/4c7d8c28d6a410c580066f64b82d37dd7bc9a302">4c7d8c28d6a410c580066f64b82d37dd7bc9a302</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
ssri 5.2.2-8.0.0, fixed in 8.0.1, processes SRIs using a regular expression which is vulnerable to a denial of service. Malicious SRIs could take an extremely long time to process, leading to denial of service. This issue only affects consumers using the strict option.
<p>Publish Date: 2021-03-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-27290>CVE-2021-27290</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27290">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27290</a></p>
<p>Release Date: 2021-03-12</p>
<p>Fix Resolution: ssri - 6.0.2,8.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in ssri tgz autoclosed cve high severity vulnerability vulnerable library ssri tgz standard subresource integrity library parses serializes generates and verifies integrity metadata according to the sri spec library home page a href path to dependency file mythicdrops website package json path to vulnerable library mythicdrops website node modules webpack node modules ssri package json mythicdrops node modules npm node modules ssri package json dependency hierarchy semantic release tgz root library npm tgz npm tgz x ssri tgz vulnerable library found in head commit a href found in base branch main vulnerability details ssri fixed in processes sris using a regular expression which is vulnerable to a denial of service malicious sris could take an extremely long time to process leading to denial of service this issue only affects consumers using the strict option publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution ssri step up your open source security game with whitesource | 0 |
72,288 | 9,562,589,768 | IssuesEvent | 2019-05-04 10:32:41 | openscript/beefindr | https://api.github.com/repos/openscript/beefindr | closed | Risikoanalyse | documentation | # Ziel
Schutzbedarf und Risikoanalyse erstellen (die Excel Vorlagen verwenden)
# Auftrag
- [x] Schutzbedarf und Risikoanalyse erstellen (die Excel Vorlagen verwenden)
https://www.isb.admin.ch/isb/de/home/ikt-vorgaben/prozesse-methoden/p041-schutzbedarfsanalyse_schuban.html
https://www.isb.admin.ch/isb/de/home/ikt-vorgaben/prozesse-methoden/p042-informationssicherheits-und-datenschutzkonzept_ISDS.html
- [x] Auswahl der geeigneten Schutzmassnahmen
- [x] Konfigurieren der Massnahmen für den Service und das GUI umsetzen und testen
- [x] Dokumentation für den Schlussbericht erstellen
- [x] **Die 2 Top Risiken und 2 wichtigsten Massnahmen im Modulforum mit den anderen Gruppen teilen und gegenseitig kommentieren.** | 1.0 | Risikoanalyse - # Ziel
Schutzbedarf und Risikoanalyse erstellen (die Excel Vorlagen verwenden)
# Auftrag
- [x] Schutzbedarf und Risikoanalyse erstellen (die Excel Vorlagen verwenden)
https://www.isb.admin.ch/isb/de/home/ikt-vorgaben/prozesse-methoden/p041-schutzbedarfsanalyse_schuban.html
https://www.isb.admin.ch/isb/de/home/ikt-vorgaben/prozesse-methoden/p042-informationssicherheits-und-datenschutzkonzept_ISDS.html
- [x] Auswahl der geeigneten Schutzmassnahmen
- [x] Konfigurieren der Massnahmen für den Service und das GUI umsetzen und testen
- [x] Dokumentation für den Schlussbericht erstellen
- [x] **Die 2 Top Risiken und 2 wichtigsten Massnahmen im Modulforum mit den anderen Gruppen teilen und gegenseitig kommentieren.** | non_priority | risikoanalyse ziel schutzbedarf und risikoanalyse erstellen die excel vorlagen verwenden auftrag schutzbedarf und risikoanalyse erstellen die excel vorlagen verwenden auswahl der geeigneten schutzmassnahmen konfigurieren der massnahmen für den service und das gui umsetzen und testen dokumentation für den schlussbericht erstellen die top risiken und wichtigsten massnahmen im modulforum mit den anderen gruppen teilen und gegenseitig kommentieren | 0 |
176,925 | 21,464,438,422 | IssuesEvent | 2022-04-26 01:09:20 | alexcorvi/apexo | https://api.github.com/repos/alexcorvi/apexo | closed | CVE-2020-7789 (Medium) detected in node-notifier-5.4.3.tgz - autoclosed | security vulnerability | ## CVE-2020-7789 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-notifier-5.4.3.tgz</b></p></summary>
<p>A Node.js module for sending notifications on native Mac, Windows (post and pre 8) and Linux (or Growl as fallback)</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-notifier/-/node-notifier-5.4.3.tgz">https://registry.npmjs.org/node-notifier/-/node-notifier-5.4.3.tgz</a></p>
<p>Path to dependency file: apexo/package.json</p>
<p>Path to vulnerable library: apexo/node_modules/node-notifier/package.json</p>
<p>
Dependency Hierarchy:
- jest-24.9.0.tgz (Root Library)
- jest-cli-24.9.0.tgz
- core-24.9.0.tgz
- reporters-24.9.0.tgz
- :x: **node-notifier-5.4.3.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/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
This affects the package node-notifier before 9.0.0. It allows an attacker to run arbitrary commands on Linux machines due to the options params not being sanitised when being passed an array.
<p>Publish Date: 2020-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7789>CVE-2020-7789</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7789">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7789</a></p>
<p>Release Date: 2020-12-11</p>
<p>Fix Resolution: 9.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-7789 (Medium) detected in node-notifier-5.4.3.tgz - autoclosed - ## CVE-2020-7789 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-notifier-5.4.3.tgz</b></p></summary>
<p>A Node.js module for sending notifications on native Mac, Windows (post and pre 8) and Linux (or Growl as fallback)</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-notifier/-/node-notifier-5.4.3.tgz">https://registry.npmjs.org/node-notifier/-/node-notifier-5.4.3.tgz</a></p>
<p>Path to dependency file: apexo/package.json</p>
<p>Path to vulnerable library: apexo/node_modules/node-notifier/package.json</p>
<p>
Dependency Hierarchy:
- jest-24.9.0.tgz (Root Library)
- jest-cli-24.9.0.tgz
- core-24.9.0.tgz
- reporters-24.9.0.tgz
- :x: **node-notifier-5.4.3.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/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
This affects the package node-notifier before 9.0.0. It allows an attacker to run arbitrary commands on Linux machines due to the options params not being sanitised when being passed an array.
<p>Publish Date: 2020-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7789>CVE-2020-7789</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7789">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7789</a></p>
<p>Release Date: 2020-12-11</p>
<p>Fix Resolution: 9.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in node notifier tgz autoclosed cve medium severity vulnerability vulnerable library node notifier tgz a node js module for sending notifications on native mac windows post and pre and linux or growl as fallback library home page a href path to dependency file apexo package json path to vulnerable library apexo node modules node notifier package json dependency hierarchy jest tgz root library jest cli tgz core tgz reporters tgz x node notifier tgz vulnerable library found in base branch master vulnerability details this affects the package node notifier before it allows an attacker to run arbitrary commands on linux machines due to the options params not being sanitised when being passed an array publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
374,175 | 26,103,747,599 | IssuesEvent | 2022-12-27 10:29:36 | WorldHealthOrganization/open-source-communication-channel | https://api.github.com/repos/WorldHealthOrganization/open-source-communication-channel | closed | Update projects on README | documentation | Update README file to include Step-by-step and Em Care to list of projects and project points of contact. | 1.0 | Update projects on README - Update README file to include Step-by-step and Em Care to list of projects and project points of contact. | non_priority | update projects on readme update readme file to include step by step and em care to list of projects and project points of contact | 0 |
425 | 2,496,666,619 | IssuesEvent | 2015-01-06 21:18:39 | cytoscape/cytoscape.js | https://api.github.com/repos/cytoscape/cytoscape.js | opened | Private renderer.renderTo() motionblur conflict | 1-high-priority bug renderer | Seems to be timeout related, as the forced context case should not affect the main rendering logic. | 1.0 | Private renderer.renderTo() motionblur conflict - Seems to be timeout related, as the forced context case should not affect the main rendering logic. | priority | private renderer renderto motionblur conflict seems to be timeout related as the forced context case should not affect the main rendering logic | 1 |
242,163 | 20,201,516,548 | IssuesEvent | 2022-02-11 15:41:40 | ubtue/DatenProbleme | https://api.github.com/repos/ubtue/DatenProbleme | reopened | ISSN 2513-1389 | Zeitschrift für christlich-jüdische Begegnung im Kontext | Seitenangabe | ready for testing Zotero_SEMI-AUTO | **URL**
https://zfbeg.org/ojs/index.php/cjbk/issue/view/28
**Import-Translator**
ubtue_Open Journal Systems Standard.js
(Einzel- und Mehrfach-Import)
**Problembeschreibung**
Bei der Seitenangabe wird der Ausdruck "S." mit importiert sowie am Ende ein Punkt-Zeichen, was dann zum gleichen Export führt. Korrekte Angabe ist ohne "S." und Punkt am Ende und einfach nur die arabische Ziffer.
| 1.0 | ISSN 2513-1389 | Zeitschrift für christlich-jüdische Begegnung im Kontext | Seitenangabe - **URL**
https://zfbeg.org/ojs/index.php/cjbk/issue/view/28
**Import-Translator**
ubtue_Open Journal Systems Standard.js
(Einzel- und Mehrfach-Import)
**Problembeschreibung**
Bei der Seitenangabe wird der Ausdruck "S." mit importiert sowie am Ende ein Punkt-Zeichen, was dann zum gleichen Export führt. Korrekte Angabe ist ohne "S." und Punkt am Ende und einfach nur die arabische Ziffer.
| non_priority | issn zeitschrift für christlich jüdische begegnung im kontext seitenangabe url import translator ubtue open journal systems standard js einzel und mehrfach import problembeschreibung bei der seitenangabe wird der ausdruck s mit importiert sowie am ende ein punkt zeichen was dann zum gleichen export führt korrekte angabe ist ohne s und punkt am ende und einfach nur die arabische ziffer | 0 |
339,905 | 10,264,130,306 | IssuesEvent | 2019-08-22 15:41:33 | medic/medic-conf | https://api.github.com/repos/medic/medic-conf | closed | Declarative Configuration - Ability to control which contact is associated with emitted task | Priority: 1 - High enhancement | Tasks which are emitted by app_settings configuration contain a contact attribute which controls which contact is associated with the task. In the declarative configuration system, the contact associated with the task is the owner of the report that generated the task. [Here](https://github.com/medic/medic-conf/blob/master/src/nools/lib.js#L142)
For Muso's mRDT supervisor workflows, we need to generate tasks for supervisors which are based on the content of reports owned by patients.
More details contained in: https://github.com/medic/medic-projects/issues/6519 | 1.0 | Declarative Configuration - Ability to control which contact is associated with emitted task - Tasks which are emitted by app_settings configuration contain a contact attribute which controls which contact is associated with the task. In the declarative configuration system, the contact associated with the task is the owner of the report that generated the task. [Here](https://github.com/medic/medic-conf/blob/master/src/nools/lib.js#L142)
For Muso's mRDT supervisor workflows, we need to generate tasks for supervisors which are based on the content of reports owned by patients.
More details contained in: https://github.com/medic/medic-projects/issues/6519 | priority | declarative configuration ability to control which contact is associated with emitted task tasks which are emitted by app settings configuration contain a contact attribute which controls which contact is associated with the task in the declarative configuration system the contact associated with the task is the owner of the report that generated the task for muso s mrdt supervisor workflows we need to generate tasks for supervisors which are based on the content of reports owned by patients more details contained in | 1 |
92,591 | 10,758,944,835 | IssuesEvent | 2019-10-31 15:47:43 | microsoft/PowerToys | https://api.github.com/repos/microsoft/PowerToys | closed | PowerRename - capturing and using regex parts | PowerRename documentation | I wanted to check if capturing and using regex parts is possible - I'm used to this from Visual Studio and Notepad++. Found it by accident, it should be documented.
Capturing a part can be done like "(...)", using the captured values in the replace can be done with "$1"..."$n".
This is very useful and should be added to the documentation. | 1.0 | PowerRename - capturing and using regex parts - I wanted to check if capturing and using regex parts is possible - I'm used to this from Visual Studio and Notepad++. Found it by accident, it should be documented.
Capturing a part can be done like "(...)", using the captured values in the replace can be done with "$1"..."$n".
This is very useful and should be added to the documentation. | non_priority | powerrename capturing and using regex parts i wanted to check if capturing and using regex parts is possible i m used to this from visual studio and notepad found it by accident it should be documented capturing a part can be done like using the captured values in the replace can be done with n this is very useful and should be added to the documentation | 0 |
27,272 | 4,049,144,372 | IssuesEvent | 2016-05-23 13:13:30 | duckduckgo/community-platform | https://api.github.com/repos/duckduckgo/community-platform | closed | An idea to make it quicker to delete spam | Design Forum | The spam has been heavy lately. That and the fact that my laptop has a small screen has forced to scoll up and down tons of times to be able click the "Leave invisible" button, whenever there was a difference in the length of the content of the spam-post (and thus the height of `div` containing it).
I quickly checked out the CSS, and managed to add the following CSS code:
```CSS
.moderation .notification__comment {
height: 350px;
max-height: 350px;
min-height: 350px;
overflow-y: scroll;
}
```
This makes each `div` containing a spam message in the moderation-section always have an height of 350px. This means the "Leave invisible"-button is in the same place, every time a new spam message "moves up".
Would that be something you would consider adding?
Maybe you could make this option if most people don't want this?
I figured out that the changes should go into `notifications.css`, but I didn't add it as it should include the `.moderation`-part, and I don't know if you want *that* part to go in `notifications.css`.)
In case it can go there I can make a pull request! :) That would be my first one! xD ^_^
Let me know what you think! :) | 1.0 | An idea to make it quicker to delete spam - The spam has been heavy lately. That and the fact that my laptop has a small screen has forced to scoll up and down tons of times to be able click the "Leave invisible" button, whenever there was a difference in the length of the content of the spam-post (and thus the height of `div` containing it).
I quickly checked out the CSS, and managed to add the following CSS code:
```CSS
.moderation .notification__comment {
height: 350px;
max-height: 350px;
min-height: 350px;
overflow-y: scroll;
}
```
This makes each `div` containing a spam message in the moderation-section always have an height of 350px. This means the "Leave invisible"-button is in the same place, every time a new spam message "moves up".
Would that be something you would consider adding?
Maybe you could make this option if most people don't want this?
I figured out that the changes should go into `notifications.css`, but I didn't add it as it should include the `.moderation`-part, and I don't know if you want *that* part to go in `notifications.css`.)
In case it can go there I can make a pull request! :) That would be my first one! xD ^_^
Let me know what you think! :) | non_priority | an idea to make it quicker to delete spam the spam has been heavy lately that and the fact that my laptop has a small screen has forced to scoll up and down tons of times to be able click the leave invisible button whenever there was a difference in the length of the content of the spam post and thus the height of div containing it i quickly checked out the css and managed to add the following css code css moderation notification comment height max height min height overflow y scroll this makes each div containing a spam message in the moderation section always have an height of this means the leave invisible button is in the same place every time a new spam message moves up would that be something you would consider adding maybe you could make this option if most people don t want this i figured out that the changes should go into notifications css but i didn t add it as it should include the moderation part and i don t know if you want that part to go in notifications css in case it can go there i can make a pull request that would be my first one xd let me know what you think | 0 |
809,251 | 30,182,186,142 | IssuesEvent | 2023-07-04 09:36:35 | pendulum-chain/spacewalk | https://api.github.com/repos/pendulum-chain/spacewalk | closed | Support 'confirm' SCP messages in the stellar-relay when proving transaction validity | priority:high | # Problem
With the current implementation, the `stellar-relay` pallet only considers `ScpStatementExternalize` consensus messages to prove the validity of a Stellar transaction. However, we identified that Stellar archive entries usually only contain just **one** externalized message but many other 'ScpStatementConfim` or `ScpStatementPrepare` messages. This means that we currently cannot use archive entries to submit 'execute...' extrinsics, since this one externalized message is not enough.
# Solution
We want to change the validation logic used in the `stellar-relay` pallet to also consider `ScpStatementConfirm` messages. If we combine all 'confirm' and 'externalize' messages contained in archive entries, we should be build valid proofs even when missing the relevant consensus messages when they are emitted on Stellar's overlay network.
The reasoning why we can do this can be found on [this](https://www.notion.so/satoshipay/Archived-SCP-Messages-6801530d58d44f1fba1208db27ddee03#b052bb35b2fa416ea69034c5a2b34ae9) Notion page. For our implementation, we will follow the 'simplified approach' described [here](https://www.notion.so/satoshipay/Archived-SCP-Messages-6801530d58d44f1fba1208db27ddee03?pvs=4#b052bb35b2fa416ea69034c5a2b34ae9).
### Steps
Note: The structure of `ScpStatements` can be found [here](https://stellar-sdk.readthedocs.io/en/stable/api.html#scpstatement). This is relevant for the next steps.
Extend the logic of [this](https://github.com/pendulum-chain/spacewalk/blob/06873f16c4a7ab884e4759d98b7b86c712e0c0ae/pallets/stellar-relay/src/lib.rs#L577-L586) `match` statement:
- [ ] Add a new branch for `ScpStConfirm` pledges. Add logic that is very similar to the check for externalized messages, ie. check that the transaction set hash contained in the `ScpBallot` of the pledge matches the one we expect. **Note** that you might have to slightly adapt the `get_tx_set_hash` function because the names for the ballots differ between 'externalize' and 'confirm' messages (ie. it's either `commit` or `ballot`).
- [ ] Ensure that all statements contained in the envelopes refer to the same `nH` value.
By checking if the transaction set hash contained in the externalized/confirmed ballot matches the expected, we make sure that the consensus messages are related to the same value and the value we are looking for simultaneously. | 1.0 | Support 'confirm' SCP messages in the stellar-relay when proving transaction validity - # Problem
With the current implementation, the `stellar-relay` pallet only considers `ScpStatementExternalize` consensus messages to prove the validity of a Stellar transaction. However, we identified that Stellar archive entries usually only contain just **one** externalized message but many other 'ScpStatementConfim` or `ScpStatementPrepare` messages. This means that we currently cannot use archive entries to submit 'execute...' extrinsics, since this one externalized message is not enough.
# Solution
We want to change the validation logic used in the `stellar-relay` pallet to also consider `ScpStatementConfirm` messages. If we combine all 'confirm' and 'externalize' messages contained in archive entries, we should be build valid proofs even when missing the relevant consensus messages when they are emitted on Stellar's overlay network.
The reasoning why we can do this can be found on [this](https://www.notion.so/satoshipay/Archived-SCP-Messages-6801530d58d44f1fba1208db27ddee03#b052bb35b2fa416ea69034c5a2b34ae9) Notion page. For our implementation, we will follow the 'simplified approach' described [here](https://www.notion.so/satoshipay/Archived-SCP-Messages-6801530d58d44f1fba1208db27ddee03?pvs=4#b052bb35b2fa416ea69034c5a2b34ae9).
### Steps
Note: The structure of `ScpStatements` can be found [here](https://stellar-sdk.readthedocs.io/en/stable/api.html#scpstatement). This is relevant for the next steps.
Extend the logic of [this](https://github.com/pendulum-chain/spacewalk/blob/06873f16c4a7ab884e4759d98b7b86c712e0c0ae/pallets/stellar-relay/src/lib.rs#L577-L586) `match` statement:
- [ ] Add a new branch for `ScpStConfirm` pledges. Add logic that is very similar to the check for externalized messages, ie. check that the transaction set hash contained in the `ScpBallot` of the pledge matches the one we expect. **Note** that you might have to slightly adapt the `get_tx_set_hash` function because the names for the ballots differ between 'externalize' and 'confirm' messages (ie. it's either `commit` or `ballot`).
- [ ] Ensure that all statements contained in the envelopes refer to the same `nH` value.
By checking if the transaction set hash contained in the externalized/confirmed ballot matches the expected, we make sure that the consensus messages are related to the same value and the value we are looking for simultaneously. | priority | support confirm scp messages in the stellar relay when proving transaction validity problem with the current implementation the stellar relay pallet only considers scpstatementexternalize consensus messages to prove the validity of a stellar transaction however we identified that stellar archive entries usually only contain just one externalized message but many other scpstatementconfim or scpstatementprepare messages this means that we currently cannot use archive entries to submit execute extrinsics since this one externalized message is not enough solution we want to change the validation logic used in the stellar relay pallet to also consider scpstatementconfirm messages if we combine all confirm and externalize messages contained in archive entries we should be build valid proofs even when missing the relevant consensus messages when they are emitted on stellar s overlay network the reasoning why we can do this can be found on notion page for our implementation we will follow the simplified approach described steps note the structure of scpstatements can be found this is relevant for the next steps extend the logic of match statement add a new branch for scpstconfirm pledges add logic that is very similar to the check for externalized messages ie check that the transaction set hash contained in the scpballot of the pledge matches the one we expect note that you might have to slightly adapt the get tx set hash function because the names for the ballots differ between externalize and confirm messages ie it s either commit or ballot ensure that all statements contained in the envelopes refer to the same nh value by checking if the transaction set hash contained in the externalized confirmed ballot matches the expected we make sure that the consensus messages are related to the same value and the value we are looking for simultaneously | 1 |
615,974 | 19,287,131,076 | IssuesEvent | 2021-12-11 05:48:53 | Vyxal/Vyxal | https://api.github.com/repos/Vyxal/Vyxal | closed | Mold modifies inputs | bug difficulty: average priority:high | When one of the arguments passed to Mold is input, whether taken implicitly or explicitly, it permanently modifies that input to be whatever the output of the Mold command was.
Examples:
[1 Input](https://vyxal.pythonanywhere.com/#WyIiLCIiLCI/LD8sIMK2LCDin6hcXGF8XFxifFxcY+KfqT8g4oCiID8sPywiLCIiLCJbMSwyLDMsNCw1LDYsNyw4LDldIl0=)
[2 Inputs](https://vyxal.pythonanywhere.com/#WyIiLCIiLCLigKIgwrkswrkswrksIiwiIiwiWzEsMiwzLDQsNSw2LDcsOCw5XVxuWydhJywgJ2InLCAnYyddIl0=) | 1.0 | Mold modifies inputs - When one of the arguments passed to Mold is input, whether taken implicitly or explicitly, it permanently modifies that input to be whatever the output of the Mold command was.
Examples:
[1 Input](https://vyxal.pythonanywhere.com/#WyIiLCIiLCI/LD8sIMK2LCDin6hcXGF8XFxifFxcY+KfqT8g4oCiID8sPywiLCIiLCJbMSwyLDMsNCw1LDYsNyw4LDldIl0=)
[2 Inputs](https://vyxal.pythonanywhere.com/#WyIiLCIiLCLigKIgwrkswrkswrksIiwiIiwiWzEsMiwzLDQsNSw2LDcsOCw5XVxuWydhJywgJ2InLCAnYyddIl0=) | priority | mold modifies inputs when one of the arguments passed to mold is input whether taken implicitly or explicitly it permanently modifies that input to be whatever the output of the mold command was examples | 1 |
582,547 | 17,363,986,114 | IssuesEvent | 2021-07-30 03:06:18 | ReliaQualAssociates/ramstk | https://api.github.com/repos/ReliaQualAssociates/ramstk | closed | Remove do_get_tree() from Hardware Datamanager | priority: normal status: inprogress type: refactor | **Describe the chore that needs to be addressed.**
1. The do_get_tree() method should be deleted.
2. The pub.subscribe should be deleted.
3. _tag attributes needs to be singular.
4. Fix tests that expect _tag to be plural.
5. Fix export and test_export
- [ ] This issue is an epic issue which subsumes the following:
| 1.0 | Remove do_get_tree() from Hardware Datamanager - **Describe the chore that needs to be addressed.**
1. The do_get_tree() method should be deleted.
2. The pub.subscribe should be deleted.
3. _tag attributes needs to be singular.
4. Fix tests that expect _tag to be plural.
5. Fix export and test_export
- [ ] This issue is an epic issue which subsumes the following:
| priority | remove do get tree from hardware datamanager describe the chore that needs to be addressed the do get tree method should be deleted the pub subscribe should be deleted tag attributes needs to be singular fix tests that expect tag to be plural fix export and test export this issue is an epic issue which subsumes the following | 1 |
636,906 | 20,612,641,003 | IssuesEvent | 2022-03-07 10:08:50 | Soulcialize/souldragonknight | https://api.github.com/repos/Soulcialize/souldragonknight | opened | Add stamina and mana system | type.Enhancement priority.Medium | The knight will have stamina while the dragon has mana. These two resources are depleted when attacking and will recharge over time.
This would discourage players from spamming their attacks which would make the enemies too easy to defeat. Players will have to cooperate more closely so that they do not waste stamina/mana on aimless attacks. | 1.0 | Add stamina and mana system - The knight will have stamina while the dragon has mana. These two resources are depleted when attacking and will recharge over time.
This would discourage players from spamming their attacks which would make the enemies too easy to defeat. Players will have to cooperate more closely so that they do not waste stamina/mana on aimless attacks. | priority | add stamina and mana system the knight will have stamina while the dragon has mana these two resources are depleted when attacking and will recharge over time this would discourage players from spamming their attacks which would make the enemies too easy to defeat players will have to cooperate more closely so that they do not waste stamina mana on aimless attacks | 1 |
705,014 | 24,218,361,781 | IssuesEvent | 2022-09-26 08:47:21 | AY2223S1-CS2103T-T12-2/tp | https://api.github.com/repos/AY2223S1-CS2103T-T12-2/tp | closed | Update site-wide settings | type.Task priority.High | ## Tasks
- Follow guide for [Using Jekyll for project documentation @SE-EDU/guides](https://se-education.org/guides/tutorials/jekyll.html)
- The text `AB-3` in `docs\_sass\minima\_base.scss` needs updating (it comes into play when you convert documentation to PDF formats)
[Link](https://nus-cs2103-ay2223s1.github.io/website/schedule/week7/project.html#2-update-project-website-aboutus-readme) to details | 1.0 | Update site-wide settings - ## Tasks
- Follow guide for [Using Jekyll for project documentation @SE-EDU/guides](https://se-education.org/guides/tutorials/jekyll.html)
- The text `AB-3` in `docs\_sass\minima\_base.scss` needs updating (it comes into play when you convert documentation to PDF formats)
[Link](https://nus-cs2103-ay2223s1.github.io/website/schedule/week7/project.html#2-update-project-website-aboutus-readme) to details | priority | update site wide settings tasks follow guide for the text ab in docs sass minima base scss needs updating it comes into play when you convert documentation to pdf formats to details | 1 |
121,511 | 15,954,004,112 | IssuesEvent | 2021-04-15 13:06:48 | department-of-veterans-affairs/vets-design-system-documentation | https://api.github.com/repos/department-of-veterans-affairs/vets-design-system-documentation | closed | Rename action link class to match documented naming convention | vsp-design-system-team | # Bug Report
- [x] I’ve searched for any related issues and avoided creating a duplicate issue.
## Description
The documentation on design.va.gov describes naming conventions for `formation` component classes:
However, our action link component doesn't follow this documentation:
## Context
- [Slack thread](https://dsva.slack.com/archives/CBU0KDSB1/p1617805314484100)
## Acceptance Criteria
- [ ] `formation` is updated to change the action link class name to `vads-c-action-link`
- [ ] `vets-website` is updated to find and replace all instances of the action link
| 1.0 | Rename action link class to match documented naming convention - # Bug Report
- [x] I’ve searched for any related issues and avoided creating a duplicate issue.
## Description
The documentation on design.va.gov describes naming conventions for `formation` component classes:
However, our action link component doesn't follow this documentation:
## Context
- [Slack thread](https://dsva.slack.com/archives/CBU0KDSB1/p1617805314484100)
## Acceptance Criteria
- [ ] `formation` is updated to change the action link class name to `vads-c-action-link`
- [ ] `vets-website` is updated to find and replace all instances of the action link
| non_priority | rename action link class to match documented naming convention bug report i’ve searched for any related issues and avoided creating a duplicate issue description the documentation on design va gov describes naming conventions for formation component classes however our action link component doesn t follow this documentation context acceptance criteria formation is updated to change the action link class name to vads c action link vets website is updated to find and replace all instances of the action link | 0 |
14,303 | 3,822,386,762 | IssuesEvent | 2016-03-30 00:47:30 | iovisor/bcc | https://api.github.com/repos/iovisor/bcc | opened | add /docs/INSTALL-UBUNTU.md | documentation | Targeted at Ubuntu Xenial and beyond. Should work. The docs should also mention that some /tools won't work on the older Xenial 4.4 kernel, and to check under /tools/old for versions that may work.
If you've figured out the install steps, please drop comments here or a pull request. | 1.0 | add /docs/INSTALL-UBUNTU.md - Targeted at Ubuntu Xenial and beyond. Should work. The docs should also mention that some /tools won't work on the older Xenial 4.4 kernel, and to check under /tools/old for versions that may work.
If you've figured out the install steps, please drop comments here or a pull request. | non_priority | add docs install ubuntu md targeted at ubuntu xenial and beyond should work the docs should also mention that some tools won t work on the older xenial kernel and to check under tools old for versions that may work if you ve figured out the install steps please drop comments here or a pull request | 0 |
231,347 | 25,499,126,800 | IssuesEvent | 2022-11-28 01:09:26 | jtimberlake/pacbot | https://api.github.com/repos/jtimberlake/pacbot | opened | CVE-2022-24999 (Medium) detected in multiple libraries | security vulnerability | ## CVE-2022-24999 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>qs-6.5.2.tgz</b>, <b>qs-6.7.0.tgz</b>, <b>qs-6.4.0.tgz</b></p></summary>
<p>
<details><summary><b>qs-6.5.2.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.5.2.tgz">https://registry.npmjs.org/qs/-/qs-6.5.2.tgz</a></p>
<p>Path to dependency file: /webapp/package.json</p>
<p>Path to vulnerable library: /webapp/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.6.8.tgz (Root Library)
- node-sass-4.14.1.tgz
- request-2.88.2.tgz
- :x: **qs-6.5.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-6.7.0.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.7.0.tgz">https://registry.npmjs.org/qs/-/qs-6.7.0.tgz</a></p>
<p>Path to dependency file: /webapp/package.json</p>
<p>Path to vulnerable library: /webapp/node_modules/body-parser/node_modules/qs/package.json,/webapp/node_modules/express/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- karma-4.4.1.tgz (Root Library)
- body-parser-1.19.0.tgz
- :x: **qs-6.7.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-6.4.0.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.4.0.tgz">https://registry.npmjs.org/qs/-/qs-6.4.0.tgz</a></p>
<p>Path to dependency file: /webapp/package.json</p>
<p>Path to vulnerable library: /webapp/node_modules/less/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.6.8.tgz (Root Library)
- less-2.7.3.tgz
- request-2.81.0.tgz
- :x: **qs-6.4.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/jtimberlake/pacbot/commit/5a25dc15882324583860630e773af2e2647dd5fa">5a25dc15882324583860630e773af2e2647dd5fa</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
<p>Publish Date: 2022-11-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-24999>CVE-2022-24999</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>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-24999">https://www.cve.org/CVERecord?id=CVE-2022-24999</a></p>
<p>Release Date: 2022-11-26</p>
<p>Fix Resolution: qs - 6.2.4,6.3.3,6.4.1,6.5.3,6.6.1,6.7.3,6.8.3,6.9.7,6.10.3</p>
</p>
</details>
<p></p>
| True | CVE-2022-24999 (Medium) detected in multiple libraries - ## CVE-2022-24999 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>qs-6.5.2.tgz</b>, <b>qs-6.7.0.tgz</b>, <b>qs-6.4.0.tgz</b></p></summary>
<p>
<details><summary><b>qs-6.5.2.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.5.2.tgz">https://registry.npmjs.org/qs/-/qs-6.5.2.tgz</a></p>
<p>Path to dependency file: /webapp/package.json</p>
<p>Path to vulnerable library: /webapp/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.6.8.tgz (Root Library)
- node-sass-4.14.1.tgz
- request-2.88.2.tgz
- :x: **qs-6.5.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-6.7.0.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.7.0.tgz">https://registry.npmjs.org/qs/-/qs-6.7.0.tgz</a></p>
<p>Path to dependency file: /webapp/package.json</p>
<p>Path to vulnerable library: /webapp/node_modules/body-parser/node_modules/qs/package.json,/webapp/node_modules/express/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- karma-4.4.1.tgz (Root Library)
- body-parser-1.19.0.tgz
- :x: **qs-6.7.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-6.4.0.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.4.0.tgz">https://registry.npmjs.org/qs/-/qs-6.4.0.tgz</a></p>
<p>Path to dependency file: /webapp/package.json</p>
<p>Path to vulnerable library: /webapp/node_modules/less/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.6.8.tgz (Root Library)
- less-2.7.3.tgz
- request-2.81.0.tgz
- :x: **qs-6.4.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/jtimberlake/pacbot/commit/5a25dc15882324583860630e773af2e2647dd5fa">5a25dc15882324583860630e773af2e2647dd5fa</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
<p>Publish Date: 2022-11-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-24999>CVE-2022-24999</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>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-24999">https://www.cve.org/CVERecord?id=CVE-2022-24999</a></p>
<p>Release Date: 2022-11-26</p>
<p>Fix Resolution: qs - 6.2.4,6.3.3,6.4.1,6.5.3,6.6.1,6.7.3,6.8.3,6.9.7,6.10.3</p>
</p>
</details>
<p></p>
| non_priority | cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries qs tgz qs tgz qs tgz qs tgz a querystring parser that supports nesting and arrays with a depth limit library home page a href path to dependency file webapp package json path to vulnerable library webapp node modules qs package json dependency hierarchy cli tgz root library node sass tgz request tgz x qs tgz vulnerable library qs tgz a querystring parser that supports nesting and arrays with a depth limit library home page a href path to dependency file webapp package json path to vulnerable library webapp node modules body parser node modules qs package json webapp node modules express node modules qs package json dependency hierarchy karma tgz root library body parser tgz x qs tgz vulnerable library qs tgz a querystring parser that supports nesting and arrays with a depth limit library home page a href path to dependency file webapp package json path to vulnerable library webapp node modules less node modules qs package json dependency hierarchy cli tgz root library less tgz request tgz x qs tgz vulnerable library found in head commit a href found in base branch master vulnerability details qs before as used in express before and other products allows attackers to cause a node process hang for an express application because an proto key can be used in many typical express use cases an unauthenticated remote attacker can place the attack payload in the query string of the url that is used to visit the application such as a b a a the fix was backported to qs and and therefore express which has deps qs in its release description is not vulnerable 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 origin a href release date fix resolution qs | 0 |
178,314 | 29,668,094,332 | IssuesEvent | 2023-06-11 03:30:55 | calcom/cal.com | https://api.github.com/repos/calcom/cal.com | closed | [CAL-1734] Clarify what Sender ID means in Workflows | 🎨 needs design 🧹 Improvements ⚡ Quick Wins :scroll: Needs Documentation Update Low priority | There's a portion that says "Sender ID" when setting up a workflow when the action is "Send SMS" it may exist for other actions too.
No idea what this Sender ID means or how it is presented for the user. This should be explained with some explainer text below the field.
<sub>From [SyncLinear.com](https://synclinear.com) | [CAL-1734](https://linear.app/calcom/issue/CAL-1734/clarify-what-sender-id-means-in-workflows)</sub> | 1.0 | [CAL-1734] Clarify what Sender ID means in Workflows - There's a portion that says "Sender ID" when setting up a workflow when the action is "Send SMS" it may exist for other actions too.
No idea what this Sender ID means or how it is presented for the user. This should be explained with some explainer text below the field.
<sub>From [SyncLinear.com](https://synclinear.com) | [CAL-1734](https://linear.app/calcom/issue/CAL-1734/clarify-what-sender-id-means-in-workflows)</sub> | non_priority | clarify what sender id means in workflows there s a portion that says sender id when setting up a workflow when the action is send sms it may exist for other actions too no idea what this sender id means or how it is presented for the user this should be explained with some explainer text below the field from | 0 |
333,114 | 10,115,773,708 | IssuesEvent | 2019-07-30 22:56:49 | BuddyForms/BuddyForms | https://api.github.com/repos/BuddyForms/BuddyForms | closed | Endpoints take attached page as edit | High Priorety Priority 1 bug | **Describe the bug**
The form endpoints are broken. If you select Sample page as example as attached page and then visit the form the title and content of sample page are displayed in the form. But it should be empty
**To Reproduce**
Steps to reproduce the behavior:
1. Go to a post form
2. Select a page for edit submissions with a real title and content
3. Click on the View form link in the sidebar
4. Instead of a empty form the attached page is displayed in the form
**Expected behavior**
An empty form to create a new entry should be displayed
**Screenshots**
| 1.0 | Endpoints take attached page as edit - **Describe the bug**
The form endpoints are broken. If you select Sample page as example as attached page and then visit the form the title and content of sample page are displayed in the form. But it should be empty
**To Reproduce**
Steps to reproduce the behavior:
1. Go to a post form
2. Select a page for edit submissions with a real title and content
3. Click on the View form link in the sidebar
4. Instead of a empty form the attached page is displayed in the form
**Expected behavior**
An empty form to create a new entry should be displayed
**Screenshots**
| priority | endpoints take attached page as edit describe the bug the form endpoints are broken if you select sample page as example as attached page and then visit the form the title and content of sample page are displayed in the form but it should be empty to reproduce steps to reproduce the behavior go to a post form select a page for edit submissions with a real title and content click on the view form link in the sidebar instead of a empty form the attached page is displayed in the form expected behavior an empty form to create a new entry should be displayed screenshots | 1 |
288,716 | 8,850,723,855 | IssuesEvent | 2019-01-08 14:03:01 | rathena/rathena | https://api.github.com/repos/rathena/rathena | closed | Unable to restore stack! Double continuation! | component:core mode:prerenewal mode:renewal priority:medium type:bug | <!-- NOTE: Anything within these brackets will be hidden on the preview of the Issue. -->
* **rAthena Hash**: 79766cd99eebbc507c82f1900df60e909e46a23e
<!-- Please specify the rAthena [GitHub hash](https://help.github.com/articles/autolinked-references-and-urls/#commit-shas) on which you encountered this issue.
How to get your GitHub Hash:
1. cd your/rAthena/directory/
2. git rev-parse --short HEAD
3. Copy the resulting hash.
-->
* **Client Date**: 2017-06-14
<!-- Please specify the client date you used. -->
* **Server Mode**: Pre-renewal
<!-- Which mode does your server use: Pre-Renewal or Renewal? -->
* **Description of Issue**:
```
[Warning]: Unable to restore stack! Double continuation!
[Debug]: Previous script (lost):
[Debug]: Source (NPC): FAKE_NPC (invisible/not on a map)
[Debug]: Current script:
[Debug]: Source (NPC): FAKE_NPC (invisible/not on a map)
Program received signal SIGSEGV, Segmentation fault.
0x00005555556b6bed in pop_stack (st=st@entry=0x7fffeca07b54, start=0, end=0)
at script.cpp:3398
3398 struct script_stack* stack = st->stack;
(gdb) bt full
#0 0x00005555556b6bed in pop_stack (st=st@entry=0x7fffeca07b54, start=0,
end=0) at script.cpp:3398
stack = 0x0
data = <optimized out>
i = <optimized out>
__FUNCTION__ = "pop_stack"
#1 0x00005555556b7ab2 in run_func (st=st@entry=0x7fffeca07b54)
at script.cpp:4007
data = <optimized out>
i = <optimized out>
start_sp = <optimized out>
end_sp = <optimized out>
func = 50
#2 0x00005555556bc800 in run_script_main (st=0x7fffeca07b54)
at script.cpp:4270
c = <optimized out>
cmdcount = 655339
gotocount = 2047
sd = <optimized out>
stack = 0x7fffe78ceb1c
#3 0x000055555564b7a8 in npc_scriptcont(map_session_data*, int, bool) ()
No symbol table info available.
#4 0x00005555555d0905 in clif_parse (fd=8) at clif.cpp:20990
cmd = <optimized out>
packet_len = 2
sd = <optimized out>
pnum = 0
cmd2 = 21845
#5 0x00005555555749d5 in main ()
No symbol table info available.
```
This only happens today. after i applied this PR https://github.com/rathena/rathena/pull/3831 which im not sure if its connected.
Edit ---
Yup. reverted back without the PR and everything works fine. | 1.0 | Unable to restore stack! Double continuation! - <!-- NOTE: Anything within these brackets will be hidden on the preview of the Issue. -->
* **rAthena Hash**: 79766cd99eebbc507c82f1900df60e909e46a23e
<!-- Please specify the rAthena [GitHub hash](https://help.github.com/articles/autolinked-references-and-urls/#commit-shas) on which you encountered this issue.
How to get your GitHub Hash:
1. cd your/rAthena/directory/
2. git rev-parse --short HEAD
3. Copy the resulting hash.
-->
* **Client Date**: 2017-06-14
<!-- Please specify the client date you used. -->
* **Server Mode**: Pre-renewal
<!-- Which mode does your server use: Pre-Renewal or Renewal? -->
* **Description of Issue**:
```
[Warning]: Unable to restore stack! Double continuation!
[Debug]: Previous script (lost):
[Debug]: Source (NPC): FAKE_NPC (invisible/not on a map)
[Debug]: Current script:
[Debug]: Source (NPC): FAKE_NPC (invisible/not on a map)
Program received signal SIGSEGV, Segmentation fault.
0x00005555556b6bed in pop_stack (st=st@entry=0x7fffeca07b54, start=0, end=0)
at script.cpp:3398
3398 struct script_stack* stack = st->stack;
(gdb) bt full
#0 0x00005555556b6bed in pop_stack (st=st@entry=0x7fffeca07b54, start=0,
end=0) at script.cpp:3398
stack = 0x0
data = <optimized out>
i = <optimized out>
__FUNCTION__ = "pop_stack"
#1 0x00005555556b7ab2 in run_func (st=st@entry=0x7fffeca07b54)
at script.cpp:4007
data = <optimized out>
i = <optimized out>
start_sp = <optimized out>
end_sp = <optimized out>
func = 50
#2 0x00005555556bc800 in run_script_main (st=0x7fffeca07b54)
at script.cpp:4270
c = <optimized out>
cmdcount = 655339
gotocount = 2047
sd = <optimized out>
stack = 0x7fffe78ceb1c
#3 0x000055555564b7a8 in npc_scriptcont(map_session_data*, int, bool) ()
No symbol table info available.
#4 0x00005555555d0905 in clif_parse (fd=8) at clif.cpp:20990
cmd = <optimized out>
packet_len = 2
sd = <optimized out>
pnum = 0
cmd2 = 21845
#5 0x00005555555749d5 in main ()
No symbol table info available.
```
This only happens today. after i applied this PR https://github.com/rathena/rathena/pull/3831 which im not sure if its connected.
Edit ---
Yup. reverted back without the PR and everything works fine. | priority | unable to restore stack double continuation rathena hash please specify the rathena on which you encountered this issue how to get your github hash cd your rathena directory git rev parse short head copy the resulting hash client date server mode pre renewal description of issue unable to restore stack double continuation previous script lost source npc fake npc invisible not on a map current script source npc fake npc invisible not on a map program received signal sigsegv segmentation fault in pop stack st st entry start end at script cpp struct script stack stack st stack gdb bt full in pop stack st st entry start end at script cpp stack data i function pop stack in run func st st entry at script cpp data i start sp end sp func in run script main st at script cpp c cmdcount gotocount sd stack in npc scriptcont map session data int bool no symbol table info available in clif parse fd at clif cpp cmd packet len sd pnum in main no symbol table info available this only happens today after i applied this pr which im not sure if its connected edit yup reverted back without the pr and everything works fine | 1 |
17,090 | 3,354,268,211 | IssuesEvent | 2015-11-18 11:13:15 | vigour-io/hub | https://api.github.com/repos/vigour-io/hub | closed | [Current Implementation] Region example | new:design | to get an idea what we are using this for , this an example of a region of the mtv app
[] | 1.0 | [Current Implementation] Region example - to get an idea what we are using this for , this an example of a region of the mtv app
[] | non_priority | region example to get an idea what we are using this for this an example of a region of the mtv app | 0 |
51,873 | 3,015,025,053 | IssuesEvent | 2015-07-29 17:33:20 | brharp/hjckrrh | https://api.github.com/repos/brharp/hjckrrh | closed | G13 General Taxonomy results | feature: general (G) priority: high | Please remove the Read More buttons as Titles will link to the content | 1.0 | G13 General Taxonomy results - Please remove the Read More buttons as Titles will link to the content | priority | general taxonomy results please remove the read more buttons as titles will link to the content | 1 |
763,638 | 26,766,353,290 | IssuesEvent | 2023-01-31 10:55:26 | minio/mc | https://api.github.com/repos/minio/mc | closed | Display arn:bucketname under mc replicate ls | community priority: medium | ## Expected behavior
The current display under mc replicate ls displays entire arn value under Destbucket column
## Actual behavior
The Destbucket column should display arn:buckname instead of entire arn value.
## Steps to reproduce the behavior
Set up replication rule for a bucket on an instance.
Run comman mc replicate ls myminio/bucket_name
## mc --version
RELEASE.2022-10-06T01-20-06Z
| 1.0 | Display arn:bucketname under mc replicate ls - ## Expected behavior
The current display under mc replicate ls displays entire arn value under Destbucket column
## Actual behavior
The Destbucket column should display arn:buckname instead of entire arn value.
## Steps to reproduce the behavior
Set up replication rule for a bucket on an instance.
Run comman mc replicate ls myminio/bucket_name
## mc --version
RELEASE.2022-10-06T01-20-06Z
| priority | display arn bucketname under mc replicate ls expected behavior the current display under mc replicate ls displays entire arn value under destbucket column actual behavior the destbucket column should display arn buckname instead of entire arn value steps to reproduce the behavior set up replication rule for a bucket on an instance run comman mc replicate ls myminio bucket name mc version release | 1 |
563,163 | 16,676,991,828 | IssuesEvent | 2021-06-07 17:28:28 | googleapis/java-aiplatform | https://api.github.com/repos/googleapis/java-aiplatform | closed | aiplatform.CreateTrainingPipelineImageObjectDetectionSampleTest: testCreateTrainingPipelineImageObjectDetectionSample failed | api: aiplatform flakybot: flaky flakybot: issue priority: p1 type: bug | Note: #216 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
----
commit: dafca5d9fc1c0d77fc0c3f26c08c6827e53492a3
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/d828fa34-eac2-4ee9-98e4-0f94a6d7d73f), [Sponge](http://sponge2/d828fa34-eac2-4ee9-98e4-0f94a6d7d73f)
status: failed
<details><summary>Test output</summary><br><pre>com.google.api.gax.rpc.FailedPreconditionException: io.grpc.StatusRuntimeException: FAILED_PRECONDITION: The TrainingPipeline "projects/ucaip-sample-tests/locations/us-central1/trainingPipelines/4256609733353406464" is in state PIPELINE_STATE_FAILED and cannot be canceled.
at com.google.api.gax.rpc.ApiExceptionFactory.createException(ApiExceptionFactory.java:59)
at com.google.api.gax.grpc.GrpcApiExceptionFactory.create(GrpcApiExceptionFactory.java:72)
at com.google.api.gax.grpc.GrpcApiExceptionFactory.create(GrpcApiExceptionFactory.java:60)
at com.google.api.gax.grpc.GrpcExceptionCallable$ExceptionTransformingFuture.onFailure(GrpcExceptionCallable.java:97)
at com.google.api.core.ApiFutures$1.onFailure(ApiFutures.java:68)
at com.google.common.util.concurrent.Futures$CallbackListener.run(Futures.java:1041)
at com.google.common.util.concurrent.DirectExecutor.execute(DirectExecutor.java:30)
at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1215)
at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:983)
at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:771)
at io.grpc.stub.ClientCalls$GrpcFuture.setException(ClientCalls.java:563)
at io.grpc.stub.ClientCalls$UnaryStreamToFuture.onClose(ClientCalls.java:533)
at io.grpc.internal.DelayedClientCall$DelayedListener$3.run(DelayedClientCall.java:464)
at io.grpc.internal.DelayedClientCall$DelayedListener.delayOrExecute(DelayedClientCall.java:428)
at io.grpc.internal.DelayedClientCall$DelayedListener.onClose(DelayedClientCall.java:461)
at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:553)
at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:68)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:739)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:718)
at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Suppressed: com.google.api.gax.rpc.AsyncTaskException: Asynchronous task failed
at com.google.api.gax.rpc.ApiExceptions.callAndTranslateApiException(ApiExceptions.java:57)
at com.google.api.gax.rpc.UnaryCallable.call(UnaryCallable.java:112)
at com.google.cloud.aiplatform.v1.PipelineServiceClient.cancelTrainingPipeline(PipelineServiceClient.java:757)
at com.google.cloud.aiplatform.v1.PipelineServiceClient.cancelTrainingPipeline(PipelineServiceClient.java:688)
at aiplatform.CancelTrainingPipelineSample.cancelTrainingPipelineSample(CancelTrainingPipelineSample.java:51)
at aiplatform.CreateTrainingPipelineImageObjectDetectionSampleTest.tearDown(CreateTrainingPipelineImageObjectDetectionSampleTest.java:72)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.junit.internal.runners.statements.RunAfters.invokeMethod(RunAfters.java:46)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
Caused by: io.grpc.StatusRuntimeException: FAILED_PRECONDITION: The TrainingPipeline "projects/ucaip-sample-tests/locations/us-central1/trainingPipelines/4256609733353406464" is in state PIPELINE_STATE_FAILED and cannot be canceled.
at io.grpc.Status.asRuntimeException(Status.java:535)
... 17 more
</pre></details> | 1.0 | aiplatform.CreateTrainingPipelineImageObjectDetectionSampleTest: testCreateTrainingPipelineImageObjectDetectionSample failed - Note: #216 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
----
commit: dafca5d9fc1c0d77fc0c3f26c08c6827e53492a3
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/d828fa34-eac2-4ee9-98e4-0f94a6d7d73f), [Sponge](http://sponge2/d828fa34-eac2-4ee9-98e4-0f94a6d7d73f)
status: failed
<details><summary>Test output</summary><br><pre>com.google.api.gax.rpc.FailedPreconditionException: io.grpc.StatusRuntimeException: FAILED_PRECONDITION: The TrainingPipeline "projects/ucaip-sample-tests/locations/us-central1/trainingPipelines/4256609733353406464" is in state PIPELINE_STATE_FAILED and cannot be canceled.
at com.google.api.gax.rpc.ApiExceptionFactory.createException(ApiExceptionFactory.java:59)
at com.google.api.gax.grpc.GrpcApiExceptionFactory.create(GrpcApiExceptionFactory.java:72)
at com.google.api.gax.grpc.GrpcApiExceptionFactory.create(GrpcApiExceptionFactory.java:60)
at com.google.api.gax.grpc.GrpcExceptionCallable$ExceptionTransformingFuture.onFailure(GrpcExceptionCallable.java:97)
at com.google.api.core.ApiFutures$1.onFailure(ApiFutures.java:68)
at com.google.common.util.concurrent.Futures$CallbackListener.run(Futures.java:1041)
at com.google.common.util.concurrent.DirectExecutor.execute(DirectExecutor.java:30)
at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1215)
at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:983)
at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:771)
at io.grpc.stub.ClientCalls$GrpcFuture.setException(ClientCalls.java:563)
at io.grpc.stub.ClientCalls$UnaryStreamToFuture.onClose(ClientCalls.java:533)
at io.grpc.internal.DelayedClientCall$DelayedListener$3.run(DelayedClientCall.java:464)
at io.grpc.internal.DelayedClientCall$DelayedListener.delayOrExecute(DelayedClientCall.java:428)
at io.grpc.internal.DelayedClientCall$DelayedListener.onClose(DelayedClientCall.java:461)
at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:553)
at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:68)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:739)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:718)
at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Suppressed: com.google.api.gax.rpc.AsyncTaskException: Asynchronous task failed
at com.google.api.gax.rpc.ApiExceptions.callAndTranslateApiException(ApiExceptions.java:57)
at com.google.api.gax.rpc.UnaryCallable.call(UnaryCallable.java:112)
at com.google.cloud.aiplatform.v1.PipelineServiceClient.cancelTrainingPipeline(PipelineServiceClient.java:757)
at com.google.cloud.aiplatform.v1.PipelineServiceClient.cancelTrainingPipeline(PipelineServiceClient.java:688)
at aiplatform.CancelTrainingPipelineSample.cancelTrainingPipelineSample(CancelTrainingPipelineSample.java:51)
at aiplatform.CreateTrainingPipelineImageObjectDetectionSampleTest.tearDown(CreateTrainingPipelineImageObjectDetectionSampleTest.java:72)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.junit.internal.runners.statements.RunAfters.invokeMethod(RunAfters.java:46)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
Caused by: io.grpc.StatusRuntimeException: FAILED_PRECONDITION: The TrainingPipeline "projects/ucaip-sample-tests/locations/us-central1/trainingPipelines/4256609733353406464" is in state PIPELINE_STATE_FAILED and cannot be canceled.
at io.grpc.Status.asRuntimeException(Status.java:535)
... 17 more
</pre></details> | priority | aiplatform createtrainingpipelineimageobjectdetectionsampletest testcreatetrainingpipelineimageobjectdetectionsample failed note was also for this test but it was closed more than days ago so i didn t mark it flaky commit buildurl status failed test output com google api gax rpc failedpreconditionexception io grpc statusruntimeexception failed precondition the trainingpipeline projects ucaip sample tests locations us trainingpipelines is in state pipeline state failed and cannot be canceled at com google api gax rpc apiexceptionfactory createexception apiexceptionfactory java at com google api gax grpc grpcapiexceptionfactory create grpcapiexceptionfactory java at com google api gax grpc grpcapiexceptionfactory create grpcapiexceptionfactory java at com google api gax grpc grpcexceptioncallable exceptiontransformingfuture onfailure grpcexceptioncallable java at com google api core apifutures onfailure apifutures java at com google common util concurrent futures callbacklistener run futures java at com google common util concurrent directexecutor execute directexecutor java at com google common util concurrent abstractfuture executelistener abstractfuture java at com google common util concurrent abstractfuture complete abstractfuture java at com google common util concurrent abstractfuture setexception abstractfuture java at io grpc stub clientcalls grpcfuture setexception clientcalls java at io grpc stub clientcalls unarystreamtofuture onclose clientcalls java at io grpc internal delayedclientcall delayedlistener run delayedclientcall java at io grpc internal delayedclientcall delayedlistener delayorexecute delayedclientcall java at io grpc internal delayedclientcall delayedlistener onclose delayedclientcall java at io grpc internal clientcallimpl closeobserver clientcallimpl java at io grpc internal clientcallimpl access clientcallimpl java at io grpc internal clientcallimpl clientstreamlistenerimpl runinternal clientcallimpl java at io grpc internal clientcallimpl clientstreamlistenerimpl runincontext clientcallimpl java at io grpc internal contextrunnable run contextrunnable java at io grpc internal serializingexecutor run serializingexecutor java at java util concurrent executors runnableadapter call executors java at java util concurrent futuretask run futuretask java at java util concurrent scheduledthreadpoolexecutor scheduledfuturetask access scheduledthreadpoolexecutor java at java util concurrent scheduledthreadpoolexecutor scheduledfuturetask run scheduledthreadpoolexecutor java at java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java lang thread run thread java suppressed com google api gax rpc asynctaskexception asynchronous task failed at com google api gax rpc apiexceptions callandtranslateapiexception apiexceptions java at com google api gax rpc unarycallable call unarycallable java at com google cloud aiplatform pipelineserviceclient canceltrainingpipeline pipelineserviceclient java at com google cloud aiplatform pipelineserviceclient canceltrainingpipeline pipelineserviceclient java at aiplatform canceltrainingpipelinesample canceltrainingpipelinesample canceltrainingpipelinesample java at aiplatform createtrainingpipelineimageobjectdetectionsampletest teardown createtrainingpipelineimageobjectdetectionsampletest java at sun reflect nativemethodaccessorimpl native method at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org junit runners model frameworkmethod runreflectivecall frameworkmethod java at org junit internal runners model reflectivecallable run reflectivecallable java at org junit runners model frameworkmethod invokeexplosively frameworkmethod java at org junit internal runners statements runafters invokemethod runafters java at org junit internal runners statements runafters evaluate runafters java at org junit runners parentrunner evaluate parentrunner java at org junit runners evaluate java at org junit runners parentrunner runleaf parentrunner java at org junit runners runchild java at org junit runners runchild java at org junit runners parentrunner run parentrunner java at org junit runners parentrunner schedule parentrunner java at org junit runners parentrunner runchildren parentrunner java at org junit runners parentrunner access parentrunner java at org junit runners parentrunner evaluate parentrunner java at org junit internal runners statements runbefores evaluate runbefores java at org junit runners parentrunner evaluate parentrunner java at org junit runners parentrunner run parentrunner java at org apache maven surefire execute java at org apache maven surefire executewithrerun java at org apache maven surefire executetestset java at org apache maven surefire invoke java at org apache maven surefire booter forkedbooter runsuitesinprocess forkedbooter java at org apache maven surefire booter forkedbooter execute forkedbooter java at org apache maven surefire booter forkedbooter run forkedbooter java at org apache maven surefire booter forkedbooter main forkedbooter java caused by io grpc statusruntimeexception failed precondition the trainingpipeline projects ucaip sample tests locations us trainingpipelines is in state pipeline state failed and cannot be canceled at io grpc status asruntimeexception status java more | 1 |
73,562 | 7,344,302,423 | IssuesEvent | 2018-03-07 14:18:21 | italia/spid | https://api.github.com/repos/italia/spid | closed | Richiesta di validazione e deploy metadati - Comune di Cilavegna | metadata nuovo md test supporto amministrativo verifica implementazione | Buongiorno,
si richiede la verifica e il deploy dei metadati per conto del Comune di Cilavegna:
```
https://www.suaplomellina.info/simplesaml/module.php/saml/sp/metadata.php/suaplomellina
```
Si tratta di uno Sportello conforme a quelli già precedentemente validati da GLOBO.
Grazie | 1.0 | Richiesta di validazione e deploy metadati - Comune di Cilavegna - Buongiorno,
si richiede la verifica e il deploy dei metadati per conto del Comune di Cilavegna:
```
https://www.suaplomellina.info/simplesaml/module.php/saml/sp/metadata.php/suaplomellina
```
Si tratta di uno Sportello conforme a quelli già precedentemente validati da GLOBO.
Grazie | non_priority | richiesta di validazione e deploy metadati comune di cilavegna buongiorno si richiede la verifica e il deploy dei metadati per conto del comune di cilavegna si tratta di uno sportello conforme a quelli già precedentemente validati da globo grazie | 0 |
798,900 | 28,300,437,617 | IssuesEvent | 2023-04-10 05:18:21 | googleapis/google-cloud-ruby | https://api.github.com/repos/googleapis/google-cloud-ruby | closed | [Nightly CI Failures] Failures detected for google-cloud-bigquery-analytics_hub-v1 | type: bug priority: p1 nightly failure | At 2023-04-09 08:59:15 UTC, detected failures in google-cloud-bigquery-analytics_hub-v1 for: yard
report_key_e2e3dbfae4be82dcbd05632e6618c5d7 | 1.0 | [Nightly CI Failures] Failures detected for google-cloud-bigquery-analytics_hub-v1 - At 2023-04-09 08:59:15 UTC, detected failures in google-cloud-bigquery-analytics_hub-v1 for: yard
report_key_e2e3dbfae4be82dcbd05632e6618c5d7 | priority | failures detected for google cloud bigquery analytics hub at utc detected failures in google cloud bigquery analytics hub for yard report key | 1 |
240,898 | 20,100,616,357 | IssuesEvent | 2022-02-07 03:19:44 | SpenceKonde/ATTinyCore | https://api.github.com/repos/SpenceKonde/ATTinyCore | closed | tinyNeoPixel can be made to not need the menu, I think... | enhancement work complete but untested | The reason we need the menu is that we have to use OUT rather than ST in the event of a zero bit. But we *can* do that with the 2 cycle ST instruction.... it just doesn't leave us with enough spare time to meet the exact timing constraints on the final bit of each byte.
More recent investigations, however, have shown that in reality, the timing timing constraints on both the length of a 1 bit and the length of the inter-bit delay are considerably more generous than the datasheet indicates.
So, as we do now, we pre-calculate whether we shall write the 0 or 1 pattern. Each bit can then start with two consecutive ST instructions (2 clocks each, giving us a 250ns zero - note that by both WS2812B and SK6812 standards, 3 clocks, 375ns, is also a legal zero. The WS2812 datasheet puts it at 200-500ns, the SK6812 at 150-450.
So a zero that is between 200ns and 450ns should always be legal. In other words, 2 or 3 clocks.
And a 1 must be at least 550. Which means we want the ST instruction to be issued on the 5th clock,
And it looks like we also want the 1 bit to go low
And regardless of what point during the ST instruction the pin is actually toggled, I can't imagine it wouldn't be the same point every time ST is called. it doesn't matter, because all ST's are offset by the same amount...
So
ST hi (2 clocks)
ST next (the precalculated value based on next bit, hi or lo) (2 more clocks)
Something taking 1 clock
ST low whether we need it or nor. (2 clocks)
We're now 7 clocks in, We'd ideally like to finish in 10 clocks, but as has been shown, it doesn't actually need to be that short ( https://wp.josh.com/2014/05/13/ws2812-neopixels-are-not-so-finicky-once-you-get-to-know-them/ )
So let's see - how about in that gap we copy lo (or hi), then after the st, we can sbrs (or sbrc), on the next bit, with that controlling what the next bit is. That's 2 more clocks, leaving us with one clock which we.... can't really do much with until the last two bits.., but we can just NOP that cycle away. Finally, on the last two bits things get interesting. Bit 1. Adafruit puts the SBIW there (makes sense) to decrement LED count. That takes an extra clock, so this new implementation would take 11 clocks on the second to last bit. Finally, after that last ST, we can't precalculate the next bit, first we have to load it with ld (2 clocks) - ujp to 9 - and we then do the SBRC/MOV to prep bit 7 bringing us to 11, and the BRNE to get back to the start of the next byte is 2 clocks bringing us to 13.
That means the last bit will be 1682ns total, with the LOW time being 1us instead of our targeted 625us on the final bit, and 750us on the next-to-last bit. But if the site I linked above is accurate, the actual timing constraint there is just that it needs to be less than like 5000ns, which would imply we are in the clear. The penalty would be only a 5% reduction in write speed, (Adafruit's timing was **perfect** - 80 clocks exactly. My proposal adds 1 clock at the next-to-last bit and 3 at the final one.
But I'd wager money it would work.... and everyone is always complaining about how many confusing tools submenus there are, and the menus for that are obnoxious because each part gets a different set of menus, they're not saved alongside the sketch, so you have to think to put in a reminder of what you chose. | 1.0 | tinyNeoPixel can be made to not need the menu, I think... - The reason we need the menu is that we have to use OUT rather than ST in the event of a zero bit. But we *can* do that with the 2 cycle ST instruction.... it just doesn't leave us with enough spare time to meet the exact timing constraints on the final bit of each byte.
More recent investigations, however, have shown that in reality, the timing timing constraints on both the length of a 1 bit and the length of the inter-bit delay are considerably more generous than the datasheet indicates.
So, as we do now, we pre-calculate whether we shall write the 0 or 1 pattern. Each bit can then start with two consecutive ST instructions (2 clocks each, giving us a 250ns zero - note that by both WS2812B and SK6812 standards, 3 clocks, 375ns, is also a legal zero. The WS2812 datasheet puts it at 200-500ns, the SK6812 at 150-450.
So a zero that is between 200ns and 450ns should always be legal. In other words, 2 or 3 clocks.
And a 1 must be at least 550. Which means we want the ST instruction to be issued on the 5th clock,
And it looks like we also want the 1 bit to go low
And regardless of what point during the ST instruction the pin is actually toggled, I can't imagine it wouldn't be the same point every time ST is called. it doesn't matter, because all ST's are offset by the same amount...
So
ST hi (2 clocks)
ST next (the precalculated value based on next bit, hi or lo) (2 more clocks)
Something taking 1 clock
ST low whether we need it or nor. (2 clocks)
We're now 7 clocks in, We'd ideally like to finish in 10 clocks, but as has been shown, it doesn't actually need to be that short ( https://wp.josh.com/2014/05/13/ws2812-neopixels-are-not-so-finicky-once-you-get-to-know-them/ )
So let's see - how about in that gap we copy lo (or hi), then after the st, we can sbrs (or sbrc), on the next bit, with that controlling what the next bit is. That's 2 more clocks, leaving us with one clock which we.... can't really do much with until the last two bits.., but we can just NOP that cycle away. Finally, on the last two bits things get interesting. Bit 1. Adafruit puts the SBIW there (makes sense) to decrement LED count. That takes an extra clock, so this new implementation would take 11 clocks on the second to last bit. Finally, after that last ST, we can't precalculate the next bit, first we have to load it with ld (2 clocks) - ujp to 9 - and we then do the SBRC/MOV to prep bit 7 bringing us to 11, and the BRNE to get back to the start of the next byte is 2 clocks bringing us to 13.
That means the last bit will be 1682ns total, with the LOW time being 1us instead of our targeted 625us on the final bit, and 750us on the next-to-last bit. But if the site I linked above is accurate, the actual timing constraint there is just that it needs to be less than like 5000ns, which would imply we are in the clear. The penalty would be only a 5% reduction in write speed, (Adafruit's timing was **perfect** - 80 clocks exactly. My proposal adds 1 clock at the next-to-last bit and 3 at the final one.
But I'd wager money it would work.... and everyone is always complaining about how many confusing tools submenus there are, and the menus for that are obnoxious because each part gets a different set of menus, they're not saved alongside the sketch, so you have to think to put in a reminder of what you chose. | non_priority | tinyneopixel can be made to not need the menu i think the reason we need the menu is that we have to use out rather than st in the event of a zero bit but we can do that with the cycle st instruction it just doesn t leave us with enough spare time to meet the exact timing constraints on the final bit of each byte more recent investigations however have shown that in reality the timing timing constraints on both the length of a bit and the length of the inter bit delay are considerably more generous than the datasheet indicates so as we do now we pre calculate whether we shall write the or pattern each bit can then start with two consecutive st instructions clocks each giving us a zero note that by both and standards clocks is also a legal zero the datasheet puts it at the at so a zero that is between and should always be legal in other words or clocks and a must be at least which means we want the st instruction to be issued on the clock and it looks like we also want the bit to go low and regardless of what point during the st instruction the pin is actually toggled i can t imagine it wouldn t be the same point every time st is called it doesn t matter because all st s are offset by the same amount so st hi clocks st next the precalculated value based on next bit hi or lo more clocks something taking clock st low whether we need it or nor clocks we re now clocks in we d ideally like to finish in clocks but as has been shown it doesn t actually need to be that short so let s see how about in that gap we copy lo or hi then after the st we can sbrs or sbrc on the next bit with that controlling what the next bit is that s more clocks leaving us with one clock which we can t really do much with until the last two bits but we can just nop that cycle away finally on the last two bits things get interesting bit adafruit puts the sbiw there makes sense to decrement led count that takes an extra clock so this new implementation would take clocks on the second to last bit finally after that last st we can t precalculate the next bit first we have to load it with ld clocks ujp to and we then do the sbrc mov to prep bit bringing us to and the brne to get back to the start of the next byte is clocks bringing us to that means the last bit will be total with the low time being instead of our targeted on the final bit and on the next to last bit but if the site i linked above is accurate the actual timing constraint there is just that it needs to be less than like which would imply we are in the clear the penalty would be only a reduction in write speed adafruit s timing was perfect clocks exactly my proposal adds clock at the next to last bit and at the final one but i d wager money it would work and everyone is always complaining about how many confusing tools submenus there are and the menus for that are obnoxious because each part gets a different set of menus they re not saved alongside the sketch so you have to think to put in a reminder of what you chose | 0 |
796,452 | 28,112,881,588 | IssuesEvent | 2023-03-31 08:35:21 | YangCatalog/backend | https://api.github.com/repos/YangCatalog/backend | closed | Remove unnecessary git clones | Priority: Low maintenance | `pull_local.py`, `openconfigPullLocal.py`, `ietf_push.py` and `iana_push.py` for various reasons all trigger clones of repositories already downloaded in `/var/yang/nonietf`.
Usually the reason is needing an up to date copy of the repository, or needing to add files to the repository without impacting other scripts.
A better alternative to this would be to have one script keeping the repositories up to date (`run_download_github.sh` in module-compilation already does this). Any script that would need a copy of the repo that it can modify and that will not be modified by other scripts could then create it's own git worktree and delete it when it's done. | 1.0 | Remove unnecessary git clones - `pull_local.py`, `openconfigPullLocal.py`, `ietf_push.py` and `iana_push.py` for various reasons all trigger clones of repositories already downloaded in `/var/yang/nonietf`.
Usually the reason is needing an up to date copy of the repository, or needing to add files to the repository without impacting other scripts.
A better alternative to this would be to have one script keeping the repositories up to date (`run_download_github.sh` in module-compilation already does this). Any script that would need a copy of the repo that it can modify and that will not be modified by other scripts could then create it's own git worktree and delete it when it's done. | priority | remove unnecessary git clones pull local py openconfigpulllocal py ietf push py and iana push py for various reasons all trigger clones of repositories already downloaded in var yang nonietf usually the reason is needing an up to date copy of the repository or needing to add files to the repository without impacting other scripts a better alternative to this would be to have one script keeping the repositories up to date run download github sh in module compilation already does this any script that would need a copy of the repo that it can modify and that will not be modified by other scripts could then create it s own git worktree and delete it when it s done | 1 |
25,481 | 7,718,007,930 | IssuesEvent | 2018-05-23 15:07:47 | grafana/grafana | https://api.github.com/repos/grafana/grafana | closed | Publish archives and packages for all platforms to s3 and grafana.com | type: build & packaging | The new crossplatform build supplies archives and packages for linux, windows, darwin, armv7 and arm64. Currently only amd64/linux is published to grafana.com through the normal build pipeline.
- [x] update build pipeline to publish the artifacts
- [ ] update grafana.com to support showing the new artifacts
Related to #11557 | 1.0 | Publish archives and packages for all platforms to s3 and grafana.com - The new crossplatform build supplies archives and packages for linux, windows, darwin, armv7 and arm64. Currently only amd64/linux is published to grafana.com through the normal build pipeline.
- [x] update build pipeline to publish the artifacts
- [ ] update grafana.com to support showing the new artifacts
Related to #11557 | non_priority | publish archives and packages for all platforms to and grafana com the new crossplatform build supplies archives and packages for linux windows darwin and currently only linux is published to grafana com through the normal build pipeline update build pipeline to publish the artifacts update grafana com to support showing the new artifacts related to | 0 |
649,943 | 21,330,710,108 | IssuesEvent | 2022-04-18 07:58:13 | ZapSquared/Quaver | https://api.github.com/repos/ZapSquared/Quaver | closed | Queue command crashes Quaver | type:bug released on @next affects:functionality priority:p0 | **Describe the bug**
What isn't working as intended, and what does it affect?
**Affected versions**
What versions are affected by this bug? (e.g. >=3.0.1, 2.5.1-2.6.3, >=1.2.0)
3.4.0-next.34
**Steps to reproduce**
Steps to reproduce the behavior. (e.g. click on a button, enter a value, etc. and see error)
1. Join a stage or voice channel
2. Play any track with Quaver
3. Use the queue command
**Expected behavior**
What is expected to happen?
Send the queue
**Actual behavior**
What actually happens? Attach or add errors or screenshots here as well.
Crashes immediately.
```js
Ava@DESKTOP-5531PRA MINGW64 ~/Documents/GitHub/Quaver (next)
$ node main.js
2022-04-02T11:10:59.123Z [Discord] INFO: Connected. Logged in as Aia#3990.
2022-04-02T11:10:59.126Z [Quaver] INFO: Running version 3.4.0-next.34. For help,
see https://github.com/ZapSquared/Quaver/issues.
2022-04-02T11:10:59.127Z [Quaver] WARN: You are running an unstable version of Q
uaver. Please report bugs using the link above, and note that features may chang
e or be removed entirely prior to release.
2022-04-02T11:10:59.897Z [Lavalink] INFO: Connected.
2022-04-02T11:11:13.318Z [Quaver] INFO: [G 906471497231630336 | U 25093458962166
5793] Processing command play
2022-04-02T11:11:13.322Z [Quaver] INFO: [G 906471497231630336 | U 25093458962166
5793] Executing command play
2022-04-02T11:11:15.710Z [Quaver] INFO: [G 906471497231630336] Starting track
2022-04-02T11:11:23.168Z [Quaver] INFO: [G 906471497231630336 | U 25093458962166
5793] Processing command queue
2022-04-02T11:11:23.171Z [Quaver] INFO: [G 906471497231630336 | U 25093458962166
5793] Executing command queue
2022-04-02T11:11:23.175Z [Quaver] ERROR: [G 906471497231630336 | U 2509345896216
65793] Encountered error with command queue
2022-04-02T11:11:23.177Z [Quaver] ERROR: Cannot read properties of undefined (re
ading 'additionalEmbeds')
TypeError: Cannot read properties of undefined (reading 'additionalEmbeds')
at ReplyHandler.error (C:\Users\Ava\Documents\GitHub\Quaver\classes\ReplyHan
dler.js:56:20)
at ReplyHandler.localeError (C:\Users\Ava\Documents\GitHub\Quaver\classes\Re
plyHandler.js:90:15)
at Object.execute (C:\Users\Ava\Documents\GitHub\Quaver\commands\queue.js:22
:35)
at Object.execute (C:\Users\Ava\Documents\GitHub\Quaver\events\interactionCr
eate.js:78:19)
at Client.<anonymous> (C:\Users\Ava\Documents\GitHub\Quaver\main.js:162:41)
at Client.emit (node:events:526:28)
at InteractionCreateAction.handle (C:\Users\Ava\Documents\GitHub\Quaver\node
_modules\discord.js\src\client\actions\InteractionCreate.js:74:12)
at Object.module.exports [as INTERACTION_CREATE] (C:\Users\Ava\Documents\Git
Hub\Quaver\node_modules\discord.js\src\client\websocket\handlers\INTERACTION_CRE
ATE.js:4:36)
at WebSocketManager.handlePacket (C:\Users\Ava\Documents\GitHub\Quaver\node_
modules\discord.js\src\client\websocket\WebSocketManager.js:351:31)
at WebSocketShard.onPacket (C:\Users\Ava\Documents\GitHub\Quaver\node_module
s\discord.js\src\client\websocket\WebSocketShard.js:444:22)
2022-04-02T11:11:23.179Z [Quaver] INFO: Shutting down...
2022-04-02T11:11:23.180Z [Quaver] INFO: Disconnecting from all guilds...
2022-04-02T11:11:23.180Z [Quaver] INFO: [G 906471497231630336] Disconnecting (re
starting)
2022-04-02T11:11:23.594Z [Quaver] ERROR: Cannot read properties of undefined (re
ading 'additionalEmbeds')
TypeError: Cannot read properties of undefined (reading 'additionalEmbeds')
at ReplyHandler.error (C:\Users\Ava\Documents\GitHub\Quaver\classes\ReplyHan
dler.js:56:20)
at ReplyHandler.localeError (C:\Users\Ava\Documents\GitHub\Quaver\classes\Re
plyHandler.js:90:15)
at Object.execute (C:\Users\Ava\Documents\GitHub\Quaver\events\interactionCr
eate.js:83:36)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
2022-04-02T11:11:23.595Z [Quaver] INFO: Logging additional output to error.log.
Ava@DESKTOP-5531PRA MINGW64 ~/Documents/GitHub/Quaver (next)
``` | 1.0 | Queue command crashes Quaver - **Describe the bug**
What isn't working as intended, and what does it affect?
**Affected versions**
What versions are affected by this bug? (e.g. >=3.0.1, 2.5.1-2.6.3, >=1.2.0)
3.4.0-next.34
**Steps to reproduce**
Steps to reproduce the behavior. (e.g. click on a button, enter a value, etc. and see error)
1. Join a stage or voice channel
2. Play any track with Quaver
3. Use the queue command
**Expected behavior**
What is expected to happen?
Send the queue
**Actual behavior**
What actually happens? Attach or add errors or screenshots here as well.
Crashes immediately.
```js
Ava@DESKTOP-5531PRA MINGW64 ~/Documents/GitHub/Quaver (next)
$ node main.js
2022-04-02T11:10:59.123Z [Discord] INFO: Connected. Logged in as Aia#3990.
2022-04-02T11:10:59.126Z [Quaver] INFO: Running version 3.4.0-next.34. For help,
see https://github.com/ZapSquared/Quaver/issues.
2022-04-02T11:10:59.127Z [Quaver] WARN: You are running an unstable version of Q
uaver. Please report bugs using the link above, and note that features may chang
e or be removed entirely prior to release.
2022-04-02T11:10:59.897Z [Lavalink] INFO: Connected.
2022-04-02T11:11:13.318Z [Quaver] INFO: [G 906471497231630336 | U 25093458962166
5793] Processing command play
2022-04-02T11:11:13.322Z [Quaver] INFO: [G 906471497231630336 | U 25093458962166
5793] Executing command play
2022-04-02T11:11:15.710Z [Quaver] INFO: [G 906471497231630336] Starting track
2022-04-02T11:11:23.168Z [Quaver] INFO: [G 906471497231630336 | U 25093458962166
5793] Processing command queue
2022-04-02T11:11:23.171Z [Quaver] INFO: [G 906471497231630336 | U 25093458962166
5793] Executing command queue
2022-04-02T11:11:23.175Z [Quaver] ERROR: [G 906471497231630336 | U 2509345896216
65793] Encountered error with command queue
2022-04-02T11:11:23.177Z [Quaver] ERROR: Cannot read properties of undefined (re
ading 'additionalEmbeds')
TypeError: Cannot read properties of undefined (reading 'additionalEmbeds')
at ReplyHandler.error (C:\Users\Ava\Documents\GitHub\Quaver\classes\ReplyHan
dler.js:56:20)
at ReplyHandler.localeError (C:\Users\Ava\Documents\GitHub\Quaver\classes\Re
plyHandler.js:90:15)
at Object.execute (C:\Users\Ava\Documents\GitHub\Quaver\commands\queue.js:22
:35)
at Object.execute (C:\Users\Ava\Documents\GitHub\Quaver\events\interactionCr
eate.js:78:19)
at Client.<anonymous> (C:\Users\Ava\Documents\GitHub\Quaver\main.js:162:41)
at Client.emit (node:events:526:28)
at InteractionCreateAction.handle (C:\Users\Ava\Documents\GitHub\Quaver\node
_modules\discord.js\src\client\actions\InteractionCreate.js:74:12)
at Object.module.exports [as INTERACTION_CREATE] (C:\Users\Ava\Documents\Git
Hub\Quaver\node_modules\discord.js\src\client\websocket\handlers\INTERACTION_CRE
ATE.js:4:36)
at WebSocketManager.handlePacket (C:\Users\Ava\Documents\GitHub\Quaver\node_
modules\discord.js\src\client\websocket\WebSocketManager.js:351:31)
at WebSocketShard.onPacket (C:\Users\Ava\Documents\GitHub\Quaver\node_module
s\discord.js\src\client\websocket\WebSocketShard.js:444:22)
2022-04-02T11:11:23.179Z [Quaver] INFO: Shutting down...
2022-04-02T11:11:23.180Z [Quaver] INFO: Disconnecting from all guilds...
2022-04-02T11:11:23.180Z [Quaver] INFO: [G 906471497231630336] Disconnecting (re
starting)
2022-04-02T11:11:23.594Z [Quaver] ERROR: Cannot read properties of undefined (re
ading 'additionalEmbeds')
TypeError: Cannot read properties of undefined (reading 'additionalEmbeds')
at ReplyHandler.error (C:\Users\Ava\Documents\GitHub\Quaver\classes\ReplyHan
dler.js:56:20)
at ReplyHandler.localeError (C:\Users\Ava\Documents\GitHub\Quaver\classes\Re
plyHandler.js:90:15)
at Object.execute (C:\Users\Ava\Documents\GitHub\Quaver\events\interactionCr
eate.js:83:36)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
2022-04-02T11:11:23.595Z [Quaver] INFO: Logging additional output to error.log.
Ava@DESKTOP-5531PRA MINGW64 ~/Documents/GitHub/Quaver (next)
``` | priority | queue command crashes quaver describe the bug what isn t working as intended and what does it affect affected versions what versions are affected by this bug e g next steps to reproduce steps to reproduce the behavior e g click on a button enter a value etc and see error join a stage or voice channel play any track with quaver use the queue command expected behavior what is expected to happen send the queue actual behavior what actually happens attach or add errors or screenshots here as well crashes immediately js ava desktop documents github quaver next node main js info connected logged in as aia info running version next for help see warn you are running an unstable version of q uaver please report bugs using the link above and note that features may chang e or be removed entirely prior to release info connected info g u processing command play info g u executing command play info starting track info g u processing command queue info g u executing command queue error g u encountered error with command queue error cannot read properties of undefined re ading additionalembeds typeerror cannot read properties of undefined reading additionalembeds at replyhandler error c users ava documents github quaver classes replyhan dler js at replyhandler localeerror c users ava documents github quaver classes re plyhandler js at object execute c users ava documents github quaver commands queue js at object execute c users ava documents github quaver events interactioncr eate js at client c users ava documents github quaver main js at client emit node events at interactioncreateaction handle c users ava documents github quaver node modules discord js src client actions interactioncreate js at object module exports c users ava documents git hub quaver node modules discord js src client websocket handlers interaction cre ate js at websocketmanager handlepacket c users ava documents github quaver node modules discord js src client websocket websocketmanager js at websocketshard onpacket c users ava documents github quaver node module s discord js src client websocket websocketshard js info shutting down info disconnecting from all guilds info disconnecting re starting error cannot read properties of undefined re ading additionalembeds typeerror cannot read properties of undefined reading additionalembeds at replyhandler error c users ava documents github quaver classes replyhan dler js at replyhandler localeerror c users ava documents github quaver classes re plyhandler js at object execute c users ava documents github quaver events interactioncr eate js at processticksandrejections node internal process task queues info logging additional output to error log ava desktop documents github quaver next | 1 |
225,080 | 17,225,366,391 | IssuesEvent | 2021-07-20 00:17:47 | FourierFlows/FourierFlows.jl | https://api.github.com/repos/FourierFlows/FourierFlows.jl | reopened | JOSS todo list | GPU MPI documentation enhancement | This is a proposed list for things we should implement before we announce the code in an open source journal, e.g., JOSS
- [x] GPU
- [x] Full GPU functionality on all modules
- [ ] 3D grid + 3DNavierStokes Module
- [x] Full Docs
- [x] Examples (w/ Literate.jl) that include animations where appropriate
- [ ] Choose 3 problems to demonstrate the code's capabilities (CPU, GPU, MPI).
As a maybes:
- [ ] MPI
- [ ] Field Abstraction; #129
- [ ] use DifferentialEquations.jl for time integration (?)
- [ ] TimeSteppers for NamedTuples (?)
- [ ] AdaptiveTimeStepping (?)
| 1.0 | JOSS todo list - This is a proposed list for things we should implement before we announce the code in an open source journal, e.g., JOSS
- [x] GPU
- [x] Full GPU functionality on all modules
- [ ] 3D grid + 3DNavierStokes Module
- [x] Full Docs
- [x] Examples (w/ Literate.jl) that include animations where appropriate
- [ ] Choose 3 problems to demonstrate the code's capabilities (CPU, GPU, MPI).
As a maybes:
- [ ] MPI
- [ ] Field Abstraction; #129
- [ ] use DifferentialEquations.jl for time integration (?)
- [ ] TimeSteppers for NamedTuples (?)
- [ ] AdaptiveTimeStepping (?)
| non_priority | joss todo list this is a proposed list for things we should implement before we announce the code in an open source journal e g joss gpu full gpu functionality on all modules grid module full docs examples w literate jl that include animations where appropriate choose problems to demonstrate the code s capabilities cpu gpu mpi as a maybes mpi field abstraction use differentialequations jl for time integration timesteppers for namedtuples adaptivetimestepping | 0 |
150,947 | 23,739,079,150 | IssuesEvent | 2022-08-31 10:44:32 | stores-cedcommerce/Lucy-Store-Design | https://api.github.com/repos/stores-cedcommerce/Lucy-Store-Design | opened | The handle needed to be update on the collection page. | Header section Desktop Design / UI / UX | **Actual result:**
The handle needed to be update on the collection page.
https://bellabrina-boutique.myshopify.com/collections/pants-1
https://bellabrina-boutique.myshopify.com/collections/shoes-1
https://bellabrina-boutique.myshopify.com/collections/accessories-1
**Expected result:**
The handle needed to be updated | 1.0 | The handle needed to be update on the collection page. - **Actual result:**
The handle needed to be update on the collection page.
https://bellabrina-boutique.myshopify.com/collections/pants-1
https://bellabrina-boutique.myshopify.com/collections/shoes-1
https://bellabrina-boutique.myshopify.com/collections/accessories-1
**Expected result:**
The handle needed to be updated | non_priority | the handle needed to be update on the collection page actual result the handle needed to be update on the collection page expected result the handle needed to be updated | 0 |
178,108 | 6,599,128,081 | IssuesEvent | 2017-09-16 15:45:50 | zerobias/telegram-mtproto | https://api.github.com/repos/zerobias/telegram-mtproto | opened | Support media DC (or possibly CDNs?) | Priority: High Type: Bug | Can't load avatars from different DC even when `FILE_MIGRATE_x` works because we have different DCs for media content (I think `media_only` thing matters) and for messages. But I'm not sure about this. | 1.0 | Support media DC (or possibly CDNs?) - Can't load avatars from different DC even when `FILE_MIGRATE_x` works because we have different DCs for media content (I think `media_only` thing matters) and for messages. But I'm not sure about this. | priority | support media dc or possibly cdns can t load avatars from different dc even when file migrate x works because we have different dcs for media content i think media only thing matters and for messages but i m not sure about this | 1 |
750,908 | 26,224,426,017 | IssuesEvent | 2023-01-04 17:20:28 | restarone/violet_rails | https://api.github.com/repos/restarone/violet_rails | closed | run error actions (if any) when recaptcha fails | enhancement high priority API - data pipeline v3 | **Is your feature request related to a problem? Please describe.**
Currently we don't fire error actions when recaptcha fails
**Describe the solution you'd like**
fire error actions when recaptcha fails
<img width="1728" alt="Screen Shot 2022-07-30 at 1 21 42 PM" src="https://user-images.githubusercontent.com/35935196/181934704-db882ca1-0684-47cb-9394-790ca846e875.png">
| 1.0 | run error actions (if any) when recaptcha fails - **Is your feature request related to a problem? Please describe.**
Currently we don't fire error actions when recaptcha fails
**Describe the solution you'd like**
fire error actions when recaptcha fails
<img width="1728" alt="Screen Shot 2022-07-30 at 1 21 42 PM" src="https://user-images.githubusercontent.com/35935196/181934704-db882ca1-0684-47cb-9394-790ca846e875.png">
| priority | run error actions if any when recaptcha fails is your feature request related to a problem please describe currently we don t fire error actions when recaptcha fails describe the solution you d like fire error actions when recaptcha fails img width alt screen shot at pm src | 1 |
99,579 | 4,057,023,161 | IssuesEvent | 2016-05-24 20:39:46 | opencaching/okapi | https://api.github.com/repos/opencaching/okapi | closed | User can log cache even if is already banned | bug Priority-Critical | Hi!
There was an issue in oc.pl repo:
https://github.com/opencaching/opencaching-pl/issues/646
How I understand architecture of OKAPI, this have to be solved here. | 1.0 | User can log cache even if is already banned - Hi!
There was an issue in oc.pl repo:
https://github.com/opencaching/opencaching-pl/issues/646
How I understand architecture of OKAPI, this have to be solved here. | priority | user can log cache even if is already banned hi there was an issue in oc pl repo how i understand architecture of okapi this have to be solved here | 1 |
88,701 | 10,577,875,000 | IssuesEvent | 2019-10-07 21:06:38 | mRemoteNG/mRemoteNG | https://api.github.com/repos/mRemoteNG/mRemoteNG | closed | Code style: Place attributes on a separate line | Documentation | In the recent code cleanup, attributes were placed in-line with the code that they decorate. I propose we place attributes on a separate line before the target code that they decorate.
## Current style
```csharp
[Browsable(false)] public RootPuttySessionsNodeInfo RootRootPuttySessionsInfo { get; set; }
```
## Proposed style:
```csharp
[Browsable(false)]
public RootPuttySessionsNodeInfo RootRootPuttySessionsInfo { get; set; }
```
## Justification
Attribute adornments are not critical to the immediate understanding of the code they decorate. It is easier to pick out language keywords (public/readonly/etc) and type information when the definition of a class/property/method is at the start of a line.
In addition, placing attributes in-line with a normal code adds quite a bit of length to that line. This may cause us to add line breaks to the property/method definition that further reduces readability. | 1.0 | Code style: Place attributes on a separate line - In the recent code cleanup, attributes were placed in-line with the code that they decorate. I propose we place attributes on a separate line before the target code that they decorate.
## Current style
```csharp
[Browsable(false)] public RootPuttySessionsNodeInfo RootRootPuttySessionsInfo { get; set; }
```
## Proposed style:
```csharp
[Browsable(false)]
public RootPuttySessionsNodeInfo RootRootPuttySessionsInfo { get; set; }
```
## Justification
Attribute adornments are not critical to the immediate understanding of the code they decorate. It is easier to pick out language keywords (public/readonly/etc) and type information when the definition of a class/property/method is at the start of a line.
In addition, placing attributes in-line with a normal code adds quite a bit of length to that line. This may cause us to add line breaks to the property/method definition that further reduces readability. | non_priority | code style place attributes on a separate line in the recent code cleanup attributes were placed in line with the code that they decorate i propose we place attributes on a separate line before the target code that they decorate current style csharp public rootputtysessionsnodeinfo rootrootputtysessionsinfo get set proposed style csharp public rootputtysessionsnodeinfo rootrootputtysessionsinfo get set justification attribute adornments are not critical to the immediate understanding of the code they decorate it is easier to pick out language keywords public readonly etc and type information when the definition of a class property method is at the start of a line in addition placing attributes in line with a normal code adds quite a bit of length to that line this may cause us to add line breaks to the property method definition that further reduces readability | 0 |
152,374 | 5,846,019,271 | IssuesEvent | 2017-05-10 15:21:06 | vmware/vic | https://api.github.com/repos/vmware/vic | closed | HTML5 Plugin displays wrong port number when using --no-tls | area/ui kind/bug kind/customer-found priority/high | When creating a VCH with the --no-tls option, HTML5 plugin displays wrong port number (2376 instead of 2375). I attached a screenshot.
May 5 2017 13:06:57.777Z INFO ### Installing VCH ####
May 5 2017 13:06:57.778Z INFO vSphere password for administrator@corp.local:
May 5 2017 13:07:01.063Z WARN Using administrative user for VCH operation - use --ops-user to improve security (see -x for advanced help)
May 5 2017 13:07:01.063Z WARN Configuring without TLS - all communications will be insecure
May 5 2017 13:07:01.064Z INFO Loaded registry CA from /etc/docker/certs.d/192.168.100.104/ca.crt
May 5 2017 13:07:01.492Z INFO Validating supplied configuration
May 5 2017 13:07:02.017Z INFO vDS configuration OK on "Bridge01-RegionA01-vDS-COMP"
May 5 2017 13:07:02.118Z INFO Firewall status: ENABLED on "/RegionA01/host/RegionA01-COMP01/esx-01a.corp.local"
May 5 2017 13:07:02.184Z INFO Firewall status: ENABLED on "/RegionA01/host/RegionA01-COMP01/esx-02a.corp.local"
May 5 2017 13:07:02.250Z INFO Firewall status: ENABLED on "/RegionA01/host/RegionA01-COMP01/esx-03a.corp.local"
May 5 2017 13:07:02.272Z INFO Firewall configuration OK on hosts:
May 5 2017 13:07:02.272Z INFO "/RegionA01/host/RegionA01-COMP01/esx-01a.corp.local"
May 5 2017 13:07:02.272Z INFO "/RegionA01/host/RegionA01-COMP01/esx-02a.corp.local"
May 5 2017 13:07:02.273Z INFO "/RegionA01/host/RegionA01-COMP01/esx-03a.corp.local"
May 5 2017 13:07:02.783Z INFO License check OK on hosts:
May 5 2017 13:07:02.783Z INFO "/RegionA01/host/RegionA01-COMP01/esx-01a.corp.local"
May 5 2017 13:07:02.790Z INFO "/RegionA01/host/RegionA01-COMP01/esx-02a.corp.local"
May 5 2017 13:07:02.790Z INFO "/RegionA01/host/RegionA01-COMP01/esx-03a.corp.local"
May 5 2017 13:07:02.801Z INFO DRS check OK on:
May 5 2017 13:07:02.802Z INFO "/RegionA01/host/RegionA01-COMP01"
May 5 2017 13:07:02.913Z INFO
May 5 2017 13:07:03.164Z INFO Creating virtual app "virtual-container-host"
May 5 2017 13:07:03.277Z INFO Creating directory [RegionA01-ISCSI01-COMP01] VIC
May 5 2017 13:07:03.323Z INFO Datastore path is [RegionA01-ISCSI01-COMP01] VIC
May 5 2017 13:07:03.323Z INFO Creating appliance on target
May 5 2017 13:07:03.406Z INFO Network role "management" is sharing NIC with "client"
May 5 2017 13:07:03.445Z INFO Network role "public" is sharing NIC with "client"
May 5 2017 13:07:06.264Z INFO Uploading images for container
May 5 2017 13:07:06.265Z INFO "bootstrap.iso"
May 5 2017 13:07:06.267Z INFO "appliance.iso"
May 5 2017 13:07:24.474Z INFO Waiting for IP information
May 5 2017 13:07:53.688Z INFO Waiting for major appliance components to launch
May 5 2017 13:07:53.843Z INFO Obtained IP address for client interface: "192.168.100.106"
May 5 2017 13:07:53.843Z INFO Checking VCH connectivity with vSphere target
May 5 2017 13:07:54.127Z INFO vSphere API Test: https://vcsa-01a.corp.local vSphere API target responds as expected
May 5 2017 13:08:10.187Z INFO Initialization of appliance successful
May 5 2017 13:08:10.188Z INFO
May 5 2017 13:08:10.188Z INFO VCH Admin Portal:
May 5 2017 13:08:10.189Z INFO https://192.168.100.106:2378
May 5 2017 13:08:10.189Z INFO
May 5 2017 13:08:10.189Z INFO Published ports can be reached at:
May 5 2017 13:08:10.190Z INFO 192.168.100.106
May 5 2017 13:08:10.190Z INFO
May 5 2017 13:08:10.191Z INFO Docker environment variables:
May 5 2017 13:08:10.192Z INFO DOCKER_HOST=192.168.100.106:2375
May 5 2017 13:08:10.192Z INFO
May 5 2017 13:08:10.193Z INFO Connect to docker:
May 5 2017 13:08:10.193Z INFO docker -H 192.168.100.106:2375 info
May 5 2017 13:08:10.193Z INFO Installer completed successfully
**VIC version:**
1.1.0
**Deployment details:**
vic-machine-linux create --target vcsa-01a.corp.local \
--user administrator@corp.local \
--compute-resource RegionA01-COMP01 \
--image-store RegionA01-ISCSI01-COMP01 \
--volume-store RegionA01-ISCSI01-COMP01:default \
--public-network VM-RegionA01-vDS-COMP \
--bridge-network Bridge01-RegionA01-vDS-COMP \
--name virtual-container-host \
--registry-ca=/etc/docker/certs.d/192.168.100.104/ca.crt \
--no-tls
**Steps to reproduce:**
**Actual behavior:**
HTML5 plugin displays DOCKER_HOST=192.168.100.106:2376
**Expected behavior:**
HTML5 plugin should display DOCKER_HOST=192.168.100.106:2375
**Logs:**
**Additional details as necessary:**
I am able to reproduce this in my lab if needed. | 1.0 | HTML5 Plugin displays wrong port number when using --no-tls - When creating a VCH with the --no-tls option, HTML5 plugin displays wrong port number (2376 instead of 2375). I attached a screenshot.
May 5 2017 13:06:57.777Z INFO ### Installing VCH ####
May 5 2017 13:06:57.778Z INFO vSphere password for administrator@corp.local:
May 5 2017 13:07:01.063Z WARN Using administrative user for VCH operation - use --ops-user to improve security (see -x for advanced help)
May 5 2017 13:07:01.063Z WARN Configuring without TLS - all communications will be insecure
May 5 2017 13:07:01.064Z INFO Loaded registry CA from /etc/docker/certs.d/192.168.100.104/ca.crt
May 5 2017 13:07:01.492Z INFO Validating supplied configuration
May 5 2017 13:07:02.017Z INFO vDS configuration OK on "Bridge01-RegionA01-vDS-COMP"
May 5 2017 13:07:02.118Z INFO Firewall status: ENABLED on "/RegionA01/host/RegionA01-COMP01/esx-01a.corp.local"
May 5 2017 13:07:02.184Z INFO Firewall status: ENABLED on "/RegionA01/host/RegionA01-COMP01/esx-02a.corp.local"
May 5 2017 13:07:02.250Z INFO Firewall status: ENABLED on "/RegionA01/host/RegionA01-COMP01/esx-03a.corp.local"
May 5 2017 13:07:02.272Z INFO Firewall configuration OK on hosts:
May 5 2017 13:07:02.272Z INFO "/RegionA01/host/RegionA01-COMP01/esx-01a.corp.local"
May 5 2017 13:07:02.272Z INFO "/RegionA01/host/RegionA01-COMP01/esx-02a.corp.local"
May 5 2017 13:07:02.273Z INFO "/RegionA01/host/RegionA01-COMP01/esx-03a.corp.local"
May 5 2017 13:07:02.783Z INFO License check OK on hosts:
May 5 2017 13:07:02.783Z INFO "/RegionA01/host/RegionA01-COMP01/esx-01a.corp.local"
May 5 2017 13:07:02.790Z INFO "/RegionA01/host/RegionA01-COMP01/esx-02a.corp.local"
May 5 2017 13:07:02.790Z INFO "/RegionA01/host/RegionA01-COMP01/esx-03a.corp.local"
May 5 2017 13:07:02.801Z INFO DRS check OK on:
May 5 2017 13:07:02.802Z INFO "/RegionA01/host/RegionA01-COMP01"
May 5 2017 13:07:02.913Z INFO
May 5 2017 13:07:03.164Z INFO Creating virtual app "virtual-container-host"
May 5 2017 13:07:03.277Z INFO Creating directory [RegionA01-ISCSI01-COMP01] VIC
May 5 2017 13:07:03.323Z INFO Datastore path is [RegionA01-ISCSI01-COMP01] VIC
May 5 2017 13:07:03.323Z INFO Creating appliance on target
May 5 2017 13:07:03.406Z INFO Network role "management" is sharing NIC with "client"
May 5 2017 13:07:03.445Z INFO Network role "public" is sharing NIC with "client"
May 5 2017 13:07:06.264Z INFO Uploading images for container
May 5 2017 13:07:06.265Z INFO "bootstrap.iso"
May 5 2017 13:07:06.267Z INFO "appliance.iso"
May 5 2017 13:07:24.474Z INFO Waiting for IP information
May 5 2017 13:07:53.688Z INFO Waiting for major appliance components to launch
May 5 2017 13:07:53.843Z INFO Obtained IP address for client interface: "192.168.100.106"
May 5 2017 13:07:53.843Z INFO Checking VCH connectivity with vSphere target
May 5 2017 13:07:54.127Z INFO vSphere API Test: https://vcsa-01a.corp.local vSphere API target responds as expected
May 5 2017 13:08:10.187Z INFO Initialization of appliance successful
May 5 2017 13:08:10.188Z INFO
May 5 2017 13:08:10.188Z INFO VCH Admin Portal:
May 5 2017 13:08:10.189Z INFO https://192.168.100.106:2378
May 5 2017 13:08:10.189Z INFO
May 5 2017 13:08:10.189Z INFO Published ports can be reached at:
May 5 2017 13:08:10.190Z INFO 192.168.100.106
May 5 2017 13:08:10.190Z INFO
May 5 2017 13:08:10.191Z INFO Docker environment variables:
May 5 2017 13:08:10.192Z INFO DOCKER_HOST=192.168.100.106:2375
May 5 2017 13:08:10.192Z INFO
May 5 2017 13:08:10.193Z INFO Connect to docker:
May 5 2017 13:08:10.193Z INFO docker -H 192.168.100.106:2375 info
May 5 2017 13:08:10.193Z INFO Installer completed successfully
**VIC version:**
1.1.0
**Deployment details:**
vic-machine-linux create --target vcsa-01a.corp.local \
--user administrator@corp.local \
--compute-resource RegionA01-COMP01 \
--image-store RegionA01-ISCSI01-COMP01 \
--volume-store RegionA01-ISCSI01-COMP01:default \
--public-network VM-RegionA01-vDS-COMP \
--bridge-network Bridge01-RegionA01-vDS-COMP \
--name virtual-container-host \
--registry-ca=/etc/docker/certs.d/192.168.100.104/ca.crt \
--no-tls
**Steps to reproduce:**
**Actual behavior:**
HTML5 plugin displays DOCKER_HOST=192.168.100.106:2376
**Expected behavior:**
HTML5 plugin should display DOCKER_HOST=192.168.100.106:2375
**Logs:**
**Additional details as necessary:**
I am able to reproduce this in my lab if needed. | priority | plugin displays wrong port number when using no tls when creating a vch with the no tls option plugin displays wrong port number instead of i attached a screenshot may info installing vch may info vsphere password for administrator corp local may warn using administrative user for vch operation use ops user to improve security see x for advanced help may warn configuring without tls all communications will be insecure may info loaded registry ca from etc docker certs d ca crt may info validating supplied configuration may info vds configuration ok on vds comp may info firewall status enabled on host esx corp local may info firewall status enabled on host esx corp local may info firewall status enabled on host esx corp local may info firewall configuration ok on hosts may info host esx corp local may info host esx corp local may info host esx corp local may info license check ok on hosts may info host esx corp local may info host esx corp local may info host esx corp local may info drs check ok on may info host may info may info creating virtual app virtual container host may info creating directory vic may info datastore path is vic may info creating appliance on target may info network role management is sharing nic with client may info network role public is sharing nic with client may info uploading images for container may info bootstrap iso may info appliance iso may info waiting for ip information may info waiting for major appliance components to launch may info obtained ip address for client interface may info checking vch connectivity with vsphere target may info vsphere api test vsphere api target responds as expected may info initialization of appliance successful may info may info vch admin portal may info may info may info published ports can be reached at may info may info may info docker environment variables may info docker host may info may info connect to docker may info docker h info may info installer completed successfully vic version deployment details vic machine linux create target vcsa corp local user administrator corp local compute resource image store volume store default public network vm vds comp bridge network vds comp name virtual container host registry ca etc docker certs d ca crt no tls steps to reproduce actual behavior plugin displays docker host expected behavior plugin should display docker host logs additional details as necessary i am able to reproduce this in my lab if needed | 1 |
375,720 | 26,174,578,777 | IssuesEvent | 2023-01-02 07:59:40 | deepchecks/deepchecks | https://api.github.com/repos/deepchecks/deepchecks | closed | [BUG] Fix Typo in docs/source/getting-started/installation.rst | documentation bug | **Describe the bug**
In [docs/source/getting-started/installation.rst](https://github.com/deepchecks/deepchecks/blob/cdfcfc5fbc23d7daf99a74505c0cfd17fc320a17/docs/source/getting-started/installation.rst) fix typo located at line 73
Before
```
Istallation of deepchecks for CV should be stated explicitly and it includes
```
After
```
Installation of deepchecks for CV should be stated explicitly and it includes
``` | 1.0 | [BUG] Fix Typo in docs/source/getting-started/installation.rst - **Describe the bug**
In [docs/source/getting-started/installation.rst](https://github.com/deepchecks/deepchecks/blob/cdfcfc5fbc23d7daf99a74505c0cfd17fc320a17/docs/source/getting-started/installation.rst) fix typo located at line 73
Before
```
Istallation of deepchecks for CV should be stated explicitly and it includes
```
After
```
Installation of deepchecks for CV should be stated explicitly and it includes
``` | non_priority | fix typo in docs source getting started installation rst describe the bug in fix typo located at line before istallation of deepchecks for cv should be stated explicitly and it includes after installation of deepchecks for cv should be stated explicitly and it includes | 0 |
650,397 | 21,390,327,701 | IssuesEvent | 2022-04-21 06:17:59 | TerriaJS/terriajs | https://api.github.com/repos/TerriaJS/terriajs | opened | Shared link should always work | T-Bug High priority | When creating a catalog item's shared link before adding the item to the map, the shared link is not usable. Besides, if using the shared link, `Explore map data` will become unclickable. | 1.0 | Shared link should always work - When creating a catalog item's shared link before adding the item to the map, the shared link is not usable. Besides, if using the shared link, `Explore map data` will become unclickable. | priority | shared link should always work when creating a catalog item s shared link before adding the item to the map the shared link is not usable besides if using the shared link explore map data will become unclickable | 1 |
6,955 | 2,610,319,325 | IssuesEvent | 2015-02-26 19:43:02 | chrsmith/republic-at-war | https://api.github.com/repos/chrsmith/republic-at-war | closed | Text | auto-migrated Priority-Medium Type-Defect | ```
AA9 transport [missing] description
```
-----
Original issue reported on code.google.com by `z3r0...@gmail.com` on 7 May 2011 at 11:37 | 1.0 | Text - ```
AA9 transport [missing] description
```
-----
Original issue reported on code.google.com by `z3r0...@gmail.com` on 7 May 2011 at 11:37 | non_priority | text transport description original issue reported on code google com by gmail com on may at | 0 |
29,400 | 4,500,789,768 | IssuesEvent | 2016-09-01 06:51:53 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | teamcity: failed tests on develop: test/TestRaftRemoveRace | Robot test-failure | The following tests appear to have failed:
[#17097](https://teamcity.cockroachdb.com/viewLog.html?buildId=17097):
```
--- FAIL: test/TestRaftRemoveRace (0.013s)
client_test.go:884: change replicas of range 1 aborted due to failed preemptive snapshot: range=1: remote couldn't accept snapshot with error: permanently rejected snapshot: store=3:3: canApplySnapshotLocked: cannot add placeholder, have an existing placeholder range=1 [/Min-/Max) (placeholder)
```
Please assign, take a look and update the issue accordingly. | 1.0 | teamcity: failed tests on develop: test/TestRaftRemoveRace - The following tests appear to have failed:
[#17097](https://teamcity.cockroachdb.com/viewLog.html?buildId=17097):
```
--- FAIL: test/TestRaftRemoveRace (0.013s)
client_test.go:884: change replicas of range 1 aborted due to failed preemptive snapshot: range=1: remote couldn't accept snapshot with error: permanently rejected snapshot: store=3:3: canApplySnapshotLocked: cannot add placeholder, have an existing placeholder range=1 [/Min-/Max) (placeholder)
```
Please assign, take a look and update the issue accordingly. | non_priority | teamcity failed tests on develop test testraftremoverace the following tests appear to have failed fail test testraftremoverace client test go change replicas of range aborted due to failed preemptive snapshot range remote couldn t accept snapshot with error permanently rejected snapshot store canapplysnapshotlocked cannot add placeholder have an existing placeholder range min max placeholder please assign take a look and update the issue accordingly | 0 |
800,332 | 28,361,348,999 | IssuesEvent | 2023-04-12 10:58:39 | netdata/netdata | https://api.github.com/repos/netdata/netdata | closed | Install script should support OpenWRT | area/packaging feature request priority/medium | Netdata should install and run on OpenWRT with the install script.
It is important for us that cloud works also (meaning cloud dependencies and cloud build should also work)
However, right now there are some basic problems - i.e. old version of tar being used by the install script.
See
https://forum.openwrt.org/t/how-to-claim-agent-on-netdata/68711/5
https://github.com/openwrt/packages/pull/12164#issuecomment-655981628
https://unix.stackexchange.com/questions/249353/invalid-tar-magic-on-openwrt
Initially just setting the compression explicitly should help, but let's test this end-to-end and make sure cloud features also build.
| 1.0 | Install script should support OpenWRT - Netdata should install and run on OpenWRT with the install script.
It is important for us that cloud works also (meaning cloud dependencies and cloud build should also work)
However, right now there are some basic problems - i.e. old version of tar being used by the install script.
See
https://forum.openwrt.org/t/how-to-claim-agent-on-netdata/68711/5
https://github.com/openwrt/packages/pull/12164#issuecomment-655981628
https://unix.stackexchange.com/questions/249353/invalid-tar-magic-on-openwrt
Initially just setting the compression explicitly should help, but let's test this end-to-end and make sure cloud features also build.
| priority | install script should support openwrt netdata should install and run on openwrt with the install script it is important for us that cloud works also meaning cloud dependencies and cloud build should also work however right now there are some basic problems i e old version of tar being used by the install script see initially just setting the compression explicitly should help but let s test this end to end and make sure cloud features also build | 1 |
5,563 | 7,214,145,422 | IssuesEvent | 2018-02-08 00:39:30 | wesnoth/wesnoth | https://api.github.com/repos/wesnoth/wesnoth | closed | support anonymous issues | Services | it would be nice to be have some form to enable users to report bugs without creating a github account. since this is a public repo we could just have a dummy account that doesn't even need access to the wesnoth repo to let a script create issues with it. One of the problems with suhc a solution that is that i am unuse whethe rit also alows user to respons in existent issues | 1.0 | support anonymous issues - it would be nice to be have some form to enable users to report bugs without creating a github account. since this is a public repo we could just have a dummy account that doesn't even need access to the wesnoth repo to let a script create issues with it. One of the problems with suhc a solution that is that i am unuse whethe rit also alows user to respons in existent issues | non_priority | support anonymous issues it would be nice to be have some form to enable users to report bugs without creating a github account since this is a public repo we could just have a dummy account that doesn t even need access to the wesnoth repo to let a script create issues with it one of the problems with suhc a solution that is that i am unuse whethe rit also alows user to respons in existent issues | 0 |
87,510 | 25,136,211,577 | IssuesEvent | 2022-11-09 18:49:28 | libreswan/libreswan | https://api.github.com/repos/libreswan/libreswan | closed | delete include/unbound/unbound-event.h | build upstream FreeBSD blocked | | OS | Status |
|-|-|
| Linux | installed |
| NetBSD | installed |
| OpenBSD | 7.2 |
| FreeBSD | submitted https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263838 | | 1.0 | delete include/unbound/unbound-event.h - | OS | Status |
|-|-|
| Linux | installed |
| NetBSD | installed |
| OpenBSD | 7.2 |
| FreeBSD | submitted https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263838 | | non_priority | delete include unbound unbound event h os status linux installed netbsd installed openbsd freebsd submitted | 0 |
42,873 | 7,006,765,603 | IssuesEvent | 2017-12-19 09:45:51 | PaddlePaddle/Paddle | https://api.github.com/repos/PaddlePaddle/Paddle | closed | Navigation of Distributed Training is wrong | documentation | In the Chinese version, we can use the downward arrow:
But in the English version, this arrow is missing:
The reason is that [kubernetes distributed](https://github.com/PaddlePaddle/Paddle/blob/develop/doc/howto/usage/cluster/cluster_train_en.md#use-different-clusters) doesn't have a link. | 1.0 | Navigation of Distributed Training is wrong - In the Chinese version, we can use the downward arrow:
But in the English version, this arrow is missing:
The reason is that [kubernetes distributed](https://github.com/PaddlePaddle/Paddle/blob/develop/doc/howto/usage/cluster/cluster_train_en.md#use-different-clusters) doesn't have a link. | non_priority | navigation of distributed training is wrong in the chinese version we can use the downward arrow but in the english version this arrow is missing the reason is that doesn t have a link | 0 |
37,964 | 12,510,908,286 | IssuesEvent | 2020-06-02 19:32:29 | kenferrara/react-base-table | https://api.github.com/repos/kenferrara/react-base-table | opened | CVE-2018-11698 (High) detected in opennms-opennms-source-22.0.1-1 | security vulnerability | ## CVE-2018-11698 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>opennmsopennms-source-22.0.1-1</b></p></summary>
<p>
<p>A Java based fault and performance management system</p>
<p>Library home page: <a href=https://sourceforge.net/projects/opennms/>https://sourceforge.net/projects/opennms/</a></p>
<p>Found in HEAD commit: <a href="https://github.com/kenferrara/react-base-table/commit/8e278435a954b3faf16104b3f871a7a2a913555a">8e278435a954b3faf16104b3f871a7a2a913555a</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Library Source Files (64)</summary>
<p></p>
<p> * The source files were matched to this source library based on a best effort match. Source libraries are selected from a list of probable public libraries.</p>
<p>
- /react-base-table/node_modules/node-sass/src/sass_types/number.cpp
- /react-base-table/website/node_modules/console-browserify/test/static/test-adapter.js
- /react-base-table/website/node_modules/nan/nan_persistent_pre_12_inl.h
- /react-base-table/node_modules/nan/nan_persistent_12_inl.h
- /react-base-table/node_modules/node-sass/src/libsass/src/emitter.hpp
- /react-base-table/node_modules/node-sass/src/sass_types/color.h
- /react-base-table/node_modules/node-sass/src/libsass/src/ast.hpp
- /react-base-table/node_modules/node-sass/src/libsass/src/operation.hpp
- /react-base-table/node_modules/node-sass/src/libsass/src/emitter.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/bind.cpp
- /react-base-table/node_modules/js-base64/.attic/test-moment/./yoshinoya.js
- /react-base-table/node_modules/node-sass/src/libsass/src/cssize.hpp
- /react-base-table/node_modules/node-sass/src/libsass/src/error_handling.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/context.cpp
- /react-base-table/node_modules/node-sass/src/sass_types/factory.cpp
- /react-base-table/node_modules/node-sass/src/sass_types/list.h
- /react-base-table/node_modules/nan/nan_callbacks_pre_12_inl.h
- /react-base-table/node_modules/node-sass/src/libsass/src/values.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/util.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/ast.cpp
- /react-base-table/node_modules/node-sass/src/sass_types/list.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/to_value.hpp
- /react-base-table/website/node_modules/nan/nan_json.h
- /react-base-table/node_modules/node-sass/src/libsass/src/prelexer.hpp
- /react-base-table/node_modules/node-sass/src/sass_types/boolean.h
- /react-base-table/node_modules/node-sass/src/sass_types/null.cpp
- /react-base-table/node_modules/node-sass/src/sass_types/color.cpp
- /react-base-table/node_modules/node-sass/src/custom_function_bridge.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/operators.hpp
- /react-base-table/node_modules/node-sass/src/libsass/src/to_value.cpp
- /react-base-table/website/node_modules/nan/nan_callbacks.h
- /react-base-table/node_modules/node-sass/src/libsass/src/to_c.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/output.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/constants.hpp
- /react-base-table/node_modules/node-sass/src/libsass/src/eval.hpp
- /react-base-table/node_modules/node-sass/src/libsass/src/extend.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/ast_def_macros.hpp
- /react-base-table/website/node_modules/nan/nan_converters.h
- /react-base-table/node_modules/nan/nan_converters_pre_43_inl.h
- /react-base-table/node_modules/node-sass/src/libsass/src/functions.hpp
- /react-base-table/node_modules/nan/nan_define_own_property_helper.h
- /react-base-table/node_modules/node-sass/src/libsass/src/expand.hpp
- /react-base-table/node_modules/node-sass/src/sass_types/map.cpp
- /react-base-table/node_modules/node-sass/src/custom_importer_bridge.h
- /react-base-table/node_modules/nan/nan_private.h
- /react-base-table/website/node_modules/nan/nan_new.h
- /react-base-table/node_modules/js-base64/.attic/test-moment/./es5.js
- /react-base-table/node_modules/node-sass/src/libsass/src/inspect.hpp
- /react-base-table/node_modules/nan/nan_implementation_pre_12_inl.h
- /react-base-table/node_modules/node-sass/src/libsass/src/ast_fwd_decl.hpp
- /react-base-table/node_modules/node-sass/src/libsass/src/check_nesting.hpp
- /react-base-table/node_modules/node-sass/src/sass_types/value.h
- /react-base-table/node_modules/node-sass/src/libsass/src/backtrace.cpp
- /react-base-table/node_modules/node-sass/src/sass_types/boolean.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/check_nesting.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/file.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/error_handling.hpp
- /react-base-table/node_modules/node-sass/src/sass_types/sass_value_wrapper.h
- /react-base-table/node_modules/node-sass/src/libsass/src/sass_values.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/context.hpp
- /react-base-table/node_modules/node-sass/src/libsass/src/sass_context.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/constants.cpp
- /react-base-table/node_modules/js-base64/.attic/test-moment/./dankogai.js
- /react-base-table/node_modules/node-sass/src/sass_types/string.cpp
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in LibSass through 3.5.4. An out-of-bounds read of a memory region was found in the function Sass::handle_error which could be leveraged by an attacker to disclose information or manipulated to read from unmapped memory causing a denial of service.
<p>Publish Date: 2018-06-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11698>CVE-2018-11698</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.1</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: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11698">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11698</a></p>
<p>Release Date: 2019-08-06</p>
<p>Fix Resolution: LibSass - 3.6.0</p>
</p>
</details>
<p></p>
| True | CVE-2018-11698 (High) detected in opennms-opennms-source-22.0.1-1 - ## CVE-2018-11698 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>opennmsopennms-source-22.0.1-1</b></p></summary>
<p>
<p>A Java based fault and performance management system</p>
<p>Library home page: <a href=https://sourceforge.net/projects/opennms/>https://sourceforge.net/projects/opennms/</a></p>
<p>Found in HEAD commit: <a href="https://github.com/kenferrara/react-base-table/commit/8e278435a954b3faf16104b3f871a7a2a913555a">8e278435a954b3faf16104b3f871a7a2a913555a</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Library Source Files (64)</summary>
<p></p>
<p> * The source files were matched to this source library based on a best effort match. Source libraries are selected from a list of probable public libraries.</p>
<p>
- /react-base-table/node_modules/node-sass/src/sass_types/number.cpp
- /react-base-table/website/node_modules/console-browserify/test/static/test-adapter.js
- /react-base-table/website/node_modules/nan/nan_persistent_pre_12_inl.h
- /react-base-table/node_modules/nan/nan_persistent_12_inl.h
- /react-base-table/node_modules/node-sass/src/libsass/src/emitter.hpp
- /react-base-table/node_modules/node-sass/src/sass_types/color.h
- /react-base-table/node_modules/node-sass/src/libsass/src/ast.hpp
- /react-base-table/node_modules/node-sass/src/libsass/src/operation.hpp
- /react-base-table/node_modules/node-sass/src/libsass/src/emitter.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/bind.cpp
- /react-base-table/node_modules/js-base64/.attic/test-moment/./yoshinoya.js
- /react-base-table/node_modules/node-sass/src/libsass/src/cssize.hpp
- /react-base-table/node_modules/node-sass/src/libsass/src/error_handling.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/context.cpp
- /react-base-table/node_modules/node-sass/src/sass_types/factory.cpp
- /react-base-table/node_modules/node-sass/src/sass_types/list.h
- /react-base-table/node_modules/nan/nan_callbacks_pre_12_inl.h
- /react-base-table/node_modules/node-sass/src/libsass/src/values.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/util.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/ast.cpp
- /react-base-table/node_modules/node-sass/src/sass_types/list.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/to_value.hpp
- /react-base-table/website/node_modules/nan/nan_json.h
- /react-base-table/node_modules/node-sass/src/libsass/src/prelexer.hpp
- /react-base-table/node_modules/node-sass/src/sass_types/boolean.h
- /react-base-table/node_modules/node-sass/src/sass_types/null.cpp
- /react-base-table/node_modules/node-sass/src/sass_types/color.cpp
- /react-base-table/node_modules/node-sass/src/custom_function_bridge.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/operators.hpp
- /react-base-table/node_modules/node-sass/src/libsass/src/to_value.cpp
- /react-base-table/website/node_modules/nan/nan_callbacks.h
- /react-base-table/node_modules/node-sass/src/libsass/src/to_c.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/output.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/constants.hpp
- /react-base-table/node_modules/node-sass/src/libsass/src/eval.hpp
- /react-base-table/node_modules/node-sass/src/libsass/src/extend.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/ast_def_macros.hpp
- /react-base-table/website/node_modules/nan/nan_converters.h
- /react-base-table/node_modules/nan/nan_converters_pre_43_inl.h
- /react-base-table/node_modules/node-sass/src/libsass/src/functions.hpp
- /react-base-table/node_modules/nan/nan_define_own_property_helper.h
- /react-base-table/node_modules/node-sass/src/libsass/src/expand.hpp
- /react-base-table/node_modules/node-sass/src/sass_types/map.cpp
- /react-base-table/node_modules/node-sass/src/custom_importer_bridge.h
- /react-base-table/node_modules/nan/nan_private.h
- /react-base-table/website/node_modules/nan/nan_new.h
- /react-base-table/node_modules/js-base64/.attic/test-moment/./es5.js
- /react-base-table/node_modules/node-sass/src/libsass/src/inspect.hpp
- /react-base-table/node_modules/nan/nan_implementation_pre_12_inl.h
- /react-base-table/node_modules/node-sass/src/libsass/src/ast_fwd_decl.hpp
- /react-base-table/node_modules/node-sass/src/libsass/src/check_nesting.hpp
- /react-base-table/node_modules/node-sass/src/sass_types/value.h
- /react-base-table/node_modules/node-sass/src/libsass/src/backtrace.cpp
- /react-base-table/node_modules/node-sass/src/sass_types/boolean.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/check_nesting.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/file.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/error_handling.hpp
- /react-base-table/node_modules/node-sass/src/sass_types/sass_value_wrapper.h
- /react-base-table/node_modules/node-sass/src/libsass/src/sass_values.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/context.hpp
- /react-base-table/node_modules/node-sass/src/libsass/src/sass_context.cpp
- /react-base-table/node_modules/node-sass/src/libsass/src/constants.cpp
- /react-base-table/node_modules/js-base64/.attic/test-moment/./dankogai.js
- /react-base-table/node_modules/node-sass/src/sass_types/string.cpp
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in LibSass through 3.5.4. An out-of-bounds read of a memory region was found in the function Sass::handle_error which could be leveraged by an attacker to disclose information or manipulated to read from unmapped memory causing a denial of service.
<p>Publish Date: 2018-06-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11698>CVE-2018-11698</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.1</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: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11698">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11698</a></p>
<p>Release Date: 2019-08-06</p>
<p>Fix Resolution: LibSass - 3.6.0</p>
</p>
</details>
<p></p>
| non_priority | cve high detected in opennms opennms source cve high severity vulnerability vulnerable library opennmsopennms source a java based fault and performance management system library home page a href found in head commit a href library source files the source files were matched to this source library based on a best effort match source libraries are selected from a list of probable public libraries react base table node modules node sass src sass types number cpp react base table website node modules console browserify test static test adapter js react base table website node modules nan nan persistent pre inl h react base table node modules nan nan persistent inl h react base table node modules node sass src libsass src emitter hpp react base table node modules node sass src sass types color h react base table node modules node sass src libsass src ast hpp react base table node modules node sass src libsass src operation hpp react base table node modules node sass src libsass src emitter cpp react base table node modules node sass src libsass src bind cpp react base table node modules js attic test moment yoshinoya js react base table node modules node sass src libsass src cssize hpp react base table node modules node sass src libsass src error handling cpp react base table node modules node sass src libsass src context cpp react base table node modules node sass src sass types factory cpp react base table node modules node sass src sass types list h react base table node modules nan nan callbacks pre inl h react base table node modules node sass src libsass src values cpp react base table node modules node sass src libsass src util cpp react base table node modules node sass src libsass src ast cpp react base table node modules node sass src sass types list cpp react base table node modules node sass src libsass src to value hpp react base table website node modules nan nan json h react base table node modules node sass src libsass src prelexer hpp react base table node modules node sass src sass types boolean h react base table node modules node sass src sass types null cpp react base table node modules node sass src sass types color cpp react base table node modules node sass src custom function bridge cpp react base table node modules node sass src libsass src operators hpp react base table node modules node sass src libsass src to value cpp react base table website node modules nan nan callbacks h react base table node modules node sass src libsass src to c cpp react base table node modules node sass src libsass src output cpp react base table node modules node sass src libsass src constants hpp react base table node modules node sass src libsass src eval hpp react base table node modules node sass src libsass src extend cpp react base table node modules node sass src libsass src ast def macros hpp react base table website node modules nan nan converters h react base table node modules nan nan converters pre inl h react base table node modules node sass src libsass src functions hpp react base table node modules nan nan define own property helper h react base table node modules node sass src libsass src expand hpp react base table node modules node sass src sass types map cpp react base table node modules node sass src custom importer bridge h react base table node modules nan nan private h react base table website node modules nan nan new h react base table node modules js attic test moment js react base table node modules node sass src libsass src inspect hpp react base table node modules nan nan implementation pre inl h react base table node modules node sass src libsass src ast fwd decl hpp react base table node modules node sass src libsass src check nesting hpp react base table node modules node sass src sass types value h react base table node modules node sass src libsass src backtrace cpp react base table node modules node sass src sass types boolean cpp react base table node modules node sass src libsass src check nesting cpp react base table node modules node sass src libsass src file cpp react base table node modules node sass src libsass src error handling hpp react base table node modules node sass src sass types sass value wrapper h react base table node modules node sass src libsass src sass values cpp react base table node modules node sass src libsass src context hpp react base table node modules node sass src libsass src sass context cpp react base table node modules node sass src libsass src constants cpp react base table node modules js attic test moment dankogai js react base table node modules node sass src sass types string cpp vulnerability details an issue was discovered in libsass through an out of bounds read of a memory region was found in the function sass handle error which could be leveraged by an attacker to disclose information or manipulated to read from unmapped memory causing a denial of service publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution libsass | 0 |
8,812 | 2,886,714,497 | IssuesEvent | 2015-06-12 10:16:42 | quantmind/lux | https://api.github.com/repos/quantmind/lux | opened | template url for views with parameters | AngularJS bug extension requires design effort | The `lux` way for serving templates to angular [ui-roter](https://github.com/angular-ui/ui-router) pages for a give url ``/foo`` is:
```
GET /foo?template=ui
```
This is added by a router via the [angular_page](https://github.com/quantmind/lux/blob/dev/lux/core/wrappers.py#L169) method which is invoked by the [add_to_sidemap](https://github.com/quantmind/lux/blob/dev/lux/extensions/angular/__init__.py#L159) function in the angular extension.
This method does not work well when the router is serving a page with url parameters, for example ``/foo/<id>``.
| 1.0 | template url for views with parameters - The `lux` way for serving templates to angular [ui-roter](https://github.com/angular-ui/ui-router) pages for a give url ``/foo`` is:
```
GET /foo?template=ui
```
This is added by a router via the [angular_page](https://github.com/quantmind/lux/blob/dev/lux/core/wrappers.py#L169) method which is invoked by the [add_to_sidemap](https://github.com/quantmind/lux/blob/dev/lux/extensions/angular/__init__.py#L159) function in the angular extension.
This method does not work well when the router is serving a page with url parameters, for example ``/foo/<id>``.
| non_priority | template url for views with parameters the lux way for serving templates to angular pages for a give url foo is get foo template ui this is added by a router via the method which is invoked by the function in the angular extension this method does not work well when the router is serving a page with url parameters for example foo | 0 |
157,286 | 19,957,083,829 | IssuesEvent | 2022-01-28 01:22:39 | panasalap/linux-4.1.15 | https://api.github.com/repos/panasalap/linux-4.1.15 | opened | CVE-2015-8787 (High) detected in linuxlinux-4.1.17 | security vulnerability | ## CVE-2015-8787 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.1.17</b></p></summary>
<p>
<p>Apache Software Foundation (ASF)</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/nf_nat_redirect.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/nf_nat_redirect.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The nf_nat_redirect_ipv4 function in net/netfilter/nf_nat_redirect.c in the Linux kernel before 4.4 allows remote attackers to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by sending certain IPv4 packets to an incompletely configured interface, a related issue to CVE-2003-1604.
<p>Publish Date: 2016-02-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-8787>CVE-2015-8787</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-8787">https://nvd.nist.gov/vuln/detail/CVE-2015-8787</a></p>
<p>Release Date: 2016-02-08</p>
<p>Fix Resolution: 4.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2015-8787 (High) detected in linuxlinux-4.1.17 - ## CVE-2015-8787 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.1.17</b></p></summary>
<p>
<p>Apache Software Foundation (ASF)</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/nf_nat_redirect.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/nf_nat_redirect.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The nf_nat_redirect_ipv4 function in net/netfilter/nf_nat_redirect.c in the Linux kernel before 4.4 allows remote attackers to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by sending certain IPv4 packets to an incompletely configured interface, a related issue to CVE-2003-1604.
<p>Publish Date: 2016-02-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-8787>CVE-2015-8787</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-8787">https://nvd.nist.gov/vuln/detail/CVE-2015-8787</a></p>
<p>Release Date: 2016-02-08</p>
<p>Fix Resolution: 4.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in linuxlinux cve high severity vulnerability vulnerable library linuxlinux apache software foundation asf library home page a href found in base branch master vulnerable source files net netfilter nf nat redirect c net netfilter nf nat redirect c vulnerability details the nf nat redirect function in net netfilter nf nat redirect c in the linux kernel before allows remote attackers to cause a denial of service null pointer dereference and system crash or possibly have unspecified other impact by sending certain packets to an incompletely configured interface a related issue to cve publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
692,946 | 23,755,875,882 | IssuesEvent | 2022-09-01 03:00:29 | brainhackorg/brainhack_cloud | https://api.github.com/repos/brainhackorg/brainhack_cloud | closed | Layout of landing page: suboptimal responsiveness | website low_priority | For certain devices the layout will not be optimal.
| 1.0 | Layout of landing page: suboptimal responsiveness - For certain devices the layout will not be optimal.
| priority | layout of landing page suboptimal responsiveness for certain devices the layout will not be optimal | 1 |
728,527 | 25,082,980,156 | IssuesEvent | 2022-11-07 21:01:44 | rmlockwood/FLExTrans | https://api.github.com/repos/rmlockwood/FLExTrans | closed | [Live Rule Tester] Refresh rules on advanced transfer unchecks the other tabs that aren't in focus | bug medium priority | All rules in all tabs should remain in the checked state they were in. | 1.0 | [Live Rule Tester] Refresh rules on advanced transfer unchecks the other tabs that aren't in focus - All rules in all tabs should remain in the checked state they were in. | priority | refresh rules on advanced transfer unchecks the other tabs that aren t in focus all rules in all tabs should remain in the checked state they were in | 1 |
156,925 | 24,626,336,907 | IssuesEvent | 2022-10-16 15:13:46 | baloise-incubator/design-system | https://api.github.com/repos/baloise-incubator/design-system | closed | Exchange Fallback Avatars | 🆕 Enhancement 💁 Help Wanted 🎨 Design Support | We got the feedback that the avatars that were created by Meta do not match our use-case. Therefore we have to create new ones in order that IBM can replace them.
Following tasks should be completed:
- [x] Prepare briefing for Stadtluft (2:3)
- [x] Update Figma
- [x] Send new icons to Leo (upload to Frontify)
- [x] Send feedback to Michael (he'll forward request to IBM) | 1.0 | Exchange Fallback Avatars - We got the feedback that the avatars that were created by Meta do not match our use-case. Therefore we have to create new ones in order that IBM can replace them.
Following tasks should be completed:
- [x] Prepare briefing for Stadtluft (2:3)
- [x] Update Figma
- [x] Send new icons to Leo (upload to Frontify)
- [x] Send feedback to Michael (he'll forward request to IBM) | non_priority | exchange fallback avatars we got the feedback that the avatars that were created by meta do not match our use case therefore we have to create new ones in order that ibm can replace them following tasks should be completed prepare briefing for stadtluft update figma send new icons to leo upload to frontify send feedback to michael he ll forward request to ibm | 0 |
731,881 | 25,235,242,911 | IssuesEvent | 2022-11-14 23:58:54 | open-telemetry/opentelemetry-collector | https://api.github.com/repos/open-telemetry/opentelemetry-collector | closed | Make default config per type (metric, traces, etc.) | enhancement priority:p3 release:after-ga area:config |
**Is your feature request related to a problem? Please describe.**
Created from https://github.com/open-telemetry/opentelemetry-collector/pull/1966#discussion_r524005206
I want to create default config that is different for each entity (traces, metrics, logs). Currently the `Factory.createDefaultConfig` creates a default config for all entities.
**Describe the solution you'd like**
A factory interface that allows creating different default config for each entity.
**Describe alternatives you've considered**
Create a single default config with zero values and set appropriate defaults in the create exporter.
**Additional context**
https://github.com/open-telemetry/opentelemetry-collector/pull/1966#discussion_r524005206
| 1.0 | Make default config per type (metric, traces, etc.) -
**Is your feature request related to a problem? Please describe.**
Created from https://github.com/open-telemetry/opentelemetry-collector/pull/1966#discussion_r524005206
I want to create default config that is different for each entity (traces, metrics, logs). Currently the `Factory.createDefaultConfig` creates a default config for all entities.
**Describe the solution you'd like**
A factory interface that allows creating different default config for each entity.
**Describe alternatives you've considered**
Create a single default config with zero values and set appropriate defaults in the create exporter.
**Additional context**
https://github.com/open-telemetry/opentelemetry-collector/pull/1966#discussion_r524005206
| priority | make default config per type metric traces etc is your feature request related to a problem please describe created from i want to create default config that is different for each entity traces metrics logs currently the factory createdefaultconfig creates a default config for all entities describe the solution you d like a factory interface that allows creating different default config for each entity describe alternatives you ve considered create a single default config with zero values and set appropriate defaults in the create exporter additional context | 1 |
23,125 | 2,652,930,884 | IssuesEvent | 2015-03-16 20:08:10 | GoogleCloudPlatform/kubernetes | https://api.github.com/repos/GoogleCloudPlatform/kubernetes | closed | Write an e2e test that specifically tests kubectl functionality | area/reliability priority/P2 team/UX | As #3130 nears completion, we want to make sure that kubectl coverage isn't lost by moving to go tests. | 1.0 | Write an e2e test that specifically tests kubectl functionality - As #3130 nears completion, we want to make sure that kubectl coverage isn't lost by moving to go tests. | priority | write an test that specifically tests kubectl functionality as nears completion we want to make sure that kubectl coverage isn t lost by moving to go tests | 1 |
2,978 | 3,050,761,564 | IssuesEvent | 2015-08-12 01:30:35 | Carthage/Carthage | https://api.github.com/repos/Carthage/Carthage | closed | Carthage build fails with iOS 7.1 simulator installed | bug build help wanted | Steps to reproduce:
- Install the iOS 7.1 Simulator in Xcode 6.2
- Create a new Cocoa Touch Framework project in Xcode
- Run `carthage build --no-skip-current` in the directory that the Framework project was created in
You will receive the following build error:
```
CompileC ...
invalid architecture 'arm64' for deployment target '-mios-simulator-version-min=8.2'
Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 1
```
This is due to the fact that Carthage (as far as I can tell) is running the following command during `carthage build --no-skip-current`:
```
xcodebuild build -scheme Framework -sdk iphonesimulator
```
If you run the above command on your new framework project, you will see the same build error that is produced when you run `carthage build`.
As far as I can tell, the reason for this failure is that when no destination is specified in a build command, `xcodebuild` implicitly selects a destination simulator to build for. Since we have the iOS 7.1 Simulator installed, it is (for some reason) picked as the default destination, causing the above error to occur. However, if you select the latest simulator as the build destination via the command line:
```bash
xcodebuild build -scheme Framework -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 4s,OS=latest'
```
There is no build failure. The solution for this (as far as I can tell) would be to have Carthage allow for a `destination` option to be specified in addition to the existing `platform` and `configuration` options, or simply to not support Xcode installs that have pre-iOS 8 simulators installed. | 1.0 | Carthage build fails with iOS 7.1 simulator installed - Steps to reproduce:
- Install the iOS 7.1 Simulator in Xcode 6.2
- Create a new Cocoa Touch Framework project in Xcode
- Run `carthage build --no-skip-current` in the directory that the Framework project was created in
You will receive the following build error:
```
CompileC ...
invalid architecture 'arm64' for deployment target '-mios-simulator-version-min=8.2'
Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 1
```
This is due to the fact that Carthage (as far as I can tell) is running the following command during `carthage build --no-skip-current`:
```
xcodebuild build -scheme Framework -sdk iphonesimulator
```
If you run the above command on your new framework project, you will see the same build error that is produced when you run `carthage build`.
As far as I can tell, the reason for this failure is that when no destination is specified in a build command, `xcodebuild` implicitly selects a destination simulator to build for. Since we have the iOS 7.1 Simulator installed, it is (for some reason) picked as the default destination, causing the above error to occur. However, if you select the latest simulator as the build destination via the command line:
```bash
xcodebuild build -scheme Framework -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 4s,OS=latest'
```
There is no build failure. The solution for this (as far as I can tell) would be to have Carthage allow for a `destination` option to be specified in addition to the existing `platform` and `configuration` options, or simply to not support Xcode installs that have pre-iOS 8 simulators installed. | non_priority | carthage build fails with ios simulator installed steps to reproduce install the ios simulator in xcode create a new cocoa touch framework project in xcode run carthage build no skip current in the directory that the framework project was created in you will receive the following build error compilec invalid architecture for deployment target mios simulator version min command applications xcode app contents developer toolchains xcodedefault xctoolchain usr bin clang failed with exit code this is due to the fact that carthage as far as i can tell is running the following command during carthage build no skip current xcodebuild build scheme framework sdk iphonesimulator if you run the above command on your new framework project you will see the same build error that is produced when you run carthage build as far as i can tell the reason for this failure is that when no destination is specified in a build command xcodebuild implicitly selects a destination simulator to build for since we have the ios simulator installed it is for some reason picked as the default destination causing the above error to occur however if you select the latest simulator as the build destination via the command line bash xcodebuild build scheme framework sdk iphonesimulator destination platform ios simulator name iphone os latest there is no build failure the solution for this as far as i can tell would be to have carthage allow for a destination option to be specified in addition to the existing platform and configuration options or simply to not support xcode installs that have pre ios simulators installed | 0 |
342,074 | 30,607,469,966 | IssuesEvent | 2023-07-23 07:20:27 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | closed | Fix manipulations.test_jax_resize | NumPy Frontend Sub Task Failing Test | | | |
|---|---|
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5491105443/jobs/10007308085"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5491105443/jobs/10007308085"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5491105443/jobs/10007308085"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5491105443/jobs/10007308085"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5491105443/jobs/10007308085"><img src=https://img.shields.io/badge/-success-success></a>
| 1.0 | Fix manipulations.test_jax_resize - | | |
|---|---|
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5491105443/jobs/10007308085"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5491105443/jobs/10007308085"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5491105443/jobs/10007308085"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5491105443/jobs/10007308085"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5491105443/jobs/10007308085"><img src=https://img.shields.io/badge/-success-success></a>
| non_priority | fix manipulations test jax resize jax a href src numpy a href src tensorflow a href src torch a href src paddle a href src | 0 |
206,200 | 7,110,073,518 | IssuesEvent | 2018-01-17 09:22:40 | vanilla-framework/vanilla-framework | https://api.github.com/repos/vanilla-framework/vanilla-framework | closed | Go live: Update DNS to point docs.vanillaframework.io at the Kubernetes ingress | Priority: High Status: Blocked Type: Maintenance | I believe we control the DNS. When (and only when) we've confirmed that the Kubernetes environment is correctly able to serve docs.staging.vanillaframework.io and docs.vanillaframework.io, with correct HTTPS certificates, then we should switch over DNS to point to Kubernetes. | 1.0 | Go live: Update DNS to point docs.vanillaframework.io at the Kubernetes ingress - I believe we control the DNS. When (and only when) we've confirmed that the Kubernetes environment is correctly able to serve docs.staging.vanillaframework.io and docs.vanillaframework.io, with correct HTTPS certificates, then we should switch over DNS to point to Kubernetes. | priority | go live update dns to point docs vanillaframework io at the kubernetes ingress i believe we control the dns when and only when we ve confirmed that the kubernetes environment is correctly able to serve docs staging vanillaframework io and docs vanillaframework io with correct https certificates then we should switch over dns to point to kubernetes | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.