Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 4 112 | repo_url stringlengths 33 141 | action stringclasses 3 values | title stringlengths 1 1.02k | labels stringlengths 4 1.54k | body stringlengths 1 262k | index stringclasses 17 values | text_combine stringlengths 95 262k | label stringclasses 2 values | text stringlengths 96 252k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
184,567 | 14,289,501,554 | IssuesEvent | 2020-11-23 19:21:45 | github-vet/rangeclosure-findings | https://api.github.com/repos/github-vet/rangeclosure-findings | closed | qinguanri/iconf: deps/etcd/e2e/ctl_v3_watch_test.go; 14 LoC | fresh small test |
Found a possible issue in [qinguanri/iconf](https://www.github.com/qinguanri/iconf) at [deps/etcd/e2e/ctl_v3_watch_test.go](https://github.com/qinguanri/iconf/blob/51b3272ed5da6f2ea3a94d9197e78ef8bf441353/deps/etcd/e2e/ctl_v3_watch_test.go#L65-L78)
The below snippet of Go code triggered static analysis which searches for goroutines and/or defer statements
which capture loop variables.
[Click here to see the code in its original context.](https://github.com/qinguanri/iconf/blob/51b3272ed5da6f2ea3a94d9197e78ef8bf441353/deps/etcd/e2e/ctl_v3_watch_test.go#L65-L78)
<details>
<summary>Click here to show the 14 line(s) of Go which triggered the analyzer.</summary>
```go
for i, tt := range tests {
go func() {
for j := range tt.puts {
if err := ctlV3Put(cx, tt.puts[j].key, tt.puts[j].val, ""); err != nil {
cx.t.Fatalf("watchTest #%d-%d: ctlV3Put error (%v)", i, j, err)
}
}
}()
if err := ctlV3Watch(cx, tt.args, tt.wkv...); err != nil {
if cx.dialTimeout > 0 && !isGRPCTimedout(err) {
cx.t.Errorf("watchTest #%d: ctlV3Watch error (%v)", i, err)
}
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 51b3272ed5da6f2ea3a94d9197e78ef8bf441353
| 1.0 | qinguanri/iconf: deps/etcd/e2e/ctl_v3_watch_test.go; 14 LoC -
Found a possible issue in [qinguanri/iconf](https://www.github.com/qinguanri/iconf) at [deps/etcd/e2e/ctl_v3_watch_test.go](https://github.com/qinguanri/iconf/blob/51b3272ed5da6f2ea3a94d9197e78ef8bf441353/deps/etcd/e2e/ctl_v3_watch_test.go#L65-L78)
The below snippet of Go code triggered static analysis which searches for goroutines and/or defer statements
which capture loop variables.
[Click here to see the code in its original context.](https://github.com/qinguanri/iconf/blob/51b3272ed5da6f2ea3a94d9197e78ef8bf441353/deps/etcd/e2e/ctl_v3_watch_test.go#L65-L78)
<details>
<summary>Click here to show the 14 line(s) of Go which triggered the analyzer.</summary>
```go
for i, tt := range tests {
go func() {
for j := range tt.puts {
if err := ctlV3Put(cx, tt.puts[j].key, tt.puts[j].val, ""); err != nil {
cx.t.Fatalf("watchTest #%d-%d: ctlV3Put error (%v)", i, j, err)
}
}
}()
if err := ctlV3Watch(cx, tt.args, tt.wkv...); err != nil {
if cx.dialTimeout > 0 && !isGRPCTimedout(err) {
cx.t.Errorf("watchTest #%d: ctlV3Watch error (%v)", i, err)
}
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 51b3272ed5da6f2ea3a94d9197e78ef8bf441353
| test | qinguanri iconf deps etcd ctl watch test go loc found a possible issue in at the below snippet of go code triggered static analysis which searches for goroutines and or defer statements which capture loop variables click here to show the line s of go which triggered the analyzer go for i tt range tests go func for j range tt puts if err cx tt puts key tt puts val err nil cx t fatalf watchtest d d error v i j err if err cx tt args tt wkv err nil if cx dialtimeout isgrpctimedout err cx t errorf watchtest d error v i err leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id | 1 |
66,734 | 14,798,947,599 | IssuesEvent | 2021-01-13 01:03:15 | jtimberlake/jazz | https://api.github.com/repos/jtimberlake/jazz | opened | CVE-2020-24025 (Medium) detected in multiple libraries | security vulnerability | ## CVE-2020-24025 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.5.3.tgz</b>, <b>node-sass-4.14.1.tgz</b>, <b>node-sass-4.13.1.tgz</b></p></summary>
<p>
<details><summary><b>node-sass-4.5.3.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.5.3.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.5.3.tgz</a></p>
<p>Path to dependency file: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ngx-slimscroll/ngx-slimscroll/package.json</p>
<p>Path to vulnerable library: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/angular-library-builder/node_modules/node-sass/package.json,jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/angular-library-builder/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.5.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>node-sass-4.14.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz</a></p>
<p>Path to dependency file: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/package.json</p>
<p>Path to vulnerable library: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/node-sass/package.json,jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.7.4.tgz (Root Library)
- :x: **node-sass-4.14.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>node-sass-4.13.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz</a></p>
<p>Path to dependency file: jazz/templates/angular-website-template/app/package.json</p>
<p>Path to vulnerable library: jazz/templates/angular-website-template/app/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- build-angular-0.13.10.tgz (Root Library)
- :x: **node-sass-4.13.1.tgz** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Certificate validation in node-sass 2.0.0 to 4.14.1 is disabled when requesting binaries even if the user is not specifying an alternative download path.
<p>Publish Date: 2021-01-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-24025>CVE-2020-24025</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- 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>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.5.3","isTransitiveDependency":false,"dependencyTree":"node-sass:4.5.3","isMinimumFixVersionAvailable":false},{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.14.1","isTransitiveDependency":true,"dependencyTree":"@angular/cli:1.7.4;node-sass:4.14.1","isMinimumFixVersionAvailable":false},{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.13.1","isTransitiveDependency":true,"dependencyTree":"@angular-devkit/build-angular:0.13.10;node-sass:4.13.1","isMinimumFixVersionAvailable":false}],"vulnerabilityIdentifier":"CVE-2020-24025","vulnerabilityDetails":"Certificate validation in node-sass 2.0.0 to 4.14.1 is disabled when requesting binaries even if the user is not specifying an alternative download path.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-24025","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-24025 (Medium) detected in multiple libraries - ## CVE-2020-24025 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.5.3.tgz</b>, <b>node-sass-4.14.1.tgz</b>, <b>node-sass-4.13.1.tgz</b></p></summary>
<p>
<details><summary><b>node-sass-4.5.3.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.5.3.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.5.3.tgz</a></p>
<p>Path to dependency file: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ngx-slimscroll/ngx-slimscroll/package.json</p>
<p>Path to vulnerable library: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/angular-library-builder/node_modules/node-sass/package.json,jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/angular-library-builder/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.5.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>node-sass-4.14.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz</a></p>
<p>Path to dependency file: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/package.json</p>
<p>Path to vulnerable library: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/node-sass/package.json,jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.7.4.tgz (Root Library)
- :x: **node-sass-4.14.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>node-sass-4.13.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz</a></p>
<p>Path to dependency file: jazz/templates/angular-website-template/app/package.json</p>
<p>Path to vulnerable library: jazz/templates/angular-website-template/app/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- build-angular-0.13.10.tgz (Root Library)
- :x: **node-sass-4.13.1.tgz** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Certificate validation in node-sass 2.0.0 to 4.14.1 is disabled when requesting binaries even if the user is not specifying an alternative download path.
<p>Publish Date: 2021-01-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-24025>CVE-2020-24025</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- 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>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.5.3","isTransitiveDependency":false,"dependencyTree":"node-sass:4.5.3","isMinimumFixVersionAvailable":false},{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.14.1","isTransitiveDependency":true,"dependencyTree":"@angular/cli:1.7.4;node-sass:4.14.1","isMinimumFixVersionAvailable":false},{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.13.1","isTransitiveDependency":true,"dependencyTree":"@angular-devkit/build-angular:0.13.10;node-sass:4.13.1","isMinimumFixVersionAvailable":false}],"vulnerabilityIdentifier":"CVE-2020-24025","vulnerabilityDetails":"Certificate validation in node-sass 2.0.0 to 4.14.1 is disabled when requesting binaries even if the user is not specifying an alternative download path.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-24025","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_test | cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries node sass tgz node sass tgz node sass tgz node sass tgz wrapper around libsass library home page a href path to dependency file jazz core jazz ui src app primary components daterange picker ngx slimscroll ngx slimscroll package json path to vulnerable library jazz core jazz ui src app primary components daterange picker datepicker node modules angular library builder node modules node sass package json jazz core jazz ui src app primary components daterange picker datepicker node modules angular library builder node modules node sass package json dependency hierarchy x node sass tgz vulnerable library node sass tgz wrapper around libsass library home page a href path to dependency file jazz core jazz ui src app primary components daterange picker datepicker package json path to vulnerable library jazz core jazz ui src app primary components daterange picker datepicker node modules node sass package json jazz core jazz ui src app primary components daterange picker datepicker node modules node sass package json dependency hierarchy cli tgz root library x node sass tgz vulnerable library node sass tgz wrapper around libsass library home page a href path to dependency file jazz templates angular website template app package json path to vulnerable library jazz templates angular website template app node modules node sass package json dependency hierarchy build angular tgz root library x node sass tgz vulnerable library vulnerability details certificate validation in node sass to is disabled when requesting binaries even if the user is not specifying an alternative download path 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 low for more information on scores click a href isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails certificate validation in node sass to is disabled when requesting binaries even if the user is not specifying an alternative download path vulnerabilityurl | 0 |
142,867 | 11,497,721,431 | IssuesEvent | 2020-02-12 10:33:36 | kubernetes/kubernetes | https://api.github.com/repos/kubernetes/kubernetes | closed | [Failing Test] gce-ubuntu-master-containerd (ci-kubernetes-e2e-ubuntu-gce-containerd) | kind/failing-test priority/important-soon sig/auth sig/node | **Which jobs are failing**:
`gce-ubuntu-master-containerd (ci-kubernetes-e2e-ubuntu-gce-containerd)`
**Which test(s) are failing**:
```
[sig-auth] PodSecurityPolicy should allow pods under the privileged policy.PodSecurityPolicy
```
```
[sig-node] RuntimeClass should run a Pod requesting a RuntimeClass with a configured handler [NodeFeature:RuntimeHandler]
```
**Since when has it been failing**:
`2nd Feb 05:22 PST`
**Testgrid link**:
https://testgrid.k8s.io/sig-release-master-informing#gce-ubuntu-master-containerd
**Reason for failure**:
see https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-ubuntu-gce-containerd/1226919914875392001
**Anything else we need to know**:
/milestone v1.18
/cc @kubernetes/ci-signal
/sig auth
/sig node
/priority critical-urgent
| 1.0 | [Failing Test] gce-ubuntu-master-containerd (ci-kubernetes-e2e-ubuntu-gce-containerd) - **Which jobs are failing**:
`gce-ubuntu-master-containerd (ci-kubernetes-e2e-ubuntu-gce-containerd)`
**Which test(s) are failing**:
```
[sig-auth] PodSecurityPolicy should allow pods under the privileged policy.PodSecurityPolicy
```
```
[sig-node] RuntimeClass should run a Pod requesting a RuntimeClass with a configured handler [NodeFeature:RuntimeHandler]
```
**Since when has it been failing**:
`2nd Feb 05:22 PST`
**Testgrid link**:
https://testgrid.k8s.io/sig-release-master-informing#gce-ubuntu-master-containerd
**Reason for failure**:
see https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-ubuntu-gce-containerd/1226919914875392001
**Anything else we need to know**:
/milestone v1.18
/cc @kubernetes/ci-signal
/sig auth
/sig node
/priority critical-urgent
| test | gce ubuntu master containerd ci kubernetes ubuntu gce containerd which jobs are failing gce ubuntu master containerd ci kubernetes ubuntu gce containerd which test s are failing podsecuritypolicy should allow pods under the privileged policy podsecuritypolicy runtimeclass should run a pod requesting a runtimeclass with a configured handler since when has it been failing feb pst testgrid link reason for failure see anything else we need to know milestone cc kubernetes ci signal sig auth sig node priority critical urgent | 1 |
209,524 | 16,196,877,358 | IssuesEvent | 2021-05-04 15:33:26 | NEON-biodiversity/Ostats | https://api.github.com/repos/NEON-biodiversity/Ostats | closed | Unified documentation in Ostats() | documentation | Right now some useful documentation is spread around the different functions. But really the users will not be expected to call the internal functions. Instead they will just call Ostats(). So we should move any useful documentation to Ostats(). One example would be an explanation of how the input data should be formatted, for normal and circular data types | 1.0 | Unified documentation in Ostats() - Right now some useful documentation is spread around the different functions. But really the users will not be expected to call the internal functions. Instead they will just call Ostats(). So we should move any useful documentation to Ostats(). One example would be an explanation of how the input data should be formatted, for normal and circular data types | non_test | unified documentation in ostats right now some useful documentation is spread around the different functions but really the users will not be expected to call the internal functions instead they will just call ostats so we should move any useful documentation to ostats one example would be an explanation of how the input data should be formatted for normal and circular data types | 0 |
215,254 | 16,658,589,544 | IssuesEvent | 2021-06-06 00:39:27 | python-discord/bot | https://api.github.com/repos/python-discord/bot | opened | Unittest Parallelization & Pytest | a: tests a: tools s: planning t: feature | ## Description
Over time, this project's test suite has grown to be very large, and so too has its operation time. On my machine, the test suite currently takes about 80s to complete. You can see a full breakdown [here](https://hassanamr.dev/pydis/tests.html).
This issue proposes parallelization to help shorten the run time of tests.
## Approaches
Naturally, there are many ways to go about doing this, each with varying degrees of difficulty.
**Approach 1:** [`unittest-parallel`](https://pypi.org/project/unittest-parallel/)
unittest-parallel is a pypi plugin for unittest. It theoretically should be the least effort required to get parallelization working, yet, I could not get it to work after a lot of testing. Random tests were failing, I could not get it to work at all.
Other complaints include:
- Can't kill the test runner. No combination of `ctrl+combo` would stop the tests after they started.
- It was not faster than plain unittests from the looks of it. I obviously couldn't get the entire test suite to run, but the part that did took much longer than plain unittests.
- There were other various formatting complaints, but they'll take a lot of space, and they're completely moot if the points above are not addressed.
**Approach 2:** [`pytest-xdist`](https://pypi.org/project/pytest-xdist/)
Alright, hold your horses. Don't start typing out how terrible this idea is yet. Yes, this idea relies on pytest, but we'll get to that later. The possibility of adding pytest is a large part of this issue. Now, back to xdist:
It's a pytest plugin that parallelizes your code. I don't really have anything else to say about that. It worked really well out of the box, and I didn't run into any problems. Here are some numbers:
| Unittests | Pytest | xdist |
| -- | -- | -- |
| 79s | 71s | 45s |
## Pytest
This is the next large part of this issue. Using pytest has a few benefits, which we can get into in a second. There are two approaches however: using pytest as a runner, and using it as a framework.
**Using as a runner:**
We could use pytest exclusively to run the tests. That would give us access to pytest plugins, without requiring we use pytest. It's the least work since pytest has native support for unittest suites, and the only changes needed are installing the dependencies.
**Using as a framework:**
Alternatively, we could use pytest in full. That will give us access to all the things mentioned above, as well as other pytest features, such as fixtures. This could be a much larger job depending on how it's approached. There is no requirement to immediately refractor all old tests into pytest format, we could have a mix of both. We could stop accepting any more non-pytest test suites, and slowly update old suites as they are worked on. Not the most ideal solution because it would require maintaining two test suites, but it's an idea. | 1.0 | Unittest Parallelization & Pytest - ## Description
Over time, this project's test suite has grown to be very large, and so too has its operation time. On my machine, the test suite currently takes about 80s to complete. You can see a full breakdown [here](https://hassanamr.dev/pydis/tests.html).
This issue proposes parallelization to help shorten the run time of tests.
## Approaches
Naturally, there are many ways to go about doing this, each with varying degrees of difficulty.
**Approach 1:** [`unittest-parallel`](https://pypi.org/project/unittest-parallel/)
unittest-parallel is a pypi plugin for unittest. It theoretically should be the least effort required to get parallelization working, yet, I could not get it to work after a lot of testing. Random tests were failing, I could not get it to work at all.
Other complaints include:
- Can't kill the test runner. No combination of `ctrl+combo` would stop the tests after they started.
- It was not faster than plain unittests from the looks of it. I obviously couldn't get the entire test suite to run, but the part that did took much longer than plain unittests.
- There were other various formatting complaints, but they'll take a lot of space, and they're completely moot if the points above are not addressed.
**Approach 2:** [`pytest-xdist`](https://pypi.org/project/pytest-xdist/)
Alright, hold your horses. Don't start typing out how terrible this idea is yet. Yes, this idea relies on pytest, but we'll get to that later. The possibility of adding pytest is a large part of this issue. Now, back to xdist:
It's a pytest plugin that parallelizes your code. I don't really have anything else to say about that. It worked really well out of the box, and I didn't run into any problems. Here are some numbers:
| Unittests | Pytest | xdist |
| -- | -- | -- |
| 79s | 71s | 45s |
## Pytest
This is the next large part of this issue. Using pytest has a few benefits, which we can get into in a second. There are two approaches however: using pytest as a runner, and using it as a framework.
**Using as a runner:**
We could use pytest exclusively to run the tests. That would give us access to pytest plugins, without requiring we use pytest. It's the least work since pytest has native support for unittest suites, and the only changes needed are installing the dependencies.
**Using as a framework:**
Alternatively, we could use pytest in full. That will give us access to all the things mentioned above, as well as other pytest features, such as fixtures. This could be a much larger job depending on how it's approached. There is no requirement to immediately refractor all old tests into pytest format, we could have a mix of both. We could stop accepting any more non-pytest test suites, and slowly update old suites as they are worked on. Not the most ideal solution because it would require maintaining two test suites, but it's an idea. | test | unittest parallelization pytest description over time this project s test suite has grown to be very large and so too has its operation time on my machine the test suite currently takes about to complete you can see a full breakdown this issue proposes parallelization to help shorten the run time of tests approaches naturally there are many ways to go about doing this each with varying degrees of difficulty approach unittest parallel is a pypi plugin for unittest it theoretically should be the least effort required to get parallelization working yet i could not get it to work after a lot of testing random tests were failing i could not get it to work at all other complaints include can t kill the test runner no combination of ctrl combo would stop the tests after they started it was not faster than plain unittests from the looks of it i obviously couldn t get the entire test suite to run but the part that did took much longer than plain unittests there were other various formatting complaints but they ll take a lot of space and they re completely moot if the points above are not addressed approach alright hold your horses don t start typing out how terrible this idea is yet yes this idea relies on pytest but we ll get to that later the possibility of adding pytest is a large part of this issue now back to xdist it s a pytest plugin that parallelizes your code i don t really have anything else to say about that it worked really well out of the box and i didn t run into any problems here are some numbers unittests pytest xdist pytest this is the next large part of this issue using pytest has a few benefits which we can get into in a second there are two approaches however using pytest as a runner and using it as a framework using as a runner we could use pytest exclusively to run the tests that would give us access to pytest plugins without requiring we use pytest it s the least work since pytest has native support for unittest suites and the only changes needed are installing the dependencies using as a framework alternatively we could use pytest in full that will give us access to all the things mentioned above as well as other pytest features such as fixtures this could be a much larger job depending on how it s approached there is no requirement to immediately refractor all old tests into pytest format we could have a mix of both we could stop accepting any more non pytest test suites and slowly update old suites as they are worked on not the most ideal solution because it would require maintaining two test suites but it s an idea | 1 |
62,436 | 6,796,755,902 | IssuesEvent | 2017-11-01 20:09:04 | Microsoft/vscode | https://api.github.com/repos/Microsoft/vscode | closed | Test: Updates to Recommendation Views and extensions | extensions testplan-item | Complexity: 3
- [x] macOS @alexandrudima
- [x] Linux @aeschli
- [x] Windows @egamma
**Testing updates to File based recommendations**
- Open a folder with no Workspace Recommendations. (i.e. no `extensions.json` file in the `.vscode` folder)
- Open any java/vue/cs/python file. Corresponding extensions should get recommended via the pop up
- `Install` should open the "Recommended View" and install the extension
- `Show Recommendations` should open the "Recommended View"
- In the `Recommended View`, "Workspace Recommendations` section should be collapsed.
**Testing updates to Workspace recommendations**
- Click on the edit icon to configure workspace recommendations. (Try this in multi root mode as well)
- Save and Reload Window, you should see pop up for "Workspace Recommendations"
- `Show Recommendations` should open the "Recommended View" with the `Workspace Recommendations` view now expanded.
- Click on the download icon on the header to install all recommendations
**Testing Recommendation Indicators**
In the default view, ensure you have some recommendations. Type search text in the search box to get the recommendations in the search results
- You should be able to differentiate the recommended extension from rest of the search results due to the badge on the top left
- Hovering on the list item should display the recommendation reason
- The same reason should also appear in the extension editor which you can open by clicking on the list item
| 1.0 | Test: Updates to Recommendation Views and extensions - Complexity: 3
- [x] macOS @alexandrudima
- [x] Linux @aeschli
- [x] Windows @egamma
**Testing updates to File based recommendations**
- Open a folder with no Workspace Recommendations. (i.e. no `extensions.json` file in the `.vscode` folder)
- Open any java/vue/cs/python file. Corresponding extensions should get recommended via the pop up
- `Install` should open the "Recommended View" and install the extension
- `Show Recommendations` should open the "Recommended View"
- In the `Recommended View`, "Workspace Recommendations` section should be collapsed.
**Testing updates to Workspace recommendations**
- Click on the edit icon to configure workspace recommendations. (Try this in multi root mode as well)
- Save and Reload Window, you should see pop up for "Workspace Recommendations"
- `Show Recommendations` should open the "Recommended View" with the `Workspace Recommendations` view now expanded.
- Click on the download icon on the header to install all recommendations
**Testing Recommendation Indicators**
In the default view, ensure you have some recommendations. Type search text in the search box to get the recommendations in the search results
- You should be able to differentiate the recommended extension from rest of the search results due to the badge on the top left
- Hovering on the list item should display the recommendation reason
- The same reason should also appear in the extension editor which you can open by clicking on the list item
| test | test updates to recommendation views and extensions complexity macos alexandrudima linux aeschli windows egamma testing updates to file based recommendations open a folder with no workspace recommendations i e no extensions json file in the vscode folder open any java vue cs python file corresponding extensions should get recommended via the pop up install should open the recommended view and install the extension show recommendations should open the recommended view in the recommended view workspace recommendations section should be collapsed testing updates to workspace recommendations click on the edit icon to configure workspace recommendations try this in multi root mode as well save and reload window you should see pop up for workspace recommendations show recommendations should open the recommended view with the workspace recommendations view now expanded click on the download icon on the header to install all recommendations testing recommendation indicators in the default view ensure you have some recommendations type search text in the search box to get the recommendations in the search results you should be able to differentiate the recommended extension from rest of the search results due to the badge on the top left hovering on the list item should display the recommendation reason the same reason should also appear in the extension editor which you can open by clicking on the list item | 1 |
136,348 | 5,280,881,563 | IssuesEvent | 2017-02-07 15:16:23 | botpress/botpress | https://api.github.com/repos/botpress/botpress | closed | Integrate with Botkit | enhancement priority/urgent | Botpress lacks conversation management, we should have an easy Botkit support built-in | 1.0 | Integrate with Botkit - Botpress lacks conversation management, we should have an easy Botkit support built-in | non_test | integrate with botkit botpress lacks conversation management we should have an easy botkit support built in | 0 |
138,631 | 20,621,888,352 | IssuesEvent | 2022-03-07 18:14:02 | frnsys/half_earth | https://api.github.com/repos/frnsys/half_earth | closed | Color-coded event categories | enhancement content design | E.g.
- Social
- Ecological
- Climate
- Natural Disasters
- Food?
To accompany #45, just may make the structure of the game a bit easier to parse | 1.0 | Color-coded event categories - E.g.
- Social
- Ecological
- Climate
- Natural Disasters
- Food?
To accompany #45, just may make the structure of the game a bit easier to parse | non_test | color coded event categories e g social ecological climate natural disasters food to accompany just may make the structure of the game a bit easier to parse | 0 |
602,894 | 18,513,595,501 | IssuesEvent | 2021-10-20 07:36:28 | dot-base/fhir-server | https://api.github.com/repos/dot-base/fhir-server | opened | $history does not allow GET requests | Priority: Critical Status: Available Type: Bug | ### 🔥 Bug Description
Requesting `/api/fhir/$history` using GET returns a `405 Method Not Allowed`. Since this is a operation, designed primarily to return information, it should allow GET reqests.
### 🔍 Steps to Reproduce the Bug
1. Request `/api/fhir/$history?_type=Condition` using GET
2. Response is `405 Method Not Allowed`
### Screenshot
| 1.0 | $history does not allow GET requests - ### 🔥 Bug Description
Requesting `/api/fhir/$history` using GET returns a `405 Method Not Allowed`. Since this is a operation, designed primarily to return information, it should allow GET reqests.
### 🔍 Steps to Reproduce the Bug
1. Request `/api/fhir/$history?_type=Condition` using GET
2. Response is `405 Method Not Allowed`
### Screenshot
| non_test | history does not allow get requests 🔥 bug description requesting api fhir history using get returns a method not allowed since this is a operation designed primarily to return information it should allow get reqests 🔍 steps to reproduce the bug request api fhir history type condition using get response is method not allowed screenshot | 0 |
265,456 | 23,169,401,881 | IssuesEvent | 2022-07-30 13:17:05 | akasolace/HO | https://api.github.com/repos/akasolace/HO | closed | [BUG] Age of Players negative , Dates of HRF incorrect | reso: can't reproduce status: needs test | I upgraded from latest stable release ( 5.2.3945.2 ) to pre-release 6 ( 6.0.341.1 ).
Upgrade steps:
1) Downloaded version HO-6.0.341.1-portable-win-BETA-JRE.zip
2) Unzip file
3) copy db folder from HO5 to HO6 folder
4) open HO.exe
Age of Players are smilar to -171129
Years of date in HRF frame are like 54505 and day/month are not correct.
HO Languange IT-it
| 1.0 | [BUG] Age of Players negative , Dates of HRF incorrect - I upgraded from latest stable release ( 5.2.3945.2 ) to pre-release 6 ( 6.0.341.1 ).
Upgrade steps:
1) Downloaded version HO-6.0.341.1-portable-win-BETA-JRE.zip
2) Unzip file
3) copy db folder from HO5 to HO6 folder
4) open HO.exe
Age of Players are smilar to -171129
Years of date in HRF frame are like 54505 and day/month are not correct.
HO Languange IT-it
| test | age of players negative dates of hrf incorrect i upgraded from latest stable release to pre release upgrade steps downloaded version ho portable win beta jre zip unzip file copy db folder from to folder open ho exe age of players are smilar to years of date in hrf frame are like and day month are not correct ho languange it it | 1 |
211,612 | 16,329,526,655 | IssuesEvent | 2021-05-12 07:26:46 | ckeditor/ckeditor4 | https://api.github.com/repos/ckeditor/ckeditor4 | opened | Failing tests: /tests/plugins/clipboard/drop | browser:safari status:confirmed type:failingtest | ## Type of report
Failing test
## Provide detailed reproduction steps (if any)
Three tests of `/tests/plugins/clipboard/drop` are fails:
1. [test internal drag and drop on editors margin (framed)](tests/plugins/clipboard/drop#tests%2Fplugins%2Fclipboard%2Fdrop%20test%20internal%20drag%20and%20drop%20on%20editors%20margin%20(framed))
2. [test internal drag and drop on editors margin (inline)](ests/plugins/clipboard/drop#tests%2Fplugins%2Fclipboard%2Fdrop%20test%20internal%20drag%20and%20drop%20on%20editors%20margin%20(inline))
3. [test internal drag and drop on editors margin (divarea)](tests/plugins/clipboard/drop#tests%2Fplugins%2Fclipboard%2Fdrop%20test%20internal%20drag%20and%20drop%20on%20editors%20margin%20(divarea))
All of this tests have the same errors: <br>
`TypeError: undefined is not an object (evaluating 'a.is2')`, <br>
`Timeout: wait() called but resume() never called.`
### Expected result
*Tests passed
### Actual result
* Tests fails
## Other details
* Browser: Safari
* OS: macOs
* CKEditor version: 4.16.1
| 1.0 | Failing tests: /tests/plugins/clipboard/drop - ## Type of report
Failing test
## Provide detailed reproduction steps (if any)
Three tests of `/tests/plugins/clipboard/drop` are fails:
1. [test internal drag and drop on editors margin (framed)](tests/plugins/clipboard/drop#tests%2Fplugins%2Fclipboard%2Fdrop%20test%20internal%20drag%20and%20drop%20on%20editors%20margin%20(framed))
2. [test internal drag and drop on editors margin (inline)](ests/plugins/clipboard/drop#tests%2Fplugins%2Fclipboard%2Fdrop%20test%20internal%20drag%20and%20drop%20on%20editors%20margin%20(inline))
3. [test internal drag and drop on editors margin (divarea)](tests/plugins/clipboard/drop#tests%2Fplugins%2Fclipboard%2Fdrop%20test%20internal%20drag%20and%20drop%20on%20editors%20margin%20(divarea))
All of this tests have the same errors: <br>
`TypeError: undefined is not an object (evaluating 'a.is2')`, <br>
`Timeout: wait() called but resume() never called.`
### Expected result
*Tests passed
### Actual result
* Tests fails
## Other details
* Browser: Safari
* OS: macOs
* CKEditor version: 4.16.1
| test | failing tests tests plugins clipboard drop type of report failing test provide detailed reproduction steps if any three tests of tests plugins clipboard drop are fails tests plugins clipboard drop tests framed ests plugins clipboard drop tests inline tests plugins clipboard drop tests divarea all of this tests have the same errors typeerror undefined is not an object evaluating a timeout wait called but resume never called expected result tests passed actual result tests fails other details browser safari os macos ckeditor version | 1 |
52,764 | 6,276,652,615 | IssuesEvent | 2017-07-18 10:05:01 | gap-system/gap | https://api.github.com/repos/gap-system/gap | opened | Add tests to travis for GAP command line options | tests | I am not 100% sure how to best to this, but it might have caught the regression fixed by issue #1516, and possibly others.
Also, it would fit nicely into the idea of cleaning up the command line options, removing obsolete ones, and adding long-name alternatives to others: as always, for any refactoring I feel safer about it if there is a test suite to at least make sure there are no "obvious" regressions caused by such a refactoring. | 1.0 | Add tests to travis for GAP command line options - I am not 100% sure how to best to this, but it might have caught the regression fixed by issue #1516, and possibly others.
Also, it would fit nicely into the idea of cleaning up the command line options, removing obsolete ones, and adding long-name alternatives to others: as always, for any refactoring I feel safer about it if there is a test suite to at least make sure there are no "obvious" regressions caused by such a refactoring. | test | add tests to travis for gap command line options i am not sure how to best to this but it might have caught the regression fixed by issue and possibly others also it would fit nicely into the idea of cleaning up the command line options removing obsolete ones and adding long name alternatives to others as always for any refactoring i feel safer about it if there is a test suite to at least make sure there are no obvious regressions caused by such a refactoring | 1 |
92,098 | 8,345,357,351 | IssuesEvent | 2018-10-01 02:02:13 | thinkingmachines/linksight | https://api.github.com/repos/thinkingmachines/linksight | closed | Create staging server | dev test | - [x] Ansible playbook to setup the instance
- [x] Installs Docker and Certbot
- [x] Enables sending of emails through Mailgun
- [x] Cloud Build builds images and pushes them to Container Registry
- [x] Pull latest images and update containers thru Docker Compose
- [ ] Automate deployment | 1.0 | Create staging server - - [x] Ansible playbook to setup the instance
- [x] Installs Docker and Certbot
- [x] Enables sending of emails through Mailgun
- [x] Cloud Build builds images and pushes them to Container Registry
- [x] Pull latest images and update containers thru Docker Compose
- [ ] Automate deployment | test | create staging server ansible playbook to setup the instance installs docker and certbot enables sending of emails through mailgun cloud build builds images and pushes them to container registry pull latest images and update containers thru docker compose automate deployment | 1 |
89,254 | 11,208,275,706 | IssuesEvent | 2020-01-06 07:17:53 | ayugioh2003/today-i-learned | https://api.github.com/repos/ayugioh2003/today-i-learned | opened | 如何用 Impact Mapping & Fake Door 舉辦 Workshop 與凝聚團隊共識 | Design P-Facebook | ## 網址
* [Taiwan UI/UX Designers](https://www.facebook.com/groups/TaiwanUIUXDesigners/?multi_permalinks=1682491808559662%2C1682418425233667%2C1681746995300810%2C1681732701968906%2C1679363802205796¬if_id=1577872697042929¬if_t=group_activity)
* [如何用 Impact Mapping & Fake Door 舉辦 Workshop 與凝聚團隊共識 - Whoscall 設計師們的學習筆記 - Medium](https://medium.com/gogolook-design/%E5%A6%82%E4%BD%95%E7%94%A8-impact-mapping-fake-door-%E8%88%89%E8%BE%A6-workshop-%E8%88%87%E5%87%9D%E8%81%9A%E5%9C%98%E9%9A%8A%E5%85%B1%E8%AD%98-25dd405daded)
## 記錄原因
設計工作坊流程
## 觀念
## 學習點
## 相關資料
| 1.0 | 如何用 Impact Mapping & Fake Door 舉辦 Workshop 與凝聚團隊共識 - ## 網址
* [Taiwan UI/UX Designers](https://www.facebook.com/groups/TaiwanUIUXDesigners/?multi_permalinks=1682491808559662%2C1682418425233667%2C1681746995300810%2C1681732701968906%2C1679363802205796¬if_id=1577872697042929¬if_t=group_activity)
* [如何用 Impact Mapping & Fake Door 舉辦 Workshop 與凝聚團隊共識 - Whoscall 設計師們的學習筆記 - Medium](https://medium.com/gogolook-design/%E5%A6%82%E4%BD%95%E7%94%A8-impact-mapping-fake-door-%E8%88%89%E8%BE%A6-workshop-%E8%88%87%E5%87%9D%E8%81%9A%E5%9C%98%E9%9A%8A%E5%85%B1%E8%AD%98-25dd405daded)
## 記錄原因
設計工作坊流程
## 觀念
## 學習點
## 相關資料
| non_test | 如何用 impact mapping fake door 舉辦 workshop 與凝聚團隊共識 網址 記錄原因 設計工作坊流程 觀念 學習點 相關資料 | 0 |
175,964 | 13,621,972,977 | IssuesEvent | 2020-09-24 02:15:58 | goharbor/harbor | https://api.github.com/repos/goharbor/harbor | closed | Add artifact pull/push test in nightly upgrade tests | area/ui-test area/upgrade needs/test-case target/2.2.0 | Currently, in nightly upgrade test, only data existence verification is covered, actually, more function verification is needed as well.
| 2.0 | Add artifact pull/push test in nightly upgrade tests - Currently, in nightly upgrade test, only data existence verification is covered, actually, more function verification is needed as well.
| test | add artifact pull push test in nightly upgrade tests currently in nightly upgrade test only data existence verification is covered actually more function verification is needed as well | 1 |
106,924 | 9,197,382,083 | IssuesEvent | 2019-03-07 09:52:13 | NKCR-INPROVE/evidence.periodik | https://api.github.com/repos/NKCR-INPROVE/evidence.periodik | closed | Způsob označení mutace | ready for test | K exempláři přidat pole "Označení regionálního vydání". Toto pole bude omezeně editovatelné předpřipravenými znaky /například * nebo • nebo +/. Bude se doplňovat pouze počet těchto znaků, které budou určovat o jakou mutaci se jedná. Pod tím bude pole "Popis označení mutace", které bude volně editovatelné a bude popisovat případný zjištěný rozdíl. V přehledové tabulce bude u vydání přidáno pole "Způsob označení mutace", kde bude vložen výše uvedený znak, aby bylo vidět, čím bylo vydání popisováno. | 1.0 | Způsob označení mutace - K exempláři přidat pole "Označení regionálního vydání". Toto pole bude omezeně editovatelné předpřipravenými znaky /například * nebo • nebo +/. Bude se doplňovat pouze počet těchto znaků, které budou určovat o jakou mutaci se jedná. Pod tím bude pole "Popis označení mutace", které bude volně editovatelné a bude popisovat případný zjištěný rozdíl. V přehledové tabulce bude u vydání přidáno pole "Způsob označení mutace", kde bude vložen výše uvedený znak, aby bylo vidět, čím bylo vydání popisováno. | test | způsob označení mutace k exempláři přidat pole označení regionálního vydání toto pole bude omezeně editovatelné předpřipravenými znaky například nebo • nebo bude se doplňovat pouze počet těchto znaků které budou určovat o jakou mutaci se jedná pod tím bude pole popis označení mutace které bude volně editovatelné a bude popisovat případný zjištěný rozdíl v přehledové tabulce bude u vydání přidáno pole způsob označení mutace kde bude vložen výše uvedený znak aby bylo vidět čím bylo vydání popisováno | 1 |
143,822 | 11,580,367,870 | IssuesEvent | 2020-02-21 19:59:05 | ros-tooling/aws-oncall | https://api.github.com/repos/ros-tooling/aws-oncall | closed | All Linux Packaging jobs - ros1_bridge DynamicBridge test failures from CycloneDDS | arch - aarch64 arch - armhf arch - x86_64 platform - Ubuntu test failure | ## Overview
A few test failures from ros1_bridge around the DynamicBridge functionality
All Linux Packaging jobs - ros1_bridge DynamicBridge test failures from CycloneDDS
Only appears in the nightly packaging builds - because that's the only nightly where Cyclone and ros1_bridge are built.
## Required Information
* **Job Home**: https://ci.ros2.org/view/packaging/job/packaging_linux-aarch64/
* **First Failing Build** (or oldest/old-ish one with this issue that you can find, best effort): https://ci.ros2.org/view/packaging/job/packaging_linux-aarch64/986/
* **Latest Failing Build** (try to keep this up to date):
* **External tracking ticket**:
* https://github.com/ros2/rmw_cyclonedds/issues/72
* https://github.com/eclipse-cyclonedds/cyclonedds/issues/339 | 1.0 | All Linux Packaging jobs - ros1_bridge DynamicBridge test failures from CycloneDDS - ## Overview
A few test failures from ros1_bridge around the DynamicBridge functionality
All Linux Packaging jobs - ros1_bridge DynamicBridge test failures from CycloneDDS
Only appears in the nightly packaging builds - because that's the only nightly where Cyclone and ros1_bridge are built.
## Required Information
* **Job Home**: https://ci.ros2.org/view/packaging/job/packaging_linux-aarch64/
* **First Failing Build** (or oldest/old-ish one with this issue that you can find, best effort): https://ci.ros2.org/view/packaging/job/packaging_linux-aarch64/986/
* **Latest Failing Build** (try to keep this up to date):
* **External tracking ticket**:
* https://github.com/ros2/rmw_cyclonedds/issues/72
* https://github.com/eclipse-cyclonedds/cyclonedds/issues/339 | test | all linux packaging jobs bridge dynamicbridge test failures from cyclonedds overview a few test failures from bridge around the dynamicbridge functionality all linux packaging jobs bridge dynamicbridge test failures from cyclonedds only appears in the nightly packaging builds because that s the only nightly where cyclone and bridge are built required information job home first failing build or oldest old ish one with this issue that you can find best effort latest failing build try to keep this up to date external tracking ticket | 1 |
66,443 | 7,000,951,549 | IssuesEvent | 2017-12-18 08:16:15 | qooxdoo/qooxdoo | https://api.github.com/repos/qooxdoo/qooxdoo | opened | Some iframe related tests fail in testrunner in full run, but not if run separately | bug C:app.testrunner P:IE | All failing tests are somehow iframe related. I suspect that it has something to do with the native iframe "load" event not being fired or not bubbling up to the listeners. The problem is, that if you don't run the test completely but just start each section separately and run them in linear order, starting from "application" to "util" you won't see the tests failing which makes it horrible to debug, as it always needs a refresh and a full run til it breaks. | 1.0 | Some iframe related tests fail in testrunner in full run, but not if run separately - All failing tests are somehow iframe related. I suspect that it has something to do with the native iframe "load" event not being fired or not bubbling up to the listeners. The problem is, that if you don't run the test completely but just start each section separately and run them in linear order, starting from "application" to "util" you won't see the tests failing which makes it horrible to debug, as it always needs a refresh and a full run til it breaks. | test | some iframe related tests fail in testrunner in full run but not if run separately all failing tests are somehow iframe related i suspect that it has something to do with the native iframe load event not being fired or not bubbling up to the listeners the problem is that if you don t run the test completely but just start each section separately and run them in linear order starting from application to util you won t see the tests failing which makes it horrible to debug as it always needs a refresh and a full run til it breaks | 1 |
78,568 | 15,586,036,388 | IssuesEvent | 2021-03-18 01:01:37 | TreyM-WSS/togglr-api | https://api.github.com/repos/TreyM-WSS/togglr-api | opened | CVE-2020-36184 (Medium) detected in jackson-databind-2.9.9.jar | security vulnerability | ## CVE-2020-36184 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.9.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: togglr-api/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.9/jackson-databind-2.9.9.jar</p>
<p>
Dependency Hierarchy:
- jjwt-0.6.0.jar (Root Library)
- :x: **jackson-databind-2.9.9.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp2.datasources.PerUserPoolDataSource.
<p>Publish Date: 2021-01-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36184>CVE-2020-36184</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>6.8</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: Change files</p>
<p>Origin: <a href="https://github.com/FasterXML/jackson-databind/commit/567194c53ae91f0a14dc27239afb739b1c10448a">https://github.com/FasterXML/jackson-databind/commit/567194c53ae91f0a14dc27239afb739b1c10448a</a></p>
<p>Release Date: 2020-12-26</p>
<p>Fix Resolution: Replace or update the following files: SubTypeValidator.java, VERSION-2.x</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.9.9","packageFilePaths":["/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"io.jsonwebtoken:jjwt:0.6.0;com.fasterxml.jackson.core:jackson-databind:2.9.9","isMinimumFixVersionAvailable":false}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2020-36184","vulnerabilityDetails":"FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp2.datasources.PerUserPoolDataSource.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36184","cvss2Severity":"medium","cvss2Score":"6.8","extraData":{}}</REMEDIATE> --> | True | CVE-2020-36184 (Medium) detected in jackson-databind-2.9.9.jar - ## CVE-2020-36184 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.9.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: togglr-api/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.9/jackson-databind-2.9.9.jar</p>
<p>
Dependency Hierarchy:
- jjwt-0.6.0.jar (Root Library)
- :x: **jackson-databind-2.9.9.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp2.datasources.PerUserPoolDataSource.
<p>Publish Date: 2021-01-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36184>CVE-2020-36184</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>6.8</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: Change files</p>
<p>Origin: <a href="https://github.com/FasterXML/jackson-databind/commit/567194c53ae91f0a14dc27239afb739b1c10448a">https://github.com/FasterXML/jackson-databind/commit/567194c53ae91f0a14dc27239afb739b1c10448a</a></p>
<p>Release Date: 2020-12-26</p>
<p>Fix Resolution: Replace or update the following files: SubTypeValidator.java, VERSION-2.x</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.9.9","packageFilePaths":["/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"io.jsonwebtoken:jjwt:0.6.0;com.fasterxml.jackson.core:jackson-databind:2.9.9","isMinimumFixVersionAvailable":false}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2020-36184","vulnerabilityDetails":"FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp2.datasources.PerUserPoolDataSource.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36184","cvss2Severity":"medium","cvss2Score":"6.8","extraData":{}}</REMEDIATE> --> | non_test | cve medium detected in jackson databind jar cve medium severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file togglr api pom xml path to vulnerable library home wss scanner repository com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy jjwt jar root library x jackson databind jar vulnerable library vulnerability details fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to org apache tomcat dbcp datasources peruserpooldatasource publish date url a href cvss score details base score metrics not available suggested fix type change files origin a href release date fix resolution replace or update the following files subtypevalidator java version x isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree io jsonwebtoken jjwt com fasterxml jackson core jackson databind isminimumfixversionavailable false basebranches vulnerabilityidentifier cve vulnerabilitydetails fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to org apache tomcat dbcp datasources peruserpooldatasource vulnerabilityurl | 0 |
42,195 | 2,869,280,141 | IssuesEvent | 2015-06-06 02:02:05 | PredictiveEcology/SpaDES | https://api.github.com/repos/PredictiveEcology/SpaDES | closed | test that simulations can be resumed by changing stop time | Medium priority | In theory, this should work:
mySim <- simInit(...) # using stop time = 10
mySim <- spades(mySim)
simStopTime(mySim) <- 100
spades(mySim) # should continue the simulation from time 10 to 100
Need to:
1. make sure it DOES work
2. create unit test for this feature
| 1.0 | test that simulations can be resumed by changing stop time - In theory, this should work:
mySim <- simInit(...) # using stop time = 10
mySim <- spades(mySim)
simStopTime(mySim) <- 100
spades(mySim) # should continue the simulation from time 10 to 100
Need to:
1. make sure it DOES work
2. create unit test for this feature
| non_test | test that simulations can be resumed by changing stop time in theory this should work mysim siminit using stop time mysim spades mysim simstoptime mysim spades mysim should continue the simulation from time to need to make sure it does work create unit test for this feature | 0 |
759,777 | 26,610,284,524 | IssuesEvent | 2023-01-23 23:16:43 | googleapis/google-api-dotnet-client | https://api.github.com/repos/googleapis/google-api-dotnet-client | closed | Crash when trying to use AddGoogleOpenIdConnect | type: question needs more info priority: p3 | Hi, I'm trying to add a Google Auth button to my website which is based on a React SPA using @react-oauth/google + a dotnet 7 API using Google.Apis.Auth.AspNetCore3.
Something doesn't seems to quite work and I don't understand why.
My current flow is this:
spa get an auth code and send it to api.
api exchange it for token and send back the token_id (jwt)
spa start using this token id as Authorization Header (with GoogleOpenIdConnect scheme)
I'm expecting at that stage to get api to handle the token. (maybe i don't understand what it's supposed to do ?)
additionally without even having the spa I just get a crash from some kind of infinite loop as soon as I open a page:
```
public class Program
{
public static void Main(string[] args)
{
BuildWebHost(args).Run();
}
public static IWebHost BuildWebHost(string[] args)
{
return WebHost.CreateDefaultBuilder(args)
.UseStartup<Startup>()
.Build();
}
}
public class HomeController : Controller
{
public IActionResult Index()
{
return Json("index");
}
}
public class Startup
{
public void ConfigureServices(IServiceCollection services)
{
services.AddControllers();
services.AddAuthentication()
.AddGoogleOpenIdConnect(options =>
{
options.ClientId = "CLIENT_ID";
options.ClientSecret = "CLIENT_SECRET";
});
}
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
app.UseRouting();
app.UseAuthentication();
app.UseEndpoints(endpoints =>
{
endpoints.MapControllers();
endpoints.MapControllerRoute("default", "{controller=Default}/{action=Index}");
});
}
}
```
Opening the page https://localhost:5001 is just making it crash.
<details>
<summary>stacktrace is too big for my console but here parts of what I get</summary>
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<HandleAuthenticateAsync>d__13<System.__Canon> ByRef)
at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].HandleAuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__48<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__48<System.__Canon> ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].AuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14, Microsoft.AspNetCore.Authentication.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__14 ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14, Microsoft.AspNetCore.Authentication.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__14 ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationService.AuthenticateAsync(Microsoft.AspNetCore.Http.HttpContext, System.String)
at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<HandleAuthenticateAsync>d__13<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<HandleAuthenticateAsync>d__13<System.__Canon> ByRef)
at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].HandleAuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__48<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__48<System.__Canon> ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].AuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14, Microsoft.AspNetCore.Authentication.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__14 ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14, Microsoft.AspNetCore.Authentication.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__14 ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationService.AuthenticateAsync(Microsoft.AspNetCore.Http.HttpContext, System.String)
at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<HandleAuthenticateAsync>d__13<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<HandleAuthenticateAsync>d__13<System.__Canon> ByRef)
at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].HandleAuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__48<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__48<System.__Canon> ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].AuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14, Microsoft.AspNetCore.Authentication.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__14 ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14, Microsoft.AspNetCore.Authentication.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__14 ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationService.AuthenticateAsync(Microsoft.AspNetCore.Http.HttpContext, System.String)
at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<HandleAuthenticateAsync>d__13<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<HandleAuthenticateAsync>d__13<System.__Canon> ByRef)
at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].HandleAuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__48<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__48<System.__Canon> ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].AuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14, Microsoft.AspNetCore.Authentication.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__14 ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14, Microsoft.AspNetCore.Authentication.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__14 ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationService.AuthenticateAsync(Microsoft.AspNetCore.Http.HttpContext, System.String)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware+<Invoke>d__6.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationMiddleware+<Invoke>d__6, Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<Invoke>d__6 ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[[Microsoft.AspNetCore.Authentication.AuthenticationMiddleware+<Invoke>d__6, Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<Invoke>d__6 ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(Microsoft.AspNetCore.Http.HttpContext)
at Microsoft.WebTools.BrowserLink.Net.BrowserLinkMiddleware+<ExecuteWithFilterAsync>d__9.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.WebTools.BrowserLink.Net.BrowserLinkMiddleware+<ExecuteWithFilterAsync>d__9, Microsoft.WebTools.BrowserLink.Net, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]](<ExecuteWithFilterAsync>d__9 ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[[Microsoft.WebTools.BrowserLink.Net.BrowserLinkMiddleware+<ExecuteWithFilterAsync>d__9, Microsoft.WebTools.BrowserLink.Net, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]](<ExecuteWithFilterAsync>d__9 ByRef)
at Microsoft.WebTools.BrowserLink.Net.BrowserLinkMiddleware.ExecuteWithFilterAsync(Microsoft.WebTools.BrowserLink.Net.IHttpSocketAdapter, System.String, Microsoft.AspNetCore.Http.HttpContext)
at Microsoft.WebTools.BrowserLink.Net.BrowserLinkMiddleware.InvokeAsync(Microsoft.AspNetCore.Http.HttpContext)
at Microsoft.WebTools.BrowserLink.Net.VsContentMiddleware.InvokeAsync(Microsoft.AspNetCore.Http.HttpContext)
at Microsoft.AspNetCore.Watch.BrowserRefresh.BrowserRefreshMiddleware+<InvokeAsync>d__4.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Watch.BrowserRefresh.BrowserRefreshMiddleware+<InvokeAsync>d__4, Microsoft.AspNetCore.Watch.BrowserRefresh, Version=7.0.102.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<InvokeAsync>d__4 ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[[Microsoft.AspNetCore.Watch.BrowserRefresh.BrowserRefreshMiddleware+<InvokeAsync>d__4, Microsoft.AspNetCore.Watch.BrowserRefresh, Version=7.0.102.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<InvokeAsync>d__4 ByRef)
at Microsoft.AspNetCore.Watch.BrowserRefresh.BrowserRefreshMiddleware.InvokeAsync(Microsoft.AspNetCore.Http.HttpContext)
at Microsoft.AspNetCore.HostFiltering.HostFilteringMiddleware.Invoke(Microsoft.AspNetCore.Http.HttpContext)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol+<ProcessRequests>d__238`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol+<ProcessRequests>d__238`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Server.Kestrel.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<ProcessRequests>d__238`1<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[[Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol+<ProcessRequests>d__238`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Server.Kestrel.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<ProcessRequests>d__238`1<System.__Canon> ByRef)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]](Microsoft.AspNetCore.Hosting.Server.IHttpApplication`1<System.__Canon>)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol+<ProcessRequestsAsync>d__237`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol+<ProcessRequestsAsync>d__237`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Server.Kestrel.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<ProcessRequestsAsync>d__237`1<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[[Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol+<ProcessRequestsAsync>d__237`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Server.Kestrel.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<ProcessRequestsAsync>d__237`1<System.__Canon> ByRef)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequestsAsync[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]](Microsoft.AspNetCore.Hosting.Server.IHttpApplication`1<System.__Canon>)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http2.Http2Stream`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Execute()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading.PortableThreadPool+WorkerThread.WorkerThreadStart()
</details>
| 1.0 | Crash when trying to use AddGoogleOpenIdConnect - Hi, I'm trying to add a Google Auth button to my website which is based on a React SPA using @react-oauth/google + a dotnet 7 API using Google.Apis.Auth.AspNetCore3.
Something doesn't seems to quite work and I don't understand why.
My current flow is this:
spa get an auth code and send it to api.
api exchange it for token and send back the token_id (jwt)
spa start using this token id as Authorization Header (with GoogleOpenIdConnect scheme)
I'm expecting at that stage to get api to handle the token. (maybe i don't understand what it's supposed to do ?)
additionally without even having the spa I just get a crash from some kind of infinite loop as soon as I open a page:
```
public class Program
{
public static void Main(string[] args)
{
BuildWebHost(args).Run();
}
public static IWebHost BuildWebHost(string[] args)
{
return WebHost.CreateDefaultBuilder(args)
.UseStartup<Startup>()
.Build();
}
}
public class HomeController : Controller
{
public IActionResult Index()
{
return Json("index");
}
}
public class Startup
{
public void ConfigureServices(IServiceCollection services)
{
services.AddControllers();
services.AddAuthentication()
.AddGoogleOpenIdConnect(options =>
{
options.ClientId = "CLIENT_ID";
options.ClientSecret = "CLIENT_SECRET";
});
}
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
app.UseRouting();
app.UseAuthentication();
app.UseEndpoints(endpoints =>
{
endpoints.MapControllers();
endpoints.MapControllerRoute("default", "{controller=Default}/{action=Index}");
});
}
}
```
Opening the page https://localhost:5001 is just making it crash.
<details>
<summary>stacktrace is too big for my console but here parts of what I get</summary>
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<HandleAuthenticateAsync>d__13<System.__Canon> ByRef)
at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].HandleAuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__48<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__48<System.__Canon> ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].AuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14, Microsoft.AspNetCore.Authentication.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__14 ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14, Microsoft.AspNetCore.Authentication.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__14 ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationService.AuthenticateAsync(Microsoft.AspNetCore.Http.HttpContext, System.String)
at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<HandleAuthenticateAsync>d__13<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<HandleAuthenticateAsync>d__13<System.__Canon> ByRef)
at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].HandleAuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__48<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__48<System.__Canon> ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].AuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14, Microsoft.AspNetCore.Authentication.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__14 ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14, Microsoft.AspNetCore.Authentication.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__14 ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationService.AuthenticateAsync(Microsoft.AspNetCore.Http.HttpContext, System.String)
at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<HandleAuthenticateAsync>d__13<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<HandleAuthenticateAsync>d__13<System.__Canon> ByRef)
at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].HandleAuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__48<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__48<System.__Canon> ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].AuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14, Microsoft.AspNetCore.Authentication.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__14 ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14, Microsoft.AspNetCore.Authentication.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__14 ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationService.AuthenticateAsync(Microsoft.AspNetCore.Http.HttpContext, System.String)
at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<HandleAuthenticateAsync>d__13<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1+<HandleAuthenticateAsync>d__13[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<HandleAuthenticateAsync>d__13<System.__Canon> ByRef)
at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].HandleAuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__48<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.AuthenticationHandler`1+<AuthenticateAsync>d__48[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__48<System.__Canon> ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationHandler`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].AuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14, Microsoft.AspNetCore.Authentication.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__14 ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.AspNetCore.Authentication.AuthenticationService+<AuthenticateAsync>d__14, Microsoft.AspNetCore.Authentication.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<AuthenticateAsync>d__14 ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationService.AuthenticateAsync(Microsoft.AspNetCore.Http.HttpContext, System.String)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware+<Invoke>d__6.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Authentication.AuthenticationMiddleware+<Invoke>d__6, Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<Invoke>d__6 ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[[Microsoft.AspNetCore.Authentication.AuthenticationMiddleware+<Invoke>d__6, Microsoft.AspNetCore.Authentication, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<Invoke>d__6 ByRef)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(Microsoft.AspNetCore.Http.HttpContext)
at Microsoft.WebTools.BrowserLink.Net.BrowserLinkMiddleware+<ExecuteWithFilterAsync>d__9.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.WebTools.BrowserLink.Net.BrowserLinkMiddleware+<ExecuteWithFilterAsync>d__9, Microsoft.WebTools.BrowserLink.Net, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]](<ExecuteWithFilterAsync>d__9 ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[[Microsoft.WebTools.BrowserLink.Net.BrowserLinkMiddleware+<ExecuteWithFilterAsync>d__9, Microsoft.WebTools.BrowserLink.Net, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]](<ExecuteWithFilterAsync>d__9 ByRef)
at Microsoft.WebTools.BrowserLink.Net.BrowserLinkMiddleware.ExecuteWithFilterAsync(Microsoft.WebTools.BrowserLink.Net.IHttpSocketAdapter, System.String, Microsoft.AspNetCore.Http.HttpContext)
at Microsoft.WebTools.BrowserLink.Net.BrowserLinkMiddleware.InvokeAsync(Microsoft.AspNetCore.Http.HttpContext)
at Microsoft.WebTools.BrowserLink.Net.VsContentMiddleware.InvokeAsync(Microsoft.AspNetCore.Http.HttpContext)
at Microsoft.AspNetCore.Watch.BrowserRefresh.BrowserRefreshMiddleware+<InvokeAsync>d__4.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Watch.BrowserRefresh.BrowserRefreshMiddleware+<InvokeAsync>d__4, Microsoft.AspNetCore.Watch.BrowserRefresh, Version=7.0.102.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<InvokeAsync>d__4 ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[[Microsoft.AspNetCore.Watch.BrowserRefresh.BrowserRefreshMiddleware+<InvokeAsync>d__4, Microsoft.AspNetCore.Watch.BrowserRefresh, Version=7.0.102.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<InvokeAsync>d__4 ByRef)
at Microsoft.AspNetCore.Watch.BrowserRefresh.BrowserRefreshMiddleware.InvokeAsync(Microsoft.AspNetCore.Http.HttpContext)
at Microsoft.AspNetCore.HostFiltering.HostFilteringMiddleware.Invoke(Microsoft.AspNetCore.Http.HttpContext)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol+<ProcessRequests>d__238`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol+<ProcessRequests>d__238`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Server.Kestrel.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<ProcessRequests>d__238`1<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[[Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol+<ProcessRequests>d__238`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Server.Kestrel.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<ProcessRequests>d__238`1<System.__Canon> ByRef)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]](Microsoft.AspNetCore.Hosting.Server.IHttpApplication`1<System.__Canon>)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol+<ProcessRequestsAsync>d__237`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol+<ProcessRequestsAsync>d__237`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Server.Kestrel.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<ProcessRequestsAsync>d__237`1<System.__Canon> ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[[Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol+<ProcessRequestsAsync>d__237`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], Microsoft.AspNetCore.Server.Kestrel.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<ProcessRequestsAsync>d__237`1<System.__Canon> ByRef)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequestsAsync[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]](Microsoft.AspNetCore.Hosting.Server.IHttpApplication`1<System.__Canon>)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http2.Http2Stream`1[[System.__Canon, System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Execute()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading.PortableThreadPool+WorkerThread.WorkerThreadStart()
</details>
| non_test | crash when trying to use addgoogleopenidconnect hi i m trying to add a google auth button to my website which is based on a react spa using react oauth google a dotnet api using google apis auth something doesn t seems to quite work and i don t understand why my current flow is this spa get an auth code and send it to api api exchange it for token and send back the token id jwt spa start using this token id as authorization header with googleopenidconnect scheme i m expecting at that stage to get api to handle the token maybe i don t understand what it s supposed to do additionally without even having the spa i just get a crash from some kind of infinite loop as soon as i open a page public class program public static void main string args buildwebhost args run public static iwebhost buildwebhost string args return webhost createdefaultbuilder args usestartup build public class homecontroller controller public iactionresult index return json index public class startup public void configureservices iservicecollection services services addcontrollers services addauthentication addgoogleopenidconnect options options clientid client id options clientsecret client secret public void configure iapplicationbuilder app ihostingenvironment env app userouting app useauthentication app useendpoints endpoints endpoints mapcontrollers endpoints mapcontrollerroute default controller default action index opening the page is just making it crash stacktrace is too big for my console but here parts of what i get at system runtime compilerservices asynctaskmethodbuilder start microsoft aspnetcore authentication version culture neutral publickeytoken d byref at microsoft aspnetcore authentication remoteauthenticationhandler handleauthenticateasync at microsoft aspnetcore authentication authenticationhandler d movenext at system runtime compilerservices asyncmethodbuildercore start microsoft aspnetcore authentication version culture neutral publickeytoken d byref at system runtime compilerservices asynctaskmethodbuilder start microsoft aspnetcore authentication version culture neutral publickeytoken d byref at microsoft aspnetcore authentication authenticationhandler authenticateasync at microsoft aspnetcore authentication authenticationservice d movenext at system runtime compilerservices asyncmethodbuildercore start d byref at system runtime compilerservices asynctaskmethodbuilder start d byref at microsoft aspnetcore authentication authenticationservice authenticateasync microsoft aspnetcore http httpcontext system string at microsoft aspnetcore authentication remoteauthenticationhandler d movenext at system runtime compilerservices asyncmethodbuildercore start microsoft aspnetcore authentication version culture neutral publickeytoken d byref at system runtime compilerservices asynctaskmethodbuilder start microsoft aspnetcore authentication version culture neutral publickeytoken d byref at microsoft aspnetcore authentication remoteauthenticationhandler handleauthenticateasync at microsoft aspnetcore authentication authenticationhandler d movenext at system runtime compilerservices asyncmethodbuildercore start microsoft aspnetcore authentication version culture neutral publickeytoken d byref at system runtime compilerservices asynctaskmethodbuilder start microsoft aspnetcore authentication version culture neutral publickeytoken d byref at microsoft aspnetcore authentication authenticationhandler authenticateasync at microsoft aspnetcore authentication authenticationservice d movenext at system runtime compilerservices asyncmethodbuildercore start d byref at system runtime compilerservices asynctaskmethodbuilder start d byref at microsoft aspnetcore authentication authenticationservice authenticateasync microsoft aspnetcore http httpcontext system string at microsoft aspnetcore authentication remoteauthenticationhandler d movenext at system runtime compilerservices asyncmethodbuildercore start microsoft aspnetcore authentication version culture neutral publickeytoken d byref at system runtime compilerservices asynctaskmethodbuilder start microsoft aspnetcore authentication version culture neutral publickeytoken d byref at microsoft aspnetcore authentication remoteauthenticationhandler handleauthenticateasync at microsoft aspnetcore authentication authenticationhandler d movenext at system runtime compilerservices asyncmethodbuildercore start microsoft aspnetcore authentication version culture neutral publickeytoken d byref at system runtime compilerservices asynctaskmethodbuilder start microsoft aspnetcore authentication version culture neutral publickeytoken d byref at microsoft aspnetcore authentication authenticationhandler authenticateasync at microsoft aspnetcore authentication authenticationservice d movenext at system runtime compilerservices asyncmethodbuildercore start d byref at system runtime compilerservices asynctaskmethodbuilder start d byref at microsoft aspnetcore authentication authenticationservice authenticateasync microsoft aspnetcore http httpcontext system string at microsoft aspnetcore authentication remoteauthenticationhandler d movenext at system runtime compilerservices asyncmethodbuildercore start microsoft aspnetcore authentication version culture neutral publickeytoken d byref at system runtime compilerservices asynctaskmethodbuilder start microsoft aspnetcore authentication version culture neutral publickeytoken d byref at microsoft aspnetcore authentication remoteauthenticationhandler handleauthenticateasync at microsoft aspnetcore authentication authenticationhandler d movenext at system runtime compilerservices asyncmethodbuildercore start microsoft aspnetcore authentication version culture neutral publickeytoken d byref at system runtime compilerservices asynctaskmethodbuilder start microsoft aspnetcore authentication version culture neutral publickeytoken d byref at microsoft aspnetcore authentication authenticationhandler authenticateasync at microsoft aspnetcore authentication authenticationservice d movenext at system runtime compilerservices asyncmethodbuildercore start d byref at system runtime compilerservices asynctaskmethodbuilder start d byref at microsoft aspnetcore authentication authenticationservice authenticateasync microsoft aspnetcore http httpcontext system string at microsoft aspnetcore authentication authenticationmiddleware d movenext at system runtime compilerservices asyncmethodbuildercore start d byref at system runtime compilerservices asynctaskmethodbuilder start d byref at microsoft aspnetcore authentication authenticationmiddleware invoke microsoft aspnetcore http httpcontext at microsoft webtools browserlink net browserlinkmiddleware d movenext at system runtime compilerservices asyncmethodbuildercore start d byref at system runtime compilerservices asynctaskmethodbuilder start d byref at microsoft webtools browserlink net browserlinkmiddleware executewithfilterasync microsoft webtools browserlink net ihttpsocketadapter system string microsoft aspnetcore http httpcontext at microsoft webtools browserlink net browserlinkmiddleware invokeasync microsoft aspnetcore http httpcontext at microsoft webtools browserlink net vscontentmiddleware invokeasync microsoft aspnetcore http httpcontext at microsoft aspnetcore watch browserrefresh browserrefreshmiddleware d movenext at system runtime compilerservices asyncmethodbuildercore start d byref at system runtime compilerservices asynctaskmethodbuilder start d byref at microsoft aspnetcore watch browserrefresh browserrefreshmiddleware invokeasync microsoft aspnetcore http httpcontext at microsoft aspnetcore hostfiltering hostfilteringmiddleware invoke microsoft aspnetcore http httpcontext at microsoft aspnetcore server kestrel core internal http httpprotocol d movenext at system runtime compilerservices asyncmethodbuildercore start microsoft aspnetcore server kestrel core version culture neutral publickeytoken d byref at system runtime compilerservices asynctaskmethodbuilder start microsoft aspnetcore server kestrel core version culture neutral publickeytoken d byref at microsoft aspnetcore server kestrel core internal http httpprotocol processrequests microsoft aspnetcore hosting server ihttpapplication at microsoft aspnetcore server kestrel core internal http httpprotocol d movenext at system runtime compilerservices asyncmethodbuildercore start microsoft aspnetcore server kestrel core version culture neutral publickeytoken d byref at system runtime compilerservices asynctaskmethodbuilder start microsoft aspnetcore server kestrel core version culture neutral publickeytoken d byref at microsoft aspnetcore server kestrel core internal http httpprotocol processrequestsasync microsoft aspnetcore hosting server ihttpapplication at microsoft aspnetcore server kestrel core internal execute at system threading threadpoolworkqueue dispatch at system threading portablethreadpool workerthread workerthreadstart | 0 |
31,832 | 6,008,726,463 | IssuesEvent | 2017-06-06 08:41:12 | open-contracting/standard | https://api.github.com/repos/open-contracting/standard | closed | Documentation on updating final value and completion date | 1 - Discussion Focus - Core Focus - Documentation | From Mihaly:
> I would recommend introducing 'double accounting' for the most crucial bits of information prone to error and corruption. Final value and completion date are two obvious candidates. So having them visibly there rather than implicitly among transactions and milestones makes hiding more difficult in addition to allowing for cross-checking records.
<!---
@huboard:{"order":147.0,"milestone_order":147.0,"custom_state":"ready"}
-->
| 1.0 | Documentation on updating final value and completion date - From Mihaly:
> I would recommend introducing 'double accounting' for the most crucial bits of information prone to error and corruption. Final value and completion date are two obvious candidates. So having them visibly there rather than implicitly among transactions and milestones makes hiding more difficult in addition to allowing for cross-checking records.
<!---
@huboard:{"order":147.0,"milestone_order":147.0,"custom_state":"ready"}
-->
| non_test | documentation on updating final value and completion date from mihaly i would recommend introducing double accounting for the most crucial bits of information prone to error and corruption final value and completion date are two obvious candidates so having them visibly there rather than implicitly among transactions and milestones makes hiding more difficult in addition to allowing for cross checking records huboard order milestone order custom state ready | 0 |
160,758 | 6,101,960,987 | IssuesEvent | 2017-06-20 15:33:09 | openshift/origin-web-console | https://api.github.com/repos/openshift/origin-web-console | closed | Deleting a binding for a secret does a flip-flop on the results step | kind/bug priority/P2 | Starts as a secret:
Magically turns into a binding:
I have now deleted a binding for a binding and confused myself. ☹️
Re: PR #1705
| 1.0 | Deleting a binding for a secret does a flip-flop on the results step - Starts as a secret:
Magically turns into a binding:
I have now deleted a binding for a binding and confused myself. ☹️
Re: PR #1705
| non_test | deleting a binding for a secret does a flip flop on the results step starts as a secret magically turns into a binding i have now deleted a binding for a binding and confused myself ☹️ re pr | 0 |
342,516 | 30,625,423,683 | IssuesEvent | 2023-07-24 11:08:04 | heroku/libcnb.rs | https://api.github.com/repos/heroku/libcnb.rs | opened | libcnb-test: `ContainerConfig::expose_port` exposes ports to the internet | bug libcnb-test | The `ContainerConfig::expose_port` exposes ports on the started container to the host machine.
Currently libcnb-test does not set a `host_ip` in the corresponding `PortBinding`:
https://github.com/heroku/libcnb.rs/blob/95c2e8164e1382f6da0be72dd99777c12f39f091/libcnb-test/src/container_port_mapping.rs#L82
https://docs.rs/bollard/latest/bollard/models/struct.PortBinding.html
The Bollard docs don't say what this implies, however, the Docker run docs say:
> Note that ports which are not bound to the host (i.e., -p 80:80 instead of -p 127.0.0.1:80:80) are externally accessible.
(on https://docs.docker.com/engine/reference/commandline/run/#publish)
And on the networking page:
> Publishing container ports is insecure by default. Meaning, when you publish a container’s ports it becomes available not only to the Docker host, but to the outside world as well.
>
> If you include the localhost IP address (127.0.0.1) with the publish flag, only the Docker host can access the published container port.
(on https://docs.docker.com/network/#published-ports)
We should set the `host_ip` to 127.0.0.1, so that ports are only exposed to localhost, and not the internet.
Plus IMO this is another example of how using Bollard makes it harder for us to understand what's going on, since Bollard's docs don't mention this pitfall, and it's not necessarily obvious at first glance how `PortBinding` works by default. | 1.0 | libcnb-test: `ContainerConfig::expose_port` exposes ports to the internet - The `ContainerConfig::expose_port` exposes ports on the started container to the host machine.
Currently libcnb-test does not set a `host_ip` in the corresponding `PortBinding`:
https://github.com/heroku/libcnb.rs/blob/95c2e8164e1382f6da0be72dd99777c12f39f091/libcnb-test/src/container_port_mapping.rs#L82
https://docs.rs/bollard/latest/bollard/models/struct.PortBinding.html
The Bollard docs don't say what this implies, however, the Docker run docs say:
> Note that ports which are not bound to the host (i.e., -p 80:80 instead of -p 127.0.0.1:80:80) are externally accessible.
(on https://docs.docker.com/engine/reference/commandline/run/#publish)
And on the networking page:
> Publishing container ports is insecure by default. Meaning, when you publish a container’s ports it becomes available not only to the Docker host, but to the outside world as well.
>
> If you include the localhost IP address (127.0.0.1) with the publish flag, only the Docker host can access the published container port.
(on https://docs.docker.com/network/#published-ports)
We should set the `host_ip` to 127.0.0.1, so that ports are only exposed to localhost, and not the internet.
Plus IMO this is another example of how using Bollard makes it harder for us to understand what's going on, since Bollard's docs don't mention this pitfall, and it's not necessarily obvious at first glance how `PortBinding` works by default. | test | libcnb test containerconfig expose port exposes ports to the internet the containerconfig expose port exposes ports on the started container to the host machine currently libcnb test does not set a host ip in the corresponding portbinding the bollard docs don t say what this implies however the docker run docs say note that ports which are not bound to the host i e p instead of p are externally accessible on and on the networking page publishing container ports is insecure by default meaning when you publish a container’s ports it becomes available not only to the docker host but to the outside world as well if you include the localhost ip address with the publish flag only the docker host can access the published container port on we should set the host ip to so that ports are only exposed to localhost and not the internet plus imo this is another example of how using bollard makes it harder for us to understand what s going on since bollard s docs don t mention this pitfall and it s not necessarily obvious at first glance how portbinding works by default | 1 |
323,363 | 27,718,249,548 | IssuesEvent | 2023-03-14 18:26:18 | gravitee-io/issues | https://api.github.com/repos/gravitee-io/issues | closed | [API test] Create an API with Key-Plan with a 'general conditions' markdown page | project: APIM Test Automation | Use-case test for API Management:
As an API publisher, I want to create simple API with API-Key plan > Create markdown page with "General conditions" for that API. Then set the previously created page as "General conditions" page in the plan.
(UC-APIM57) | 1.0 | [API test] Create an API with Key-Plan with a 'general conditions' markdown page - Use-case test for API Management:
As an API publisher, I want to create simple API with API-Key plan > Create markdown page with "General conditions" for that API. Then set the previously created page as "General conditions" page in the plan.
(UC-APIM57) | test | create an api with key plan with a general conditions markdown page use case test for api management as an api publisher i want to create simple api with api key plan create markdown page with general conditions for that api then set the previously created page as general conditions page in the plan uc | 1 |
479,386 | 13,795,650,187 | IssuesEvent | 2020-10-09 18:23:48 | vanjarosoftware/Vanjaro.Platform | https://api.github.com/repos/vanjarosoftware/Vanjaro.Platform | closed | Add resource file in Authentication package | Area: Backend Priority: High Release: Minor | extract in file in below path
DesktopModules\AuthenticationServices\Vanjaro\App_LocalResources | 1.0 | Add resource file in Authentication package - extract in file in below path
DesktopModules\AuthenticationServices\Vanjaro\App_LocalResources | non_test | add resource file in authentication package extract in file in below path desktopmodules authenticationservices vanjaro app localresources | 0 |
123,108 | 10,253,706,504 | IssuesEvent | 2019-08-21 11:58:42 | ballerina-platform/ballerina-lang | https://api.github.com/repos/ballerina-platform/ballerina-lang | closed | Formatting breaks for UNI-Code symbols | Area/Tooling BetaTesting Component/Formatting Component/LanguageServer Priority/Blocker Type/Bug | **Description:**
Formatting breaks for UNI-Code symbols.
**Before Format:**
**After Format:**
**Steps to reproduce:**
```ballerina
map<string> defaultChars = { "top": "═" , "top-mid": "╤" , "top-left": "╔" , "top-right": "╗"
, "bottom": "═" , "bottom-mid": "╧" , "bottom-left": "╚" , "bottom-right": "╝"
, "left": "║" , "left-mid": "╟" , "mid": "─" , "mid-mid": "┼"
, "right": "║" , "right-mid": "╢" , "middle": "│" };
```
**Affected Versions:**
1.0.0-beta-SNAPSHOT
| 1.0 | Formatting breaks for UNI-Code symbols - **Description:**
Formatting breaks for UNI-Code symbols.
**Before Format:**
**After Format:**
**Steps to reproduce:**
```ballerina
map<string> defaultChars = { "top": "═" , "top-mid": "╤" , "top-left": "╔" , "top-right": "╗"
, "bottom": "═" , "bottom-mid": "╧" , "bottom-left": "╚" , "bottom-right": "╝"
, "left": "║" , "left-mid": "╟" , "mid": "─" , "mid-mid": "┼"
, "right": "║" , "right-mid": "╢" , "middle": "│" };
```
**Affected Versions:**
1.0.0-beta-SNAPSHOT
| test | formatting breaks for uni code symbols description formatting breaks for uni code symbols before format after format steps to reproduce ballerina map defaultchars top ═ top mid ╤ top left ╔ top right ╗ bottom ═ bottom mid ╧ bottom left ╚ bottom right ╝ left ║ left mid ╟ mid ─ mid mid ┼ right ║ right mid ╢ middle │ affected versions beta snapshot | 1 |
191,541 | 22,215,800,657 | IssuesEvent | 2022-06-08 01:25:00 | panasalap/linux-4.1.15 | https://api.github.com/repos/panasalap/linux-4.1.15 | reopened | CVE-2019-20934 (Medium) detected in linux-yocto-devv4.2.8, linux-yocto-devv4.2.8 | security vulnerability | ## CVE-2019-20934 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linux-yocto-devv4.2.8</b>, <b>linux-yocto-devv4.2.8</b></p></summary>
<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>
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
<p>Publish Date: 2020-11-28
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20934>CVE-2019-20934</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20934">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20934</a></p>
<p>Release Date: 2020-11-28</p>
<p>Fix Resolution: v5.3-rc2</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-20934 (Medium) detected in linux-yocto-devv4.2.8, linux-yocto-devv4.2.8 - ## CVE-2019-20934 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linux-yocto-devv4.2.8</b>, <b>linux-yocto-devv4.2.8</b></p></summary>
<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>
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
<p>Publish Date: 2020-11-28
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20934>CVE-2019-20934</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20934">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20934</a></p>
<p>Release Date: 2020-11-28</p>
<p>Fix Resolution: v5.3-rc2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve medium detected in linux yocto linux yocto cve medium severity vulnerability vulnerable libraries linux yocto linux yocto vulnerability details an issue was discovered in the linux kernel before on numa systems the linux fair scheduler has a use after free in show numa stats because numa fault statistics are inappropriately freed aka cid publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
33,494 | 7,722,216,633 | IssuesEvent | 2018-05-24 08:35:56 | Automattic/jetpack | https://api.github.com/repos/Automattic/jetpack | closed | GDPR Compliance - modify output of embed shortcodes like youtube etc. | Shortcodes [Status] Needs Author Reply [Type] GDPR | Please modify any social media embed shortcodes to comply with new GDPR.
| 1.0 | GDPR Compliance - modify output of embed shortcodes like youtube etc. - Please modify any social media embed shortcodes to comply with new GDPR.
| non_test | gdpr compliance modify output of embed shortcodes like youtube etc please modify any social media embed shortcodes to comply with new gdpr | 0 |
205,620 | 15,650,378,198 | IssuesEvent | 2021-03-23 08:54:58 | mozilla-mobile/firefox-ios | https://api.github.com/repos/mozilla-mobile/firefox-ios | opened | DataManagementTests.testWebSiteDataEnterFirstTime() | eng:automation eng:intermittent-test | ### Bitrise Test Run:
Provide a Bitrise test run report link here showcasing the problem
https://app.bitrise.io/build/160f3a0416775387#?tab=log
### Stacktrace:
file:///Users/vagrant/git/XCUITests/FxScreenGraph.swift:CharacterRangeLen=0&EndingLineNumber=721&StartingLineNumber=721 - Failed to get matching snapshot: No matches found for Descendants matching type Alert from input {(
Application, pid: 11424, label: 'Fennec (vagrant)'
)}
### Build:
Scheduled Smoke March 23rd | 1.0 | DataManagementTests.testWebSiteDataEnterFirstTime() - ### Bitrise Test Run:
Provide a Bitrise test run report link here showcasing the problem
https://app.bitrise.io/build/160f3a0416775387#?tab=log
### Stacktrace:
file:///Users/vagrant/git/XCUITests/FxScreenGraph.swift:CharacterRangeLen=0&EndingLineNumber=721&StartingLineNumber=721 - Failed to get matching snapshot: No matches found for Descendants matching type Alert from input {(
Application, pid: 11424, label: 'Fennec (vagrant)'
)}
### Build:
Scheduled Smoke March 23rd | test | datamanagementtests testwebsitedataenterfirsttime bitrise test run provide a bitrise test run report link here showcasing the problem stacktrace file users vagrant git xcuitests fxscreengraph swift characterrangelen endinglinenumber startinglinenumber failed to get matching snapshot no matches found for descendants matching type alert from input application pid label fennec vagrant build scheduled smoke march | 1 |
22,523 | 3,788,106,072 | IssuesEvent | 2016-03-21 13:39:14 | RestComm/Restcomm-Connect | https://api.github.com/repos/RestComm/Restcomm-Connect | opened | Display "broken" applications in RVD with "remove" link | 1. Bug Visual App Designer | In case there is a restcomm Application record with no corresponding RVD project (as if it has been manually deleted) the application is considered "broken". Currently such applications are hidden from RVD but are displayed in AdminUI (both in number registration and Restcomm Apps) list.
1. They should appear in the RVD project list along with a link to remove them.
2. Ideally, a "broken" indication should also appear in AdminUI (number registration and Restcomm Apps views) if this can be easily patched too (i think not). | 1.0 | Display "broken" applications in RVD with "remove" link - In case there is a restcomm Application record with no corresponding RVD project (as if it has been manually deleted) the application is considered "broken". Currently such applications are hidden from RVD but are displayed in AdminUI (both in number registration and Restcomm Apps) list.
1. They should appear in the RVD project list along with a link to remove them.
2. Ideally, a "broken" indication should also appear in AdminUI (number registration and Restcomm Apps views) if this can be easily patched too (i think not). | non_test | display broken applications in rvd with remove link in case there is a restcomm application record with no corresponding rvd project as if it has been manually deleted the application is considered broken currently such applications are hidden from rvd but are displayed in adminui both in number registration and restcomm apps list they should appear in the rvd project list along with a link to remove them ideally a broken indication should also appear in adminui number registration and restcomm apps views if this can be easily patched too i think not | 0 |
54,812 | 11,307,939,066 | IssuesEvent | 2020-01-19 01:03:37 | jyn514/rcc | https://api.github.com/repos/jyn514/rcc | opened | Initialization at local scope is more messed up | bug codegen | **Expected behavior**
Should output "salut".
**Actual Behavior**
Outputs garbage (on my machine, looks like null bytes).
**Code**
```c
int main()
{
char string[100] = "salut";
printf("\n%s\n", string);
}
```
<details><summary>AST</summary>
Please paste the output of `cargo run -- --debug-ast` here.
```
extern int printf(char * format, ...);
extern int main() {
auto char string[100] = "salut";;
(printf)("
%s
", string);
}
```
</details>
<details><summary>ASM</summary>
Please paste the output of `cargo run -- --debug-asm` here.
```
function u0:0() -> i32 system_v {
ss0 = explicit_slot 100
gv0 = symbol colocated u1:0
gv1 = symbol colocated u1:1
sig0 = (i64, i64, i8 [%0]) -> i32 system_v
fn0 = u0:0 sig0
ebb0:
v0 = global_value.i64 gv0
v1 = stack_addr.i64 ss0
store v0, v1
v2 = global_value.i64 gv1
v3 = stack_addr.i64 ss0 ; notice how ss0 is never initialized
v4 = iconst.i8 0
v5 = call fn0(v2, v3, v4)
v6 = iconst.i32 0
return v6
}
```
</details> | 1.0 | Initialization at local scope is more messed up - **Expected behavior**
Should output "salut".
**Actual Behavior**
Outputs garbage (on my machine, looks like null bytes).
**Code**
```c
int main()
{
char string[100] = "salut";
printf("\n%s\n", string);
}
```
<details><summary>AST</summary>
Please paste the output of `cargo run -- --debug-ast` here.
```
extern int printf(char * format, ...);
extern int main() {
auto char string[100] = "salut";;
(printf)("
%s
", string);
}
```
</details>
<details><summary>ASM</summary>
Please paste the output of `cargo run -- --debug-asm` here.
```
function u0:0() -> i32 system_v {
ss0 = explicit_slot 100
gv0 = symbol colocated u1:0
gv1 = symbol colocated u1:1
sig0 = (i64, i64, i8 [%0]) -> i32 system_v
fn0 = u0:0 sig0
ebb0:
v0 = global_value.i64 gv0
v1 = stack_addr.i64 ss0
store v0, v1
v2 = global_value.i64 gv1
v3 = stack_addr.i64 ss0 ; notice how ss0 is never initialized
v4 = iconst.i8 0
v5 = call fn0(v2, v3, v4)
v6 = iconst.i32 0
return v6
}
```
</details> | non_test | initialization at local scope is more messed up expected behavior should output salut actual behavior outputs garbage on my machine looks like null bytes code c int main char string salut printf n s n string ast please paste the output of cargo run debug ast here extern int printf char format extern int main auto char string salut printf s string asm please paste the output of cargo run debug asm here function system v explicit slot symbol colocated symbol colocated system v global value stack addr store global value stack addr notice how is never initialized iconst call iconst return | 0 |
90,987 | 11,455,768,949 | IssuesEvent | 2020-02-06 19:47:22 | luyadev/luya-module-admin | https://api.github.com/repos/luyadev/luya-module-admin | closed | No vertical scrollbar in Chrome | bug:research design | ### What steps will reproduce the problem?
Open an admin panel in Chrome. Make the window height is small enough.
### What is the expected result?
Vertical scrollbars should appears.
### What do you get instead? (A Screenshot can help us a lot!)
No scrollbars in Chrome (Windows). Everything is fine in Firefox.
| 1.0 | No vertical scrollbar in Chrome - ### What steps will reproduce the problem?
Open an admin panel in Chrome. Make the window height is small enough.
### What is the expected result?
Vertical scrollbars should appears.
### What do you get instead? (A Screenshot can help us a lot!)
No scrollbars in Chrome (Windows). Everything is fine in Firefox.
| non_test | no vertical scrollbar in chrome what steps will reproduce the problem open an admin panel in chrome make the window height is small enough what is the expected result vertical scrollbars should appears what do you get instead a screenshot can help us a lot no scrollbars in chrome windows everything is fine in firefox | 0 |
318,540 | 9,693,988,765 | IssuesEvent | 2019-05-24 17:38:34 | devopsec/student_clubs | https://api.github.com/repos/devopsec/student_clubs | opened | File Upload Handling | priority 2 | Finish the file upload feature for clubs page.
Need to implement on backend in php | 1.0 | File Upload Handling - Finish the file upload feature for clubs page.
Need to implement on backend in php | non_test | file upload handling finish the file upload feature for clubs page need to implement on backend in php | 0 |
818,626 | 30,696,899,498 | IssuesEvent | 2023-07-26 19:21:41 | GoogleCloudPlatform/java-docs-samples | https://api.github.com/repos/GoogleCloudPlatform/java-docs-samples | opened | Adding samples for calling the Cloud Support API | type: feature request priority: p3 triage me | ## Is your feature request related to a problem? Please describe.
Yes. Users of my team's API, the Cloud Support API, need examples of how to call it with Java.
## Describe the solution you'd like.
We'd like to add examples of calling our API to this repository. Specifically, an example for every endpoint in [our REST reference](https://cloud.google.com/support/docs/reference/v2):
- caseClassifications.search
- cases.attachments.list
- cases.close
- cases.comments.create
- cases.comments.list
- cases.create
- cases.escalate
- cases.get
- cases.list
- cases.patch
- cases.search
- media.download
- media.upload
## Describe alternatives you've considered.
### Inlining examples straight in our docs.
Summary: Add a Java example inline for the docs for each of our endpoints.
Pros:
- Fastest to do.
- Don't need to keep track of a new repository.
- Don't need to work with any other teams to do.
Cons:
- Hard to read.
- Adds clutter to the docs.
- Not searchable in snippets.
- Java is very verbose, and we wouldn't have space for a verbose solution.
- Tricky to test.
Rejection reason: This would be too hard to read for our users and for us to test, and we couldn't include all the details we'd want to include because the examples would need to be so short.
### Making our own GitHub repository.
Summary: Make our own GitHub repository to place our examples in.
Pros:
- Don't need to work with any other teams to do this.
- Can choose what we merge.
Cons:
- Unknown how we'd do this, or whether we're allowed.
- Would need to structure the repo ourselves - including testing and GitHub actions.
- Not the canonical solution.
Rejection reason: It'd be a bigger lift than we'd like to set up a brand new repository. Also, I believe Google recommends that we place our examples in the current repo anyway.
## Additional context.
The examples we want to include will use client libraries generated from our discovery document.
Thanks for your time!
| 1.0 | Adding samples for calling the Cloud Support API - ## Is your feature request related to a problem? Please describe.
Yes. Users of my team's API, the Cloud Support API, need examples of how to call it with Java.
## Describe the solution you'd like.
We'd like to add examples of calling our API to this repository. Specifically, an example for every endpoint in [our REST reference](https://cloud.google.com/support/docs/reference/v2):
- caseClassifications.search
- cases.attachments.list
- cases.close
- cases.comments.create
- cases.comments.list
- cases.create
- cases.escalate
- cases.get
- cases.list
- cases.patch
- cases.search
- media.download
- media.upload
## Describe alternatives you've considered.
### Inlining examples straight in our docs.
Summary: Add a Java example inline for the docs for each of our endpoints.
Pros:
- Fastest to do.
- Don't need to keep track of a new repository.
- Don't need to work with any other teams to do.
Cons:
- Hard to read.
- Adds clutter to the docs.
- Not searchable in snippets.
- Java is very verbose, and we wouldn't have space for a verbose solution.
- Tricky to test.
Rejection reason: This would be too hard to read for our users and for us to test, and we couldn't include all the details we'd want to include because the examples would need to be so short.
### Making our own GitHub repository.
Summary: Make our own GitHub repository to place our examples in.
Pros:
- Don't need to work with any other teams to do this.
- Can choose what we merge.
Cons:
- Unknown how we'd do this, or whether we're allowed.
- Would need to structure the repo ourselves - including testing and GitHub actions.
- Not the canonical solution.
Rejection reason: It'd be a bigger lift than we'd like to set up a brand new repository. Also, I believe Google recommends that we place our examples in the current repo anyway.
## Additional context.
The examples we want to include will use client libraries generated from our discovery document.
Thanks for your time!
| non_test | adding samples for calling the cloud support api is your feature request related to a problem please describe yes users of my team s api the cloud support api need examples of how to call it with java describe the solution you d like we d like to add examples of calling our api to this repository specifically an example for every endpoint in caseclassifications search cases attachments list cases close cases comments create cases comments list cases create cases escalate cases get cases list cases patch cases search media download media upload describe alternatives you ve considered inlining examples straight in our docs summary add a java example inline for the docs for each of our endpoints pros fastest to do don t need to keep track of a new repository don t need to work with any other teams to do cons hard to read adds clutter to the docs not searchable in snippets java is very verbose and we wouldn t have space for a verbose solution tricky to test rejection reason this would be too hard to read for our users and for us to test and we couldn t include all the details we d want to include because the examples would need to be so short making our own github repository summary make our own github repository to place our examples in pros don t need to work with any other teams to do this can choose what we merge cons unknown how we d do this or whether we re allowed would need to structure the repo ourselves including testing and github actions not the canonical solution rejection reason it d be a bigger lift than we d like to set up a brand new repository also i believe google recommends that we place our examples in the current repo anyway additional context the examples we want to include will use client libraries generated from our discovery document thanks for your time | 0 |
22,076 | 11,473,181,042 | IssuesEvent | 2020-02-09 21:35:53 | PrincetonUniversity/athena-public-version | https://api.github.com/repos/PrincetonUniversity/athena-public-version | closed | Memory leak using AMD Threadripper 2950x | bug file IO performance | Hi,
I compiled the most recent version of Athena++ using AMD threadripper 2950x CPU, gcc 9.2 and openmpi. I tried to test the field_loop_poles case using 16 cores in parallel. The test case is working properly but I found that my memory usage increases continuously at about 1GB per output step when the grid size is 64x32x128. It seems that this is the problem of the parallelization. The memory stays fine when I'm using single core. Do you have any idea of what may go wrong?
Thanks,
Cheng | True | Memory leak using AMD Threadripper 2950x - Hi,
I compiled the most recent version of Athena++ using AMD threadripper 2950x CPU, gcc 9.2 and openmpi. I tried to test the field_loop_poles case using 16 cores in parallel. The test case is working properly but I found that my memory usage increases continuously at about 1GB per output step when the grid size is 64x32x128. It seems that this is the problem of the parallelization. The memory stays fine when I'm using single core. Do you have any idea of what may go wrong?
Thanks,
Cheng | non_test | memory leak using amd threadripper hi i compiled the most recent version of athena using amd threadripper cpu gcc and openmpi i tried to test the field loop poles case using cores in parallel the test case is working properly but i found that my memory usage increases continuously at about per output step when the grid size is it seems that this is the problem of the parallelization the memory stays fine when i m using single core do you have any idea of what may go wrong thanks cheng | 0 |
39,742 | 6,772,687,804 | IssuesEvent | 2017-10-27 00:30:16 | MessageKit/MessageKit | https://api.github.com/repos/MessageKit/MessageKit | closed | Add more badges to README | documentation good first issue hacktoberfest | We could use some more badges on the README. Possibly for:
- remove travis & add buddybuild badge
- add MIT license badge
- add CocoaPods badge
- add Carthage badge
- add Swift Version badge
- add Xcode version badge
- add contributors welcome badge 😃
You can check out another one of my projects for an example of some of these:
https://github.com/SD10/Nora
| 1.0 | Add more badges to README - We could use some more badges on the README. Possibly for:
- remove travis & add buddybuild badge
- add MIT license badge
- add CocoaPods badge
- add Carthage badge
- add Swift Version badge
- add Xcode version badge
- add contributors welcome badge 😃
You can check out another one of my projects for an example of some of these:
https://github.com/SD10/Nora
| non_test | add more badges to readme we could use some more badges on the readme possibly for remove travis add buddybuild badge add mit license badge add cocoapods badge add carthage badge add swift version badge add xcode version badge add contributors welcome badge 😃 you can check out another one of my projects for an example of some of these | 0 |
613,176 | 19,074,518,458 | IssuesEvent | 2021-11-27 14:24:33 | rizwansoaib/whatsapp-monitor | https://api.github.com/repos/rizwansoaib/whatsapp-monitor | closed | Notification after latest whatsapp web upgrade is not working | bug High Severity & Priority WhatsApp Beta | **Describe the bug**
After today's latest web webgrade for whatsapp , automatic online/offline notification is not coming unless we have opened the client .
**Expected behavior**
Automatic online notification should come how usually it was coming so far .
**Desktop (please complete the following information):**
- OS: [e.g. iOS] - Mac
- Browser [e.g. chrome, safari] - Both Chrome and firefox
**Smartphone (please complete the following information):**
- Device: [e.g. iPhone6] iphone 6S
**Additional context**
| 1.0 | Notification after latest whatsapp web upgrade is not working - **Describe the bug**
After today's latest web webgrade for whatsapp , automatic online/offline notification is not coming unless we have opened the client .
**Expected behavior**
Automatic online notification should come how usually it was coming so far .
**Desktop (please complete the following information):**
- OS: [e.g. iOS] - Mac
- Browser [e.g. chrome, safari] - Both Chrome and firefox
**Smartphone (please complete the following information):**
- Device: [e.g. iPhone6] iphone 6S
**Additional context**
| non_test | notification after latest whatsapp web upgrade is not working describe the bug after today s latest web webgrade for whatsapp automatic online offline notification is not coming unless we have opened the client expected behavior automatic online notification should come how usually it was coming so far desktop please complete the following information os mac browser both chrome and firefox smartphone please complete the following information device iphone additional context | 0 |
4,592 | 3,873,164,538 | IssuesEvent | 2016-04-11 16:02:38 | lionheart/openradar-mirror | https://api.github.com/repos/lionheart/openradar-mirror | opened | 22434677: Singer/Songwriter label overflows its bubble on “Tell us what you like” | classification:ui/usability reproducible:always status:open | #### Description
See screenshot.
-
Product Version: 12.2.2.25
Created: 2015-08-26T08:48:35.309890
Originated: 2015-08-26T09:48:00
Open Radar Link: http://www.openradar.me/22434677 | True | 22434677: Singer/Songwriter label overflows its bubble on “Tell us what you like” - #### Description
See screenshot.
-
Product Version: 12.2.2.25
Created: 2015-08-26T08:48:35.309890
Originated: 2015-08-26T09:48:00
Open Radar Link: http://www.openradar.me/22434677 | non_test | singer songwriter label overflows its bubble on “tell us what you like” description see screenshot product version created originated open radar link | 0 |
457,154 | 13,152,569,664 | IssuesEvent | 2020-08-09 23:05:11 | jenkins-x/jx | https://api.github.com/repos/jenkins-x/jx | closed | The docker image expected in a deployed quickstart doesn't match the image in the registry | area/fox area/pipeline kind/bug lifecycle/rotten priority/important-longterm | ### Summary
When creating a new quickstart, I noticed that, when deployed, the application wasn't starting up.
It was caused by a `imagePullBackOff`.
The image it was trying to deploy was: `gcr.io/apps-dev-229310/golang_test:0.0.1` yet, the image pushed to gcr.io from the pipeline was `gcr.io/apps-dev-229310/golang-test:0.0.1`.
When creating the quickstart, the repository was called `golang_test` but the image was created with `-` instead of `_`.
### Steps to reproduce the behavior
Create a quickstart, name the repository something with an underscore like `golang_test`.
### Expected behavior
The application should deploy correctly in the staging environment.
### Actual behavior
`imagePullBackOff` because the docker images tags don't match.
### Jenkins type
<!--
Select which installation type are you using.
-->
- [X] Serverless Jenkins X Pipelines (Tekton + Prow)
- [ ] Classic Jenkins | 1.0 | The docker image expected in a deployed quickstart doesn't match the image in the registry - ### Summary
When creating a new quickstart, I noticed that, when deployed, the application wasn't starting up.
It was caused by a `imagePullBackOff`.
The image it was trying to deploy was: `gcr.io/apps-dev-229310/golang_test:0.0.1` yet, the image pushed to gcr.io from the pipeline was `gcr.io/apps-dev-229310/golang-test:0.0.1`.
When creating the quickstart, the repository was called `golang_test` but the image was created with `-` instead of `_`.
### Steps to reproduce the behavior
Create a quickstart, name the repository something with an underscore like `golang_test`.
### Expected behavior
The application should deploy correctly in the staging environment.
### Actual behavior
`imagePullBackOff` because the docker images tags don't match.
### Jenkins type
<!--
Select which installation type are you using.
-->
- [X] Serverless Jenkins X Pipelines (Tekton + Prow)
- [ ] Classic Jenkins | non_test | the docker image expected in a deployed quickstart doesn t match the image in the registry summary when creating a new quickstart i noticed that when deployed the application wasn t starting up it was caused by a imagepullbackoff the image it was trying to deploy was gcr io apps dev golang test yet the image pushed to gcr io from the pipeline was gcr io apps dev golang test when creating the quickstart the repository was called golang test but the image was created with instead of steps to reproduce the behavior create a quickstart name the repository something with an underscore like golang test expected behavior the application should deploy correctly in the staging environment actual behavior imagepullbackoff because the docker images tags don t match jenkins type select which installation type are you using serverless jenkins x pipelines tekton prow classic jenkins | 0 |
206,533 | 15,733,622,210 | IssuesEvent | 2021-03-29 19:48:35 | Azure/azure-sdk-for-net | https://api.github.com/repos/Azure/azure-sdk-for-net | opened | Content null after retry before authentication succeeded | Client KeyVault test-reliability | During live Key Vault tests, ran into an exception where the request body to create a key was null (request parameters were provided):
```
[Informational] Azure-Core: Request [405dfb8d-5006-47d4-8012-bc8da6ea3377] POST https://tf17be9f7633d4c85.vault.azure.net/keys/CloudRsaKey-8e8e168f-1b47-439d-8563-675cc3e78499/create?api-version=7.2
Accept:application/json
x-ms-client-request-id:405dfb8d-5006-47d4-8012-bc8da6ea3377
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Security.KeyVault.Keys/4.2.0-alpha.20210329.1,(.NET 5.0.3; Darwin 19.6.0 Darwin Kernel Version 19.6.0: Tue Jan 12 22:13:05 PST 2021; root:xnu-6153.141.16~1/RELEASE_X86_64)
Content-Type:application/json
client assembly: Azure.Security.KeyVault.Keys
[Informational] Azure-Core: Request [405dfb8d-5006-47d4-8012-bc8da6ea3377] exception Azure.RequestFailedException: Operation timed out (tf17be9f7633d4c85.vault.azure.net:443)
---> System.Net.Http.HttpRequestException: Operation timed out (tf17be9f7633d4c85.vault.azure.net:443)
---> System.Net.Sockets.SocketException (60): Operation timed out
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|283_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.DefaultConnectAsync(SocketsHttpConnectionContext context, CancellationToken cancellationToken)
at System.Net.Http.ConnectHelper.ConnectAsync(Func`3 callback, DnsEndPoint endPoint, HttpRequestMessage requestMessage, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at System.Net.Http.ConnectHelper.ConnectAsync(Func`3 callback, DnsEndPoint endPoint, HttpRequestMessage requestMessage, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.GetHttpConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpClient.SendAsyncCore(HttpRequestMessage request, HttpCompletionOption completionOption, Boolean async, Boolean emitTelemetryStartStop, CancellationToken cancellationToken)
at Azure.Core.Pipeline.HttpClientTransport.ProcessAsync(HttpMessage message, Boolean async) in /_/sdk/core/Azure.Core/src/Pipeline/HttpClientTransport.cs:line 92
--- End of inner exception stack trace ---
at Azure.Core.Pipeline.HttpClientTransport.ProcessAsync(HttpMessage message, Boolean async) in /_/sdk/core/Azure.Core/src/Pipeline/HttpClientTransport.cs:line 122
at Azure.Core.Pipeline.ResponseBodyPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async) in /_/sdk/core/Azure.Core/src/Pipeline/Internal/ResponseBodyPolicy.cs:line 45
at Azure.Core.Pipeline.LoggingPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async) in /_/sdk/core/Azure.Core/src/Pipeline/Internal/LoggingPolicy.cs:line 79
[Informational] Azure-Core: Request [405dfb8d-5006-47d4-8012-bc8da6ea3377] retry number 1 took 10.7s
[Informational] Azure-Core: Request [405dfb8d-5006-47d4-8012-bc8da6ea3377] POST https://tf17be9f7633d4c85.vault.azure.net/keys/CloudRsaKey-8e8e168f-1b47-439d-8563-675cc3e78499/create?api-version=7.2
Accept:application/json
x-ms-client-request-id:405dfb8d-5006-47d4-8012-bc8da6ea3377
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Security.KeyVault.Keys/4.2.0-alpha.20210329.1,(.NET 5.0.3; Darwin 19.6.0 Darwin Kernel Version 19.6.0: Tue Jan 12 22:13:05 PST 2021; root:xnu-6153.141.16~1/RELEASE_X86_64)
Content-Type:application/json
client assembly: Azure.Security.KeyVault.Keys
[Warning] Azure-Core: Error response [405dfb8d-5006-47d4-8012-bc8da6ea3377] 401 Unauthorized (00.5s)
Cache-Control:no-cache
Pragma:no-cache
WWW-Authenticate:REDACTED
x-ms-keyvault-region:westus2
x-ms-client-request-id:405dfb8d-5006-47d4-8012-bc8da6ea3377
x-ms-request-id:REDACTED
x-ms-keyvault-service-version:1.2.205.0
x-ms-keyvault-network-info:conn_type=Ipv4;addr=13.105.49.36;act_addr_fam=InterNetwork;
X-Powered-By:REDACTED
Strict-Transport-Security:REDACTED
X-Content-Type-Options:REDACTED
Date:Mon, 29 Mar 2021 11:58:29 GMT
Content-Length:87
Content-Type:application/json; charset=utf-8
Expires:-1
... auth elided for brevity ...
[Informational] Azure-Core: Request [405dfb8d-5006-47d4-8012-bc8da6ea3377] POST https://tf17be9f7633d4c85.vault.azure.net/keys/CloudRsaKey-8e8e168f-1b47-439d-8563-675cc3e78499/create?api-version=7.2
Accept:application/json
x-ms-client-request-id:405dfb8d-5006-47d4-8012-bc8da6ea3377
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Security.KeyVault.Keys/4.2.0-alpha.20210329.1,(.NET 5.0.3; Darwin 19.6.0 Darwin Kernel Version 19.6.0: Tue Jan 12 22:13:05 PST 2021; root:xnu-6153.141.16~1/RELEASE_X86_64)
Authorization:REDACTED
Content-Type:application/json
client assembly: Azure.Security.KeyVault.Keys
[Warning] Azure-Core: Error response [405dfb8d-5006-47d4-8012-bc8da6ea3377] 400 Bad Request (00.0s)
Cache-Control:no-cache
Pragma:no-cache
x-ms-keyvault-region:westus2
x-ms-client-request-id:405dfb8d-5006-47d4-8012-bc8da6ea3377
x-ms-request-id:REDACTED
x-ms-keyvault-service-version:1.2.205.0
x-ms-keyvault-network-info:conn_type=Ipv4;addr=13.105.49.36;act_addr_fam=InterNetwork;
X-Powered-By:REDACTED
Strict-Transport-Security:REDACTED
X-Content-Type-Options:REDACTED
Date:Mon, 29 Mar 2021 11:58:30 GMT
Content-Length:72
Content-Type:application/json; charset=utf-8
Expires:-1
``` | 1.0 | Content null after retry before authentication succeeded - During live Key Vault tests, ran into an exception where the request body to create a key was null (request parameters were provided):
```
[Informational] Azure-Core: Request [405dfb8d-5006-47d4-8012-bc8da6ea3377] POST https://tf17be9f7633d4c85.vault.azure.net/keys/CloudRsaKey-8e8e168f-1b47-439d-8563-675cc3e78499/create?api-version=7.2
Accept:application/json
x-ms-client-request-id:405dfb8d-5006-47d4-8012-bc8da6ea3377
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Security.KeyVault.Keys/4.2.0-alpha.20210329.1,(.NET 5.0.3; Darwin 19.6.0 Darwin Kernel Version 19.6.0: Tue Jan 12 22:13:05 PST 2021; root:xnu-6153.141.16~1/RELEASE_X86_64)
Content-Type:application/json
client assembly: Azure.Security.KeyVault.Keys
[Informational] Azure-Core: Request [405dfb8d-5006-47d4-8012-bc8da6ea3377] exception Azure.RequestFailedException: Operation timed out (tf17be9f7633d4c85.vault.azure.net:443)
---> System.Net.Http.HttpRequestException: Operation timed out (tf17be9f7633d4c85.vault.azure.net:443)
---> System.Net.Sockets.SocketException (60): Operation timed out
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|283_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.DefaultConnectAsync(SocketsHttpConnectionContext context, CancellationToken cancellationToken)
at System.Net.Http.ConnectHelper.ConnectAsync(Func`3 callback, DnsEndPoint endPoint, HttpRequestMessage requestMessage, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at System.Net.Http.ConnectHelper.ConnectAsync(Func`3 callback, DnsEndPoint endPoint, HttpRequestMessage requestMessage, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.GetHttpConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpClient.SendAsyncCore(HttpRequestMessage request, HttpCompletionOption completionOption, Boolean async, Boolean emitTelemetryStartStop, CancellationToken cancellationToken)
at Azure.Core.Pipeline.HttpClientTransport.ProcessAsync(HttpMessage message, Boolean async) in /_/sdk/core/Azure.Core/src/Pipeline/HttpClientTransport.cs:line 92
--- End of inner exception stack trace ---
at Azure.Core.Pipeline.HttpClientTransport.ProcessAsync(HttpMessage message, Boolean async) in /_/sdk/core/Azure.Core/src/Pipeline/HttpClientTransport.cs:line 122
at Azure.Core.Pipeline.ResponseBodyPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async) in /_/sdk/core/Azure.Core/src/Pipeline/Internal/ResponseBodyPolicy.cs:line 45
at Azure.Core.Pipeline.LoggingPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async) in /_/sdk/core/Azure.Core/src/Pipeline/Internal/LoggingPolicy.cs:line 79
[Informational] Azure-Core: Request [405dfb8d-5006-47d4-8012-bc8da6ea3377] retry number 1 took 10.7s
[Informational] Azure-Core: Request [405dfb8d-5006-47d4-8012-bc8da6ea3377] POST https://tf17be9f7633d4c85.vault.azure.net/keys/CloudRsaKey-8e8e168f-1b47-439d-8563-675cc3e78499/create?api-version=7.2
Accept:application/json
x-ms-client-request-id:405dfb8d-5006-47d4-8012-bc8da6ea3377
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Security.KeyVault.Keys/4.2.0-alpha.20210329.1,(.NET 5.0.3; Darwin 19.6.0 Darwin Kernel Version 19.6.0: Tue Jan 12 22:13:05 PST 2021; root:xnu-6153.141.16~1/RELEASE_X86_64)
Content-Type:application/json
client assembly: Azure.Security.KeyVault.Keys
[Warning] Azure-Core: Error response [405dfb8d-5006-47d4-8012-bc8da6ea3377] 401 Unauthorized (00.5s)
Cache-Control:no-cache
Pragma:no-cache
WWW-Authenticate:REDACTED
x-ms-keyvault-region:westus2
x-ms-client-request-id:405dfb8d-5006-47d4-8012-bc8da6ea3377
x-ms-request-id:REDACTED
x-ms-keyvault-service-version:1.2.205.0
x-ms-keyvault-network-info:conn_type=Ipv4;addr=13.105.49.36;act_addr_fam=InterNetwork;
X-Powered-By:REDACTED
Strict-Transport-Security:REDACTED
X-Content-Type-Options:REDACTED
Date:Mon, 29 Mar 2021 11:58:29 GMT
Content-Length:87
Content-Type:application/json; charset=utf-8
Expires:-1
... auth elided for brevity ...
[Informational] Azure-Core: Request [405dfb8d-5006-47d4-8012-bc8da6ea3377] POST https://tf17be9f7633d4c85.vault.azure.net/keys/CloudRsaKey-8e8e168f-1b47-439d-8563-675cc3e78499/create?api-version=7.2
Accept:application/json
x-ms-client-request-id:405dfb8d-5006-47d4-8012-bc8da6ea3377
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Security.KeyVault.Keys/4.2.0-alpha.20210329.1,(.NET 5.0.3; Darwin 19.6.0 Darwin Kernel Version 19.6.0: Tue Jan 12 22:13:05 PST 2021; root:xnu-6153.141.16~1/RELEASE_X86_64)
Authorization:REDACTED
Content-Type:application/json
client assembly: Azure.Security.KeyVault.Keys
[Warning] Azure-Core: Error response [405dfb8d-5006-47d4-8012-bc8da6ea3377] 400 Bad Request (00.0s)
Cache-Control:no-cache
Pragma:no-cache
x-ms-keyvault-region:westus2
x-ms-client-request-id:405dfb8d-5006-47d4-8012-bc8da6ea3377
x-ms-request-id:REDACTED
x-ms-keyvault-service-version:1.2.205.0
x-ms-keyvault-network-info:conn_type=Ipv4;addr=13.105.49.36;act_addr_fam=InterNetwork;
X-Powered-By:REDACTED
Strict-Transport-Security:REDACTED
X-Content-Type-Options:REDACTED
Date:Mon, 29 Mar 2021 11:58:30 GMT
Content-Length:72
Content-Type:application/json; charset=utf-8
Expires:-1
``` | test | content null after retry before authentication succeeded during live key vault tests ran into an exception where the request body to create a key was null request parameters were provided azure core request post accept application json x ms client request id x ms return client request id true user agent azsdk net security keyvault keys alpha net darwin darwin kernel version tue jan pst root xnu release content type application json client assembly azure security keyvault keys azure core request exception azure requestfailedexception operation timed out vault azure net system net http httprequestexception operation timed out vault azure net system net sockets socketexception operation timed out at system net sockets socket awaitablesocketasynceventargs throwexception socketerror error cancellationtoken cancellationtoken at system net sockets socket awaitablesocketasynceventargs system threading tasks sources ivaluetasksource getresult token at system net sockets socket g waitforconnectwithcancellation awaitablesocketasynceventargs saea valuetask connecttask cancellationtoken cancellationtoken at system net http httpconnectionpool defaultconnectasync socketshttpconnectioncontext context cancellationtoken cancellationtoken at system net http connecthelper connectasync func callback dnsendpoint endpoint httprequestmessage requestmessage cancellationtoken cancellationtoken end of inner exception stack trace at system net http connecthelper connectasync func callback dnsendpoint endpoint httprequestmessage requestmessage cancellationtoken cancellationtoken at system net http httpconnectionpool connectasync httprequestmessage request boolean async cancellationtoken cancellationtoken at system net http httpconnectionpool httprequestmessage request boolean async cancellationtoken cancellationtoken at system net http httpconnectionpool gethttpconnectionasync httprequestmessage request boolean async cancellationtoken cancellationtoken at system net http httpconnectionpool sendwithretryasync httprequestmessage request boolean async boolean dorequestauth cancellationtoken cancellationtoken at system net http redirecthandler sendasync httprequestmessage request boolean async cancellationtoken cancellationtoken at system net http httpclient sendasynccore httprequestmessage request httpcompletionoption completionoption boolean async boolean emittelemetrystartstop cancellationtoken cancellationtoken at azure core pipeline httpclienttransport processasync httpmessage message boolean async in sdk core azure core src pipeline httpclienttransport cs line end of inner exception stack trace at azure core pipeline httpclienttransport processasync httpmessage message boolean async in sdk core azure core src pipeline httpclienttransport cs line at azure core pipeline responsebodypolicy processasync httpmessage message readonlymemory pipeline boolean async in sdk core azure core src pipeline internal responsebodypolicy cs line at azure core pipeline loggingpolicy processasync httpmessage message readonlymemory pipeline boolean async in sdk core azure core src pipeline internal loggingpolicy cs line azure core request retry number took azure core request post accept application json x ms client request id x ms return client request id true user agent azsdk net security keyvault keys alpha net darwin darwin kernel version tue jan pst root xnu release content type application json client assembly azure security keyvault keys azure core error response unauthorized cache control no cache pragma no cache www authenticate redacted x ms keyvault region x ms client request id x ms request id redacted x ms keyvault service version x ms keyvault network info conn type addr act addr fam internetwork x powered by redacted strict transport security redacted x content type options redacted date mon mar gmt content length content type application json charset utf expires auth elided for brevity azure core request post accept application json x ms client request id x ms return client request id true user agent azsdk net security keyvault keys alpha net darwin darwin kernel version tue jan pst root xnu release authorization redacted content type application json client assembly azure security keyvault keys azure core error response bad request cache control no cache pragma no cache x ms keyvault region x ms client request id x ms request id redacted x ms keyvault service version x ms keyvault network info conn type addr act addr fam internetwork x powered by redacted strict transport security redacted x content type options redacted date mon mar gmt content length content type application json charset utf expires | 1 |
571,695 | 17,023,348,134 | IssuesEvent | 2021-07-03 01:33:27 | tomhughes/trac-tickets | https://api.github.com/repos/tomhughes/trac-tickets | closed | pop-up dialog boxes break workflow | Component: merkaartor Priority: minor Resolution: fixed Type: enhancement | **[Submitted to the original trac issue database at 9.10pm, Monday, 12th January 2009]**
When merging nodes by moving the workflow is broken by popping up a dialog box (merge yes/no). In connection with ticket #1486 this is pretty annoying. Automerging should be a configurable option (always/never), and the user should be asked for confirmation only if the merging nodes have different tags.
Other pop-up dialogs disturb the workflow, too:
- At the end of Create Area
- Delete road nodes when deleting a road
All of this could be made configurable to default behavior in order to improve workflow.
| 1.0 | pop-up dialog boxes break workflow - **[Submitted to the original trac issue database at 9.10pm, Monday, 12th January 2009]**
When merging nodes by moving the workflow is broken by popping up a dialog box (merge yes/no). In connection with ticket #1486 this is pretty annoying. Automerging should be a configurable option (always/never), and the user should be asked for confirmation only if the merging nodes have different tags.
Other pop-up dialogs disturb the workflow, too:
- At the end of Create Area
- Delete road nodes when deleting a road
All of this could be made configurable to default behavior in order to improve workflow.
| non_test | pop up dialog boxes break workflow when merging nodes by moving the workflow is broken by popping up a dialog box merge yes no in connection with ticket this is pretty annoying automerging should be a configurable option always never and the user should be asked for confirmation only if the merging nodes have different tags other pop up dialogs disturb the workflow too at the end of create area delete road nodes when deleting a road all of this could be made configurable to default behavior in order to improve workflow | 0 |
282,391 | 24,472,438,653 | IssuesEvent | 2022-10-07 21:42:25 | pytorch/pytorch | https://api.github.com/repos/pytorch/pytorch | opened | DISABLED test_forward_mode_AD_linalg_lu_factor_cuda_float64 (__main__.TestGradientsCUDA) | module: flaky-tests skipped module: unknown | Platforms: linux
This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_forward_mode_AD_linalg_lu_factor_cuda_float64&suite=TestGradientsCUDA) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/8771217936).
Over the past 3 hours, it has been determined flaky in 1 workflow(s) with 1 failures and 1 successes.
**Debugging instructions (after clicking on the recent samples link):**
DO NOT BE ALARMED IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_forward_mode_AD_linalg_lu_factor_cuda_float64`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.
| 1.0 | DISABLED test_forward_mode_AD_linalg_lu_factor_cuda_float64 (__main__.TestGradientsCUDA) - Platforms: linux
This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_forward_mode_AD_linalg_lu_factor_cuda_float64&suite=TestGradientsCUDA) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/8771217936).
Over the past 3 hours, it has been determined flaky in 1 workflow(s) with 1 failures and 1 successes.
**Debugging instructions (after clicking on the recent samples link):**
DO NOT BE ALARMED IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_forward_mode_AD_linalg_lu_factor_cuda_float64`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.
| test | disabled test forward mode ad linalg lu factor cuda main testgradientscuda platforms linux this test was disabled because it is failing in ci see and the most recent trunk over the past hours it has been determined flaky in workflow s with failures and successes debugging instructions after clicking on the recent samples link do not be alarmed if the ci is green we now shield flaky tests from developers so ci will thus be green but it will be harder to parse the logs to find relevant log snippets click on the workflow logs linked above click on the test step of the job so that it is expanded otherwise the grepping will not work grep for test forward mode ad linalg lu factor cuda there should be several instances run as flaky tests are rerun in ci from which you can study the logs | 1 |
11,017 | 7,024,850,291 | IssuesEvent | 2017-12-23 00:30:29 | uber/pyro | https://api.github.com/repos/uber/pyro | closed | Pyro docker image | enhancement usability | As discussed in #114, it will be nice to have a dockerfile that we can use to build a docker container with pyro and all its dependencies packaged in, specially for running on a GPU. I suppose this will need to wait until we make Pyro public (as pip / git clone will not work with restricted access), but opening this task to keep track of the issue.
| True | Pyro docker image - As discussed in #114, it will be nice to have a dockerfile that we can use to build a docker container with pyro and all its dependencies packaged in, specially for running on a GPU. I suppose this will need to wait until we make Pyro public (as pip / git clone will not work with restricted access), but opening this task to keep track of the issue.
| non_test | pyro docker image as discussed in it will be nice to have a dockerfile that we can use to build a docker container with pyro and all its dependencies packaged in specially for running on a gpu i suppose this will need to wait until we make pyro public as pip git clone will not work with restricted access but opening this task to keep track of the issue | 0 |
396,986 | 11,716,704,779 | IssuesEvent | 2020-03-09 16:03:07 | TykTechnologies/tyk-pump | https://api.github.com/repos/TykTechnologies/tyk-pump | reopened | improve backpressure resilience of pump | Priority: High bug enhancement | # Problem 1
If one pump is configured, and the data-sink e.g. elastic-search or mongo etc fail or experience a slow-down (disk, ram, IO, CPU), then analytics pile up inside Redis, and pump pulls in a significantly larger collection of analytics to purge
# Problem 2
If multiple pumps are configured - e.g. elastic-search and mongo and statsd, and one of the data-sinks fail, then analytics writing get delayed due to blocking operation, and analytics pile up inside Redis
---
```
func writeToPumps(keys []interface{}, job *health.Job, startTime time.Time) {
// Send to pumps
if Pumps != nil {
for _, pmp := range Pumps {
log.WithFields(logrus.Fields{
"prefix": mainPrefix,
}).Debug("Writing to: ", pmp.GetName())
pmp.WriteData(keys)
if job != nil {
job.Timing("purge_time_"+pmp.GetName(), time.Since(startTime).Nanoseconds())
}
}
} else {
log.WithFields(logrus.Fields{
"prefix": mainPrefix,
}).Warning("No pumps defined!")
}
}
```
`pmp.WriteData(keys)` is a blocking operation. Tyk-Pump in above scenarios is not the root-cause of the problem, but it should be resilient to network partitions, failures and slow-downs of the data-sinks it ships to.
As such, I would consider this both an enhancement and a bug.
# Proposal
`pmp.WriteData` should be called as a goroutine for each pump
Once all writes are done, we can then go and get the next analytics records from Redis
Each pump configuration should have an optional deadline to complete in seconds.
It should be possible to set the deadline as 0 - meaning no deadline.
After the deadline has passed - we log which pump did not finish yet along with how many records are being dropped and close the goroutine.
# Expected output
- Visibility in the logs that there is a problem and identifying the specific data-sink that is causing the issue
- Ensure analytics are still being received at the problem-free data-sinks
- We ensure that analytics collections inside Redis do not build up too much and cause back-pressure
# CC
@buger
@tbuchaillot
@letzya | 1.0 | improve backpressure resilience of pump - # Problem 1
If one pump is configured, and the data-sink e.g. elastic-search or mongo etc fail or experience a slow-down (disk, ram, IO, CPU), then analytics pile up inside Redis, and pump pulls in a significantly larger collection of analytics to purge
# Problem 2
If multiple pumps are configured - e.g. elastic-search and mongo and statsd, and one of the data-sinks fail, then analytics writing get delayed due to blocking operation, and analytics pile up inside Redis
---
```
func writeToPumps(keys []interface{}, job *health.Job, startTime time.Time) {
// Send to pumps
if Pumps != nil {
for _, pmp := range Pumps {
log.WithFields(logrus.Fields{
"prefix": mainPrefix,
}).Debug("Writing to: ", pmp.GetName())
pmp.WriteData(keys)
if job != nil {
job.Timing("purge_time_"+pmp.GetName(), time.Since(startTime).Nanoseconds())
}
}
} else {
log.WithFields(logrus.Fields{
"prefix": mainPrefix,
}).Warning("No pumps defined!")
}
}
```
`pmp.WriteData(keys)` is a blocking operation. Tyk-Pump in above scenarios is not the root-cause of the problem, but it should be resilient to network partitions, failures and slow-downs of the data-sinks it ships to.
As such, I would consider this both an enhancement and a bug.
# Proposal
`pmp.WriteData` should be called as a goroutine for each pump
Once all writes are done, we can then go and get the next analytics records from Redis
Each pump configuration should have an optional deadline to complete in seconds.
It should be possible to set the deadline as 0 - meaning no deadline.
After the deadline has passed - we log which pump did not finish yet along with how many records are being dropped and close the goroutine.
# Expected output
- Visibility in the logs that there is a problem and identifying the specific data-sink that is causing the issue
- Ensure analytics are still being received at the problem-free data-sinks
- We ensure that analytics collections inside Redis do not build up too much and cause back-pressure
# CC
@buger
@tbuchaillot
@letzya | non_test | improve backpressure resilience of pump problem if one pump is configured and the data sink e g elastic search or mongo etc fail or experience a slow down disk ram io cpu then analytics pile up inside redis and pump pulls in a significantly larger collection of analytics to purge problem if multiple pumps are configured e g elastic search and mongo and statsd and one of the data sinks fail then analytics writing get delayed due to blocking operation and analytics pile up inside redis func writetopumps keys interface job health job starttime time time send to pumps if pumps nil for pmp range pumps log withfields logrus fields prefix mainprefix debug writing to pmp getname pmp writedata keys if job nil job timing purge time pmp getname time since starttime nanoseconds else log withfields logrus fields prefix mainprefix warning no pumps defined pmp writedata keys is a blocking operation tyk pump in above scenarios is not the root cause of the problem but it should be resilient to network partitions failures and slow downs of the data sinks it ships to as such i would consider this both an enhancement and a bug proposal pmp writedata should be called as a goroutine for each pump once all writes are done we can then go and get the next analytics records from redis each pump configuration should have an optional deadline to complete in seconds it should be possible to set the deadline as meaning no deadline after the deadline has passed we log which pump did not finish yet along with how many records are being dropped and close the goroutine expected output visibility in the logs that there is a problem and identifying the specific data sink that is causing the issue ensure analytics are still being received at the problem free data sinks we ensure that analytics collections inside redis do not build up too much and cause back pressure cc buger tbuchaillot letzya | 0 |
88,237 | 15,800,754,380 | IssuesEvent | 2021-04-03 01:08:28 | hashier/test-bazel-go | https://api.github.com/repos/hashier/test-bazel-go | opened | CVE-2020-36186 (High) detected in jackson-databind-2.3.3.jar | security vulnerability | ## CVE-2020-36186 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.3.3.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Path to dependency file: /tmp/ws-scm/test-bolt/build.gradle</p>
<p>Path to vulnerable library: /root/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.3.3/63b77400b5f1cf83a81823562c48d3120ef5518e/jackson-databind-2.3.3.jar,/root/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.3.3/63b77400b5f1cf83a81823562c48d3120ef5518e/jackson-databind-2.3.3.jar</p>
<p>
Dependency Hierarchy:
- dropwizard-core-0.7.1.jar (Root Library)
- dropwizard-jackson-0.7.1.jar
- :x: **jackson-databind-2.3.3.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp.datasources.PerUserPoolDataSource.
<p>Publish Date: 2021-01-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36186>CVE-2020-36186</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://github.com/FasterXML/jackson-databind/issues/2997">https://github.com/FasterXML/jackson-databind/issues/2997</a></p>
<p>Release Date: 2021-01-06</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.8</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-36186 (High) detected in jackson-databind-2.3.3.jar - ## CVE-2020-36186 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.3.3.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Path to dependency file: /tmp/ws-scm/test-bolt/build.gradle</p>
<p>Path to vulnerable library: /root/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.3.3/63b77400b5f1cf83a81823562c48d3120ef5518e/jackson-databind-2.3.3.jar,/root/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.3.3/63b77400b5f1cf83a81823562c48d3120ef5518e/jackson-databind-2.3.3.jar</p>
<p>
Dependency Hierarchy:
- dropwizard-core-0.7.1.jar (Root Library)
- dropwizard-jackson-0.7.1.jar
- :x: **jackson-databind-2.3.3.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp.datasources.PerUserPoolDataSource.
<p>Publish Date: 2021-01-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36186>CVE-2020-36186</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://github.com/FasterXML/jackson-databind/issues/2997">https://github.com/FasterXML/jackson-databind/issues/2997</a></p>
<p>Release Date: 2021-01-06</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.8</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve high detected in jackson databind jar cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api path to dependency file tmp ws scm test bolt build gradle path to vulnerable library root gradle caches modules files com fasterxml jackson core jackson databind jackson databind jar root gradle caches modules files com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy dropwizard core jar root library dropwizard jackson jar x jackson databind jar vulnerable library vulnerability details fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to org apache tomcat dbcp dbcp datasources peruserpooldatasource 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 com fasterxml jackson core jackson databind step up your open source security game with whitesource | 0 |
29,004 | 11,706,145,396 | IssuesEvent | 2020-03-07 20:12:43 | vlaship/graphql-resolver | https://api.github.com/repos/vlaship/graphql-resolver | opened | CVE-2019-14893 (Medium) detected in jackson-databind-2.9.9.3.jar | security vulnerability | ## CVE-2019-14893 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.9.3.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /tmp/ws-scm/graphql-resolver/build.gradle</p>
<p>Path to vulnerable library: /root/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.9.9.3/68ddd453458765757fd3ffca9437f9a42d91003e/jackson-databind-2.9.9.3.jar,/root/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.9.9.3/68ddd453458765757fd3ffca9437f9a42d91003e/jackson-databind-2.9.9.3.jar</p>
<p>
Dependency Hierarchy:
- graphql-spring-boot-starter-5.0.2.jar (Root Library)
- graphql-spring-boot-autoconfigure-5.0.2.jar
- graphql-java-servlet-6.1.2.jar
- :x: **jackson-databind-2.9.9.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vlaship/graphql-resolver/commit/69b2d878133579d23ef9f8bc407028c32bfc4a47">69b2d878133579d23ef9f8bc407028c32bfc4a47</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was discovered in FasterXML jackson-databind in all versions before 2.9.10 and 2.10.0, where it would permit polymorphic deserialization of malicious objects using the xalan JNDI gadget when used in conjunction with polymorphic type handling methods such as `enableDefaultTyping()` or when @JsonTypeInfo is using `Id.CLASS` or `Id.MINIMAL_CLASS` or in any other way which ObjectMapper.readValue might instantiate objects from unsafe sources. An attacker could use this flaw to execute arbitrary code.
<p>Publish Date: 2020-03-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14893>CVE-2019-14893</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14893">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14893</a></p>
<p>Release Date: 2020-03-02</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.10.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-2019-14893 (Medium) detected in jackson-databind-2.9.9.3.jar - ## CVE-2019-14893 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.9.3.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /tmp/ws-scm/graphql-resolver/build.gradle</p>
<p>Path to vulnerable library: /root/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.9.9.3/68ddd453458765757fd3ffca9437f9a42d91003e/jackson-databind-2.9.9.3.jar,/root/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.9.9.3/68ddd453458765757fd3ffca9437f9a42d91003e/jackson-databind-2.9.9.3.jar</p>
<p>
Dependency Hierarchy:
- graphql-spring-boot-starter-5.0.2.jar (Root Library)
- graphql-spring-boot-autoconfigure-5.0.2.jar
- graphql-java-servlet-6.1.2.jar
- :x: **jackson-databind-2.9.9.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vlaship/graphql-resolver/commit/69b2d878133579d23ef9f8bc407028c32bfc4a47">69b2d878133579d23ef9f8bc407028c32bfc4a47</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was discovered in FasterXML jackson-databind in all versions before 2.9.10 and 2.10.0, where it would permit polymorphic deserialization of malicious objects using the xalan JNDI gadget when used in conjunction with polymorphic type handling methods such as `enableDefaultTyping()` or when @JsonTypeInfo is using `Id.CLASS` or `Id.MINIMAL_CLASS` or in any other way which ObjectMapper.readValue might instantiate objects from unsafe sources. An attacker could use this flaw to execute arbitrary code.
<p>Publish Date: 2020-03-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14893>CVE-2019-14893</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14893">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14893</a></p>
<p>Release Date: 2020-03-02</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.10.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_test | cve medium detected in jackson databind jar cve medium severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file tmp ws scm graphql resolver build gradle path to vulnerable library root gradle caches modules files com fasterxml jackson core jackson databind jackson databind jar root gradle caches modules files com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy graphql spring boot starter jar root library graphql spring boot autoconfigure jar graphql java servlet jar x jackson databind jar vulnerable library found in head commit a href vulnerability details a flaw was discovered in fasterxml jackson databind in all versions before and where it would permit polymorphic deserialization of malicious objects using the xalan jndi gadget when used in conjunction with polymorphic type handling methods such as enabledefaulttyping or when jsontypeinfo is using id class or id minimal class or in any other way which objectmapper readvalue might instantiate objects from unsafe sources an attacker could use this flaw to execute arbitrary code 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 com fasterxml jackson core jackson databind step up your open source security game with whitesource | 0 |
12,528 | 5,205,446,415 | IssuesEvent | 2017-01-24 17:57:54 | GoogleCloudPlatform/google-cloud-eclipse | https://api.github.com/repos/GoogleCloudPlatform/google-cloud-eclipse | opened | Test failures do not make Travis build fail | bug build high priority | https://travis-ci.org/GoogleCloudPlatform/google-cloud-eclipse/jobs/194884620#L6687
Possible cause:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=490890
This is how Code Recommenders worked around it: http://git.eclipse.org/c/recommenders/org.eclipse.recommenders.git/commit/?id=5cd08804815230b9e6fb42002de0b6437eef5151
Another possibility is that we're running an older Tycho that is using the older Equinox.
Upgrading Tycho has a problem with our toolchain config.
From @briandealwis :
> Problem is that Tycho 0.26 (0.25?) requires Java 8. And so our tycho.toolchains won't work on Travis.
> Ah, we can have a .travis.yml rule to copy in a configured ~/.m2/toolchains.xml, and use the docker image to figure out what needs to be done
> I have part of this done as I explored going pomless a while back but hit this issue
Also Travis uses an older Maven version. | 1.0 | Test failures do not make Travis build fail - https://travis-ci.org/GoogleCloudPlatform/google-cloud-eclipse/jobs/194884620#L6687
Possible cause:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=490890
This is how Code Recommenders worked around it: http://git.eclipse.org/c/recommenders/org.eclipse.recommenders.git/commit/?id=5cd08804815230b9e6fb42002de0b6437eef5151
Another possibility is that we're running an older Tycho that is using the older Equinox.
Upgrading Tycho has a problem with our toolchain config.
From @briandealwis :
> Problem is that Tycho 0.26 (0.25?) requires Java 8. And so our tycho.toolchains won't work on Travis.
> Ah, we can have a .travis.yml rule to copy in a configured ~/.m2/toolchains.xml, and use the docker image to figure out what needs to be done
> I have part of this done as I explored going pomless a while back but hit this issue
Also Travis uses an older Maven version. | non_test | test failures do not make travis build fail possible cause this is how code recommenders worked around it another possibility is that we re running an older tycho that is using the older equinox upgrading tycho has a problem with our toolchain config from briandealwis problem is that tycho requires java and so our tycho toolchains won t work on travis ah we can have a travis yml rule to copy in a configured toolchains xml and use the docker image to figure out what needs to be done i have part of this done as i explored going pomless a while back but hit this issue also travis uses an older maven version | 0 |
274,336 | 8,559,761,365 | IssuesEvent | 2018-11-08 22:18:58 | wevote/WeVoteCordova | https://api.github.com/repos/wevote/WeVoteCordova | opened | Header styles: After Twitter sign in, notification box partially hidden under header | Priority: 2 | After Twitter sign in, notification box partially hidden under header.
| 1.0 | Header styles: After Twitter sign in, notification box partially hidden under header - After Twitter sign in, notification box partially hidden under header.
| non_test | header styles after twitter sign in notification box partially hidden under header after twitter sign in notification box partially hidden under header | 0 |
63,484 | 6,848,027,398 | IssuesEvent | 2017-11-13 17:06:58 | zephyrproject-rtos/zephyr | https://api.github.com/repos/zephyrproject-rtos/zephyr | closed | [Coverity CID: 178785] Incorrect expression in /tests/kernel/static_idt/src/static_idt.c | area: Tests bug priority: medium | Static code scan issues seen in File: /tests/kernel/static_idt/src/static_idt.c
Category: Incorrect expression
Function: testing_static_idt
Component: Tests
CID: 178785
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996 | 1.0 | [Coverity CID: 178785] Incorrect expression in /tests/kernel/static_idt/src/static_idt.c - Static code scan issues seen in File: /tests/kernel/static_idt/src/static_idt.c
Category: Incorrect expression
Function: testing_static_idt
Component: Tests
CID: 178785
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996 | test | incorrect expression in tests kernel static idt src static idt c static code scan issues seen in file tests kernel static idt src static idt c category incorrect expression function testing static idt component tests cid please fix or provide comments to square it off in coverity in the link | 1 |
61,529 | 6,742,083,947 | IssuesEvent | 2017-10-20 05:40:08 | owncloud/core | https://api.github.com/repos/owncloud/core | opened | speed up UI tests | 1 - To develop dev:acceptance-tests | - [ ] **create skeleton folder for users in UI tests without login**
Currently the UI tests that rely on multiple users to be fully set-up (have the skeleton directory files) do a login and logout, need to find a way to do it without a full login
- [ ] **redirect to page under test without going to files page**
After login every UI test lands on the files page, if we would navigate first to a page and then login we would save time that we currently spending in the files page
- [ ] **do not reload files page after login**
When the Files page is to be tested, the tests login, then navigate to the files page. But after a normal login we are already on the files page, so no need to waste time reloading.
- [ ] **fix #29264 (waitTillPageIsLoaded does not work correctly for trashbin)** | 1.0 | speed up UI tests - - [ ] **create skeleton folder for users in UI tests without login**
Currently the UI tests that rely on multiple users to be fully set-up (have the skeleton directory files) do a login and logout, need to find a way to do it without a full login
- [ ] **redirect to page under test without going to files page**
After login every UI test lands on the files page, if we would navigate first to a page and then login we would save time that we currently spending in the files page
- [ ] **do not reload files page after login**
When the Files page is to be tested, the tests login, then navigate to the files page. But after a normal login we are already on the files page, so no need to waste time reloading.
- [ ] **fix #29264 (waitTillPageIsLoaded does not work correctly for trashbin)** | test | speed up ui tests create skeleton folder for users in ui tests without login currently the ui tests that rely on multiple users to be fully set up have the skeleton directory files do a login and logout need to find a way to do it without a full login redirect to page under test without going to files page after login every ui test lands on the files page if we would navigate first to a page and then login we would save time that we currently spending in the files page do not reload files page after login when the files page is to be tested the tests login then navigate to the files page but after a normal login we are already on the files page so no need to waste time reloading fix waittillpageisloaded does not work correctly for trashbin | 1 |
673,613 | 23,022,628,650 | IssuesEvent | 2022-07-22 06:34:25 | okTurtles/group-income | https://api.github.com/repos/okTurtles/group-income | closed | Force users to enter their payment details if they indicate they're receiving [$25 bounty] | App:Frontend Level:Starter Priority:High Note:UI/UX Note:Bounty | ### Problem
Some users will indicate they have a financial need but will forget to entire their payment details. This makes it difficult for other users to pay them with manual mode because it increases coordination costs.
### Solution
The income details form should error if no payment details are entered.
### Bounty
$25 bounty for a clean solution to this (paid in cryptocurrency). | 1.0 | Force users to enter their payment details if they indicate they're receiving [$25 bounty] - ### Problem
Some users will indicate they have a financial need but will forget to entire their payment details. This makes it difficult for other users to pay them with manual mode because it increases coordination costs.
### Solution
The income details form should error if no payment details are entered.
### Bounty
$25 bounty for a clean solution to this (paid in cryptocurrency). | non_test | force users to enter their payment details if they indicate they re receiving problem some users will indicate they have a financial need but will forget to entire their payment details this makes it difficult for other users to pay them with manual mode because it increases coordination costs solution the income details form should error if no payment details are entered bounty bounty for a clean solution to this paid in cryptocurrency | 0 |
228,861 | 18,267,367,569 | IssuesEvent | 2021-10-04 10:00:48 | kyma-project/kyma | https://api.github.com/repos/kyma-project/kyma | closed | Failing tests on GKE 1.20.2-gke.2500 | area/ci test-failing area/api-gateway | **Description**
The `post-master-kyma-gke-rapid-integration` job started failing when the new version of GKE (1.20.2-gke.2500) appeared on the rapid channel.
First failure happened on 3.3.2021 - https://status.build.kyma-project.io/view/gcs/kyma-prow-logs/logs/post-master-kyma-gke-rapid-integration/1367004095398809600
Two tests are failing randomly:
- kyma-system/api-gateway
- kyma-system/rafter
**I am not sure if we should invest time in debugging** because of two reasons:
- this is a new gke version on the rapid channel - it may contain some bugs that will be fixed by google
- <s>api-gateway</s> and rafter are kind of deprecated, they might be gone till we migrate to 1.20
api-gateway is **NOT depracated**, so we might need to have a closer look into the issue
Since this job is red all the time we will disable reporting for now
**Related issue**
https://github.com/kyma-project/kyma/issues/10794 | 1.0 | Failing tests on GKE 1.20.2-gke.2500 - **Description**
The `post-master-kyma-gke-rapid-integration` job started failing when the new version of GKE (1.20.2-gke.2500) appeared on the rapid channel.
First failure happened on 3.3.2021 - https://status.build.kyma-project.io/view/gcs/kyma-prow-logs/logs/post-master-kyma-gke-rapid-integration/1367004095398809600
Two tests are failing randomly:
- kyma-system/api-gateway
- kyma-system/rafter
**I am not sure if we should invest time in debugging** because of two reasons:
- this is a new gke version on the rapid channel - it may contain some bugs that will be fixed by google
- <s>api-gateway</s> and rafter are kind of deprecated, they might be gone till we migrate to 1.20
api-gateway is **NOT depracated**, so we might need to have a closer look into the issue
Since this job is red all the time we will disable reporting for now
**Related issue**
https://github.com/kyma-project/kyma/issues/10794 | test | failing tests on gke gke description the post master kyma gke rapid integration job started failing when the new version of gke gke appeared on the rapid channel first failure happened on two tests are failing randomly kyma system api gateway kyma system rafter i am not sure if we should invest time in debugging because of two reasons this is a new gke version on the rapid channel it may contain some bugs that will be fixed by google api gateway and rafter are kind of deprecated they might be gone till we migrate to api gateway is not depracated so we might need to have a closer look into the issue since this job is red all the time we will disable reporting for now related issue | 1 |
297,697 | 25,756,992,973 | IssuesEvent | 2022-12-08 17:09:35 | golang/go | https://api.github.com/repos/golang/go | closed | x/vuln: tests consistently failing on Android builders due to missing "compile" tool starting 2022-11-02 | Testing OS-Android NeedsFix vulncheck or vulndb x/vuln | ```
--- FAIL: TestInits (0.20s)
callstacks_test.go:191: err: exit status 2: stderr: go: no such tool "compile"
FAIL
exitcode=1
FAIL golang.org/x/vuln/internal/govulncheck 46.719s
ok golang.org/x/vuln/internal/semver 46.828s
ok golang.org/x/vuln/internal/web 47.031s
ok golang.org/x/vuln/osv 46.925s
--- FAIL: TestSlicing (0.04s)
slicing_test.go:96: err: exit status 2: stderr: go: no such tool "compile"
--- FAIL: TestImports (0.95s)
source_test.go:117: err: exit status 2: stderr: go: no such tool "compile"
--- FAIL: TestRequires (0.07s)
source_test.go:259: err: exit status 2: stderr: go: no such tool "compile"
--- FAIL: TestCalls (0.06s)
source_test.go:496: err: exit status 2: stderr: go: no such tool "compile"
--- FAIL: TestFiltering (0.06s)
source_test.go:595: err: exit status 2: stderr: go: no such tool "compile"
--- FAIL: TestAllSymbolsVulnerable (0.05s)
source_test.go:686: err: exit status 2: stderr: go: no such tool "compile"
--- FAIL: TestNoSyntheticNodes (0.04s)
source_test.go:752: err: exit status 2: stderr: go: no such tool "compile"
--- FAIL: TestRecursion (0.07s)
source_test.go:833: err: exit status 2: stderr: go: no such tool "compile"
--- FAIL: TestConvert (0.09s)
vulncheck_test.go:414: err: exit status 2: stderr: go: no such tool "compile"
FAIL
exitcode=1
FAIL golang.org/x/vuln/vulncheck 48.377s
```
`greplogs -l -e '\Aandroid.*(\n.*)*no such tool "compile"(.*\n)*FAIL\s+golang\.org/x/vuln' --since=2022-07-01 --details`
<details>
[2022-12-07T18:18:50-05fb725-7c7cd56/android-386-emu](https://build.golang.org/log/df3d5a2541dc4919003ec8f8100df5ddb6822650)
[2022-12-07T18:18:50-05fb725-7c7cd56/android-amd64-emu](https://build.golang.org/log/6b80f79e84d2362ccd6d843bf40c5db996b47862)
[2022-12-07T16:56:12-05fb725-e57e673/android-386-emu](https://build.golang.org/log/fe23c75bec338b45e5252e4b64388f273a52035b)
[2022-12-07T16:56:12-05fb725-e57e673/android-amd64-emu](https://build.golang.org/log/841cf73bfb5302054f70b9d886ac5f58ca877490)
[2022-12-07T16:49:08-05fb725-3ec5085/android-386-emu](https://build.golang.org/log/4a8dc91edc92ee584f4458c0784258a4dd995cef)
[2022-12-07T16:49:08-05fb725-3ec5085/android-amd64-emu](https://build.golang.org/log/d499acbebc4f843ee70b424f105205b7a299810d)
[2022-12-07T16:26:42-05fb725-f715d28/android-386-emu](https://build.golang.org/log/109069ae258e9ced451aa021384176f4fbf1f7e9)
[2022-12-07T16:26:42-05fb725-f715d28/android-amd64-emu](https://build.golang.org/log/0954970ac4c6c51924e7c24631146c4e07b842e3)
[2022-12-07T16:09:09-05fb725-7ed50cf/android-386-emu](https://build.golang.org/log/78c52487b1f82711a4ca38b60745f954c43ab5f1)
[2022-12-07T16:09:09-05fb725-7ed50cf/android-amd64-emu](https://build.golang.org/log/03ce4d1d4caf4603c420f2f8c4ee57c0b7313f2b)
[2022-12-07T14:20:49-05fb725-a4a86c7/android-386-emu](https://build.golang.org/log/50c95b71e82aa86a5cfe50de735b73ac17005b8e)
[2022-12-07T14:20:49-05fb725-a4a86c7/android-amd64-emu](https://build.golang.org/log/660a3c8c0f94b8165815dde702f496f1fc09f1a9)
[2022-12-07T03:45:50-05fb725-a398963/android-386-emu](https://build.golang.org/log/d7f426e7105822a0e1ec294770265e64933c08a9)
[2022-12-07T03:45:50-05fb725-a398963/android-amd64-emu](https://build.golang.org/log/c94d2371bbb4eaba27a29249d8b14fd61085db96)
[2022-12-07T00:51:44-05fb725-8cd931f/android-386-emu](https://build.golang.org/log/7607df4f33f1b29922006c495440c214cc0b1993)
[2022-12-07T00:51:44-05fb725-8cd931f/android-amd64-emu](https://build.golang.org/log/afebdc430d5984896dc37a538a522e34e2df9b78)
[2022-12-07T00:25:27-05fb725-10bb003/android-386-emu](https://build.golang.org/log/ed68456a838ed44c925c31d27e9773ca888c2bf2)
[2022-12-07T00:25:27-05fb725-10bb003/android-amd64-emu](https://build.golang.org/log/57a2783beaf7ab6586786cf53f4164de6deb88d3)
[2022-12-06T23:50:47-05fb725-7dc9fcb/android-386-emu](https://build.golang.org/log/bad6bf1d32481d461fcfe978477c46dfd84d0b69)
[2022-12-06T23:50:47-05fb725-7dc9fcb/android-amd64-emu](https://build.golang.org/log/ac919e077aaf92f970948686e719b687d1aebc67)
[2022-12-06T22:07:25-05fb725-e535d67/android-386-emu](https://build.golang.org/log/6625c5e418829a90ff42418800087e45a41ca610)
[2022-12-06T22:07:25-05fb725-e535d67/android-amd64-emu](https://build.golang.org/log/0f2250edd358e01bff6cacdd2fd075c287fcff57)
[2022-12-06T20:53:50-05fb725-89871dd/android-386-emu](https://build.golang.org/log/e2e3d2dfecbed667267f90e08a1b56b942058fe5)
[2022-12-06T20:53:50-05fb725-89871dd/android-amd64-emu](https://build.golang.org/log/e2e4726473bc2dde67c9c5389e6309f9c4f7ecb6)
[2022-12-06T20:19:47-05fb725-5167e5c/android-386-emu](https://build.golang.org/log/fab02b887e7de4daad26c88240779715a7520d38)
[2022-12-06T20:19:47-05fb725-5167e5c/android-amd64-emu](https://build.golang.org/log/e7faafd1b76281672895f1c2f11ee82aded68be3)
[2022-12-06T19:52:35-05fb725-03bf6f4/android-386-emu](https://build.golang.org/log/61179b3ae900489e1d6b23e0be3798f90464c9ee)
[2022-12-06T19:52:35-05fb725-03bf6f4/android-amd64-emu](https://build.golang.org/log/d638646a0e21b29c2139567af2fc30c5c8dfa22f)
[2022-12-06T18:32:51-05fb725-dfd13ce/android-386-emu](https://build.golang.org/log/2716f500526787d1c8cb6508aaaf0f3f4e66f9a4)
[2022-12-06T18:32:51-05fb725-dfd13ce/android-amd64-emu](https://build.golang.org/log/a59ac8de75daa20c9e8e7003a70446d145b60dcf)
[2022-12-06T18:11:17-05fb725-98da0fb/android-386-emu](https://build.golang.org/log/683c90b9c1fb301a24a125beefc457c40245a5f6)
[2022-12-06T18:11:17-05fb725-98da0fb/android-amd64-emu](https://build.golang.org/log/1ea97fb384febc4cb1be8d984e57e23b4e03bd24)
[2022-12-06T15:55:39-05fb725-fe67a21/android-386-emu](https://build.golang.org/log/61ba39efde488243ce672ae8cefe97b623515858)
[2022-12-06T15:55:39-05fb725-fe67a21/android-amd64-emu](https://build.golang.org/log/4ee32c27e0633841fc508f6392afe7efab9f866c)
[2022-12-06T05:12:12-05fb725-1eb0465/android-386-emu](https://build.golang.org/log/fcc31a797775dc0b4b1b27626017a2c4297baf5d)
[2022-12-06T05:12:12-05fb725-1eb0465/android-amd64-emu](https://build.golang.org/log/12d3415c3889aaf4b6fc1ba266b6d1a7502fd21a)
[2022-12-05T23:21:07-05fb725-9dde2de/android-386-emu](https://build.golang.org/log/6c79cb21c103377045d64db8221634cfd8a2f3e3)
[2022-12-05T23:21:07-05fb725-9dde2de/android-amd64-emu](https://build.golang.org/log/7e80fcc106e7a359ba621d8ea56abd1de2254bc7)
[2022-12-05T22:29:44-05fb725-0b323a3/android-386-emu](https://build.golang.org/log/29dfb72748ab8164328c43e0d7e568b8fe0094bb)
[2022-12-05T22:29:44-05fb725-0b323a3/android-amd64-emu](https://build.golang.org/log/d9804cc43389fd119cbe45b7e44cec88143b087b)
[2022-12-05T22:22:11-05fb725-9e05963/android-386-emu](https://build.golang.org/log/8a9fa3e0cc973c6ae150676d95a95b70f5e3fea9)
[2022-12-05T22:22:11-05fb725-9e05963/android-amd64-emu](https://build.golang.org/log/90510d6456366a7202c928a1d3870f125f4c9d8a)
[2022-12-05T22:01:50-05fb725-185e1a7/android-386-emu](https://build.golang.org/log/64fcd68d6481ee2e0d2ab64497a4696e3add4a9e)
[2022-12-05T22:01:50-05fb725-185e1a7/android-amd64-emu](https://build.golang.org/log/c2d8747efa0a56d487cbd8dac2a9bbd0237e4534)
[2022-12-05T20:45:49-05fb725-a5b10be/android-386-emu](https://build.golang.org/log/e94339fea0c9f71b1a6425f38101773681e03d52)
[2022-12-05T20:45:49-05fb725-a5b10be/android-amd64-emu](https://build.golang.org/log/d86b3daaa17276df1ede6751f4ef5d27795b6af3)
[2022-12-05T19:25:34-05fb725-b45cb0c/android-386-emu](https://build.golang.org/log/c71584294642cf8eac91ad8943d546475b1b80ce)
[2022-12-05T19:25:34-05fb725-b45cb0c/android-amd64-emu](https://build.golang.org/log/bda0b623f86636d2161f52b76b5b6220d7a90229)
[2022-12-05T18:57:04-05fb725-2986358/android-386-emu](https://build.golang.org/log/9eaa4e62d58fa4b76306f80adcc55d0fdd8cfb93)
[2022-12-05T18:57:04-05fb725-2986358/android-amd64-emu](https://build.golang.org/log/bdcae6a7b27500a6a0b84579899a533ea1c302e2)
[2022-12-05T16:41:48-05fb725-ad55b87/android-386-emu](https://build.golang.org/log/6a3bd0b4f43073d26dedbdcd3603fd5d87a183f5)
[2022-12-05T16:41:48-05fb725-ad55b87/android-amd64-emu](https://build.golang.org/log/62c228dca71a1c3ec549fd24f810fca3d21cca6d)
[2022-12-03T17:08:51-05fb725-3a7a528/android-386-emu](https://build.golang.org/log/48f6a7361afc246edc9ec4f9a89a10d7012c19f7)
[2022-12-03T17:08:51-05fb725-3a7a528/android-amd64-emu](https://build.golang.org/log/3a1667a09610baa0678ec9b9ae98f041721fcb1a)
[2022-12-02T23:40:37-05fb725-c0497d1/android-386-emu](https://build.golang.org/log/93c606f8a157d4581e03e1dc7f6d3fe12e3fccf7)
[2022-12-02T23:40:37-05fb725-c0497d1/android-amd64-emu](https://build.golang.org/log/88520d9f612e5862be367ccaec10f253abbf1dbd)
[2022-12-02T22:24:00-05fb725-7ab3615/android-386-emu](https://build.golang.org/log/785db740749be82de36d2aae04a560c606e97ebc)
[2022-12-02T22:24:00-05fb725-7ab3615/android-amd64-emu](https://build.golang.org/log/2d6bffbe6cc95abe9e495ccf7aae6ff52c622f8c)
[2022-12-02T21:15:10-05fb725-45f5ef4/android-386-emu](https://build.golang.org/log/34e30991324b04c4b467e3cc72af920c04d1297a)
[2022-12-02T21:15:10-05fb725-45f5ef4/android-amd64-emu](https://build.golang.org/log/c1bb9b05722edade39c19d039ebe552ab35c81c2)
[2022-11-22T16:07:28-fac3670-9160e15/android-386-emu](https://build.golang.org/log/44c0c88823366b1a9ce0c6c760b98eb25af1ab83)
[2022-11-22T16:07:28-fac3670-9160e15/android-amd64-emu](https://build.golang.org/log/7756f10d2bc2d0d1dd778ae65f2c184150553a5b)
[2022-11-22T15:58:43-fac3670-5c9a506/android-386-emu](https://build.golang.org/log/789f7a142046593e4e74ac8cdc6291977f67386a)
[2022-11-22T15:58:43-fac3670-5c9a506/android-amd64-emu](https://build.golang.org/log/22cf185e9da7ab58a50e6fe23a0cbb7b54725404)
[2022-11-22T14:09:24-fac3670-9efc5a5/android-386-emu](https://build.golang.org/log/b1af713617d86ea28743b5a489c3f963fe2f677c)
[2022-11-22T14:09:24-fac3670-9efc5a5/android-amd64-emu](https://build.golang.org/log/634122570bfa647c598dd188c06f4d55267d1d59)
[2022-11-22T03:11:31-fac3670-6a72514/android-386-emu](https://build.golang.org/log/d396c1d36a9e04739b733c3de5708490e1881035)
[2022-11-22T03:11:31-fac3670-6a72514/android-amd64-emu](https://build.golang.org/log/b5861dfcf5a87b22134b5389f9750bd776f0905f)
[2022-11-22T02:52:19-fac3670-f41fdc1/android-386-emu](https://build.golang.org/log/aca50ba6c17ee89da7661a813f31fd8a6d536969)
[2022-11-22T02:52:19-fac3670-f41fdc1/android-amd64-emu](https://build.golang.org/log/6f07f896b5a0f115d656de5e1d49fb3516d9dd97)
[2022-11-22T02:27:05-fac3670-14a4138/android-386-emu](https://build.golang.org/log/e396a1806338d61acb49af8d332f59c3433b24aa)
[2022-11-22T02:27:05-fac3670-14a4138/android-amd64-emu](https://build.golang.org/log/95a7a39b2fba65d81cd245193a57da74ef8665f7)
[2022-11-22T01:42:49-fac3670-1521199/android-386-emu](https://build.golang.org/log/8c1a5a39a86958f521dfde14657d383df4fae490)
[2022-11-22T01:42:49-fac3670-1521199/android-amd64-emu](https://build.golang.org/log/78280b6974ed0c1929510fe4d2919d77bb6f2c1f)
[2022-11-21T22:49:25-fac3670-1c9eba1/android-386-emu](https://build.golang.org/log/bce99df3eabf0d10f21fcad73842bfb63780952e)
[2022-11-21T22:49:25-fac3670-1c9eba1/android-amd64-emu](https://build.golang.org/log/3ed25d387749e344e9aef936fbe4274945e19477)
[2022-11-21T22:43:41-fac3670-7656cba/android-386-emu](https://build.golang.org/log/089bdfcad3ce2fa872098d187419786d046f8ac9)
[2022-11-21T22:43:41-fac3670-7656cba/android-amd64-emu](https://build.golang.org/log/75cff201e73093c88880299f03a9016ce9f6dade)
[2022-11-21T22:21:04-fac3670-d58f2e7/android-386-emu](https://build.golang.org/log/14af01de13a5bb5a349b4359475107359073452e)
[2022-11-21T22:21:04-fac3670-d58f2e7/android-amd64-emu](https://build.golang.org/log/76164bbc0fdcdada8c88d35b99070dcde2e97c41)
[2022-11-21T22:16:06-fac3670-995c0f3/android-386-emu](https://build.golang.org/log/962b1aee2d83b7d8ea4722e08c526305f16332e7)
[2022-11-21T22:16:06-fac3670-995c0f3/android-amd64-emu](https://build.golang.org/log/c433d3521a84d36effbb4da85f6f0fb893900611)
[2022-11-21T21:55:53-fac3670-089dcd7/android-386-emu](https://build.golang.org/log/8b4b99875bbce770d405a019629bdffa915ad501)
[2022-11-21T21:55:53-fac3670-089dcd7/android-amd64-emu](https://build.golang.org/log/aecd64f91c7a8498a6f658d6a638bfcd47f05f07)
[2022-11-21T21:14:38-fac3670-85a2c19/android-386-emu](https://build.golang.org/log/8a63f66aae06a66e2f1ca462247666ccd1df7a90)
[2022-11-21T21:14:38-fac3670-85a2c19/android-amd64-emu](https://build.golang.org/log/0a3c74f2fdeac9489fac098f0ee3767f979c2d48)
[2022-11-16T20:18:50-50a0e29-e6eaf39/android-386-emu](https://build.golang.org/log/9ec5e2dca09ca9e0d50826a64ecb457bc47a6a4a)
[2022-11-16T20:18:50-50a0e29-e6eaf39/android-amd64-emu](https://build.golang.org/log/e0896223e854a31d9d85a284319b38f6c1e43997)
[2022-11-16T19:00:20-50a0e29-cd9d26f/android-386-emu](https://build.golang.org/log/895587cef56226ad44de16491cbf43b114043f4a)
[2022-11-16T19:00:20-50a0e29-cd9d26f/android-amd64-emu](https://build.golang.org/log/b5ae3e2de7b0ab7f9b16663e8c4cef7be6838873)
[2022-11-16T17:22:19-50a0e29-8c17505/android-386-emu](https://build.golang.org/log/e2978a9b033e6608828eac81e122edc984dcd5eb)
[2022-11-16T17:22:19-50a0e29-8c17505/android-amd64-emu](https://build.golang.org/log/68dac71f360ac16491a3c48f8232c505c03c2dd5)
[2022-11-16T16:42:18-50a0e29-0266671/android-386-emu](https://build.golang.org/log/3dd090156d0a3dceb6e8de599ba452581f100aa4)
[2022-11-16T16:42:18-50a0e29-0266671/android-amd64-emu](https://build.golang.org/log/39e87a7004c9b6b38841c3b9c0d0830c5791db91)
[2022-11-16T16:25:58-50a0e29-38218f3/android-386-emu](https://build.golang.org/log/b9ce1e0681b9efad08e0ffeda34d8ecd51a510d6)
[2022-11-16T16:25:58-50a0e29-38218f3/android-amd64-emu](https://build.golang.org/log/191f3c9a5631da6275f3de69848e4a9cf861e6ff)
[2022-11-16T15:10:02-50a0e29-70f585f/android-386-emu](https://build.golang.org/log/2ea7e504358569e590c71647c576189145137219)
[2022-11-16T15:10:02-50a0e29-70f585f/android-amd64-emu](https://build.golang.org/log/da136101f911b75dc6faa6c8ff5dd69b03a1053e)
[2022-11-16T14:42:36-50a0e29-978ce7e/android-386-emu](https://build.golang.org/log/3897060fb992cfb202c8495ea745598afdac5561)
[2022-11-16T14:42:36-50a0e29-978ce7e/android-amd64-emu](https://build.golang.org/log/d385c9fc65723cbc508cb4f1808473f01b50aeea)
[2022-11-16T14:38:38-50a0e29-7c8c209/android-386-emu](https://build.golang.org/log/ece8e174fac3a1ac070c0f0e428f0a3188fffff6)
[2022-11-16T14:38:38-50a0e29-7c8c209/android-amd64-emu](https://build.golang.org/log/16d3ca2e74c67e74d0fda288fa7913a261576f6d)
[2022-11-16T13:26:16-50a0e29-5947a07/android-386-emu](https://build.golang.org/log/b096640e57e76a6dd69a679c02eda4cacdd2199f)
[2022-11-16T13:26:16-50a0e29-5947a07/android-amd64-emu](https://build.golang.org/log/bd00ee89e6430270a4042f153504bd01ab6160bb)
[2022-11-16T04:04:52-50a0e29-b1678e5/android-386-emu](https://build.golang.org/log/6f35c68bd01ba276446a1b13711554ba1007535e)
[2022-11-16T04:04:52-50a0e29-b1678e5/android-amd64-emu](https://build.golang.org/log/d1c77534c6773346a2404a269dd8eb170c7612b9)
[2022-11-16T02:02:26-50a0e29-cb5534c/android-386-emu](https://build.golang.org/log/9e77a365bcb090fe469a43c9d3dff8be09dec3e7)
[2022-11-16T02:02:26-50a0e29-cb5534c/android-amd64-emu](https://build.golang.org/log/91d9387b07cee23faf625eccc156596615e56f02)
[2022-11-15T23:48:34-50a0e29-c085c6c/android-386-emu](https://build.golang.org/log/44e7d5f57e6157fa6484cdd3d3ad1f7c4a4fcf63)
[2022-11-15T23:48:34-50a0e29-c085c6c/android-amd64-emu](https://build.golang.org/log/367820e15f0f80edf4efea6e10df98dddc422115)
[2022-11-15T22:52:03-50a0e29-8477562/android-386-emu](https://build.golang.org/log/170da895bb9a904121f507ca33835dbc172d020a)
[2022-11-15T22:52:03-50a0e29-8477562/android-amd64-emu](https://build.golang.org/log/ff8d14c0bbe85fbb26bc434aa84bc297bcb24937)
[2022-11-11T16:04:21-3af8368-fcd14bd/android-386-emu](https://build.golang.org/log/99dffdc735422a5e73d61612138a41474f111e6e)
[2022-11-11T16:04:21-3af8368-fcd14bd/android-amd64-emu](https://build.golang.org/log/8e6610e283d426c1a56075c674b90175f191c2c2)
[2022-11-11T14:51:14-3af8368-fffda6b/android-386-emu](https://build.golang.org/log/cbe581e45312d8f5738201bd948313dd3e425457)
[2022-11-11T14:51:14-3af8368-fffda6b/android-amd64-emu](https://build.golang.org/log/3fbd0ae2deaa8c21f92092691597d7f815a207af)
[2022-11-11T14:48:29-3af8368-73f987c/android-386-emu](https://build.golang.org/log/a59e56a9f476461375ddc7b850248c284b7ca934)
[2022-11-11T14:48:29-3af8368-73f987c/android-amd64-emu](https://build.golang.org/log/4c0ae6927ba3d49d9e43f68a1a013476717988db)
[2022-11-11T04:31:34-3af8368-185766d/android-386-emu](https://build.golang.org/log/9c53d786e08ba9288558fc4ca22b161be79ab5e0)
[2022-11-11T04:31:34-3af8368-185766d/android-amd64-emu](https://build.golang.org/log/6d9da936c2613f0cd7bdfbfa82a5ab02e9dd496c)
[2022-11-11T01:42:03-3af8368-d62f8d5/android-386-emu](https://build.golang.org/log/c4b92731968895e538c863f15c9bc987ce154fa7)
[2022-11-11T01:42:03-3af8368-d62f8d5/android-amd64-emu](https://build.golang.org/log/ccbbc9133304e8c777d34703904b5b956a5e7546)
[2022-11-11T01:35:11-3af8368-ffc4496/android-386-emu](https://build.golang.org/log/245aefd3fdc1b126f1f39c09ec17e083e7b7fa7a)
[2022-11-11T01:35:11-3af8368-ffc4496/android-amd64-emu](https://build.golang.org/log/915b1ac32e1d108071bb5d099e2ed99f438326d1)
[2022-11-11T01:29:15-3af8368-4d37f96/android-386-emu](https://build.golang.org/log/9b9d0f106fe2f07584aba663a00b070690aed131)
[2022-11-11T01:29:15-3af8368-4d37f96/android-amd64-emu](https://build.golang.org/log/e9f785c5f0f1a32d6965fe7af0723d10ec5cd984)
[2022-11-10T23:11:59-3af8368-1b03568/android-386-emu](https://build.golang.org/log/78f2f0b344547d58dc1a58afde87c60ff5d28484)
[2022-11-10T23:11:59-3af8368-1b03568/android-amd64-emu](https://build.golang.org/log/8c594aeb5c4b5c8618dcb944884042a004a080ee)
[2022-11-10T22:41:06-3af8368-5497300/android-386-emu](https://build.golang.org/log/cc269ed2894d1715c12da2afeee93ff897b5cad5)
[2022-11-10T22:41:06-3af8368-5497300/android-amd64-emu](https://build.golang.org/log/b62ab7088100f0833c13238c49e31384597069d2)
[2022-11-10T21:11:02-3af8368-79950a4/android-386-emu](https://build.golang.org/log/e28f0e1bb16d07ab5924991a5e9b2783416c2eaa)
[2022-11-10T21:11:02-3af8368-79950a4/android-amd64-emu](https://build.golang.org/log/c571a63c3fdcc581f50e1d90b3a594ad97168c0e)
[2022-11-10T20:44:45-3af8368-14018c8/android-386-emu](https://build.golang.org/log/6796c686249c5e3d2152fea5eeb097091eb1eade)
[2022-11-10T20:44:45-3af8368-14018c8/android-amd64-emu](https://build.golang.org/log/5b0c9eace199346b870705ad6383a6daac54f268)
[2022-11-10T20:38:57-3af8368-d96eb82/android-386-emu](https://build.golang.org/log/fcf0378b19347e527bc43109e686731fa62fbcc1)
[2022-11-10T20:38:57-3af8368-d96eb82/android-amd64-emu](https://build.golang.org/log/8cf10139a2e7bb2b626b4d4b7c21e748e7e1405f)
[2022-11-10T20:24:57-3af8368-f57ebed/android-386-emu](https://build.golang.org/log/076c2ab4d6c7bb0f3b193ebd91efa497de5f0d4e)
[2022-11-10T20:24:57-3af8368-f57ebed/android-amd64-emu](https://build.golang.org/log/e32240c73c58465983f8c4b5e52bcdcac162a7aa)
[2022-11-09T20:13:45-fc17c87-d02fceb/android-386-emu](https://build.golang.org/log/f9d329124eecb47e6d0ef5d82696ff8f956c81fb)
[2022-11-09T20:13:45-fc17c87-d02fceb/android-amd64-emu](https://build.golang.org/log/0aec9d3abf17a3350aa00761319729e5adc2899a)
[2022-11-09T19:40:02-1943a78-d02fceb/android-386-emu](https://build.golang.org/log/394ffe29262fb8ebe44e851485440f67865a224d)
[2022-11-09T19:40:02-1943a78-d02fceb/android-amd64-emu](https://build.golang.org/log/702ce791710c1512453be97be3ff52603cafceb1)
[2022-11-09T18:21:12-1943a78-342751a/android-386-emu](https://build.golang.org/log/a7f75d269d162aca39060cfbe54d928c9b056c0e)
[2022-11-09T18:21:12-1943a78-342751a/android-amd64-emu](https://build.golang.org/log/b1bfd4ec56cb92edc7e35d61728f9a4cb0a3740a)
[2022-11-09T18:07:37-1943a78-4f13067/android-386-emu](https://build.golang.org/log/5c017ba08bb9a5e3e83e7db186b5e1a8e48ee56f)
[2022-11-09T18:07:37-1943a78-4f13067/android-amd64-emu](https://build.golang.org/log/43175615bad629907c6f57407cd50fb8ec65d517)
[2022-11-09T18:05:45-1943a78-2f4d5c3/android-386-emu](https://build.golang.org/log/c8ade0a530577d98444161ec1e756cc3362a92ad)
[2022-11-09T18:05:45-1943a78-2f4d5c3/android-amd64-emu](https://build.golang.org/log/1d4c43d6abecbf90633a5eaa2934bcbc24df627f)
[2022-11-09T17:41:34-6a111ce-2f4d5c3/android-386-emu](https://build.golang.org/log/1831ba1a6f3dc8b794e9dfbffcfc06a359ee31e2)
[2022-11-09T17:41:34-6a111ce-2f4d5c3/android-amd64-emu](https://build.golang.org/log/c2d687d8941f0e60611b508266e9191df50a64cd)
[2022-11-09T17:33:07-6a111ce-7a92c4f/android-386-emu](https://build.golang.org/log/9d03e3b23205f031dd8119c74accdbe4b87ac2f8)
[2022-11-09T17:33:07-6a111ce-7a92c4f/android-amd64-emu](https://build.golang.org/log/c27d69fd3cc62bb13ff5be1f89bd6418003baf88)
[2022-11-09T16:52:00-6a111ce-9ff2a66/android-386-emu](https://build.golang.org/log/214d2cd818f9c45a5511ab1cbebf026e96009922)
[2022-11-09T16:52:00-6a111ce-9ff2a66/android-amd64-emu](https://build.golang.org/log/9d2ca9b361b6ff66e6cb9c2332067ee482a40113)
[2022-11-09T14:47:58-55c64d8-9ff2a66/android-386-emu](https://build.golang.org/log/249dce179fffa1048027eb7b9251e33b01040b07)
[2022-11-09T14:47:58-55c64d8-9ff2a66/android-amd64-emu](https://build.golang.org/log/6cf07fd32bc75cbc463cb4752537834e51d84b63)
[2022-11-09T14:05:53-55c64d8-821e310/android-386-emu](https://build.golang.org/log/449c91239072bc75fbf732bc7f8a32cae326f66b)
[2022-11-09T14:05:53-55c64d8-821e310/android-amd64-emu](https://build.golang.org/log/0891064a60c66d0759612b4e40d3fc0538afa6b7)
[2022-11-09T06:30:59-55c64d8-3a41094/android-386-emu](https://build.golang.org/log/c134c6ab25c8613bf473a2ecebef850631ecaabc)
[2022-11-09T06:30:59-55c64d8-3a41094/android-amd64-emu](https://build.golang.org/log/cc67b6a1292d49d8b0ece7371f0b0b94fcfa8b58)
[2022-11-09T06:10:55-55c64d8-268f462/android-386-emu](https://build.golang.org/log/d44bd6a714e706136eab1da7a9866fcdecfc34b2)
[2022-11-09T06:10:55-55c64d8-268f462/android-amd64-emu](https://build.golang.org/log/a8ac1837afe71ff55585eb15a4c2896f862e21b6)
[2022-11-09T04:03:15-55c64d8-6b45863/android-386-emu](https://build.golang.org/log/9f32aed5090bcf35c642c8a90de240ce53352b90)
[2022-11-09T04:03:15-55c64d8-6b45863/android-amd64-emu](https://build.golang.org/log/0fe4c1a77ae8533f002bf47bd1dd029bdf2ba36c)
[2022-11-09T03:01:33-55c64d8-27c3814/android-386-emu](https://build.golang.org/log/824eab70eeaf080ddf89f77b9dd138d081a31928)
[2022-11-09T03:01:33-55c64d8-27c3814/android-amd64-emu](https://build.golang.org/log/67330d8f0fbf90b80cb517240443c248f8cc6487)
[2022-11-08T23:11:32-55c64d8-fe4e59e/android-386-emu](https://build.golang.org/log/8ab4dfb77213e148942718f7ebcf4ff218629709)
[2022-11-08T23:11:32-55c64d8-fe4e59e/android-amd64-emu](https://build.golang.org/log/829455b6b3c5ed7a911382da457434efa67275b5)
[2022-11-08T22:14:56-55c64d8-896faf3/android-386-emu](https://build.golang.org/log/e915f2e6f3e37aef9b06605fe50fa1f51e7280e1)
[2022-11-08T22:14:56-55c64d8-896faf3/android-amd64-emu](https://build.golang.org/log/3bca29eaca68b265f1685b356f0043bff1b72b6b)
[2022-11-08T21:50:06-55c64d8-8befe0e/android-386-emu](https://build.golang.org/log/018140f94b37af65083b1b841764fb2f60b9d559)
[2022-11-08T21:50:06-55c64d8-8befe0e/android-amd64-emu](https://build.golang.org/log/519976938170aa82948f2d170d265fdc0e5b73ee)
[2022-11-08T21:31:58-55c64d8-2df6c1a/android-386-emu](https://build.golang.org/log/7a3bfb66ed704395978f71993027bd86aa2799ca)
[2022-11-08T21:31:58-55c64d8-2df6c1a/android-amd64-emu](https://build.golang.org/log/b88574f97ddc96a9c21c703e170f1683d9f92cb2)
[2022-11-08T21:26:09-55c64d8-9944ba7/android-386-emu](https://build.golang.org/log/3208f3a369876c325963ffa171813be9a02d2a7f)
[2022-11-08T21:26:09-55c64d8-9944ba7/android-amd64-emu](https://build.golang.org/log/3bcd693995f1aadedf2b410071e979a85ce92b7f)
[2022-11-08T20:59:42-55c64d8-a7538d7/android-386-emu](https://build.golang.org/log/3bd869d0767ccfccdb63e8bce47769402cbdca02)
[2022-11-08T20:59:42-55c64d8-a7538d7/android-amd64-emu](https://build.golang.org/log/783972bc48b471f2459713b32762f38af874b64b)
[2022-11-08T14:15:17-4f561ca-be3184c/android-386-emu](https://build.golang.org/log/d229c7e54dd407024824796cda3cce03404a9149)
[2022-11-08T14:15:17-4f561ca-be3184c/android-amd64-emu](https://build.golang.org/log/f633c70c5dfff5a51506d99a26106e5268289011)
[2022-11-08T13:51:16-4f561ca-5b42f89/android-386-emu](https://build.golang.org/log/b1b59ec7f8c72b09675086d329bcb74a1ef8e5ca)
[2022-11-08T13:51:16-4f561ca-5b42f89/android-amd64-emu](https://build.golang.org/log/ffb1421423a3cf5d3d5476acf1250ace3013ac22)
[2022-11-08T08:14:37-4f561ca-0b7aa9f/android-386-emu](https://build.golang.org/log/3757bab47b1ec83aee8bf03752c1ebc5e86b0e70)
[2022-11-08T08:14:37-4f561ca-0b7aa9f/android-amd64-emu](https://build.golang.org/log/23b856b0786671971187b76df9574de5aaecdc5c)
[2022-11-08T05:24:43-4f561ca-9860faa/android-386-emu](https://build.golang.org/log/cc5b9757f586a0467e691309d2ca96855e4c3028)
[2022-11-08T05:24:43-4f561ca-9860faa/android-amd64-emu](https://build.golang.org/log/38c0402cf1509e03c3c9f725100257c77bdf222a)
[2022-11-03T21:13:39-6f7a8cb-69abfab/android-386-emu](https://build.golang.org/log/9d5e0457773186b0d275e86ca91f6c6dde3868f9)
[2022-11-03T21:13:39-6f7a8cb-69abfab/android-amd64-emu](https://build.golang.org/log/b5186566b5ebc8e0490a0b064faad9748bdd4a5d)
[2022-11-03T20:35:31-6f7a8cb-aa6240a/android-386-emu](https://build.golang.org/log/f6899acf83fea70aed92671ff0a53f0fb526eaf0)
[2022-11-03T20:35:31-6f7a8cb-aa6240a/android-amd64-emu](https://build.golang.org/log/0fab81d0e0813f8307eaa010d8faf8f384039870)
[2022-11-03T20:32:06-6f7a8cb-48ff5c1/android-386-emu](https://build.golang.org/log/884a57f60a04bd710ef2a76bd01dba30d2504b67)
[2022-11-03T20:32:06-6f7a8cb-48ff5c1/android-amd64-emu](https://build.golang.org/log/c49e35c7493785db6b9e7a4d0b34ea366d15cecc)
[2022-11-03T19:59:19-6f7a8cb-d031e9e/android-386-emu](https://build.golang.org/log/18d8905eb07bea643536d4ca00e7493f3945b9cb)
[2022-11-03T19:59:19-6f7a8cb-d031e9e/android-amd64-emu](https://build.golang.org/log/c0de714b9cbfc50895df86fe99cf3a5eed8f40ef)
[2022-11-03T19:40:36-6f7a8cb-c065bc7/android-386-emu](https://build.golang.org/log/5c92f9d577e9f66e3e2d9d11a2a710bc3ddbfe84)
[2022-11-03T19:40:36-6f7a8cb-c065bc7/android-amd64-emu](https://build.golang.org/log/1edb20a8d67f536ed401700f0c807dc6c0e5c583)
[2022-11-03T19:34:40-6f7a8cb-3511c82/android-386-emu](https://build.golang.org/log/f115e2a15d3115aa02dc27299e8e23eb597744fc)
[2022-11-03T19:34:40-6f7a8cb-3511c82/android-amd64-emu](https://build.golang.org/log/1448b5a85f06c3dbeee548a4f7aa02e521b4eb92)
[2022-11-03T18:33:42-6f7a8cb-44cabb8/android-386-emu](https://build.golang.org/log/86c4761a2b8a1e41b811afe1031e1ae6b0907ac3)
[2022-11-03T18:33:42-6f7a8cb-44cabb8/android-amd64-emu](https://build.golang.org/log/277278aa27a63ecc6f40a84904aaa78b839415b2)
[2022-11-03T18:31:08-6f7a8cb-0b76e32/android-386-emu](https://build.golang.org/log/fdf9afba8cb99ccc5f25590ec549613ff130e113)
[2022-11-03T18:31:08-6f7a8cb-0b76e32/android-amd64-emu](https://build.golang.org/log/63f86036dc45ab0f4571642b365abb61e141e45a)
[2022-11-03T17:41:32-f9bfb22-0b76e32/android-386-emu](https://build.golang.org/log/7e3c5ea5def77437d2857f4687d65deb9887a52c)
[2022-11-03T17:41:32-f9bfb22-0b76e32/android-amd64-emu](https://build.golang.org/log/2a7da06f2334d75992f0d638ee22a91056ea6ea5)
[2022-11-03T17:08:32-f9bfb22-667c53e/android-386-emu](https://build.golang.org/log/e8ebb71072eebfe5ed318ee9ca86f77caaf45df3)
[2022-11-03T17:08:32-f9bfb22-667c53e/android-amd64-emu](https://build.golang.org/log/8a8f03d568dea3748594190b79a9c0972785dd28)
[2022-11-03T17:01:54-995372c-667c53e/android-386-emu](https://build.golang.org/log/691b6bab3335a52afe41cb1d994d064ac09afb00)
[2022-11-03T17:01:54-995372c-667c53e/android-amd64-emu](https://build.golang.org/log/d096a4b6e818ee47b7cc4e745216742139df88be)
[2022-11-03T16:00:30-995372c-b07e845/android-386-emu](https://build.golang.org/log/c32fe103fabfade538eb08fb87ee9c483f391290)
[2022-11-03T16:00:30-995372c-b07e845/android-amd64-emu](https://build.golang.org/log/ebe3e1b080f1c6b3b3858ac3d33926bd315085e1)
[2022-11-03T15:53:45-995372c-932330f/android-386-emu](https://build.golang.org/log/bc52afd4f64a31d74f014f8668ffe63f578638db)
[2022-11-03T15:53:45-995372c-932330f/android-amd64-emu](https://build.golang.org/log/7ee32e33579812f8029c89a82eef4500b40c2e2d)
[2022-11-03T15:34:01-995372c-ebb71ad/android-386-emu](https://build.golang.org/log/31c5f8a95458186d64aa815cc0b940bc70f166aa)
[2022-11-03T15:34:01-995372c-ebb71ad/android-amd64-emu](https://build.golang.org/log/2d167961b204c3c12a4d6a74b348e480e0cbbd70)
[2022-11-03T15:18:40-995372c-a367981/android-386-emu](https://build.golang.org/log/8932b14d65b7957cb5430f3c165214f535f01616)
[2022-11-03T15:18:40-995372c-a367981/android-amd64-emu](https://build.golang.org/log/92adcc4b271ae8b897d46a803c3bf39563a7601e)
[2022-11-03T14:38:29-995372c-56ad133/android-386-emu](https://build.golang.org/log/459e5092715a37f57fcf07edb0fceef17d7d4f75)
[2022-11-03T14:38:29-995372c-56ad133/android-amd64-emu](https://build.golang.org/log/26114b9a9a1b0c77c6827e68b5c8828f1e63301f)
[2022-11-03T12:16:35-995372c-2af48cb/android-386-emu](https://build.golang.org/log/e5cda3cfbb9a2ed8df7c9a6aa75d496975c58d4e)
[2022-11-03T12:16:35-995372c-2af48cb/android-amd64-emu](https://build.golang.org/log/1f1114de96869e9e14719b083f96a0c8610b14e6)
[2022-11-02T21:06:46-995372c-fb4f7fd/android-386-emu](https://build.golang.org/log/829dc4f6790d8d3bb3a16ddb5efef74216118368)
[2022-11-02T21:06:46-995372c-fb4f7fd/android-amd64-emu](https://build.golang.org/log/db172e1ec52ac98f0b2783fc0e0898bb124b60f2)
[2022-11-02T20:14:56-995372c-a5b4283/android-386-emu](https://build.golang.org/log/6deaf8d0f5166c5a8456d2fbfbefe882fe55aac7)
[2022-11-02T20:14:56-995372c-a5b4283/android-amd64-emu](https://build.golang.org/log/3d303f597bfcfd083380b971ce32a92875896680)
[2022-11-02T19:08:10-995372c-ca8b319/android-386-emu](https://build.golang.org/log/16d539c70715efb2ff400fea8bccb1c6d1707457)
[2022-11-02T19:08:10-995372c-ca8b319/android-amd64-emu](https://build.golang.org/log/81955b79d8b247ed17ec2a7c69cff1782d0ab050)
[2022-11-02T18:43:27-995372c-be7068f/android-386-emu](https://build.golang.org/log/3039baf8ddf88efd9bdb500d47e71b1ef7711d9f)
[2022-11-02T18:43:27-995372c-be7068f/android-amd64-emu](https://build.golang.org/log/de68a74933759d91ff54b465ef4c22368adf259d)
[2022-11-02T18:19:04-995372c-07a70bc/android-386-emu](https://build.golang.org/log/583e5bfe894b83ef1e05d0d7ff73429d97fae9cf)
[2022-11-02T18:19:04-995372c-07a70bc/android-amd64-emu](https://build.golang.org/log/f77fac05f010bd158e2f10920074347c8587483d)
[2022-11-02T18:15:21-995372c-581a822/android-386-emu](https://build.golang.org/log/a2cad7c12218a311aab8c5ca3a7d72336f7917ad)
[2022-11-02T18:15:21-995372c-581a822/android-amd64-emu](https://build.golang.org/log/e3302226f44e6f5512123d77ac84530f4e7ae230)
[2022-11-02T17:01:39-995372c-03f6d81/android-386-emu](https://build.golang.org/log/656ebeac34fb8515b8af7b2fb88b402a559dc1f7)
[2022-11-02T17:01:39-995372c-03f6d81/android-amd64-emu](https://build.golang.org/log/811d65b5175b4d0909902f4c484cf4fcf0123333)
[2022-11-02T14:43:52-995372c-3ba3b48/android-386-emu](https://build.golang.org/log/ece98e823264b098cf2c59fefd6ca933818d676d)
[2022-11-02T14:43:52-995372c-3ba3b48/android-amd64-emu](https://build.golang.org/log/01f6f02683466081b6c3f9e049749283ccb9c902)
</details>
(236 matching logs)
(attn @golang/vulndb) | 1.0 | x/vuln: tests consistently failing on Android builders due to missing "compile" tool starting 2022-11-02 - ```
--- FAIL: TestInits (0.20s)
callstacks_test.go:191: err: exit status 2: stderr: go: no such tool "compile"
FAIL
exitcode=1
FAIL golang.org/x/vuln/internal/govulncheck 46.719s
ok golang.org/x/vuln/internal/semver 46.828s
ok golang.org/x/vuln/internal/web 47.031s
ok golang.org/x/vuln/osv 46.925s
--- FAIL: TestSlicing (0.04s)
slicing_test.go:96: err: exit status 2: stderr: go: no such tool "compile"
--- FAIL: TestImports (0.95s)
source_test.go:117: err: exit status 2: stderr: go: no such tool "compile"
--- FAIL: TestRequires (0.07s)
source_test.go:259: err: exit status 2: stderr: go: no such tool "compile"
--- FAIL: TestCalls (0.06s)
source_test.go:496: err: exit status 2: stderr: go: no such tool "compile"
--- FAIL: TestFiltering (0.06s)
source_test.go:595: err: exit status 2: stderr: go: no such tool "compile"
--- FAIL: TestAllSymbolsVulnerable (0.05s)
source_test.go:686: err: exit status 2: stderr: go: no such tool "compile"
--- FAIL: TestNoSyntheticNodes (0.04s)
source_test.go:752: err: exit status 2: stderr: go: no such tool "compile"
--- FAIL: TestRecursion (0.07s)
source_test.go:833: err: exit status 2: stderr: go: no such tool "compile"
--- FAIL: TestConvert (0.09s)
vulncheck_test.go:414: err: exit status 2: stderr: go: no such tool "compile"
FAIL
exitcode=1
FAIL golang.org/x/vuln/vulncheck 48.377s
```
`greplogs -l -e '\Aandroid.*(\n.*)*no such tool "compile"(.*\n)*FAIL\s+golang\.org/x/vuln' --since=2022-07-01 --details`
<details>
[2022-12-07T18:18:50-05fb725-7c7cd56/android-386-emu](https://build.golang.org/log/df3d5a2541dc4919003ec8f8100df5ddb6822650)
[2022-12-07T18:18:50-05fb725-7c7cd56/android-amd64-emu](https://build.golang.org/log/6b80f79e84d2362ccd6d843bf40c5db996b47862)
[2022-12-07T16:56:12-05fb725-e57e673/android-386-emu](https://build.golang.org/log/fe23c75bec338b45e5252e4b64388f273a52035b)
[2022-12-07T16:56:12-05fb725-e57e673/android-amd64-emu](https://build.golang.org/log/841cf73bfb5302054f70b9d886ac5f58ca877490)
[2022-12-07T16:49:08-05fb725-3ec5085/android-386-emu](https://build.golang.org/log/4a8dc91edc92ee584f4458c0784258a4dd995cef)
[2022-12-07T16:49:08-05fb725-3ec5085/android-amd64-emu](https://build.golang.org/log/d499acbebc4f843ee70b424f105205b7a299810d)
[2022-12-07T16:26:42-05fb725-f715d28/android-386-emu](https://build.golang.org/log/109069ae258e9ced451aa021384176f4fbf1f7e9)
[2022-12-07T16:26:42-05fb725-f715d28/android-amd64-emu](https://build.golang.org/log/0954970ac4c6c51924e7c24631146c4e07b842e3)
[2022-12-07T16:09:09-05fb725-7ed50cf/android-386-emu](https://build.golang.org/log/78c52487b1f82711a4ca38b60745f954c43ab5f1)
[2022-12-07T16:09:09-05fb725-7ed50cf/android-amd64-emu](https://build.golang.org/log/03ce4d1d4caf4603c420f2f8c4ee57c0b7313f2b)
[2022-12-07T14:20:49-05fb725-a4a86c7/android-386-emu](https://build.golang.org/log/50c95b71e82aa86a5cfe50de735b73ac17005b8e)
[2022-12-07T14:20:49-05fb725-a4a86c7/android-amd64-emu](https://build.golang.org/log/660a3c8c0f94b8165815dde702f496f1fc09f1a9)
[2022-12-07T03:45:50-05fb725-a398963/android-386-emu](https://build.golang.org/log/d7f426e7105822a0e1ec294770265e64933c08a9)
[2022-12-07T03:45:50-05fb725-a398963/android-amd64-emu](https://build.golang.org/log/c94d2371bbb4eaba27a29249d8b14fd61085db96)
[2022-12-07T00:51:44-05fb725-8cd931f/android-386-emu](https://build.golang.org/log/7607df4f33f1b29922006c495440c214cc0b1993)
[2022-12-07T00:51:44-05fb725-8cd931f/android-amd64-emu](https://build.golang.org/log/afebdc430d5984896dc37a538a522e34e2df9b78)
[2022-12-07T00:25:27-05fb725-10bb003/android-386-emu](https://build.golang.org/log/ed68456a838ed44c925c31d27e9773ca888c2bf2)
[2022-12-07T00:25:27-05fb725-10bb003/android-amd64-emu](https://build.golang.org/log/57a2783beaf7ab6586786cf53f4164de6deb88d3)
[2022-12-06T23:50:47-05fb725-7dc9fcb/android-386-emu](https://build.golang.org/log/bad6bf1d32481d461fcfe978477c46dfd84d0b69)
[2022-12-06T23:50:47-05fb725-7dc9fcb/android-amd64-emu](https://build.golang.org/log/ac919e077aaf92f970948686e719b687d1aebc67)
[2022-12-06T22:07:25-05fb725-e535d67/android-386-emu](https://build.golang.org/log/6625c5e418829a90ff42418800087e45a41ca610)
[2022-12-06T22:07:25-05fb725-e535d67/android-amd64-emu](https://build.golang.org/log/0f2250edd358e01bff6cacdd2fd075c287fcff57)
[2022-12-06T20:53:50-05fb725-89871dd/android-386-emu](https://build.golang.org/log/e2e3d2dfecbed667267f90e08a1b56b942058fe5)
[2022-12-06T20:53:50-05fb725-89871dd/android-amd64-emu](https://build.golang.org/log/e2e4726473bc2dde67c9c5389e6309f9c4f7ecb6)
[2022-12-06T20:19:47-05fb725-5167e5c/android-386-emu](https://build.golang.org/log/fab02b887e7de4daad26c88240779715a7520d38)
[2022-12-06T20:19:47-05fb725-5167e5c/android-amd64-emu](https://build.golang.org/log/e7faafd1b76281672895f1c2f11ee82aded68be3)
[2022-12-06T19:52:35-05fb725-03bf6f4/android-386-emu](https://build.golang.org/log/61179b3ae900489e1d6b23e0be3798f90464c9ee)
[2022-12-06T19:52:35-05fb725-03bf6f4/android-amd64-emu](https://build.golang.org/log/d638646a0e21b29c2139567af2fc30c5c8dfa22f)
[2022-12-06T18:32:51-05fb725-dfd13ce/android-386-emu](https://build.golang.org/log/2716f500526787d1c8cb6508aaaf0f3f4e66f9a4)
[2022-12-06T18:32:51-05fb725-dfd13ce/android-amd64-emu](https://build.golang.org/log/a59ac8de75daa20c9e8e7003a70446d145b60dcf)
[2022-12-06T18:11:17-05fb725-98da0fb/android-386-emu](https://build.golang.org/log/683c90b9c1fb301a24a125beefc457c40245a5f6)
[2022-12-06T18:11:17-05fb725-98da0fb/android-amd64-emu](https://build.golang.org/log/1ea97fb384febc4cb1be8d984e57e23b4e03bd24)
[2022-12-06T15:55:39-05fb725-fe67a21/android-386-emu](https://build.golang.org/log/61ba39efde488243ce672ae8cefe97b623515858)
[2022-12-06T15:55:39-05fb725-fe67a21/android-amd64-emu](https://build.golang.org/log/4ee32c27e0633841fc508f6392afe7efab9f866c)
[2022-12-06T05:12:12-05fb725-1eb0465/android-386-emu](https://build.golang.org/log/fcc31a797775dc0b4b1b27626017a2c4297baf5d)
[2022-12-06T05:12:12-05fb725-1eb0465/android-amd64-emu](https://build.golang.org/log/12d3415c3889aaf4b6fc1ba266b6d1a7502fd21a)
[2022-12-05T23:21:07-05fb725-9dde2de/android-386-emu](https://build.golang.org/log/6c79cb21c103377045d64db8221634cfd8a2f3e3)
[2022-12-05T23:21:07-05fb725-9dde2de/android-amd64-emu](https://build.golang.org/log/7e80fcc106e7a359ba621d8ea56abd1de2254bc7)
[2022-12-05T22:29:44-05fb725-0b323a3/android-386-emu](https://build.golang.org/log/29dfb72748ab8164328c43e0d7e568b8fe0094bb)
[2022-12-05T22:29:44-05fb725-0b323a3/android-amd64-emu](https://build.golang.org/log/d9804cc43389fd119cbe45b7e44cec88143b087b)
[2022-12-05T22:22:11-05fb725-9e05963/android-386-emu](https://build.golang.org/log/8a9fa3e0cc973c6ae150676d95a95b70f5e3fea9)
[2022-12-05T22:22:11-05fb725-9e05963/android-amd64-emu](https://build.golang.org/log/90510d6456366a7202c928a1d3870f125f4c9d8a)
[2022-12-05T22:01:50-05fb725-185e1a7/android-386-emu](https://build.golang.org/log/64fcd68d6481ee2e0d2ab64497a4696e3add4a9e)
[2022-12-05T22:01:50-05fb725-185e1a7/android-amd64-emu](https://build.golang.org/log/c2d8747efa0a56d487cbd8dac2a9bbd0237e4534)
[2022-12-05T20:45:49-05fb725-a5b10be/android-386-emu](https://build.golang.org/log/e94339fea0c9f71b1a6425f38101773681e03d52)
[2022-12-05T20:45:49-05fb725-a5b10be/android-amd64-emu](https://build.golang.org/log/d86b3daaa17276df1ede6751f4ef5d27795b6af3)
[2022-12-05T19:25:34-05fb725-b45cb0c/android-386-emu](https://build.golang.org/log/c71584294642cf8eac91ad8943d546475b1b80ce)
[2022-12-05T19:25:34-05fb725-b45cb0c/android-amd64-emu](https://build.golang.org/log/bda0b623f86636d2161f52b76b5b6220d7a90229)
[2022-12-05T18:57:04-05fb725-2986358/android-386-emu](https://build.golang.org/log/9eaa4e62d58fa4b76306f80adcc55d0fdd8cfb93)
[2022-12-05T18:57:04-05fb725-2986358/android-amd64-emu](https://build.golang.org/log/bdcae6a7b27500a6a0b84579899a533ea1c302e2)
[2022-12-05T16:41:48-05fb725-ad55b87/android-386-emu](https://build.golang.org/log/6a3bd0b4f43073d26dedbdcd3603fd5d87a183f5)
[2022-12-05T16:41:48-05fb725-ad55b87/android-amd64-emu](https://build.golang.org/log/62c228dca71a1c3ec549fd24f810fca3d21cca6d)
[2022-12-03T17:08:51-05fb725-3a7a528/android-386-emu](https://build.golang.org/log/48f6a7361afc246edc9ec4f9a89a10d7012c19f7)
[2022-12-03T17:08:51-05fb725-3a7a528/android-amd64-emu](https://build.golang.org/log/3a1667a09610baa0678ec9b9ae98f041721fcb1a)
[2022-12-02T23:40:37-05fb725-c0497d1/android-386-emu](https://build.golang.org/log/93c606f8a157d4581e03e1dc7f6d3fe12e3fccf7)
[2022-12-02T23:40:37-05fb725-c0497d1/android-amd64-emu](https://build.golang.org/log/88520d9f612e5862be367ccaec10f253abbf1dbd)
[2022-12-02T22:24:00-05fb725-7ab3615/android-386-emu](https://build.golang.org/log/785db740749be82de36d2aae04a560c606e97ebc)
[2022-12-02T22:24:00-05fb725-7ab3615/android-amd64-emu](https://build.golang.org/log/2d6bffbe6cc95abe9e495ccf7aae6ff52c622f8c)
[2022-12-02T21:15:10-05fb725-45f5ef4/android-386-emu](https://build.golang.org/log/34e30991324b04c4b467e3cc72af920c04d1297a)
[2022-12-02T21:15:10-05fb725-45f5ef4/android-amd64-emu](https://build.golang.org/log/c1bb9b05722edade39c19d039ebe552ab35c81c2)
[2022-11-22T16:07:28-fac3670-9160e15/android-386-emu](https://build.golang.org/log/44c0c88823366b1a9ce0c6c760b98eb25af1ab83)
[2022-11-22T16:07:28-fac3670-9160e15/android-amd64-emu](https://build.golang.org/log/7756f10d2bc2d0d1dd778ae65f2c184150553a5b)
[2022-11-22T15:58:43-fac3670-5c9a506/android-386-emu](https://build.golang.org/log/789f7a142046593e4e74ac8cdc6291977f67386a)
[2022-11-22T15:58:43-fac3670-5c9a506/android-amd64-emu](https://build.golang.org/log/22cf185e9da7ab58a50e6fe23a0cbb7b54725404)
[2022-11-22T14:09:24-fac3670-9efc5a5/android-386-emu](https://build.golang.org/log/b1af713617d86ea28743b5a489c3f963fe2f677c)
[2022-11-22T14:09:24-fac3670-9efc5a5/android-amd64-emu](https://build.golang.org/log/634122570bfa647c598dd188c06f4d55267d1d59)
[2022-11-22T03:11:31-fac3670-6a72514/android-386-emu](https://build.golang.org/log/d396c1d36a9e04739b733c3de5708490e1881035)
[2022-11-22T03:11:31-fac3670-6a72514/android-amd64-emu](https://build.golang.org/log/b5861dfcf5a87b22134b5389f9750bd776f0905f)
[2022-11-22T02:52:19-fac3670-f41fdc1/android-386-emu](https://build.golang.org/log/aca50ba6c17ee89da7661a813f31fd8a6d536969)
[2022-11-22T02:52:19-fac3670-f41fdc1/android-amd64-emu](https://build.golang.org/log/6f07f896b5a0f115d656de5e1d49fb3516d9dd97)
[2022-11-22T02:27:05-fac3670-14a4138/android-386-emu](https://build.golang.org/log/e396a1806338d61acb49af8d332f59c3433b24aa)
[2022-11-22T02:27:05-fac3670-14a4138/android-amd64-emu](https://build.golang.org/log/95a7a39b2fba65d81cd245193a57da74ef8665f7)
[2022-11-22T01:42:49-fac3670-1521199/android-386-emu](https://build.golang.org/log/8c1a5a39a86958f521dfde14657d383df4fae490)
[2022-11-22T01:42:49-fac3670-1521199/android-amd64-emu](https://build.golang.org/log/78280b6974ed0c1929510fe4d2919d77bb6f2c1f)
[2022-11-21T22:49:25-fac3670-1c9eba1/android-386-emu](https://build.golang.org/log/bce99df3eabf0d10f21fcad73842bfb63780952e)
[2022-11-21T22:49:25-fac3670-1c9eba1/android-amd64-emu](https://build.golang.org/log/3ed25d387749e344e9aef936fbe4274945e19477)
[2022-11-21T22:43:41-fac3670-7656cba/android-386-emu](https://build.golang.org/log/089bdfcad3ce2fa872098d187419786d046f8ac9)
[2022-11-21T22:43:41-fac3670-7656cba/android-amd64-emu](https://build.golang.org/log/75cff201e73093c88880299f03a9016ce9f6dade)
[2022-11-21T22:21:04-fac3670-d58f2e7/android-386-emu](https://build.golang.org/log/14af01de13a5bb5a349b4359475107359073452e)
[2022-11-21T22:21:04-fac3670-d58f2e7/android-amd64-emu](https://build.golang.org/log/76164bbc0fdcdada8c88d35b99070dcde2e97c41)
[2022-11-21T22:16:06-fac3670-995c0f3/android-386-emu](https://build.golang.org/log/962b1aee2d83b7d8ea4722e08c526305f16332e7)
[2022-11-21T22:16:06-fac3670-995c0f3/android-amd64-emu](https://build.golang.org/log/c433d3521a84d36effbb4da85f6f0fb893900611)
[2022-11-21T21:55:53-fac3670-089dcd7/android-386-emu](https://build.golang.org/log/8b4b99875bbce770d405a019629bdffa915ad501)
[2022-11-21T21:55:53-fac3670-089dcd7/android-amd64-emu](https://build.golang.org/log/aecd64f91c7a8498a6f658d6a638bfcd47f05f07)
[2022-11-21T21:14:38-fac3670-85a2c19/android-386-emu](https://build.golang.org/log/8a63f66aae06a66e2f1ca462247666ccd1df7a90)
[2022-11-21T21:14:38-fac3670-85a2c19/android-amd64-emu](https://build.golang.org/log/0a3c74f2fdeac9489fac098f0ee3767f979c2d48)
[2022-11-16T20:18:50-50a0e29-e6eaf39/android-386-emu](https://build.golang.org/log/9ec5e2dca09ca9e0d50826a64ecb457bc47a6a4a)
[2022-11-16T20:18:50-50a0e29-e6eaf39/android-amd64-emu](https://build.golang.org/log/e0896223e854a31d9d85a284319b38f6c1e43997)
[2022-11-16T19:00:20-50a0e29-cd9d26f/android-386-emu](https://build.golang.org/log/895587cef56226ad44de16491cbf43b114043f4a)
[2022-11-16T19:00:20-50a0e29-cd9d26f/android-amd64-emu](https://build.golang.org/log/b5ae3e2de7b0ab7f9b16663e8c4cef7be6838873)
[2022-11-16T17:22:19-50a0e29-8c17505/android-386-emu](https://build.golang.org/log/e2978a9b033e6608828eac81e122edc984dcd5eb)
[2022-11-16T17:22:19-50a0e29-8c17505/android-amd64-emu](https://build.golang.org/log/68dac71f360ac16491a3c48f8232c505c03c2dd5)
[2022-11-16T16:42:18-50a0e29-0266671/android-386-emu](https://build.golang.org/log/3dd090156d0a3dceb6e8de599ba452581f100aa4)
[2022-11-16T16:42:18-50a0e29-0266671/android-amd64-emu](https://build.golang.org/log/39e87a7004c9b6b38841c3b9c0d0830c5791db91)
[2022-11-16T16:25:58-50a0e29-38218f3/android-386-emu](https://build.golang.org/log/b9ce1e0681b9efad08e0ffeda34d8ecd51a510d6)
[2022-11-16T16:25:58-50a0e29-38218f3/android-amd64-emu](https://build.golang.org/log/191f3c9a5631da6275f3de69848e4a9cf861e6ff)
[2022-11-16T15:10:02-50a0e29-70f585f/android-386-emu](https://build.golang.org/log/2ea7e504358569e590c71647c576189145137219)
[2022-11-16T15:10:02-50a0e29-70f585f/android-amd64-emu](https://build.golang.org/log/da136101f911b75dc6faa6c8ff5dd69b03a1053e)
[2022-11-16T14:42:36-50a0e29-978ce7e/android-386-emu](https://build.golang.org/log/3897060fb992cfb202c8495ea745598afdac5561)
[2022-11-16T14:42:36-50a0e29-978ce7e/android-amd64-emu](https://build.golang.org/log/d385c9fc65723cbc508cb4f1808473f01b50aeea)
[2022-11-16T14:38:38-50a0e29-7c8c209/android-386-emu](https://build.golang.org/log/ece8e174fac3a1ac070c0f0e428f0a3188fffff6)
[2022-11-16T14:38:38-50a0e29-7c8c209/android-amd64-emu](https://build.golang.org/log/16d3ca2e74c67e74d0fda288fa7913a261576f6d)
[2022-11-16T13:26:16-50a0e29-5947a07/android-386-emu](https://build.golang.org/log/b096640e57e76a6dd69a679c02eda4cacdd2199f)
[2022-11-16T13:26:16-50a0e29-5947a07/android-amd64-emu](https://build.golang.org/log/bd00ee89e6430270a4042f153504bd01ab6160bb)
[2022-11-16T04:04:52-50a0e29-b1678e5/android-386-emu](https://build.golang.org/log/6f35c68bd01ba276446a1b13711554ba1007535e)
[2022-11-16T04:04:52-50a0e29-b1678e5/android-amd64-emu](https://build.golang.org/log/d1c77534c6773346a2404a269dd8eb170c7612b9)
[2022-11-16T02:02:26-50a0e29-cb5534c/android-386-emu](https://build.golang.org/log/9e77a365bcb090fe469a43c9d3dff8be09dec3e7)
[2022-11-16T02:02:26-50a0e29-cb5534c/android-amd64-emu](https://build.golang.org/log/91d9387b07cee23faf625eccc156596615e56f02)
[2022-11-15T23:48:34-50a0e29-c085c6c/android-386-emu](https://build.golang.org/log/44e7d5f57e6157fa6484cdd3d3ad1f7c4a4fcf63)
[2022-11-15T23:48:34-50a0e29-c085c6c/android-amd64-emu](https://build.golang.org/log/367820e15f0f80edf4efea6e10df98dddc422115)
[2022-11-15T22:52:03-50a0e29-8477562/android-386-emu](https://build.golang.org/log/170da895bb9a904121f507ca33835dbc172d020a)
[2022-11-15T22:52:03-50a0e29-8477562/android-amd64-emu](https://build.golang.org/log/ff8d14c0bbe85fbb26bc434aa84bc297bcb24937)
[2022-11-11T16:04:21-3af8368-fcd14bd/android-386-emu](https://build.golang.org/log/99dffdc735422a5e73d61612138a41474f111e6e)
[2022-11-11T16:04:21-3af8368-fcd14bd/android-amd64-emu](https://build.golang.org/log/8e6610e283d426c1a56075c674b90175f191c2c2)
[2022-11-11T14:51:14-3af8368-fffda6b/android-386-emu](https://build.golang.org/log/cbe581e45312d8f5738201bd948313dd3e425457)
[2022-11-11T14:51:14-3af8368-fffda6b/android-amd64-emu](https://build.golang.org/log/3fbd0ae2deaa8c21f92092691597d7f815a207af)
[2022-11-11T14:48:29-3af8368-73f987c/android-386-emu](https://build.golang.org/log/a59e56a9f476461375ddc7b850248c284b7ca934)
[2022-11-11T14:48:29-3af8368-73f987c/android-amd64-emu](https://build.golang.org/log/4c0ae6927ba3d49d9e43f68a1a013476717988db)
[2022-11-11T04:31:34-3af8368-185766d/android-386-emu](https://build.golang.org/log/9c53d786e08ba9288558fc4ca22b161be79ab5e0)
[2022-11-11T04:31:34-3af8368-185766d/android-amd64-emu](https://build.golang.org/log/6d9da936c2613f0cd7bdfbfa82a5ab02e9dd496c)
[2022-11-11T01:42:03-3af8368-d62f8d5/android-386-emu](https://build.golang.org/log/c4b92731968895e538c863f15c9bc987ce154fa7)
[2022-11-11T01:42:03-3af8368-d62f8d5/android-amd64-emu](https://build.golang.org/log/ccbbc9133304e8c777d34703904b5b956a5e7546)
[2022-11-11T01:35:11-3af8368-ffc4496/android-386-emu](https://build.golang.org/log/245aefd3fdc1b126f1f39c09ec17e083e7b7fa7a)
[2022-11-11T01:35:11-3af8368-ffc4496/android-amd64-emu](https://build.golang.org/log/915b1ac32e1d108071bb5d099e2ed99f438326d1)
[2022-11-11T01:29:15-3af8368-4d37f96/android-386-emu](https://build.golang.org/log/9b9d0f106fe2f07584aba663a00b070690aed131)
[2022-11-11T01:29:15-3af8368-4d37f96/android-amd64-emu](https://build.golang.org/log/e9f785c5f0f1a32d6965fe7af0723d10ec5cd984)
[2022-11-10T23:11:59-3af8368-1b03568/android-386-emu](https://build.golang.org/log/78f2f0b344547d58dc1a58afde87c60ff5d28484)
[2022-11-10T23:11:59-3af8368-1b03568/android-amd64-emu](https://build.golang.org/log/8c594aeb5c4b5c8618dcb944884042a004a080ee)
[2022-11-10T22:41:06-3af8368-5497300/android-386-emu](https://build.golang.org/log/cc269ed2894d1715c12da2afeee93ff897b5cad5)
[2022-11-10T22:41:06-3af8368-5497300/android-amd64-emu](https://build.golang.org/log/b62ab7088100f0833c13238c49e31384597069d2)
[2022-11-10T21:11:02-3af8368-79950a4/android-386-emu](https://build.golang.org/log/e28f0e1bb16d07ab5924991a5e9b2783416c2eaa)
[2022-11-10T21:11:02-3af8368-79950a4/android-amd64-emu](https://build.golang.org/log/c571a63c3fdcc581f50e1d90b3a594ad97168c0e)
[2022-11-10T20:44:45-3af8368-14018c8/android-386-emu](https://build.golang.org/log/6796c686249c5e3d2152fea5eeb097091eb1eade)
[2022-11-10T20:44:45-3af8368-14018c8/android-amd64-emu](https://build.golang.org/log/5b0c9eace199346b870705ad6383a6daac54f268)
[2022-11-10T20:38:57-3af8368-d96eb82/android-386-emu](https://build.golang.org/log/fcf0378b19347e527bc43109e686731fa62fbcc1)
[2022-11-10T20:38:57-3af8368-d96eb82/android-amd64-emu](https://build.golang.org/log/8cf10139a2e7bb2b626b4d4b7c21e748e7e1405f)
[2022-11-10T20:24:57-3af8368-f57ebed/android-386-emu](https://build.golang.org/log/076c2ab4d6c7bb0f3b193ebd91efa497de5f0d4e)
[2022-11-10T20:24:57-3af8368-f57ebed/android-amd64-emu](https://build.golang.org/log/e32240c73c58465983f8c4b5e52bcdcac162a7aa)
[2022-11-09T20:13:45-fc17c87-d02fceb/android-386-emu](https://build.golang.org/log/f9d329124eecb47e6d0ef5d82696ff8f956c81fb)
[2022-11-09T20:13:45-fc17c87-d02fceb/android-amd64-emu](https://build.golang.org/log/0aec9d3abf17a3350aa00761319729e5adc2899a)
[2022-11-09T19:40:02-1943a78-d02fceb/android-386-emu](https://build.golang.org/log/394ffe29262fb8ebe44e851485440f67865a224d)
[2022-11-09T19:40:02-1943a78-d02fceb/android-amd64-emu](https://build.golang.org/log/702ce791710c1512453be97be3ff52603cafceb1)
[2022-11-09T18:21:12-1943a78-342751a/android-386-emu](https://build.golang.org/log/a7f75d269d162aca39060cfbe54d928c9b056c0e)
[2022-11-09T18:21:12-1943a78-342751a/android-amd64-emu](https://build.golang.org/log/b1bfd4ec56cb92edc7e35d61728f9a4cb0a3740a)
[2022-11-09T18:07:37-1943a78-4f13067/android-386-emu](https://build.golang.org/log/5c017ba08bb9a5e3e83e7db186b5e1a8e48ee56f)
[2022-11-09T18:07:37-1943a78-4f13067/android-amd64-emu](https://build.golang.org/log/43175615bad629907c6f57407cd50fb8ec65d517)
[2022-11-09T18:05:45-1943a78-2f4d5c3/android-386-emu](https://build.golang.org/log/c8ade0a530577d98444161ec1e756cc3362a92ad)
[2022-11-09T18:05:45-1943a78-2f4d5c3/android-amd64-emu](https://build.golang.org/log/1d4c43d6abecbf90633a5eaa2934bcbc24df627f)
[2022-11-09T17:41:34-6a111ce-2f4d5c3/android-386-emu](https://build.golang.org/log/1831ba1a6f3dc8b794e9dfbffcfc06a359ee31e2)
[2022-11-09T17:41:34-6a111ce-2f4d5c3/android-amd64-emu](https://build.golang.org/log/c2d687d8941f0e60611b508266e9191df50a64cd)
[2022-11-09T17:33:07-6a111ce-7a92c4f/android-386-emu](https://build.golang.org/log/9d03e3b23205f031dd8119c74accdbe4b87ac2f8)
[2022-11-09T17:33:07-6a111ce-7a92c4f/android-amd64-emu](https://build.golang.org/log/c27d69fd3cc62bb13ff5be1f89bd6418003baf88)
[2022-11-09T16:52:00-6a111ce-9ff2a66/android-386-emu](https://build.golang.org/log/214d2cd818f9c45a5511ab1cbebf026e96009922)
[2022-11-09T16:52:00-6a111ce-9ff2a66/android-amd64-emu](https://build.golang.org/log/9d2ca9b361b6ff66e6cb9c2332067ee482a40113)
[2022-11-09T14:47:58-55c64d8-9ff2a66/android-386-emu](https://build.golang.org/log/249dce179fffa1048027eb7b9251e33b01040b07)
[2022-11-09T14:47:58-55c64d8-9ff2a66/android-amd64-emu](https://build.golang.org/log/6cf07fd32bc75cbc463cb4752537834e51d84b63)
[2022-11-09T14:05:53-55c64d8-821e310/android-386-emu](https://build.golang.org/log/449c91239072bc75fbf732bc7f8a32cae326f66b)
[2022-11-09T14:05:53-55c64d8-821e310/android-amd64-emu](https://build.golang.org/log/0891064a60c66d0759612b4e40d3fc0538afa6b7)
[2022-11-09T06:30:59-55c64d8-3a41094/android-386-emu](https://build.golang.org/log/c134c6ab25c8613bf473a2ecebef850631ecaabc)
[2022-11-09T06:30:59-55c64d8-3a41094/android-amd64-emu](https://build.golang.org/log/cc67b6a1292d49d8b0ece7371f0b0b94fcfa8b58)
[2022-11-09T06:10:55-55c64d8-268f462/android-386-emu](https://build.golang.org/log/d44bd6a714e706136eab1da7a9866fcdecfc34b2)
[2022-11-09T06:10:55-55c64d8-268f462/android-amd64-emu](https://build.golang.org/log/a8ac1837afe71ff55585eb15a4c2896f862e21b6)
[2022-11-09T04:03:15-55c64d8-6b45863/android-386-emu](https://build.golang.org/log/9f32aed5090bcf35c642c8a90de240ce53352b90)
[2022-11-09T04:03:15-55c64d8-6b45863/android-amd64-emu](https://build.golang.org/log/0fe4c1a77ae8533f002bf47bd1dd029bdf2ba36c)
[2022-11-09T03:01:33-55c64d8-27c3814/android-386-emu](https://build.golang.org/log/824eab70eeaf080ddf89f77b9dd138d081a31928)
[2022-11-09T03:01:33-55c64d8-27c3814/android-amd64-emu](https://build.golang.org/log/67330d8f0fbf90b80cb517240443c248f8cc6487)
[2022-11-08T23:11:32-55c64d8-fe4e59e/android-386-emu](https://build.golang.org/log/8ab4dfb77213e148942718f7ebcf4ff218629709)
[2022-11-08T23:11:32-55c64d8-fe4e59e/android-amd64-emu](https://build.golang.org/log/829455b6b3c5ed7a911382da457434efa67275b5)
[2022-11-08T22:14:56-55c64d8-896faf3/android-386-emu](https://build.golang.org/log/e915f2e6f3e37aef9b06605fe50fa1f51e7280e1)
[2022-11-08T22:14:56-55c64d8-896faf3/android-amd64-emu](https://build.golang.org/log/3bca29eaca68b265f1685b356f0043bff1b72b6b)
[2022-11-08T21:50:06-55c64d8-8befe0e/android-386-emu](https://build.golang.org/log/018140f94b37af65083b1b841764fb2f60b9d559)
[2022-11-08T21:50:06-55c64d8-8befe0e/android-amd64-emu](https://build.golang.org/log/519976938170aa82948f2d170d265fdc0e5b73ee)
[2022-11-08T21:31:58-55c64d8-2df6c1a/android-386-emu](https://build.golang.org/log/7a3bfb66ed704395978f71993027bd86aa2799ca)
[2022-11-08T21:31:58-55c64d8-2df6c1a/android-amd64-emu](https://build.golang.org/log/b88574f97ddc96a9c21c703e170f1683d9f92cb2)
[2022-11-08T21:26:09-55c64d8-9944ba7/android-386-emu](https://build.golang.org/log/3208f3a369876c325963ffa171813be9a02d2a7f)
[2022-11-08T21:26:09-55c64d8-9944ba7/android-amd64-emu](https://build.golang.org/log/3bcd693995f1aadedf2b410071e979a85ce92b7f)
[2022-11-08T20:59:42-55c64d8-a7538d7/android-386-emu](https://build.golang.org/log/3bd869d0767ccfccdb63e8bce47769402cbdca02)
[2022-11-08T20:59:42-55c64d8-a7538d7/android-amd64-emu](https://build.golang.org/log/783972bc48b471f2459713b32762f38af874b64b)
[2022-11-08T14:15:17-4f561ca-be3184c/android-386-emu](https://build.golang.org/log/d229c7e54dd407024824796cda3cce03404a9149)
[2022-11-08T14:15:17-4f561ca-be3184c/android-amd64-emu](https://build.golang.org/log/f633c70c5dfff5a51506d99a26106e5268289011)
[2022-11-08T13:51:16-4f561ca-5b42f89/android-386-emu](https://build.golang.org/log/b1b59ec7f8c72b09675086d329bcb74a1ef8e5ca)
[2022-11-08T13:51:16-4f561ca-5b42f89/android-amd64-emu](https://build.golang.org/log/ffb1421423a3cf5d3d5476acf1250ace3013ac22)
[2022-11-08T08:14:37-4f561ca-0b7aa9f/android-386-emu](https://build.golang.org/log/3757bab47b1ec83aee8bf03752c1ebc5e86b0e70)
[2022-11-08T08:14:37-4f561ca-0b7aa9f/android-amd64-emu](https://build.golang.org/log/23b856b0786671971187b76df9574de5aaecdc5c)
[2022-11-08T05:24:43-4f561ca-9860faa/android-386-emu](https://build.golang.org/log/cc5b9757f586a0467e691309d2ca96855e4c3028)
[2022-11-08T05:24:43-4f561ca-9860faa/android-amd64-emu](https://build.golang.org/log/38c0402cf1509e03c3c9f725100257c77bdf222a)
[2022-11-03T21:13:39-6f7a8cb-69abfab/android-386-emu](https://build.golang.org/log/9d5e0457773186b0d275e86ca91f6c6dde3868f9)
[2022-11-03T21:13:39-6f7a8cb-69abfab/android-amd64-emu](https://build.golang.org/log/b5186566b5ebc8e0490a0b064faad9748bdd4a5d)
[2022-11-03T20:35:31-6f7a8cb-aa6240a/android-386-emu](https://build.golang.org/log/f6899acf83fea70aed92671ff0a53f0fb526eaf0)
[2022-11-03T20:35:31-6f7a8cb-aa6240a/android-amd64-emu](https://build.golang.org/log/0fab81d0e0813f8307eaa010d8faf8f384039870)
[2022-11-03T20:32:06-6f7a8cb-48ff5c1/android-386-emu](https://build.golang.org/log/884a57f60a04bd710ef2a76bd01dba30d2504b67)
[2022-11-03T20:32:06-6f7a8cb-48ff5c1/android-amd64-emu](https://build.golang.org/log/c49e35c7493785db6b9e7a4d0b34ea366d15cecc)
[2022-11-03T19:59:19-6f7a8cb-d031e9e/android-386-emu](https://build.golang.org/log/18d8905eb07bea643536d4ca00e7493f3945b9cb)
[2022-11-03T19:59:19-6f7a8cb-d031e9e/android-amd64-emu](https://build.golang.org/log/c0de714b9cbfc50895df86fe99cf3a5eed8f40ef)
[2022-11-03T19:40:36-6f7a8cb-c065bc7/android-386-emu](https://build.golang.org/log/5c92f9d577e9f66e3e2d9d11a2a710bc3ddbfe84)
[2022-11-03T19:40:36-6f7a8cb-c065bc7/android-amd64-emu](https://build.golang.org/log/1edb20a8d67f536ed401700f0c807dc6c0e5c583)
[2022-11-03T19:34:40-6f7a8cb-3511c82/android-386-emu](https://build.golang.org/log/f115e2a15d3115aa02dc27299e8e23eb597744fc)
[2022-11-03T19:34:40-6f7a8cb-3511c82/android-amd64-emu](https://build.golang.org/log/1448b5a85f06c3dbeee548a4f7aa02e521b4eb92)
[2022-11-03T18:33:42-6f7a8cb-44cabb8/android-386-emu](https://build.golang.org/log/86c4761a2b8a1e41b811afe1031e1ae6b0907ac3)
[2022-11-03T18:33:42-6f7a8cb-44cabb8/android-amd64-emu](https://build.golang.org/log/277278aa27a63ecc6f40a84904aaa78b839415b2)
[2022-11-03T18:31:08-6f7a8cb-0b76e32/android-386-emu](https://build.golang.org/log/fdf9afba8cb99ccc5f25590ec549613ff130e113)
[2022-11-03T18:31:08-6f7a8cb-0b76e32/android-amd64-emu](https://build.golang.org/log/63f86036dc45ab0f4571642b365abb61e141e45a)
[2022-11-03T17:41:32-f9bfb22-0b76e32/android-386-emu](https://build.golang.org/log/7e3c5ea5def77437d2857f4687d65deb9887a52c)
[2022-11-03T17:41:32-f9bfb22-0b76e32/android-amd64-emu](https://build.golang.org/log/2a7da06f2334d75992f0d638ee22a91056ea6ea5)
[2022-11-03T17:08:32-f9bfb22-667c53e/android-386-emu](https://build.golang.org/log/e8ebb71072eebfe5ed318ee9ca86f77caaf45df3)
[2022-11-03T17:08:32-f9bfb22-667c53e/android-amd64-emu](https://build.golang.org/log/8a8f03d568dea3748594190b79a9c0972785dd28)
[2022-11-03T17:01:54-995372c-667c53e/android-386-emu](https://build.golang.org/log/691b6bab3335a52afe41cb1d994d064ac09afb00)
[2022-11-03T17:01:54-995372c-667c53e/android-amd64-emu](https://build.golang.org/log/d096a4b6e818ee47b7cc4e745216742139df88be)
[2022-11-03T16:00:30-995372c-b07e845/android-386-emu](https://build.golang.org/log/c32fe103fabfade538eb08fb87ee9c483f391290)
[2022-11-03T16:00:30-995372c-b07e845/android-amd64-emu](https://build.golang.org/log/ebe3e1b080f1c6b3b3858ac3d33926bd315085e1)
[2022-11-03T15:53:45-995372c-932330f/android-386-emu](https://build.golang.org/log/bc52afd4f64a31d74f014f8668ffe63f578638db)
[2022-11-03T15:53:45-995372c-932330f/android-amd64-emu](https://build.golang.org/log/7ee32e33579812f8029c89a82eef4500b40c2e2d)
[2022-11-03T15:34:01-995372c-ebb71ad/android-386-emu](https://build.golang.org/log/31c5f8a95458186d64aa815cc0b940bc70f166aa)
[2022-11-03T15:34:01-995372c-ebb71ad/android-amd64-emu](https://build.golang.org/log/2d167961b204c3c12a4d6a74b348e480e0cbbd70)
[2022-11-03T15:18:40-995372c-a367981/android-386-emu](https://build.golang.org/log/8932b14d65b7957cb5430f3c165214f535f01616)
[2022-11-03T15:18:40-995372c-a367981/android-amd64-emu](https://build.golang.org/log/92adcc4b271ae8b897d46a803c3bf39563a7601e)
[2022-11-03T14:38:29-995372c-56ad133/android-386-emu](https://build.golang.org/log/459e5092715a37f57fcf07edb0fceef17d7d4f75)
[2022-11-03T14:38:29-995372c-56ad133/android-amd64-emu](https://build.golang.org/log/26114b9a9a1b0c77c6827e68b5c8828f1e63301f)
[2022-11-03T12:16:35-995372c-2af48cb/android-386-emu](https://build.golang.org/log/e5cda3cfbb9a2ed8df7c9a6aa75d496975c58d4e)
[2022-11-03T12:16:35-995372c-2af48cb/android-amd64-emu](https://build.golang.org/log/1f1114de96869e9e14719b083f96a0c8610b14e6)
[2022-11-02T21:06:46-995372c-fb4f7fd/android-386-emu](https://build.golang.org/log/829dc4f6790d8d3bb3a16ddb5efef74216118368)
[2022-11-02T21:06:46-995372c-fb4f7fd/android-amd64-emu](https://build.golang.org/log/db172e1ec52ac98f0b2783fc0e0898bb124b60f2)
[2022-11-02T20:14:56-995372c-a5b4283/android-386-emu](https://build.golang.org/log/6deaf8d0f5166c5a8456d2fbfbefe882fe55aac7)
[2022-11-02T20:14:56-995372c-a5b4283/android-amd64-emu](https://build.golang.org/log/3d303f597bfcfd083380b971ce32a92875896680)
[2022-11-02T19:08:10-995372c-ca8b319/android-386-emu](https://build.golang.org/log/16d539c70715efb2ff400fea8bccb1c6d1707457)
[2022-11-02T19:08:10-995372c-ca8b319/android-amd64-emu](https://build.golang.org/log/81955b79d8b247ed17ec2a7c69cff1782d0ab050)
[2022-11-02T18:43:27-995372c-be7068f/android-386-emu](https://build.golang.org/log/3039baf8ddf88efd9bdb500d47e71b1ef7711d9f)
[2022-11-02T18:43:27-995372c-be7068f/android-amd64-emu](https://build.golang.org/log/de68a74933759d91ff54b465ef4c22368adf259d)
[2022-11-02T18:19:04-995372c-07a70bc/android-386-emu](https://build.golang.org/log/583e5bfe894b83ef1e05d0d7ff73429d97fae9cf)
[2022-11-02T18:19:04-995372c-07a70bc/android-amd64-emu](https://build.golang.org/log/f77fac05f010bd158e2f10920074347c8587483d)
[2022-11-02T18:15:21-995372c-581a822/android-386-emu](https://build.golang.org/log/a2cad7c12218a311aab8c5ca3a7d72336f7917ad)
[2022-11-02T18:15:21-995372c-581a822/android-amd64-emu](https://build.golang.org/log/e3302226f44e6f5512123d77ac84530f4e7ae230)
[2022-11-02T17:01:39-995372c-03f6d81/android-386-emu](https://build.golang.org/log/656ebeac34fb8515b8af7b2fb88b402a559dc1f7)
[2022-11-02T17:01:39-995372c-03f6d81/android-amd64-emu](https://build.golang.org/log/811d65b5175b4d0909902f4c484cf4fcf0123333)
[2022-11-02T14:43:52-995372c-3ba3b48/android-386-emu](https://build.golang.org/log/ece98e823264b098cf2c59fefd6ca933818d676d)
[2022-11-02T14:43:52-995372c-3ba3b48/android-amd64-emu](https://build.golang.org/log/01f6f02683466081b6c3f9e049749283ccb9c902)
</details>
(236 matching logs)
(attn @golang/vulndb) | test | x vuln tests consistently failing on android builders due to missing compile tool starting fail testinits callstacks test go err exit status stderr go no such tool compile fail exitcode fail golang org x vuln internal govulncheck ok golang org x vuln internal semver ok golang org x vuln internal web ok golang org x vuln osv fail testslicing slicing test go err exit status stderr go no such tool compile fail testimports source test go err exit status stderr go no such tool compile fail testrequires source test go err exit status stderr go no such tool compile fail testcalls source test go err exit status stderr go no such tool compile fail testfiltering source test go err exit status stderr go no such tool compile fail testallsymbolsvulnerable source test go err exit status stderr go no such tool compile fail testnosyntheticnodes source test go err exit status stderr go no such tool compile fail testrecursion source test go err exit status stderr go no such tool compile fail testconvert vulncheck test go err exit status stderr go no such tool compile fail exitcode fail golang org x vuln vulncheck greplogs l e aandroid n no such tool compile n fail s golang org x vuln since details matching logs attn golang vulndb | 1 |
196,033 | 14,790,089,550 | IssuesEvent | 2021-01-12 11:30:40 | kubeedge/kubeedge | https://api.github.com/repos/kubeedge/kubeedge | opened | edge device use containerd failed | kind/failing-test | Edge device side use docker is worked.
I try to use containerd for edge device.
I modifiy the mini edgecore.yaml.
But it always failed!.
> apiVersion: edgecore.config.kubeedge.io/v1alpha1
> database:
> dataSource: /var/lib/kubeedge/edgecore.db
> kind: EdgeCore
> modules:
> edgeHub:
> heartbeat: 15
> httpServer: https://172.16.192.25:10002
> tlsCaFile: /etc/kubeedge/ca/rootCA.crt
> tlsCertFile: /etc/kubeedge/certs/server.crt
> tlsPrivateKeyFile: /etc/kubeedge/certs/server.key
> token: b1346a1f1a2a321ecd29dc519dc66ce9ea216e131da7ca1e594cceda4f037c00.eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE2MTA0NzIzNzZ9.DK8A5G0lfP0t_FXxX9nC-S-tMd0ch3p-TlzpY0JuxIc
> websocket:
> enable: true
> handshakeTimeout: 30
> readDeadline: 15
> server: 172.16.192.25:10000
> writeDeadline: 15
> edged:
> cgroupDriver: systemd
> cgroupRoot: ""
> cgroupsPerQOS: true
> clusterDNS: ""
> clusterDomain: ""
> devicePluginEnabled: false
> gpuPluginEnabled: false
> hostnameOverride: containerdedge
> nodeIP: 192.168.137.140
> runtimeRequestTimeout: 2
> podSandboxImage: k8s.gcr.io/pause:3.2
> remoteImageEndpoint: unix:///var/run/containerd/containerd.sock
> remoteRuntimeEndpoint: unix:///var/run/containerd/containerd.sock
> runtimeType: remote
> eventBus:
> mqttMode: 2
> mqttQOS: 0
> mqttRetain: false
> mqttServerExternal: tcp://127.0.0.1:1883
> mqttServerInternal: tcp://127.0.0.1:1884
> ./edgecore --config edgecore.yaml
> 2021-01-12 03:19:28.221296 I | INFO: Install client plugin, protocol: rest
> 2021-01-12 03:19:28.221467 I | INFO: Installed service discovery plugin: edge
> I0112 03:19:28.242535 20469 remote_runtime.go:59] parsed scheme: ""
> I0112 03:19:28.242561 20469 remote_runtime.go:59] scheme "" not registered, fallback to default scheme
> I0112 03:19:28.242610 20469 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{/var/run/containerd/containerd.sock <nil> 0 <nil>}] <nil> <nil>}
> I0112 03:19:28.242631 20469 clientconn.go:948] ClientConn switching balancer to "pick_first"
> I0112 03:19:28.242681 20469 remote_image.go:50] parsed scheme: ""
> I0112 03:19:28.242698 20469 remote_image.go:50] scheme "" not registered, fallback to default scheme
> I0112 03:19:28.242718 20469 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{/var/run/containerd/containerd.sock <nil> 0 <nil>}] <nil> <nil>}
> I0112 03:19:28.242733 20469 clientconn.go:948] ClientConn switching balancer to "pick_first"
> W0112 03:19:33.253309 20469 nvidia.go:61] NVIDIA GPU metrics will not be available: no NVIDIA devices found
> E0112 03:19:33.277444 20469 remote_runtime.go:83] Version from runtime service failed: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService
> E0112 03:19:33.277501 20469 kuberuntime_manager.go:200] Get runtime version failed: get remote runtime typed version failed: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService
> E0112 03:19:33.277514 20469 edged.go:262] init new edged error, New generic runtime manager failed, err: get remote runtime typed version failed: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService
| 1.0 | edge device use containerd failed - Edge device side use docker is worked.
I try to use containerd for edge device.
I modifiy the mini edgecore.yaml.
But it always failed!.
> apiVersion: edgecore.config.kubeedge.io/v1alpha1
> database:
> dataSource: /var/lib/kubeedge/edgecore.db
> kind: EdgeCore
> modules:
> edgeHub:
> heartbeat: 15
> httpServer: https://172.16.192.25:10002
> tlsCaFile: /etc/kubeedge/ca/rootCA.crt
> tlsCertFile: /etc/kubeedge/certs/server.crt
> tlsPrivateKeyFile: /etc/kubeedge/certs/server.key
> token: b1346a1f1a2a321ecd29dc519dc66ce9ea216e131da7ca1e594cceda4f037c00.eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE2MTA0NzIzNzZ9.DK8A5G0lfP0t_FXxX9nC-S-tMd0ch3p-TlzpY0JuxIc
> websocket:
> enable: true
> handshakeTimeout: 30
> readDeadline: 15
> server: 172.16.192.25:10000
> writeDeadline: 15
> edged:
> cgroupDriver: systemd
> cgroupRoot: ""
> cgroupsPerQOS: true
> clusterDNS: ""
> clusterDomain: ""
> devicePluginEnabled: false
> gpuPluginEnabled: false
> hostnameOverride: containerdedge
> nodeIP: 192.168.137.140
> runtimeRequestTimeout: 2
> podSandboxImage: k8s.gcr.io/pause:3.2
> remoteImageEndpoint: unix:///var/run/containerd/containerd.sock
> remoteRuntimeEndpoint: unix:///var/run/containerd/containerd.sock
> runtimeType: remote
> eventBus:
> mqttMode: 2
> mqttQOS: 0
> mqttRetain: false
> mqttServerExternal: tcp://127.0.0.1:1883
> mqttServerInternal: tcp://127.0.0.1:1884
> ./edgecore --config edgecore.yaml
> 2021-01-12 03:19:28.221296 I | INFO: Install client plugin, protocol: rest
> 2021-01-12 03:19:28.221467 I | INFO: Installed service discovery plugin: edge
> I0112 03:19:28.242535 20469 remote_runtime.go:59] parsed scheme: ""
> I0112 03:19:28.242561 20469 remote_runtime.go:59] scheme "" not registered, fallback to default scheme
> I0112 03:19:28.242610 20469 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{/var/run/containerd/containerd.sock <nil> 0 <nil>}] <nil> <nil>}
> I0112 03:19:28.242631 20469 clientconn.go:948] ClientConn switching balancer to "pick_first"
> I0112 03:19:28.242681 20469 remote_image.go:50] parsed scheme: ""
> I0112 03:19:28.242698 20469 remote_image.go:50] scheme "" not registered, fallback to default scheme
> I0112 03:19:28.242718 20469 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{/var/run/containerd/containerd.sock <nil> 0 <nil>}] <nil> <nil>}
> I0112 03:19:28.242733 20469 clientconn.go:948] ClientConn switching balancer to "pick_first"
> W0112 03:19:33.253309 20469 nvidia.go:61] NVIDIA GPU metrics will not be available: no NVIDIA devices found
> E0112 03:19:33.277444 20469 remote_runtime.go:83] Version from runtime service failed: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService
> E0112 03:19:33.277501 20469 kuberuntime_manager.go:200] Get runtime version failed: get remote runtime typed version failed: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService
> E0112 03:19:33.277514 20469 edged.go:262] init new edged error, New generic runtime manager failed, err: get remote runtime typed version failed: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService
| test | edge device use containerd failed edge device side use docker is worked i try to use containerd for edge device i modifiy the mini edgecore yaml but it always failed apiversion edgecore config kubeedge io database datasource var lib kubeedge edgecore db kind edgecore modules edgehub heartbeat httpserver tlscafile etc kubeedge ca rootca crt tlscertfile etc kubeedge certs server crt tlsprivatekeyfile etc kubeedge certs server key token s websocket enable true handshaketimeout readdeadline server writedeadline edged cgroupdriver systemd cgrouproot cgroupsperqos true clusterdns clusterdomain devicepluginenabled false gpupluginenabled false hostnameoverride containerdedge nodeip runtimerequesttimeout podsandboximage gcr io pause remoteimageendpoint unix var run containerd containerd sock remoteruntimeendpoint unix var run containerd containerd sock runtimetype remote eventbus mqttmode mqttqos mqttretain false mqttserverexternal tcp mqttserverinternal tcp edgecore config edgecore yaml i info install client plugin protocol rest i info installed service discovery plugin edge remote runtime go parsed scheme remote runtime go scheme not registered fallback to default scheme passthrough go ccresolverwrapper sending update to cc clientconn go clientconn switching balancer to pick first remote image go parsed scheme remote image go scheme not registered fallback to default scheme passthrough go ccresolverwrapper sending update to cc clientconn go clientconn switching balancer to pick first nvidia go nvidia gpu metrics will not be available no nvidia devices found remote runtime go version from runtime service failed rpc error code unimplemented desc unknown service runtime runtimeservice kuberuntime manager go get runtime version failed get remote runtime typed version failed rpc error code unimplemented desc unknown service runtime runtimeservice edged go init new edged error new generic runtime manager failed err get remote runtime typed version failed rpc error code unimplemented desc unknown service runtime runtimeservice | 1 |
37,101 | 18,108,360,618 | IssuesEvent | 2021-09-22 22:12:53 | mozilla-mobile/fenix | https://api.github.com/repos/mozilla-mobile/fenix | closed | [Bug]: pinch to zoom lag | 🐞 bug eng:performance needs:triage | ### Steps to reproduce
1. Go to gsmarena.com
2. Switch to desktop view
3.Try zoom in and zoom out (either pinch to zoom or double tap hold and swipe to zoom)
### Expected behaviour
Smooth pinch to zoom animation
### Actual behaviour
Laggy animation and sometimes doesn't zoom out
### Device name
Samsung Galaxy M51
### Android version
Android 11
### Firefox release type
Firefox Nightly
### Firefox version
94.0a1
### Device logs
_No response_
### Additional information
https://user-images.githubusercontent.com/90913333/133792396-3c518f1e-af77-4150-94bb-411fe23e89dd.mp4
| True | [Bug]: pinch to zoom lag - ### Steps to reproduce
1. Go to gsmarena.com
2. Switch to desktop view
3.Try zoom in and zoom out (either pinch to zoom or double tap hold and swipe to zoom)
### Expected behaviour
Smooth pinch to zoom animation
### Actual behaviour
Laggy animation and sometimes doesn't zoom out
### Device name
Samsung Galaxy M51
### Android version
Android 11
### Firefox release type
Firefox Nightly
### Firefox version
94.0a1
### Device logs
_No response_
### Additional information
https://user-images.githubusercontent.com/90913333/133792396-3c518f1e-af77-4150-94bb-411fe23e89dd.mp4
| non_test | pinch to zoom lag steps to reproduce go to gsmarena com switch to desktop view try zoom in and zoom out either pinch to zoom or double tap hold and swipe to zoom expected behaviour smooth pinch to zoom animation actual behaviour laggy animation and sometimes doesn t zoom out device name samsung galaxy android version android firefox release type firefox nightly firefox version device logs no response additional information | 0 |
170,229 | 14,245,546,483 | IssuesEvent | 2020-11-19 08:50:02 | ing-bank/probatus | https://api.github.com/repos/ing-bank/probatus | opened | Make an experiment comparing sklearn.RFECV with ShapRFECV | documentation | **Issue Description**
- Compare RFECV with ShapRFECV in an experiment in a jupyter notebook
- Make a page in docs presenting this experiment
**Code snippets**
There are some ready to use code snippets:
```python
from probatus.feature_elimination import ShapRFECV
import numpy as np
import pandas as pd
import lightgbm
from sklearn.datasets import make_classification
from sklearn.model_selection import train_test_split, cross_val_score
from sklearn.feature_selection import RFECV
import matplotlib.pyplot as plt
# Prepare train and test data:
X, y = make_classification(n_samples=10000, class_sep=0.1, n_informative=40, n_features=50,
random_state=0, n_clusters_per_class=10)
X = pd.DataFrame(X)
X_train, X_test, y_train, y_test = train_test_split(X, y, test_size=0.5, random_state=42)
# Set up the model:
clf = lightgbm.LGBMClassifier(n_estimators=10, num_leaves=7)
# Run RFECV and ShapRFECV with the same parameters
rfe = RFECV(clf, step=1, cv=10, scoring='roc_auc', n_jobs=3).fit(X_train, y_train)
shap_elimination = ShapRFECV(clf=clf, step=2, cv=10, scoring='roc_auc', n_jobs=3)
shap_report = shap_elimination.fit_compute(X_train, y_train)
# Check how many freatures are selected by RFECV
rfe_num_features = rfe.n_features_
# RFE has chosen 13 features
# Compare the CV Validation AUC for different number of features in each method.
ax = pd.DataFrame({'RFECV Validation AUC': list(reversed(rfe.grid_scores_)),
'ShapRFECV Validation AUC': report['val_metric_mean'].values.tolist()},
index=report['num_features'].values.tolist()).plot(ylim=(0.5, 0.6), rot=10, title='Comparison of RFECV and ShapRFECV', figsize=(10,5))
ax.set_ylabel("Model Performance")
ax.set_xlabel("Number of features")
ax.invert_xaxis()
plt.show()
# Calculate the AUC for the models with different feature sets
test_auc_full = clf.fit(X_train, y_train).score(X_test, y_test)
val_auc_full = np.mean(cross_val_score(clf, X_train, y_train, cv=10))
rfe_features_set = X_train.columns[rfe.support_]
test_auc_rfe = clf.fit(X_train[rfe_features_set], y_train).score(X_test[rfe_features_set], y_test)
val_auc_rfe = rfe.grid_scores_[rfe.n_features_]
shap_feature_set = X_train.columns[shap_elimination.get_reduced_features_set(n_features_shap)]
test_auc_shap = clf.fit(X_train[shap_feature_set], y_train).score(X_test[shap_feature_set], y_test)
val_auc_shap = report[report.num_features == n_features_shap]['val_metric_mean'].values[0]
shap_feature_set_size_rfe = X_train.columns[shap_elimination.get_reduced_features_set(rfe.n_features_)]
test_auc_shap_size_rfe = clf.fit(X_train[shap_feature_set_size_rfe], y_train).score(X_test[shap_feature_set_size_rfe], y_test)
val_auc_shap_size_rfe = report[report.num_features == rfe.n_features_]['val_metric_mean'].values[0]
# Plot Test and Validation Performance
variants = ('All 50 features', f'RFECV {rfe.n_features_} features', f'ShapRFECV {n_features_shap} features', f'ShapRFECV {rfe.n_features_} features')
results_test = [test_auc_full, test_auc_rfe, test_auc_shap, test_auc_shap_size_rfe]
results_val = [val_auc_full, val_auc_rfe, val_auc_shap, val_auc_shap_size_rfe]
ax = pd.DataFrame({'CV Validation AUC': results_val,
'Test AUC': results_test}, index=variants).plot.bar(ylim=(0.5, 0.60), rot=10, title='Comparison of RFECV and ShapRFECV', figsize=(10,5))
ax.set_ylabel("Model Performance")
plt.show()
``` | 1.0 | Make an experiment comparing sklearn.RFECV with ShapRFECV - **Issue Description**
- Compare RFECV with ShapRFECV in an experiment in a jupyter notebook
- Make a page in docs presenting this experiment
**Code snippets**
There are some ready to use code snippets:
```python
from probatus.feature_elimination import ShapRFECV
import numpy as np
import pandas as pd
import lightgbm
from sklearn.datasets import make_classification
from sklearn.model_selection import train_test_split, cross_val_score
from sklearn.feature_selection import RFECV
import matplotlib.pyplot as plt
# Prepare train and test data:
X, y = make_classification(n_samples=10000, class_sep=0.1, n_informative=40, n_features=50,
random_state=0, n_clusters_per_class=10)
X = pd.DataFrame(X)
X_train, X_test, y_train, y_test = train_test_split(X, y, test_size=0.5, random_state=42)
# Set up the model:
clf = lightgbm.LGBMClassifier(n_estimators=10, num_leaves=7)
# Run RFECV and ShapRFECV with the same parameters
rfe = RFECV(clf, step=1, cv=10, scoring='roc_auc', n_jobs=3).fit(X_train, y_train)
shap_elimination = ShapRFECV(clf=clf, step=2, cv=10, scoring='roc_auc', n_jobs=3)
shap_report = shap_elimination.fit_compute(X_train, y_train)
# Check how many freatures are selected by RFECV
rfe_num_features = rfe.n_features_
# RFE has chosen 13 features
# Compare the CV Validation AUC for different number of features in each method.
ax = pd.DataFrame({'RFECV Validation AUC': list(reversed(rfe.grid_scores_)),
'ShapRFECV Validation AUC': report['val_metric_mean'].values.tolist()},
index=report['num_features'].values.tolist()).plot(ylim=(0.5, 0.6), rot=10, title='Comparison of RFECV and ShapRFECV', figsize=(10,5))
ax.set_ylabel("Model Performance")
ax.set_xlabel("Number of features")
ax.invert_xaxis()
plt.show()
# Calculate the AUC for the models with different feature sets
test_auc_full = clf.fit(X_train, y_train).score(X_test, y_test)
val_auc_full = np.mean(cross_val_score(clf, X_train, y_train, cv=10))
rfe_features_set = X_train.columns[rfe.support_]
test_auc_rfe = clf.fit(X_train[rfe_features_set], y_train).score(X_test[rfe_features_set], y_test)
val_auc_rfe = rfe.grid_scores_[rfe.n_features_]
shap_feature_set = X_train.columns[shap_elimination.get_reduced_features_set(n_features_shap)]
test_auc_shap = clf.fit(X_train[shap_feature_set], y_train).score(X_test[shap_feature_set], y_test)
val_auc_shap = report[report.num_features == n_features_shap]['val_metric_mean'].values[0]
shap_feature_set_size_rfe = X_train.columns[shap_elimination.get_reduced_features_set(rfe.n_features_)]
test_auc_shap_size_rfe = clf.fit(X_train[shap_feature_set_size_rfe], y_train).score(X_test[shap_feature_set_size_rfe], y_test)
val_auc_shap_size_rfe = report[report.num_features == rfe.n_features_]['val_metric_mean'].values[0]
# Plot Test and Validation Performance
variants = ('All 50 features', f'RFECV {rfe.n_features_} features', f'ShapRFECV {n_features_shap} features', f'ShapRFECV {rfe.n_features_} features')
results_test = [test_auc_full, test_auc_rfe, test_auc_shap, test_auc_shap_size_rfe]
results_val = [val_auc_full, val_auc_rfe, val_auc_shap, val_auc_shap_size_rfe]
ax = pd.DataFrame({'CV Validation AUC': results_val,
'Test AUC': results_test}, index=variants).plot.bar(ylim=(0.5, 0.60), rot=10, title='Comparison of RFECV and ShapRFECV', figsize=(10,5))
ax.set_ylabel("Model Performance")
plt.show()
``` | non_test | make an experiment comparing sklearn rfecv with shaprfecv issue description compare rfecv with shaprfecv in an experiment in a jupyter notebook make a page in docs presenting this experiment code snippets there are some ready to use code snippets python from probatus feature elimination import shaprfecv import numpy as np import pandas as pd import lightgbm from sklearn datasets import make classification from sklearn model selection import train test split cross val score from sklearn feature selection import rfecv import matplotlib pyplot as plt prepare train and test data x y make classification n samples class sep n informative n features random state n clusters per class x pd dataframe x x train x test y train y test train test split x y test size random state set up the model clf lightgbm lgbmclassifier n estimators num leaves run rfecv and shaprfecv with the same parameters rfe rfecv clf step cv scoring roc auc n jobs fit x train y train shap elimination shaprfecv clf clf step cv scoring roc auc n jobs shap report shap elimination fit compute x train y train check how many freatures are selected by rfecv rfe num features rfe n features rfe has chosen features compare the cv validation auc for different number of features in each method ax pd dataframe rfecv validation auc list reversed rfe grid scores shaprfecv validation auc report values tolist index report values tolist plot ylim rot title comparison of rfecv and shaprfecv figsize ax set ylabel model performance ax set xlabel number of features ax invert xaxis plt show calculate the auc for the models with different feature sets test auc full clf fit x train y train score x test y test val auc full np mean cross val score clf x train y train cv rfe features set x train columns test auc rfe clf fit x train y train score x test y test val auc rfe rfe grid scores shap feature set x train columns test auc shap clf fit x train y train score x test y test val auc shap report values shap feature set size rfe x train columns test auc shap size rfe clf fit x train y train score x test y test val auc shap size rfe report values plot test and validation performance variants all features f rfecv rfe n features features f shaprfecv n features shap features f shaprfecv rfe n features features results test results val ax pd dataframe cv validation auc results val test auc results test index variants plot bar ylim rot title comparison of rfecv and shaprfecv figsize ax set ylabel model performance plt show | 0 |
48,562 | 10,260,989,149 | IssuesEvent | 2019-08-22 08:46:41 | Cinimex-Informatica/mq-java-exporter | https://api.github.com/repos/Cinimex-Informatica/mq-java-exporter | closed | Change "hundredth" type to "untyped" | code config docs enhancement | As far as "hundredth" units are quite vague, the decision to shift to "untyped" type is made. | 1.0 | Change "hundredth" type to "untyped" - As far as "hundredth" units are quite vague, the decision to shift to "untyped" type is made. | non_test | change hundredth type to untyped as far as hundredth units are quite vague the decision to shift to untyped type is made | 0 |
66,657 | 3,256,967,922 | IssuesEvent | 2015-10-20 15:52:03 | cs2103aug2015-w13-2j/main | https://api.github.com/repos/cs2103aug2015-w13-2j/main | closed | I want to be able to mark my tasks as important | priority.high type.story | so that I can prioritise which tasks to complete first | 1.0 | I want to be able to mark my tasks as important - so that I can prioritise which tasks to complete first | non_test | i want to be able to mark my tasks as important so that i can prioritise which tasks to complete first | 0 |
22,676 | 6,284,466,199 | IssuesEvent | 2017-07-19 07:51:21 | joomla/joomla-cms | https://api.github.com/repos/joomla/joomla-cms | closed | Insert Field in Articles shows as Field Number {field } when clicked on Title in Category Blog | No Code Attached Yet | ### Steps to reproduce the issue
1. Insert Field in Article
2. Article Options - Set Linked Titles to Yes, Show Unauthorised Links to Yes, Show Intro Text to Hide,
3. Set Article Access to Registered
4. Create any custom field with access right to public and insert in the article before read more (intro text)
5. Create category blog menu item
6. Check front end as non logged in user.
### Expected result
Clicking on article title should show inserted field value.
### Actual result
Clicking on article title show field name as (field --}
### System information (as much as possible)
1. PHP 7.0.18
2. Joomla 3.7
3. Database 5.6.28
4. Database Collation utf8_general_ci
5. Joomla Platform Version 13.1.0 Stable
### Additional comments
| 1.0 | Insert Field in Articles shows as Field Number {field } when clicked on Title in Category Blog - ### Steps to reproduce the issue
1. Insert Field in Article
2. Article Options - Set Linked Titles to Yes, Show Unauthorised Links to Yes, Show Intro Text to Hide,
3. Set Article Access to Registered
4. Create any custom field with access right to public and insert in the article before read more (intro text)
5. Create category blog menu item
6. Check front end as non logged in user.
### Expected result
Clicking on article title should show inserted field value.
### Actual result
Clicking on article title show field name as (field --}
### System information (as much as possible)
1. PHP 7.0.18
2. Joomla 3.7
3. Database 5.6.28
4. Database Collation utf8_general_ci
5. Joomla Platform Version 13.1.0 Stable
### Additional comments
| non_test | insert field in articles shows as field number field when clicked on title in category blog steps to reproduce the issue insert field in article article options set linked titles to yes show unauthorised links to yes show intro text to hide set article access to registered create any custom field with access right to public and insert in the article before read more intro text create category blog menu item check front end as non logged in user expected result clicking on article title should show inserted field value actual result clicking on article title show field name as field system information as much as possible php joomla database database collation general ci joomla platform version stable additional comments | 0 |
245,161 | 20,750,073,226 | IssuesEvent | 2022-03-15 06:14:03 | mennaelkashef/eShop | https://api.github.com/repos/mennaelkashef/eShop | opened | Failed | Hello! RULE-GOT-APPLIED DOES-NOT-CONTAIN-STRING Rule-works-on-convert-to-bug test instabug | # :clipboard: Bug Details
>Failed
key | value
--|--
Reported At | 2022-03-15 06:13:07 UTC
Categories | Report a bug, Failed Custom
Tags | test, Hello!, RULE-GOT-APPLIED, DOES-NOT-CONTAIN-STRING, Rule-works-on-convert-to-bug, instabug
App Version | 1.1 (1)
Session Duration | 0
Device | Google sdk_gphone_arm64, OS Level 30
Display | 1080x2220 (xhdpi)
Location | Giza, Egypt (en)
## :point_right: [View Full Bug Report on Instabug](https://dashboard.instabug.com/applications/android-sample/beta/bugs/8658?utm_source=github&utm_medium=integrations) :point_left:
___
# :iphone: View Hierarchy
This bug was reported from **com.example.app.main.MainFragment**
Find its interactive view hierarchy with all its subviews here: :point_right: **[Check View Hierarchy](https://dashboard.instabug.com/applications/android-sample/beta/bugs/8658?show-hierarchy-view=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :chart_with_downwards_trend: Session Profiler
Here is what the app was doing right before the bug was reported:
Key | Value
--|--
Find all the changes that happened in the parameters mentioned above during the last 60 seconds before the bug was reported here: :point_right: **[View Full Session Profiler](https://dashboard.instabug.com/applications/android-sample/beta/bugs/8658?show-session-profiler=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :bust_in_silhouette: User Info
### User Attributes
```
key_name 706865304: key value bla bla bla la
key_name -1425189832: key value bla bla bla la
key_name 601669085: key value bla bla bla la
```
___
# :mag_right: Logs
### User Steps
Here are the last 10 steps done by the user right before the bug was reported:
```
06:13:07 com.example.app.main.MainActivity was created.
06:13:07 com.example.app.main.MainActivity was started.
06:13:07 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was attached.
06:13:07 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was created.
06:13:07 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was started.
06:13:07 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was resumed.
06:13:07 com.example.app.main.MainActivity was resumed.
```
Find all the user steps done by the user throughout the session here: :point_right: **[View All User Steps](https://dashboard.instabug.com/applications/android-sample/beta/bugs/8658?show-logs=user_steps&utm_source=github&utm_medium=integrations)** :point_left:
### Console Log
Here are the last 10 console logs logged right before the bug was reported:
```
06:13:08 D/IB-ViewHierarchyDiskUtils(13816): file zipped successfully, path: /storage/emulated/0/Android/data/com.example.app/files/instabug/view-hierarchy-images/0-2.png, time in MS: 1647324788426
06:13:08 D/IB-ViewHierarchyDiskUtils(13816): file zipped successfully, path: /storage/emulated/0/Android/data/com.example.app/files/instabug/view-hierarchy-images/0-3.png, time in MS: 1647324788426
06:13:08 D/IB-ViewHierarchyDiskUtils(13816): zip viewHierarchy images done successfully, path: /storage/emulated/0/Android/data/com.example.app/files/instabug/view_hierarchy_attachment_1647324788402.zip, time in MS: 1647324788426
06:13:08 D/IB-ActivityViewInspectorTask(13816): viewHierarchy images zipped successfully, zip file uri: file:///storage/emulated/0/Android/data/com.example.app/files/instabug/view_hierarchy_attachment_1647324788402.zip, time in MS: 1647324788433
06:13:08 D/IB-ActivityViewInspectorTask(13816): activity view inspection done successfully, time in MS: 1647324788435
06:13:08 D/IB-ActivityViewInspectorTask(13816): bug ! null,converting>json started
06:13:08 D/IB-ActivityViewInspectorTask(13816): bug ! null,converting>json ended
06:13:08 D/IB-ActivityViewInspectorTask(13816): bug ! null,set inspection state
06:13:08 D/IB-ActionsOrchestrator(13816): runAction
06:13:08 D/IB-AttachmentsUtility(13816): encryptAttachments
```
Find all the logged console logs throughout the session here: :point_right: **[View All Console Log](https://dashboard.instabug.com/applications/android-sample/beta/bugs/8658?show-logs=console_log&utm_source=github&utm_medium=integrations)** :point_left:
___
# :camera: Images
[](https://d38gnqwzxziyyy.cloudfront.net/attachments/bugs/18012290/3596860679eae6d4d692987822618aff_original/25350611/bug_1647324787620_.jpg?Expires=4802998441&Signature=jq4xrdWoX6ltWrN5FNCUTXOoQAKu0rq~iNcYG1e3sP8BADenznwFu6Xu3cSfGNVcTr1Rx9yu5R2scKQfKjXJtXRQolBt6MsBXsaKMDSlA1owsO0AZiIlxhvQGKDKQM70mHfPZXuV3mwlEL4kkrRKgc6sj6Y2zOhsTjzAEcA8TuHNOrLeCp8tAIS07JpNiDCixTOv9zsM-X7j785SMgoJr4LkYp~u5fUkVh6SneNsqeXdAYSAFXShM346gs~~NWF9IF-Df~xS64kXKalXFoC9wRlO6lMLi7knee61VULRI8kkxDhcXdz4AbKwE8E7NqEe3u8~kNJJHx8XN~rGqavC3Q__&Key-Pair-Id=APKAIXAG65U6UUX7JAQQ)
___
# :warning: Looking for More Details?
1. **Network Log**: we are unable to capture your network requests automatically. If you are using HttpUrlConnection or Okhttp requests, [**check the details mentioned here**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations#section-network-logs).
2. **User Events**: start capturing custom User Events to send them along with each report. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations).
3. **Instabug Log**: start adding Instabug logs to see them right inside each report you receive. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations). | 1.0 | Failed - # :clipboard: Bug Details
>Failed
key | value
--|--
Reported At | 2022-03-15 06:13:07 UTC
Categories | Report a bug, Failed Custom
Tags | test, Hello!, RULE-GOT-APPLIED, DOES-NOT-CONTAIN-STRING, Rule-works-on-convert-to-bug, instabug
App Version | 1.1 (1)
Session Duration | 0
Device | Google sdk_gphone_arm64, OS Level 30
Display | 1080x2220 (xhdpi)
Location | Giza, Egypt (en)
## :point_right: [View Full Bug Report on Instabug](https://dashboard.instabug.com/applications/android-sample/beta/bugs/8658?utm_source=github&utm_medium=integrations) :point_left:
___
# :iphone: View Hierarchy
This bug was reported from **com.example.app.main.MainFragment**
Find its interactive view hierarchy with all its subviews here: :point_right: **[Check View Hierarchy](https://dashboard.instabug.com/applications/android-sample/beta/bugs/8658?show-hierarchy-view=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :chart_with_downwards_trend: Session Profiler
Here is what the app was doing right before the bug was reported:
Key | Value
--|--
Find all the changes that happened in the parameters mentioned above during the last 60 seconds before the bug was reported here: :point_right: **[View Full Session Profiler](https://dashboard.instabug.com/applications/android-sample/beta/bugs/8658?show-session-profiler=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :bust_in_silhouette: User Info
### User Attributes
```
key_name 706865304: key value bla bla bla la
key_name -1425189832: key value bla bla bla la
key_name 601669085: key value bla bla bla la
```
___
# :mag_right: Logs
### User Steps
Here are the last 10 steps done by the user right before the bug was reported:
```
06:13:07 com.example.app.main.MainActivity was created.
06:13:07 com.example.app.main.MainActivity was started.
06:13:07 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was attached.
06:13:07 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was created.
06:13:07 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was started.
06:13:07 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was resumed.
06:13:07 com.example.app.main.MainActivity was resumed.
```
Find all the user steps done by the user throughout the session here: :point_right: **[View All User Steps](https://dashboard.instabug.com/applications/android-sample/beta/bugs/8658?show-logs=user_steps&utm_source=github&utm_medium=integrations)** :point_left:
### Console Log
Here are the last 10 console logs logged right before the bug was reported:
```
06:13:08 D/IB-ViewHierarchyDiskUtils(13816): file zipped successfully, path: /storage/emulated/0/Android/data/com.example.app/files/instabug/view-hierarchy-images/0-2.png, time in MS: 1647324788426
06:13:08 D/IB-ViewHierarchyDiskUtils(13816): file zipped successfully, path: /storage/emulated/0/Android/data/com.example.app/files/instabug/view-hierarchy-images/0-3.png, time in MS: 1647324788426
06:13:08 D/IB-ViewHierarchyDiskUtils(13816): zip viewHierarchy images done successfully, path: /storage/emulated/0/Android/data/com.example.app/files/instabug/view_hierarchy_attachment_1647324788402.zip, time in MS: 1647324788426
06:13:08 D/IB-ActivityViewInspectorTask(13816): viewHierarchy images zipped successfully, zip file uri: file:///storage/emulated/0/Android/data/com.example.app/files/instabug/view_hierarchy_attachment_1647324788402.zip, time in MS: 1647324788433
06:13:08 D/IB-ActivityViewInspectorTask(13816): activity view inspection done successfully, time in MS: 1647324788435
06:13:08 D/IB-ActivityViewInspectorTask(13816): bug ! null,converting>json started
06:13:08 D/IB-ActivityViewInspectorTask(13816): bug ! null,converting>json ended
06:13:08 D/IB-ActivityViewInspectorTask(13816): bug ! null,set inspection state
06:13:08 D/IB-ActionsOrchestrator(13816): runAction
06:13:08 D/IB-AttachmentsUtility(13816): encryptAttachments
```
Find all the logged console logs throughout the session here: :point_right: **[View All Console Log](https://dashboard.instabug.com/applications/android-sample/beta/bugs/8658?show-logs=console_log&utm_source=github&utm_medium=integrations)** :point_left:
___
# :camera: Images
[](https://d38gnqwzxziyyy.cloudfront.net/attachments/bugs/18012290/3596860679eae6d4d692987822618aff_original/25350611/bug_1647324787620_.jpg?Expires=4802998441&Signature=jq4xrdWoX6ltWrN5FNCUTXOoQAKu0rq~iNcYG1e3sP8BADenznwFu6Xu3cSfGNVcTr1Rx9yu5R2scKQfKjXJtXRQolBt6MsBXsaKMDSlA1owsO0AZiIlxhvQGKDKQM70mHfPZXuV3mwlEL4kkrRKgc6sj6Y2zOhsTjzAEcA8TuHNOrLeCp8tAIS07JpNiDCixTOv9zsM-X7j785SMgoJr4LkYp~u5fUkVh6SneNsqeXdAYSAFXShM346gs~~NWF9IF-Df~xS64kXKalXFoC9wRlO6lMLi7knee61VULRI8kkxDhcXdz4AbKwE8E7NqEe3u8~kNJJHx8XN~rGqavC3Q__&Key-Pair-Id=APKAIXAG65U6UUX7JAQQ)
___
# :warning: Looking for More Details?
1. **Network Log**: we are unable to capture your network requests automatically. If you are using HttpUrlConnection or Okhttp requests, [**check the details mentioned here**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations#section-network-logs).
2. **User Events**: start capturing custom User Events to send them along with each report. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations).
3. **Instabug Log**: start adding Instabug logs to see them right inside each report you receive. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations). | test | failed clipboard bug details failed key value reported at utc categories report a bug failed custom tags test hello rule got applied does not contain string rule works on convert to bug instabug app version session duration device google sdk gphone os level display xhdpi location giza egypt en point right point left iphone view hierarchy this bug was reported from com example app main mainfragment find its interactive view hierarchy with all its subviews here point right point left chart with downwards trend session profiler here is what the app was doing right before the bug was reported key value find all the changes that happened in the parameters mentioned above during the last seconds before the bug was reported here point right point left bust in silhouette user info user attributes key name key value bla bla bla la key name key value bla bla bla la key name key value bla bla bla la mag right logs user steps here are the last steps done by the user right before the bug was reported com example app main mainactivity was created com example app main mainactivity was started in activity com example app main mainactivity fragment com example app main mainfragment was attached in activity com example app main mainactivity fragment com example app main mainfragment was created in activity com example app main mainactivity fragment com example app main mainfragment was started in activity com example app main mainactivity fragment com example app main mainfragment was resumed com example app main mainactivity was resumed find all the user steps done by the user throughout the session here point right point left console log here are the last console logs logged right before the bug was reported d ib viewhierarchydiskutils file zipped successfully path storage emulated android data com example app files instabug view hierarchy images png time in ms d ib viewhierarchydiskutils file zipped successfully path storage emulated android data com example app files instabug view hierarchy images png time in ms d ib viewhierarchydiskutils zip viewhierarchy images done successfully path storage emulated android data com example app files instabug view hierarchy attachment zip time in ms d ib activityviewinspectortask viewhierarchy images zipped successfully zip file uri file storage emulated android data com example app files instabug view hierarchy attachment zip time in ms d ib activityviewinspectortask activity view inspection done successfully time in ms d ib activityviewinspectortask bug null converting json started d ib activityviewinspectortask bug null converting json ended d ib activityviewinspectortask bug null set inspection state d ib actionsorchestrator runaction d ib attachmentsutility encryptattachments find all the logged console logs throughout the session here point right point left camera images warning looking for more details network log we are unable to capture your network requests automatically if you are using httpurlconnection or okhttp requests user events start capturing custom user events to send them along with each report instabug log start adding instabug logs to see them right inside each report you receive | 1 |
60,189 | 6,673,837,422 | IssuesEvent | 2017-10-04 16:19:04 | ExpressGateway/express-gateway.io | https://api.github.com/repos/ExpressGateway/express-gateway.io | closed | Admin: spec for API signatures for new API | test | - extend your current OpenAPI spec - adding to what we already have
- examples of fine grain and course grain manipulation
- examples of URL structures
- overall architecture to do client interaction - CLI + web GUI (including JSON schema based validation and typing etc) | 1.0 | Admin: spec for API signatures for new API - - extend your current OpenAPI spec - adding to what we already have
- examples of fine grain and course grain manipulation
- examples of URL structures
- overall architecture to do client interaction - CLI + web GUI (including JSON schema based validation and typing etc) | test | admin spec for api signatures for new api extend your current openapi spec adding to what we already have examples of fine grain and course grain manipulation examples of url structures overall architecture to do client interaction cli web gui including json schema based validation and typing etc | 1 |
332,601 | 29,488,433,107 | IssuesEvent | 2023-06-02 11:38:58 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | roachtest: failover/liveness/deadlock/lease=expiration failed | C-test-failure O-robot O-roachtest branch-master release-blocker T-kv | roachtest.failover/liveness/deadlock/lease=expiration [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/10356406?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/10356406?buildTab=artifacts#/failover/liveness/deadlock/lease=expiration) on master @ [bf25b7bf93a6b8e57557813957da263389796bb4](https://github.com/cockroachdb/cockroach/commits/bf25b7bf93a6b8e57557813957da263389796bb4):
```
test artifacts and logs in: /artifacts/failover/liveness/deadlock/lease=expiration/run_1
(assertions.go:333).Fail:
Error Trace: github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/failover.go:1577
github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/failover.go:1038
main/pkg/cmd/roachtest/monitor.go:105
golang.org/x/sync/errgroup/external/org_golang_x_sync/errgroup/errgroup.go:75
GOROOT/src/runtime/asm_amd64.s:1594
Error: "[2]" should have 5 item(s), but has 1
Test: failover/liveness/deadlock/lease=expiration
Messages: couldn't lock requested number of replicas
(require.go:1162).Len: FailNow called
(cluster.go:2095).Run: output in run_112210.018937327_n5_cockroach-workload-r: ./cockroach workload run kv --read-percent 50 --duration 20m --concurrency 256 --max-rate 2048 --timeout 1m --tolerate-errors --histograms=perf/stats.json {pgurl:1-3} returned: context canceled
(monitor.go:127).Wait: monitor failure: monitor task failed: t.Fatal() was called
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/kv-triage
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*failover/liveness/deadlock/lease=expiration.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 2.0 | roachtest: failover/liveness/deadlock/lease=expiration failed - roachtest.failover/liveness/deadlock/lease=expiration [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/10356406?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/10356406?buildTab=artifacts#/failover/liveness/deadlock/lease=expiration) on master @ [bf25b7bf93a6b8e57557813957da263389796bb4](https://github.com/cockroachdb/cockroach/commits/bf25b7bf93a6b8e57557813957da263389796bb4):
```
test artifacts and logs in: /artifacts/failover/liveness/deadlock/lease=expiration/run_1
(assertions.go:333).Fail:
Error Trace: github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/failover.go:1577
github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/failover.go:1038
main/pkg/cmd/roachtest/monitor.go:105
golang.org/x/sync/errgroup/external/org_golang_x_sync/errgroup/errgroup.go:75
GOROOT/src/runtime/asm_amd64.s:1594
Error: "[2]" should have 5 item(s), but has 1
Test: failover/liveness/deadlock/lease=expiration
Messages: couldn't lock requested number of replicas
(require.go:1162).Len: FailNow called
(cluster.go:2095).Run: output in run_112210.018937327_n5_cockroach-workload-r: ./cockroach workload run kv --read-percent 50 --duration 20m --concurrency 256 --max-rate 2048 --timeout 1m --tolerate-errors --histograms=perf/stats.json {pgurl:1-3} returned: context canceled
(monitor.go:127).Wait: monitor failure: monitor task failed: t.Fatal() was called
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/kv-triage
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*failover/liveness/deadlock/lease=expiration.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| test | roachtest failover liveness deadlock lease expiration failed roachtest failover liveness deadlock lease expiration with on master test artifacts and logs in artifacts failover liveness deadlock lease expiration run assertions go fail error trace github com cockroachdb cockroach pkg cmd roachtest tests failover go github com cockroachdb cockroach pkg cmd roachtest tests failover go main pkg cmd roachtest monitor go golang org x sync errgroup external org golang x sync errgroup errgroup go goroot src runtime asm s error should have item s but has test failover liveness deadlock lease expiration messages couldn t lock requested number of replicas require go len failnow called cluster go run output in run cockroach workload r cockroach workload run kv read percent duration concurrency max rate timeout tolerate errors histograms perf stats json pgurl returned context canceled monitor go wait monitor failure monitor task failed t fatal was called parameters roachtest cloud gce roachtest cpu roachtest encrypted false roachtest ssd help see see cc cockroachdb kv triage | 1 |
705,892 | 24,253,662,215 | IssuesEvent | 2022-09-27 15:56:27 | NOAA-OWP/inundation-mapping | https://api.github.com/repos/NOAA-OWP/inundation-mapping | closed | [8pt] Download USGS Dems. | High Priority FIM4 | For now, just pull them down RAW (find a home for them). They are coming down as VRT driven and lat/long. A different ticket exists for figuring out how to convert them to HUC and be consumed by FIM
See Issue [668](https://github.com/NOAA-OWP/inundation-mapping/issues/668)
Make sure we have space.. clean up fim_share first. | 1.0 | [8pt] Download USGS Dems. - For now, just pull them down RAW (find a home for them). They are coming down as VRT driven and lat/long. A different ticket exists for figuring out how to convert them to HUC and be consumed by FIM
See Issue [668](https://github.com/NOAA-OWP/inundation-mapping/issues/668)
Make sure we have space.. clean up fim_share first. | non_test | download usgs dems for now just pull them down raw find a home for them they are coming down as vrt driven and lat long a different ticket exists for figuring out how to convert them to huc and be consumed by fim see issue make sure we have space clean up fim share first | 0 |
65,236 | 8,793,824,587 | IssuesEvent | 2018-12-21 21:42:37 | mozilla/dinobuildr | https://api.github.com/repos/mozilla/dinobuildr | closed | Update: Update README | documentation enhancement | As part of the cleanup that went into #143 (removing stale files, updating file/path names) the info in README is out of date and needs to be updated. | 1.0 | Update: Update README - As part of the cleanup that went into #143 (removing stale files, updating file/path names) the info in README is out of date and needs to be updated. | non_test | update update readme as part of the cleanup that went into removing stale files updating file path names the info in readme is out of date and needs to be updated | 0 |
79,305 | 7,704,206,325 | IssuesEvent | 2018-05-21 11:19:52 | DevExpress/DevExtreme | https://api.github.com/repos/DevExpress/DevExtreme | closed | Charts - Bar Width and Spacing Improvements | 18_1 RFC / discussion alpha testing | # The Problem
The following chart customizations were not supported:
* Assigning different bar widths to bar series within a chart
* Adjusting the spacing between bar groups (two neighboring arguments)
* Specify the fixed bar width
* Specify the fixed bar group width
# The Solution
We added the following options to the [Chart](https://js.devexpress.com/Demos/WidgetsGallery/Demo/Charts/StandardBar/jQuery/Light/) and [PolarChart](https://js.devexpress.com/Demos/WidgetsGallery/Demo/Charts/WindRose/jQuery/Light/) components:
## Controlling Bar Group Paddings
You can use the new `barGroupPadding` option to control the spacing between two bar groups. A bar group occupies 0.7 of an argument space width and the rest 0.3 is for padding by default. It may look as follows:
You can change the padding-to-bar ratio by assigning a value from 0 to 1 to the `barGroupPadding` option. For instance, you can remove the padding by setting the option to 0.
```js
{
...
barGroupPadding: 0
}
```
In this case, the chart looks as follows:
It also works the same way with a single series.
With default padding:
Without padding:
## Controlling Bar Group Width
A bar group’s width is calculated based on padding and the total argument value width. So, its absolute value may change depending on the whole chart’s width. You can now use the new `barGroupWidth` option to specify absolute bar group widths. It accepts a group width value in pixels and automatically reduces the value if it exceeds the available space.
For instance, in the following chart, the flexible group’s width occupies 0.7 of the argument area:
You can specify larger absolute padding widths:
```js
{
...
barGroupWidth: 50
}
```
## Controlling Series Bar Paddings and Width
You can control a bar’s padding and width within individual series. Custom series’ padding allows you to visualize an extra data dimension as it is shown in the example below.
The default chart:
With series bar padding customization:
```js
{
...
series: [
{ valueField: "young", name: "0-14", barPadding: 0 },
{ valueField: "middle", name: "15-64", barPadding: 0.3 },
{ valueField: "older", name: "65 and older", barPadding: 0.6 }
]
}
```
Custom series bar width allows you to fix the bar width for specific series on a single or several panes.
The default chart:
The customized chart:
```js
{
...
panes: [{name: "pane1"}, {name: "pane2"}],
series: [
{ valueField: "year2004", name: "2004", pane: "pane1", barWidth: 10 },
{ valueField: "year2001", name: "2001", pane: "pane1", barWidth: 40 },
{ valueField: "year1998", name: "1998", pane: "pane2", barWidth: 20 }
]
}
```
# Try It And Give Us Feedback
Follow the installation guide from the [release page](https://github.com/DevExpress/DevExtreme/releases/tag/18.1.0-sprint.2) and leave us feedback on this topic. Feel free to leave comments or use [GitHub reactions](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments).
| 1.0 | Charts - Bar Width and Spacing Improvements - # The Problem
The following chart customizations were not supported:
* Assigning different bar widths to bar series within a chart
* Adjusting the spacing between bar groups (two neighboring arguments)
* Specify the fixed bar width
* Specify the fixed bar group width
# The Solution
We added the following options to the [Chart](https://js.devexpress.com/Demos/WidgetsGallery/Demo/Charts/StandardBar/jQuery/Light/) and [PolarChart](https://js.devexpress.com/Demos/WidgetsGallery/Demo/Charts/WindRose/jQuery/Light/) components:
## Controlling Bar Group Paddings
You can use the new `barGroupPadding` option to control the spacing between two bar groups. A bar group occupies 0.7 of an argument space width and the rest 0.3 is for padding by default. It may look as follows:
You can change the padding-to-bar ratio by assigning a value from 0 to 1 to the `barGroupPadding` option. For instance, you can remove the padding by setting the option to 0.
```js
{
...
barGroupPadding: 0
}
```
In this case, the chart looks as follows:
It also works the same way with a single series.
With default padding:
Without padding:
## Controlling Bar Group Width
A bar group’s width is calculated based on padding and the total argument value width. So, its absolute value may change depending on the whole chart’s width. You can now use the new `barGroupWidth` option to specify absolute bar group widths. It accepts a group width value in pixels and automatically reduces the value if it exceeds the available space.
For instance, in the following chart, the flexible group’s width occupies 0.7 of the argument area:
You can specify larger absolute padding widths:
```js
{
...
barGroupWidth: 50
}
```
## Controlling Series Bar Paddings and Width
You can control a bar’s padding and width within individual series. Custom series’ padding allows you to visualize an extra data dimension as it is shown in the example below.
The default chart:
With series bar padding customization:
```js
{
...
series: [
{ valueField: "young", name: "0-14", barPadding: 0 },
{ valueField: "middle", name: "15-64", barPadding: 0.3 },
{ valueField: "older", name: "65 and older", barPadding: 0.6 }
]
}
```
Custom series bar width allows you to fix the bar width for specific series on a single or several panes.
The default chart:
The customized chart:
```js
{
...
panes: [{name: "pane1"}, {name: "pane2"}],
series: [
{ valueField: "year2004", name: "2004", pane: "pane1", barWidth: 10 },
{ valueField: "year2001", name: "2001", pane: "pane1", barWidth: 40 },
{ valueField: "year1998", name: "1998", pane: "pane2", barWidth: 20 }
]
}
```
# Try It And Give Us Feedback
Follow the installation guide from the [release page](https://github.com/DevExpress/DevExtreme/releases/tag/18.1.0-sprint.2) and leave us feedback on this topic. Feel free to leave comments or use [GitHub reactions](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments).
| test | charts bar width and spacing improvements the problem the following chart customizations were not supported assigning different bar widths to bar series within a chart adjusting the spacing between bar groups two neighboring arguments specify the fixed bar width specify the fixed bar group width the solution we added the following options to the and components controlling bar group paddings you can use the new bargrouppadding option to control the spacing between two bar groups a bar group occupies of an argument space width and the rest is for padding by default it may look as follows you can change the padding to bar ratio by assigning a value from to to the bargrouppadding option for instance you can remove the padding by setting the option to js bargrouppadding in this case the chart looks as follows it also works the same way with a single series with default padding without padding controlling bar group width a bar group’s width is calculated based on padding and the total argument value width so its absolute value may change depending on the whole chart’s width you can now use the new bargroupwidth option to specify absolute bar group widths it accepts a group width value in pixels and automatically reduces the value if it exceeds the available space for instance in the following chart the flexible group’s width occupies of the argument area you can specify larger absolute padding widths js bargroupwidth controlling series bar paddings and width you can control a bar’s padding and width within individual series custom series’ padding allows you to visualize an extra data dimension as it is shown in the example below the default chart with series bar padding customization js series valuefield young name barpadding valuefield middle name barpadding valuefield older name and older barpadding custom series bar width allows you to fix the bar width for specific series on a single or several panes the default chart the customized chart js panes series valuefield name pane barwidth valuefield name pane barwidth valuefield name pane barwidth try it and give us feedback follow the installation guide from the and leave us feedback on this topic feel free to leave comments or use | 1 |
47,748 | 5,914,380,460 | IssuesEvent | 2017-05-22 02:27:54 | trailofbits/algo | https://api.github.com/repos/trailofbits/algo | closed | Test our support for Android VPN Profiles | client_android needs_tests | We can now generate all-in-one profiles for users of the Android StrongSwan app.
https://github.com/trailofbits/algo/commit/aca036142fb14c037ea457a72881580b757745a9
We should test to make sure this feature works as expected and update any relevant documentation for it. | 1.0 | Test our support for Android VPN Profiles - We can now generate all-in-one profiles for users of the Android StrongSwan app.
https://github.com/trailofbits/algo/commit/aca036142fb14c037ea457a72881580b757745a9
We should test to make sure this feature works as expected and update any relevant documentation for it. | test | test our support for android vpn profiles we can now generate all in one profiles for users of the android strongswan app we should test to make sure this feature works as expected and update any relevant documentation for it | 1 |
76,709 | 3,491,142,378 | IssuesEvent | 2016-01-04 14:22:18 | ngageoint/hootenanny-ui | https://api.github.com/repos/ngageoint/hootenanny-ui | opened | Copy/paste attribution creates empty fields | Category: UI Priority: High Status: New/Undefined Type: Bug | When copying/pasting attributes for line features, it will create blank "tunnel" and "bridge" attributes for the feature. This occurs even when the copied attribution does not include a bridge or tunnel attribute. | 1.0 | Copy/paste attribution creates empty fields - When copying/pasting attributes for line features, it will create blank "tunnel" and "bridge" attributes for the feature. This occurs even when the copied attribution does not include a bridge or tunnel attribute. | non_test | copy paste attribution creates empty fields when copying pasting attributes for line features it will create blank tunnel and bridge attributes for the feature this occurs even when the copied attribution does not include a bridge or tunnel attribute | 0 |
56,214 | 6,506,931,228 | IssuesEvent | 2017-08-24 11:05:16 | LDMW/cms | https://api.github.com/repos/LDMW/cms | closed | 'Order by' section | please-test T1d | As a user, I want to be able to order my results how I choose to, so that I can prioritise the most relevant criteria for me.
- [x] Creation of 'Order by' drop down
- [x] Default is 'Most relevant'
- [x] Other option to order by 'most recommended'
- [x] 'Most recommended' is defined by the total score of likes minus dislikes
| 1.0 | 'Order by' section - As a user, I want to be able to order my results how I choose to, so that I can prioritise the most relevant criteria for me.
- [x] Creation of 'Order by' drop down
- [x] Default is 'Most relevant'
- [x] Other option to order by 'most recommended'
- [x] 'Most recommended' is defined by the total score of likes minus dislikes
| test | order by section as a user i want to be able to order my results how i choose to so that i can prioritise the most relevant criteria for me creation of order by drop down default is most relevant other option to order by most recommended most recommended is defined by the total score of likes minus dislikes | 1 |
123,277 | 17,772,200,967 | IssuesEvent | 2021-08-30 14:50:55 | kapseliboi/milsymbol | https://api.github.com/repos/kapseliboi/milsymbol | opened | CVE-2020-7598 (Medium) detected in minimist-0.0.8.tgz | security vulnerability | ## CVE-2020-7598 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>minimist-0.0.8.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz</a></p>
<p>Path to dependency file: milsymbol/package.json</p>
<p>Path to vulnerable library: milsymbol/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- eslint-5.16.0.tgz (Root Library)
- mkdirp-0.5.1.tgz
- :x: **minimist-0.0.8.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kapseliboi/milsymbol/commit/7580826c5a4fd27b6ad4825b68f2eb0cde246070">7580826c5a4fd27b6ad4825b68f2eb0cde246070</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "__proto__" payload.
<p>Publish Date: 2020-03-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598>CVE-2020-7598</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94">https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94</a></p>
<p>Release Date: 2020-03-11</p>
<p>Fix Resolution: minimist - 0.2.1,1.2.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-7598 (Medium) detected in minimist-0.0.8.tgz - ## CVE-2020-7598 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>minimist-0.0.8.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz</a></p>
<p>Path to dependency file: milsymbol/package.json</p>
<p>Path to vulnerable library: milsymbol/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- eslint-5.16.0.tgz (Root Library)
- mkdirp-0.5.1.tgz
- :x: **minimist-0.0.8.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kapseliboi/milsymbol/commit/7580826c5a4fd27b6ad4825b68f2eb0cde246070">7580826c5a4fd27b6ad4825b68f2eb0cde246070</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "__proto__" payload.
<p>Publish Date: 2020-03-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598>CVE-2020-7598</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94">https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94</a></p>
<p>Release Date: 2020-03-11</p>
<p>Fix Resolution: minimist - 0.2.1,1.2.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve medium detected in minimist tgz cve medium severity vulnerability vulnerable library minimist tgz parse argument options library home page a href path to dependency file milsymbol package json path to vulnerable library milsymbol node modules minimist package json dependency hierarchy eslint tgz root library mkdirp tgz x minimist tgz vulnerable library found in head commit a href found in base branch master vulnerability details minimist before could be tricked into adding or modifying properties of object prototype using a constructor or proto payload publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution minimist step up your open source security game with whitesource | 0 |
217,752 | 16,736,561,945 | IssuesEvent | 2021-06-11 02:51:38 | nhost/hasura-backend-plus | https://api.github.com/repos/nhost/hasura-backend-plus | closed | How do you deploy? | Priority: Low Scope: Documentation | I'd like to add documentation for how to self-host the hasura-backend-plus project through a service like AWS (what my agency uses).
I'm currently attempting to use ECS with EC2 instances but haven't figured out how to host the `./custom` directory so my private key and email templates are properly connected.
The other method I expect will work is to build my own hasura-backed-plus Docker image including my changes in the `./custom` directory and host it on AWS's ECR and deploy it through ECS Fargate. But that seems like more work to maintain over time.
I'll also be setting up CI with GitHub Actions. Once it's fully working I'll add what I did to the documentation ;)
Any suggestions on how to deploy as a Docker container and include the custom directory? | 1.0 | How do you deploy? - I'd like to add documentation for how to self-host the hasura-backend-plus project through a service like AWS (what my agency uses).
I'm currently attempting to use ECS with EC2 instances but haven't figured out how to host the `./custom` directory so my private key and email templates are properly connected.
The other method I expect will work is to build my own hasura-backed-plus Docker image including my changes in the `./custom` directory and host it on AWS's ECR and deploy it through ECS Fargate. But that seems like more work to maintain over time.
I'll also be setting up CI with GitHub Actions. Once it's fully working I'll add what I did to the documentation ;)
Any suggestions on how to deploy as a Docker container and include the custom directory? | non_test | how do you deploy i d like to add documentation for how to self host the hasura backend plus project through a service like aws what my agency uses i m currently attempting to use ecs with instances but haven t figured out how to host the custom directory so my private key and email templates are properly connected the other method i expect will work is to build my own hasura backed plus docker image including my changes in the custom directory and host it on aws s ecr and deploy it through ecs fargate but that seems like more work to maintain over time i ll also be setting up ci with github actions once it s fully working i ll add what i did to the documentation any suggestions on how to deploy as a docker container and include the custom directory | 0 |
153,891 | 12,168,021,427 | IssuesEvent | 2020-04-27 11:58:32 | WoWManiaUK/Redemption | https://api.github.com/repos/WoWManiaUK/Redemption | closed | [Talent/Spell] Titan's Grip interaction with Shield Wall / Spell Reflection on stance change | Fix - Tester Confirmed | **Links:** [Titan's Grip](https://www.wow-mania.com/armory/?spell=46917) / [Shield Wall](https://www.wow-mania.com/armory/?spell=871) / [Spell Reflection](http://www.wow-mania.com/armory?spell=23920)
**What is Happening:** Warriors with Titan's Grip talent, changing to Defensive Stance and using Shield Wall / Spell Reflect do not keep the buffs on themselves after changing the shield to 2H weapon. They just disappear.
**What Should happen:** The buffs should remain on the player until the timer ticks off.
Reference: https://youtu.be/OqCk2_QkOio (01:12 Shield Wall) / (02:54 Spell Reflection)
Spell Reflection is near end before he swaps back to Berserk Stance and change to another 2H weapon, best seen in slow-mo. | 1.0 | [Talent/Spell] Titan's Grip interaction with Shield Wall / Spell Reflection on stance change - **Links:** [Titan's Grip](https://www.wow-mania.com/armory/?spell=46917) / [Shield Wall](https://www.wow-mania.com/armory/?spell=871) / [Spell Reflection](http://www.wow-mania.com/armory?spell=23920)
**What is Happening:** Warriors with Titan's Grip talent, changing to Defensive Stance and using Shield Wall / Spell Reflect do not keep the buffs on themselves after changing the shield to 2H weapon. They just disappear.
**What Should happen:** The buffs should remain on the player until the timer ticks off.
Reference: https://youtu.be/OqCk2_QkOio (01:12 Shield Wall) / (02:54 Spell Reflection)
Spell Reflection is near end before he swaps back to Berserk Stance and change to another 2H weapon, best seen in slow-mo. | test | titan s grip interaction with shield wall spell reflection on stance change links what is happening warriors with titan s grip talent changing to defensive stance and using shield wall spell reflect do not keep the buffs on themselves after changing the shield to weapon they just disappear what should happen the buffs should remain on the player until the timer ticks off reference shield wall spell reflection spell reflection is near end before he swaps back to berserk stance and change to another weapon best seen in slow mo | 1 |
6,353 | 5,395,001,935 | IssuesEvent | 2017-02-27 06:41:10 | LiskHQ/lisk | https://api.github.com/repos/LiskHQ/lisk | opened | Improve blocks processing | enhancement hard performance | Block processing is not so efficient and logic is not perfect currently - because of that there are many possible issues and boottlenecks. Since it prevents us from expanding network and features - time to improve that.
- [ ] Refactor processing flow
- [ ] Research phase
- [ ] One entry point for block verification
- [ ] Improve block verifications/checks, low-cost ones should be done first, heavy ones - last
- [ ] Break block verification on first error (performance, we don't need to complete all other checks if one failed and block is already invalid)
- [ ] Eliminate double checks
- [ ] Split blocks module to few modules
- [ ] Review all used sequences (db, balance, etc.) and drop them where not needed
- [ ] Improve blocks propagation
- [ ] We should trust self-forged blocks and broadcast them before verification
- [ ] Every node should decide to include (or not) block on his own - so we should broadcast block immediatelly without verification (we can perform schema verification only)
- [ ] SQL performance & flexibility
- [ ] Review queries and test their performance, find slow queries/views
- [ ] Improve performance for existing queries/view (if needed)
- [ ] Review data types performance & consistency
- [ ] Use better/faster data types (if needed)
- [ ] Adjust fields in blocks-related tables - add usefull ones, remove unused (if any)
- [ ] Prepare for 'memory tables' removal
- [ ] Research phase
- [ ] Improve `transactionPool`
- [ ] Remove `undoUnconfirmedList`, `applyUnconfirmed`, `applyConfirmed`, `applyUnconfirmedIds` and possible other heavy functions, rewrite checks to use `transactionPool` directly
- [ ] If we need to modify 'memory tables' - best approach is using postgres triggers if possible
- [ ] Should be also possible to create postgres function that can be used for block insertion/deletion
- [ ] Improve dealing with rounds in context of forks and removal blocks
- [ ] Never crash node if something went wrong, all possible errors should be handled gracefully
- [ ] Improve behavior on forks
- [ ] Research phase
- [ ] Improve logging
- [ ] We should know why block verification/insertion/removal failed with every details needed to reproduce it
- [ ] Add performance counters when processing blocks/txs (block per sec, txs per sec - with few time windows)
- [ ] Compact blocks when sending over network
- [ ] Research phase
- [ ] Should be possible to decrease block size
- Remove empty/not-significant properties
- Use binary format, there are some libraries that we can use https://github.com/dcodeIO/PSON, https://github.com/mongodb/js-bson
- If we need backward-compatibility, `features` header/endpoint or similar should be developed, so we can check if node supports `compact_blocks` feature
Connected issues:
- Consistency when dealing with timestamps https://github.com/LiskHQ/lisk/issues/448
- Round arithmetic is using standard Math functions https://github.com/LiskHQ/lisk/issues/447
- Reload sometimes cause blockchain rebuild https://github.com/LiskHQ/lisk/issues/411
- Syncing from scratch randomly slows down https://github.com/LiskHQ/lisk/issues/352
- Tracking of missed blocks https://github.com/LiskHQ/lisk/issues/349
- Add information about slot to blocks https://github.com/LiskHQ/lisk/issues/348
- Networks lose stability when broadcasting transactions https://github.com/LiskHQ/lisk/issues/339
- Improve block replication https://github.com/LiskHQ/lisk/issues/333
- Node forked and didn't rolled back https://github.com/LiskHQ/lisk/issues/324
- Rewrite all database logic to follow pg-promise best practices https://github.com/LiskHQ/lisk/issues/302
- LIP001: Improving network synchronisation - decentralised blockchain snapshots https://github.com/LiskHQ/lisk/issues/235
- why mem_round was flushed twice while finishing a round https://github.com/LiskHQ/lisk/issues/216 | True | Improve blocks processing - Block processing is not so efficient and logic is not perfect currently - because of that there are many possible issues and boottlenecks. Since it prevents us from expanding network and features - time to improve that.
- [ ] Refactor processing flow
- [ ] Research phase
- [ ] One entry point for block verification
- [ ] Improve block verifications/checks, low-cost ones should be done first, heavy ones - last
- [ ] Break block verification on first error (performance, we don't need to complete all other checks if one failed and block is already invalid)
- [ ] Eliminate double checks
- [ ] Split blocks module to few modules
- [ ] Review all used sequences (db, balance, etc.) and drop them where not needed
- [ ] Improve blocks propagation
- [ ] We should trust self-forged blocks and broadcast them before verification
- [ ] Every node should decide to include (or not) block on his own - so we should broadcast block immediatelly without verification (we can perform schema verification only)
- [ ] SQL performance & flexibility
- [ ] Review queries and test their performance, find slow queries/views
- [ ] Improve performance for existing queries/view (if needed)
- [ ] Review data types performance & consistency
- [ ] Use better/faster data types (if needed)
- [ ] Adjust fields in blocks-related tables - add usefull ones, remove unused (if any)
- [ ] Prepare for 'memory tables' removal
- [ ] Research phase
- [ ] Improve `transactionPool`
- [ ] Remove `undoUnconfirmedList`, `applyUnconfirmed`, `applyConfirmed`, `applyUnconfirmedIds` and possible other heavy functions, rewrite checks to use `transactionPool` directly
- [ ] If we need to modify 'memory tables' - best approach is using postgres triggers if possible
- [ ] Should be also possible to create postgres function that can be used for block insertion/deletion
- [ ] Improve dealing with rounds in context of forks and removal blocks
- [ ] Never crash node if something went wrong, all possible errors should be handled gracefully
- [ ] Improve behavior on forks
- [ ] Research phase
- [ ] Improve logging
- [ ] We should know why block verification/insertion/removal failed with every details needed to reproduce it
- [ ] Add performance counters when processing blocks/txs (block per sec, txs per sec - with few time windows)
- [ ] Compact blocks when sending over network
- [ ] Research phase
- [ ] Should be possible to decrease block size
- Remove empty/not-significant properties
- Use binary format, there are some libraries that we can use https://github.com/dcodeIO/PSON, https://github.com/mongodb/js-bson
- If we need backward-compatibility, `features` header/endpoint or similar should be developed, so we can check if node supports `compact_blocks` feature
Connected issues:
- Consistency when dealing with timestamps https://github.com/LiskHQ/lisk/issues/448
- Round arithmetic is using standard Math functions https://github.com/LiskHQ/lisk/issues/447
- Reload sometimes cause blockchain rebuild https://github.com/LiskHQ/lisk/issues/411
- Syncing from scratch randomly slows down https://github.com/LiskHQ/lisk/issues/352
- Tracking of missed blocks https://github.com/LiskHQ/lisk/issues/349
- Add information about slot to blocks https://github.com/LiskHQ/lisk/issues/348
- Networks lose stability when broadcasting transactions https://github.com/LiskHQ/lisk/issues/339
- Improve block replication https://github.com/LiskHQ/lisk/issues/333
- Node forked and didn't rolled back https://github.com/LiskHQ/lisk/issues/324
- Rewrite all database logic to follow pg-promise best practices https://github.com/LiskHQ/lisk/issues/302
- LIP001: Improving network synchronisation - decentralised blockchain snapshots https://github.com/LiskHQ/lisk/issues/235
- why mem_round was flushed twice while finishing a round https://github.com/LiskHQ/lisk/issues/216 | non_test | improve blocks processing block processing is not so efficient and logic is not perfect currently because of that there are many possible issues and boottlenecks since it prevents us from expanding network and features time to improve that refactor processing flow research phase one entry point for block verification improve block verifications checks low cost ones should be done first heavy ones last break block verification on first error performance we don t need to complete all other checks if one failed and block is already invalid eliminate double checks split blocks module to few modules review all used sequences db balance etc and drop them where not needed improve blocks propagation we should trust self forged blocks and broadcast them before verification every node should decide to include or not block on his own so we should broadcast block immediatelly without verification we can perform schema verification only sql performance flexibility review queries and test their performance find slow queries views improve performance for existing queries view if needed review data types performance consistency use better faster data types if needed adjust fields in blocks related tables add usefull ones remove unused if any prepare for memory tables removal research phase improve transactionpool remove undounconfirmedlist applyunconfirmed applyconfirmed applyunconfirmedids and possible other heavy functions rewrite checks to use transactionpool directly if we need to modify memory tables best approach is using postgres triggers if possible should be also possible to create postgres function that can be used for block insertion deletion improve dealing with rounds in context of forks and removal blocks never crash node if something went wrong all possible errors should be handled gracefully improve behavior on forks research phase improve logging we should know why block verification insertion removal failed with every details needed to reproduce it add performance counters when processing blocks txs block per sec txs per sec with few time windows compact blocks when sending over network research phase should be possible to decrease block size remove empty not significant properties use binary format there are some libraries that we can use if we need backward compatibility features header endpoint or similar should be developed so we can check if node supports compact blocks feature connected issues consistency when dealing with timestamps round arithmetic is using standard math functions reload sometimes cause blockchain rebuild syncing from scratch randomly slows down tracking of missed blocks add information about slot to blocks networks lose stability when broadcasting transactions improve block replication node forked and didn t rolled back rewrite all database logic to follow pg promise best practices improving network synchronisation decentralised blockchain snapshots why mem round was flushed twice while finishing a round | 0 |
232,617 | 25,589,726,252 | IssuesEvent | 2022-12-01 12:05:20 | MatBenfield/news | https://api.github.com/repos/MatBenfield/news | closed | [SecurityWeek] Self-Replicating Malware Used by Chinese Cyberspies Spreads via USB Drives | SecurityWeek Stale |
**A China-linked cyberespionage group tracked as UNC4191 has been observed using self-replicating malware on USB drives to infect targets, and the technique could allow them to steal data from air-gapped systems, Google-owned Mandiant reports.**
[read more](https://www.securityweek.com/self-replicating-malware-used-chinese-cyberspies-spreads-usb-drives)
<https://www.securityweek.com/self-replicating-malware-used-chinese-cyberspies-spreads-usb-drives>
| True | [SecurityWeek] Self-Replicating Malware Used by Chinese Cyberspies Spreads via USB Drives -
**A China-linked cyberespionage group tracked as UNC4191 has been observed using self-replicating malware on USB drives to infect targets, and the technique could allow them to steal data from air-gapped systems, Google-owned Mandiant reports.**
[read more](https://www.securityweek.com/self-replicating-malware-used-chinese-cyberspies-spreads-usb-drives)
<https://www.securityweek.com/self-replicating-malware-used-chinese-cyberspies-spreads-usb-drives>
| non_test | self replicating malware used by chinese cyberspies spreads via usb drives a china linked cyberespionage group tracked as has been observed using self replicating malware on usb drives to infect targets and the technique could allow them to steal data from air gapped systems google owned mandiant reports | 0 |
824,629 | 31,164,179,463 | IssuesEvent | 2023-08-16 18:17:57 | Vexcenot/-Middle-Mann | https://api.github.com/repos/Vexcenot/-Middle-Mann | closed | TODO: Item Meter Rewrites | enhancement todo priority:low | basically what it says on the tin
basic plan: reposition and enhance meters to work well on most gamemodes + mvm (and fix #42 #49 #50 in the process)
some extras: improve the meter customizations to also work with this rewrite
for reference
<html>
<body>
<!--StartFragment-->
huditemeffectmeter.res | Charge meter for: Sandman / Wrap Assassin / Sandvich / Spy Watches / Jarate / Razorback / Cleaner's Carbine / Soldier Banners / Gas Passer
-- | --
huditemeffectmeter_cleaver.res | Charge meter for: Flying Guillotine
huditemeffectmeter_demoman.res | Counter for: Eyelander heads and AirStrike
huditemeffectmeter_engineer.res | Counter for: Frontier Justice and Manmelter (use demoman base)
huditemeffectmeter_halloweensouls.res | No longer in use
huditemeffectmeter_heavy.res | Charge meter for: Heavy rage in MvM
huditemeffectmeter_kartcharge.res | Charge meter for: Halloween Karts
huditemeffectmeter_killstreak.res | Counter for: killstreak weapons
huditemeffectmeter_organs.res | Counter for: Vita-Saw
huditemeffectmeter_particlecannon.res | Charge meter for: Cow Mangler
huditemeffectmeter_pomson.res | Charge meter for: Pomson
huditemeffectmeter_powerupbottle.res | Counter for: PowerUp Canteen in MvM
huditemeffectmeter_pyro.res | Charge meter for: Phlogistinator
huditemeffectmeter_raygun.res | Charge meter for: Righteous Bison
huditemeffectmeter_sapper.res | Charge meter for: Sapper
huditemeffectmeter_scout.res | Charge meter for: Bonk! Atomic Punch/Crit-a-Cola/Mad Milk and MvM medic shield (will be iffy)
huditemeffectmeter_sniper.res | Counter for: Bazaar Bargain (use demoman base)
huditemeffectmeter_sniperfocus.res | Charge meter for: Hitman's Heatmaker
huditemeffectmeter_sodapopper.res | Charge meter for: Sodapopper
huditemeffectmeter_spy.res | Counter for: Diamondback
huditemeffectmeter_spyknife.res | Charge for: Spy-cicle
<!--EndFragment-->
</body>
</html>
extras: engineer metal | 1.0 | TODO: Item Meter Rewrites - basically what it says on the tin
basic plan: reposition and enhance meters to work well on most gamemodes + mvm (and fix #42 #49 #50 in the process)
some extras: improve the meter customizations to also work with this rewrite
for reference
<html>
<body>
<!--StartFragment-->
huditemeffectmeter.res | Charge meter for: Sandman / Wrap Assassin / Sandvich / Spy Watches / Jarate / Razorback / Cleaner's Carbine / Soldier Banners / Gas Passer
-- | --
huditemeffectmeter_cleaver.res | Charge meter for: Flying Guillotine
huditemeffectmeter_demoman.res | Counter for: Eyelander heads and AirStrike
huditemeffectmeter_engineer.res | Counter for: Frontier Justice and Manmelter (use demoman base)
huditemeffectmeter_halloweensouls.res | No longer in use
huditemeffectmeter_heavy.res | Charge meter for: Heavy rage in MvM
huditemeffectmeter_kartcharge.res | Charge meter for: Halloween Karts
huditemeffectmeter_killstreak.res | Counter for: killstreak weapons
huditemeffectmeter_organs.res | Counter for: Vita-Saw
huditemeffectmeter_particlecannon.res | Charge meter for: Cow Mangler
huditemeffectmeter_pomson.res | Charge meter for: Pomson
huditemeffectmeter_powerupbottle.res | Counter for: PowerUp Canteen in MvM
huditemeffectmeter_pyro.res | Charge meter for: Phlogistinator
huditemeffectmeter_raygun.res | Charge meter for: Righteous Bison
huditemeffectmeter_sapper.res | Charge meter for: Sapper
huditemeffectmeter_scout.res | Charge meter for: Bonk! Atomic Punch/Crit-a-Cola/Mad Milk and MvM medic shield (will be iffy)
huditemeffectmeter_sniper.res | Counter for: Bazaar Bargain (use demoman base)
huditemeffectmeter_sniperfocus.res | Charge meter for: Hitman's Heatmaker
huditemeffectmeter_sodapopper.res | Charge meter for: Sodapopper
huditemeffectmeter_spy.res | Counter for: Diamondback
huditemeffectmeter_spyknife.res | Charge for: Spy-cicle
<!--EndFragment-->
</body>
</html>
extras: engineer metal | non_test | todo item meter rewrites basically what it says on the tin basic plan reposition and enhance meters to work well on most gamemodes mvm and fix in the process some extras improve the meter customizations to also work with this rewrite for reference huditemeffectmeter res charge meter for sandman wrap assassin sandvich spy watches jarate razorback cleaner s carbine soldier banners gas passer huditemeffectmeter cleaver res charge meter for flying guillotine huditemeffectmeter demoman res counter for eyelander heads and airstrike huditemeffectmeter engineer res counter for frontier justice and manmelter use demoman base huditemeffectmeter halloweensouls res no longer in use huditemeffectmeter heavy res charge meter for heavy rage in mvm huditemeffectmeter kartcharge res charge meter for halloween karts huditemeffectmeter killstreak res counter for killstreak weapons huditemeffectmeter organs res counter for vita saw huditemeffectmeter particlecannon res charge meter for cow mangler huditemeffectmeter pomson res charge meter for pomson huditemeffectmeter powerupbottle res counter for powerup canteen in mvm huditemeffectmeter pyro res charge meter for phlogistinator huditemeffectmeter raygun res charge meter for righteous bison huditemeffectmeter sapper res charge meter for sapper huditemeffectmeter scout res charge meter for bonk atomic punch crit a cola mad milk and mvm medic shield will be iffy huditemeffectmeter sniper res counter for bazaar bargain use demoman base huditemeffectmeter sniperfocus res charge meter for hitman s heatmaker huditemeffectmeter sodapopper res charge meter for sodapopper huditemeffectmeter spy res counter for diamondback huditemeffectmeter spyknife res charge for spy cicle extras engineer metal | 0 |
236,787 | 26,052,600,512 | IssuesEvent | 2022-12-22 20:26:30 | billmcchesney1/Hangar | https://api.github.com/repos/billmcchesney1/Hangar | opened | CVE-2022-23529 (High) detected in jsonwebtoken-8.5.1.tgz | security vulnerability | ## CVE-2022-23529 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jsonwebtoken-8.5.1.tgz</b></p></summary>
<p>JSON Web Token implementation (symmetric and asymmetric)</p>
<p>Library home page: <a href="https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-8.5.1.tgz">https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-8.5.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/jsonwebtoken/package.json</p>
<p>
Dependency Hierarchy:
- bolt-2.3.0.tgz (Root Library)
- oauth-1.2.0.tgz
- :x: **jsonwebtoken-8.5.1.tgz** (Vulnerable Library)
<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>
node-jsonwebtoken is a JsonWebToken implementation for node.js. For versions `<= 8.5.1` of `jsonwebtoken` library, if a malicious actor has the ability to modify the key retrieval parameter (referring to the `secretOrPublicKey` argument from the readme link of the `jwt.verify()` function, they can write arbitrary files on the host machine. Users are affected only if untrusted entities are allowed to modify the key retrieval parameter of the `jwt.verify()` on a host that you control. This issue has been fixed, please update to version 9.0.0.
<p>Publish Date: 2022-12-21
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23529>CVE-2022-23529</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.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: High
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-27h2-hvpr-p74q">https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-27h2-hvpr-p74q</a></p>
<p>Release Date: 2022-12-21</p>
<p>Fix Resolution: jsonwebtoken - 9.0.0</p>
</p>
</details>
<p></p>
| True | CVE-2022-23529 (High) detected in jsonwebtoken-8.5.1.tgz - ## CVE-2022-23529 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jsonwebtoken-8.5.1.tgz</b></p></summary>
<p>JSON Web Token implementation (symmetric and asymmetric)</p>
<p>Library home page: <a href="https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-8.5.1.tgz">https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-8.5.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/jsonwebtoken/package.json</p>
<p>
Dependency Hierarchy:
- bolt-2.3.0.tgz (Root Library)
- oauth-1.2.0.tgz
- :x: **jsonwebtoken-8.5.1.tgz** (Vulnerable Library)
<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>
node-jsonwebtoken is a JsonWebToken implementation for node.js. For versions `<= 8.5.1` of `jsonwebtoken` library, if a malicious actor has the ability to modify the key retrieval parameter (referring to the `secretOrPublicKey` argument from the readme link of the `jwt.verify()` function, they can write arbitrary files on the host machine. Users are affected only if untrusted entities are allowed to modify the key retrieval parameter of the `jwt.verify()` on a host that you control. This issue has been fixed, please update to version 9.0.0.
<p>Publish Date: 2022-12-21
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23529>CVE-2022-23529</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.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: High
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-27h2-hvpr-p74q">https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-27h2-hvpr-p74q</a></p>
<p>Release Date: 2022-12-21</p>
<p>Fix Resolution: jsonwebtoken - 9.0.0</p>
</p>
</details>
<p></p>
| non_test | cve high detected in jsonwebtoken tgz cve high severity vulnerability vulnerable library jsonwebtoken tgz json web token implementation symmetric and asymmetric library home page a href path to dependency file package json path to vulnerable library node modules jsonwebtoken package json dependency hierarchy bolt tgz root library oauth tgz x jsonwebtoken tgz vulnerable library found in base branch main vulnerability details node jsonwebtoken is a jsonwebtoken implementation for node js for versions of jsonwebtoken library if a malicious actor has the ability to modify the key retrieval parameter referring to the secretorpublickey argument from the readme link of the jwt verify function they can write arbitrary files on the host machine users are affected only if untrusted entities are allowed to modify the key retrieval parameter of the jwt verify on a host that you control this issue has been fixed please update to version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact low integrity impact high availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jsonwebtoken | 0 |
64,128 | 6,893,595,499 | IssuesEvent | 2017-11-23 05:16:05 | dotnet/corefx | https://api.github.com/repos/dotnet/corefx | closed | System.Diagnostics.Tests.ProcessCollectionTests.TestThreadCollectionBehavior failed in CI | area-System.Diagnostics test bug test-run-core | Failed test: System.Diagnostics.Tests.ProcessCollectionTests.TestThreadCollectionBehavior
Configuration:
osx10.12_debug
Detail: https://ci.dot.net/job/dotnet_corefx/job/master/job/osx10.12_debug/3296/testReport/System.Diagnostics.Tests/ProcessCollectionTests/TestThreadCollectionBehavior/
MESSAGE:
~~~
System.IndexOutOfRangeException : Index was outside the bounds of the array.
~~~
STACK TRACE:
~~~
at System.Diagnostics.Tests.ProcessCollectionTests.TestThreadCollectionBehavior() in /Users/dotnet-bot/j/workspace/dotnet_corefx/master/osx10.12_debug/src/System.Diagnostics.Process/tests/ProcessCollectionTests.cs:line 95
~~~
| 2.0 | System.Diagnostics.Tests.ProcessCollectionTests.TestThreadCollectionBehavior failed in CI - Failed test: System.Diagnostics.Tests.ProcessCollectionTests.TestThreadCollectionBehavior
Configuration:
osx10.12_debug
Detail: https://ci.dot.net/job/dotnet_corefx/job/master/job/osx10.12_debug/3296/testReport/System.Diagnostics.Tests/ProcessCollectionTests/TestThreadCollectionBehavior/
MESSAGE:
~~~
System.IndexOutOfRangeException : Index was outside the bounds of the array.
~~~
STACK TRACE:
~~~
at System.Diagnostics.Tests.ProcessCollectionTests.TestThreadCollectionBehavior() in /Users/dotnet-bot/j/workspace/dotnet_corefx/master/osx10.12_debug/src/System.Diagnostics.Process/tests/ProcessCollectionTests.cs:line 95
~~~
| test | system diagnostics tests processcollectiontests testthreadcollectionbehavior failed in ci failed test system diagnostics tests processcollectiontests testthreadcollectionbehavior configuration debug detail message system indexoutofrangeexception index was outside the bounds of the array stack trace at system diagnostics tests processcollectiontests testthreadcollectionbehavior in users dotnet bot j workspace dotnet corefx master debug src system diagnostics process tests processcollectiontests cs line | 1 |
3,251 | 3,098,713,435 | IssuesEvent | 2015-08-28 12:59:36 | projectatomic/atomic-reactor | https://api.github.com/repos/projectatomic/atomic-reactor | opened | squashing: provide id of base image to the tool | bug post-build plugin priority 1 | so it will squash just the built image, not multiple layers from base image | 1.0 | squashing: provide id of base image to the tool - so it will squash just the built image, not multiple layers from base image | non_test | squashing provide id of base image to the tool so it will squash just the built image not multiple layers from base image | 0 |
176,329 | 13,636,188,818 | IssuesEvent | 2020-09-25 05:09:46 | rancher/dashboard | https://api.github.com/repos/rancher/dashboard | closed | Custom Backup-restore-operator Deployment Page | [zube]: To Test area/backup-restore-operator priority/0 status/blocker | Chart.yaml Annotation:
catalog.cattle.io/ui-component: backup-restore-operator
What fields are required/needed for chart deployment?
Label Name | Description | k8s YAML | Input | Default
-- | ---- | -- | -- | --
Operator Image | "Provide the name of the backup-restore-operator image" | image.respository | String | rancher/backup-restore-operator |
Operator Image Tag | "Provide a tag for the backup-restore-operator image" | image.tag | String | "" |
Configure storage location for all backups created by the operator
**NOTE** Either S3 or PV can be configured
### S3
Label Name | Description | k8s YAML | Input | Default
-- | -- | -- | -- | --
S3 | Configure s3/minio as a backup storage location by setting `enabled` and provide any necessary fields | s3 | - |
Enabled | This flag determines if s3 is configured | s3.enabled | Boolean | false
S3 Credentials secret | Provide the name of the secret containing s3/minio creds. This secret must be created in the namespace in which chart is installed, and can be created after the chart is installed | s3.credentialSecretName | String | ""
Bucket | Provide the name of the bucket to store backups in | s3.bucket | String | ""
Region | Provide region if applicable | s3.region | String | ""
Folder | Provide base folder if applicable | s3.folder | String | ""
Endpoint | Provide endpoint | s3.endpoint | String | ""
EndpointCA | Provide base64 encoded CA cert | s3.endpointCA | String/Read file | ""
Insecure TLS Skip Verify | |s3.insecureTLSSkipVerify | Boolean | false
### PV (Has two sub sections, PVC and NFS)
Label Name | Description | k8s YAML | Input | Default
-- | -- | -- | -- | --
Persistence | Configure a Persistent Volume as a backup storage location by setting `enabled` and provide any necessary fields | persistence | - |
Enabled | This flag determines if a Persistent Volume storage is configured | persistence.enabled | Boolean | false
Storage Class | Provide name of the StorageClass to use for creating the PVC. If set to "-", PVC will be created with an empty storageClassName which disables dynamic provisioning | persistence.storageClass
Size | Provide the storage request/size of PV | persistence.size | String | 2Gi
| 1.0 | Custom Backup-restore-operator Deployment Page - Chart.yaml Annotation:
catalog.cattle.io/ui-component: backup-restore-operator
What fields are required/needed for chart deployment?
Label Name | Description | k8s YAML | Input | Default
-- | ---- | -- | -- | --
Operator Image | "Provide the name of the backup-restore-operator image" | image.respository | String | rancher/backup-restore-operator |
Operator Image Tag | "Provide a tag for the backup-restore-operator image" | image.tag | String | "" |
Configure storage location for all backups created by the operator
**NOTE** Either S3 or PV can be configured
### S3
Label Name | Description | k8s YAML | Input | Default
-- | -- | -- | -- | --
S3 | Configure s3/minio as a backup storage location by setting `enabled` and provide any necessary fields | s3 | - |
Enabled | This flag determines if s3 is configured | s3.enabled | Boolean | false
S3 Credentials secret | Provide the name of the secret containing s3/minio creds. This secret must be created in the namespace in which chart is installed, and can be created after the chart is installed | s3.credentialSecretName | String | ""
Bucket | Provide the name of the bucket to store backups in | s3.bucket | String | ""
Region | Provide region if applicable | s3.region | String | ""
Folder | Provide base folder if applicable | s3.folder | String | ""
Endpoint | Provide endpoint | s3.endpoint | String | ""
EndpointCA | Provide base64 encoded CA cert | s3.endpointCA | String/Read file | ""
Insecure TLS Skip Verify | |s3.insecureTLSSkipVerify | Boolean | false
### PV (Has two sub sections, PVC and NFS)
Label Name | Description | k8s YAML | Input | Default
-- | -- | -- | -- | --
Persistence | Configure a Persistent Volume as a backup storage location by setting `enabled` and provide any necessary fields | persistence | - |
Enabled | This flag determines if a Persistent Volume storage is configured | persistence.enabled | Boolean | false
Storage Class | Provide name of the StorageClass to use for creating the PVC. If set to "-", PVC will be created with an empty storageClassName which disables dynamic provisioning | persistence.storageClass
Size | Provide the storage request/size of PV | persistence.size | String | 2Gi
| test | custom backup restore operator deployment page chart yaml annotation catalog cattle io ui component backup restore operator what fields are required needed for chart deployment label name description yaml input default operator image provide the name of the backup restore operator image image respository string rancher backup restore operator operator image tag provide a tag for the backup restore operator image image tag string configure storage location for all backups created by the operator note either or pv can be configured label name description yaml input default configure minio as a backup storage location by setting enabled and provide any necessary fields enabled this flag determines if is configured enabled boolean false credentials secret provide the name of the secret containing minio creds this secret must be created in the namespace in which chart is installed and can be created after the chart is installed credentialsecretname string bucket provide the name of the bucket to store backups in bucket string region provide region if applicable region string folder provide base folder if applicable folder string endpoint provide endpoint endpoint string endpointca provide encoded ca cert endpointca string read file insecure tls skip verify insecuretlsskipverify boolean false pv has two sub sections pvc and nfs label name description yaml input default persistence configure a persistent volume as a backup storage location by setting enabled and provide any necessary fields persistence enabled this flag determines if a persistent volume storage is configured persistence enabled boolean false storage class provide name of the storageclass to use for creating the pvc if set to pvc will be created with an empty storageclassname which disables dynamic provisioning persistence storageclass size provide the storage request size of pv persistence size string | 1 |
171,838 | 13,250,630,265 | IssuesEvent | 2020-08-19 23:37:00 | ESCOMP/CTSM | https://api.github.com/repos/ESCOMP/CTSM | closed | ARCTIC test failing in ctsm1.0.dev107 | type: bug type: tests | ### Brief summary of bug
This test fails:
ERS_Ln9.ne0ARCTICne30x4_ne0ARCTICne30x4_mt12.IHistClm50Sp.cheyenne_intel.clm-clm50cam6LndTuningMode_1979Start
### General bug information
**CTSM version you are using:** ctsm1.0.dev107
**Does this bug cause significantly incorrect results in the model's science?** No
**Configurations affected:** ERS sub day test with CISM
### Details of bug
CISM can't run a sub-day restart test.
| 1.0 | ARCTIC test failing in ctsm1.0.dev107 - ### Brief summary of bug
This test fails:
ERS_Ln9.ne0ARCTICne30x4_ne0ARCTICne30x4_mt12.IHistClm50Sp.cheyenne_intel.clm-clm50cam6LndTuningMode_1979Start
### General bug information
**CTSM version you are using:** ctsm1.0.dev107
**Does this bug cause significantly incorrect results in the model's science?** No
**Configurations affected:** ERS sub day test with CISM
### Details of bug
CISM can't run a sub-day restart test.
| test | arctic test failing in brief summary of bug this test fails ers cheyenne intel clm general bug information ctsm version you are using does this bug cause significantly incorrect results in the model s science no configurations affected ers sub day test with cism details of bug cism can t run a sub day restart test | 1 |
113,076 | 9,621,102,025 | IssuesEvent | 2019-05-14 09:50:22 | stan-dev/math | https://api.github.com/repos/stan-dev/math | opened | Randomly failing test in matrix_exp_pade_test | bug testing | ## Description
After the last PR merge `develop` failed on Jenkins on this [test](https://github.com/stan-dev/math/blob/develop/test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp#L95) in matrix_exp_pade_test. I manually restarted the Jenkins tests and it passed. The PR that was merged was a renaming PR in the Stan Math OpenCL codebase.
It seemed an unrelated PR but you can never really know so I modified the test to repeat this test for 320 times and went back to an old commit in develop https://github.com/stan-dev/math/commits/6bb33cfa No particular reason I chose this one, just went back on the git log and picked one.
```cpp
void do_test(){
using Eigen::Dynamic;
using Eigen::Matrix;
using stan::math::matrix_v;
using stan::math::var;
int size = 25;
std::random_device rd;
std::mt19937 mt(rd());
// Randomly construct input matrix
Matrix<double, Dynamic, Dynamic> S = Eigen::MatrixXd::Identity(size, size),
I = Eigen::MatrixXd::Identity(size, size);
int col1, col2;
for (int i = 0; i < 5 * size; i++) {
col1 = rd() % size;
col2 = rd() % size;
while (col1 == col2)
col2 = rd() % size;
S.col(col1) += S.col(col2) * std::pow(-1, rd());
}
Matrix<double, Dynamic, Dynamic> S_inv = stan::math::mdivide_right(I, S);
Matrix<double, Dynamic, Dynamic> diag_elements(1, size);
diag_elements.setRandom();
// Compute matrix exponential (analytically and using function)
stan::math::start_nested();
matrix_v diag_elements_var = diag_elements.cast<var>();
matrix_v A
= S.cast<var>() * diag_elements_var.asDiagonal() * S_inv.cast<var>();
matrix_v expm_A = stan::math::matrix_exp_pade(A);
Matrix<double, Dynamic, Dynamic> exp_diag_elements
= stan::math::exp(diag_elements);
Matrix<double, Dynamic, Dynamic> exp_A
= S * exp_diag_elements.asDiagonal() * S_inv;
double rel_err = 1e-10
* std::max(exp_A.cwiseAbs().maxCoeff(),
expm_A.cwiseAbs().maxCoeff().val());
// Test values
for (int i = 0; i < size; i++)
for (int j = 0; j < size; j++)
EXPECT_NEAR(exp_A(i, j), expm_A(i, j).val(), rel_err);
// Test adjoints
for (int i = 0; i < size; i++) {
for (int j = 0; j < size; j++) {
if (i > 0 || j > 0)
stan::math::set_zero_all_adjoints_nested();
grad(expm_A(i, j).vi_);
std::vector<double> g_abs(size);
for (int k = 0; k < size; k++)
g_abs[k] = std::abs(diag_elements_var(k).adj());
Matrix<double, Dynamic, Dynamic> dA(size, size), dA_exp(size, size);
for (int k = 0; k < size; k++) {
dA.setZero();
dA(k, k) = exp(diag_elements(k));
dA_exp = S * dA * S_inv;
rel_err = std::max(dA_exp.cwiseAbs().maxCoeff(), stan::math::max(g_abs))
* 1e-10;
EXPECT_NEAR(dA_exp(i, j), diag_elements_var(k).adj(), rel_err);
}
}
}
}
TEST(MathMatrix, matrix_exp_25x25_1) {
do_test();
}
TEST(MathMatrix, matrix_exp_25x25_2) {
do_test();
}
// .. and so on
```
1 of the 320 repeats of the same tests failed with this error message:
```
[ RUN ] MathMatrix.matrix_exp_25x25_1_43
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.0948728146331632e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 16.233583831312952,
diag_elements_var(k).adj() evaluates to 16.23358384226168, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.2407681992954167e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -16.233583831312941,
diag_elements_var(k).adj() evaluates to -16.233583843720623, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.5544677545165086e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 6.3130603788439634,
diag_elements_var(k).adj() evaluates to 6.3130603632992859, and
rel_err evaluates to 1.0064620200060062e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.7232567373071106e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 8.1167919156564761,
diag_elements_var(k).adj() evaluates to 8.1167919328890434, and
rel_err evaluates to 1.0838821758652955e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 2.1192293253591288e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -4.5093288420313948,
diag_elements_var(k).adj() evaluates to -4.5093288208391016, and
rel_err evaluates to 1.1613023307870846e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.2901507417950597e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -15.383280815786479,
diag_elements_var(k).adj() evaluates to -15.383280828687987, and
rel_err evaluates to 1.0838821759640349e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 2.2139580835300876e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -8.1167919156564707,
diag_elements_var(k).adj() evaluates to -8.1167919377960516, and
rel_err evaluates to 1.0838821759640349e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1298270763404616e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -6.1854337194179561,
diag_elements_var(k).adj() evaluates to -6.1854337307162268, and
rel_err evaluates to 1.0838821759640349e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1101725760909176e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -9.0186576840628945,
diag_elements_var(k).adj() evaluates to -9.0186576951646202, and
rel_err evaluates to 9.2904186493362664e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.0286100859957514e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -27.055973052187937,
diag_elements_var(k).adj() evaluates to -27.055973062474038, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.944448158042178e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -27.055973052188389,
diag_elements_var(k).adj() evaluates to -27.055973032743907, and
rel_err evaluates to 1.5484031076695103e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 3.2325161214430409e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 40.583959578282347,
diag_elements_var(k).adj() evaluates to 40.583959610607508, and
rel_err evaluates to 2.1677643517422122e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.0824820151356107e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -31.565301894219814,
diag_elements_var(k).adj() evaluates to -31.565301905044635, and
rel_err evaluates to 1.0064620204045832e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.2455306119818488e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -27.055973052188389,
diag_elements_var(k).adj() evaluates to -27.055973064643695, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.5639372463738255e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 40.583959578282347,
diag_elements_var(k).adj() evaluates to 40.583959562642974, and
rel_err evaluates to 1.0838821753938328e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.598195176200079e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -15.331718062906875,
diag_elements_var(k).adj() evaluates to -15.331718078888827, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 7.5546000566362181e-09, which exceeds rel_err, where
dA_exp(i, j) evaluates to -3.8064207504112102,
diag_elements_var(k).adj() evaluates to -3.8064207579658103, and
rel_err evaluates to 6.8515573507398604e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.2318207787131996e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 7.6658590314533628,
diag_elements_var(k).adj() evaluates to 7.665859019135155, and
rel_err evaluates to 9.2904186459849822e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 2.7143023828557489e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -15.331718062906923,
diag_elements_var(k).adj() evaluates to -15.331718090049947, and
rel_err evaluates to 1.3935627976052571e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.6921646306400362e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -45.995154188719496,
diag_elements_var(k).adj() evaluates to -45.995154205641143, and
rel_err evaluates to 9.2904186493889942e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 6.0598040363402106e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -68.992731283080047,
diag_elements_var(k).adj() evaluates to -68.992731343678088, and
rel_err evaluates to 3.2516465277888346e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.041806285684288e-07, which exceeds rel_err, where
dA_exp(i, j) evaluates to 325.16465267470284,
diag_elements_var(k).adj() evaluates to 325.16465277888346, and
rel_err evaluates to 7.5678201902266853e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 4.0912667031989258e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -45.995154188720264,
diag_elements_var(k).adj() evaluates to -45.995154229632931, and
rel_err evaluates to 2.3226046626705967e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.0202370503975544e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 12.175187873484703,
diag_elements_var(k).adj() evaluates to 12.175187883687073, and
rel_err evaluates to 9.8710698147014681e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.2195554788263507e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -12.175187873484715,
diag_elements_var(k).adj() evaluates to -12.17518786128916, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.0285599927328803e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -8.1167919156565169,
diag_elements_var(k).adj() evaluates to -8.116791905370917, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1459227344801093e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 6.7639932630470918,
diag_elements_var(k).adj() evaluates to 6.7639932745063192, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 2.3146114358496561e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 10.822389220875394,
diag_elements_var(k).adj() evaluates to 10.822389244021508, and
rel_err evaluates to 1.7032434191861717e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 3.3876009553068798e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -27.055973052188389,
diag_elements_var(k).adj() evaluates to -27.055973086064398, and
rel_err evaluates to 1.5484031084777054e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 3.0645779247606697e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 22.54664421015697,
diag_elements_var(k).adj() evaluates to 22.54664417951119, and
rel_err evaluates to 2.3226046614067266e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.7586778255918034e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -36.525563620454143,
diag_elements_var(k).adj() evaluates to -36.525563638040921, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 9.6794146031697892e-09, which exceeds rel_err, where
dA_exp(i, j) evaluates to -6.1854337194179685,
diag_elements_var(k).adj() evaluates to -6.1854337290973831, and
rel_err evaluates to 8.1291163199766469e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.0768207658884421e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 20.291979789141276,
diag_elements_var(k).adj() evaluates to 20.291979799909484, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.228774948458522e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 36.525563620454115,
diag_elements_var(k).adj() evaluates to 36.525563632741864, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1315322900884439e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 4.058395957828238,
diag_elements_var(k).adj() evaluates to 4.0583959691435609, and
rel_err evaluates to 1.0838821757946313e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.0362007252240346e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -1.3527986526094304,
diag_elements_var(k).adj() evaluates to -1.3527986629714377, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.202325661253667e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -2.2546644210156974,
diag_elements_var(k).adj() evaluates to -2.254664433038954, and
rel_err evaluates to 1.1613023311380983e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1744493377818799e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -4.0583959578282354,
diag_elements_var(k).adj() evaluates to -4.0583959695727287, and
rel_err evaluates to 1.0838821758194707e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.0219626034313478e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 25.252241515375854,
diag_elements_var(k).adj() evaluates to 25.25224152559548, and
rel_err evaluates to 1.006462020331628e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1292748069990921e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 32.467167662625904,
diag_elements_var(k).adj() evaluates to 32.467167673918652, and
rel_err evaluates to 1.0838821756659423e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1999560456388281e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -32.467167662625883,
diag_elements_var(k).adj() evaluates to -32.467167674625443, and
rel_err evaluates to 1.0838821757270261e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.5601685277033539e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -10.822389220875394,
diag_elements_var(k).adj() evaluates to -10.822389236477079, and
rel_err evaluates to 1.490337991760937e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 9.6624790391075521e-09, which exceeds rel_err, where
dA_exp(i, j) evaluates to 1.8037315368125559,
diag_elements_var(k).adj() evaluates to 1.803731546475035, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.5050801493998733e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 21.644778441750788,
diag_elements_var(k).adj() evaluates to 21.644778426699986, and
rel_err evaluates to 1.490337991326735e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.2504028035209558e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 21.644778441750351,
diag_elements_var(k).adj() evaluates to 21.644778454254379, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 2.114898478566829e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -30.766561631572763,
diag_elements_var(k).adj() evaluates to -30.766561652721748, and
rel_err evaluates to 2.0322790798395047e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 2.6739538583342437e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -18.037315368125579,
diag_elements_var(k).adj() evaluates to -18.037315394865118, and
rel_err evaluates to 2.0322790798395047e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 2.0865368099975967e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 15.782650947109882,
diag_elements_var(k).adj() evaluates to 15.782650926244514, and
rel_err evaluates to 1.1613023306710136e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.016763917505159e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 19.84104690493831,
diag_elements_var(k).adj() evaluates to 19.841046915105949, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1298688207261876e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -16.665220883768363,
diag_elements_var(k).adj() evaluates to -16.665220895067051, and
rel_err evaluates to 9.9991325302611487e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.2936393351791698e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -1.7402109814158124e-13,
diag_elements_var(k).adj() evaluates to -1.293656737288984e-08, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 9.5133412258974204e-09, which exceeds rel_err, where
dA_exp(i, j) evaluates to -8.5644466884246828,
diag_elements_var(k).adj() evaluates to -8.564446697938024, and
rel_err evaluates to 8.9033178742021168e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 4.9536247104242648e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 41.663052209421998,
diag_elements_var(k).adj() evaluates to 41.663052159885751, and
rel_err evaluates to 4.8968248277391013e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 5.8023623239478184e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 59.523140714814666,
diag_elements_var(k).adj() evaluates to 59.523140656791043, and
rel_err evaluates to 4.8968248277391013e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.2311329555814154e-07, which exceeds rel_err, where
dA_exp(i, j) evaluates to -489.68248289702342,
diag_elements_var(k).adj() evaluates to -489.68248277391012, and
rel_err evaluates to 7.5678201902266853e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.561290829954487e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 16.665220883768267,
diag_elements_var(k).adj() evaluates to 16.665220868155359, and
rel_err evaluates to 9.9991325302611487e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 3.3021670731159247e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -59.523140714813543,
diag_elements_var(k).adj() evaluates to -59.523140747835214, and
rel_err evaluates to 8.9284711072221241e-09.
....
[ FAILED ] MathMatrix.matrix_exp_25x25_1_43 (1464 ms)
```
On the second run of these 320 tests, a different error message:
```
[ RUN ] MathMatrix.matrix_exp_25x25_3_14
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1636963392902544e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 55.469370008224381,
diag_elements_var(k).adj() evaluates to 55.469370019861344, and
rel_err evaluates to 1.081668887919168e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 2.0092898012080695e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 95.090348585527522,
diag_elements_var(k).adj() evaluates to 95.09034860562042, and
rel_err evaluates to 1.9470039982888374e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.9812773643934634e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -95.090348585527522,
diag_elements_var(k).adj() evaluates to -95.090348605340296, and
rel_err evaluates to 1.4061695543450561e-08.
[ FAILED ] MathMatrix.matrix_exp_25x25_3_14 (1505 ms)
```
## Example
To repeat run this test a few times (it will probably fail in the first run):
https://gist.github.com/rok-cesnovar/0ea7a3e82737580a07a4153b73a5460a
## Expected Output
This should not fail.
#### Current Version:
v2.19.1
| 1.0 | Randomly failing test in matrix_exp_pade_test - ## Description
After the last PR merge `develop` failed on Jenkins on this [test](https://github.com/stan-dev/math/blob/develop/test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp#L95) in matrix_exp_pade_test. I manually restarted the Jenkins tests and it passed. The PR that was merged was a renaming PR in the Stan Math OpenCL codebase.
It seemed an unrelated PR but you can never really know so I modified the test to repeat this test for 320 times and went back to an old commit in develop https://github.com/stan-dev/math/commits/6bb33cfa No particular reason I chose this one, just went back on the git log and picked one.
```cpp
void do_test(){
using Eigen::Dynamic;
using Eigen::Matrix;
using stan::math::matrix_v;
using stan::math::var;
int size = 25;
std::random_device rd;
std::mt19937 mt(rd());
// Randomly construct input matrix
Matrix<double, Dynamic, Dynamic> S = Eigen::MatrixXd::Identity(size, size),
I = Eigen::MatrixXd::Identity(size, size);
int col1, col2;
for (int i = 0; i < 5 * size; i++) {
col1 = rd() % size;
col2 = rd() % size;
while (col1 == col2)
col2 = rd() % size;
S.col(col1) += S.col(col2) * std::pow(-1, rd());
}
Matrix<double, Dynamic, Dynamic> S_inv = stan::math::mdivide_right(I, S);
Matrix<double, Dynamic, Dynamic> diag_elements(1, size);
diag_elements.setRandom();
// Compute matrix exponential (analytically and using function)
stan::math::start_nested();
matrix_v diag_elements_var = diag_elements.cast<var>();
matrix_v A
= S.cast<var>() * diag_elements_var.asDiagonal() * S_inv.cast<var>();
matrix_v expm_A = stan::math::matrix_exp_pade(A);
Matrix<double, Dynamic, Dynamic> exp_diag_elements
= stan::math::exp(diag_elements);
Matrix<double, Dynamic, Dynamic> exp_A
= S * exp_diag_elements.asDiagonal() * S_inv;
double rel_err = 1e-10
* std::max(exp_A.cwiseAbs().maxCoeff(),
expm_A.cwiseAbs().maxCoeff().val());
// Test values
for (int i = 0; i < size; i++)
for (int j = 0; j < size; j++)
EXPECT_NEAR(exp_A(i, j), expm_A(i, j).val(), rel_err);
// Test adjoints
for (int i = 0; i < size; i++) {
for (int j = 0; j < size; j++) {
if (i > 0 || j > 0)
stan::math::set_zero_all_adjoints_nested();
grad(expm_A(i, j).vi_);
std::vector<double> g_abs(size);
for (int k = 0; k < size; k++)
g_abs[k] = std::abs(diag_elements_var(k).adj());
Matrix<double, Dynamic, Dynamic> dA(size, size), dA_exp(size, size);
for (int k = 0; k < size; k++) {
dA.setZero();
dA(k, k) = exp(diag_elements(k));
dA_exp = S * dA * S_inv;
rel_err = std::max(dA_exp.cwiseAbs().maxCoeff(), stan::math::max(g_abs))
* 1e-10;
EXPECT_NEAR(dA_exp(i, j), diag_elements_var(k).adj(), rel_err);
}
}
}
}
TEST(MathMatrix, matrix_exp_25x25_1) {
do_test();
}
TEST(MathMatrix, matrix_exp_25x25_2) {
do_test();
}
// .. and so on
```
1 of the 320 repeats of the same tests failed with this error message:
```
[ RUN ] MathMatrix.matrix_exp_25x25_1_43
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.0948728146331632e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 16.233583831312952,
diag_elements_var(k).adj() evaluates to 16.23358384226168, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.2407681992954167e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -16.233583831312941,
diag_elements_var(k).adj() evaluates to -16.233583843720623, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.5544677545165086e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 6.3130603788439634,
diag_elements_var(k).adj() evaluates to 6.3130603632992859, and
rel_err evaluates to 1.0064620200060062e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.7232567373071106e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 8.1167919156564761,
diag_elements_var(k).adj() evaluates to 8.1167919328890434, and
rel_err evaluates to 1.0838821758652955e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 2.1192293253591288e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -4.5093288420313948,
diag_elements_var(k).adj() evaluates to -4.5093288208391016, and
rel_err evaluates to 1.1613023307870846e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.2901507417950597e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -15.383280815786479,
diag_elements_var(k).adj() evaluates to -15.383280828687987, and
rel_err evaluates to 1.0838821759640349e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 2.2139580835300876e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -8.1167919156564707,
diag_elements_var(k).adj() evaluates to -8.1167919377960516, and
rel_err evaluates to 1.0838821759640349e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1298270763404616e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -6.1854337194179561,
diag_elements_var(k).adj() evaluates to -6.1854337307162268, and
rel_err evaluates to 1.0838821759640349e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1101725760909176e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -9.0186576840628945,
diag_elements_var(k).adj() evaluates to -9.0186576951646202, and
rel_err evaluates to 9.2904186493362664e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.0286100859957514e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -27.055973052187937,
diag_elements_var(k).adj() evaluates to -27.055973062474038, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.944448158042178e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -27.055973052188389,
diag_elements_var(k).adj() evaluates to -27.055973032743907, and
rel_err evaluates to 1.5484031076695103e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 3.2325161214430409e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 40.583959578282347,
diag_elements_var(k).adj() evaluates to 40.583959610607508, and
rel_err evaluates to 2.1677643517422122e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.0824820151356107e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -31.565301894219814,
diag_elements_var(k).adj() evaluates to -31.565301905044635, and
rel_err evaluates to 1.0064620204045832e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.2455306119818488e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -27.055973052188389,
diag_elements_var(k).adj() evaluates to -27.055973064643695, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.5639372463738255e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 40.583959578282347,
diag_elements_var(k).adj() evaluates to 40.583959562642974, and
rel_err evaluates to 1.0838821753938328e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.598195176200079e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -15.331718062906875,
diag_elements_var(k).adj() evaluates to -15.331718078888827, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 7.5546000566362181e-09, which exceeds rel_err, where
dA_exp(i, j) evaluates to -3.8064207504112102,
diag_elements_var(k).adj() evaluates to -3.8064207579658103, and
rel_err evaluates to 6.8515573507398604e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.2318207787131996e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 7.6658590314533628,
diag_elements_var(k).adj() evaluates to 7.665859019135155, and
rel_err evaluates to 9.2904186459849822e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 2.7143023828557489e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -15.331718062906923,
diag_elements_var(k).adj() evaluates to -15.331718090049947, and
rel_err evaluates to 1.3935627976052571e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.6921646306400362e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -45.995154188719496,
diag_elements_var(k).adj() evaluates to -45.995154205641143, and
rel_err evaluates to 9.2904186493889942e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 6.0598040363402106e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -68.992731283080047,
diag_elements_var(k).adj() evaluates to -68.992731343678088, and
rel_err evaluates to 3.2516465277888346e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.041806285684288e-07, which exceeds rel_err, where
dA_exp(i, j) evaluates to 325.16465267470284,
diag_elements_var(k).adj() evaluates to 325.16465277888346, and
rel_err evaluates to 7.5678201902266853e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 4.0912667031989258e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -45.995154188720264,
diag_elements_var(k).adj() evaluates to -45.995154229632931, and
rel_err evaluates to 2.3226046626705967e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.0202370503975544e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 12.175187873484703,
diag_elements_var(k).adj() evaluates to 12.175187883687073, and
rel_err evaluates to 9.8710698147014681e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.2195554788263507e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -12.175187873484715,
diag_elements_var(k).adj() evaluates to -12.17518786128916, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.0285599927328803e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -8.1167919156565169,
diag_elements_var(k).adj() evaluates to -8.116791905370917, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1459227344801093e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 6.7639932630470918,
diag_elements_var(k).adj() evaluates to 6.7639932745063192, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 2.3146114358496561e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 10.822389220875394,
diag_elements_var(k).adj() evaluates to 10.822389244021508, and
rel_err evaluates to 1.7032434191861717e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 3.3876009553068798e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -27.055973052188389,
diag_elements_var(k).adj() evaluates to -27.055973086064398, and
rel_err evaluates to 1.5484031084777054e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 3.0645779247606697e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 22.54664421015697,
diag_elements_var(k).adj() evaluates to 22.54664417951119, and
rel_err evaluates to 2.3226046614067266e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.7586778255918034e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -36.525563620454143,
diag_elements_var(k).adj() evaluates to -36.525563638040921, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 9.6794146031697892e-09, which exceeds rel_err, where
dA_exp(i, j) evaluates to -6.1854337194179685,
diag_elements_var(k).adj() evaluates to -6.1854337290973831, and
rel_err evaluates to 8.1291163199766469e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.0768207658884421e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 20.291979789141276,
diag_elements_var(k).adj() evaluates to 20.291979799909484, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.228774948458522e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 36.525563620454115,
diag_elements_var(k).adj() evaluates to 36.525563632741864, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1315322900884439e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 4.058395957828238,
diag_elements_var(k).adj() evaluates to 4.0583959691435609, and
rel_err evaluates to 1.0838821757946313e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.0362007252240346e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -1.3527986526094304,
diag_elements_var(k).adj() evaluates to -1.3527986629714377, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.202325661253667e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -2.2546644210156974,
diag_elements_var(k).adj() evaluates to -2.254664433038954, and
rel_err evaluates to 1.1613023311380983e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1744493377818799e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -4.0583959578282354,
diag_elements_var(k).adj() evaluates to -4.0583959695727287, and
rel_err evaluates to 1.0838821758194707e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.0219626034313478e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 25.252241515375854,
diag_elements_var(k).adj() evaluates to 25.25224152559548, and
rel_err evaluates to 1.006462020331628e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1292748069990921e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 32.467167662625904,
diag_elements_var(k).adj() evaluates to 32.467167673918652, and
rel_err evaluates to 1.0838821756659423e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1999560456388281e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -32.467167662625883,
diag_elements_var(k).adj() evaluates to -32.467167674625443, and
rel_err evaluates to 1.0838821757270261e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.5601685277033539e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -10.822389220875394,
diag_elements_var(k).adj() evaluates to -10.822389236477079, and
rel_err evaluates to 1.490337991760937e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 9.6624790391075521e-09, which exceeds rel_err, where
dA_exp(i, j) evaluates to 1.8037315368125559,
diag_elements_var(k).adj() evaluates to 1.803731546475035, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.5050801493998733e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 21.644778441750788,
diag_elements_var(k).adj() evaluates to 21.644778426699986, and
rel_err evaluates to 1.490337991326735e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.2504028035209558e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 21.644778441750351,
diag_elements_var(k).adj() evaluates to 21.644778454254379, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 2.114898478566829e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -30.766561631572763,
diag_elements_var(k).adj() evaluates to -30.766561652721748, and
rel_err evaluates to 2.0322790798395047e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 2.6739538583342437e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -18.037315368125579,
diag_elements_var(k).adj() evaluates to -18.037315394865118, and
rel_err evaluates to 2.0322790798395047e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 2.0865368099975967e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 15.782650947109882,
diag_elements_var(k).adj() evaluates to 15.782650926244514, and
rel_err evaluates to 1.1613023306710136e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.016763917505159e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 19.84104690493831,
diag_elements_var(k).adj() evaluates to 19.841046915105949, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1298688207261876e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -16.665220883768363,
diag_elements_var(k).adj() evaluates to -16.665220895067051, and
rel_err evaluates to 9.9991325302611487e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.2936393351791698e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -1.7402109814158124e-13,
diag_elements_var(k).adj() evaluates to -1.293656737288984e-08, and
rel_err evaluates to 8.9284711072221241e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 9.5133412258974204e-09, which exceeds rel_err, where
dA_exp(i, j) evaluates to -8.5644466884246828,
diag_elements_var(k).adj() evaluates to -8.564446697938024, and
rel_err evaluates to 8.9033178742021168e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 4.9536247104242648e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 41.663052209421998,
diag_elements_var(k).adj() evaluates to 41.663052159885751, and
rel_err evaluates to 4.8968248277391013e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 5.8023623239478184e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 59.523140714814666,
diag_elements_var(k).adj() evaluates to 59.523140656791043, and
rel_err evaluates to 4.8968248277391013e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.2311329555814154e-07, which exceeds rel_err, where
dA_exp(i, j) evaluates to -489.68248289702342,
diag_elements_var(k).adj() evaluates to -489.68248277391012, and
rel_err evaluates to 7.5678201902266853e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.561290829954487e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 16.665220883768267,
diag_elements_var(k).adj() evaluates to 16.665220868155359, and
rel_err evaluates to 9.9991325302611487e-09.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 3.3021670731159247e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -59.523140714813543,
diag_elements_var(k).adj() evaluates to -59.523140747835214, and
rel_err evaluates to 8.9284711072221241e-09.
....
[ FAILED ] MathMatrix.matrix_exp_25x25_1_43 (1464 ms)
```
On the second run of these 320 tests, a different error message:
```
[ RUN ] MathMatrix.matrix_exp_25x25_3_14
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.1636963392902544e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 55.469370008224381,
diag_elements_var(k).adj() evaluates to 55.469370019861344, and
rel_err evaluates to 1.081668887919168e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 2.0092898012080695e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to 95.090348585527522,
diag_elements_var(k).adj() evaluates to 95.09034860562042, and
rel_err evaluates to 1.9470039982888374e-08.
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:158: Failure
The difference between dA_exp(i, j) and diag_elements_var(k).adj() is 1.9812773643934634e-08, which exceeds rel_err, where
dA_exp(i, j) evaluates to -95.090348585527522,
diag_elements_var(k).adj() evaluates to -95.090348605340296, and
rel_err evaluates to 1.4061695543450561e-08.
[ FAILED ] MathMatrix.matrix_exp_25x25_3_14 (1505 ms)
```
## Example
To repeat run this test a few times (it will probably fail in the first run):
https://gist.github.com/rok-cesnovar/0ea7a3e82737580a07a4153b73a5460a
## Expected Output
This should not fail.
#### Current Version:
v2.19.1
| test | randomly failing test in matrix exp pade test description after the last pr merge develop failed on jenkins on this in matrix exp pade test i manually restarted the jenkins tests and it passed the pr that was merged was a renaming pr in the stan math opencl codebase it seemed an unrelated pr but you can never really know so i modified the test to repeat this test for times and went back to an old commit in develop no particular reason i chose this one just went back on the git log and picked one cpp void do test using eigen dynamic using eigen matrix using stan math matrix v using stan math var int size std random device rd std mt rd randomly construct input matrix matrix s eigen matrixxd identity size size i eigen matrixxd identity size size int for int i i size i rd size rd size while rd size s col s col std pow rd matrix s inv stan math mdivide right i s matrix diag elements size diag elements setrandom compute matrix exponential analytically and using function stan math start nested matrix v diag elements var diag elements cast matrix v a s cast diag elements var asdiagonal s inv cast matrix v expm a stan math matrix exp pade a matrix exp diag elements stan math exp diag elements matrix exp a s exp diag elements asdiagonal s inv double rel err std max exp a cwiseabs maxcoeff expm a cwiseabs maxcoeff val test values for int i i size i for int j j size j expect near exp a i j expm a i j val rel err test adjoints for int i i size i for int j j size j if i j stan math set zero all adjoints nested grad expm a i j vi std vector g abs size for int k k size k g abs std abs diag elements var k adj matrix da size size da exp size size for int k k size k da setzero da k k exp diag elements k da exp s da s inv rel err std max da exp cwiseabs maxcoeff stan math max g abs expect near da exp i j diag elements var k adj rel err test mathmatrix matrix exp do test test mathmatrix matrix exp do test and so on of the repeats of the same tests failed with this error message mathmatrix matrix exp test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to mathmatrix matrix exp ms on the second run of these tests a different error message mathmatrix matrix exp test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to test unit math rev mat fun matrix exp pade test cpp failure the difference between da exp i j and diag elements var k adj is which exceeds rel err where da exp i j evaluates to diag elements var k adj evaluates to and rel err evaluates to mathmatrix matrix exp ms example to repeat run this test a few times it will probably fail in the first run expected output this should not fail current version | 1 |
374,095 | 26,099,080,637 | IssuesEvent | 2022-12-27 03:12:48 | tinkerbell/tink | https://api.github.com/repos/tinkerbell/tink | closed | Document how to run Tinkerbell in production | kind/documentation priority/backlog | Can you please provide guidance on how to securely run a tinkbell installation?
For example:
* Should all machines have a dedicated NIC for DHCP? VLAN?
* Should all machines be configured to Secure Boot?
* Well, I don't secure boot described anywhere, so I guess this is not yet supported.
* Should all machines be configured to secure boot from an https .ipxe endpoint?
* Should a TPM be required? Will this support remote attestation of some kind?
* Should we configure the underline networking infrastructure to disable DHCP packets from non DHCP servers?
* `setup.sh` seems nice for development purposes, but for production, we should probably use k8s? Other orchestrator?
* What about HA/DR?
* Etc.
| 1.0 | Document how to run Tinkerbell in production - Can you please provide guidance on how to securely run a tinkbell installation?
For example:
* Should all machines have a dedicated NIC for DHCP? VLAN?
* Should all machines be configured to Secure Boot?
* Well, I don't secure boot described anywhere, so I guess this is not yet supported.
* Should all machines be configured to secure boot from an https .ipxe endpoint?
* Should a TPM be required? Will this support remote attestation of some kind?
* Should we configure the underline networking infrastructure to disable DHCP packets from non DHCP servers?
* `setup.sh` seems nice for development purposes, but for production, we should probably use k8s? Other orchestrator?
* What about HA/DR?
* Etc.
| non_test | document how to run tinkerbell in production can you please provide guidance on how to securely run a tinkbell installation for example should all machines have a dedicated nic for dhcp vlan should all machines be configured to secure boot well i don t secure boot described anywhere so i guess this is not yet supported should all machines be configured to secure boot from an https ipxe endpoint should a tpm be required will this support remote attestation of some kind should we configure the underline networking infrastructure to disable dhcp packets from non dhcp servers setup sh seems nice for development purposes but for production we should probably use other orchestrator what about ha dr etc | 0 |
158,922 | 12,438,796,835 | IssuesEvent | 2020-05-26 09:01:55 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | roachtest: acceptance/many-splits failed | C-test-failure O-roachtest O-robot branch-release-20.1 release-blocker | [(roachtest).acceptance/many-splits failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=1967633&tab=buildLog) on [release-20.1@77dca29ecaf770ed52776c66d5ebdf65cd4dd253](https://github.com/cockroachdb/cockroach/commits/77dca29ecaf770ed52776c66d5ebdf65cd4dd253):
```
| | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:852
| | github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra.(*Command).Execute
| | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:800
| | main.main
| | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:1799
| | runtime.main
| | /usr/local/go/src/runtime/proc.go:203
| | runtime.goexit
| | /usr/local/go/src/runtime/asm_amd64.s:1357
| Wraps: (3) unknown cluster: teamcity-1967633-1590483511-12-n4cpu4
| |
| | Available clusters:
| | darin-1590478647-01-n21cpu8
| | glenn-ck
| | glenn-haproxy
| | teamcity-1967593-1590473552-05-n4cpu4
| | teamcity-1967593-1590473552-13-n5cpu4
| | teamcity-1967593-1590473552-18-n3cpu4
| | teamcity-1967593-1590473552-20-n4cpu16
| | teamcity-1967593-1590473552-21-n4cpu16
| | teamcity-1967593-1590473552-24-n1cpu4
| | teamcity-1967593-1590473552-25-n4cpu16
| | teamcity-1967593-1590473552-26-n10cpu4
| | teamcity-1967593-1590473552-36-n8cpu4
| | teamcity-1967593-1590473552-39-n6cpu4
| | teamcity-1967593-1590473552-40-n6cpu4
| | teamcity-1967593-1590473552-41-n6cpu4
| | teamcity-1967593-1590473552-42-n6cpu4
| | teamcity-1967593-1590473552-43-n6cpu4
| | teamcity-1967593-1590473552-44-n6cpu4
| | teamcity-1967593-1590473552-45-n6cpu4
| | teamcity-1967613-1590478346-06-n4cpu4
| | teamcity-1967613-1590478346-16-n4cpu4
| | teamcity-1967613-1590478346-18-n10cpu4
| | teamcity-1967613-1590478346-20-n3cpu4
| | teamcity-1967613-1590478346-22-n4cpu16
| | teamcity-1967613-1590478346-23-n4cpu16
| | teamcity-1967613-1590478346-25-n1cpu4
| | teamcity-1967613-1590478346-26-n4cpu16
| | teamcity-1967613-1590478346-27-n10cpu4
| | teamcity-1967613-1590478346-28-n10cpu4
| | teamcity-1967613-1590478346-31-n9cpu4
| | teamcity-1967613-1590478346-32-n9cpu4
| | teamcity-1967613-1590478346-33-n1cpu16
| | teamcity-1967613-1590478346-35-n32cpu4
| |
| | Hint: use "roachprod sync" to update the list of available clusters.
| Error types: (1) errors.Unclassified (2) *withstack.withStack (3) *errors.errorString
Wraps: (5) exit status 1
Error types: (1) *withstack.withStack (2) *safedetails.withSafeDetails (3) *errutil.withMessage (4) *main.withCommandDetails (5) *exec.ExitError
```
<details><summary>More</summary><p>
Artifacts: [/acceptance/many-splits](https://teamcity.cockroachdb.com/viewLog.html?buildId=1967633&tab=artifacts#/acceptance/many-splits)
Related:
- #48377 roachtest: acceptance/many-splits failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-provisional_202005041945_v19.1.9](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-provisional_202005041945_v19.1.9) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
- #47556 roachtest: acceptance/many-splits failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-release-19.1](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-release-19.1) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
- #47325 roachtest: acceptance/many-splits failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-master](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-master) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Aacceptance%2Fmany-splits.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
| 2.0 | roachtest: acceptance/many-splits failed - [(roachtest).acceptance/many-splits failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=1967633&tab=buildLog) on [release-20.1@77dca29ecaf770ed52776c66d5ebdf65cd4dd253](https://github.com/cockroachdb/cockroach/commits/77dca29ecaf770ed52776c66d5ebdf65cd4dd253):
```
| | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:852
| | github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra.(*Command).Execute
| | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:800
| | main.main
| | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:1799
| | runtime.main
| | /usr/local/go/src/runtime/proc.go:203
| | runtime.goexit
| | /usr/local/go/src/runtime/asm_amd64.s:1357
| Wraps: (3) unknown cluster: teamcity-1967633-1590483511-12-n4cpu4
| |
| | Available clusters:
| | darin-1590478647-01-n21cpu8
| | glenn-ck
| | glenn-haproxy
| | teamcity-1967593-1590473552-05-n4cpu4
| | teamcity-1967593-1590473552-13-n5cpu4
| | teamcity-1967593-1590473552-18-n3cpu4
| | teamcity-1967593-1590473552-20-n4cpu16
| | teamcity-1967593-1590473552-21-n4cpu16
| | teamcity-1967593-1590473552-24-n1cpu4
| | teamcity-1967593-1590473552-25-n4cpu16
| | teamcity-1967593-1590473552-26-n10cpu4
| | teamcity-1967593-1590473552-36-n8cpu4
| | teamcity-1967593-1590473552-39-n6cpu4
| | teamcity-1967593-1590473552-40-n6cpu4
| | teamcity-1967593-1590473552-41-n6cpu4
| | teamcity-1967593-1590473552-42-n6cpu4
| | teamcity-1967593-1590473552-43-n6cpu4
| | teamcity-1967593-1590473552-44-n6cpu4
| | teamcity-1967593-1590473552-45-n6cpu4
| | teamcity-1967613-1590478346-06-n4cpu4
| | teamcity-1967613-1590478346-16-n4cpu4
| | teamcity-1967613-1590478346-18-n10cpu4
| | teamcity-1967613-1590478346-20-n3cpu4
| | teamcity-1967613-1590478346-22-n4cpu16
| | teamcity-1967613-1590478346-23-n4cpu16
| | teamcity-1967613-1590478346-25-n1cpu4
| | teamcity-1967613-1590478346-26-n4cpu16
| | teamcity-1967613-1590478346-27-n10cpu4
| | teamcity-1967613-1590478346-28-n10cpu4
| | teamcity-1967613-1590478346-31-n9cpu4
| | teamcity-1967613-1590478346-32-n9cpu4
| | teamcity-1967613-1590478346-33-n1cpu16
| | teamcity-1967613-1590478346-35-n32cpu4
| |
| | Hint: use "roachprod sync" to update the list of available clusters.
| Error types: (1) errors.Unclassified (2) *withstack.withStack (3) *errors.errorString
Wraps: (5) exit status 1
Error types: (1) *withstack.withStack (2) *safedetails.withSafeDetails (3) *errutil.withMessage (4) *main.withCommandDetails (5) *exec.ExitError
```
<details><summary>More</summary><p>
Artifacts: [/acceptance/many-splits](https://teamcity.cockroachdb.com/viewLog.html?buildId=1967633&tab=artifacts#/acceptance/many-splits)
Related:
- #48377 roachtest: acceptance/many-splits failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-provisional_202005041945_v19.1.9](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-provisional_202005041945_v19.1.9) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
- #47556 roachtest: acceptance/many-splits failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-release-19.1](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-release-19.1) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
- #47325 roachtest: acceptance/many-splits failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-master](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-master) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Aacceptance%2Fmany-splits.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
| test | roachtest acceptance many splits failed on home agent work go src github com cockroachdb cockroach vendor github com cobra command go github com cockroachdb cockroach vendor github com cobra command execute home agent work go src github com cockroachdb cockroach vendor github com cobra command go main main home agent work go src github com cockroachdb cockroach pkg cmd roachprod main go runtime main usr local go src runtime proc go runtime goexit usr local go src runtime asm s wraps unknown cluster teamcity available clusters darin glenn ck glenn haproxy teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity teamcity hint use roachprod sync to update the list of available clusters error types errors unclassified withstack withstack errors errorstring wraps exit status error types withstack withstack safedetails withsafedetails errutil withmessage main withcommanddetails exec exiterror more artifacts related roachtest acceptance many splits failed roachtest acceptance many splits failed roachtest acceptance many splits failed powered by | 1 |
446,522 | 12,865,721,456 | IssuesEvent | 2020-07-10 01:17:27 | the-future-society/modern-slavery-statements-research | https://api.github.com/repos/the-future-society/modern-slavery-statements-research | opened | Develop a tool to identify company's description of ownership disclosure | Metric difficulty - Low Priority 0 enhancement | Requirements:
Given an input of statement text detect part of the text that is describing the company's ownership disclosure
The delivery should be a simple API interface where the input is either a string of text or a .txt file. The output should be a JSON or python dictionary response showing:
strings of text that most likely describe company's ownership disclosure
a confidence indicator for each returned string showing the confidence by which a returned string actually describes the company's ownership disclosure
Some examples (but not limiting) of vocabulary include:
whether its businesses, brands, and subsidairies are:
owned and managed by the reporting company
leased
managed properties
franchised properties
joint ventures
You may find more examples of how companies discuss their ownership disclosure in [Wikirate](https://wikirate.org/Walk_Free_Foundation+MSA_Ownership_Disclosure?filter%5Bproject%5D=UK+Modern+Slavery+Act+Research&filter%5Bstatus%5D=all).
| 1.0 | Develop a tool to identify company's description of ownership disclosure - Requirements:
Given an input of statement text detect part of the text that is describing the company's ownership disclosure
The delivery should be a simple API interface where the input is either a string of text or a .txt file. The output should be a JSON or python dictionary response showing:
strings of text that most likely describe company's ownership disclosure
a confidence indicator for each returned string showing the confidence by which a returned string actually describes the company's ownership disclosure
Some examples (but not limiting) of vocabulary include:
whether its businesses, brands, and subsidairies are:
owned and managed by the reporting company
leased
managed properties
franchised properties
joint ventures
You may find more examples of how companies discuss their ownership disclosure in [Wikirate](https://wikirate.org/Walk_Free_Foundation+MSA_Ownership_Disclosure?filter%5Bproject%5D=UK+Modern+Slavery+Act+Research&filter%5Bstatus%5D=all).
| non_test | develop a tool to identify company s description of ownership disclosure requirements given an input of statement text detect part of the text that is describing the company s ownership disclosure the delivery should be a simple api interface where the input is either a string of text or a txt file the output should be a json or python dictionary response showing strings of text that most likely describe company s ownership disclosure a confidence indicator for each returned string showing the confidence by which a returned string actually describes the company s ownership disclosure some examples but not limiting of vocabulary include whether its businesses brands and subsidairies are owned and managed by the reporting company leased managed properties franchised properties joint ventures you may find more examples of how companies discuss their ownership disclosure in | 0 |
255,057 | 21,897,419,423 | IssuesEvent | 2022-05-20 09:58:43 | showMeTheMoneyPrac/FE_repo | https://api.github.com/repos/showMeTheMoneyPrac/FE_repo | closed | 사이드 바 네비게이션 테스트 코드 작성 | test | ## Description
사이드 바 네비게이션이 url에 따라 동적으로 스타일 변경되는 테스트 코드 작성
## Todo
- [ ] 사이드 바 네비게이션 테스트 코드 작성
| 1.0 | 사이드 바 네비게이션 테스트 코드 작성 - ## Description
사이드 바 네비게이션이 url에 따라 동적으로 스타일 변경되는 테스트 코드 작성
## Todo
- [ ] 사이드 바 네비게이션 테스트 코드 작성
| test | 사이드 바 네비게이션 테스트 코드 작성 description 사이드 바 네비게이션이 url에 따라 동적으로 스타일 변경되는 테스트 코드 작성 todo 사이드 바 네비게이션 테스트 코드 작성 | 1 |
84,797 | 7,934,315,451 | IssuesEvent | 2018-07-08 17:44:40 | adventurerscodex/uat | https://api.github.com/repos/adventurerscodex/uat | closed | Test: Add Read Aloud Text | severity-low-priority type-test | ### Test File
test_encounters.py
### User Story from UAT Doc
As a dm, I can add read aloud text to an encounter and the data persists | 1.0 | Test: Add Read Aloud Text - ### Test File
test_encounters.py
### User Story from UAT Doc
As a dm, I can add read aloud text to an encounter and the data persists | test | test add read aloud text test file test encounters py user story from uat doc as a dm i can add read aloud text to an encounter and the data persists | 1 |
306,674 | 26,489,431,858 | IssuesEvent | 2023-01-17 21:05:57 | elastic/elasticsearch | https://api.github.com/repos/elastic/elasticsearch | opened | [CI] SearchRedStateIndexIT testClusterAllowPartialsWithRedState failing | :Search/Search >test-failure | Windows related failure.
Exception is expecting just `\n` but the test provided `\n\r`.
**Build scan:**
https://gradle-enterprise.elastic.co/s/gtcy3hdaxcw66/tests/:server:internalClusterTest/org.elasticsearch.search.basic.SearchRedStateIndexIT/testClusterAllowPartialsWithRedState
**Reproduction line:**
```
gradlew ':server:internalClusterTest' --tests "org.elasticsearch.search.basic.SearchRedStateIndexIT.testClusterAllowPartialsWithRedState" -Dtests.seed=1760636D83AE5486 -Dtests.locale=ms-MY -Dtests.timezone=Hongkong -Druntime.java=19
```
**Applicable branches:**
main, 8.6
**Reproduces locally?:**
No
**Failure history:**
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.search.basic.SearchRedStateIndexIT&tests.test=testClusterAllowPartialsWithRedState
**Failure excerpt:**
```
java.lang.AssertionError:
Expected: "org.elasticsearch.action.NoShardAvailableActionException\n"
but: was "org.elasticsearch.action.NoShardAvailableActionException\r\n"
at __randomizedtesting.SeedInfo.seed([1760636D83AE5486:2AC3A9E4B63D4FB5]:0)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
at org.junit.Assert.assertThat(Assert.java:956)
at org.junit.Assert.assertThat(Assert.java:923)
at org.elasticsearch.search.basic.SearchRedStateIndexIT.testClusterAllowPartialsWithRedState(SearchRedStateIndexIT.java:73)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.lang.reflect.Method.invoke(Method.java:578)
at com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1758)
at com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:946)
at com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:982)
at com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:996)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.tests.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:44)
at org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
at org.apache.lucene.tests.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:45)
at org.apache.lucene.tests.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
at org.apache.lucene.tests.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:390)
at com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:843)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:490)
at com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:955)
at com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:840)
at com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:891)
at com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:902)
at org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.tests.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:38)
at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.tests.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:53)
at org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
at org.apache.lucene.tests.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
at org.apache.lucene.tests.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
at org.apache.lucene.tests.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:47)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:390)
at com.carrotsearch.randomizedtesting.ThreadLeakControl.lambda$forkTimeoutingTask$0(ThreadLeakControl.java:850)
at java.lang.Thread.run(Thread.java:1589)
``` | 1.0 | [CI] SearchRedStateIndexIT testClusterAllowPartialsWithRedState failing - Windows related failure.
Exception is expecting just `\n` but the test provided `\n\r`.
**Build scan:**
https://gradle-enterprise.elastic.co/s/gtcy3hdaxcw66/tests/:server:internalClusterTest/org.elasticsearch.search.basic.SearchRedStateIndexIT/testClusterAllowPartialsWithRedState
**Reproduction line:**
```
gradlew ':server:internalClusterTest' --tests "org.elasticsearch.search.basic.SearchRedStateIndexIT.testClusterAllowPartialsWithRedState" -Dtests.seed=1760636D83AE5486 -Dtests.locale=ms-MY -Dtests.timezone=Hongkong -Druntime.java=19
```
**Applicable branches:**
main, 8.6
**Reproduces locally?:**
No
**Failure history:**
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.search.basic.SearchRedStateIndexIT&tests.test=testClusterAllowPartialsWithRedState
**Failure excerpt:**
```
java.lang.AssertionError:
Expected: "org.elasticsearch.action.NoShardAvailableActionException\n"
but: was "org.elasticsearch.action.NoShardAvailableActionException\r\n"
at __randomizedtesting.SeedInfo.seed([1760636D83AE5486:2AC3A9E4B63D4FB5]:0)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
at org.junit.Assert.assertThat(Assert.java:956)
at org.junit.Assert.assertThat(Assert.java:923)
at org.elasticsearch.search.basic.SearchRedStateIndexIT.testClusterAllowPartialsWithRedState(SearchRedStateIndexIT.java:73)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.lang.reflect.Method.invoke(Method.java:578)
at com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1758)
at com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:946)
at com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:982)
at com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:996)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.tests.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:44)
at org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
at org.apache.lucene.tests.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:45)
at org.apache.lucene.tests.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
at org.apache.lucene.tests.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:390)
at com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:843)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:490)
at com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:955)
at com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:840)
at com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:891)
at com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:902)
at org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.tests.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:38)
at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.tests.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:53)
at org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
at org.apache.lucene.tests.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
at org.apache.lucene.tests.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
at org.apache.lucene.tests.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:47)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:390)
at com.carrotsearch.randomizedtesting.ThreadLeakControl.lambda$forkTimeoutingTask$0(ThreadLeakControl.java:850)
at java.lang.Thread.run(Thread.java:1589)
``` | test | searchredstateindexit testclusterallowpartialswithredstate failing windows related failure exception is expecting just n but the test provided n r build scan reproduction line gradlew server internalclustertest tests org elasticsearch search basic searchredstateindexit testclusterallowpartialswithredstate dtests seed dtests locale ms my dtests timezone hongkong druntime java applicable branches main reproduces locally no failure history failure excerpt java lang assertionerror expected org elasticsearch action noshardavailableactionexception n but was org elasticsearch action noshardavailableactionexception r n at randomizedtesting seedinfo seed at org hamcrest matcherassert assertthat matcherassert java at org junit assert assertthat assert java at org junit assert assertthat assert java at org elasticsearch search basic searchredstateindexit testclusterallowpartialswithredstate searchredstateindexit java at jdk internal reflect directmethodhandleaccessor invoke directmethodhandleaccessor java at java lang reflect method invoke method java at com carrotsearch randomizedtesting randomizedrunner invoke randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at org apache lucene tests util testrulesetupteardownchained evaluate testrulesetupteardownchained java at org apache lucene tests util abstractbeforeafterrule evaluate abstractbeforeafterrule java at org apache lucene tests util testrulethreadandtestname evaluate testrulethreadandtestname java at org apache lucene tests util testruleignoreaftermaxfailures evaluate testruleignoreaftermaxfailures java at org apache lucene tests util testrulemarkfailure evaluate testrulemarkfailure java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at com carrotsearch randomizedtesting threadleakcontrol statementrunner run threadleakcontrol java at com carrotsearch randomizedtesting threadleakcontrol forktimeoutingtask threadleakcontrol java at com carrotsearch randomizedtesting threadleakcontrol evaluate threadleakcontrol java at com carrotsearch randomizedtesting randomizedrunner runsingletest randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at org apache lucene tests util abstractbeforeafterrule evaluate abstractbeforeafterrule java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at org apache lucene tests util testrulestoreclassname evaluate testrulestoreclassname java at com carrotsearch randomizedtesting rules noshadowingoroverridesonmethodsrule evaluate noshadowingoroverridesonmethodsrule java at com carrotsearch randomizedtesting rules noshadowingoroverridesonmethodsrule evaluate noshadowingoroverridesonmethodsrule java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at org apache lucene tests util testruleassertionsrequired evaluate testruleassertionsrequired java at org apache lucene tests util abstractbeforeafterrule evaluate abstractbeforeafterrule java at org apache lucene tests util testrulemarkfailure evaluate testrulemarkfailure java at org apache lucene tests util testruleignoreaftermaxfailures evaluate testruleignoreaftermaxfailures java at org apache lucene tests util testruleignoretestsuites evaluate testruleignoretestsuites java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at com carrotsearch randomizedtesting threadleakcontrol statementrunner run threadleakcontrol java at com carrotsearch randomizedtesting threadleakcontrol lambda forktimeoutingtask threadleakcontrol java at java lang thread run thread java | 1 |
213,948 | 24,022,895,899 | IssuesEvent | 2022-09-15 09:06:45 | sast-automation-dev/verademo-25 | https://api.github.com/repos/sast-automation-dev/verademo-25 | opened | slf4j-log4j12-1.7.7.jar: 1 vulnerabilities (highest severity is: 9.8) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>slf4j-log4j12-1.7.7.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /app/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.17/log4j-1.2.17.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-25/commit/21a2394d49cdc2b9d9416e60d24b864e04cff13c">21a2394d49cdc2b9d9416e60d24b864e04cff13c</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2019-17571](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17571) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | log4j-1.2.17.jar | Transitive | N/A | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-17571</summary>
### Vulnerable Library - <b>log4j-1.2.17.jar</b></p>
<p>Apache Log4j 1.2</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/1.2/">http://logging.apache.org/log4j/1.2/</a></p>
<p>Path to dependency file: /app/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.17/log4j-1.2.17.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.7.7.jar (Root Library)
- :x: **log4j-1.2.17.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-25/commit/21a2394d49cdc2b9d9416e60d24b864e04cff13c">21a2394d49cdc2b9d9416e60d24b864e04cff13c</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
<p>Publish Date: 2019-12-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17571>CVE-2019-17571</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-17571">https://nvd.nist.gov/vuln/detail/CVE-2019-17571</a></p>
<p>Release Date: 2019-12-20</p>
<p>Fix Resolution: log4j:log4j - 1.2.13-NODEP,1.2.17-atlassian-1,1.2.16.redhat-5;org.slf4j:nlog4j - 1.2.18</p>
</p>
<p></p>
</details> | True | slf4j-log4j12-1.7.7.jar: 1 vulnerabilities (highest severity is: 9.8) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>slf4j-log4j12-1.7.7.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /app/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.17/log4j-1.2.17.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-25/commit/21a2394d49cdc2b9d9416e60d24b864e04cff13c">21a2394d49cdc2b9d9416e60d24b864e04cff13c</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2019-17571](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17571) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | log4j-1.2.17.jar | Transitive | N/A | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-17571</summary>
### Vulnerable Library - <b>log4j-1.2.17.jar</b></p>
<p>Apache Log4j 1.2</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/1.2/">http://logging.apache.org/log4j/1.2/</a></p>
<p>Path to dependency file: /app/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.17/log4j-1.2.17.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.7.7.jar (Root Library)
- :x: **log4j-1.2.17.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-25/commit/21a2394d49cdc2b9d9416e60d24b864e04cff13c">21a2394d49cdc2b9d9416e60d24b864e04cff13c</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
<p>Publish Date: 2019-12-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17571>CVE-2019-17571</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-17571">https://nvd.nist.gov/vuln/detail/CVE-2019-17571</a></p>
<p>Release Date: 2019-12-20</p>
<p>Fix Resolution: log4j:log4j - 1.2.13-NODEP,1.2.17-atlassian-1,1.2.16.redhat-5;org.slf4j:nlog4j - 1.2.18</p>
</p>
<p></p>
</details> | non_test | jar vulnerabilities highest severity is vulnerable library jar path to dependency file app pom xml path to vulnerable library home wss scanner repository jar found in head commit a href vulnerabilities cve severity cvss dependency type fixed in remediation available high jar transitive n a details cve vulnerable library jar apache library home page a href path to dependency file app pom xml path to vulnerable library home wss scanner repository jar dependency hierarchy jar root library x jar vulnerable library found in head commit a href found in base branch master vulnerability details included in is a socketserver class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data this affects versions up to up to 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 nodep atlassian redhat org | 0 |
147,508 | 11,790,519,266 | IssuesEvent | 2020-03-17 19:07:43 | unfoldingWord/translationCore | https://api.github.com/repos/unfoldingWord/translationCore | closed | Critical errors when opening a tStudio project that has merge conflicts and one that doesn't have conflicts | QA/ElsyTested QA/KozTested QA/Pass | 2.2.0 (c65f647)
<img width="1440" alt="critical error" src="https://user-images.githubusercontent.com/8171759/74488927-4c8cbf80-4e89-11ea-8b83-775288906ff6.png">
[Thu Feb 13 2020.log.zip](https://github.com/unfoldingWord/translationCore/files/4202001/Thu.Feb.13.2020.log.zip)
To replicate:
1. Import [en-x-demo1_php_text_ulb.tstudio.zip](https://github.com/unfoldingWord/translationCore/files/4201994/en-x-demo1_php_text_ulb.tstudio.zip)
2. On Merge Conflicts screen choose the Version 1 option for both conflicts
3. Load the project in wA
Critical error screen in displayed
I'm also seeing the same failure on this project even though it does not have any merge conflicts:
[en_1th_text_reg.tstudio.zip](https://github.com/unfoldingWord/translationCore/files/4202006/en_1th_text_reg.tstudio.zip)
| 2.0 | Critical errors when opening a tStudio project that has merge conflicts and one that doesn't have conflicts - 2.2.0 (c65f647)
<img width="1440" alt="critical error" src="https://user-images.githubusercontent.com/8171759/74488927-4c8cbf80-4e89-11ea-8b83-775288906ff6.png">
[Thu Feb 13 2020.log.zip](https://github.com/unfoldingWord/translationCore/files/4202001/Thu.Feb.13.2020.log.zip)
To replicate:
1. Import [en-x-demo1_php_text_ulb.tstudio.zip](https://github.com/unfoldingWord/translationCore/files/4201994/en-x-demo1_php_text_ulb.tstudio.zip)
2. On Merge Conflicts screen choose the Version 1 option for both conflicts
3. Load the project in wA
Critical error screen in displayed
I'm also seeing the same failure on this project even though it does not have any merge conflicts:
[en_1th_text_reg.tstudio.zip](https://github.com/unfoldingWord/translationCore/files/4202006/en_1th_text_reg.tstudio.zip)
| test | critical errors when opening a tstudio project that has merge conflicts and one that doesn t have conflicts img width alt critical error src to replicate import on merge conflicts screen choose the version option for both conflicts load the project in wa critical error screen in displayed i m also seeing the same failure on this project even though it does not have any merge conflicts | 1 |
236,603 | 19,561,923,891 | IssuesEvent | 2022-01-03 17:23:08 | aws-observability/aws-otel-collector | https://api.github.com/repos/aws-observability/aws-otel-collector | closed | Most of soaking tests failing or timing out | tests-soaking | Even looking at all the [previous successful](https://github.com/aws-observability/aws-otel-collector/actions/workflows/soaking.yml?query=is%3Asuccess) soaking tests, there was never a time where all the tests passed. These need to be fixed.
Memory threshold exceeded ~Trying to remove network~
[run-soaking-test (otlp_grpc_exporter_trace_mock, soaking_linux)](https://github.com/aws-observability/aws-otel-collector/runs/4054558304?check_suite_focus=true)
```
│ validator_1 | 16:46:42.806 [main] ERROR
│ com.amazon.aoc.validators.AlarmPullingValidator - alarm
│ otel-soaking-mem-alarm-7d3d08f5833d8e05 is alarming, status is ALARM,
│ metric is [{Id: mem,MetricStat: {Metric: {Namespace:
│ AWSOtelCollector/SoakingTest,MetricName: procstat_memory_rss,Dimensions:
│ [{Name: negative_soaking,Value: false}, {Name: testing_ami,Value:
│ soaking_linux}, {Name: exe,Value: aws-otel-collector}, {Name:
│ launch_date,Value: 2021-10-30}, {Name: instance_type,Value: m5.2xlarge},
│ {Name: testcase,Value: otlp_grpc_exporter_trace_mock}, {Name:
│ InstanceId,Value: i-059b8ea9c7d581911}, {Name: process_name,Value:
│ aws-otel-collector}, {Name: commit_id,Value:
│ cc8eb315135bdfed89782ee2f1368e5445df5ed3}, {Name: data_rate,Value:
│ trace-1000}]},Period: 60,Stat: Average,},ReturnData: true,}], failing to
│ bake
```
Insufficient resources
[run-soaking-test (datadog_exporter_trace_mock, soaking_linux)](https://github.com/aws-observability/aws-otel-collector/runs/4054558489?check_suite_focus=true)
```
│ Error: Error launching source instance: InsufficientFreeAddressesInSubnet: insufficient free addresses to allocate 1 addresses in subnet subnet-036ece2ceb3d31fb1
│ status code: 400, request id: 0d037002-dfa5-42b5-b07b-c0cbfa00e892
│
│ with module.ec2_setup.module.ec2_setup.aws_instance.sidecar,
│ on ../ec2/main.tf line 88, in resource "aws_instance" "sidecar":
│ 88: resource "aws_instance" "sidecar" {
│
```
~Soaking test not pulled
[negative-soaking-pulling-1 (sapm_exporter_trace_mock, soaking_windows)](https://github.com/aws-observability/aws-otel-collector/runs/4057114797?check_suite_focus=true)~
```
Run cd testing-framework/terraform/soaking && docker-compose -f validator_docker_compose.yml up --abort-on-container-exit
/home/runner/work/_temp/0f4615fa-7da2-49aa-a26c-8869e8e449fa.sh: line 1: cd: testing-framework/terraform/soaking: No such file or directory
```
No available runners (in progress)
```
Can't find any online and idle self-hosted runner in the current repository, account/organization and enterprise that matches the required labels: 'ubuntu-test'
Waiting for a self-hosted runner to pickup this job...
```
No available runners (timed out)
```
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
``` | 1.0 | Most of soaking tests failing or timing out - Even looking at all the [previous successful](https://github.com/aws-observability/aws-otel-collector/actions/workflows/soaking.yml?query=is%3Asuccess) soaking tests, there was never a time where all the tests passed. These need to be fixed.
Memory threshold exceeded ~Trying to remove network~
[run-soaking-test (otlp_grpc_exporter_trace_mock, soaking_linux)](https://github.com/aws-observability/aws-otel-collector/runs/4054558304?check_suite_focus=true)
```
│ validator_1 | 16:46:42.806 [main] ERROR
│ com.amazon.aoc.validators.AlarmPullingValidator - alarm
│ otel-soaking-mem-alarm-7d3d08f5833d8e05 is alarming, status is ALARM,
│ metric is [{Id: mem,MetricStat: {Metric: {Namespace:
│ AWSOtelCollector/SoakingTest,MetricName: procstat_memory_rss,Dimensions:
│ [{Name: negative_soaking,Value: false}, {Name: testing_ami,Value:
│ soaking_linux}, {Name: exe,Value: aws-otel-collector}, {Name:
│ launch_date,Value: 2021-10-30}, {Name: instance_type,Value: m5.2xlarge},
│ {Name: testcase,Value: otlp_grpc_exporter_trace_mock}, {Name:
│ InstanceId,Value: i-059b8ea9c7d581911}, {Name: process_name,Value:
│ aws-otel-collector}, {Name: commit_id,Value:
│ cc8eb315135bdfed89782ee2f1368e5445df5ed3}, {Name: data_rate,Value:
│ trace-1000}]},Period: 60,Stat: Average,},ReturnData: true,}], failing to
│ bake
```
Insufficient resources
[run-soaking-test (datadog_exporter_trace_mock, soaking_linux)](https://github.com/aws-observability/aws-otel-collector/runs/4054558489?check_suite_focus=true)
```
│ Error: Error launching source instance: InsufficientFreeAddressesInSubnet: insufficient free addresses to allocate 1 addresses in subnet subnet-036ece2ceb3d31fb1
│ status code: 400, request id: 0d037002-dfa5-42b5-b07b-c0cbfa00e892
│
│ with module.ec2_setup.module.ec2_setup.aws_instance.sidecar,
│ on ../ec2/main.tf line 88, in resource "aws_instance" "sidecar":
│ 88: resource "aws_instance" "sidecar" {
│
```
~Soaking test not pulled
[negative-soaking-pulling-1 (sapm_exporter_trace_mock, soaking_windows)](https://github.com/aws-observability/aws-otel-collector/runs/4057114797?check_suite_focus=true)~
```
Run cd testing-framework/terraform/soaking && docker-compose -f validator_docker_compose.yml up --abort-on-container-exit
/home/runner/work/_temp/0f4615fa-7da2-49aa-a26c-8869e8e449fa.sh: line 1: cd: testing-framework/terraform/soaking: No such file or directory
```
No available runners (in progress)
```
Can't find any online and idle self-hosted runner in the current repository, account/organization and enterprise that matches the required labels: 'ubuntu-test'
Waiting for a self-hosted runner to pickup this job...
```
No available runners (timed out)
```
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
``` | test | most of soaking tests failing or timing out even looking at all the soaking tests there was never a time where all the tests passed these need to be fixed memory threshold exceeded trying to remove network │ validator error │ com amazon aoc validators alarmpullingvalidator alarm │ otel soaking mem alarm is alarming status is alarm │ metric is id mem metricstat metric namespace │ awsotelcollector soakingtest metricname procstat memory rss dimensions │ name negative soaking value false name testing ami value │ soaking linux name exe value aws otel collector name │ launch date value name instance type value │ name testcase value otlp grpc exporter trace mock name │ instanceid value i name process name value │ aws otel collector name commit id value │ name data rate value │ trace period stat average returndata true failing to │ bake insufficient resources │ error error launching source instance insufficientfreeaddressesinsubnet insufficient free addresses to allocate addresses in subnet subnet │ status code request id │ │ with module setup module setup aws instance sidecar │ on main tf line in resource aws instance sidecar │ resource aws instance sidecar │ soaking test not pulled run cd testing framework terraform soaking docker compose f validator docker compose yml up abort on container exit home runner work temp sh line cd testing framework terraform soaking no such file or directory no available runners in progress can t find any online and idle self hosted runner in the current repository account organization and enterprise that matches the required labels ubuntu test waiting for a self hosted runner to pickup this job no available runners timed out this request was automatically failed because there were no enabled runners online to process the request for more than days | 1 |
324,060 | 27,774,922,319 | IssuesEvent | 2023-03-16 16:35:46 | mehah/otclient | https://api.github.com/repos/mehah/otclient | closed | [Highlight] Highlight disappears on relog | Priority: Low Status: Pending Test Type: Bug | ### Priority
Low
### Area
- [ ] Data
- [X] Source
- [ ] Docker
- [ ] Other
### What happened?
# How to reproduce
1. Position your mouse anywhere on a game screen position.
2. Relog (`Ctrl+G`) **_without moving your mouse_**.
The highlight will not appear again, unless you move your mouse.
Note: I tried this with the original code of 16th March 2023 with original TFS 1.5 and protocol 12.87.
### What OS are you seeing the problem on?
Windows
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct | 1.0 | [Highlight] Highlight disappears on relog - ### Priority
Low
### Area
- [ ] Data
- [X] Source
- [ ] Docker
- [ ] Other
### What happened?
# How to reproduce
1. Position your mouse anywhere on a game screen position.
2. Relog (`Ctrl+G`) **_without moving your mouse_**.
The highlight will not appear again, unless you move your mouse.
Note: I tried this with the original code of 16th March 2023 with original TFS 1.5 and protocol 12.87.
### What OS are you seeing the problem on?
Windows
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct | test | highlight disappears on relog priority low area data source docker other what happened how to reproduce position your mouse anywhere on a game screen position relog ctrl g without moving your mouse the highlight will not appear again unless you move your mouse note i tried this with the original code of march with original tfs and protocol what os are you seeing the problem on windows code of conduct i agree to follow this project s code of conduct | 1 |
242,927 | 20,323,605,541 | IssuesEvent | 2022-02-18 02:26:58 | reach4help/covidhelphub-frontend | https://api.github.com/repos/reach4help/covidhelphub-frontend | closed | Add Cypress test | test | **What**: Start learning how to use Cypress and show that Cypress is working properly in our repo. Set up Cypress and add a Cypress test.
**Why**: We want to start adding Cypress tests so we can have end to end and integration tests in the future. Right now we are not ready to add those tests, but we would like to start learning about Cypress now.
**How**:
- Set up Cypress
- Add a simple Cypress test. This is just to show that Cypress is working, rather than to make an extensive test | 1.0 | Add Cypress test - **What**: Start learning how to use Cypress and show that Cypress is working properly in our repo. Set up Cypress and add a Cypress test.
**Why**: We want to start adding Cypress tests so we can have end to end and integration tests in the future. Right now we are not ready to add those tests, but we would like to start learning about Cypress now.
**How**:
- Set up Cypress
- Add a simple Cypress test. This is just to show that Cypress is working, rather than to make an extensive test | test | add cypress test what start learning how to use cypress and show that cypress is working properly in our repo set up cypress and add a cypress test why we want to start adding cypress tests so we can have end to end and integration tests in the future right now we are not ready to add those tests but we would like to start learning about cypress now how set up cypress add a simple cypress test this is just to show that cypress is working rather than to make an extensive test | 1 |
95,596 | 3,954,313,774 | IssuesEvent | 2016-04-29 16:31:08 | giantotter/giantotter_public | https://api.github.com/repos/giantotter/giantotter_public | closed | Otto: bot crashes on first interaction | bug priority: A ready | Since proactively messaging a new user crashes (see other bug), I tried to just begin a DM with Otto myself.
Repro:
- I joined Slack as jefforkin
- I started a DM via Slack's menus with coach_otto
- When the new DM channel opened, I (as jefforkin) typed hi.
- bot crashes with: TypeError: api_call() got multiple values for keyword argument 'channel' | 1.0 | Otto: bot crashes on first interaction - Since proactively messaging a new user crashes (see other bug), I tried to just begin a DM with Otto myself.
Repro:
- I joined Slack as jefforkin
- I started a DM via Slack's menus with coach_otto
- When the new DM channel opened, I (as jefforkin) typed hi.
- bot crashes with: TypeError: api_call() got multiple values for keyword argument 'channel' | non_test | otto bot crashes on first interaction since proactively messaging a new user crashes see other bug i tried to just begin a dm with otto myself repro i joined slack as jefforkin i started a dm via slack s menus with coach otto when the new dm channel opened i as jefforkin typed hi bot crashes with typeerror api call got multiple values for keyword argument channel | 0 |
277,244 | 24,055,660,400 | IssuesEvent | 2022-09-16 16:35:44 | gradle/gradle | https://api.github.com/repos/gradle/gradle | closed | GradleRunner should not fork a long-live daemon when `withDebug(true)` | a:bug in:test-kit stale | As reported [here](https://discuss.gradle.org/t/testkit-and-worker-api-st-when-debug-is-enabled/25490?u=dpukyle), at some point between `4.0` and `4.1`, we create worker daemon process with `KeepAliveMode.DAEMON`, which we have to force kill after the build and this results in a stacktrace printed on console.
Before `4.1`, we created child process for `GradleRunner.withDebug(true)` with the following sequence:
- [Fork a child process for the actual build](https://github.com/gradle/gradle/blob/c8143c9bcf412a2d19053b8c926c7787c1dc8087/subprojects/core/src/main/java/org/gradle/process/internal/ExecHandleRunner.java#L68).
- [`waitFor` child process to exit](https://github.com/gradle/gradle/blob/c8143c9bcf412a2d19053b8c926c7787c1dc8087/subprojects/core/src/main/java/org/gradle/process/internal/ExecHandleRunner.java#L81).
- `GradleRunner` process exits.
After `4.1`:
- [Fork a child process for the actual build](https://github.com/gradle/gradle/blob/c8143c9bcf412a2d19053b8c926c7787c1dc8087/subprojects/core/src/main/java/org/gradle/process/internal/ExecHandleRunner.java#L68).
- This child process is long-live daemon so it never exits.
- `GradleRunner` process exits.
- [Some shutdown hooks are triggered](https://github.com/gradle/gradle/blob/c8143c9bcf412a2d19053b8c926c7787c1dc8087/subprojects/core/src/main/java/org/gradle/process/internal/ExecHandleShutdownHookAction.java#L39).
- [Force kill child process](https://github.com/gradle/gradle/blob/c8143c9bcf412a2d19053b8c926c7787c1dc8087/subprojects/core/src/main/java/org/gradle/process/internal/ExecHandleRunner.java#L58).
- Child process return with 143 (`SIGTERM`).
- Stacktrace printed on `System.err`.
@ghale Seems you're more familiar with this issue and the solution.
See https://github.com/blindpirate/gradle-worker-poc for a reproducible sample. | 1.0 | GradleRunner should not fork a long-live daemon when `withDebug(true)` - As reported [here](https://discuss.gradle.org/t/testkit-and-worker-api-st-when-debug-is-enabled/25490?u=dpukyle), at some point between `4.0` and `4.1`, we create worker daemon process with `KeepAliveMode.DAEMON`, which we have to force kill after the build and this results in a stacktrace printed on console.
Before `4.1`, we created child process for `GradleRunner.withDebug(true)` with the following sequence:
- [Fork a child process for the actual build](https://github.com/gradle/gradle/blob/c8143c9bcf412a2d19053b8c926c7787c1dc8087/subprojects/core/src/main/java/org/gradle/process/internal/ExecHandleRunner.java#L68).
- [`waitFor` child process to exit](https://github.com/gradle/gradle/blob/c8143c9bcf412a2d19053b8c926c7787c1dc8087/subprojects/core/src/main/java/org/gradle/process/internal/ExecHandleRunner.java#L81).
- `GradleRunner` process exits.
After `4.1`:
- [Fork a child process for the actual build](https://github.com/gradle/gradle/blob/c8143c9bcf412a2d19053b8c926c7787c1dc8087/subprojects/core/src/main/java/org/gradle/process/internal/ExecHandleRunner.java#L68).
- This child process is long-live daemon so it never exits.
- `GradleRunner` process exits.
- [Some shutdown hooks are triggered](https://github.com/gradle/gradle/blob/c8143c9bcf412a2d19053b8c926c7787c1dc8087/subprojects/core/src/main/java/org/gradle/process/internal/ExecHandleShutdownHookAction.java#L39).
- [Force kill child process](https://github.com/gradle/gradle/blob/c8143c9bcf412a2d19053b8c926c7787c1dc8087/subprojects/core/src/main/java/org/gradle/process/internal/ExecHandleRunner.java#L58).
- Child process return with 143 (`SIGTERM`).
- Stacktrace printed on `System.err`.
@ghale Seems you're more familiar with this issue and the solution.
See https://github.com/blindpirate/gradle-worker-poc for a reproducible sample. | test | gradlerunner should not fork a long live daemon when withdebug true as reported at some point between and we create worker daemon process with keepalivemode daemon which we have to force kill after the build and this results in a stacktrace printed on console before we created child process for gradlerunner withdebug true with the following sequence gradlerunner process exits after this child process is long live daemon so it never exits gradlerunner process exits child process return with sigterm stacktrace printed on system err ghale seems you re more familiar with this issue and the solution see for a reproducible sample | 1 |
139,631 | 12,876,729,086 | IssuesEvent | 2020-07-11 06:47:02 | clojure-emacs/cider | https://api.github.com/repos/clojure-emacs/cider | closed | Chose a license for the documentation portal | documentation help wanted | I was recently asked about this and I realized we never chose a license for the docs portal.
Some options are outline here - https://www.dreamsongs.com/IHE/IHE-50.html I'm leaning towards the GNU FDL, but there are also some concerns about it https://www.debian.org/vote/2006/vote_001 (at least for version 1.2).
@clojure-emacs/cider Let me know if someone has ideas on the subject. | 1.0 | Chose a license for the documentation portal - I was recently asked about this and I realized we never chose a license for the docs portal.
Some options are outline here - https://www.dreamsongs.com/IHE/IHE-50.html I'm leaning towards the GNU FDL, but there are also some concerns about it https://www.debian.org/vote/2006/vote_001 (at least for version 1.2).
@clojure-emacs/cider Let me know if someone has ideas on the subject. | non_test | chose a license for the documentation portal i was recently asked about this and i realized we never chose a license for the docs portal some options are outline here i m leaning towards the gnu fdl but there are also some concerns about it at least for version clojure emacs cider let me know if someone has ideas on the subject | 0 |
347,674 | 24,895,363,845 | IssuesEvent | 2022-10-28 15:20:47 | neo4j-labs/neodash | https://api.github.com/repos/neo4j-labs/neodash | closed | Save the dashboard automatically upon closing | documentation | As described in another issue (https://github.com/neo4j-labs/neodash/issues/238#issuecomment-1289290775), I lost a few days worth of work after deleting cookies from my browser, because I do/did not save the dashboard after every modification.
I now checked the documentation again and I cannot find any warning about this lurking danger anywhere (at least not in plain sight, but I might have overlooked it).
So I have 2 requests:
1. please add a clear warning in the documentation: cookies gone equals dashboard gone!
2. please consider adding a feature to the General Settings: "Save dashboard when closing?" which eliminates a lot of work as well as destruction-by-forgetfulness.
Thank you. | 1.0 | Save the dashboard automatically upon closing - As described in another issue (https://github.com/neo4j-labs/neodash/issues/238#issuecomment-1289290775), I lost a few days worth of work after deleting cookies from my browser, because I do/did not save the dashboard after every modification.
I now checked the documentation again and I cannot find any warning about this lurking danger anywhere (at least not in plain sight, but I might have overlooked it).
So I have 2 requests:
1. please add a clear warning in the documentation: cookies gone equals dashboard gone!
2. please consider adding a feature to the General Settings: "Save dashboard when closing?" which eliminates a lot of work as well as destruction-by-forgetfulness.
Thank you. | non_test | save the dashboard automatically upon closing as described in another issue i lost a few days worth of work after deleting cookies from my browser because i do did not save the dashboard after every modification i now checked the documentation again and i cannot find any warning about this lurking danger anywhere at least not in plain sight but i might have overlooked it so i have requests please add a clear warning in the documentation cookies gone equals dashboard gone please consider adding a feature to the general settings save dashboard when closing which eliminates a lot of work as well as destruction by forgetfulness thank you | 0 |
119,511 | 10,056,619,993 | IssuesEvent | 2019-07-22 09:34:17 | acacode/kinka | https://api.github.com/repos/acacode/kinka | closed | Create own api for manual testing | internal/testing | Currently project is using `https://reqres.in/api` to do manual tests.
And I think that it is not correct to use another api for manual testing.
| 1.0 | Create own api for manual testing - Currently project is using `https://reqres.in/api` to do manual tests.
And I think that it is not correct to use another api for manual testing.
| test | create own api for manual testing currently project is using to do manual tests and i think that it is not correct to use another api for manual testing | 1 |
4,512 | 6,664,387,087 | IssuesEvent | 2017-10-02 19:57:12 | cedardevs/onestop | https://api.github.com/repos/cedardevs/onestop | closed | Migrate Envelope dateline wrapping bugfix to api-metadata | api bug EPIC: Microservices ready | #206 Bugfix was applied to the api module, and needs to be applied to the new api-metadata module as well.
See https://github.com/cedardevs/onestop/pull/207 | 1.0 | Migrate Envelope dateline wrapping bugfix to api-metadata - #206 Bugfix was applied to the api module, and needs to be applied to the new api-metadata module as well.
See https://github.com/cedardevs/onestop/pull/207 | non_test | migrate envelope dateline wrapping bugfix to api metadata bugfix was applied to the api module and needs to be applied to the new api metadata module as well see | 0 |
166,742 | 12,970,879,174 | IssuesEvent | 2020-07-21 10:00:45 | kyma-project/kyma | https://api.github.com/repos/kyma-project/kyma | closed | Fix test-e2e-upgrade-test-prepare-data | area/eventing duplicate test-failing | The "test-e2e-upgrade-test-prepare-data" part of post-master-kyma-gke-upgrade is failing:
https://storage.googleapis.com/kyma-prow-logs/logs/post-master-kyma-gke-upgrade/1260114112860393472/build-log.txt
Extract from log file:
```
1 pod(s) in e2e-upgrade-test namespace have not terminated phase. Retry checking.
Test pod 'test-e2e-upgrade-test-prepare-data' has phase: "Running"
1 pod(s) in e2e-upgrade-test namespace have not terminated phase. Retry checking.
Test pod 'test-e2e-upgrade-test-prepare-data' has phase: "Failed"
1 pod(s) has failed status
Logs for prepare data operation to test e2e upgrade:
TESTING start
time="2020-05-12T08:10:48Z" level=info msg="using domainName: gke-upgrade-commit-72e7fc3ae-rqumib5diz.a.build.kyma-project.io"
......
......
{"level":"info","log":{"message":"[CreateResources: EventMeshUpgradeTest] Starting execution","taskID":"1180b9c3-ded7-4c68-a1f3-768519899c29","time":"2020-05-12T08:13:49.871Z"}}
time="2020-05-12T08:15:22Z" level=fatal msg="while executing prepare data for all registered tests: executed 12 task and 1 of them failed"
{"level":"error","log":{"error":"All attempts fail:\n#1: trigger eventmesh-upgrade not ready: {{0 []} }\n#2: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#3: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#4: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#5: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#6: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#7: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#8: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#9: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:53 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-filter' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:53 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-filter' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#10: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady True {2020-05-12 08:14:58 +0000 UTC} } {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready Unknown {2020-05-12 08:14:58 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}","message":"CreateResources() failed","taskID":"1180b9c3-ded7-4c68-a1f3-768519899c29","time":"2020-05-12T08:15:22.053Z"}}
{"level":"error","log":{"message":"[CreateResources: EventMeshUpgradeTest] End with error [start time: Tue, 12 May 2020 08:13:49 UTC, duration: 1m32.175932732s]: All attempts fail:\n#1: trigger eventmesh-upgrade not ready: {{0 []} }\n#2: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#3: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#4: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#5: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#6: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#7: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#8: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#9: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:53 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-filter' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:53 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-filter' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#10: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady True {2020-05-12 08:14:58 +0000 UTC} } {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready Unknown {2020-05-12 08:14:58 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}","taskID":"1180b9c3-ded7-4c68-a1f3-768519899c29","time":"2020-05-12T08:15:22.053Z"}}
exit_code is 1
``` | 1.0 | Fix test-e2e-upgrade-test-prepare-data - The "test-e2e-upgrade-test-prepare-data" part of post-master-kyma-gke-upgrade is failing:
https://storage.googleapis.com/kyma-prow-logs/logs/post-master-kyma-gke-upgrade/1260114112860393472/build-log.txt
Extract from log file:
```
1 pod(s) in e2e-upgrade-test namespace have not terminated phase. Retry checking.
Test pod 'test-e2e-upgrade-test-prepare-data' has phase: "Running"
1 pod(s) in e2e-upgrade-test namespace have not terminated phase. Retry checking.
Test pod 'test-e2e-upgrade-test-prepare-data' has phase: "Failed"
1 pod(s) has failed status
Logs for prepare data operation to test e2e upgrade:
TESTING start
time="2020-05-12T08:10:48Z" level=info msg="using domainName: gke-upgrade-commit-72e7fc3ae-rqumib5diz.a.build.kyma-project.io"
......
......
{"level":"info","log":{"message":"[CreateResources: EventMeshUpgradeTest] Starting execution","taskID":"1180b9c3-ded7-4c68-a1f3-768519899c29","time":"2020-05-12T08:13:49.871Z"}}
time="2020-05-12T08:15:22Z" level=fatal msg="while executing prepare data for all registered tests: executed 12 task and 1 of them failed"
{"level":"error","log":{"error":"All attempts fail:\n#1: trigger eventmesh-upgrade not ready: {{0 []} }\n#2: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#3: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#4: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#5: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#6: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#7: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#8: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#9: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:53 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-filter' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:53 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-filter' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#10: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady True {2020-05-12 08:14:58 +0000 UTC} } {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready Unknown {2020-05-12 08:14:58 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}","message":"CreateResources() failed","taskID":"1180b9c3-ded7-4c68-a1f3-768519899c29","time":"2020-05-12T08:15:22.053Z"}}
{"level":"error","log":{"message":"[CreateResources: EventMeshUpgradeTest] End with error [start time: Tue, 12 May 2020 08:13:49 UTC, duration: 1m32.175932732s]: All attempts fail:\n#1: trigger eventmesh-upgrade not ready: {{0 []} }\n#2: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#3: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#4: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#5: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#6: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#7: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#8: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:30 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-ingress' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#9: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady False {2020-05-12 08:14:53 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-filter' is unavailable.} {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready False {2020-05-12 08:14:53 +0000 UTC} DeploymentUnavailable The Deployment 'default-broker-filter' is unavailable.} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}\n#10: trigger eventmesh-upgrade not ready: {{1 [{BrokerReady True {2020-05-12 08:14:58 +0000 UTC} } {DependencyReady True {2020-05-12 08:14:30 +0000 UTC} } {Ready Unknown {2020-05-12 08:14:58 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {Subscribed Unknown {2020-05-12 08:14:30 +0000 UTC} SubscriptionNotMarkedReadyByChannel Failed to get subscription status: [channel.Status.SubscribableStatus is nil]} {SubscriberResolved True {2020-05-12 08:14:30 +0000 UTC} }]} http://eventmesh-upgrade.eventmeshupgradetest.svc.cluster.local:9000/v3/events}","taskID":"1180b9c3-ded7-4c68-a1f3-768519899c29","time":"2020-05-12T08:15:22.053Z"}}
exit_code is 1
``` | test | fix test upgrade test prepare data the test upgrade test prepare data part of post master kyma gke upgrade is failing extract from log file pod s in upgrade test namespace have not terminated phase retry checking test pod test upgrade test prepare data has phase running pod s in upgrade test namespace have not terminated phase retry checking test pod test upgrade test prepare data has phase failed pod s has failed status logs for prepare data operation to test upgrade testing start time level info msg using domainname gke upgrade commit a build kyma project io level info log message starting execution taskid time time level fatal msg while executing prepare data for all registered tests executed task and of them failed level error log error all attempts fail n trigger eventmesh upgrade not ready n trigger eventmesh upgrade not ready subscriberresolved true utc trigger eventmesh upgrade not ready subscriberresolved true utc trigger eventmesh upgrade not ready subscriberresolved true utc trigger eventmesh upgrade not ready subscriberresolved true utc trigger eventmesh upgrade not ready subscriberresolved true utc trigger eventmesh upgrade not ready subscriberresolved true utc trigger eventmesh upgrade not ready subscriberresolved true utc trigger eventmesh upgrade not ready subscriberresolved true utc trigger eventmesh upgrade not ready subscribed unknown utc subscriptionnotmarkedreadybychannel failed to get subscription status subscriberresolved true utc failed taskid time level error log message end with error all attempts fail n trigger eventmesh upgrade not ready n trigger eventmesh upgrade not ready subscriberresolved true utc trigger eventmesh upgrade not ready subscriberresolved true utc trigger eventmesh upgrade not ready subscriberresolved true utc trigger eventmesh upgrade not ready subscriberresolved true utc trigger eventmesh upgrade not ready subscriberresolved true utc trigger eventmesh upgrade not ready subscriberresolved true utc trigger eventmesh upgrade not ready subscriberresolved true utc trigger eventmesh upgrade not ready subscriberresolved true utc trigger eventmesh upgrade not ready subscribed unknown utc subscriptionnotmarkedreadybychannel failed to get subscription status subscriberresolved true utc exit code is | 1 |
40,776 | 5,316,101,277 | IssuesEvent | 2017-02-13 19:01:22 | litehelpers/Cordova-sqlcipher-adapter | https://api.github.com/repos/litehelpers/Cordova-sqlcipher-adapter | opened | Include SQLCipher 3.4.1 | bug enhancement testing | ref: <https://discuss.zetetic.net/t/sqlcipher-3-4-1-release/1962>
FYI this should provide slightly better consistency with cordova-sqlite-storage which is now using sqlite 3.15.2. | 1.0 | Include SQLCipher 3.4.1 - ref: <https://discuss.zetetic.net/t/sqlcipher-3-4-1-release/1962>
FYI this should provide slightly better consistency with cordova-sqlite-storage which is now using sqlite 3.15.2. | test | include sqlcipher ref fyi this should provide slightly better consistency with cordova sqlite storage which is now using sqlite | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.