Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 7 112 | repo_url stringlengths 36 141 | action stringclasses 3 values | title stringlengths 2 665 | labels stringlengths 4 554 | body stringlengths 3 235k | index stringclasses 6 values | text_combine stringlengths 96 235k | label stringclasses 2 values | text stringlengths 96 196k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
32,243 | 26,561,438,637 | IssuesEvent | 2023-01-20 16:10:50 | centerofci/mathesar | https://api.github.com/repos/centerofci/mathesar | closed | Finishing setting up mathesar-update-companion repo | type: housekeeping work: infrastructure status: ready | Following repo has been spun up for our update companion container: https://github.com/centerofci/mathesar-update-companion
The repo might need additional setting up.
### Tasks
- [x] Standardize branch names
- [x] Set up access permissions correctly
- [x] Set up GitHub workflows (sync files from main repo)
- [x] Set up label & milestone sync
- [x] Remove "fork" status
- [x] Set up repo settings - merge types, automatic delete of head branches, etc.
- [x] Verify new labels and milestones
- [x] Delete default labels that we don't use
- [x] Close milestones as needed | 1.0 | Finishing setting up mathesar-update-companion repo - Following repo has been spun up for our update companion container: https://github.com/centerofci/mathesar-update-companion
The repo might need additional setting up.
### Tasks
- [x] Standardize branch names
- [x] Set up access permissions correctly
- [x] Set up GitHub workflows (sync files from main repo)
- [x] Set up label & milestone sync
- [x] Remove "fork" status
- [x] Set up repo settings - merge types, automatic delete of head branches, etc.
- [x] Verify new labels and milestones
- [x] Delete default labels that we don't use
- [x] Close milestones as needed | infrastructure | finishing setting up mathesar update companion repo following repo has been spun up for our update companion container the repo might need additional setting up tasks standardize branch names set up access permissions correctly set up github workflows sync files from main repo set up label milestone sync remove fork status set up repo settings merge types automatic delete of head branches etc verify new labels and milestones delete default labels that we don t use close milestones as needed | 1 |
500,956 | 14,517,593,350 | IssuesEvent | 2020-12-13 20:13:56 | DimensionDev/Maskbook | https://api.github.com/repos/DimensionDev/Maskbook | closed | [Bug] Able to send img payload through mobile Mask.io | Platform: Android (GeckoView) Platform: iOS (WebExt-shim) Priority: P2 (Important) Type: Bug | # Bug Report
followup of #976;
Now blocked by #1786 ;
But we still need to study whats the best way to send img payload through mobile Mask.io; Download locally and upload again is not the best way. | 1.0 | [Bug] Able to send img payload through mobile Mask.io - # Bug Report
followup of #976;
Now blocked by #1786 ;
But we still need to study whats the best way to send img payload through mobile Mask.io; Download locally and upload again is not the best way. | non_infrastructure | able to send img payload through mobile mask io bug report followup of now blocked by but we still need to study whats the best way to send img payload through mobile mask io download locally and upload again is not the best way | 0 |
742,347 | 25,850,487,761 | IssuesEvent | 2022-12-13 10:03:29 | deckhouse/deckhouse | https://api.github.com/repos/deckhouse/deckhouse | closed | [docs] Add snippet to reset deckhouse to use cm/deckhouse | area/docs priority/backlog source/deckhouse-team | ### Preflight Checklist
- [X] I agree to follow the [Code of Conduct](https://github.com/deckhouse/deckhouse/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://github.com/deckhouse/deckhouse/issues) for an issue that matches the one I want to file, without success.
### Use case. Why is this important?
It may be useful to run some snippet to restore deckhouse state to use cm/deckhouse again after merging #1729.
### Proposed Solution
- Scale Deployment/deckhouse replicas to 0.
- Edit Deployment/deckhouse, set env ADDON_OPERATOR_CONFIG_MAP to "deckhouse".
- Disable validating webhook: `kubectl delete validatingwebhookconfiguration/deckhouse-config-webhook`.
- Remove cm/deckhouse-generated-config-do-not-edit.
- Remove all ModuleConfig resources.
### Additional Information
_No response_ | 1.0 | [docs] Add snippet to reset deckhouse to use cm/deckhouse - ### Preflight Checklist
- [X] I agree to follow the [Code of Conduct](https://github.com/deckhouse/deckhouse/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://github.com/deckhouse/deckhouse/issues) for an issue that matches the one I want to file, without success.
### Use case. Why is this important?
It may be useful to run some snippet to restore deckhouse state to use cm/deckhouse again after merging #1729.
### Proposed Solution
- Scale Deployment/deckhouse replicas to 0.
- Edit Deployment/deckhouse, set env ADDON_OPERATOR_CONFIG_MAP to "deckhouse".
- Disable validating webhook: `kubectl delete validatingwebhookconfiguration/deckhouse-config-webhook`.
- Remove cm/deckhouse-generated-config-do-not-edit.
- Remove all ModuleConfig resources.
### Additional Information
_No response_ | non_infrastructure | add snippet to reset deckhouse to use cm deckhouse preflight checklist i agree to follow the that this project adheres to i have searched the for an issue that matches the one i want to file without success use case why is this important it may be useful to run some snippet to restore deckhouse state to use cm deckhouse again after merging proposed solution scale deployment deckhouse replicas to edit deployment deckhouse set env addon operator config map to deckhouse disable validating webhook kubectl delete validatingwebhookconfiguration deckhouse config webhook remove cm deckhouse generated config do not edit remove all moduleconfig resources additional information no response | 0 |
31,036 | 8,641,807,119 | IssuesEvent | 2018-11-24 21:54:19 | Trustroots/trustroots | https://api.github.com/repos/Trustroots/trustroots | closed | easy installation for devs | build | It seems currently the only way to get this set up is if you have a _lot_ of knowledge of node, docker, and mongo.
It should be possible to set this up in less than 15 minutes with minimal knowledge of any of these, at least on Debian/Ubuntu and OSX.
How can we do this? | 1.0 | easy installation for devs - It seems currently the only way to get this set up is if you have a _lot_ of knowledge of node, docker, and mongo.
It should be possible to set this up in less than 15 minutes with minimal knowledge of any of these, at least on Debian/Ubuntu and OSX.
How can we do this? | non_infrastructure | easy installation for devs it seems currently the only way to get this set up is if you have a lot of knowledge of node docker and mongo it should be possible to set this up in less than minutes with minimal knowledge of any of these at least on debian ubuntu and osx how can we do this | 0 |
25,066 | 18,071,366,535 | IssuesEvent | 2021-09-21 03:35:50 | wfau/aglais | https://api.github.com/repos/wfau/aglais | closed | Automate the DNS update | quickfix infrastructure | Create an automated script to update the DNS entries from within the Ansible deployment. | 1.0 | Automate the DNS update - Create an automated script to update the DNS entries from within the Ansible deployment. | infrastructure | automate the dns update create an automated script to update the dns entries from within the ansible deployment | 1 |
63,116 | 14,656,670,743 | IssuesEvent | 2020-12-28 13:56:42 | fu1771695yongxie/redux-saga | https://api.github.com/repos/fu1771695yongxie/redux-saga | opened | CVE-2020-15095 (Medium) detected in npm-2.15.12.tgz, npm-5.1.0.tgz | security vulnerability | ## CVE-2020-15095 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>npm-2.15.12.tgz</b>, <b>npm-5.1.0.tgz</b></p></summary>
<p>
<details><summary><b>npm-2.15.12.tgz</b></p></summary>
<p>a package manager for JavaScript</p>
<p>Library home page: <a href="https://registry.npmjs.org/npm/-/npm-2.15.12.tgz">https://registry.npmjs.org/npm/-/npm-2.15.12.tgz</a></p>
<p>Path to dependency file: redux-saga/node_modules/npm/package.json</p>
<p>Path to vulnerable library: redux-saga/node_modules/npm/package.json</p>
<p>
Dependency Hierarchy:
- gitbook-cli-2.3.2.tgz (Root Library)
- npmi-1.0.1.tgz
- :x: **npm-2.15.12.tgz** (Vulnerable Library)
</details>
<details><summary><b>npm-5.1.0.tgz</b></p></summary>
<p>a package manager for JavaScript</p>
<p>Library home page: <a href="https://registry.npmjs.org/npm/-/npm-5.1.0.tgz">https://registry.npmjs.org/npm/-/npm-5.1.0.tgz</a></p>
<p>Path to dependency file: redux-saga/node_modules/npm/package.json</p>
<p>Path to vulnerable library: redux-saga/node_modules/npm/package.json</p>
<p>
Dependency Hierarchy:
- gitbook-cli-2.3.2.tgz (Root Library)
- :x: **npm-5.1.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/redux-saga/commit/f720d297e70f5336402ca1f30381804ebcfbd5fc">f720d297e70f5336402ca1f30381804ebcfbd5fc</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>
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like "<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>". The password value is not redacted and is printed to stdout and also to any generated log files.
<p>Publish Date: 2020-07-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15095>CVE-2020-15095</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>4.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/cli/security/advisories/GHSA-93f3-23rq-pjfp">https://github.com/npm/cli/security/advisories/GHSA-93f3-23rq-pjfp</a></p>
<p>Release Date: 2020-07-07</p>
<p>Fix Resolution: npm - 6.14.6</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-15095 (Medium) detected in npm-2.15.12.tgz, npm-5.1.0.tgz - ## CVE-2020-15095 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>npm-2.15.12.tgz</b>, <b>npm-5.1.0.tgz</b></p></summary>
<p>
<details><summary><b>npm-2.15.12.tgz</b></p></summary>
<p>a package manager for JavaScript</p>
<p>Library home page: <a href="https://registry.npmjs.org/npm/-/npm-2.15.12.tgz">https://registry.npmjs.org/npm/-/npm-2.15.12.tgz</a></p>
<p>Path to dependency file: redux-saga/node_modules/npm/package.json</p>
<p>Path to vulnerable library: redux-saga/node_modules/npm/package.json</p>
<p>
Dependency Hierarchy:
- gitbook-cli-2.3.2.tgz (Root Library)
- npmi-1.0.1.tgz
- :x: **npm-2.15.12.tgz** (Vulnerable Library)
</details>
<details><summary><b>npm-5.1.0.tgz</b></p></summary>
<p>a package manager for JavaScript</p>
<p>Library home page: <a href="https://registry.npmjs.org/npm/-/npm-5.1.0.tgz">https://registry.npmjs.org/npm/-/npm-5.1.0.tgz</a></p>
<p>Path to dependency file: redux-saga/node_modules/npm/package.json</p>
<p>Path to vulnerable library: redux-saga/node_modules/npm/package.json</p>
<p>
Dependency Hierarchy:
- gitbook-cli-2.3.2.tgz (Root Library)
- :x: **npm-5.1.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/redux-saga/commit/f720d297e70f5336402ca1f30381804ebcfbd5fc">f720d297e70f5336402ca1f30381804ebcfbd5fc</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>
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like "<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>". The password value is not redacted and is printed to stdout and also to any generated log files.
<p>Publish Date: 2020-07-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15095>CVE-2020-15095</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>4.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/cli/security/advisories/GHSA-93f3-23rq-pjfp">https://github.com/npm/cli/security/advisories/GHSA-93f3-23rq-pjfp</a></p>
<p>Release Date: 2020-07-07</p>
<p>Fix Resolution: npm - 6.14.6</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_infrastructure | cve medium detected in npm tgz npm tgz cve medium severity vulnerability vulnerable libraries npm tgz npm tgz npm tgz a package manager for javascript library home page a href path to dependency file redux saga node modules npm package json path to vulnerable library redux saga node modules npm package json dependency hierarchy gitbook cli tgz root library npmi tgz x npm tgz vulnerable library npm tgz a package manager for javascript library home page a href path to dependency file redux saga node modules npm package json path to vulnerable library redux saga node modules npm package json dependency hierarchy gitbook cli tgz root library x npm tgz vulnerable library found in head commit a href found in base branch master vulnerability details versions of the npm cli prior to are vulnerable to an information exposure vulnerability through log files the cli supports urls like the password value is not redacted and is printed to stdout and also to any generated log files publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low user interaction required scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution npm step up your open source security game with whitesource | 0 |
34,927 | 30,592,381,402 | IssuesEvent | 2023-07-21 18:16:35 | casangi/astrohack | https://api.github.com/repos/casangi/astrohack | closed | fix-testing-to-check-cell-size-after-extract-holog | bug Area:Infrastructure Area:Verification | The testing of the cell size is done when testing `holog(...)` , which was fine when that was where it was computed. It was moved into `extract_holog(...)` so we will test it there. | 1.0 | fix-testing-to-check-cell-size-after-extract-holog - The testing of the cell size is done when testing `holog(...)` , which was fine when that was where it was computed. It was moved into `extract_holog(...)` so we will test it there. | infrastructure | fix testing to check cell size after extract holog the testing of the cell size is done when testing holog which was fine when that was where it was computed it was moved into extract holog so we will test it there | 1 |
18,303 | 10,060,912,228 | IssuesEvent | 2019-07-22 20:01:29 | alpheios-project/components | https://api.github.com/repos/alpheios-project/components | closed | Firefox: yellow message on loading diagram | duplicate performance | Firefox, build 1.0.0.11
double click on αὐτοὺς in http://texts-beta.alpheios.net/text/urn:cts:greekLit:tlg0012.tlg001.alpheios-text-grc1/passage/1.1-1.30
and click on Diagram. the yellow message is generating on top of the page. Diagram panel opens up, but then I am not longer able to do any lookup (sort of freeze)
see screenshot
| True | Firefox: yellow message on loading diagram - Firefox, build 1.0.0.11
double click on αὐτοὺς in http://texts-beta.alpheios.net/text/urn:cts:greekLit:tlg0012.tlg001.alpheios-text-grc1/passage/1.1-1.30
and click on Diagram. the yellow message is generating on top of the page. Diagram panel opens up, but then I am not longer able to do any lookup (sort of freeze)
see screenshot
| non_infrastructure | firefox yellow message on loading diagram firefox build double click on αὐτοὺς in and click on diagram the yellow message is generating on top of the page diagram panel opens up but then i am not longer able to do any lookup sort of freeze see screenshot | 0 |
479,367 | 13,795,339,281 | IssuesEvent | 2020-10-09 17:50:37 | idaholab/raven | https://api.github.com/repos/idaholab/raven | closed | [TASK] New metric in post processor | priority_minor task | --------
Issue Description
--------
**Is your feature request related to a problem? Please describe.**
New metrics are needed for optimizing the allocation capital between the constituent assets of the portfolio.
**Describe the solution you'd like**
For risk-adjusted return:
[Sharpe ratio](https://en.wikipedia.org/wiki/Sharpe_ratio) risk-free rate as 0
[Sortino ratio ](https://en.wikipedia.org/wiki/Sortino_ratio)
gain loss ratio:
the first-order higher partial moment of a portfolio's returns, divided by the first-order lower partial moment of a portfolio's returns.
[value at risk](https://en.wikipedia.org/wiki/Value_at_risk)
[conditional value at risk](https://en.wikipedia.org/wiki/Expected_shortfall)
----------------
For Change Control Board: Issue Review
----------------
This review should occur before any development is performed as a response to this issue.
- [x] 1. Is it tagged with a type: defect or task?
- [x] 2. Is it tagged with a priority: critical, normal or minor?
- [x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
- [x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
- [x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)
-------
For Change Control Board: Issue Closure
-------
This review should occur when the issue is imminently going to be closed.
- [x] 1. If the issue is a defect, is the defect fixed?
- [x] 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
- [x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
- [x] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
- [x] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
| 1.0 | [TASK] New metric in post processor - --------
Issue Description
--------
**Is your feature request related to a problem? Please describe.**
New metrics are needed for optimizing the allocation capital between the constituent assets of the portfolio.
**Describe the solution you'd like**
For risk-adjusted return:
[Sharpe ratio](https://en.wikipedia.org/wiki/Sharpe_ratio) risk-free rate as 0
[Sortino ratio ](https://en.wikipedia.org/wiki/Sortino_ratio)
gain loss ratio:
the first-order higher partial moment of a portfolio's returns, divided by the first-order lower partial moment of a portfolio's returns.
[value at risk](https://en.wikipedia.org/wiki/Value_at_risk)
[conditional value at risk](https://en.wikipedia.org/wiki/Expected_shortfall)
----------------
For Change Control Board: Issue Review
----------------
This review should occur before any development is performed as a response to this issue.
- [x] 1. Is it tagged with a type: defect or task?
- [x] 2. Is it tagged with a priority: critical, normal or minor?
- [x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
- [x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
- [x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)
-------
For Change Control Board: Issue Closure
-------
This review should occur when the issue is imminently going to be closed.
- [x] 1. If the issue is a defect, is the defect fixed?
- [x] 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
- [x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
- [x] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
- [x] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
| non_infrastructure | new metric in post processor issue description is your feature request related to a problem please describe new metrics are needed for optimizing the allocation capital between the constituent assets of the portfolio describe the solution you d like for risk adjusted return risk free rate as gain loss ratio the first order higher partial moment of a portfolio s returns divided by the first order lower partial moment of a portfolio s returns for change control board issue review this review should occur before any development is performed as a response to this issue is it tagged with a type defect or task is it tagged with a priority critical normal or minor if it will impact requirements or requirements tests is it tagged with requirements if it is a defect can it cause wrong results for users if so an email needs to be sent to the users is a rationale provided such as explaining why the improvement is needed or why current code is wrong for change control board issue closure this review should occur when the issue is imminently going to be closed if the issue is a defect is the defect fixed if the issue is a defect is the defect tested for in the regression test system if not explain why not if the issue can impact users has an email to the users group been written the email should specify if the defect impacts stable or master if the issue is a defect does it impact the latest release branch if yes is there any issue tagged with release create if needed if the issue is being closed without a pull request has an explanation of why it is being closed been provided | 0 |
294,894 | 25,413,474,524 | IssuesEvent | 2022-11-22 21:15:25 | DARPA-ASKEM/data-service | https://api.github.com/repos/DARPA-ASKEM/data-service | closed | Thin thread API call walk through | enhancement testing | 1. `CREATE` framework called `Petri Net` (script load common frameworks)
2. `CREATE` person `JohnSmith@gmail.com`
3. `CREATE` project called `MyProject`; specify this was created by `John Smith` [keep track of this project id!]
4. `CREATE` publication with xDD id `616cf16267467f7269ccde6f`. The ID is in `document_xdd-gddid.txt`
5. `UPDATE` project with asset for `MyProject` indicating that the publication is an asset of the project
6. `CREATE` intermediate `intermediate_xyz` from MIRA that’s a MIRA meta template where the representation is from `model_mmt-templates.json`
7. `UPDATE` project with asset for `MyProject` indicating that the intermediate is an asset of the project
8. `CREATE` provenance relation: `intermediate_xyz` is derived from `616cf16267467f7269ccde6f`
9. `CREATE` model called `petri_xyz` from model_petri.json and has the “Petri Net” framework
10. `UPDATE` project with asset for `MyProject` attaching `petri_xyz` to it
11. `CREATE` provenance relation: `petri_xyz` is derived from `intermediate_xyz`
12. `CREATE` simulation plan `MySim` from simulation-plan_ATE.json with associated model `petri_xyz`
13. `CREATE` provenance relation: `MySim` relies on `petri_xyz`
14. `UPDATE` project with asset for `MyProject` attaching `MySim` to it
15. `CREATE` parameters from `model_mmt-parameters.json` associated with simulation `MySim`. This should create 28 parameters records in the database
16. `CREATE` simulation run `MyRun` from file (TBD) associated with `MySim`
17. `CREATE` dataset `MyData` from simulation run `MyRun`
18. `CREATE` provenance relation: `MyData` is derived from `MyRun`
| 1.0 | Thin thread API call walk through - 1. `CREATE` framework called `Petri Net` (script load common frameworks)
2. `CREATE` person `JohnSmith@gmail.com`
3. `CREATE` project called `MyProject`; specify this was created by `John Smith` [keep track of this project id!]
4. `CREATE` publication with xDD id `616cf16267467f7269ccde6f`. The ID is in `document_xdd-gddid.txt`
5. `UPDATE` project with asset for `MyProject` indicating that the publication is an asset of the project
6. `CREATE` intermediate `intermediate_xyz` from MIRA that’s a MIRA meta template where the representation is from `model_mmt-templates.json`
7. `UPDATE` project with asset for `MyProject` indicating that the intermediate is an asset of the project
8. `CREATE` provenance relation: `intermediate_xyz` is derived from `616cf16267467f7269ccde6f`
9. `CREATE` model called `petri_xyz` from model_petri.json and has the “Petri Net” framework
10. `UPDATE` project with asset for `MyProject` attaching `petri_xyz` to it
11. `CREATE` provenance relation: `petri_xyz` is derived from `intermediate_xyz`
12. `CREATE` simulation plan `MySim` from simulation-plan_ATE.json with associated model `petri_xyz`
13. `CREATE` provenance relation: `MySim` relies on `petri_xyz`
14. `UPDATE` project with asset for `MyProject` attaching `MySim` to it
15. `CREATE` parameters from `model_mmt-parameters.json` associated with simulation `MySim`. This should create 28 parameters records in the database
16. `CREATE` simulation run `MyRun` from file (TBD) associated with `MySim`
17. `CREATE` dataset `MyData` from simulation run `MyRun`
18. `CREATE` provenance relation: `MyData` is derived from `MyRun`
| non_infrastructure | thin thread api call walk through create framework called petri net script load common frameworks create person johnsmith gmail com create project called myproject specify this was created by john smith create publication with xdd id the id is in document xdd gddid txt update project with asset for myproject indicating that the publication is an asset of the project create intermediate intermediate xyz from mira that’s a mira meta template where the representation is from model mmt templates json update project with asset for myproject indicating that the intermediate is an asset of the project create provenance relation intermediate xyz is derived from create model called petri xyz from model petri json and has the “petri net” framework update project with asset for myproject attaching petri xyz to it create provenance relation petri xyz is derived from intermediate xyz create simulation plan mysim from simulation plan ate json with associated model petri xyz create provenance relation mysim relies on petri xyz update project with asset for myproject attaching mysim to it create parameters from model mmt parameters json associated with simulation mysim this should create parameters records in the database create simulation run myrun from file tbd associated with mysim create dataset mydata from simulation run myrun create provenance relation mydata is derived from myrun | 0 |
2,775 | 3,863,169,463 | IssuesEvent | 2016-04-08 08:11:27 | servo/servo | https://api.github.com/repos/servo/servo | closed | manifest_changed.sh is slow | A-infrastructure A-testing | On Travis, it takes ~250s. It's probably going to be hard to improve, but we should look into it. | 1.0 | manifest_changed.sh is slow - On Travis, it takes ~250s. It's probably going to be hard to improve, but we should look into it. | infrastructure | manifest changed sh is slow on travis it takes it s probably going to be hard to improve but we should look into it | 1 |
1,073 | 3,030,271,787 | IssuesEvent | 2015-08-04 16:37:16 | google/trace-viewer | https://api.github.com/repos/google/trace-viewer | closed | Tracing as a chrome extension | Enhancement Infrastructure | _From [dsinclair@chromium.org](https://code.google.com/u/dsinclair@chromium.org/) on September 04, 2013 10:52:16_
Currently tracing works thought the WebUI layer of chrome. If we change this to work as an extension it would provide us with a few benefits.
- trace-viewer can become a chrome app giving access to things like the google drive api
- Easier for third parties to access tracing data
_Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=432_ | 1.0 | Tracing as a chrome extension - _From [dsinclair@chromium.org](https://code.google.com/u/dsinclair@chromium.org/) on September 04, 2013 10:52:16_
Currently tracing works thought the WebUI layer of chrome. If we change this to work as an extension it would provide us with a few benefits.
- trace-viewer can become a chrome app giving access to things like the google drive api
- Easier for third parties to access tracing data
_Original issue: http://code.google.com/p/trace-viewer/issues/detail?id=432_ | infrastructure | tracing as a chrome extension from on september currently tracing works thought the webui layer of chrome if we change this to work as an extension it would provide us with a few benefits trace viewer can become a chrome app giving access to things like the google drive api easier for third parties to access tracing data original issue | 1 |
31,183 | 25,395,018,175 | IssuesEvent | 2022-11-22 07:58:19 | lisa-analyzer/lisa | https://api.github.com/repos/lisa-analyzer/lisa | closed | [FEATURE REQUEST] Build improvements | 🎆 type:feature 🎊 resolution:resolved ⁉ priority:p2 🏨 scope:infrastructure | **Description**
- [x] ensure maximum debug info are produced
- [x] force source and target level
- [ ] ~investigate upgrade to java 17~ not relevant at the moment
- [ ] ~modules (still optional, depending on gradle/eclipse)~ will do with java 17
- [ ] ~gradle github action~ no real benefits
- [ ] ~cron test: "extensive" all combinations?~ not relevant at the moment
More to be added.
| 1.0 | [FEATURE REQUEST] Build improvements - **Description**
- [x] ensure maximum debug info are produced
- [x] force source and target level
- [ ] ~investigate upgrade to java 17~ not relevant at the moment
- [ ] ~modules (still optional, depending on gradle/eclipse)~ will do with java 17
- [ ] ~gradle github action~ no real benefits
- [ ] ~cron test: "extensive" all combinations?~ not relevant at the moment
More to be added.
| infrastructure | build improvements description ensure maximum debug info are produced force source and target level investigate upgrade to java not relevant at the moment modules still optional depending on gradle eclipse will do with java gradle github action no real benefits cron test extensive all combinations not relevant at the moment more to be added | 1 |
31,220 | 4,698,308,219 | IssuesEvent | 2016-10-12 12:31:42 | coala/coala | https://api.github.com/repos/coala/coala | opened | Make LocalBearTestHelper robust | difficulty/low type/feature type/test | _From @sils on February 21, 2016 15:8_
_From @AbdealiJK on December 8, 2015 13:31_
Currently, `LocalBearTestHelper` simply checks if there are results that are yielded or not.
Would be considerably better is we give it a list of line, cols where the result should yield in a given file.
_Copied from original issue: coala-analyzer/coala#1111_
_Copied from original issue: coala/coala-bears#36_ | 1.0 | Make LocalBearTestHelper robust - _From @sils on February 21, 2016 15:8_
_From @AbdealiJK on December 8, 2015 13:31_
Currently, `LocalBearTestHelper` simply checks if there are results that are yielded or not.
Would be considerably better is we give it a list of line, cols where the result should yield in a given file.
_Copied from original issue: coala-analyzer/coala#1111_
_Copied from original issue: coala/coala-bears#36_ | non_infrastructure | make localbeartesthelper robust from sils on february from abdealijk on december currently localbeartesthelper simply checks if there are results that are yielded or not would be considerably better is we give it a list of line cols where the result should yield in a given file copied from original issue coala analyzer coala copied from original issue coala coala bears | 0 |
33,524 | 27,549,436,422 | IssuesEvent | 2023-03-07 14:03:19 | nf-core/tools | https://api.github.com/repos/nf-core/tools | closed | Improve test coverage of `__main__.py` | enhancement infrastructure | ### Description of feature
`__main__.py` defines all cli commands. It is here there are the more coverage misses (~240).
Relates to #1790 | 1.0 | Improve test coverage of `__main__.py` - ### Description of feature
`__main__.py` defines all cli commands. It is here there are the more coverage misses (~240).
Relates to #1790 | infrastructure | improve test coverage of main py description of feature main py defines all cli commands it is here there are the more coverage misses relates to | 1 |
32,084 | 6,711,928,911 | IssuesEvent | 2017-10-13 07:14:33 | RIOT-OS/RIOT | https://api.github.com/repos/RIOT-OS/RIOT | closed | core: thread_flags: THREAD_FLAG_MUTEX_UNLOCKED, THREAD_FLAG_TIMEOUT are not used | core quality defect timer | Follow up to #7533. I found that there are two other predefined constants which are not used in the tree.
- `THREAD_FLAG_MUTEX_UNLOCKED`
- `THREAD_FLAG_TIMEOUT`
I think the constants may be intended for `xtimer_msg_timeout`, which mentions core_thread_flags in the documentation, but does not in fact use thread flags for the implementation. | 1.0 | core: thread_flags: THREAD_FLAG_MUTEX_UNLOCKED, THREAD_FLAG_TIMEOUT are not used - Follow up to #7533. I found that there are two other predefined constants which are not used in the tree.
- `THREAD_FLAG_MUTEX_UNLOCKED`
- `THREAD_FLAG_TIMEOUT`
I think the constants may be intended for `xtimer_msg_timeout`, which mentions core_thread_flags in the documentation, but does not in fact use thread flags for the implementation. | non_infrastructure | core thread flags thread flag mutex unlocked thread flag timeout are not used follow up to i found that there are two other predefined constants which are not used in the tree thread flag mutex unlocked thread flag timeout i think the constants may be intended for xtimer msg timeout which mentions core thread flags in the documentation but does not in fact use thread flags for the implementation | 0 |
15,692 | 11,661,881,340 | IssuesEvent | 2020-03-03 07:56:07 | containous/maesh | https://api.github.com/repos/containous/maesh | closed | GHPages fails in CI | area/infrastructure area/tests | Semaphore fails on the GH-Pages branch becuase there is no `semaphore.yml` file.
We should have our deploy script copy that file in, and modify it so that it skips the test suite, and "passes". | 1.0 | GHPages fails in CI - Semaphore fails on the GH-Pages branch becuase there is no `semaphore.yml` file.
We should have our deploy script copy that file in, and modify it so that it skips the test suite, and "passes". | infrastructure | ghpages fails in ci semaphore fails on the gh pages branch becuase there is no semaphore yml file we should have our deploy script copy that file in and modify it so that it skips the test suite and passes | 1 |
21,266 | 14,484,371,750 | IssuesEvent | 2020-12-10 16:15:34 | 18F/aws-admin | https://api.github.com/repos/18F/aws-admin | closed | audit IAM policies that aren't being used | g: accepted i: infrastructure improvement t: days | ## User Story:
As someone responsible for AWS Admin, I would like to audit IAM permissions
## Problem Statement:
Wondering if there's something we can do centrally to be safer about this by default.
## Background information:
[Login.gov discussion that spurred this.](https://docs.google.com/document/d/1a6N8DxnThYsgEay6CkeW_J0-MiphXhghUYjMQhpTAwU/edit#heading=h.iz5wwlbhsruc)
## Actions to take:
- [x] Review Your AWS Account Credentials
- [x] Review Your IAM Users
- [x] Review Your IAM Groups
- [x] Review Your IAM Roles
- [x] Review Your IAM Providers for SAML and OpenID Connect (OIDC)
- [ ] Review Your Mobile Apps
- [ ] Review Your Amazon EC2 Security Configuration
- [x] Review AWS Policies in Other Services
- [ ] Monitor Activity in Your AWS Account
## Acceptance criteria:
- [ ] We have notified respective teams about unused policies
- [ ] We have a documented way to perform this audit in the future
- [x] Create new issue around doing so on an ongoing/automated/real-time basis
## Supporting Documentation:
Some tools that came up:
- [repokid](https://github.com/Netflix/repokid)
- [CloudMapper](https://github.com/duo-labs/cloudmapper)
- [CloudTracker](https://github.com/duo-labs/cloudtracker)
- [AWS Access Advisor](https://aws.amazon.com/blogs/security/automate-analyzing-permissions-using-iam-access-advisor/)
## Related Issues:
| 1.0 | audit IAM policies that aren't being used - ## User Story:
As someone responsible for AWS Admin, I would like to audit IAM permissions
## Problem Statement:
Wondering if there's something we can do centrally to be safer about this by default.
## Background information:
[Login.gov discussion that spurred this.](https://docs.google.com/document/d/1a6N8DxnThYsgEay6CkeW_J0-MiphXhghUYjMQhpTAwU/edit#heading=h.iz5wwlbhsruc)
## Actions to take:
- [x] Review Your AWS Account Credentials
- [x] Review Your IAM Users
- [x] Review Your IAM Groups
- [x] Review Your IAM Roles
- [x] Review Your IAM Providers for SAML and OpenID Connect (OIDC)
- [ ] Review Your Mobile Apps
- [ ] Review Your Amazon EC2 Security Configuration
- [x] Review AWS Policies in Other Services
- [ ] Monitor Activity in Your AWS Account
## Acceptance criteria:
- [ ] We have notified respective teams about unused policies
- [ ] We have a documented way to perform this audit in the future
- [x] Create new issue around doing so on an ongoing/automated/real-time basis
## Supporting Documentation:
Some tools that came up:
- [repokid](https://github.com/Netflix/repokid)
- [CloudMapper](https://github.com/duo-labs/cloudmapper)
- [CloudTracker](https://github.com/duo-labs/cloudtracker)
- [AWS Access Advisor](https://aws.amazon.com/blogs/security/automate-analyzing-permissions-using-iam-access-advisor/)
## Related Issues:
| infrastructure | audit iam policies that aren t being used user story as someone responsible for aws admin i would like to audit iam permissions problem statement wondering if there s something we can do centrally to be safer about this by default background information actions to take review your aws account credentials review your iam users review your iam groups review your iam roles review your iam providers for saml and openid connect oidc review your mobile apps review your amazon security configuration review aws policies in other services monitor activity in your aws account acceptance criteria we have notified respective teams about unused policies we have a documented way to perform this audit in the future create new issue around doing so on an ongoing automated real time basis supporting documentation some tools that came up related issues | 1 |
349,723 | 10,472,433,006 | IssuesEvent | 2019-09-23 10:10:07 | AY1920S1-CS2113T-W12-4/main | https://api.github.com/repos/AY1920S1-CS2113T-W12-4/main | opened | As a user, I can input multiple dates for a task | priority.High type.Story | so that I can refer to the dates in the list until I can confirm the timing. | 1.0 | As a user, I can input multiple dates for a task - so that I can refer to the dates in the list until I can confirm the timing. | non_infrastructure | as a user i can input multiple dates for a task so that i can refer to the dates in the list until i can confirm the timing | 0 |
31,370 | 25,595,019,267 | IssuesEvent | 2022-12-01 15:35:44 | enarx/enarx | https://api.github.com/repos/enarx/enarx | closed | [Feature]: QPL Patch | intel sgx infrastructure external | # Description:
We would like to remove the requirement for the PCCS API Key and to modify the python script to fetch the cached key and read it from disk.
| 1.0 | [Feature]: QPL Patch - # Description:
We would like to remove the requirement for the PCCS API Key and to modify the python script to fetch the cached key and read it from disk.
| infrastructure | qpl patch description we would like to remove the requirement for the pccs api key and to modify the python script to fetch the cached key and read it from disk | 1 |
688 | 2,852,226,997 | IssuesEvent | 2015-06-01 12:28:48 | Starcounter/Starcounter | https://api.github.com/repos/Starcounter/Starcounter | opened | Compiling non-C files in VS | enhancement Infrastructure question | An example of non-C, which is part of Level0 branch `next`, is `gram.y`. As I understood the only way to build it, i.e., to generate c and h files, is to build entire project. Is it possible that CMake generates VS project file that allows to build just this file, i.e., using Ctrl-F7, like it was in branch `develop`. | 1.0 | Compiling non-C files in VS - An example of non-C, which is part of Level0 branch `next`, is `gram.y`. As I understood the only way to build it, i.e., to generate c and h files, is to build entire project. Is it possible that CMake generates VS project file that allows to build just this file, i.e., using Ctrl-F7, like it was in branch `develop`. | infrastructure | compiling non c files in vs an example of non c which is part of branch next is gram y as i understood the only way to build it i e to generate c and h files is to build entire project is it possible that cmake generates vs project file that allows to build just this file i e using ctrl like it was in branch develop | 1 |
22,236 | 15,055,896,462 | IssuesEvent | 2021-02-03 19:25:45 | commitdev/zero | https://api.github.com/repos/commitdev/zero | opened | bug: user-auth namespace already exist | bug infrastructure | when terraform applies, maybe because of the secret creation the user-auth namespace is already created
terraform errors out because it also tries to create it, we need to either change the https://github.com/commitdev/zero-aws-eks-stack/blob/main/templates/kubernetes/terraform/modules/kubernetes/user_auth.tf#L21 to be a `data` instead of `resource` | 1.0 | bug: user-auth namespace already exist - when terraform applies, maybe because of the secret creation the user-auth namespace is already created
terraform errors out because it also tries to create it, we need to either change the https://github.com/commitdev/zero-aws-eks-stack/blob/main/templates/kubernetes/terraform/modules/kubernetes/user_auth.tf#L21 to be a `data` instead of `resource` | infrastructure | bug user auth namespace already exist when terraform applies maybe because of the secret creation the user auth namespace is already created terraform errors out because it also tries to create it we need to either change the to be a data instead of resource | 1 |
494,141 | 14,245,979,916 | IssuesEvent | 2020-11-19 09:26:37 | wso2/product-apim | https://api.github.com/repos/wso2/product-apim | closed | Prevent listing workflow approval tasks based on the user scope | Priority/Highest Type/Improvement | ### Describe your problem(s)
Currently any user with apim:admin scope can view and approve/reject workflow tasks in the admin portal. As an improvement, allow only admin portal users with specific scope to view and approve these tasks | 1.0 | Prevent listing workflow approval tasks based on the user scope - ### Describe your problem(s)
Currently any user with apim:admin scope can view and approve/reject workflow tasks in the admin portal. As an improvement, allow only admin portal users with specific scope to view and approve these tasks | non_infrastructure | prevent listing workflow approval tasks based on the user scope describe your problem s currently any user with apim admin scope can view and approve reject workflow tasks in the admin portal as an improvement allow only admin portal users with specific scope to view and approve these tasks | 0 |
6,295 | 6,304,351,174 | IssuesEvent | 2017-07-21 15:42:46 | abstools/abstools | https://api.github.com/repos/abstools/abstools | closed | Deltas with parameters do not currently work | bug Category: Compiler Infrastructure | e.g., `examples/T4.2/D4.2.1/Indexing-abstract.abs` does not currently compile with parameter `-product=PrefixIndexingDemo` | 1.0 | Deltas with parameters do not currently work - e.g., `examples/T4.2/D4.2.1/Indexing-abstract.abs` does not currently compile with parameter `-product=PrefixIndexingDemo` | infrastructure | deltas with parameters do not currently work e g examples indexing abstract abs does not currently compile with parameter product prefixindexingdemo | 1 |
29,625 | 24,118,899,169 | IssuesEvent | 2022-09-20 16:52:07 | pulibrary/orangelight | https://api.github.com/repos/pulibrary/orangelight | closed | Sitemap log should be rotated | infrastructure | The way whenever writes to the log is always appending, which means the log either needs to be added to logrotate or truncated at the beginning of the job.
More background on #1666. | 1.0 | Sitemap log should be rotated - The way whenever writes to the log is always appending, which means the log either needs to be added to logrotate or truncated at the beginning of the job.
More background on #1666. | infrastructure | sitemap log should be rotated the way whenever writes to the log is always appending which means the log either needs to be added to logrotate or truncated at the beginning of the job more background on | 1 |
783,723 | 27,543,298,399 | IssuesEvent | 2023-03-07 10:01:47 | BlueCodeSystems/opensrp-client-ecap-chw | https://api.github.com/repos/BlueCodeSystems/opensrp-client-ecap-chw | closed | The question on “Is the child on MMD?” is not prefilling on VCA screening. As a result the next question “Level of MMD for child” is also not showing | High Priority | 
| 1.0 | The question on “Is the child on MMD?” is not prefilling on VCA screening. As a result the next question “Level of MMD for child” is also not showing - 
| non_infrastructure | the question on “is the child on mmd ” is not prefilling on vca screening as a result the next question “level of mmd for child” is also not showing | 0 |
8,180 | 7,268,401,123 | IssuesEvent | 2018-02-20 09:58:39 | matthiasbeyer/imag | https://api.github.com/repos/matthiasbeyer/imag | opened | libimagentrylink: Unlink functionality | complexity/easy kind/infrastructure kind/nicetohave | Would be helpful to have a "unlink" functionality in `libimagentrylink`, which removes all internal links to an entry.
That might be helpful when deleting entries. | 1.0 | libimagentrylink: Unlink functionality - Would be helpful to have a "unlink" functionality in `libimagentrylink`, which removes all internal links to an entry.
That might be helpful when deleting entries. | infrastructure | libimagentrylink unlink functionality would be helpful to have a unlink functionality in libimagentrylink which removes all internal links to an entry that might be helpful when deleting entries | 1 |
638,340 | 20,725,224,254 | IssuesEvent | 2022-03-14 00:18:47 | etternagame/etterna | https://api.github.com/repos/etternagame/etterna | closed | rebirth tag filtering can overfilter in certain conditions | Type: Bug Priority: Low Language: Lua | ```I found a bug with tags. I'm currently using 0.71.1 Rebirth, Win 10, openGL, made some changes with in the theme(adding 10/15/50% stealth, adding smaller increments on music rates). It seems like if there are multiple difficulties for a chart and I tag one of the difficulties with a tag, the song doesn't show up when I use require tag function unless all of the difficulties for the song are tagged with the tag. In my case, I tried to search for judah in tranceEX pack which I definitely tagged as 'jack' on one of the difficulties but it didn't show up when I tried to filter by tags or when I tried to search with the the tag filter applied. So, I tagged all the difficulties on judah with 'jack' and it's now searchable and as soon as I remove the 'jack' tag on one of the difficulties, it's gone again.``` | 1.0 | rebirth tag filtering can overfilter in certain conditions - ```I found a bug with tags. I'm currently using 0.71.1 Rebirth, Win 10, openGL, made some changes with in the theme(adding 10/15/50% stealth, adding smaller increments on music rates). It seems like if there are multiple difficulties for a chart and I tag one of the difficulties with a tag, the song doesn't show up when I use require tag function unless all of the difficulties for the song are tagged with the tag. In my case, I tried to search for judah in tranceEX pack which I definitely tagged as 'jack' on one of the difficulties but it didn't show up when I tried to filter by tags or when I tried to search with the the tag filter applied. So, I tagged all the difficulties on judah with 'jack' and it's now searchable and as soon as I remove the 'jack' tag on one of the difficulties, it's gone again.``` | non_infrastructure | rebirth tag filtering can overfilter in certain conditions i found a bug with tags i m currently using rebirth win opengl made some changes with in the theme adding stealth adding smaller increments on music rates it seems like if there are multiple difficulties for a chart and i tag one of the difficulties with a tag the song doesn t show up when i use require tag function unless all of the difficulties for the song are tagged with the tag in my case i tried to search for judah in tranceex pack which i definitely tagged as jack on one of the difficulties but it didn t show up when i tried to filter by tags or when i tried to search with the the tag filter applied so i tagged all the difficulties on judah with jack and it s now searchable and as soon as i remove the jack tag on one of the difficulties it s gone again | 0 |
27,978 | 22,691,179,936 | IssuesEvent | 2022-07-04 20:34:57 | provectus/kafka-ui | https://api.github.com/repos/provectus/kafka-ui | closed | Item for AWS Marketplace | status/accepted scope/infrastructure type/feature | ### Is your proposal related to a problem?
<!--
Provide a clear and concise description of what the problem is.
For example, "I'm always frustrated when..."
-->
A bit harder to deploy the application on an environment without docker (old-styled AWS environments on EC2)
### Describe the solution you'd like
Prepare Cloudformation stack with application deployment on EC2 instance
Buton for quick launch of UI for Apache Kafka in AWS account from the this repository
### Describe alternatives you've considered
<!--
Let us know about other solutions you've tried or researched.
-->
(Write your answer here.)
### Additional context
<!--
Is there anything else you can add about the proposal?
You might want to link to related issues here, if you haven't already.
-->
(Write your answer here.) | 1.0 | Item for AWS Marketplace - ### Is your proposal related to a problem?
<!--
Provide a clear and concise description of what the problem is.
For example, "I'm always frustrated when..."
-->
A bit harder to deploy the application on an environment without docker (old-styled AWS environments on EC2)
### Describe the solution you'd like
Prepare Cloudformation stack with application deployment on EC2 instance
Buton for quick launch of UI for Apache Kafka in AWS account from the this repository
### Describe alternatives you've considered
<!--
Let us know about other solutions you've tried or researched.
-->
(Write your answer here.)
### Additional context
<!--
Is there anything else you can add about the proposal?
You might want to link to related issues here, if you haven't already.
-->
(Write your answer here.) | infrastructure | item for aws marketplace is your proposal related to a problem provide a clear and concise description of what the problem is for example i m always frustrated when a bit harder to deploy the application on an environment without docker old styled aws environments on describe the solution you d like prepare cloudformation stack with application deployment on instance buton for quick launch of ui for apache kafka in aws account from the this repository describe alternatives you ve considered let us know about other solutions you ve tried or researched write your answer here additional context is there anything else you can add about the proposal you might want to link to related issues here if you haven t already write your answer here | 1 |
101,209 | 30,923,073,394 | IssuesEvent | 2023-08-06 06:17:32 | Traben-0/Entity_Texture_Features | https://api.github.com/repos/Traben-0/Entity_Texture_Features | closed | 1.19.2 - missing mixin property minversion | enhancement Fixed or added in dev build (released) | `[17:15:13] [main/ERROR] [mixin/]: Mixin config entity_texture_features-forge.mixins.json does not specify "minVersion" property`
`[17:15:13] [main/ERROR] [mixin/]:</span> Mixin config entity_texture_features-common.mixins.json does not specify "minVersion" property`
These are what the logs are complaining about. It does not change much in gameplay, but it would clean up the log files a tiny bit. it being marked as an error will also frighten those not familiar with the logs or mixin errors. | 1.0 | 1.19.2 - missing mixin property minversion - `[17:15:13] [main/ERROR] [mixin/]: Mixin config entity_texture_features-forge.mixins.json does not specify "minVersion" property`
`[17:15:13] [main/ERROR] [mixin/]:</span> Mixin config entity_texture_features-common.mixins.json does not specify "minVersion" property`
These are what the logs are complaining about. It does not change much in gameplay, but it would clean up the log files a tiny bit. it being marked as an error will also frighten those not familiar with the logs or mixin errors. | non_infrastructure | missing mixin property minversion mixin config entity texture features forge mixins json does not specify minversion property mixin config entity texture features common mixins json does not specify minversion property these are what the logs are complaining about it does not change much in gameplay but it would clean up the log files a tiny bit it being marked as an error will also frighten those not familiar with the logs or mixin errors | 0 |
28,674 | 23,438,746,013 | IssuesEvent | 2022-08-15 12:56:33 | dotnet/dotnet-docker | https://api.github.com/repos/dotnet/dotnet-docker | closed | Tags latest, 6.0 and 6.0.8 apply to nanoserver 1809 only | bug area-infrastructure untriaged | <!--
Please keep in mind that the GitHub issue tracker is not intended as a general support forum, but for reporting **non-security** bugs and feature requests.
If you believe you have an issue that affects the SECURITY of the platform, please do NOT create an issue and instead email your issue details to secure@microsoft.com. Your report may be eligible for our [bug bounty](https://www.microsoft.com/en-us/msrc/bounty-dot-net-core) but ONLY if it is reported through email.
For other types of questions, consider using [Stack Overflow](https://stackoverflow.com).
-->
### Describe the Bug
<!-- A clear and concise description of what the bug is. -->
These tags at https://hub.docker.com/_/microsoft-dotnet-aspnet listed for nanoserver 20H2 are wrong:
These tags apply only to nanoserver 1809
### Steps to Reproduce
<!--
We ❤ code! Include minimal steps to reproduce the problem if possible or point us to a simple repro project hosted in a GitHub repo.
We will close this issue if:
- the repro project you share with us is complex. We can't investigate complex projects, so don't point us to such, please.
- if we are not able to repro the behavior you're reporting
-->
N/A
### Other Information
<!--
* Please include any relevant error messages. If possible please include text rather than images (so it shows up in searches).
* Does this issue consistently happen? Include the conditions which cause the problem to occur.
* Do you know of any workarounds?
-->
N/A
### Output of `docker version`
<!-- Paste the output of `docker version` here. -->
N/A
### Output of `docker info`
<!-- Paste the output of `docker info` here. -->
N/A
<!-- Thanks for taking the time to report this! -->
| 1.0 | Tags latest, 6.0 and 6.0.8 apply to nanoserver 1809 only - <!--
Please keep in mind that the GitHub issue tracker is not intended as a general support forum, but for reporting **non-security** bugs and feature requests.
If you believe you have an issue that affects the SECURITY of the platform, please do NOT create an issue and instead email your issue details to secure@microsoft.com. Your report may be eligible for our [bug bounty](https://www.microsoft.com/en-us/msrc/bounty-dot-net-core) but ONLY if it is reported through email.
For other types of questions, consider using [Stack Overflow](https://stackoverflow.com).
-->
### Describe the Bug
<!-- A clear and concise description of what the bug is. -->
These tags at https://hub.docker.com/_/microsoft-dotnet-aspnet listed for nanoserver 20H2 are wrong:
These tags apply only to nanoserver 1809
### Steps to Reproduce
<!--
We ❤ code! Include minimal steps to reproduce the problem if possible or point us to a simple repro project hosted in a GitHub repo.
We will close this issue if:
- the repro project you share with us is complex. We can't investigate complex projects, so don't point us to such, please.
- if we are not able to repro the behavior you're reporting
-->
N/A
### Other Information
<!--
* Please include any relevant error messages. If possible please include text rather than images (so it shows up in searches).
* Does this issue consistently happen? Include the conditions which cause the problem to occur.
* Do you know of any workarounds?
-->
N/A
### Output of `docker version`
<!-- Paste the output of `docker version` here. -->
N/A
### Output of `docker info`
<!-- Paste the output of `docker info` here. -->
N/A
<!-- Thanks for taking the time to report this! -->
| infrastructure | tags latest and apply to nanoserver only please keep in mind that the github issue tracker is not intended as a general support forum but for reporting non security bugs and feature requests if you believe you have an issue that affects the security of the platform please do not create an issue and instead email your issue details to secure microsoft com your report may be eligible for our but only if it is reported through email for other types of questions consider using describe the bug these tags at listed for nanoserver are wrong these tags apply only to nanoserver steps to reproduce we ❤ code include minimal steps to reproduce the problem if possible or point us to a simple repro project hosted in a github repo we will close this issue if the repro project you share with us is complex we can t investigate complex projects so don t point us to such please if we are not able to repro the behavior you re reporting n a other information please include any relevant error messages if possible please include text rather than images so it shows up in searches does this issue consistently happen include the conditions which cause the problem to occur do you know of any workarounds n a output of docker version n a output of docker info n a | 1 |
55,783 | 31,027,347,909 | IssuesEvent | 2023-08-10 10:01:47 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | opened | .NET web api stops responding, resulting in 503 errors (IIS) | tenet-performance | <!--This is just a template - feel free to delete any and all of it and replace as appropriate.-->
### Description
I need help identifying why our web api application stops responding. When the api stops responding the client gets 503 (subcode 0) back. The state of requests in IIS is "ExecuteRequestHandler".
<!--
* Please share a clear and concise description of the performance problem.
* Include minimal steps to reproduce the problem if possible. E.g.: the smallest possible code snippet; or a small repo to clone, with steps to run it.
-->
### Configuration
.NET 7
IIS 8.5
x64
Windows Server 2012
### Data
looking at this screenshot of our datadog .NET Metrics dashboard we can see that the thread count starts to skyrocket at the same time the api stops to respond.
<!--
* Please include any benchmark results, images of graphs, timings or measurements, or callstacks that are relevant.
* If possible please include text as text rather than images (so it shows up in searches).
* If applicable please include before and after measurements.
* There is helpful information about measuring code in this repo [here](https://github.com/dotnet/performance/blob/master/docs/benchmarking-workflow-dotnet-runtime.md).
-->
### Analysis
We are sometimes able to resolve the problem temporarily by recycling the app pool, but after a while the problem comes back again.
<!--
* If you have an idea where the problem might lie, let us know that here.
* Please include any pointers to code, relevant changes, or related issues you know of.
* If you don't know, you can delete this section.
-->
| True | .NET web api stops responding, resulting in 503 errors (IIS) - <!--This is just a template - feel free to delete any and all of it and replace as appropriate.-->
### Description
I need help identifying why our web api application stops responding. When the api stops responding the client gets 503 (subcode 0) back. The state of requests in IIS is "ExecuteRequestHandler".
<!--
* Please share a clear and concise description of the performance problem.
* Include minimal steps to reproduce the problem if possible. E.g.: the smallest possible code snippet; or a small repo to clone, with steps to run it.
-->
### Configuration
.NET 7
IIS 8.5
x64
Windows Server 2012
### Data
looking at this screenshot of our datadog .NET Metrics dashboard we can see that the thread count starts to skyrocket at the same time the api stops to respond.
<!--
* Please include any benchmark results, images of graphs, timings or measurements, or callstacks that are relevant.
* If possible please include text as text rather than images (so it shows up in searches).
* If applicable please include before and after measurements.
* There is helpful information about measuring code in this repo [here](https://github.com/dotnet/performance/blob/master/docs/benchmarking-workflow-dotnet-runtime.md).
-->
### Analysis
We are sometimes able to resolve the problem temporarily by recycling the app pool, but after a while the problem comes back again.
<!--
* If you have an idea where the problem might lie, let us know that here.
* Please include any pointers to code, relevant changes, or related issues you know of.
* If you don't know, you can delete this section.
-->
| non_infrastructure | net web api stops responding resulting in errors iis description i need help identifying why our web api application stops responding when the api stops responding the client gets subcode back the state of requests in iis is executerequesthandler please share a clear and concise description of the performance problem include minimal steps to reproduce the problem if possible e g the smallest possible code snippet or a small repo to clone with steps to run it configuration net iis windows server data looking at this screenshot of our datadog net metrics dashboard we can see that the thread count starts to skyrocket at the same time the api stops to respond please include any benchmark results images of graphs timings or measurements or callstacks that are relevant if possible please include text as text rather than images so it shows up in searches if applicable please include before and after measurements there is helpful information about measuring code in this repo analysis we are sometimes able to resolve the problem temporarily by recycling the app pool but after a while the problem comes back again if you have an idea where the problem might lie let us know that here please include any pointers to code relevant changes or related issues you know of if you don t know you can delete this section | 0 |
198,392 | 6,972,822,621 | IssuesEvent | 2017-12-11 18:19:22 | DavidAlt/VATumorBoard | https://api.github.com/repos/DavidAlt/VATumorBoard | opened | FReq: capture patient preferences | Knowledge Base medium priority | "The system shall capture patient preferences about clinical trial matching." | 1.0 | FReq: capture patient preferences - "The system shall capture patient preferences about clinical trial matching." | non_infrastructure | freq capture patient preferences the system shall capture patient preferences about clinical trial matching | 0 |
32,213 | 26,537,425,942 | IssuesEvent | 2023-01-19 16:36:01 | google/site-kit-wp | https://api.github.com/repos/google/site-kit-wp | opened | Fix the "Connect More Services" story in Storybook. | Type: Bug P1 Type: Infrastructure | ## Bug Description
At the moment, the `analytics-4` module is showing as a connectable module in the Connect More Services story.
Analytics 4 should not be present on this screen.
## Steps to reproduce
<!-- Please provide detailed steps on how to reproduce the bug. -->
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
## Screenshots
<!-- If applicable, please add screenshots to help explain your problem. -->
## Additional Context
<!-- Please complete the following information. -->
- PHP Version:
- OS: [e.g. iOS]
- Browser: [e.g. chrome, safari]
- Plugin Version: [e.g. 22]
- Device: [e.g. iPhone6]
<!-- Please add any additional information about the bug. -->
---------------
_Do not alter or remove anything below. The following sections will be managed by moderators only._
## Acceptance criteria
* <!-- One or more bullet points for acceptance criteria. -->
## Implementation Brief
* <!-- One or more bullet points for how to technically resolve the issue. Make sure to include changes to Storybook and visual regression tests where relevant. -->
### Test Coverage
* <!-- One or more bullet points for how to implement automated tests to verify the issue is resolved. -->
## QA Brief
* <!-- One or more bullet points for how to test that the issue has been resolved. -->
## Changelog entry
* <!-- One sentence summarizing the PR, to be used in the changelog. -->
| 1.0 | Fix the "Connect More Services" story in Storybook. - ## Bug Description
At the moment, the `analytics-4` module is showing as a connectable module in the Connect More Services story.
Analytics 4 should not be present on this screen.
## Steps to reproduce
<!-- Please provide detailed steps on how to reproduce the bug. -->
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
## Screenshots
<!-- If applicable, please add screenshots to help explain your problem. -->
## Additional Context
<!-- Please complete the following information. -->
- PHP Version:
- OS: [e.g. iOS]
- Browser: [e.g. chrome, safari]
- Plugin Version: [e.g. 22]
- Device: [e.g. iPhone6]
<!-- Please add any additional information about the bug. -->
---------------
_Do not alter or remove anything below. The following sections will be managed by moderators only._
## Acceptance criteria
* <!-- One or more bullet points for acceptance criteria. -->
## Implementation Brief
* <!-- One or more bullet points for how to technically resolve the issue. Make sure to include changes to Storybook and visual regression tests where relevant. -->
### Test Coverage
* <!-- One or more bullet points for how to implement automated tests to verify the issue is resolved. -->
## QA Brief
* <!-- One or more bullet points for how to test that the issue has been resolved. -->
## Changelog entry
* <!-- One sentence summarizing the PR, to be used in the changelog. -->
| infrastructure | fix the connect more services story in storybook bug description at the moment the analytics module is showing as a connectable module in the connect more services story analytics should not be present on this screen steps to reproduce go to click on scroll down to see error screenshots additional context php version os browser plugin version device do not alter or remove anything below the following sections will be managed by moderators only acceptance criteria implementation brief test coverage qa brief changelog entry | 1 |
197,431 | 14,924,070,015 | IssuesEvent | 2021-01-23 21:53:12 | finos/waltz | https://api.github.com/repos/finos/waltz | closed | Code cleanup: switch to jooq::fetchOptional(..) | fixed (test & close) small change task | We often use a pattern like
```
Integer val = qry.fetchOne(0, Integer.class);
return Optional.ofNullable(val);
```
This can be replaced with:
```
return qry.fetchOptional(0, Integer.class);
```
| 1.0 | Code cleanup: switch to jooq::fetchOptional(..) - We often use a pattern like
```
Integer val = qry.fetchOne(0, Integer.class);
return Optional.ofNullable(val);
```
This can be replaced with:
```
return qry.fetchOptional(0, Integer.class);
```
| non_infrastructure | code cleanup switch to jooq fetchoptional we often use a pattern like integer val qry fetchone integer class return optional ofnullable val this can be replaced with return qry fetchoptional integer class | 0 |
176,506 | 28,104,445,354 | IssuesEvent | 2023-03-30 22:35:41 | telosnetwork/telos-wallet | https://api.github.com/repos/telosnetwork/telos-wallet | closed | Design EVM Wallet 0.1 for mobile | 🎨 Needs Design | ## Overview
After getting confirmation from the current design, we want to provide the mobile version to the developers.
## Acceptance criteria
- Design the landing page
- Design the wallet balance
- Design the wallet transactions
- Design the wallet send
- Design the wallet receive
- Design the wallet stake | 1.0 | Design EVM Wallet 0.1 for mobile - ## Overview
After getting confirmation from the current design, we want to provide the mobile version to the developers.
## Acceptance criteria
- Design the landing page
- Design the wallet balance
- Design the wallet transactions
- Design the wallet send
- Design the wallet receive
- Design the wallet stake | non_infrastructure | design evm wallet for mobile overview after getting confirmation from the current design we want to provide the mobile version to the developers acceptance criteria design the landing page design the wallet balance design the wallet transactions design the wallet send design the wallet receive design the wallet stake | 0 |
615,438 | 19,255,489,672 | IssuesEvent | 2021-12-09 10:48:55 | ScicraftLearn/Scicraft | https://api.github.com/repos/ScicraftLearn/Scicraft | closed | Entropy Creeper: randomize color of sheep | enhancement low priority Entities | On top of teleporting, sheep also get a different color. | 1.0 | Entropy Creeper: randomize color of sheep - On top of teleporting, sheep also get a different color. | non_infrastructure | entropy creeper randomize color of sheep on top of teleporting sheep also get a different color | 0 |
139,219 | 31,302,021,459 | IssuesEvent | 2023-08-23 00:56:28 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | Test failure System.Threading.ThreadPools.Tests.ThreadPoolTests.FileStreamFlushAsyncThreadPoolDeadlockTest | arch-x86 os-linux os-windows JitStress area-CodeGen-coreclr | **Failed in:** [runtime-coreclr libraries-jitstress 20230730.1](https://dev.azure.com/dnceng-public/public/_build/results?buildId=356626&view=ms.vss-test-web.build-test-results-tab&runId=7504328&resultId=168374&paneView=debug)
**Failed tests:**
```
net8.0-linux-Release-arm-CoreCLR_checked-no_tiered_compilation-(Ubuntu.1804.Arm32.Open)Ubuntu.1804.Armarch.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:ubuntu-18.04-helix-arm32v7
- System.Threading.ThreadPools.Tests.ThreadPoolTests.FileStreamFlushAsyncThreadPoolDeadlockTest
net8.0-windows-Release-x86-CoreCLR_checked-zapdisable-Windows.10.Amd64.Open
- BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGenerationRollover
```
**Error message:**
```
Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Half-way through waiting for remote process.
Timed out at 7/30/2023 7:58:09 AM after 60000ms waiting for remote process.
Process ID: 307
Handle: 1412
Name: dotnet
MainModule: /root/helix/work/correlation/dotnet
StartTime: 7/30/2023 7:57:09 AM
TotalProcessorTime: 00:00:05.1800000
```
**Stack trace:**
```
at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose(Boolean disposing) in /_/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs:line 225
at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) in /_/src/coreclr/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.CoreCLR.cs:line 36
at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.cs:line 57
```
| 1.0 | Test failure System.Threading.ThreadPools.Tests.ThreadPoolTests.FileStreamFlushAsyncThreadPoolDeadlockTest - **Failed in:** [runtime-coreclr libraries-jitstress 20230730.1](https://dev.azure.com/dnceng-public/public/_build/results?buildId=356626&view=ms.vss-test-web.build-test-results-tab&runId=7504328&resultId=168374&paneView=debug)
**Failed tests:**
```
net8.0-linux-Release-arm-CoreCLR_checked-no_tiered_compilation-(Ubuntu.1804.Arm32.Open)Ubuntu.1804.Armarch.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:ubuntu-18.04-helix-arm32v7
- System.Threading.ThreadPools.Tests.ThreadPoolTests.FileStreamFlushAsyncThreadPoolDeadlockTest
net8.0-windows-Release-x86-CoreCLR_checked-zapdisable-Windows.10.Amd64.Open
- BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGenerationRollover
```
**Error message:**
```
Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Half-way through waiting for remote process.
Timed out at 7/30/2023 7:58:09 AM after 60000ms waiting for remote process.
Process ID: 307
Handle: 1412
Name: dotnet
MainModule: /root/helix/work/correlation/dotnet
StartTime: 7/30/2023 7:57:09 AM
TotalProcessorTime: 00:00:05.1800000
```
**Stack trace:**
```
at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose(Boolean disposing) in /_/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs:line 225
at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) in /_/src/coreclr/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.CoreCLR.cs:line 36
at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.cs:line 57
```
| non_infrastructure | test failure system threading threadpools tests threadpooltests filestreamflushasyncthreadpooldeadlocktest failed in failed tests linux release arm coreclr checked no tiered compilation ubuntu open ubuntu armarch open mcr microsoft com dotnet buildtools prereqs ubuntu helix system threading threadpools tests threadpooltests filestreamflushasyncthreadpooldeadlocktest windows release coreclr checked zapdisable windows open basiceventsourcetests testsmanifestgeneration test eventsource etwmanifestgenerationrollover error message microsoft dotnet remoteexecutor remoteexecutionexception half way through waiting for remote process timed out at am after waiting for remote process process id handle name dotnet mainmodule root helix work correlation dotnet starttime am totalprocessortime stack trace at microsoft dotnet remoteexecutor remoteinvokehandle dispose boolean disposing in src microsoft dotnet remoteexecutor src remoteinvokehandle cs line at system runtimemethodhandle invokemethod object target void arguments signature sig boolean isconstructor at system reflection methodbaseinvoker interpretedinvoke method object obj intptr args in src coreclr system private corelib src system reflection methodbaseinvoker coreclr cs line at system reflection methodbaseinvoker invokewithnoargs object obj bindingflags invokeattr in src libraries system private corelib src system reflection methodbaseinvoker cs line | 0 |
7,148 | 10,289,323,736 | IssuesEvent | 2019-08-27 15:35:53 | Holmeyoung/blog-comment | https://api.github.com/repos/Holmeyoung/blog-comment | opened | python 多线程与多进程 | 一只羊的碎碎念 | /python-threading-multiprocessing/ Gitalk | https://www.holmeyoung.com/python-threading-multiprocessing/
多进程进程池阻塞与非阻塞 异步进程池（非阻塞）123456789101112131415161718from multiprocessing import Pooldef test(i): print (i)if __name__=="__main__": pool = Pool(processes=10) for i in xrange(500): ''' For循环中执行步骤： | 1.0 | python 多线程与多进程 | 一只羊的碎碎念 - https://www.holmeyoung.com/python-threading-multiprocessing/
多进程进程池阻塞与非阻塞 异步进程池（非阻塞）123456789101112131415161718from multiprocessing import Pooldef test(i): print (i)if __name__=="__main__": pool = Pool(processes=10) for i in xrange(500): ''' For循环中执行步骤： | non_infrastructure | python 多线程与多进程 一只羊的碎碎念 多进程进程池阻塞与非阻塞 异步进程池（非阻塞） multiprocessing import pooldef test i print i if name main pool pool processes for i in xrange for循环中执行步骤： | 0 |
9,818 | 8,183,038,545 | IssuesEvent | 2018-08-29 07:47:59 | flutter/website | https://api.github.com/repos/flutter/website | opened | Cirrus builds are failing: "INVALID_ARGUMENT: No tasks found to start!" | Infrastructure | For example see: https://cirrus-ci.com/build/6391154123735040
The issue seems to be because of this contional: https://github.com/flutter/website/blob/568fc345160ed88c21ee2a52b706a4e58d0c994d/.cirrus.yml#L4-L6
As I'd mentioned [elsewhere](https://github.com/flutter/website/pull/1197/files#r213567319), AFAICT, there is no `CIRRUS_PR` environment variable defined for PR builds that originate from a branch on the website repo (see below for an example list of variables), and it would seem that `$CIRRUS_PR != ''` isn't true in that case.
```nocode
CIRRUS_BRANCH=chalin-jekyll-assets-0828
CIRRUS_BUILD_ID=6358354465128448
CIRRUS_CHANGE_IN_REPO=d1b309d7e8a23dd89c21bf3c3d5c32bbc7199c8a
CIRRUS_CI=true
CIRRUS_DEFAULT_BRANCH=master
CIRRUS_HTTP_CACHE_HOST=127.0.0.1:12321
CIRRUS_OS=linux
CIRRUS_REPO_CLONE_HOST=github.com
CIRRUS_REPO_CLONE_URL=https://github.com/flutter/website.git
CIRRUS_REPO_FULL_NAME=flutter/website
CIRRUS_REPO_NAME=website
CIRRUS_REPO_OWNER=flutter
CIRRUS_TASK_ID=6616932836966400
CIRRUS_TASK_NAME=website
CIRRUS_WORKING_DIR=/opt/website
```
Maybe the conditional should instead be:
```yaml
website_task:
# Only run this task on non-master or PR builds.
only_if: $CIRRUS_BRANCH != master || $CIRRUS_PR != ''
```
cc @Sfshaza
| 1.0 | Cirrus builds are failing: "INVALID_ARGUMENT: No tasks found to start!" - For example see: https://cirrus-ci.com/build/6391154123735040
The issue seems to be because of this contional: https://github.com/flutter/website/blob/568fc345160ed88c21ee2a52b706a4e58d0c994d/.cirrus.yml#L4-L6
As I'd mentioned [elsewhere](https://github.com/flutter/website/pull/1197/files#r213567319), AFAICT, there is no `CIRRUS_PR` environment variable defined for PR builds that originate from a branch on the website repo (see below for an example list of variables), and it would seem that `$CIRRUS_PR != ''` isn't true in that case.
```nocode
CIRRUS_BRANCH=chalin-jekyll-assets-0828
CIRRUS_BUILD_ID=6358354465128448
CIRRUS_CHANGE_IN_REPO=d1b309d7e8a23dd89c21bf3c3d5c32bbc7199c8a
CIRRUS_CI=true
CIRRUS_DEFAULT_BRANCH=master
CIRRUS_HTTP_CACHE_HOST=127.0.0.1:12321
CIRRUS_OS=linux
CIRRUS_REPO_CLONE_HOST=github.com
CIRRUS_REPO_CLONE_URL=https://github.com/flutter/website.git
CIRRUS_REPO_FULL_NAME=flutter/website
CIRRUS_REPO_NAME=website
CIRRUS_REPO_OWNER=flutter
CIRRUS_TASK_ID=6616932836966400
CIRRUS_TASK_NAME=website
CIRRUS_WORKING_DIR=/opt/website
```
Maybe the conditional should instead be:
```yaml
website_task:
# Only run this task on non-master or PR builds.
only_if: $CIRRUS_BRANCH != master || $CIRRUS_PR != ''
```
cc @Sfshaza
| infrastructure | cirrus builds are failing invalid argument no tasks found to start for example see the issue seems to be because of this contional as i d mentioned afaict there is no cirrus pr environment variable defined for pr builds that originate from a branch on the website repo see below for an example list of variables and it would seem that cirrus pr isn t true in that case nocode cirrus branch chalin jekyll assets cirrus build id cirrus change in repo cirrus ci true cirrus default branch master cirrus http cache host cirrus os linux cirrus repo clone host github com cirrus repo clone url cirrus repo full name flutter website cirrus repo name website cirrus repo owner flutter cirrus task id cirrus task name website cirrus working dir opt website maybe the conditional should instead be yaml website task only run this task on non master or pr builds only if cirrus branch master cirrus pr cc sfshaza | 1 |
71,787 | 8,681,405,236 | IssuesEvent | 2018-12-01 19:56:19 | Liareth/SiriusPlanning | https://api.github.com/repos/Liareth/SiriusPlanning | opened | Psionics | design | We need to plan out every psionic ability and consider how they intend to feel in-game. | 1.0 | Psionics - We need to plan out every psionic ability and consider how they intend to feel in-game. | non_infrastructure | psionics we need to plan out every psionic ability and consider how they intend to feel in game | 0 |
8,399 | 7,388,637,382 | IssuesEvent | 2018-03-16 03:56:50 | JMRI/JMRI | https://api.github.com/repos/JMRI/JMRI | reopened | Frequent Intermittent CI Failures | Bug dev/test/publish infrastructure | CI tests are frequently but intermittently failing with:
```
[ERROR] Errors:
[ERROR] AudioCommandTest.testCTor:19 ExceptionInInitializer
[ERROR] SoundBiteTest.TestSetGet:44 » NoClassDefFound Could not initialize class jmri....
[ERROR] SoundBiteTest.testCreateFull:33 » NoClassDefFound Could not initialize class j...
[ERROR] SoundBiteTest.testCreateSimple:24 » NoClassDefFound Could not initialize class...
[ERROR] SoundBiteTest.testSetXML:60 » NoClassDefFound Could not initialize class jmri....
[ERROR] VSDSoundTest.testCreateSimple:25 » NoClassDefFound Could not initialize class ...
[ERROR] VSDSoundTest.testSetGet:31 » NoClassDefFound Could not initialize class jmri.j...
[ERROR] VSDSoundTest.testSetXML:44 » NoClassDefFound Could not initialize class jmri.j...
```
I have not found a pattern yet, but I think that the failure in the constructor is causing later NoClassDefFound errors since the NullAudioSource extends AbstractAudioSource which is failing to initialize some private static fields in the first failure.
These failures appear to have been introduced by #3670. | 1.0 | Frequent Intermittent CI Failures - CI tests are frequently but intermittently failing with:
```
[ERROR] Errors:
[ERROR] AudioCommandTest.testCTor:19 ExceptionInInitializer
[ERROR] SoundBiteTest.TestSetGet:44 » NoClassDefFound Could not initialize class jmri....
[ERROR] SoundBiteTest.testCreateFull:33 » NoClassDefFound Could not initialize class j...
[ERROR] SoundBiteTest.testCreateSimple:24 » NoClassDefFound Could not initialize class...
[ERROR] SoundBiteTest.testSetXML:60 » NoClassDefFound Could not initialize class jmri....
[ERROR] VSDSoundTest.testCreateSimple:25 » NoClassDefFound Could not initialize class ...
[ERROR] VSDSoundTest.testSetGet:31 » NoClassDefFound Could not initialize class jmri.j...
[ERROR] VSDSoundTest.testSetXML:44 » NoClassDefFound Could not initialize class jmri.j...
```
I have not found a pattern yet, but I think that the failure in the constructor is causing later NoClassDefFound errors since the NullAudioSource extends AbstractAudioSource which is failing to initialize some private static fields in the first failure.
These failures appear to have been introduced by #3670. | infrastructure | frequent intermittent ci failures ci tests are frequently but intermittently failing with errors audiocommandtest testctor exceptionininitializer soundbitetest testsetget » noclassdeffound could not initialize class jmri soundbitetest testcreatefull » noclassdeffound could not initialize class j soundbitetest testcreatesimple » noclassdeffound could not initialize class soundbitetest testsetxml » noclassdeffound could not initialize class jmri vsdsoundtest testcreatesimple » noclassdeffound could not initialize class vsdsoundtest testsetget » noclassdeffound could not initialize class jmri j vsdsoundtest testsetxml » noclassdeffound could not initialize class jmri j i have not found a pattern yet but i think that the failure in the constructor is causing later noclassdeffound errors since the nullaudiosource extends abstractaudiosource which is failing to initialize some private static fields in the first failure these failures appear to have been introduced by | 1 |
24,835 | 17,838,217,175 | IssuesEvent | 2021-09-03 06:20:14 | Budibase/budibase | https://api.github.com/repos/Budibase/budibase | closed | Budibase x Kubernetes - Infra | infrastructure | Bring up the budibase stack in a EKS kubernetes cluster in AWS eu-west-1.
**Infra**
- Proxy
- Worker
- Apps
- CouchDB
- S3 instead of MinIO
- Elasticache instead of redis
**CouchDB**
We will need an EFS volume for all the couchDB pods in the cluster to use and share. Each node will need to be registered as part of this cluster.
**Conditions of Satisfaction**
- We have fully configurable yaml/helm configuration for bringing up budibase in K8S
- The entire stack is up and running in us-east-1 and we can use it the same way we use our staging env
| 1.0 | Budibase x Kubernetes - Infra - Bring up the budibase stack in a EKS kubernetes cluster in AWS eu-west-1.
**Infra**
- Proxy
- Worker
- Apps
- CouchDB
- S3 instead of MinIO
- Elasticache instead of redis
**CouchDB**
We will need an EFS volume for all the couchDB pods in the cluster to use and share. Each node will need to be registered as part of this cluster.
**Conditions of Satisfaction**
- We have fully configurable yaml/helm configuration for bringing up budibase in K8S
- The entire stack is up and running in us-east-1 and we can use it the same way we use our staging env
| infrastructure | budibase x kubernetes infra bring up the budibase stack in a eks kubernetes cluster in aws eu west infra proxy worker apps couchdb instead of minio elasticache instead of redis couchdb we will need an efs volume for all the couchdb pods in the cluster to use and share each node will need to be registered as part of this cluster conditions of satisfaction we have fully configurable yaml helm configuration for bringing up budibase in the entire stack is up and running in us east and we can use it the same way we use our staging env | 1 |
26,717 | 20,603,011,848 | IssuesEvent | 2022-03-06 15:07:40 | rdnfn/beobench | https://api.github.com/repos/rdnfn/beobench | opened | Docker-in-docker does not work on remote machine | bug concerns: infrastructure | ## Problem
Currently the docker does not work in the remote devcontainer. Both the remote and the standard devcontainer have no functioning docker on the remote machine. Locally docker is available in the devcontainer. Likely a problem with the docker installation on the remote machine.
## Solution
Check problem with remote docker installation.
| 1.0 | Docker-in-docker does not work on remote machine - ## Problem
Currently the docker does not work in the remote devcontainer. Both the remote and the standard devcontainer have no functioning docker on the remote machine. Locally docker is available in the devcontainer. Likely a problem with the docker installation on the remote machine.
## Solution
Check problem with remote docker installation.
| infrastructure | docker in docker does not work on remote machine problem currently the docker does not work in the remote devcontainer both the remote and the standard devcontainer have no functioning docker on the remote machine locally docker is available in the devcontainer likely a problem with the docker installation on the remote machine solution check problem with remote docker installation | 1 |
116,494 | 24,927,988,270 | IssuesEvent | 2022-10-31 09:13:05 | joomla/joomla-cms | https://api.github.com/repos/joomla/joomla-cms | closed | Multi-Language in combination with SEO links | No Code Attached Yet | I am not shure if this is a bug or a feature. OR is it just a configuration problem?
As stated in the title, these are problems with combining SEO links and multilingual content. Both are supported features, so they should work together.
I already posted on forum.joomla.org, but do not get any reply to my post.
Following the original post https://forum.joomla.org/viewtopic.php?f=809&t=997383
In the mean time I have simplified the configuration. Since the menues involved in the problem are all one level only, I removed 'Menu Item Alias' entries in the mentioned menues. But the problem still exists.
### Steps to reproduce the issue (múltipe issues!)
Take a browser and visit the website https://bogenparadies.de.
At the very top left there is a small menu for help and contact. At the very top right there is a flag, displayed by the language switcher. Depending on the browser configuration you will see the britisch or the german flag. Since only one flag is shown, the british flag switches to english Content and the german flag switches to german content. In German the menue at the very top left says Hilfe and Kontakt. In English it is Help and Contact.
As stated later under System Information the language codes should be removed from the URL.
Click the german flag and verify that the german help page and contact form are shown when ckicking the corresponding menue entries.
Notice the corresponding URLs are:
https://bogenparadies.de/hilfe
https://bogenparadies.de/kontakt
Click the british flag and verify that the english versions are displayed.
Notice the URLs are:
https://bogenparadies.de/en/help
https://bogenparadies.de/en/contact
The language code is NOT removed. Everything else seems to work.
Now enter the following four URLs one after the other and see what happens in the address field for ervery URL
https://bogenparadies.de/de/kontakt
https://bogenparadies.de/en/contact
https://bogenparadies.de/contact
https://bogenparadies.de/kontakt
Depending of the browser settings, at least one of those links will throw an 404 page not found error
### Expected result
Since the links to https://bogenparadies.de/kontakt to get the german contact form and https://bogenparadies.de/contact to get the english contact form are published, those links should always work.
### Actual result
Depending of the end users browser settings, does he prefer German or English content, the pages are not found.
To verify this configure a browser to delete all cached content when it is closed (cookies and cashed pages).
Configure the browser to have English as the preferred language to display pages.
Quit the browser and wait until it is finished to clean up. Then start it agein.
Now open all four contact links and note which one works or does not.
Then configure the browser to have German as the preferred language to display pages.
Again note which URLs work and which do not.
### System information (as much as possible)
The Site is running on an Internet faceing Debian LAMP server.
In Joomla! 4.2.3 there are three languages installed, but only two of them are currently used.
Joomla! was upgraded from 3.10
One simple Tempate is installed, but not used. The Default Template is Cassiopeia.
No other extensions are installed!
The 'Multilingual Status' says that 'The Language Filter Plugin' is enabled. There is one 'Language Switcher Plugin' published. There are 3 'Default Homepages' published, including 1 assigned to language All. The two languages en-GB and de-DE are both 'Enabled Site Languages', 'Published Content Languages' and 'Published Default Homepages'.
System Language Filter Plugin
All toggle switches are green (enabled).
Language Selection for new Visitors is Browser Settings.
x-default language is en-GB.
Cookie livetime is Session.
System Language Code Plugin
en-GB changed to en
de-DE changed to de
The client computer is using Debian 11.5, the browser used for testing is FireFox 102.4.0esr (64-bit)
### Additional comments
Without Multi-Language Support all links did work correct!
Removing Mutli-Language Support is also no option because assosiating pages for translation and maintanance is an important feature.
| 1.0 | Multi-Language in combination with SEO links - I am not shure if this is a bug or a feature. OR is it just a configuration problem?
As stated in the title, these are problems with combining SEO links and multilingual content. Both are supported features, so they should work together.
I already posted on forum.joomla.org, but do not get any reply to my post.
Following the original post https://forum.joomla.org/viewtopic.php?f=809&t=997383
In the mean time I have simplified the configuration. Since the menues involved in the problem are all one level only, I removed 'Menu Item Alias' entries in the mentioned menues. But the problem still exists.
### Steps to reproduce the issue (múltipe issues!)
Take a browser and visit the website https://bogenparadies.de.
At the very top left there is a small menu for help and contact. At the very top right there is a flag, displayed by the language switcher. Depending on the browser configuration you will see the britisch or the german flag. Since only one flag is shown, the british flag switches to english Content and the german flag switches to german content. In German the menue at the very top left says Hilfe and Kontakt. In English it is Help and Contact.
As stated later under System Information the language codes should be removed from the URL.
Click the german flag and verify that the german help page and contact form are shown when ckicking the corresponding menue entries.
Notice the corresponding URLs are:
https://bogenparadies.de/hilfe
https://bogenparadies.de/kontakt
Click the british flag and verify that the english versions are displayed.
Notice the URLs are:
https://bogenparadies.de/en/help
https://bogenparadies.de/en/contact
The language code is NOT removed. Everything else seems to work.
Now enter the following four URLs one after the other and see what happens in the address field for ervery URL
https://bogenparadies.de/de/kontakt
https://bogenparadies.de/en/contact
https://bogenparadies.de/contact
https://bogenparadies.de/kontakt
Depending of the browser settings, at least one of those links will throw an 404 page not found error
### Expected result
Since the links to https://bogenparadies.de/kontakt to get the german contact form and https://bogenparadies.de/contact to get the english contact form are published, those links should always work.
### Actual result
Depending of the end users browser settings, does he prefer German or English content, the pages are not found.
To verify this configure a browser to delete all cached content when it is closed (cookies and cashed pages).
Configure the browser to have English as the preferred language to display pages.
Quit the browser and wait until it is finished to clean up. Then start it agein.
Now open all four contact links and note which one works or does not.
Then configure the browser to have German as the preferred language to display pages.
Again note which URLs work and which do not.
### System information (as much as possible)
The Site is running on an Internet faceing Debian LAMP server.
In Joomla! 4.2.3 there are three languages installed, but only two of them are currently used.
Joomla! was upgraded from 3.10
One simple Tempate is installed, but not used. The Default Template is Cassiopeia.
No other extensions are installed!
The 'Multilingual Status' says that 'The Language Filter Plugin' is enabled. There is one 'Language Switcher Plugin' published. There are 3 'Default Homepages' published, including 1 assigned to language All. The two languages en-GB and de-DE are both 'Enabled Site Languages', 'Published Content Languages' and 'Published Default Homepages'.
System Language Filter Plugin
All toggle switches are green (enabled).
Language Selection for new Visitors is Browser Settings.
x-default language is en-GB.
Cookie livetime is Session.
System Language Code Plugin
en-GB changed to en
de-DE changed to de
The client computer is using Debian 11.5, the browser used for testing is FireFox 102.4.0esr (64-bit)
### Additional comments
Without Multi-Language Support all links did work correct!
Removing Mutli-Language Support is also no option because assosiating pages for translation and maintanance is an important feature.
| non_infrastructure | multi language in combination with seo links i am not shure if this is a bug or a feature or is it just a configuration problem as stated in the title these are problems with combining seo links and multilingual content both are supported features so they should work together i already posted on forum joomla org but do not get any reply to my post following the original post in the mean time i have simplified the configuration since the menues involved in the problem are all one level only i removed menu item alias entries in the mentioned menues but the problem still exists steps to reproduce the issue múltipe issues take a browser and visit the website at the very top left there is a small menu for help and contact at the very top right there is a flag displayed by the language switcher depending on the browser configuration you will see the britisch or the german flag since only one flag is shown the british flag switches to english content and the german flag switches to german content in german the menue at the very top left says hilfe and kontakt in english it is help and contact as stated later under system information the language codes should be removed from the url click the german flag and verify that the german help page and contact form are shown when ckicking the corresponding menue entries notice the corresponding urls are click the british flag and verify that the english versions are displayed notice the urls are the language code is not removed everything else seems to work now enter the following four urls one after the other and see what happens in the address field for ervery url depending of the browser settings at least one of those links will throw an page not found error expected result since the links to to get the german contact form and to get the english contact form are published those links should always work actual result depending of the end users browser settings does he prefer german or english content the pages are not found to verify this configure a browser to delete all cached content when it is closed cookies and cashed pages configure the browser to have english as the preferred language to display pages quit the browser and wait until it is finished to clean up then start it agein now open all four contact links and note which one works or does not then configure the browser to have german as the preferred language to display pages again note which urls work and which do not system information as much as possible the site is running on an internet faceing debian lamp server in joomla there are three languages installed but only two of them are currently used joomla was upgraded from one simple tempate is installed but not used the default template is cassiopeia no other extensions are installed the multilingual status says that the language filter plugin is enabled there is one language switcher plugin published there are default homepages published including assigned to language all the two languages en gb and de de are both enabled site languages published content languages and published default homepages system language filter plugin all toggle switches are green enabled language selection for new visitors is browser settings x default language is en gb cookie livetime is session system language code plugin en gb changed to en de de changed to de the client computer is using debian the browser used for testing is firefox bit additional comments without multi language support all links did work correct removing mutli language support is also no option because assosiating pages for translation and maintanance is an important feature | 0 |
35,498 | 31,722,503,749 | IssuesEvent | 2023-09-10 15:15:53 | acterglobal/a3 | https://api.github.com/repos/acterglobal/a3 | closed | [tracking] Reporting and blocking of content and users | infrastructure | As an app that shows user generated content to people, we need to add the ability to report content, block users and remove content from a users feed easily and quickly.
At this point, there already exist two UI's that _indicate_ to provide such a feature:
the `...` on an News Item:
and a long-press on a chat message:
What we need:
- [x] implement the [`MemberProfile.ignore`](https://matrix-org.github.io/matrix-rust-sdk/matrix_sdk/room/struct.RoomMember.html#method.ignore) on the rust SDK
- [x] implement [the `report_content` API](https://matrix-org.github.io/matrix-rust-sdk/matrix_sdk_base/ruma/api/client/room/report_content/index.html) on the rust SDK
- [x] Create a singular [report-content flow](https://github.com/acterglobal/a3/issues/913) (based on the UI of the news item)
- [x] hook that up to:
- [x] News
- [x] Pins
- [x] Events
- [x] Chat Room Message
- [x] Add the ability to ignore a User from the chat screen as well as the space-members screen, #927
| 1.0 | [tracking] Reporting and blocking of content and users - As an app that shows user generated content to people, we need to add the ability to report content, block users and remove content from a users feed easily and quickly.
At this point, there already exist two UI's that _indicate_ to provide such a feature:
the `...` on an News Item:
and a long-press on a chat message:
What we need:
- [x] implement the [`MemberProfile.ignore`](https://matrix-org.github.io/matrix-rust-sdk/matrix_sdk/room/struct.RoomMember.html#method.ignore) on the rust SDK
- [x] implement [the `report_content` API](https://matrix-org.github.io/matrix-rust-sdk/matrix_sdk_base/ruma/api/client/room/report_content/index.html) on the rust SDK
- [x] Create a singular [report-content flow](https://github.com/acterglobal/a3/issues/913) (based on the UI of the news item)
- [x] hook that up to:
- [x] News
- [x] Pins
- [x] Events
- [x] Chat Room Message
- [x] Add the ability to ignore a User from the chat screen as well as the space-members screen, #927
| infrastructure | reporting and blocking of content and users as an app that shows user generated content to people we need to add the ability to report content block users and remove content from a users feed easily and quickly at this point there already exist two ui s that indicate to provide such a feature the on an news item and a long press on a chat message what we need implement the on the rust sdk implement on the rust sdk create a singular based on the ui of the news item hook that up to news pins events chat room message add the ability to ignore a user from the chat screen as well as the space members screen | 1 |
31,130 | 25,347,938,354 | IssuesEvent | 2022-11-19 12:25:46 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | Local test run fails to analyze HardwareIntrinsics test results | area-Infrastructure-coreclr in-pr | After a local crossgen2 tests run, using `.\src\tests\run.cmd checked runcrossgen2tests`, I hit
```
Analyzing C:\dev\dotnet\runtime2\artifacts\log\JIT.HardwareIntrinsics.HardwareIntrinsics_r.testRun.xml
Analyzing C:\dev\dotnet\runtime2\artifacts\log\JIT.HardwareIntrinsics.HardwareIntrinsics_ro.testRun.xml
Traceback (most recent call last):
File "C:\dev\dotnet\runtime2\src\tests\run.py", line 1411, in <module>
sys.exit(main(args))
File "C:\dev\dotnet\runtime2\src\tests\run.py", line 1399, in main
parse_test_results(args, tests, assemblies)
File "C:\dev\dotnet\runtime2\src\tests\run.py", line 1196, in parse_test_results
parse_test_results_xml_file(args, item, item_name, tests, assemblies)
File "C:\dev\dotnet\runtime2\src\tests\run.py", line 1255, in parse_test_results_xml_file
assert tests[test_name] == None
AssertionError
```
There is a test named `JIT.HardwareIntrinsics.Arm::Abs_Vector128_Double (global::JIT.HardwareIntrinsics.Arm._AdvSimd.Arm64.Program.Abs_Vector128_Double())` in both `JIT.HardwareIntrinsics.HardwareIntrinsics_r.testRun.xml` and `JIT.HardwareIntrinsics.HardwareIntrinsics_ro.testRun.xml` which causes the assert.
Does the analysis need to disambiguate by the assembly somehow too?
cc @davidwrighton, presumably related to your recent changes here | 1.0 | Local test run fails to analyze HardwareIntrinsics test results - After a local crossgen2 tests run, using `.\src\tests\run.cmd checked runcrossgen2tests`, I hit
```
Analyzing C:\dev\dotnet\runtime2\artifacts\log\JIT.HardwareIntrinsics.HardwareIntrinsics_r.testRun.xml
Analyzing C:\dev\dotnet\runtime2\artifacts\log\JIT.HardwareIntrinsics.HardwareIntrinsics_ro.testRun.xml
Traceback (most recent call last):
File "C:\dev\dotnet\runtime2\src\tests\run.py", line 1411, in <module>
sys.exit(main(args))
File "C:\dev\dotnet\runtime2\src\tests\run.py", line 1399, in main
parse_test_results(args, tests, assemblies)
File "C:\dev\dotnet\runtime2\src\tests\run.py", line 1196, in parse_test_results
parse_test_results_xml_file(args, item, item_name, tests, assemblies)
File "C:\dev\dotnet\runtime2\src\tests\run.py", line 1255, in parse_test_results_xml_file
assert tests[test_name] == None
AssertionError
```
There is a test named `JIT.HardwareIntrinsics.Arm::Abs_Vector128_Double (global::JIT.HardwareIntrinsics.Arm._AdvSimd.Arm64.Program.Abs_Vector128_Double())` in both `JIT.HardwareIntrinsics.HardwareIntrinsics_r.testRun.xml` and `JIT.HardwareIntrinsics.HardwareIntrinsics_ro.testRun.xml` which causes the assert.
Does the analysis need to disambiguate by the assembly somehow too?
cc @davidwrighton, presumably related to your recent changes here | infrastructure | local test run fails to analyze hardwareintrinsics test results after a local tests run using src tests run cmd checked i hit analyzing c dev dotnet artifacts log jit hardwareintrinsics hardwareintrinsics r testrun xml analyzing c dev dotnet artifacts log jit hardwareintrinsics hardwareintrinsics ro testrun xml traceback most recent call last file c dev dotnet src tests run py line in sys exit main args file c dev dotnet src tests run py line in main parse test results args tests assemblies file c dev dotnet src tests run py line in parse test results parse test results xml file args item item name tests assemblies file c dev dotnet src tests run py line in parse test results xml file assert tests none assertionerror there is a test named jit hardwareintrinsics arm abs double global jit hardwareintrinsics arm advsimd program abs double in both jit hardwareintrinsics hardwareintrinsics r testrun xml and jit hardwareintrinsics hardwareintrinsics ro testrun xml which causes the assert does the analysis need to disambiguate by the assembly somehow too cc davidwrighton presumably related to your recent changes here | 1 |
17,049 | 12,214,125,804 | IssuesEvent | 2020-05-01 09:03:59 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | reopened | Project '..' targets 'net5.0'. It cannot be referenced by a project that targets '.NETCoreApp,Version=v5.0' | area-Infrastructure-libraries | While trying to reference a NET5.0 class library project from a NET5.0 WinForm project I get the error stated in the title:
> Project 'classlib.csproj' targets 'net5.0'. It cannot be referenced by a project that targets '.NETCoreApp,Version=v5.0' | 1.0 | Project '..' targets 'net5.0'. It cannot be referenced by a project that targets '.NETCoreApp,Version=v5.0' - While trying to reference a NET5.0 class library project from a NET5.0 WinForm project I get the error stated in the title:
> Project 'classlib.csproj' targets 'net5.0'. It cannot be referenced by a project that targets '.NETCoreApp,Version=v5.0' | infrastructure | project targets it cannot be referenced by a project that targets netcoreapp version while trying to reference a class library project from a winform project i get the error stated in the title project classlib csproj targets it cannot be referenced by a project that targets netcoreapp version | 1 |
20,679 | 14,099,383,920 | IssuesEvent | 2020-11-06 01:14:58 | noahtalerman/test-issues-kolide | https://api.github.com/repos/noahtalerman/test-issues-kolide | opened | [CLOSED] Lower test verbosity in Makefile | Component: Development Infrastructure | <a href="https://github.com/marpaia"><img src="https://avatars2.githubusercontent.com/u/927168?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [marpaia](https://github.com/marpaia)**
_Monday Oct 03, 2016 at 03:19 GMT_
_Originally opened as https://github.com/kolide/fleet/pull/259_
----
I think that the output here is much more useful when allowing go to
determine when the output of a test should be displayed.
----
_**[marpaia](https://github.com/marpaia)** included the following code: https://github.com/kolide/fleet/pull/259/commits_
| 1.0 | [CLOSED] Lower test verbosity in Makefile - <a href="https://github.com/marpaia"><img src="https://avatars2.githubusercontent.com/u/927168?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [marpaia](https://github.com/marpaia)**
_Monday Oct 03, 2016 at 03:19 GMT_
_Originally opened as https://github.com/kolide/fleet/pull/259_
----
I think that the output here is much more useful when allowing go to
determine when the output of a test should be displayed.
----
_**[marpaia](https://github.com/marpaia)** included the following code: https://github.com/kolide/fleet/pull/259/commits_
| infrastructure | lower test verbosity in makefile issue by monday oct at gmt originally opened as i think that the output here is much more useful when allowing go to determine when the output of a test should be displayed included the following code | 1 |
14,970 | 11,274,272,304 | IssuesEvent | 2020-01-14 18:12:46 | cashapp/sqldelight | https://api.github.com/repos/cashapp/sqldelight | closed | Use Travis CI build stages | enhancement infrastructure | https://docs.travis-ci.com/user/build-stages
This should allow us to prevent snapshot deployment until linux and mac os pass. The downside is that we can't easily share artifacts so we would have to rebuild on mac os to deploy everything as the final stage.
(Circle CI would let us do partial builds on multiple platforms, aggregate, and publish) | 1.0 | Use Travis CI build stages - https://docs.travis-ci.com/user/build-stages
This should allow us to prevent snapshot deployment until linux and mac os pass. The downside is that we can't easily share artifacts so we would have to rebuild on mac os to deploy everything as the final stage.
(Circle CI would let us do partial builds on multiple platforms, aggregate, and publish) | infrastructure | use travis ci build stages this should allow us to prevent snapshot deployment until linux and mac os pass the downside is that we can t easily share artifacts so we would have to rebuild on mac os to deploy everything as the final stage circle ci would let us do partial builds on multiple platforms aggregate and publish | 1 |
740,045 | 25,733,771,851 | IssuesEvent | 2022-12-07 22:34:39 | projectLEMDO/lemdoIssues | https://api.github.com/repos/projectLEMDO/lemdoIssues | closed | All hard-coded strings should be abstracted to a captions module | enhancement Priority: low go for it | There are lots of captions which are hard-coded into the XSLT, dating back years (for example, the captions in the left column of the Metadata table). These should be abstracted into a central captions module. | 1.0 | All hard-coded strings should be abstracted to a captions module - There are lots of captions which are hard-coded into the XSLT, dating back years (for example, the captions in the left column of the Metadata table). These should be abstracted into a central captions module. | non_infrastructure | all hard coded strings should be abstracted to a captions module there are lots of captions which are hard coded into the xslt dating back years for example the captions in the left column of the metadata table these should be abstracted into a central captions module | 0 |
106,421 | 16,673,362,015 | IssuesEvent | 2021-06-07 13:36:11 | VivekBuzruk/Hygieia | https://api.github.com/repos/VivekBuzruk/Hygieia | closed | WS-2018-0103 (Medium) detected in stringstream-0.0.5.tgz - autoclosed | security vulnerability | ## WS-2018-0103 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>stringstream-0.0.5.tgz</b></p></summary>
<p>Encode and decode streams into string streams</p>
<p>Library home page: <a href="https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz">https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz</a></p>
<p>Path to dependency file: Hygieia/UI-protractor-tests/package.json</p>
<p>Path to vulnerable library: Hygieia/UI-protractor-tests/node_modules/npm/node_modules/request/node_modules/stringstream/package.json</p>
<p>
Dependency Hierarchy:
- npm-failsafe-0.1.1.tgz (Root Library)
- npm-2.15.12.tgz
- request-2.74.0.tgz
- :x: **stringstream-0.0.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://api.github.com/repos/VivekBuzruk/Hygieia/commits/3c4f119e4343cf7fa276bb4756361b926902248e">3c4f119e4343cf7fa276bb4756361b926902248e</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
All versions of stringstream are vulnerable to out-of-bounds read as it allocates uninitialized Buffers when number is passed in input stream on Node.js 4.x and below.
<p>Publish Date: 2018-05-16
<p>URL: <a href=https://hackerone.com/reports/321670>WS-2018-0103</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>4.8</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: 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>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nodesecurity.io/advisories/664">https://nodesecurity.io/advisories/664</a></p>
<p>Release Date: 2018-01-27</p>
<p>Fix Resolution: 0.0.6</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2018-0103 (Medium) detected in stringstream-0.0.5.tgz - autoclosed - ## WS-2018-0103 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>stringstream-0.0.5.tgz</b></p></summary>
<p>Encode and decode streams into string streams</p>
<p>Library home page: <a href="https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz">https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz</a></p>
<p>Path to dependency file: Hygieia/UI-protractor-tests/package.json</p>
<p>Path to vulnerable library: Hygieia/UI-protractor-tests/node_modules/npm/node_modules/request/node_modules/stringstream/package.json</p>
<p>
Dependency Hierarchy:
- npm-failsafe-0.1.1.tgz (Root Library)
- npm-2.15.12.tgz
- request-2.74.0.tgz
- :x: **stringstream-0.0.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://api.github.com/repos/VivekBuzruk/Hygieia/commits/3c4f119e4343cf7fa276bb4756361b926902248e">3c4f119e4343cf7fa276bb4756361b926902248e</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
All versions of stringstream are vulnerable to out-of-bounds read as it allocates uninitialized Buffers when number is passed in input stream on Node.js 4.x and below.
<p>Publish Date: 2018-05-16
<p>URL: <a href=https://hackerone.com/reports/321670>WS-2018-0103</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>4.8</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: 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>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nodesecurity.io/advisories/664">https://nodesecurity.io/advisories/664</a></p>
<p>Release Date: 2018-01-27</p>
<p>Fix Resolution: 0.0.6</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_infrastructure | ws medium detected in stringstream tgz autoclosed ws medium severity vulnerability vulnerable library stringstream tgz encode and decode streams into string streams library home page a href path to dependency file hygieia ui protractor tests package json path to vulnerable library hygieia ui protractor tests node modules npm node modules request node modules stringstream package json dependency hierarchy npm failsafe tgz root library npm tgz request tgz x stringstream tgz vulnerable library found in head commit a href found in base branch master vulnerability details all versions of stringstream are vulnerable to out of bounds read as it allocates uninitialized buffers when number is passed in input stream on node js x and below 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 none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
5,456 | 5,661,313,862 | IssuesEvent | 2017-04-10 17:03:37 | openshift/origin | https://api.github.com/repos/openshift/origin | closed | OPENSHIFT_ANSIBLE_PULL_ID: unbound variable | area/infrastructure kind/bug | ```
########## STARTING STAGE: SYNC OPENSHIFT-ANSIBLE PULL REQUEST ##########
+ [[ -s /var/lib/jenkins/jobs/test_pull_request_origin_extended_conformance_install_update/workspace/activate ]]
+ source /var/lib/jenkins/jobs/test_pull_request_origin_extended_conformance_install_update/workspace/activate
++ export VIRTUAL_ENV=/var/lib/jenkins/origin-ci-tool/66c7a62841fd7219eba155679e0b64ce34e81628
++ VIRTUAL_ENV=/var/lib/jenkins/origin-ci-tool/66c7a62841fd7219eba155679e0b64ce34e81628
++ export PATH=/var/lib/jenkins/origin-ci-tool/66c7a62841fd7219eba155679e0b64ce34e81628/bin:/sbin:/usr/sbin:/bin:/usr/bin
++ PATH=/var/lib/jenkins/origin-ci-tool/66c7a62841fd7219eba155679e0b64ce34e81628/bin:/sbin:/usr/sbin:/bin:/usr/bin
++ unset PYTHON_HOME
++ export OCT_CONFIG_HOME=/var/lib/jenkins/jobs/test_pull_request_origin_extended_conformance_install_update/workspace/.config
++ OCT_CONFIG_HOME=/var/lib/jenkins/jobs/test_pull_request_origin_extended_conformance_install_update/workspace/.config
/tmp/hudson8988133873819713627.sh: line 3: OPENSHIFT_ANSIBLE_PULL_ID: unbound variable
++ set +o xtrace
/tmp/hudson8988133873819713627.sh: line 1: OPENSHIFT_ANSIBLE_PULL_ID: unbound variable
Build step 'Execute shell' marked build as failure
```
Seen here: https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_install_update/17/console
CC @stevekuznetsov | 1.0 | OPENSHIFT_ANSIBLE_PULL_ID: unbound variable - ```
########## STARTING STAGE: SYNC OPENSHIFT-ANSIBLE PULL REQUEST ##########
+ [[ -s /var/lib/jenkins/jobs/test_pull_request_origin_extended_conformance_install_update/workspace/activate ]]
+ source /var/lib/jenkins/jobs/test_pull_request_origin_extended_conformance_install_update/workspace/activate
++ export VIRTUAL_ENV=/var/lib/jenkins/origin-ci-tool/66c7a62841fd7219eba155679e0b64ce34e81628
++ VIRTUAL_ENV=/var/lib/jenkins/origin-ci-tool/66c7a62841fd7219eba155679e0b64ce34e81628
++ export PATH=/var/lib/jenkins/origin-ci-tool/66c7a62841fd7219eba155679e0b64ce34e81628/bin:/sbin:/usr/sbin:/bin:/usr/bin
++ PATH=/var/lib/jenkins/origin-ci-tool/66c7a62841fd7219eba155679e0b64ce34e81628/bin:/sbin:/usr/sbin:/bin:/usr/bin
++ unset PYTHON_HOME
++ export OCT_CONFIG_HOME=/var/lib/jenkins/jobs/test_pull_request_origin_extended_conformance_install_update/workspace/.config
++ OCT_CONFIG_HOME=/var/lib/jenkins/jobs/test_pull_request_origin_extended_conformance_install_update/workspace/.config
/tmp/hudson8988133873819713627.sh: line 3: OPENSHIFT_ANSIBLE_PULL_ID: unbound variable
++ set +o xtrace
/tmp/hudson8988133873819713627.sh: line 1: OPENSHIFT_ANSIBLE_PULL_ID: unbound variable
Build step 'Execute shell' marked build as failure
```
Seen here: https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_install_update/17/console
CC @stevekuznetsov | infrastructure | openshift ansible pull id unbound variable starting stage sync openshift ansible pull request source var lib jenkins jobs test pull request origin extended conformance install update workspace activate export virtual env var lib jenkins origin ci tool virtual env var lib jenkins origin ci tool export path var lib jenkins origin ci tool bin sbin usr sbin bin usr bin path var lib jenkins origin ci tool bin sbin usr sbin bin usr bin unset python home export oct config home var lib jenkins jobs test pull request origin extended conformance install update workspace config oct config home var lib jenkins jobs test pull request origin extended conformance install update workspace config tmp sh line openshift ansible pull id unbound variable set o xtrace tmp sh line openshift ansible pull id unbound variable build step execute shell marked build as failure seen here cc stevekuznetsov | 1 |
11,747 | 9,415,768,302 | IssuesEvent | 2019-04-10 13:22:35 | nest/nest-simulator | https://api.github.com/repos/nest/nest-simulator | closed | Restore PyNEST functions to the top level module | C: Infrastructure I: User Interface P: PR Created S: Low T: Maintenance | With the restructuring of PyNEST in #1058, some low-level functions are no longer available from the top level `nest` module, but hidden in either `hl_api` or `ll_api`, which is great.
However, there are some functions that are not in the top level which could belong there:
- `PrintNetwork`
- `message`
- `set_verbosity`
- `get_verbosity`
Most of these functions are used in examples, so if we decide to not make these functions accessible from the top level `nest` module all examples using them have to be changed. | 1.0 | Restore PyNEST functions to the top level module - With the restructuring of PyNEST in #1058, some low-level functions are no longer available from the top level `nest` module, but hidden in either `hl_api` or `ll_api`, which is great.
However, there are some functions that are not in the top level which could belong there:
- `PrintNetwork`
- `message`
- `set_verbosity`
- `get_verbosity`
Most of these functions are used in examples, so if we decide to not make these functions accessible from the top level `nest` module all examples using them have to be changed. | infrastructure | restore pynest functions to the top level module with the restructuring of pynest in some low level functions are no longer available from the top level nest module but hidden in either hl api or ll api which is great however there are some functions that are not in the top level which could belong there printnetwork message set verbosity get verbosity most of these functions are used in examples so if we decide to not make these functions accessible from the top level nest module all examples using them have to be changed | 1 |
18,939 | 13,170,546,211 | IssuesEvent | 2020-08-11 15:18:43 | ansible/galaxy_ng | https://api.github.com/repos/ansible/galaxy_ng | closed | Infra: Application specific migrations on OSD4 | area/infrastructure priority/high sprint/4 status/new type/enhancement | Some data migrations cannot be part of the application migrations as they contain environment specific logic (i.e. switching from single public repository to public \ certified \ namespace-per-repository), and different security policies for SaaS and On-Premise environments.
We currently solve this by manually running the `django-admin` CLI tool to apply fixtures and migration scripts. In an OSD4 AppSRE environment we will not have access to perform this operation, so we'll need to build a solution using an Operator or an Init Container.
| 1.0 | Infra: Application specific migrations on OSD4 - Some data migrations cannot be part of the application migrations as they contain environment specific logic (i.e. switching from single public repository to public \ certified \ namespace-per-repository), and different security policies for SaaS and On-Premise environments.
We currently solve this by manually running the `django-admin` CLI tool to apply fixtures and migration scripts. In an OSD4 AppSRE environment we will not have access to perform this operation, so we'll need to build a solution using an Operator or an Init Container.
| infrastructure | infra application specific migrations on some data migrations cannot be part of the application migrations as they contain environment specific logic i e switching from single public repository to public certified namespace per repository and different security policies for saas and on premise environments we currently solve this by manually running the django admin cli tool to apply fixtures and migration scripts in an appsre environment we will not have access to perform this operation so we ll need to build a solution using an operator or an init container | 1 |
15,256 | 3,321,403,376 | IssuesEvent | 2015-11-09 08:43:17 | osakagamba/7GIQSKRNE5P3AVTZCEFXE3ON | https://api.github.com/repos/osakagamba/7GIQSKRNE5P3AVTZCEFXE3ON | closed | fvaHSSnfwSHiUGQlYVln5Qu6D0ZHaZYM6jobyApi6IbU+AivgCjEYOq1GKCuqPW4DQG9bJhIe6CZkiZTy9CNsugpkZmbMdUBljYGG5OXLlRjMNKZJWarZuz6O0Y7bUoJC97AdezL2ghr0QrJYgC+teRoYnYShmgQTzAlJiPY+XI= | design | 9ynu2xiwRV1xTe62oYDwPizZvjCj/Mz5JIAmEr+4+lccH6VNNrH79hKXlOwTV2UFaH5aRekW/rf8Pcgr+5zmkRtKJ63Q5hJLgiPP3KQMdS0mGFkfqogx2AqPmWI4gAi/khUapkS6IT5dhEB8LI9JBuQHyeIFVU0Bh5z74OuqLqiBOX5WGikFoe5TqHJjbvJeIyhLMJ1eLFSiQcWyKlyER3BEpjM6PY9R9N2Uk9y7yGI6TUZMopjhm+oxn92ef8lu8/Zqu8Yi7abSxEkx+H4gwiU4TN2hENMfECsYrtHDxcSuYGxEWd/KrKUrzQ0EgnjpnCk3Knr0wCvgFDjM4/XAs9O+T1s0T83FnwGAvCbgY7j0+X8rWBbr647SwOdJVswA4rMwY4s23Xr71xDYgBvf6HVMK6b5Jd/j1Gdf2X2hRVt07yFGa1PxwCgaYRSwxmb8i7gSllcMe/vBquMtVbKMDE0J0EuuPGoCyTy2TZL35LD4H5eX8ockBbjB6xn+iCDzXc3tgXTrCaRUa1HRU0YIOycKZ66cL38uZv7iBwcAXpHbMIH6LmXNhldBootIg08EbcVKh6s0g73CL5QtySlG31gvfPdmknHv6x1O4w/wWP4ej1tawee3csMt8uQhFf/l7s+9CamBYNXYCVP++kqWtpvA0A0YJQfJV2Y0B/OsHqHM2bNhAqFSydyQ4P93p2m+Ts3VxkrRglTZhLlTrBL2CiDcARo6KxnhX98aIc0RWZODIq4aFrDDYC9unL0SFqPfFwIH4SEtPc5i609ILFcsZpVQjuvonHYTpkm6iSbf91OJ76PJQ9De448SzfxchuBOkOK5ll4YLVlfguY/FcdUGnqhYtH8E16s1l0oKUh3UV9LlCpP7QOiX+3q4ZVPIiKzc2EGY3XaPH5Px0iEI5pgLfrA+G3o6E/Z7nK0VTm+HFd7lxEF7MTZYwk4uvXBps7GCndzuxm+xFC80SCddUkIWRc2LmLHaY1HbUoJrk5TymF5MLuQpjdl8AMT/XVpVlrNIXULBDskoXFI67vtcNz6HL6QaQf40Ivcii1Y+C5OKWzSZgPJdWYsKDJhlNtpxS4F6oCQgiDjsNb5yKE1ObxLxQezyog/LUv4i2O9KvlpGdo4+gdZHNm0mMEYvC/0q44CMr0aofebugdbZH+UH6qAlzreb4uw7LrO7a9w1Jy0X31RoAyTOLJFi62oYsdRWjGGtHBzBMILJ3spaSaq1bidkClkzELJqQwouuFksZtkehUMzjYwSTjBbO1uXZ78Pp7PWMICTOV9GmrWegPbdPd94v1fwl+/EqKqe5ctHuApXdndGjkuegMTxNNC6lgTIHP6A3LsaAMxHt5LZHYSyXuvZGvPQ0Q7EdoKDFqQLIjozZpLlCpP7QOiX+3q4ZVPIiKzcCS1vyMjR15HFPILKb/LHzI5KNx11RBDEquzEgBB9rB24Xo91BeQvSfLRYAgVMwYIrSjjsNZhLjabbrqk2mwUDBIDUG3BJX0huRLwRDXMyE/EkZoIqrzCe1KMDq5qrYdbg8TX716eXDvk5E6WI8FGKB6jKxGxhakBbZgQvPVkttfMkRxoVKlUUm0B9+pd/AxbuUdWWg28QlsQpM7AqbFfe0rdzWM3CzgBETilkEidUVwdVBf7jRKjfik91k2XbOHa+hb1jZy34y7vH8uQrdVQfPa9Lz93zG4XvITAOxdu+OH0QXCqX1ESzVroNwx+VUy05HR3vQwzLiEVZ9D79e/1TMrxrqTz3EvNPGy6yvhQht849YIrp7KLEqwOcpzftF80eBXh8nG9nPcEQq2BFzhVQ7DZ4fDsTxnzvmJHJinXzkKNJrgHhcYUURh48di04EU3oczP/m4iYjJ4/NxM0WUAZVW2Xwd8CdHbg60CYMDxuOrIvg6zZ5F8H0u9atzV9LM | 1.0 | fvaHSSnfwSHiUGQlYVln5Qu6D0ZHaZYM6jobyApi6IbU+AivgCjEYOq1GKCuqPW4DQG9bJhIe6CZkiZTy9CNsugpkZmbMdUBljYGG5OXLlRjMNKZJWarZuz6O0Y7bUoJC97AdezL2ghr0QrJYgC+teRoYnYShmgQTzAlJiPY+XI= - 9ynu2xiwRV1xTe62oYDwPizZvjCj/Mz5JIAmEr+4+lccH6VNNrH79hKXlOwTV2UFaH5aRekW/rf8Pcgr+5zmkRtKJ63Q5hJLgiPP3KQMdS0mGFkfqogx2AqPmWI4gAi/khUapkS6IT5dhEB8LI9JBuQHyeIFVU0Bh5z74OuqLqiBOX5WGikFoe5TqHJjbvJeIyhLMJ1eLFSiQcWyKlyER3BEpjM6PY9R9N2Uk9y7yGI6TUZMopjhm+oxn92ef8lu8/Zqu8Yi7abSxEkx+H4gwiU4TN2hENMfECsYrtHDxcSuYGxEWd/KrKUrzQ0EgnjpnCk3Knr0wCvgFDjM4/XAs9O+T1s0T83FnwGAvCbgY7j0+X8rWBbr647SwOdJVswA4rMwY4s23Xr71xDYgBvf6HVMK6b5Jd/j1Gdf2X2hRVt07yFGa1PxwCgaYRSwxmb8i7gSllcMe/vBquMtVbKMDE0J0EuuPGoCyTy2TZL35LD4H5eX8ockBbjB6xn+iCDzXc3tgXTrCaRUa1HRU0YIOycKZ66cL38uZv7iBwcAXpHbMIH6LmXNhldBootIg08EbcVKh6s0g73CL5QtySlG31gvfPdmknHv6x1O4w/wWP4ej1tawee3csMt8uQhFf/l7s+9CamBYNXYCVP++kqWtpvA0A0YJQfJV2Y0B/OsHqHM2bNhAqFSydyQ4P93p2m+Ts3VxkrRglTZhLlTrBL2CiDcARo6KxnhX98aIc0RWZODIq4aFrDDYC9unL0SFqPfFwIH4SEtPc5i609ILFcsZpVQjuvonHYTpkm6iSbf91OJ76PJQ9De448SzfxchuBOkOK5ll4YLVlfguY/FcdUGnqhYtH8E16s1l0oKUh3UV9LlCpP7QOiX+3q4ZVPIiKzc2EGY3XaPH5Px0iEI5pgLfrA+G3o6E/Z7nK0VTm+HFd7lxEF7MTZYwk4uvXBps7GCndzuxm+xFC80SCddUkIWRc2LmLHaY1HbUoJrk5TymF5MLuQpjdl8AMT/XVpVlrNIXULBDskoXFI67vtcNz6HL6QaQf40Ivcii1Y+C5OKWzSZgPJdWYsKDJhlNtpxS4F6oCQgiDjsNb5yKE1ObxLxQezyog/LUv4i2O9KvlpGdo4+gdZHNm0mMEYvC/0q44CMr0aofebugdbZH+UH6qAlzreb4uw7LrO7a9w1Jy0X31RoAyTOLJFi62oYsdRWjGGtHBzBMILJ3spaSaq1bidkClkzELJqQwouuFksZtkehUMzjYwSTjBbO1uXZ78Pp7PWMICTOV9GmrWegPbdPd94v1fwl+/EqKqe5ctHuApXdndGjkuegMTxNNC6lgTIHP6A3LsaAMxHt5LZHYSyXuvZGvPQ0Q7EdoKDFqQLIjozZpLlCpP7QOiX+3q4ZVPIiKzcCS1vyMjR15HFPILKb/LHzI5KNx11RBDEquzEgBB9rB24Xo91BeQvSfLRYAgVMwYIrSjjsNZhLjabbrqk2mwUDBIDUG3BJX0huRLwRDXMyE/EkZoIqrzCe1KMDq5qrYdbg8TX716eXDvk5E6WI8FGKB6jKxGxhakBbZgQvPVkttfMkRxoVKlUUm0B9+pd/AxbuUdWWg28QlsQpM7AqbFfe0rdzWM3CzgBETilkEidUVwdVBf7jRKjfik91k2XbOHa+hb1jZy34y7vH8uQrdVQfPa9Lz93zG4XvITAOxdu+OH0QXCqX1ESzVroNwx+VUy05HR3vQwzLiEVZ9D79e/1TMrxrqTz3EvNPGy6yvhQht849YIrp7KLEqwOcpzftF80eBXh8nG9nPcEQq2BFzhVQ7DZ4fDsTxnzvmJHJinXzkKNJrgHhcYUURh48di04EU3oczP/m4iYjJ4/NxM0WUAZVW2Xwd8CdHbg60CYMDxuOrIvg6zZ5F8H0u9atzV9LM | non_infrastructure | teroynyshmgqtzaljipy xi pd | 0 |
437,074 | 30,586,431,675 | IssuesEvent | 2023-07-21 13:43:33 | arduino/arduino-cli | https://api.github.com/repos/arduino/arduino-cli | closed | Missing documentation on 'montior -c' configuration settings | type: enhancement topic: documentation | > As a side note, an example of changing the baudrate should be added to the documentation.
_Originally posted by @romainreignier in https://github.com/arduino/arduino-cli/issues/1562#issuecomment-976941907_
The official docs are missing documentation on the available configuration options for the monitor command's `-c` option. At a minimum, the baudrate option should be documented. | 1.0 | Missing documentation on 'montior -c' configuration settings - > As a side note, an example of changing the baudrate should be added to the documentation.
_Originally posted by @romainreignier in https://github.com/arduino/arduino-cli/issues/1562#issuecomment-976941907_
The official docs are missing documentation on the available configuration options for the monitor command's `-c` option. At a minimum, the baudrate option should be documented. | non_infrastructure | missing documentation on montior c configuration settings as a side note an example of changing the baudrate should be added to the documentation originally posted by romainreignier in the official docs are missing documentation on the available configuration options for the monitor command s c option at a minimum the baudrate option should be documented | 0 |
22,716 | 15,395,206,884 | IssuesEvent | 2021-03-03 18:54:54 | hyphacoop/organizing | https://api.github.com/repos/hyphacoop/organizing | opened | Virtual Office issue: Mailcow sporadically not forwarding some emails from patcon@hypha.coop mailbox | wg:infrastructure | I've noticed this a few times. Will document more fully, but starting this stub for tracking. 🙏
- I use Gmail as my email client from patcon@hypha.coop
- I have my mailcow inbox configured to globally forward all email to patrick.c.connolly@gmail.com (leaving copy unread in mailcow)
- vast majority of email is forwarded properly, but sometimes email doesn't make it
- when email is missing from gmail, it is still inside mailcow when I go to look
## To Do
- [ ] inventory known problematic messages (currently: 2)
- [ ] compare gmail inbox to mailcow inbox, finding any others
- [ ] document fully (screenshots of settings, dumps of affected email headers, etc) | 1.0 | Virtual Office issue: Mailcow sporadically not forwarding some emails from patcon@hypha.coop mailbox - I've noticed this a few times. Will document more fully, but starting this stub for tracking. 🙏
- I use Gmail as my email client from patcon@hypha.coop
- I have my mailcow inbox configured to globally forward all email to patrick.c.connolly@gmail.com (leaving copy unread in mailcow)
- vast majority of email is forwarded properly, but sometimes email doesn't make it
- when email is missing from gmail, it is still inside mailcow when I go to look
## To Do
- [ ] inventory known problematic messages (currently: 2)
- [ ] compare gmail inbox to mailcow inbox, finding any others
- [ ] document fully (screenshots of settings, dumps of affected email headers, etc) | infrastructure | virtual office issue mailcow sporadically not forwarding some emails from patcon hypha coop mailbox i ve noticed this a few times will document more fully but starting this stub for tracking 🙏 i use gmail as my email client from patcon hypha coop i have my mailcow inbox configured to globally forward all email to patrick c connolly gmail com leaving copy unread in mailcow vast majority of email is forwarded properly but sometimes email doesn t make it when email is missing from gmail it is still inside mailcow when i go to look to do inventory known problematic messages currently compare gmail inbox to mailcow inbox finding any others document fully screenshots of settings dumps of affected email headers etc | 1 |
22,357 | 15,114,482,694 | IssuesEvent | 2021-02-09 02:02:05 | algorand/go-algorand | https://api.github.com/repos/algorand/go-algorand | closed | Scalability issues in the implementation of TEAL data types | Infrastructure | ## Summary
The code which implements Teal data types needs to be refactored to prevent storing unnecessary nil values and to make adding new data types easier.
## Scope/Requirements
In the source code we have a struct named `TealValue` which seems to be created for representing a teal data element. Currently a teal data element can be a byte slice or uint64. `TealValue` struct has this declaration:
```go
// TealValue contains type information and a value, representing a value in a
// TEAL program
type TealValue struct {
_struct struct{} `codec:",omitempty,omitemptyarray"`
Type TealType `codec:"tt"`
Bytes string `codec:"tb"`
Uint uint64 `codec:"ui"`
}
```
Similarly, somewhere else we have a `StackValue` struct with similar declaration: (I don't know why this struct was created. couldn't we just define a stack of `TealValue` instead of creating a new `StackValue` type?)
```go
// stackValue is the type for the operand stack.
// Each stackValue is either a valid []byte value or a uint64 value.
// If (.Bytes != nil) the stackValue is a []byte value, otherwise uint64 value.
type stackValue struct {
Uint uint64
Bytes []byte
}
```
All these structs contain a field for every possible data type inside them and only one of these fields will be non-nil. In my opinion this is not the right way for representing a teal data element and this representation is not scalable. in the future we may need more Teal data types like `[]int` or `float`. With the current code, adding them will not be so easy and needs a lot of changes in different parts of the code. **Also with more data types every struct will have more nil fields which wastes memory and when the struct is serialized to the ledger will waste the storage space too.**
For a situation like this In OO programing we usually define a `TealValue` (or `TealData`) super-class and a specific teal data type, for example `TealInt`, would be a subclass of it. In go language this can be implemented using interfaces, something like this:
```go
//TealValue is our super class
type TealValue interface {
SayHiLikeATeal()
}
//TealInt is a subclass of TealValue representing an integer data element
type TealInt struct {
value int
}
func (ti TealInt) Value() int {
return ti.value
}
func (ti TealInt) SayHiLikeATeal() {
fmt.Print("Hi! I'm a TealInt!")
}
//TealBytes is a subclass of TealValue representing a byte slice data element
type TealBytes struct {
value []byte
}
func (tb TealBytes) SayHiLikeATeal() {
fmt.Print("Hi! I'm a TealBytes!")
}
func (tb TealBytes) Value() []byte {
return tb.value
}
```
Then if we want a stack for storing Teal data elements we can simply do it like this:
```go
var stack []TealValue
tb := TealBytes{[]byte{1,2,3}}
ti := TealInt{value: 22}
stack = append(stack, ti, tb)
//we can use polymorphism:
stack[1].SayHiLikeATeal()
//or we can cast a stack element to its original type
stack[0].(TealInt).Value()
//or we can use a type switch (which generally, is not a good thing and makes the code less scalable!)
switch v := stack[1].(type) {
case TealInt:
// here v has type TealInt
case TealBytes:
// here v has type TealBytes
default:
// no match; here v has the same type as i
}
```
## Urgency/Relative Priority
I think these changes should be made as soon as possible.
| 1.0 | Scalability issues in the implementation of TEAL data types - ## Summary
The code which implements Teal data types needs to be refactored to prevent storing unnecessary nil values and to make adding new data types easier.
## Scope/Requirements
In the source code we have a struct named `TealValue` which seems to be created for representing a teal data element. Currently a teal data element can be a byte slice or uint64. `TealValue` struct has this declaration:
```go
// TealValue contains type information and a value, representing a value in a
// TEAL program
type TealValue struct {
_struct struct{} `codec:",omitempty,omitemptyarray"`
Type TealType `codec:"tt"`
Bytes string `codec:"tb"`
Uint uint64 `codec:"ui"`
}
```
Similarly, somewhere else we have a `StackValue` struct with similar declaration: (I don't know why this struct was created. couldn't we just define a stack of `TealValue` instead of creating a new `StackValue` type?)
```go
// stackValue is the type for the operand stack.
// Each stackValue is either a valid []byte value or a uint64 value.
// If (.Bytes != nil) the stackValue is a []byte value, otherwise uint64 value.
type stackValue struct {
Uint uint64
Bytes []byte
}
```
All these structs contain a field for every possible data type inside them and only one of these fields will be non-nil. In my opinion this is not the right way for representing a teal data element and this representation is not scalable. in the future we may need more Teal data types like `[]int` or `float`. With the current code, adding them will not be so easy and needs a lot of changes in different parts of the code. **Also with more data types every struct will have more nil fields which wastes memory and when the struct is serialized to the ledger will waste the storage space too.**
For a situation like this In OO programing we usually define a `TealValue` (or `TealData`) super-class and a specific teal data type, for example `TealInt`, would be a subclass of it. In go language this can be implemented using interfaces, something like this:
```go
//TealValue is our super class
type TealValue interface {
SayHiLikeATeal()
}
//TealInt is a subclass of TealValue representing an integer data element
type TealInt struct {
value int
}
func (ti TealInt) Value() int {
return ti.value
}
func (ti TealInt) SayHiLikeATeal() {
fmt.Print("Hi! I'm a TealInt!")
}
//TealBytes is a subclass of TealValue representing a byte slice data element
type TealBytes struct {
value []byte
}
func (tb TealBytes) SayHiLikeATeal() {
fmt.Print("Hi! I'm a TealBytes!")
}
func (tb TealBytes) Value() []byte {
return tb.value
}
```
Then if we want a stack for storing Teal data elements we can simply do it like this:
```go
var stack []TealValue
tb := TealBytes{[]byte{1,2,3}}
ti := TealInt{value: 22}
stack = append(stack, ti, tb)
//we can use polymorphism:
stack[1].SayHiLikeATeal()
//or we can cast a stack element to its original type
stack[0].(TealInt).Value()
//or we can use a type switch (which generally, is not a good thing and makes the code less scalable!)
switch v := stack[1].(type) {
case TealInt:
// here v has type TealInt
case TealBytes:
// here v has type TealBytes
default:
// no match; here v has the same type as i
}
```
## Urgency/Relative Priority
I think these changes should be made as soon as possible.
| infrastructure | scalability issues in the implementation of teal data types summary the code which implements teal data types needs to be refactored to prevent storing unnecessary nil values and to make adding new data types easier scope requirements in the source code we have a struct named tealvalue which seems to be created for representing a teal data element currently a teal data element can be a byte slice or tealvalue struct has this declaration go tealvalue contains type information and a value representing a value in a teal program type tealvalue struct struct struct codec omitempty omitemptyarray type tealtype codec tt bytes string codec tb uint codec ui similarly somewhere else we have a stackvalue struct with similar declaration i don t know why this struct was created couldn t we just define a stack of tealvalue instead of creating a new stackvalue type go stackvalue is the type for the operand stack each stackvalue is either a valid byte value or a value if bytes nil the stackvalue is a byte value otherwise value type stackvalue struct uint bytes byte all these structs contain a field for every possible data type inside them and only one of these fields will be non nil in my opinion this is not the right way for representing a teal data element and this representation is not scalable in the future we may need more teal data types like int or float with the current code adding them will not be so easy and needs a lot of changes in different parts of the code also with more data types every struct will have more nil fields which wastes memory and when the struct is serialized to the ledger will waste the storage space too for a situation like this in oo programing we usually define a tealvalue or tealdata super class and a specific teal data type for example tealint would be a subclass of it in go language this can be implemented using interfaces something like this go tealvalue is our super class type tealvalue interface sayhilikeateal tealint is a subclass of tealvalue representing an integer data element type tealint struct value int func ti tealint value int return ti value func ti tealint sayhilikeateal fmt print hi i m a tealint tealbytes is a subclass of tealvalue representing a byte slice data element type tealbytes struct value byte func tb tealbytes sayhilikeateal fmt print hi i m a tealbytes func tb tealbytes value byte return tb value then if we want a stack for storing teal data elements we can simply do it like this go var stack tealvalue tb tealbytes byte ti tealint value stack append stack ti tb we can use polymorphism stack sayhilikeateal or we can cast a stack element to its original type stack tealint value or we can use a type switch which generally is not a good thing and makes the code less scalable switch v stack type case tealint here v has type tealint case tealbytes here v has type tealbytes default no match here v has the same type as i urgency relative priority i think these changes should be made as soon as possible | 1 |
95,501 | 8,560,306,214 | IssuesEvent | 2018-11-09 00:34:51 | certbot/certbot | https://api.github.com/repos/certbot/certbot | closed | sed -i '4arenew_before_expiry = 10 years' "/var/folders/18/96y990v ...": invalid command code f | area: macOS area: testing help wanted | On OS X 10.10.5, when installing `letsencrypt` as part of running the `boulder`'s integration tests (`RUN="integration" ./test.sh`), I get the following error stemming from `letsencrypt/tests/boulder-integration.sh`:
``` sh
+ sed -i '4arenew_before_expiry = 10 years' /var/folders/.../conf/renewal/le.wtf.conf
sed: 1: "/var/folders/18/96y990v ...": invalid command code f
```
I'm pretty unfamiliar with `sed` and everything I've found suggests that the command should look differently on OS X, though I'm unsure how. Any insights?
| 1.0 | sed -i '4arenew_before_expiry = 10 years' "/var/folders/18/96y990v ...": invalid command code f - On OS X 10.10.5, when installing `letsencrypt` as part of running the `boulder`'s integration tests (`RUN="integration" ./test.sh`), I get the following error stemming from `letsencrypt/tests/boulder-integration.sh`:
``` sh
+ sed -i '4arenew_before_expiry = 10 years' /var/folders/.../conf/renewal/le.wtf.conf
sed: 1: "/var/folders/18/96y990v ...": invalid command code f
```
I'm pretty unfamiliar with `sed` and everything I've found suggests that the command should look differently on OS X, though I'm unsure how. Any insights?
| non_infrastructure | sed i before expiry years var folders invalid command code f on os x when installing letsencrypt as part of running the boulder s integration tests run integration test sh i get the following error stemming from letsencrypt tests boulder integration sh sh sed i before expiry years var folders conf renewal le wtf conf sed var folders invalid command code f i m pretty unfamiliar with sed and everything i ve found suggests that the command should look differently on os x though i m unsure how any insights | 0 |
12,612 | 9,875,193,490 | IssuesEvent | 2019-06-23 09:31:16 | OpenCHS/openchs-product | https://api.github.com/repos/OpenCHS/openchs-product | closed | Setup In-premise LBP server | 2.6 Complete Infrastructure/other Must Story | Contact : Jagdish +91 75887 72819 to connect using AnyDesk or TeamViewer
Find out solution for bugs-nag
[admin@localhost ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/centos-root 50G 5.0G 45G 10% /
devtmpfs 3.8G 0 3.8G 0% /dev
tmpfs 3.8G 156K 3.8G 1% /dev/shm
tmpfs 3.8G 11M 3.8G 1% /run
tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup
/dev/sda2 1014M 163M 852M 17% /boot
/dev/sda1 200M 9.8M 191M 5% /boot/efi
/dev/mapper/centos-home 873G 175M 872G 1% /home
tmpfs 774M 4.0K 774M 1% /run/user/42
tmpfs 774M 32K 774M 1% /run/user/1000
[admin@localhost ~]$ cat /etc/redhat-release
CentOS Linux release 7.5.1804 (Core)
[admin@localhost ~]$ free -mmmm
total used free shared buff/cache available
Mem: 7730 1103 5896 150 730 6177
Swap: 7935 0 7935
[admin@localhost ~]$
Dev/deployment info, Server/App version info:
https://docs.google.com/document/d/14XaKh-WblV0TBKiPviFUufYWz-5l9ZC294kxHQI6umQ/edit?usp=sharing | 1.0 | Setup In-premise LBP server - Contact : Jagdish +91 75887 72819 to connect using AnyDesk or TeamViewer
Find out solution for bugs-nag
[admin@localhost ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/centos-root 50G 5.0G 45G 10% /
devtmpfs 3.8G 0 3.8G 0% /dev
tmpfs 3.8G 156K 3.8G 1% /dev/shm
tmpfs 3.8G 11M 3.8G 1% /run
tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup
/dev/sda2 1014M 163M 852M 17% /boot
/dev/sda1 200M 9.8M 191M 5% /boot/efi
/dev/mapper/centos-home 873G 175M 872G 1% /home
tmpfs 774M 4.0K 774M 1% /run/user/42
tmpfs 774M 32K 774M 1% /run/user/1000
[admin@localhost ~]$ cat /etc/redhat-release
CentOS Linux release 7.5.1804 (Core)
[admin@localhost ~]$ free -mmmm
total used free shared buff/cache available
Mem: 7730 1103 5896 150 730 6177
Swap: 7935 0 7935
[admin@localhost ~]$
Dev/deployment info, Server/App version info:
https://docs.google.com/document/d/14XaKh-WblV0TBKiPviFUufYWz-5l9ZC294kxHQI6umQ/edit?usp=sharing | infrastructure | setup in premise lbp server contact jagdish to connect using anydesk or teamviewer find out solution for bugs nag df h filesystem size used avail use mounted on dev mapper centos root devtmpfs dev tmpfs dev shm tmpfs run tmpfs sys fs cgroup dev boot dev boot efi dev mapper centos home home tmpfs run user tmpfs run user cat etc redhat release centos linux release core free mmmm total used free shared buff cache available mem swap dev deployment info server app version info | 1 |
35,100 | 6,412,910,234 | IssuesEvent | 2017-08-08 05:41:01 | georgringer/news | https://api.github.com/repos/georgringer/news | closed | Documentation: Import realurl unique aliases for import of tt_news | Documentation Needs feedback from author t3dd | Would be nice to see a migration guide for Realurls unique aliases when importing from tt_news.
```
# Zwischentabelle erstellen
CREATE TABLE tx_realurl_uniqalias_migration LIKE tx_realurl_uniqalias;
# kopieren
INSERT INTO tx_realurl_uniqalias_migration SELECT * FROM tx_realurl_uniqalias WHERE tablename='tt_news';
# Korrigieren
UPDATE tx_realurl_uniqalias_migration SET value_id = (SELECT tx_news_domain_model_news.uid FROM `tx_news_domain_model_news` WHERE tx_news_domain_model_news.import_id=tx_realurl_uniqalias_migration.value_id),tablename='tx_news_domain_model_news' WHERE tablename='tt_news';
# Kaputte aliase entfernen (News, die nicht importiert wurden)
DELETE FROM tx_realurl_uniqalias_migration WHERE tablename='tx_news_domain_model_news' AND value_id=0;
# Zurückspielen
INSERT INTO tx_realurl_uniqalias (tstamp,tablename,field_id,value_alias,value_id,lang,expire) SELECT tstamp,tablename,field_id,value_alias,value_id,lang,expire FROM tx_realurl_uniqalias_migration
```
Gruß
Christoph | 1.0 | Documentation: Import realurl unique aliases for import of tt_news - Would be nice to see a migration guide for Realurls unique aliases when importing from tt_news.
```
# Zwischentabelle erstellen
CREATE TABLE tx_realurl_uniqalias_migration LIKE tx_realurl_uniqalias;
# kopieren
INSERT INTO tx_realurl_uniqalias_migration SELECT * FROM tx_realurl_uniqalias WHERE tablename='tt_news';
# Korrigieren
UPDATE tx_realurl_uniqalias_migration SET value_id = (SELECT tx_news_domain_model_news.uid FROM `tx_news_domain_model_news` WHERE tx_news_domain_model_news.import_id=tx_realurl_uniqalias_migration.value_id),tablename='tx_news_domain_model_news' WHERE tablename='tt_news';
# Kaputte aliase entfernen (News, die nicht importiert wurden)
DELETE FROM tx_realurl_uniqalias_migration WHERE tablename='tx_news_domain_model_news' AND value_id=0;
# Zurückspielen
INSERT INTO tx_realurl_uniqalias (tstamp,tablename,field_id,value_alias,value_id,lang,expire) SELECT tstamp,tablename,field_id,value_alias,value_id,lang,expire FROM tx_realurl_uniqalias_migration
```
Gruß
Christoph | non_infrastructure | documentation import realurl unique aliases for import of tt news would be nice to see a migration guide for realurls unique aliases when importing from tt news zwischentabelle erstellen create table tx realurl uniqalias migration like tx realurl uniqalias kopieren insert into tx realurl uniqalias migration select from tx realurl uniqalias where tablename tt news korrigieren update tx realurl uniqalias migration set value id select tx news domain model news uid from tx news domain model news where tx news domain model news import id tx realurl uniqalias migration value id tablename tx news domain model news where tablename tt news kaputte aliase entfernen news die nicht importiert wurden delete from tx realurl uniqalias migration where tablename tx news domain model news and value id zurückspielen insert into tx realurl uniqalias tstamp tablename field id value alias value id lang expire select tstamp tablename field id value alias value id lang expire from tx realurl uniqalias migration gruß christoph | 0 |
32,298 | 26,608,922,735 | IssuesEvent | 2023-01-23 21:53:52 | oasisprotocol/oasis-indexer | https://api.github.com/repos/oasisprotocol/oasis-indexer | closed | Deploy with CORS enabled | infrastructure | Frontend currently can't use the deployed API, so I had to add a dev proxy: https://github.com/oasisprotocol/explorer-frontend/pull/5/commits/f355c7c012935c2cd8d1a8e0b721cda1c4e064b4.
CORS headers in oasisscan https://api.oasisscan.com/mainnet/validator/list?pageSize=500
```
access-control-allow-credentials: true
access-control-allow-headers: DNT,X-Mx-ReqToken,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type
access-control-allow-methods: GET, POST, OPTIONS
access-control-allow-origin: *
```
and oasismonitor https://monitor.oasis.dev/data/transactions?limit=20
```
access-control-allow-credentials: true
access-control-allow-origin: *
``` | 1.0 | Deploy with CORS enabled - Frontend currently can't use the deployed API, so I had to add a dev proxy: https://github.com/oasisprotocol/explorer-frontend/pull/5/commits/f355c7c012935c2cd8d1a8e0b721cda1c4e064b4.
CORS headers in oasisscan https://api.oasisscan.com/mainnet/validator/list?pageSize=500
```
access-control-allow-credentials: true
access-control-allow-headers: DNT,X-Mx-ReqToken,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type
access-control-allow-methods: GET, POST, OPTIONS
access-control-allow-origin: *
```
and oasismonitor https://monitor.oasis.dev/data/transactions?limit=20
```
access-control-allow-credentials: true
access-control-allow-origin: *
``` | infrastructure | deploy with cors enabled frontend currently can t use the deployed api so i had to add a dev proxy cors headers in oasisscan access control allow credentials true access control allow headers dnt x mx reqtoken keep alive user agent x requested with if modified since cache control content type access control allow methods get post options access control allow origin and oasismonitor access control allow credentials true access control allow origin | 1 |
11,486 | 9,204,229,481 | IssuesEvent | 2019-03-08 06:30:41 | dotnet/core-setup | https://api.github.com/repos/dotnet/core-setup | closed | Building with VS 2019 fails native compilation (corehost) | Triaged area-Infrastructure | https://github.com/dotnet/corefx/issues/34613 is similar, for corefx.
> (https://github.com/dotnet/corefx/issues/34613#issuecomment-454887287) ~Cmake is rolling out a 3.14.0 in February from what I saw that contains support for VS2019 with a new project generator that might help, but I'm still trying to workaround it.~ [New cmake is out! See comment below.]
---
There are workarounds that let you keep VS 2019 installed:
> (https://github.com/dotnet/corefx/issues/34613#issuecomment-454886707) I would suggest to use the Dev Command Prompt VS2017 when building from root for now until we have a fix.
Removing `-prerelease` from this line also works (this is what I did before I saw the corefx issue, and it doesn't require me to use a dev command prompt):
https://github.com/dotnet/core-setup/blob/e34acdb8b64dc054a22242dd5cbcfceae8e8a5b9/run.cmd#L8
| 1.0 | Building with VS 2019 fails native compilation (corehost) - https://github.com/dotnet/corefx/issues/34613 is similar, for corefx.
> (https://github.com/dotnet/corefx/issues/34613#issuecomment-454887287) ~Cmake is rolling out a 3.14.0 in February from what I saw that contains support for VS2019 with a new project generator that might help, but I'm still trying to workaround it.~ [New cmake is out! See comment below.]
---
There are workarounds that let you keep VS 2019 installed:
> (https://github.com/dotnet/corefx/issues/34613#issuecomment-454886707) I would suggest to use the Dev Command Prompt VS2017 when building from root for now until we have a fix.
Removing `-prerelease` from this line also works (this is what I did before I saw the corefx issue, and it doesn't require me to use a dev command prompt):
https://github.com/dotnet/core-setup/blob/e34acdb8b64dc054a22242dd5cbcfceae8e8a5b9/run.cmd#L8
| infrastructure | building with vs fails native compilation corehost is similar for corefx cmake is rolling out a in february from what i saw that contains support for with a new project generator that might help but i m still trying to workaround it there are workarounds that let you keep vs installed i would suggest to use the dev command prompt when building from root for now until we have a fix removing prerelease from this line also works this is what i did before i saw the corefx issue and it doesn t require me to use a dev command prompt | 1 |
702,241 | 24,120,778,234 | IssuesEvent | 2022-09-20 18:30:06 | googleapis/nodejs-vision | https://api.github.com/repos/googleapis/nodejs-vision | closed | Vision: "after all" hook for "should detect from a Buffer" failed | type: bug priority: p1 api: vision flakybot: issue | Note: #951 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
----
commit: ed5c7a0ef5443c435759e65d817f3919eb9d004d
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/e8ac3eac-d506-460c-8df9-90012a94a5b7), [Sponge](http://sponge2/e8ac3eac-d506-460c-8df9-90012a94a5b7)
status: failed
<details><summary>Test output</summary><br><pre>invalid_grant: Invalid JWT Signature.
Error: invalid_grant: Invalid JWT Signature.
at Gaxios._request (node_modules/gaxios/build/src/gaxios.js:130:23)
-> /workspace/node_modules/gaxios/src/gaxios.ts:158:15
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async GoogleToken.requestToken (node_modules/gtoken/build/src/index.js:238:23)
at async GoogleToken.getTokenAsync (node_modules/gtoken/build/src/index.js:145:20)
at async JWT.refreshTokenNoCache (node_modules/google-auth-library/build/src/auth/jwtclient.js:172:23)
at async JWT.getRequestMetadataAsync (node_modules/google-auth-library/build/src/auth/oauth2client.js:284:17)
at async JWT.getRequestHeaders (node_modules/google-auth-library/build/src/auth/oauth2client.js:247:26)
at async GoogleAuth.authorizeRequest (node_modules/google-auth-library/build/src/auth/googleauth.js:677:25)
at async Promise.all (index 1)
at async prepareRequest (node_modules/@google-cloud/storage/build/src/nodejs-common/util.js:447:61)</pre></details> | 1.0 | Vision: "after all" hook for "should detect from a Buffer" failed - Note: #951 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
----
commit: ed5c7a0ef5443c435759e65d817f3919eb9d004d
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/e8ac3eac-d506-460c-8df9-90012a94a5b7), [Sponge](http://sponge2/e8ac3eac-d506-460c-8df9-90012a94a5b7)
status: failed
<details><summary>Test output</summary><br><pre>invalid_grant: Invalid JWT Signature.
Error: invalid_grant: Invalid JWT Signature.
at Gaxios._request (node_modules/gaxios/build/src/gaxios.js:130:23)
-> /workspace/node_modules/gaxios/src/gaxios.ts:158:15
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async GoogleToken.requestToken (node_modules/gtoken/build/src/index.js:238:23)
at async GoogleToken.getTokenAsync (node_modules/gtoken/build/src/index.js:145:20)
at async JWT.refreshTokenNoCache (node_modules/google-auth-library/build/src/auth/jwtclient.js:172:23)
at async JWT.getRequestMetadataAsync (node_modules/google-auth-library/build/src/auth/oauth2client.js:284:17)
at async JWT.getRequestHeaders (node_modules/google-auth-library/build/src/auth/oauth2client.js:247:26)
at async GoogleAuth.authorizeRequest (node_modules/google-auth-library/build/src/auth/googleauth.js:677:25)
at async Promise.all (index 1)
at async prepareRequest (node_modules/@google-cloud/storage/build/src/nodejs-common/util.js:447:61)</pre></details> | non_infrastructure | vision after all hook for should detect from a buffer failed note was also for this test but it was closed more than days ago so i didn t mark it flaky commit buildurl status failed test output invalid grant invalid jwt signature error invalid grant invalid jwt signature at gaxios request node modules gaxios build src gaxios js workspace node modules gaxios src gaxios ts at processticksandrejections internal process task queues js at async googletoken requesttoken node modules gtoken build src index js at async googletoken gettokenasync node modules gtoken build src index js at async jwt refreshtokennocache node modules google auth library build src auth jwtclient js at async jwt getrequestmetadataasync node modules google auth library build src auth js at async jwt getrequestheaders node modules google auth library build src auth js at async googleauth authorizerequest node modules google auth library build src auth googleauth js at async promise all index at async preparerequest node modules google cloud storage build src nodejs common util js | 0 |
10,877 | 2,622,353,432 | IssuesEvent | 2015-03-04 01:50:05 | rainerhessmer/drh-visual-odometry | https://api.github.com/repos/rainerhessmer/drh-visual-odometry | opened | Where is m_RawImage = new Image<Bgr, byte>(@"C:\aldo\drh-visual-odometry-read-only\CalibrationFiles\MicrosoftCinema\Focus14\1280x720\GroundProjectionCalibration.jpg | auto-migrated Priority-Medium Type-Defect | ```
Hi everybody,
in MainForm.cs,a instruction fails because can't find an image to load:
m_RawImage = new Image<Bgr, byte>(@"C:\aldo\drh-visual-odometry-read-only\CalibrationFiles\MicrosoftCinema\Focus14\1280x720\GroundProjectionCalibration.jpg");
Where can I download "GroundProjectionCalibration.jpg"?
Regards.
Aldo
```
Original issue reported on code.google.com by `aldobiziak` on 14 Aug 2012 at 9:43 | 1.0 | Where is m_RawImage = new Image<Bgr, byte>(@"C:\aldo\drh-visual-odometry-read-only\CalibrationFiles\MicrosoftCinema\Focus14\1280x720\GroundProjectionCalibration.jpg - ```
Hi everybody,
in MainForm.cs,a instruction fails because can't find an image to load:
m_RawImage = new Image<Bgr, byte>(@"C:\aldo\drh-visual-odometry-read-only\CalibrationFiles\MicrosoftCinema\Focus14\1280x720\GroundProjectionCalibration.jpg");
Where can I download "GroundProjectionCalibration.jpg"?
Regards.
Aldo
```
Original issue reported on code.google.com by `aldobiziak` on 14 Aug 2012 at 9:43 | non_infrastructure | where is m rawimage new image c aldo drh visual odometry read only calibrationfiles microsoftcinema groundprojectioncalibration jpg hi everybody in mainform cs a instruction fails because can t find an image to load m rawimage new image c aldo drh visual odometry read only calibrationfiles microsoftcinema groundprojectioncalibration jpg where can i download groundprojectioncalibration jpg regards aldo original issue reported on code google com by aldobiziak on aug at | 0 |
11,919 | 9,524,593,236 | IssuesEvent | 2019-04-28 04:54:31 | codebuddies/cb-connect | https://api.github.com/repos/codebuddies/cb-connect | closed | Add prop validations through prop-types to our React Components | [tech] infrastructure [tech] javascript [tech] react [type] enhancement claimed | Currently we have 31 warnings on missing prop validations. To follow modern best practices when composing React components, we should include prop types in our components (both for documentation purposes and type checking; will help us improve our tests).
To see all components with missing prop types, run `meteor npx lint` in your terminal and it should return you a similar list of warnings:
The goal of this issue is to reduce the list down to `0`.
For reference, see:
https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/prop-types.md
https://reactjs.org/docs/typechecking-with-proptypes.html
https://www.npmjs.com/package/prop-types | 1.0 | Add prop validations through prop-types to our React Components - Currently we have 31 warnings on missing prop validations. To follow modern best practices when composing React components, we should include prop types in our components (both for documentation purposes and type checking; will help us improve our tests).
To see all components with missing prop types, run `meteor npx lint` in your terminal and it should return you a similar list of warnings:
The goal of this issue is to reduce the list down to `0`.
For reference, see:
https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/prop-types.md
https://reactjs.org/docs/typechecking-with-proptypes.html
https://www.npmjs.com/package/prop-types | infrastructure | add prop validations through prop types to our react components currently we have warnings on missing prop validations to follow modern best practices when composing react components we should include prop types in our components both for documentation purposes and type checking will help us improve our tests to see all components with missing prop types run meteor npx lint in your terminal and it should return you a similar list of warnings the goal of this issue is to reduce the list down to for reference see | 1 |
7,872 | 7,120,229,098 | IssuesEvent | 2018-01-19 00:02:29 | Microsoft/TypeScript | https://api.github.com/repos/Microsoft/TypeScript | closed | Duplicate specification of `newLineCharacter` in RefactorContext | Infrastructure | **TypeScript Version:** master
**Code**
In `convertFunctionToEs6Class.ts`:
```ts
context.rulesProvider.getFormatOptions().newLineCharacter;
```
`RefactorContext` already specifies a `newLineCharacter` direct property; it looks like there are two ways of specifying this that might conflict. @RyanCavanaugh | 1.0 | Duplicate specification of `newLineCharacter` in RefactorContext - **TypeScript Version:** master
**Code**
In `convertFunctionToEs6Class.ts`:
```ts
context.rulesProvider.getFormatOptions().newLineCharacter;
```
`RefactorContext` already specifies a `newLineCharacter` direct property; it looks like there are two ways of specifying this that might conflict. @RyanCavanaugh | infrastructure | duplicate specification of newlinecharacter in refactorcontext typescript version master code in ts ts context rulesprovider getformatoptions newlinecharacter refactorcontext already specifies a newlinecharacter direct property it looks like there are two ways of specifying this that might conflict ryancavanaugh | 1 |
31,404 | 25,723,061,982 | IssuesEvent | 2022-12-07 14:56:34 | Tonomy-Foundation/Tonomy-ID | https://api.github.com/repos/Tonomy-Foundation/Tonomy-ID | opened | Antelope contracts CI | infrastructure | Definition of done
- [ ] Whenever the development branch has a commit, if there are any smart contract updates, these are redeployed on the staging server blockchain | 1.0 | Antelope contracts CI - Definition of done
- [ ] Whenever the development branch has a commit, if there are any smart contract updates, these are redeployed on the staging server blockchain | infrastructure | antelope contracts ci definition of done whenever the development branch has a commit if there are any smart contract updates these are redeployed on the staging server blockchain | 1 |
378,587 | 11,204,901,175 | IssuesEvent | 2020-01-05 10:12:36 | noobaa/noobaa-core | https://api.github.com/repos/noobaa/noobaa-core | closed | A lot of RPC warnings "GOT RESPONSE BUT REQUEST NOT PENDING" probably on test_network_perf | Priority 2 High Severity 3 Supportability Type:Bug | ### Environment info
- NooBaa Version: **VERSION**
- Platform: **Kubernetes 1.14.1 | minikube 1.1.1 | OpenShift 4.1 | other: specify**
### Actual behavior
1. on a newly installed system there are a lot of log messages that shouldn't be there.
2. for the internal agent, every time `test_network_perf` is called, we can see warn messages with `GOT RESPONSE BUT REQUEST NOT PENDING`:
```
Oct-1 10:26:16.540 [WebServer/42] [L0] core.server.node_services.nodes_monitor:: _test_network_to_server:: noobaa-internal-agent-5d9329c57b3046002a3f6a09
Oct-1 10:26:16.542 [WebServer/42] [L0] core.server.node_services.nodes_monitor:: _test_network_perf:: success in test noobaa-internal-agent-5d9329c57b3046002a3f6a09
Oct-1 10:26:16.547 [HostedAgents/33] [L0] core.agent.block_store_services.block_store_mongo:: _head_block: Block noobaa_blocks/5d9329c57b3046002a3f6a09/blocks_tree/other.blocks/_test_store_perf was not found
Oct-1 10:26:16.548 [WebServer/42] [L0] core.rpc.rpc_ws_server:: WS ACCEPT CONNECTION ws://[::ffff:127.0.0.1]:42370/(75ityoq)
Oct-1 10:26:16.705 [WebServer/42] [WARN] core.rpc.rpc:: RPC._on_response: GOT RESPONSE BUT REQUEST NOT PENDING reqid 1@n2n://5d9329c87b3046002a3f6a1a(75ewojo) connid n2n://5d9329c87b3046002a3f6a1a(75ewojo)
Oct-1 10:26:16.705 [WebServer/42] [WARN] core.rpc.rpc:: RPC._on_response: GOT RESPONSE BUT REQUEST NOT PENDING reqid 1@n2n://5d9329c87b3046002a3f6a1a(75ewojo) connid n2n://5d9329c87b3046002a3f6a1a(75ewojo)
Oct-1 10:26:16.706 [WebServer/42] [WARN] core.rpc.rpc:: RPC._on_response: GOT RESPONSE BUT REQUEST NOT PENDING reqid 1@n2n://5d9329c87b3046002a3f6a1a(75ewojo) connid n2n://5d9329c87b3046002a3f6a1a(75ewojo)
Oct-1 10:26:16.706 [WebServer/42] [WARN] core.rpc.rpc:: RPC._on_response: GOT RESPONSE BUT REQUEST NOT PENDING reqid 1@n2n://5d9329c87b3046002a3f6a1a(75ewojo) connid n2n://5d9329c87b3046002a3f6a1a(75ewojo)
Oct-1 10:26:16.706 [WebServer/42] [WARN] core.rpc.rpc:: RPC._on_response: GOT RESPONSE BUT REQUEST NOT PENDING reqid 1@n2n://5d9329c87b3046002a3f6a1a(75ewojo) connid n2n://5d9329c87b3046002a3f6a1a(75ewojo)
Oct-1 10:26:16.706 [WebServer/42] [WARN] core.rpc.rpc:: RPC._on_response: GOT RESPONSE BUT REQUEST NOT PENDING reqid 1@n2n://5d9329c87b3046002a3f6a1a(75ewojo) connid n2n://5d9329c87b3046002a3f6a1a(75ewojo)
Oct-1 10:26:16.706 [WebServer/42] [WARN] core.rpc.rpc:: RPC._on_response: GOT RESPONSE BUT REQUEST NOT PENDING reqid 1@n2n://5d9329c87b3046002a3f6a1a(75ewojo) connid n2n://5d9329c87b3046002a3f6a1a(75ewojo)
Oct-1 10:26:16.706 [WebServer/42] [WARN] core.rpc.rpc:: RPC._on_response: GOT RESPONSE BUT REQUEST NOT PENDING reqid 1@n2n://5d9329c87b3046002a3f6a1a(75ewojo) connid n2n://5d9329c87b3046002a3f6a1a(75ewojo)
Oct-1 10:26:16.706 [WebServer/42] [L0] core.server.node_services.nodes_monitor:: _test_network_to_server:: Succeeded in sending n2n rpc to noobaa-internal-agent-5d9329c57b3046002a3f6a09 took 166
Oct-1 10:26:16.707 [WebServer/42] [L0] core.rpc.rpc_n2n:: _close undefined
```
### Expected behavior
1. there shouldn't be any messages
### Steps to reproduce
1. install a new system
2. look for `GOT RESPONSE BUT REQUEST NOT PENDING` in the logs
### More information - Screenshots / Logs / Other output | 1.0 | A lot of RPC warnings "GOT RESPONSE BUT REQUEST NOT PENDING" probably on test_network_perf - ### Environment info
- NooBaa Version: **VERSION**
- Platform: **Kubernetes 1.14.1 | minikube 1.1.1 | OpenShift 4.1 | other: specify**
### Actual behavior
1. on a newly installed system there are a lot of log messages that shouldn't be there.
2. for the internal agent, every time `test_network_perf` is called, we can see warn messages with `GOT RESPONSE BUT REQUEST NOT PENDING`:
```
Oct-1 10:26:16.540 [WebServer/42] [L0] core.server.node_services.nodes_monitor:: _test_network_to_server:: noobaa-internal-agent-5d9329c57b3046002a3f6a09
Oct-1 10:26:16.542 [WebServer/42] [L0] core.server.node_services.nodes_monitor:: _test_network_perf:: success in test noobaa-internal-agent-5d9329c57b3046002a3f6a09
Oct-1 10:26:16.547 [HostedAgents/33] [L0] core.agent.block_store_services.block_store_mongo:: _head_block: Block noobaa_blocks/5d9329c57b3046002a3f6a09/blocks_tree/other.blocks/_test_store_perf was not found
Oct-1 10:26:16.548 [WebServer/42] [L0] core.rpc.rpc_ws_server:: WS ACCEPT CONNECTION ws://[::ffff:127.0.0.1]:42370/(75ityoq)
Oct-1 10:26:16.705 [WebServer/42] [WARN] core.rpc.rpc:: RPC._on_response: GOT RESPONSE BUT REQUEST NOT PENDING reqid 1@n2n://5d9329c87b3046002a3f6a1a(75ewojo) connid n2n://5d9329c87b3046002a3f6a1a(75ewojo)
Oct-1 10:26:16.705 [WebServer/42] [WARN] core.rpc.rpc:: RPC._on_response: GOT RESPONSE BUT REQUEST NOT PENDING reqid 1@n2n://5d9329c87b3046002a3f6a1a(75ewojo) connid n2n://5d9329c87b3046002a3f6a1a(75ewojo)
Oct-1 10:26:16.706 [WebServer/42] [WARN] core.rpc.rpc:: RPC._on_response: GOT RESPONSE BUT REQUEST NOT PENDING reqid 1@n2n://5d9329c87b3046002a3f6a1a(75ewojo) connid n2n://5d9329c87b3046002a3f6a1a(75ewojo)
Oct-1 10:26:16.706 [WebServer/42] [WARN] core.rpc.rpc:: RPC._on_response: GOT RESPONSE BUT REQUEST NOT PENDING reqid 1@n2n://5d9329c87b3046002a3f6a1a(75ewojo) connid n2n://5d9329c87b3046002a3f6a1a(75ewojo)
Oct-1 10:26:16.706 [WebServer/42] [WARN] core.rpc.rpc:: RPC._on_response: GOT RESPONSE BUT REQUEST NOT PENDING reqid 1@n2n://5d9329c87b3046002a3f6a1a(75ewojo) connid n2n://5d9329c87b3046002a3f6a1a(75ewojo)
Oct-1 10:26:16.706 [WebServer/42] [WARN] core.rpc.rpc:: RPC._on_response: GOT RESPONSE BUT REQUEST NOT PENDING reqid 1@n2n://5d9329c87b3046002a3f6a1a(75ewojo) connid n2n://5d9329c87b3046002a3f6a1a(75ewojo)
Oct-1 10:26:16.706 [WebServer/42] [WARN] core.rpc.rpc:: RPC._on_response: GOT RESPONSE BUT REQUEST NOT PENDING reqid 1@n2n://5d9329c87b3046002a3f6a1a(75ewojo) connid n2n://5d9329c87b3046002a3f6a1a(75ewojo)
Oct-1 10:26:16.706 [WebServer/42] [WARN] core.rpc.rpc:: RPC._on_response: GOT RESPONSE BUT REQUEST NOT PENDING reqid 1@n2n://5d9329c87b3046002a3f6a1a(75ewojo) connid n2n://5d9329c87b3046002a3f6a1a(75ewojo)
Oct-1 10:26:16.706 [WebServer/42] [L0] core.server.node_services.nodes_monitor:: _test_network_to_server:: Succeeded in sending n2n rpc to noobaa-internal-agent-5d9329c57b3046002a3f6a09 took 166
Oct-1 10:26:16.707 [WebServer/42] [L0] core.rpc.rpc_n2n:: _close undefined
```
### Expected behavior
1. there shouldn't be any messages
### Steps to reproduce
1. install a new system
2. look for `GOT RESPONSE BUT REQUEST NOT PENDING` in the logs
### More information - Screenshots / Logs / Other output | non_infrastructure | a lot of rpc warnings got response but request not pending probably on test network perf environment info noobaa version version platform kubernetes minikube openshift other specify actual behavior on a newly installed system there are a lot of log messages that shouldn t be there for the internal agent every time test network perf is called we can see warn messages with got response but request not pending oct core server node services nodes monitor test network to server noobaa internal agent oct core server node services nodes monitor test network perf success in test noobaa internal agent oct core agent block store services block store mongo head block block noobaa blocks blocks tree other blocks test store perf was not found oct core rpc rpc ws server ws accept connection ws oct core rpc rpc rpc on response got response but request not pending reqid connid oct core rpc rpc rpc on response got response but request not pending reqid connid oct core rpc rpc rpc on response got response but request not pending reqid connid oct core rpc rpc rpc on response got response but request not pending reqid connid oct core rpc rpc rpc on response got response but request not pending reqid connid oct core rpc rpc rpc on response got response but request not pending reqid connid oct core rpc rpc rpc on response got response but request not pending reqid connid oct core rpc rpc rpc on response got response but request not pending reqid connid oct core server node services nodes monitor test network to server succeeded in sending rpc to noobaa internal agent took oct core rpc rpc close undefined expected behavior there shouldn t be any messages steps to reproduce install a new system look for got response but request not pending in the logs more information screenshots logs other output | 0 |
315,820 | 27,109,031,418 | IssuesEvent | 2023-02-15 14:09:53 | rithmschool/numbers_api_v2 | https://api.github.com/repos/rithmschool/numbers_api_v2 | opened | Implement the math routes for requesting a single fact | t.test t.api | GET /api/math/:number (get single fact about a specific number)
GET /api/math/random (get single fact about a random number)
These are currently just stub routes that return a string of placeholder text. Each route should return JSON.
- we'd like to see your design plan for the JSON that's returned. Please reach out to discuss before implementing!
- take a look at the model- this category isn't limited to integers!
- think about validation that might be needed
- make sure routes are tested
Requests to /api/math/:number should respond with an appropriate status code and json when the number is not found:
```py
{ error: { message: f"A { category } fact for { number } not found", status: 404 } }
```
Make sure the actual response status code is also set to a 404 | 1.0 | Implement the math routes for requesting a single fact - GET /api/math/:number (get single fact about a specific number)
GET /api/math/random (get single fact about a random number)
These are currently just stub routes that return a string of placeholder text. Each route should return JSON.
- we'd like to see your design plan for the JSON that's returned. Please reach out to discuss before implementing!
- take a look at the model- this category isn't limited to integers!
- think about validation that might be needed
- make sure routes are tested
Requests to /api/math/:number should respond with an appropriate status code and json when the number is not found:
```py
{ error: { message: f"A { category } fact for { number } not found", status: 404 } }
```
Make sure the actual response status code is also set to a 404 | non_infrastructure | implement the math routes for requesting a single fact get api math number get single fact about a specific number get api math random get single fact about a random number these are currently just stub routes that return a string of placeholder text each route should return json we d like to see your design plan for the json that s returned please reach out to discuss before implementing take a look at the model this category isn t limited to integers think about validation that might be needed make sure routes are tested requests to api math number should respond with an appropriate status code and json when the number is not found py error message f a category fact for number not found status make sure the actual response status code is also set to a | 0 |
15,301 | 11,454,046,039 | IssuesEvent | 2020-02-06 16:23:40 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | opened | TargetFramework property isn't defined if there is no Outer-Build | area-Infrastructure-libraries | The new configuration system hooks into `DispatchToInnerBuilds` which doesn't run always, ie when a Target is directly invoked which doesn't go through the dispatching from outer to inner build procedure.
An example is `GenerateReferenceSource` target which uses the `IntermediateAssembly` item which is undefined because the IntermediatePath isn't set correctly: https://github.com/dotnet/runtime/blob/1a1a541954db674980b09efe426d3b6dfd6ae3c9/src/libraries/Directory.Build.targets#L134.
cc @Anipik @ericstj | 1.0 | TargetFramework property isn't defined if there is no Outer-Build - The new configuration system hooks into `DispatchToInnerBuilds` which doesn't run always, ie when a Target is directly invoked which doesn't go through the dispatching from outer to inner build procedure.
An example is `GenerateReferenceSource` target which uses the `IntermediateAssembly` item which is undefined because the IntermediatePath isn't set correctly: https://github.com/dotnet/runtime/blob/1a1a541954db674980b09efe426d3b6dfd6ae3c9/src/libraries/Directory.Build.targets#L134.
cc @Anipik @ericstj | infrastructure | targetframework property isn t defined if there is no outer build the new configuration system hooks into dispatchtoinnerbuilds which doesn t run always ie when a target is directly invoked which doesn t go through the dispatching from outer to inner build procedure an example is generatereferencesource target which uses the intermediateassembly item which is undefined because the intermediatepath isn t set correctly cc anipik ericstj | 1 |
175,217 | 13,540,333,092 | IssuesEvent | 2020-09-16 14:32:26 | eclipse/openj9 | https://api.github.com/repos/eclipse/openj9 | closed | JDK8 mac report failure when the test passed | test failure | Failure link
------------
https://ci.eclipse.org/openj9/job/Test_openjdk8_j9_sanity.functional_x86-64_mac_Nightly_testList_0/103/tapResults/
For example, to rebuild the failed tests in <Jenkins URL>=https://ci.eclipse.org/openj9/job/Grinder, use the following links:
23:43:23 https://ci.eclipse.org/openj9/job/Grinder/parambuild/?JDK_VERSION=8&JDK_IMPL=openj9&BUILD_LIST=functional&PLATFORM=x86-64_mac&TARGET=cmdLineTester_CryptoTest_0
Optional info
-------------
Failure output (captured from console output)
---------------------------------------------
```
===============================================
Running test cmdLineTester_CryptoTest_0 ...
===============================================
cmdLineTester_CryptoTest_0 Start Time: Fri Sep 11 23:26:21 2020 Epoch Time (ms): 1599881181332
variation: NoOptions
JVM_OPTIONS:
*** Starting test suite: OpenSSL Tests ***
Testing: CryptoTest
Test start time: 2020/09/11 23:26:21 Eastern Standard Time
Running command: "/Users/jenkins/workspace/Test_openjdk8_j9_sanity.functional_x86-64_mac_Nightly_testList_0/openjdkbinary/j2sdk-image/bin/java" -Djdk.nativeCryptoTrace=true -cp "/Users/jenkins/workspace/Test_openjdk8_j9_sanity.functional_x86-64_mac_Nightly_testList_0/openjdk-tests/TKG/../../jvmtest/functional/cmdLineTests/openssl/"openssltest.jar org.openj9.test.openssl.CryptoTest
Time spent starting: 44 milliseconds
Time spent executing: 328 milliseconds
Test result: PASSED
Output from test:
[OUT] Crypto test COMPLETED
[ERR] MessageDigest load - using Native crypto library.
[ERR] CipherCore Load - using native crypto library.
>> Success condition was found: [Output match: using native crypto library]
>> Required condition was found: [Output match: Crypto test COMPLETED]
>> Failure condition was not found: [Output match: Native crypto library load failed]
>> Failure condition was not found: [Output match: Crypto test FAILED]
---TEST RESULTS---
Number of PASSED tests: 1 out of 1
Number of FAILED tests: 0 out of 1
cmdLineTester_CryptoTest_0_FAILED
``` | 1.0 | JDK8 mac report failure when the test passed - Failure link
------------
https://ci.eclipse.org/openj9/job/Test_openjdk8_j9_sanity.functional_x86-64_mac_Nightly_testList_0/103/tapResults/
For example, to rebuild the failed tests in <Jenkins URL>=https://ci.eclipse.org/openj9/job/Grinder, use the following links:
23:43:23 https://ci.eclipse.org/openj9/job/Grinder/parambuild/?JDK_VERSION=8&JDK_IMPL=openj9&BUILD_LIST=functional&PLATFORM=x86-64_mac&TARGET=cmdLineTester_CryptoTest_0
Optional info
-------------
Failure output (captured from console output)
---------------------------------------------
```
===============================================
Running test cmdLineTester_CryptoTest_0 ...
===============================================
cmdLineTester_CryptoTest_0 Start Time: Fri Sep 11 23:26:21 2020 Epoch Time (ms): 1599881181332
variation: NoOptions
JVM_OPTIONS:
*** Starting test suite: OpenSSL Tests ***
Testing: CryptoTest
Test start time: 2020/09/11 23:26:21 Eastern Standard Time
Running command: "/Users/jenkins/workspace/Test_openjdk8_j9_sanity.functional_x86-64_mac_Nightly_testList_0/openjdkbinary/j2sdk-image/bin/java" -Djdk.nativeCryptoTrace=true -cp "/Users/jenkins/workspace/Test_openjdk8_j9_sanity.functional_x86-64_mac_Nightly_testList_0/openjdk-tests/TKG/../../jvmtest/functional/cmdLineTests/openssl/"openssltest.jar org.openj9.test.openssl.CryptoTest
Time spent starting: 44 milliseconds
Time spent executing: 328 milliseconds
Test result: PASSED
Output from test:
[OUT] Crypto test COMPLETED
[ERR] MessageDigest load - using Native crypto library.
[ERR] CipherCore Load - using native crypto library.
>> Success condition was found: [Output match: using native crypto library]
>> Required condition was found: [Output match: Crypto test COMPLETED]
>> Failure condition was not found: [Output match: Native crypto library load failed]
>> Failure condition was not found: [Output match: Crypto test FAILED]
---TEST RESULTS---
Number of PASSED tests: 1 out of 1
Number of FAILED tests: 0 out of 1
cmdLineTester_CryptoTest_0_FAILED
``` | non_infrastructure | mac report failure when the test passed failure link for example to rebuild the failed tests in use the following links optional info failure output captured from console output running test cmdlinetester cryptotest cmdlinetester cryptotest start time fri sep epoch time ms variation nooptions jvm options starting test suite openssl tests testing cryptotest test start time eastern standard time running command users jenkins workspace test sanity functional mac nightly testlist openjdkbinary image bin java djdk nativecryptotrace true cp users jenkins workspace test sanity functional mac nightly testlist openjdk tests tkg jvmtest functional cmdlinetests openssl openssltest jar org test openssl cryptotest time spent starting milliseconds time spent executing milliseconds test result passed output from test crypto test completed messagedigest load using native crypto library ciphercore load using native crypto library success condition was found required condition was found failure condition was not found failure condition was not found test results number of passed tests out of number of failed tests out of cmdlinetester cryptotest failed | 0 |
22,059 | 14,975,128,397 | IssuesEvent | 2021-01-28 05:24:14 | gnosis/safe-ios | https://api.github.com/repos/gnosis/safe-ios | opened | Release 2.9.0 | infrastructure | - [ ] Create a release task in GitHub using the “New Release” template.
- [ ] Create and push the release branch
```
git checkout main -b release/2.9.0
git push -u origin release/2.9.0
```
- [ ] Marketing version is updated (2.9.0)
```
agvtool new-marketing-version 2.9.0
```
- [ ] Notify QA
- [ ] QA approved release candidate build
- [ ] Product Owner approved submission
**AFTER PRODUCT OWNER APPROVAL**
- [ ] Submit to the App Store Review with developer approval for distribution
- [ ] Notify the team that release was submitted using the template below:
```
@here Hi everyone! We have submitted new iOS app v2.9.0 for review to the App Store.
```
- [ ] Create a new release in GitHub with release notes. This will create a tag. The tag should be in a format v2.9.0
- [ ] dSYMs are downloaded from AppStoreConnect and uploaded to Firebase Crashlytics.
```
# For the Multisig Production Rinkeby app:
> Pods/FirebaseCrashlytics/upload-symbols \
-gsp Multisig/Cross-layer/Analytics/Firebase/GoogleService-Info.Production.Rinkeby.plist \
-p ios /path/to/dSYMs
# For the Multisig app (App Store version):
> Pods/FirebaseCrashlytics/upload-symbols \
-gsp Multisig/Cross-layer/Analytics/Firebase/GoogleService-Info.Production.Mainnet.plist \
-p ios /path/to/dSYMs
```
- [ ] Release the app when it is approved by the App Store Review team (do not release on Thu/Fri). Notify the team using the following template:
```
@here Hi everyone! We have released the iOS app v2.9.0 to the App Store and it will soon be available for download.
```
- [ ] Merge the release branch to master branch via new pull-request
| 1.0 | Release 2.9.0 - - [ ] Create a release task in GitHub using the “New Release” template.
- [ ] Create and push the release branch
```
git checkout main -b release/2.9.0
git push -u origin release/2.9.0
```
- [ ] Marketing version is updated (2.9.0)
```
agvtool new-marketing-version 2.9.0
```
- [ ] Notify QA
- [ ] QA approved release candidate build
- [ ] Product Owner approved submission
**AFTER PRODUCT OWNER APPROVAL**
- [ ] Submit to the App Store Review with developer approval for distribution
- [ ] Notify the team that release was submitted using the template below:
```
@here Hi everyone! We have submitted new iOS app v2.9.0 for review to the App Store.
```
- [ ] Create a new release in GitHub with release notes. This will create a tag. The tag should be in a format v2.9.0
- [ ] dSYMs are downloaded from AppStoreConnect and uploaded to Firebase Crashlytics.
```
# For the Multisig Production Rinkeby app:
> Pods/FirebaseCrashlytics/upload-symbols \
-gsp Multisig/Cross-layer/Analytics/Firebase/GoogleService-Info.Production.Rinkeby.plist \
-p ios /path/to/dSYMs
# For the Multisig app (App Store version):
> Pods/FirebaseCrashlytics/upload-symbols \
-gsp Multisig/Cross-layer/Analytics/Firebase/GoogleService-Info.Production.Mainnet.plist \
-p ios /path/to/dSYMs
```
- [ ] Release the app when it is approved by the App Store Review team (do not release on Thu/Fri). Notify the team using the following template:
```
@here Hi everyone! We have released the iOS app v2.9.0 to the App Store and it will soon be available for download.
```
- [ ] Merge the release branch to master branch via new pull-request
| infrastructure | release create a release task in github using the “new release” template create and push the release branch git checkout main b release git push u origin release marketing version is updated agvtool new marketing version notify qa qa approved release candidate build product owner approved submission after product owner approval submit to the app store review with developer approval for distribution notify the team that release was submitted using the template below here hi everyone we have submitted new ios app for review to the app store create a new release in github with release notes this will create a tag the tag should be in a format dsyms are downloaded from appstoreconnect and uploaded to firebase crashlytics for the multisig production rinkeby app pods firebasecrashlytics upload symbols gsp multisig cross layer analytics firebase googleservice info production rinkeby plist p ios path to dsyms for the multisig app app store version pods firebasecrashlytics upload symbols gsp multisig cross layer analytics firebase googleservice info production mainnet plist p ios path to dsyms release the app when it is approved by the app store review team do not release on thu fri notify the team using the following template here hi everyone we have released the ios app to the app store and it will soon be available for download merge the release branch to master branch via new pull request | 1 |
24,807 | 17,791,171,119 | IssuesEvent | 2021-08-31 16:21:07 | dotnet/sdk | https://api.github.com/repos/dotnet/sdk | closed | SDK should not list test nupkgs in ItemsToSignPostBuild | Area-Infrastructure untriaged | The SDK pushes a bunch of test nupkgs that are consumed in dotnet/installer. These are currently listed in ItemsToSignPostBuild. This is less efficient than it could be, but also there are now files within the nupkgs that post-build signing doesn't have certs for:
https://dev.azure.com/dnceng/internal/_build/results?buildId=1314396&view=logs&j=9ff0e0af-24e7-5b0f-fa76-5e12fc9920ef&t=04e39753-8cfe-5fb5-2824-43b4c4b51e3b&l=278042 | 1.0 | SDK should not list test nupkgs in ItemsToSignPostBuild - The SDK pushes a bunch of test nupkgs that are consumed in dotnet/installer. These are currently listed in ItemsToSignPostBuild. This is less efficient than it could be, but also there are now files within the nupkgs that post-build signing doesn't have certs for:
https://dev.azure.com/dnceng/internal/_build/results?buildId=1314396&view=logs&j=9ff0e0af-24e7-5b0f-fa76-5e12fc9920ef&t=04e39753-8cfe-5fb5-2824-43b4c4b51e3b&l=278042 | infrastructure | sdk should not list test nupkgs in itemstosignpostbuild the sdk pushes a bunch of test nupkgs that are consumed in dotnet installer these are currently listed in itemstosignpostbuild this is less efficient than it could be but also there are now files within the nupkgs that post build signing doesn t have certs for | 1 |
13,257 | 3,135,401,882 | IssuesEvent | 2015-09-10 15:07:00 | cfpb/design-manual | https://api.github.com/repos/cfpb/design-manual | opened | Folder Minicon | design minicon font | ## CR Search will probably need to make use of an icon of a folder (to represent Collections, in our use case).
Starting a thread to document it's design. Some initial directions for Collections / Bookmarking that have us leaning in the folder direction.
| 1.0 | Folder Minicon - ## CR Search will probably need to make use of an icon of a folder (to represent Collections, in our use case).
Starting a thread to document it's design. Some initial directions for Collections / Bookmarking that have us leaning in the folder direction.
| non_infrastructure | folder minicon cr search will probably need to make use of an icon of a folder to represent collections in our use case starting a thread to document it s design some initial directions for collections bookmarking that have us leaning in the folder direction | 0 |
437 | 2,699,960,601 | IssuesEvent | 2015-04-03 21:13:59 | codeforamerica/communities | https://api.github.com/repos/codeforamerica/communities | closed | Build a new Brigade Sign Up Form | brigade infrastructure | Build the new version of the Brigade Sign up form. The work is happening at https://github.com/codeforamerica/brigade/issues/311
This will simplify the sign up process. People will get automatically get added to Mailchimp and the PeopleDB.
The form will be embeddable to individual Brigade sites as well.
#### Tasks
- [x] Build the new form - https://github.com/codeforamerica/brigade/issues/311
- [x] Have the PeopleDB accept the new form - https://github.com/codeforamerica/people-app/issues/11
- [x] Have Mailchimp accept the new form - https://github.com/codeforamerica/communities/issues/81 | 1.0 | Build a new Brigade Sign Up Form - Build the new version of the Brigade Sign up form. The work is happening at https://github.com/codeforamerica/brigade/issues/311
This will simplify the sign up process. People will get automatically get added to Mailchimp and the PeopleDB.
The form will be embeddable to individual Brigade sites as well.
#### Tasks
- [x] Build the new form - https://github.com/codeforamerica/brigade/issues/311
- [x] Have the PeopleDB accept the new form - https://github.com/codeforamerica/people-app/issues/11
- [x] Have Mailchimp accept the new form - https://github.com/codeforamerica/communities/issues/81 | infrastructure | build a new brigade sign up form build the new version of the brigade sign up form the work is happening at this will simplify the sign up process people will get automatically get added to mailchimp and the peopledb the form will be embeddable to individual brigade sites as well tasks build the new form have the peopledb accept the new form have mailchimp accept the new form | 1 |
46,100 | 13,150,337,707 | IssuesEvent | 2020-08-09 10:57:30 | shaundmorris/ddf | https://api.github.com/repos/shaundmorris/ddf | closed | CVE-2018-11697 High Severity Vulnerability detected by WhiteSource | security vulnerability wontfix | ## CVE-2018-11697 - High Severity Vulnerability
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-sassv4.9.4</b></p></summary>
<p>
<p>:rainbow: Node.js bindings to libsass</p>
<p>Library home page: <a href=https://github.com/sass/node-sass.git>https://github.com/sass/node-sass.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/shaundmorris/ddf/commit/ea35fc52f05b85ef437e9a9e39a887ad51692ff0">ea35fc52f05b85ef437e9a9e39a887ad51692ff0</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Library Source Files (121)</summary>
<p></p>
<p> * The source files were matched to this source library based on a best effort match. Source libraries are selected from a list of probable public libraries.</p>
<p>
- /ddf/ui/node_modules/node-sass/src/libsass/src/error_handling.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/output.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/output.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/check_nesting.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass_values.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/check_nesting.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/bind.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/test/test_node.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/constants.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/eval.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/plugins.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/include/sass/base.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/prelexer.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/subset_map.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/extend.cpp
- /ddf/ui/node_modules/node-sass/src/custom_importer_bridge.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/contrib/plugin.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/lexer.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass_util.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/test/test_superselector.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/cencode.c
- /ddf/ui/node_modules/node-sass/src/libsass/src/ast_fwd_decl.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/utf8_string.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/file.cpp
- /ddf/ui/node_modules/node-sass/src/callback_bridge.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/subset_map.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/include/sass2scss.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass_functions.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/emitter.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/environment.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/ast_def_macros.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/paths.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/expand.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/listize.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/test/test_unification.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/source_map.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/inspect.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/source_map.hpp
- /ddf/ui/node_modules/node-sass/src/sass_types/list.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass_functions.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/json.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass_util.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/position.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/listize.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/error_handling.hpp
- /ddf/ui/node_modules/node-sass/src/sass_types/string.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/eval.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/environment.hpp
- /ddf/ui/node_modules/node-sass/src/sass_types/boolean.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/emitter.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/extend.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/lexer.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/functions.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/debugger.hpp
- /ddf/ui/node_modules/node-sass/src/sass_types/factory.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/prelexer.cpp
- /ddf/ui/node_modules/node-sass/src/sass_types/color.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/operation.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/ast.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/constants.hpp
- /ddf/ui/node_modules/node-sass/src/sass_types/boolean.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/context.hpp
- /ddf/ui/node_modules/node-sass/src/sass_types/value.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/units.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/cssize.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/parser.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/functions.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/position.hpp
- /ddf/ui/node_modules/node-sass/src/sass_context_wrapper.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass_context.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/node.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/ast_fwd_decl.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/cssize.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/remove_placeholders.cpp
- /ddf/ui/node_modules/node-sass/src/binding.cpp
- /ddf/ui/node_modules/node-sass/src/sass_types/list.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/include/sass/functions.h
- /ddf/ui/node_modules/node-sass/src/custom_function_bridge.cpp
- /ddf/ui/node_modules/node-sass/src/custom_importer_bridge.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/color_maps.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/utf8_string.cpp
- /ddf/ui/node_modules/node-sass/src/sass_types/sass_value_wrapper.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/ast.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/values.cpp
- /ddf/ui/node_modules/node-sass/src/sass_context_wrapper.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/b64/encode.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/base64vlq.cpp
- /ddf/ui/node_modules/node-sass/src/sass_types/number.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/c99func.c
- /ddf/ui/node_modules/node-sass/src/libsass/src/node.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/remove_placeholders.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/util.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/memory/SharedPtr.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/backtrace.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/include/sass/values.h
- /ddf/ui/node_modules/node-sass/src/libsass/test/test_subset_map.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass2scss.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass_context.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/memory/SharedPtr.cpp
- /ddf/ui/node_modules/node-sass/src/sass_types/null.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/expand.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/to_value.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/context.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/include/sass/context.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/to_c.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass_values.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/color_maps.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/inspect.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/script/test-leaks.pl
- /ddf/ui/node_modules/node-sass/src/libsass/src/to_c.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/util.hpp
- /ddf/ui/node_modules/node-sass/src/sass_types/map.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/file.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/units.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/plugins.hpp
- /ddf/ui/node_modules/node-sass/src/sass_types/color.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/to_value.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/debug.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/parser.hpp
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in LibSass through 3.5.4. An out-of-bounds read of a memory region was found in the function Sass::Prelexer::exactly() which could be leveraged by an attacker to disclose information or manipulated to read from unmapped memory causing a denial of service.
<p>Publish Date: 2018-06-04
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11697>CVE-2018-11697</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-11697 High Severity Vulnerability detected by WhiteSource - ## CVE-2018-11697 - High Severity Vulnerability
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-sassv4.9.4</b></p></summary>
<p>
<p>:rainbow: Node.js bindings to libsass</p>
<p>Library home page: <a href=https://github.com/sass/node-sass.git>https://github.com/sass/node-sass.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/shaundmorris/ddf/commit/ea35fc52f05b85ef437e9a9e39a887ad51692ff0">ea35fc52f05b85ef437e9a9e39a887ad51692ff0</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Library Source Files (121)</summary>
<p></p>
<p> * The source files were matched to this source library based on a best effort match. Source libraries are selected from a list of probable public libraries.</p>
<p>
- /ddf/ui/node_modules/node-sass/src/libsass/src/error_handling.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/output.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/output.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/check_nesting.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass_values.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/check_nesting.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/bind.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/test/test_node.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/constants.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/eval.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/plugins.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/include/sass/base.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/prelexer.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/subset_map.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/extend.cpp
- /ddf/ui/node_modules/node-sass/src/custom_importer_bridge.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/contrib/plugin.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/lexer.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass_util.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/test/test_superselector.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/cencode.c
- /ddf/ui/node_modules/node-sass/src/libsass/src/ast_fwd_decl.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/utf8_string.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/file.cpp
- /ddf/ui/node_modules/node-sass/src/callback_bridge.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/subset_map.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/include/sass2scss.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass_functions.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/emitter.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/environment.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/ast_def_macros.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/paths.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/expand.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/listize.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/test/test_unification.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/source_map.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/inspect.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/source_map.hpp
- /ddf/ui/node_modules/node-sass/src/sass_types/list.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass_functions.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/json.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass_util.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/position.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/listize.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/error_handling.hpp
- /ddf/ui/node_modules/node-sass/src/sass_types/string.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/eval.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/environment.hpp
- /ddf/ui/node_modules/node-sass/src/sass_types/boolean.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/emitter.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/extend.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/lexer.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/functions.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/debugger.hpp
- /ddf/ui/node_modules/node-sass/src/sass_types/factory.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/prelexer.cpp
- /ddf/ui/node_modules/node-sass/src/sass_types/color.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/operation.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/ast.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/constants.hpp
- /ddf/ui/node_modules/node-sass/src/sass_types/boolean.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/context.hpp
- /ddf/ui/node_modules/node-sass/src/sass_types/value.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/units.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/cssize.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/parser.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/functions.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/position.hpp
- /ddf/ui/node_modules/node-sass/src/sass_context_wrapper.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass_context.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/node.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/ast_fwd_decl.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/cssize.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/remove_placeholders.cpp
- /ddf/ui/node_modules/node-sass/src/binding.cpp
- /ddf/ui/node_modules/node-sass/src/sass_types/list.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/include/sass/functions.h
- /ddf/ui/node_modules/node-sass/src/custom_function_bridge.cpp
- /ddf/ui/node_modules/node-sass/src/custom_importer_bridge.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/color_maps.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/utf8_string.cpp
- /ddf/ui/node_modules/node-sass/src/sass_types/sass_value_wrapper.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/ast.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/values.cpp
- /ddf/ui/node_modules/node-sass/src/sass_context_wrapper.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/b64/encode.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/base64vlq.cpp
- /ddf/ui/node_modules/node-sass/src/sass_types/number.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/c99func.c
- /ddf/ui/node_modules/node-sass/src/libsass/src/node.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/remove_placeholders.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/util.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/memory/SharedPtr.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/backtrace.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/include/sass/values.h
- /ddf/ui/node_modules/node-sass/src/libsass/test/test_subset_map.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass2scss.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass_context.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/memory/SharedPtr.cpp
- /ddf/ui/node_modules/node-sass/src/sass_types/null.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/expand.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/to_value.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/context.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/include/sass/context.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/to_c.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/sass_values.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/color_maps.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/inspect.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/script/test-leaks.pl
- /ddf/ui/node_modules/node-sass/src/libsass/src/to_c.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/util.hpp
- /ddf/ui/node_modules/node-sass/src/sass_types/map.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/file.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/units.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/plugins.hpp
- /ddf/ui/node_modules/node-sass/src/sass_types/color.h
- /ddf/ui/node_modules/node-sass/src/libsass/src/to_value.cpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/debug.hpp
- /ddf/ui/node_modules/node-sass/src/libsass/src/parser.hpp
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in LibSass through 3.5.4. An out-of-bounds read of a memory region was found in the function Sass::Prelexer::exactly() which could be leveraged by an attacker to disclose information or manipulated to read from unmapped memory causing a denial of service.
<p>Publish Date: 2018-06-04
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11697>CVE-2018-11697</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_infrastructure | cve high severity vulnerability detected by whitesource cve high severity vulnerability vulnerable library node rainbow node js bindings to libsass library home page a href found in head commit a href library source files the source files were matched to this source library based on a best effort match source libraries are selected from a list of probable public libraries ddf ui node modules node sass src libsass src error handling cpp ddf ui node modules node sass src libsass src output cpp ddf ui node modules node sass src libsass src output hpp ddf ui node modules node sass src libsass src check nesting cpp ddf ui node modules node sass src libsass src sass values hpp ddf ui node modules node sass src libsass src check nesting hpp ddf ui node modules node sass src libsass src bind cpp ddf ui node modules node sass src libsass test test node cpp ddf ui node modules node sass src libsass src constants cpp ddf ui node modules node sass src libsass src eval hpp ddf ui node modules node sass src libsass src plugins cpp ddf ui node modules node sass src libsass include sass base h ddf ui node modules node sass src libsass src prelexer hpp ddf ui node modules node sass src libsass src subset map hpp ddf ui node modules node sass src libsass src extend cpp ddf ui node modules node sass src custom importer bridge cpp ddf ui node modules node sass src libsass contrib plugin cpp ddf ui node modules node sass src libsass src lexer hpp ddf ui node modules node sass src libsass src sass util cpp ddf ui node modules node sass src libsass test test superselector cpp ddf ui node modules node sass src libsass src cencode c ddf ui node modules node sass src libsass src ast fwd decl hpp ddf ui node modules node sass src libsass src string hpp ddf ui node modules node sass src libsass src file cpp ddf ui node modules node sass src callback bridge h ddf ui node modules node sass src libsass src subset map cpp ddf ui node modules node sass src libsass include h ddf ui node modules node sass src libsass src sass functions hpp ddf ui node modules node sass src libsass src emitter cpp ddf ui node modules node sass src libsass src environment cpp ddf ui node modules node sass src libsass src ast def macros hpp ddf ui node modules node sass src libsass src paths hpp ddf ui node modules node sass src libsass src expand cpp ddf ui node modules node sass src libsass src listize cpp ddf ui node modules node sass src libsass test test unification cpp ddf ui node modules node sass src libsass src source map cpp ddf ui node modules node sass src libsass src inspect cpp ddf ui node modules node sass src libsass src source map hpp ddf ui node modules node sass src sass types list h ddf ui node modules node sass src libsass src sass functions cpp ddf ui node modules node sass src libsass src json cpp ddf ui node modules node sass src libsass src sass util hpp ddf ui node modules node sass src libsass src position cpp ddf ui node modules node sass src libsass src listize hpp ddf ui node modules node sass src libsass src error handling hpp ddf ui node modules node sass src sass types string cpp ddf ui node modules node sass src libsass src eval cpp ddf ui node modules node sass src libsass src environment hpp ddf ui node modules node sass src sass types boolean h ddf ui node modules node sass src libsass src emitter hpp ddf ui node modules node sass src libsass src extend hpp ddf ui node modules node sass src libsass src lexer cpp ddf ui node modules node sass src libsass src functions cpp ddf ui node modules node sass src libsass src debugger hpp ddf ui node modules node sass src sass types factory cpp ddf ui node modules node sass src libsass src prelexer cpp ddf ui node modules node sass src sass types color cpp ddf ui node modules node sass src libsass src operation hpp ddf ui node modules node sass src libsass src ast cpp ddf ui node modules node sass src libsass src sass hpp ddf ui node modules node sass src libsass src constants hpp ddf ui node modules node sass src sass types boolean cpp ddf ui node modules node sass src libsass src context hpp ddf ui node modules node sass src sass types value h ddf ui node modules node sass src libsass src units cpp ddf ui node modules node sass src libsass src cssize hpp ddf ui node modules node sass src libsass src parser cpp ddf ui node modules node sass src libsass src functions hpp ddf ui node modules node sass src libsass src position hpp ddf ui node modules node sass src sass context wrapper cpp ddf ui node modules node sass src libsass src sass context hpp ddf ui node modules node sass src libsass src node cpp ddf ui node modules node sass src libsass src ast fwd decl cpp ddf ui node modules node sass src libsass src cssize cpp ddf ui node modules node sass src libsass src remove placeholders cpp ddf ui node modules node sass src binding cpp ddf ui node modules node sass src sass types list cpp ddf ui node modules node sass src libsass include sass functions h ddf ui node modules node sass src custom function bridge cpp ddf ui node modules node sass src custom importer bridge h ddf ui node modules node sass src libsass src color maps cpp ddf ui node modules node sass src libsass src string cpp ddf ui node modules node sass src sass types sass value wrapper h ddf ui node modules node sass src libsass src ast hpp ddf ui node modules node sass src libsass src values cpp ddf ui node modules node sass src sass context wrapper h ddf ui node modules node sass src libsass src encode h ddf ui node modules node sass src libsass src sass cpp ddf ui node modules node sass src libsass src cpp ddf ui node modules node sass src sass types number cpp ddf ui node modules node sass src libsass src c ddf ui node modules node sass src libsass src node hpp ddf ui node modules node sass src libsass src remove placeholders hpp ddf ui node modules node sass src libsass src util cpp ddf ui node modules node sass src libsass src memory sharedptr hpp ddf ui node modules node sass src libsass src backtrace hpp ddf ui node modules node sass src libsass include sass values h ddf ui node modules node sass src libsass test test subset map cpp ddf ui node modules node sass src libsass src cpp ddf ui node modules node sass src libsass src sass context cpp ddf ui node modules node sass src libsass src memory sharedptr cpp ddf ui node modules node sass src sass types null cpp ddf ui node modules node sass src libsass src expand hpp ddf ui node modules node sass src libsass src to value hpp ddf ui node modules node sass src libsass src context cpp ddf ui node modules node sass src libsass include sass context h ddf ui node modules node sass src libsass src to c cpp ddf ui node modules node sass src libsass src sass values cpp ddf ui node modules node sass src libsass src color maps hpp ddf ui node modules node sass src libsass src inspect hpp ddf ui node modules node sass src libsass script test leaks pl ddf ui node modules node sass src libsass src to c hpp ddf ui node modules node sass src libsass src util hpp ddf ui node modules node sass src sass types map cpp ddf ui node modules node sass src libsass src file hpp ddf ui node modules node sass src libsass src units hpp ddf ui node modules node sass src libsass src plugins hpp ddf ui node modules node sass src sass types color h ddf ui node modules node sass src libsass src to value cpp ddf ui node modules node sass src libsass src debug hpp ddf ui node modules node sass src libsass src parser hpp vulnerability details an issue was discovered in libsass through an out of bounds read of a memory region was found in the function sass prelexer exactly which could be leveraged by an attacker to disclose information or manipulated to read from unmapped memory causing a denial of service publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact none availability impact high for more information on scores click a href step up your open source security game with whitesource | 0 |
335,658 | 30,079,555,781 | IssuesEvent | 2023-06-29 01:11:34 | tModLoader/tModLoader | https://api.github.com/repos/tModLoader/tModLoader | closed | Manual Install is Not Possible, no CSteamworks.dll in current steam release of Terraria (1.4.3.6) | Bug Needs Further Testing Requestor-Player | ### Version
Latest Official
### OS
Windows
### Platform
Steam
### This bug affects
Gameplay as a Player
### Description
Latest Steam Release of Terraria does not contain CSteamworks.dll, making manual installation from the steam version impossible.
### Log File
_No response_
### Steps to reproduce
1. Download a fresh installation of Terraria off of steam. (If you have a version of Terraria that has been updated from a previous version this will not work.)
### Expected Behavior
CSteamworks.dll should be present in the /Terraria folder.
### Actual Behavior
CSteamworks.dll isn't present in the /Terraria folder.
### Reproduction frequency
100% of the time.
### Additional Information
SteamDB does not show CSteamworks.dll in the current depot.
https://steamdb.info/depot/105601/ | 1.0 | Manual Install is Not Possible, no CSteamworks.dll in current steam release of Terraria (1.4.3.6) - ### Version
Latest Official
### OS
Windows
### Platform
Steam
### This bug affects
Gameplay as a Player
### Description
Latest Steam Release of Terraria does not contain CSteamworks.dll, making manual installation from the steam version impossible.
### Log File
_No response_
### Steps to reproduce
1. Download a fresh installation of Terraria off of steam. (If you have a version of Terraria that has been updated from a previous version this will not work.)
### Expected Behavior
CSteamworks.dll should be present in the /Terraria folder.
### Actual Behavior
CSteamworks.dll isn't present in the /Terraria folder.
### Reproduction frequency
100% of the time.
### Additional Information
SteamDB does not show CSteamworks.dll in the current depot.
https://steamdb.info/depot/105601/ | non_infrastructure | manual install is not possible no csteamworks dll in current steam release of terraria version latest official os windows platform steam this bug affects gameplay as a player description latest steam release of terraria does not contain csteamworks dll making manual installation from the steam version impossible log file no response steps to reproduce download a fresh installation of terraria off of steam if you have a version of terraria that has been updated from a previous version this will not work expected behavior csteamworks dll should be present in the terraria folder actual behavior csteamworks dll isn t present in the terraria folder reproduction frequency of the time additional information steamdb does not show csteamworks dll in the current depot | 0 |
46,469 | 19,214,582,724 | IssuesEvent | 2021-12-07 08:02:56 | Azure/azure-sdk-for-python | https://api.github.com/repos/Azure/azure-sdk-for-python | closed | Unable to iterate over the entire results of policy_states.list_query_results_for_subscription. | bug Policy Insights Service Attention Mgmt customer-reported no-recent-activity needs-author-feedback | - **Package Name**: azure.mgmt.policyinsights
- **Package Version**: 1.0.0
- **Operating System**: MacOS
- **Python Version**: 3.7
**Describe the bug**
The issue happens when trying to list the policy state of entire subscription.
After instantiating `PolicyInsightsClient` and iterating over the results returned by `client.policy_states.list_query_results_for_subscription(...)`, the following exception is thrown
```
File "/Users/ashishg/****/venv/lib/python3.7/site-packages/azure/mgmt/policyinsights/operations/_policy_states_operations.py", line 352, in get_next
raise HttpResponseError(response=response, model=error, error_format=ARMErrorFormat)
azure.core.exceptions.HttpResponseError: (HttpMethodNotSupported) The http method 'GET' is not supported for 'queryResults'.
```
Only the first 1000 policy state results are listed and when the client goes on to fetch the next 1000 results it errors out with the above exception.
The issue is happening because the Policy States List API (https://docs.microsoft.com/en-us/rest/api/policy/policystates/listqueryresultsforsubscription) expects the URL returned by `@odata.nextLink` attribute to be called over POST and not GET.
The problem seems to in line,
https://github.com/Azure/azure-sdk-for-python/blob/447e6f766ac809b95bac65e72752c44a59ea073f/sdk/policyinsights/azure-mgmt-policyinsights/azure/mgmt/policyinsights/operations/_policy_states_operations.py#L139
Things start to work, on changing the line from `request = self._client.get(url, query_parameters, header_parameters)`
to
`request = self._client.post(url, query_parameters, header_parameters)`
**To Reproduce**
Steps to reproduce the behavior:
1. `pip install azure-mgmt-policyinsights` (latest version which is 1.0.0)
2. Run the following simple snippet to reproduce the issue.
NOTE: Make sure that the subscription this is tried upon has more than 1000 policy state results.
```
from azure.mgmt.policyinsights._policy_insights_client import PolicyInsightsClient
#credential = <Create the credential object here>
#sub_id = <some subscription id>
client = PolicyInsightsClient(cred, base_url=mavlink_helpers.get_arm_base_url(tenant_region), subscription_id=sub_id)
policy_states = client.policy_states.list_query_results_for_subscription(policy_states_resource="latest",
subscription_id=sub_id)
for policy_state in policy_states:
policy_state = policy_state.as_dict()
print(policy_state['policy_definition_id'], policy_state['resource_id'])
```
**Expected behavior**
One should be able to iterate over the entire list of policy states.
| 1.0 | Unable to iterate over the entire results of policy_states.list_query_results_for_subscription. - - **Package Name**: azure.mgmt.policyinsights
- **Package Version**: 1.0.0
- **Operating System**: MacOS
- **Python Version**: 3.7
**Describe the bug**
The issue happens when trying to list the policy state of entire subscription.
After instantiating `PolicyInsightsClient` and iterating over the results returned by `client.policy_states.list_query_results_for_subscription(...)`, the following exception is thrown
```
File "/Users/ashishg/****/venv/lib/python3.7/site-packages/azure/mgmt/policyinsights/operations/_policy_states_operations.py", line 352, in get_next
raise HttpResponseError(response=response, model=error, error_format=ARMErrorFormat)
azure.core.exceptions.HttpResponseError: (HttpMethodNotSupported) The http method 'GET' is not supported for 'queryResults'.
```
Only the first 1000 policy state results are listed and when the client goes on to fetch the next 1000 results it errors out with the above exception.
The issue is happening because the Policy States List API (https://docs.microsoft.com/en-us/rest/api/policy/policystates/listqueryresultsforsubscription) expects the URL returned by `@odata.nextLink` attribute to be called over POST and not GET.
The problem seems to in line,
https://github.com/Azure/azure-sdk-for-python/blob/447e6f766ac809b95bac65e72752c44a59ea073f/sdk/policyinsights/azure-mgmt-policyinsights/azure/mgmt/policyinsights/operations/_policy_states_operations.py#L139
Things start to work, on changing the line from `request = self._client.get(url, query_parameters, header_parameters)`
to
`request = self._client.post(url, query_parameters, header_parameters)`
**To Reproduce**
Steps to reproduce the behavior:
1. `pip install azure-mgmt-policyinsights` (latest version which is 1.0.0)
2. Run the following simple snippet to reproduce the issue.
NOTE: Make sure that the subscription this is tried upon has more than 1000 policy state results.
```
from azure.mgmt.policyinsights._policy_insights_client import PolicyInsightsClient
#credential = <Create the credential object here>
#sub_id = <some subscription id>
client = PolicyInsightsClient(cred, base_url=mavlink_helpers.get_arm_base_url(tenant_region), subscription_id=sub_id)
policy_states = client.policy_states.list_query_results_for_subscription(policy_states_resource="latest",
subscription_id=sub_id)
for policy_state in policy_states:
policy_state = policy_state.as_dict()
print(policy_state['policy_definition_id'], policy_state['resource_id'])
```
**Expected behavior**
One should be able to iterate over the entire list of policy states.
| non_infrastructure | unable to iterate over the entire results of policy states list query results for subscription package name azure mgmt policyinsights package version operating system macos python version describe the bug the issue happens when trying to list the policy state of entire subscription after instantiating policyinsightsclient and iterating over the results returned by client policy states list query results for subscription the following exception is thrown file users ashishg venv lib site packages azure mgmt policyinsights operations policy states operations py line in get next raise httpresponseerror response response model error error format armerrorformat azure core exceptions httpresponseerror httpmethodnotsupported the http method get is not supported for queryresults only the first policy state results are listed and when the client goes on to fetch the next results it errors out with the above exception the issue is happening because the policy states list api expects the url returned by odata nextlink attribute to be called over post and not get the problem seems to in line things start to work on changing the line from request self client get url query parameters header parameters to request self client post url query parameters header parameters to reproduce steps to reproduce the behavior pip install azure mgmt policyinsights latest version which is run the following simple snippet to reproduce the issue note make sure that the subscription this is tried upon has more than policy state results from azure mgmt policyinsights policy insights client import policyinsightsclient credential sub id client policyinsightsclient cred base url mavlink helpers get arm base url tenant region subscription id sub id policy states client policy states list query results for subscription policy states resource latest subscription id sub id for policy state in policy states policy state policy state as dict print policy state policy state expected behavior one should be able to iterate over the entire list of policy states | 0 |
21,559 | 14,633,120,070 | IssuesEvent | 2020-12-24 00:44:44 | sigp/lighthouse | https://api.github.com/repos/sigp/lighthouse | closed | Fallback eth1 node and beacon node | A1 enhancement t Infrastructure CI CD Docker Directories | It would be nice to add CLI flags for a fallback eth1 node and for the VC a fallback BN.
The logic would be that if the designated eth1 node doesn't work (i.e a local eth1 node) we attempt to connect to the fallback eth1 node.
Similarly for the VC have a backup BN if the http connection fails.
| 1.0 | Fallback eth1 node and beacon node - It would be nice to add CLI flags for a fallback eth1 node and for the VC a fallback BN.
The logic would be that if the designated eth1 node doesn't work (i.e a local eth1 node) we attempt to connect to the fallback eth1 node.
Similarly for the VC have a backup BN if the http connection fails.
| infrastructure | fallback node and beacon node it would be nice to add cli flags for a fallback node and for the vc a fallback bn the logic would be that if the designated node doesn t work i e a local node we attempt to connect to the fallback node similarly for the vc have a backup bn if the http connection fails | 1 |
27,893 | 22,584,761,964 | IssuesEvent | 2022-06-28 14:26:10 | coq/coq | https://api.github.com/repos/coq/coq | closed | Makefile not insensitive to environment | kind: infrastructure | <!-- Thank you for your contribution.
Please complete the following information when reporting a bug. -->
#### Version
<!-- You can get this information by running `coqtop -v`. -->
#### Operating system
Platform Independent
#### Description of the problem
<!-- It is helpful to provide enough information so that we can reproduce the bug.
In particular, please include a code example which produces it.
If the example is small, you can include it here between ``` ```.
Otherwise, please provide a link to a repository, a gist (https://gist.github.com)
or drag-and-drop a `.zip` archive. -->
I'm seeing compilation problems with `make` that indicate that we're not using the information about ocaml/ocamlfind/etc.. that are set at `./configure` time of Coq and instead rely on non-canonical paths for these tools. Typical workflow to reproduce:
``./configure && make && opam switch blah && eval `opam config env` && touch kernel/univ.ml && make`` | 1.0 | Makefile not insensitive to environment - <!-- Thank you for your contribution.
Please complete the following information when reporting a bug. -->
#### Version
<!-- You can get this information by running `coqtop -v`. -->
#### Operating system
Platform Independent
#### Description of the problem
<!-- It is helpful to provide enough information so that we can reproduce the bug.
In particular, please include a code example which produces it.
If the example is small, you can include it here between ``` ```.
Otherwise, please provide a link to a repository, a gist (https://gist.github.com)
or drag-and-drop a `.zip` archive. -->
I'm seeing compilation problems with `make` that indicate that we're not using the information about ocaml/ocamlfind/etc.. that are set at `./configure` time of Coq and instead rely on non-canonical paths for these tools. Typical workflow to reproduce:
``./configure && make && opam switch blah && eval `opam config env` && touch kernel/univ.ml && make`` | infrastructure | makefile not insensitive to environment thank you for your contribution please complete the following information when reporting a bug version operating system platform independent description of the problem it is helpful to provide enough information so that we can reproduce the bug in particular please include a code example which produces it if the example is small you can include it here between otherwise please provide a link to a repository a gist or drag and drop a zip archive i m seeing compilation problems with make that indicate that we re not using the information about ocaml ocamlfind etc that are set at configure time of coq and instead rely on non canonical paths for these tools typical workflow to reproduce configure make opam switch blah eval opam config env touch kernel univ ml make | 1 |
95,272 | 3,941,442,015 | IssuesEvent | 2016-04-27 07:44:48 | BugBusterSWE/documentation | https://api.github.com/repos/BugBusterSWE/documentation | opened | Configurazione Jenkins | Administrator priority:high | Documento in cui si trova il problema:
Activity #296
Descrizione del problema:
Configurare Jankins
Link task: [https://bugbusters.teamwork.com/tasks/6461047](https://bugbusters.teamwork.com/tasks/6461047) | 1.0 | Configurazione Jenkins - Documento in cui si trova il problema:
Activity #296
Descrizione del problema:
Configurare Jankins
Link task: [https://bugbusters.teamwork.com/tasks/6461047](https://bugbusters.teamwork.com/tasks/6461047) | non_infrastructure | configurazione jenkins documento in cui si trova il problema activity descrizione del problema configurare jankins link task | 0 |
191,065 | 14,593,170,092 | IssuesEvent | 2020-12-19 21:18:40 | kalexmills/github-vet-tests-dec2020 | https://api.github.com/repos/kalexmills/github-vet-tests-dec2020 | opened | chen-kaka/sweetcook-backend: vendor/gopkg.in/mgo.v2/session_test.go; 5 LoC | fresh test tiny vendored |
Found a possible issue in [chen-kaka/sweetcook-backend](https://www.github.com/chen-kaka/sweetcook-backend) at [vendor/gopkg.in/mgo.v2/session_test.go](https://github.com/chen-kaka/sweetcook-backend/blob/a2cda1843374d9f11e1b113c63f3030fd8d29c2e/vendor/gopkg.in/mgo.v2/session_test.go#L3502-L3506)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> function call which takes a reference to item at line 3503 may start a goroutine
[Click here to see the code in its original context.](https://github.com/chen-kaka/sweetcook-backend/blob/a2cda1843374d9f11e1b113c63f3030fd8d29c2e/vendor/gopkg.in/mgo.v2/session_test.go#L3502-L3506)
<details>
<summary>Click here to show the 5 line(s) of Go which triggered the analyzer.</summary>
```go
for _, item := range result {
c.Logf("Item: %#v", &item)
c.Assert(item.Value.Count, Equals, expected[item.Id])
expected[item.Id] = -1
}
```
</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: a2cda1843374d9f11e1b113c63f3030fd8d29c2e
| 1.0 | chen-kaka/sweetcook-backend: vendor/gopkg.in/mgo.v2/session_test.go; 5 LoC -
Found a possible issue in [chen-kaka/sweetcook-backend](https://www.github.com/chen-kaka/sweetcook-backend) at [vendor/gopkg.in/mgo.v2/session_test.go](https://github.com/chen-kaka/sweetcook-backend/blob/a2cda1843374d9f11e1b113c63f3030fd8d29c2e/vendor/gopkg.in/mgo.v2/session_test.go#L3502-L3506)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> function call which takes a reference to item at line 3503 may start a goroutine
[Click here to see the code in its original context.](https://github.com/chen-kaka/sweetcook-backend/blob/a2cda1843374d9f11e1b113c63f3030fd8d29c2e/vendor/gopkg.in/mgo.v2/session_test.go#L3502-L3506)
<details>
<summary>Click here to show the 5 line(s) of Go which triggered the analyzer.</summary>
```go
for _, item := range result {
c.Logf("Item: %#v", &item)
c.Assert(item.Value.Count, Equals, expected[item.Id])
expected[item.Id] = -1
}
```
</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: a2cda1843374d9f11e1b113c63f3030fd8d29c2e
| non_infrastructure | chen kaka sweetcook backend vendor gopkg in mgo session test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message function call which takes a reference to item at line may start a goroutine click here to show the line s of go which triggered the analyzer go for item range result c logf item v item c assert item value count equals expected expected 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 | 0 |
142,101 | 5,452,746,773 | IssuesEvent | 2017-03-08 04:38:16 | 90301/Crescent-CRM-V | https://api.github.com/repos/90301/Crescent-CRM-V | closed | Empty XML Field exception | bug High Priority |
org.w3c.dom.DOMException: INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified.
at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.createElement(Unknown Source)
at dbUtils.InhalerUtils.mapToXML(InhalerUtils.java:178)
at dbUtils.Conversions.ClientFieldMapToString.convertToStore(ClientFieldMapToString.java:23)
at dbUtils.Conversions.ClientFieldMapToString.convertToStore(ClientFieldMapToString.java:1)
at dbUtils.MaxField.getConvertedFieldValue(MaxField.java:131)
at dbUtils.MaxObject.autoGenUpdateDBMap(MaxObject.java:450)
at dbUtils.MaxObject.updateDBMap(MaxObject.java:269)
at clientInfo.Client.setupCustomFieldsFromTemplate(Client.java:325)
at clientInfo.Client.setCustomFieldValue(Client.java:337)
at uiElements.CustomFieldEditor.updateClient(CustomFieldEditor.java:87)
at uiElements.ClientEditor.updateClientClick(ClientEditor.java:200)
at uiElements.ClientEditor.lambda$0(ClientEditor.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:508)
at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:198)
at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:161)
at com.vaadin.server.AbstractClientConnector.fireEvent(AbstractClientConnector.java:1008)
at com.vaadin.ui.Button.fireClick(Button.java:377)
at com.vaadin.ui.Button$1.click(Button.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.vaadin.server.ServerRpcManager.applyInvocation(ServerRpcManager.java:158)
at com.vaadin.server.ServerRpcManager.applyInvocation(ServerRpcManager.java:118)
at com.vaadin.server.communication.ServerRpcHandler.handleInvocation(ServerRpcHandler.java:437)
at com.vaadin.server.communication.ServerRpcHandler.handleInvocations(ServerRpcHandler.java:408)
at com.vaadin.server.communication.ServerRpcHandler.handleRpc(ServerRpcHandler.java:273)
at com.vaadin.server.communication.UidlRequestHandler.synchronizedHandleRequest(UidlRequestHandler.java:90)
at com.vaadin.server.SynchronizedRequestHandler.handleRequest(SynchronizedRequestHandler.java:41)
at com.vaadin.server.VaadinService.handleRequest(VaadinService.java:1414)
at com.vaadin.server.VaadinServlet.service(VaadinServlet.java:365)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:474)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:624)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:349)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:495)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:767)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1347)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Unknown Source) | 1.0 | Empty XML Field exception -
org.w3c.dom.DOMException: INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified.
at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.createElement(Unknown Source)
at dbUtils.InhalerUtils.mapToXML(InhalerUtils.java:178)
at dbUtils.Conversions.ClientFieldMapToString.convertToStore(ClientFieldMapToString.java:23)
at dbUtils.Conversions.ClientFieldMapToString.convertToStore(ClientFieldMapToString.java:1)
at dbUtils.MaxField.getConvertedFieldValue(MaxField.java:131)
at dbUtils.MaxObject.autoGenUpdateDBMap(MaxObject.java:450)
at dbUtils.MaxObject.updateDBMap(MaxObject.java:269)
at clientInfo.Client.setupCustomFieldsFromTemplate(Client.java:325)
at clientInfo.Client.setCustomFieldValue(Client.java:337)
at uiElements.CustomFieldEditor.updateClient(CustomFieldEditor.java:87)
at uiElements.ClientEditor.updateClientClick(ClientEditor.java:200)
at uiElements.ClientEditor.lambda$0(ClientEditor.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:508)
at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:198)
at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:161)
at com.vaadin.server.AbstractClientConnector.fireEvent(AbstractClientConnector.java:1008)
at com.vaadin.ui.Button.fireClick(Button.java:377)
at com.vaadin.ui.Button$1.click(Button.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.vaadin.server.ServerRpcManager.applyInvocation(ServerRpcManager.java:158)
at com.vaadin.server.ServerRpcManager.applyInvocation(ServerRpcManager.java:118)
at com.vaadin.server.communication.ServerRpcHandler.handleInvocation(ServerRpcHandler.java:437)
at com.vaadin.server.communication.ServerRpcHandler.handleInvocations(ServerRpcHandler.java:408)
at com.vaadin.server.communication.ServerRpcHandler.handleRpc(ServerRpcHandler.java:273)
at com.vaadin.server.communication.UidlRequestHandler.synchronizedHandleRequest(UidlRequestHandler.java:90)
at com.vaadin.server.SynchronizedRequestHandler.handleRequest(SynchronizedRequestHandler.java:41)
at com.vaadin.server.VaadinService.handleRequest(VaadinService.java:1414)
at com.vaadin.server.VaadinServlet.service(VaadinServlet.java:365)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:474)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:624)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:349)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:495)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:767)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1347)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Unknown Source) | non_infrastructure | empty xml field exception org dom domexception invalid character err an invalid or illegal xml character is specified at com sun org apache xerces internal dom coredocumentimpl createelement unknown source at dbutils inhalerutils maptoxml inhalerutils java at dbutils conversions clientfieldmaptostring converttostore clientfieldmaptostring java at dbutils conversions clientfieldmaptostring converttostore clientfieldmaptostring java at dbutils maxfield getconvertedfieldvalue maxfield java at dbutils maxobject autogenupdatedbmap maxobject java at dbutils maxobject updatedbmap maxobject java at clientinfo client setupcustomfieldsfromtemplate client java at clientinfo client setcustomfieldvalue client java at uielements customfieldeditor updateclient customfieldeditor java at uielements clienteditor updateclientclick clienteditor java at uielements clienteditor lambda clienteditor java at sun reflect nativemethodaccessorimpl native method at sun reflect nativemethodaccessorimpl invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke unknown source at java lang reflect method invoke unknown source at com vaadin event listenermethod receiveevent listenermethod java at com vaadin event eventrouter fireevent eventrouter java at com vaadin event eventrouter fireevent eventrouter java at com vaadin server abstractclientconnector fireevent abstractclientconnector java at com vaadin ui button fireclick button java at com vaadin ui button click button java at sun reflect nativemethodaccessorimpl native method at sun reflect nativemethodaccessorimpl invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke unknown source at java lang reflect method invoke unknown source at com vaadin server serverrpcmanager applyinvocation serverrpcmanager java at com vaadin server serverrpcmanager applyinvocation serverrpcmanager java at com vaadin server communication serverrpchandler handleinvocation serverrpchandler java at com vaadin server communication serverrpchandler handleinvocations serverrpchandler java at com vaadin server communication serverrpchandler handlerpc serverrpchandler java at com vaadin server communication uidlrequesthandler synchronizedhandlerequest uidlrequesthandler java at com vaadin server synchronizedrequesthandler handlerequest synchronizedrequesthandler java at com vaadin server vaadinservice handlerequest vaadinservice java at com vaadin server vaadinservlet service vaadinservlet java at javax servlet http httpservlet service httpservlet java at org apache catalina core applicationfilterchain internaldofilter applicationfilterchain java at org apache catalina core applicationfilterchain dofilter applicationfilterchain java at org apache tomcat websocket server wsfilter dofilter wsfilter java at org apache catalina core applicationfilterchain internaldofilter applicationfilterchain java at org apache catalina core applicationfilterchain dofilter applicationfilterchain java at org apache catalina core standardwrappervalve invoke standardwrappervalve java at org apache catalina core standardcontextvalve invoke standardcontextvalve java at org apache catalina authenticator authenticatorbase invoke authenticatorbase java at org apache catalina core standardhostvalve invoke standardhostvalve java at org apache catalina valves errorreportvalve invoke errorreportvalve java at org apache catalina valves abstractaccesslogvalve invoke abstractaccesslogvalve java at org apache catalina core standardenginevalve invoke standardenginevalve java at org apache catalina connector coyoteadapter service coyoteadapter java at org apache coyote service java at org apache coyote abstractprocessorlight process abstractprocessorlight java at org apache coyote abstractprotocol connectionhandler process abstractprotocol java at org apache tomcat util net nioendpoint socketprocessor dorun nioendpoint java at org apache tomcat util net socketprocessorbase run socketprocessorbase java at java util concurrent threadpoolexecutor runworker unknown source at java util concurrent threadpoolexecutor worker run unknown source at org apache tomcat util threads taskthread wrappingrunnable run taskthread java at java lang thread run unknown source | 0 |
22,878 | 15,594,399,525 | IssuesEvent | 2021-03-18 13:52:20 | google/web-stories-wp | https://api.github.com/repos/google/web-stories-wp | closed | Widget: E2E Tests | Group: Widgets Pod: WP & Infra Type: Infrastructure | <!-- NOTE: For help requests, support questions, or general feedback, please use the WordPress.org forums instead: https://wordpress.org/support/plugin/web-stories/ -->
## Task Description
Due to the nature of how WordPress widgets are built, E2E tests are the only way the Web Stories widget can really be tested.
So it would be good to have some E2E test coverage, either via the Widgets screen or the customizer, whatever works best.
| 1.0 | Widget: E2E Tests - <!-- NOTE: For help requests, support questions, or general feedback, please use the WordPress.org forums instead: https://wordpress.org/support/plugin/web-stories/ -->
## Task Description
Due to the nature of how WordPress widgets are built, E2E tests are the only way the Web Stories widget can really be tested.
So it would be good to have some E2E test coverage, either via the Widgets screen or the customizer, whatever works best.
| infrastructure | widget tests task description due to the nature of how wordpress widgets are built tests are the only way the web stories widget can really be tested so it would be good to have some test coverage either via the widgets screen or the customizer whatever works best | 1 |
124,237 | 26,427,327,082 | IssuesEvent | 2023-01-14 10:55:30 | KjellooMelloo/gameoftrons | https://api.github.com/repos/KjellooMelloo/gameoftrons | closed | maxWaitingTime bei join() hinzufügen | tron-code | maxWaitingTime als zweiten Parameter bei join() übergeben
lokale Variable in join()-Methode für die Wartezeit setzen | 1.0 | maxWaitingTime bei join() hinzufügen - maxWaitingTime als zweiten Parameter bei join() übergeben
lokale Variable in join()-Methode für die Wartezeit setzen | non_infrastructure | maxwaitingtime bei join hinzufügen maxwaitingtime als zweiten parameter bei join übergeben lokale variable in join methode für die wartezeit setzen | 0 |
28,482 | 23,287,924,602 | IssuesEvent | 2022-08-05 18:41:31 | accessibility-exchange/platform | https://api.github.com/repos/accessibility-exchange/platform | opened | CI: Implement a cron that runs the sheduler. | infrastructure | - Should run once a minute.
- Should exec the following command in the **accessibility-app** container.
```bash
php artisan schedule:run
``` | 1.0 | CI: Implement a cron that runs the sheduler. - - Should run once a minute.
- Should exec the following command in the **accessibility-app** container.
```bash
php artisan schedule:run
``` | infrastructure | ci implement a cron that runs the sheduler should run once a minute should exec the following command in the accessibility app container bash php artisan schedule run | 1 |
1,151 | 3,052,383,482 | IssuesEvent | 2015-08-12 14:28:21 | codhab/management | https://api.github.com/repos/codhab/management | closed | ambiente de homologação | infrastructure maintenance new feature | ### descrição ###
criação de um ambiente de homologação de integração contínua.
| 1.0 | ambiente de homologação - ### descrição ###
criação de um ambiente de homologação de integração contínua.
| infrastructure | ambiente de homologação descrição criação de um ambiente de homologação de integração contínua | 1 |
14,748 | 11,100,475,637 | IssuesEvent | 2019-12-16 19:17:17 | cockroachdb/docs | https://api.github.com/repos/cockroachdb/docs | closed | local htmltest runs no longer pass in a post-managed-docs world | A-docs-infrastructure T-something-broken fixitday | Sorry if there is an issue filed against this behavior already, a search for "is:open htmltest" didn't find it!
tl;dr: `htmltest` no longer passes when run locally, so we're flying blind until we push to Github and see the green check (I think? Happy to be wrong about this, maybe I'm doing something wrong locally).
Relates to #3301, #3833.
Full version:
If you run `make standard` and your build output directory contains `_site/docs`, local runs of `htmltest -s` return the following:
htmltest -s
Skipping the checking of external links.
htmltest started at 03:32:28 on _site
========================================================================
running in concurrent mode, this is experimental
docs/releases/v2.1.0.html
target does not exist --- docs/releases/v2.1.0.html --> ../managed/v2.1/
target does not exist --- docs/releases/v2.1.0.html --> ../managed/v2.1/managed-sign-up-for-a-cluster.html
docs/v2.1/frequently-asked-questions.html
target does not exist --- docs/v2.1/frequently-asked-questions.html --> ../managed/v2.1/
docs/v2.2/frequently-asked-questions.html
target does not exist --- docs/v2.2/frequently-asked-questions.html --> ../managed/v2.1/
========================================================================
âââ failed in 2.196259095s
4 errors in 1962 documents
If you then run `make managed` and your build output directory contains both `_site/docs` and `_site/managed`, local runs of `htmltest -s` return a giant list of errors that I will attach below.
[foo.txt](https://github.com/cockroachdb/docs/files/2605750/foo.txt) | 1.0 | local htmltest runs no longer pass in a post-managed-docs world - Sorry if there is an issue filed against this behavior already, a search for "is:open htmltest" didn't find it!
tl;dr: `htmltest` no longer passes when run locally, so we're flying blind until we push to Github and see the green check (I think? Happy to be wrong about this, maybe I'm doing something wrong locally).
Relates to #3301, #3833.
Full version:
If you run `make standard` and your build output directory contains `_site/docs`, local runs of `htmltest -s` return the following:
htmltest -s
Skipping the checking of external links.
htmltest started at 03:32:28 on _site
========================================================================
running in concurrent mode, this is experimental
docs/releases/v2.1.0.html
target does not exist --- docs/releases/v2.1.0.html --> ../managed/v2.1/
target does not exist --- docs/releases/v2.1.0.html --> ../managed/v2.1/managed-sign-up-for-a-cluster.html
docs/v2.1/frequently-asked-questions.html
target does not exist --- docs/v2.1/frequently-asked-questions.html --> ../managed/v2.1/
docs/v2.2/frequently-asked-questions.html
target does not exist --- docs/v2.2/frequently-asked-questions.html --> ../managed/v2.1/
========================================================================
âââ failed in 2.196259095s
4 errors in 1962 documents
If you then run `make managed` and your build output directory contains both `_site/docs` and `_site/managed`, local runs of `htmltest -s` return a giant list of errors that I will attach below.
[foo.txt](https://github.com/cockroachdb/docs/files/2605750/foo.txt) | infrastructure | local htmltest runs no longer pass in a post managed docs world sorry if there is an issue filed against this behavior already a search for is open htmltest didn t find it tl dr htmltest no longer passes when run locally so we re flying blind until we push to github and see the green check i think happy to be wrong about this maybe i m doing something wrong locally relates to full version if you run make standard and your build output directory contains site docs local runs of htmltest s return the following htmltest s skipping the checking of external links htmltest started at on site running in concurrent mode this is experimental docs releases html target does not exist docs releases html managed target does not exist docs releases html managed managed sign up for a cluster html docs frequently asked questions html target does not exist docs frequently asked questions html managed docs frequently asked questions html target does not exist docs frequently asked questions html managed âââ failed in errors in documents if you then run make managed and your build output directory contains both site docs and site managed local runs of htmltest s return a giant list of errors that i will attach below | 1 |
47,689 | 13,248,501,668 | IssuesEvent | 2020-08-19 19:05:11 | kenferrara/cbp-theme | https://api.github.com/repos/kenferrara/cbp-theme | opened | CVE-2020-7598 (Medium) detected in minimist-0.0.8.tgz, minimist-1.2.0.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 Libraries - <b>minimist-0.0.8.tgz</b>, <b>minimist-1.2.0.tgz</b></p></summary>
<p>
<details><summary><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: /tmp/ws-scm/cbp-theme/cbp-theme/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/cbp-theme/node_modules/minimist/package.json,/tmp/ws-scm/cbp-theme/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- cpx-1.5.0.tgz (Root Library)
- mkdirp-0.5.1.tgz
- :x: **minimist-0.0.8.tgz** (Vulnerable Library)
</details>
<details><summary><b>minimist-1.2.0.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/cbp-theme/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/cbp-theme/cbp-theme/node_modules/meow/node_modules/minimist/package.json,/tmp/ws-scm/cbp-theme/cbp-theme/node_modules/meow/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- cpx-1.5.0.tgz (Root Library)
- subarg-1.0.0.tgz
- :x: **minimist-1.2.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/kenferrara/cbp-theme/commit/00f1482f5efa0120a277f069fffcee0de8e6adec">00f1482f5efa0120a277f069fffcee0de8e6adec</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>
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>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"0.0.8","isTransitiveDependency":true,"dependencyTree":"cpx:1.5.0;mkdirp:0.5.1;minimist:0.0.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"minimist - 0.2.1,1.2.3"},{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"1.2.0","isTransitiveDependency":true,"dependencyTree":"cpx:1.5.0;subarg:1.0.0;minimist:1.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"minimist - 0.2.1,1.2.3"}],"vulnerabilityIdentifier":"CVE-2020-7598","vulnerabilityDetails":"minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a \"constructor\" or \"__proto__\" payload.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598","cvss3Severity":"medium","cvss3Score":"5.6","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-7598 (Medium) detected in minimist-0.0.8.tgz, minimist-1.2.0.tgz - ## CVE-2020-7598 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>minimist-0.0.8.tgz</b>, <b>minimist-1.2.0.tgz</b></p></summary>
<p>
<details><summary><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: /tmp/ws-scm/cbp-theme/cbp-theme/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/cbp-theme/node_modules/minimist/package.json,/tmp/ws-scm/cbp-theme/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- cpx-1.5.0.tgz (Root Library)
- mkdirp-0.5.1.tgz
- :x: **minimist-0.0.8.tgz** (Vulnerable Library)
</details>
<details><summary><b>minimist-1.2.0.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/cbp-theme/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/cbp-theme/cbp-theme/node_modules/meow/node_modules/minimist/package.json,/tmp/ws-scm/cbp-theme/cbp-theme/node_modules/meow/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- cpx-1.5.0.tgz (Root Library)
- subarg-1.0.0.tgz
- :x: **minimist-1.2.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/kenferrara/cbp-theme/commit/00f1482f5efa0120a277f069fffcee0de8e6adec">00f1482f5efa0120a277f069fffcee0de8e6adec</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>
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>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"0.0.8","isTransitiveDependency":true,"dependencyTree":"cpx:1.5.0;mkdirp:0.5.1;minimist:0.0.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"minimist - 0.2.1,1.2.3"},{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"1.2.0","isTransitiveDependency":true,"dependencyTree":"cpx:1.5.0;subarg:1.0.0;minimist:1.2.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"minimist - 0.2.1,1.2.3"}],"vulnerabilityIdentifier":"CVE-2020-7598","vulnerabilityDetails":"minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a \"constructor\" or \"__proto__\" payload.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598","cvss3Severity":"medium","cvss3Score":"5.6","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | non_infrastructure | cve medium detected in minimist tgz minimist tgz cve medium severity vulnerability vulnerable libraries minimist tgz minimist tgz minimist tgz parse argument options library home page a href path to dependency file tmp ws scm cbp theme cbp theme package json path to vulnerable library tmp ws scm cbp theme node modules minimist package json tmp ws scm cbp theme node modules minimist package json dependency hierarchy cpx tgz root library mkdirp tgz x minimist tgz vulnerable library minimist tgz parse argument options library home page a href path to dependency file tmp ws scm cbp theme package json path to vulnerable library tmp ws scm cbp theme cbp theme node modules meow node modules minimist package json tmp ws scm cbp theme cbp theme node modules meow node modules minimist package json dependency hierarchy cpx tgz root library subarg tgz x minimist tgz vulnerable library found in head commit a href 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 isopenpronvulnerability true ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails minimist before could be tricked into adding or modifying properties of object prototype using a constructor or proto payload vulnerabilityurl | 0 |
545,084 | 15,935,793,728 | IssuesEvent | 2021-04-14 10:17:45 | NodeFactoryIo/ChainGuardian | https://api.github.com/repos/NodeFactoryIo/ChainGuardian | closed | BN docker image version from github | enhancement priority: P1 critical | At the current state, we use the docker image version from env.
We want to change it to pull the image version from this repository to simplify updating versions of images if there are no breaking changes for the chain guardian | 1.0 | BN docker image version from github - At the current state, we use the docker image version from env.
We want to change it to pull the image version from this repository to simplify updating versions of images if there are no breaking changes for the chain guardian | non_infrastructure | bn docker image version from github at the current state we use the docker image version from env we want to change it to pull the image version from this repository to simplify updating versions of images if there are no breaking changes for the chain guardian | 0 |
26,444 | 7,837,965,534 | IssuesEvent | 2018-06-18 08:35:41 | JabRef/jabref | https://api.github.com/repos/JabRef/jabref | closed | Adjust eclipse style to intellij (line wrapping) | build-system | Has intellij one or two default indendation lines? @tobiasdiez
I now changed to align on column
[JabRefModdedStyleSettings.xml.txt](https://github.com/JabRef/jabref/files/1791055/JabRefModdedStyleSettings.xml.txt)
| 1.0 | Adjust eclipse style to intellij (line wrapping) - Has intellij one or two default indendation lines? @tobiasdiez
I now changed to align on column
[JabRefModdedStyleSettings.xml.txt](https://github.com/JabRef/jabref/files/1791055/JabRefModdedStyleSettings.xml.txt)
| non_infrastructure | adjust eclipse style to intellij line wrapping has intellij one or two default indendation lines tobiasdiez i now changed to align on column | 0 |
360,942 | 10,699,371,122 | IssuesEvent | 2019-10-23 20:47:39 | yalla-coop/curenetics | https://api.github.com/repos/yalla-coop/curenetics | closed | Small edits to Add Files page | 1-point priority-5 | - Add padding to the list of files (at the moment it's too tight to the dotted border)
- Make the X slightly bigger | 1.0 | Small edits to Add Files page - - Add padding to the list of files (at the moment it's too tight to the dotted border)
- Make the X slightly bigger | non_infrastructure | small edits to add files page add padding to the list of files at the moment it s too tight to the dotted border make the x slightly bigger | 0 |
61,126 | 14,615,301,420 | IssuesEvent | 2020-12-22 11:18:48 | rsoreq/NodeGoat | https://api.github.com/repos/rsoreq/NodeGoat | opened | CVE-2020-8203 (High) detected in multiple libraries | security vulnerability | ## CVE-2020-8203 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>lodash-4.13.1.tgz</b>, <b>lodash-2.4.2.tgz</b>, <b>lodash-4.17.11.tgz</b></p></summary>
<p>
<details><summary><b>lodash-4.13.1.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.13.1.tgz">https://registry.npmjs.org/lodash/-/lodash-4.13.1.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/nyc/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- grunt-if-0.2.0.tgz (Root Library)
- grunt-contrib-nodeunit-1.0.0.tgz
- nodeunit-0.9.5.tgz
- tap-7.1.2.tgz
- nyc-7.1.0.tgz
- istanbul-lib-instrument-1.1.0-alpha.4.tgz
- babel-generator-6.11.4.tgz
- :x: **lodash-4.13.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-2.4.2.tgz</b></p></summary>
<p>A utility library delivering consistency, customization, performance, & extras.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/zaproxy/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- zaproxy-0.2.0.tgz (Root Library)
- :x: **lodash-2.4.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-4.17.11.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.11.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.11.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- async-2.6.1.tgz (Root Library)
- :x: **lodash-4.17.11.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/rsoreq/NodeGoat/commit/30db8811fba7f9bab1b860cabc70c1795eac29e9">30db8811fba7f9bab1b860cabc70c1795eac29e9</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
<p>Publish Date: 2020-07-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203>CVE-2020-8203</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.4</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: None
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1523">https://www.npmjs.com/advisories/1523</a></p>
<p>Release Date: 2020-07-23</p>
<p>Fix Resolution: lodash - 4.17.19</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"4.13.1","isTransitiveDependency":true,"dependencyTree":"grunt-if:0.2.0;grunt-contrib-nodeunit:1.0.0;nodeunit:0.9.5;tap:7.1.2;nyc:7.1.0;istanbul-lib-instrument:1.1.0-alpha.4;babel-generator:6.11.4;lodash:4.13.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"lodash - 4.17.19"},{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"2.4.2","isTransitiveDependency":true,"dependencyTree":"zaproxy:0.2.0;lodash:2.4.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"lodash - 4.17.19"},{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"4.17.11","isTransitiveDependency":true,"dependencyTree":"async:2.6.1;lodash:4.17.11","isMinimumFixVersionAvailable":true,"minimumFixVersion":"lodash - 4.17.19"}],"vulnerabilityIdentifier":"CVE-2020-8203","vulnerabilityDetails":"Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203","cvss3Severity":"high","cvss3Score":"7.4","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-8203 (High) detected in multiple libraries - ## CVE-2020-8203 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>lodash-4.13.1.tgz</b>, <b>lodash-2.4.2.tgz</b>, <b>lodash-4.17.11.tgz</b></p></summary>
<p>
<details><summary><b>lodash-4.13.1.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.13.1.tgz">https://registry.npmjs.org/lodash/-/lodash-4.13.1.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/nyc/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- grunt-if-0.2.0.tgz (Root Library)
- grunt-contrib-nodeunit-1.0.0.tgz
- nodeunit-0.9.5.tgz
- tap-7.1.2.tgz
- nyc-7.1.0.tgz
- istanbul-lib-instrument-1.1.0-alpha.4.tgz
- babel-generator-6.11.4.tgz
- :x: **lodash-4.13.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-2.4.2.tgz</b></p></summary>
<p>A utility library delivering consistency, customization, performance, & extras.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/zaproxy/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- zaproxy-0.2.0.tgz (Root Library)
- :x: **lodash-2.4.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-4.17.11.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.11.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.11.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- async-2.6.1.tgz (Root Library)
- :x: **lodash-4.17.11.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/rsoreq/NodeGoat/commit/30db8811fba7f9bab1b860cabc70c1795eac29e9">30db8811fba7f9bab1b860cabc70c1795eac29e9</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
<p>Publish Date: 2020-07-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203>CVE-2020-8203</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.4</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: None
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1523">https://www.npmjs.com/advisories/1523</a></p>
<p>Release Date: 2020-07-23</p>
<p>Fix Resolution: lodash - 4.17.19</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"4.13.1","isTransitiveDependency":true,"dependencyTree":"grunt-if:0.2.0;grunt-contrib-nodeunit:1.0.0;nodeunit:0.9.5;tap:7.1.2;nyc:7.1.0;istanbul-lib-instrument:1.1.0-alpha.4;babel-generator:6.11.4;lodash:4.13.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"lodash - 4.17.19"},{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"2.4.2","isTransitiveDependency":true,"dependencyTree":"zaproxy:0.2.0;lodash:2.4.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"lodash - 4.17.19"},{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"4.17.11","isTransitiveDependency":true,"dependencyTree":"async:2.6.1;lodash:4.17.11","isMinimumFixVersionAvailable":true,"minimumFixVersion":"lodash - 4.17.19"}],"vulnerabilityIdentifier":"CVE-2020-8203","vulnerabilityDetails":"Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203","cvss3Severity":"high","cvss3Score":"7.4","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_infrastructure | cve high detected in multiple libraries cve high severity vulnerability vulnerable libraries lodash tgz lodash tgz lodash tgz lodash tgz lodash modular utilities library home page a href path to dependency file nodegoat package json path to vulnerable library nodegoat node modules nyc node modules lodash package json dependency hierarchy grunt if tgz root library grunt contrib nodeunit tgz nodeunit tgz tap tgz nyc tgz istanbul lib instrument alpha tgz babel generator tgz x lodash tgz vulnerable library lodash tgz a utility library delivering consistency customization performance extras library home page a href path to dependency file nodegoat package json path to vulnerable library nodegoat node modules zaproxy node modules lodash package json dependency hierarchy zaproxy tgz root library x lodash tgz vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file nodegoat package json path to vulnerable library nodegoat node modules lodash package json dependency hierarchy async tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details prototype pollution attack when using zipobjectdeep in lodash before 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 none 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 lodash isopenpronvulnerability true ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails prototype pollution attack when using zipobjectdeep in lodash before vulnerabilityurl | 0 |
23,718 | 16,541,700,354 | IssuesEvent | 2021-05-27 17:39:52 | wazuh/wazuh-documentation | https://api.github.com/repos/wazuh/wazuh-documentation | opened | Current Installation guide rework | priority: highest type: feature type: infrastructure type: refactor | Hello team!
The aim of this issue is to improve and reorganize the current installation guide.
We must ease the installation process by reorganizing the different installation and deployment alternatives to follow this menu:
Besides, the content of each section must be adapted to the new structure and simplify the steps where possible.
The sections to simplify are:
- [ ] Installation guide index #3857
- [ ] Quickstart #3858
- [ ] Step-by-step installation #3859
- [ ] Unattended installation #3860
- [ ] Wazuh agent #3861
- [ ] Package list
- [ ] More installation alternatives #3863
This issue is related to #3364 since the unattended scripts improvements must be ready before this issue can be merged.
Regards,
David
| 1.0 | Current Installation guide rework - Hello team!
The aim of this issue is to improve and reorganize the current installation guide.
We must ease the installation process by reorganizing the different installation and deployment alternatives to follow this menu:
Besides, the content of each section must be adapted to the new structure and simplify the steps where possible.
The sections to simplify are:
- [ ] Installation guide index #3857
- [ ] Quickstart #3858
- [ ] Step-by-step installation #3859
- [ ] Unattended installation #3860
- [ ] Wazuh agent #3861
- [ ] Package list
- [ ] More installation alternatives #3863
This issue is related to #3364 since the unattended scripts improvements must be ready before this issue can be merged.
Regards,
David
| infrastructure | current installation guide rework hello team the aim of this issue is to improve and reorganize the current installation guide we must ease the installation process by reorganizing the different installation and deployment alternatives to follow this menu besides the content of each section must be adapted to the new structure and simplify the steps where possible the sections to simplify are installation guide index quickstart step by step installation unattended installation wazuh agent package list more installation alternatives this issue is related to since the unattended scripts improvements must be ready before this issue can be merged regards david | 1 |
158,678 | 6,033,334,956 | IssuesEvent | 2017-06-09 08:00:14 | dotnet/docfx | https://api.github.com/repos/dotnet/docfx | closed | docfx 1.18.3 crashes on Windows 10 with docfx-seed repo | bug priority-0 | I just upgraded to v2.18.3 (chocolatey package) and docfx now crashes when trying to run on the docfx-seed repository. Well, I guess it doesn't technically crash, but the logged error looks like an unhandled exception.
I'm running Windows 10 (creators) with Visual Studio 2017 Preview (15.3 preview 2).
```
[17-06-08 08:48:34.886]Info:Config file docfx.json found, start generating metadata...
[17-06-08 08:48:41.926]Info:Completed executing in 6865.4273 milliseconds.
[17-06-08 08:48:41.926]Error:System.AggregateException: One or more errors occurred. ---> Microsoft.DocAsCode.Exceptions.ExtractMetadataException: Error extracting metadata for {"Items":{"obj/api":["C:/Users/david/Documents/Junk/docfx-seed/src/SampleClass1/SampleClass1.sln"]},"ApiFolderName":"","TocFileName":"toc.yml","IndexFileName":".manifest","PreserveRawInlineComments":false,"ForceRebuild":false,"ShouldSkipMarkup":false,"UseCompatibilityFileName":false,"MSBuildProperties":{"Configuration":"Release"}}: Unable to generate spec reference for !:CounterSampleCalculator ---> Microsoft.DocAsCode.Exceptions.DocfxException: Unable to generate spec reference for !:CounterSampleCalculator ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.DocAsCode.Metadata.ManagedReference.CSharpNameVisitor.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.NameVisitorCreator.GetName(ISymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.CSReferenceItemVisitor.AddLinkItems(INamedTypeSymbol symbol, Boolean withGenericeParameter)
at Microsoft.DocAsCode.Metadata.ManagedReference.ReferenceItemVisitor.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.CompositeYamlModelGenerator.GenerateReferenceInternal(ISymbol symbol, ReferenceItem reference, SymbolVisitorAdapter adapter, Boolean asOverload)
at Microsoft.DocAsCode.Metadata.ManagedReference.YamlModelGenerator.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters, Dictionary`2 references, SymbolVisitorAdapter adapter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters)
--- End of inner exception stack trace ---
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitProperty(IPropertySymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitDescendants[T](IEnumerable`1 children, Func`2 getChildren, Func`2 filter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitNamespace(INamespaceSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitDescendants[T](IEnumerable`1 children, Func`2 getChildren, Func`2 filter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitAssembly(IAssemblySymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.GenerateYamlMetadata(Compilation compilation, IAssemblySymbol assembly, Boolean preserveRawInlineComments, String filterConfigFile, IReadOnlyDictionary`2 extensionMethods)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<GetMetadataFromProjectLevelCacheAsync>d__43`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<SaveAllMembersFromCacheAsync>d__33.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<ExtractMetadataAsync>d__20.MoveNext()
--- End of inner exception stack trace ---
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<ExtractMetadataAsync>d__20.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at Microsoft.DocAsCode.SubCommands.MetadataCommand.Exec(SubCommandRunningContext context)
at Microsoft.DocAsCode.SubCommands.CompositeCommand.Exec(SubCommandRunningContext context)
at Microsoft.DocAsCode.Program.ExecSubCommand(String[] args)
---> (Inner Exception #0) Microsoft.DocAsCode.Exceptions.ExtractMetadataException: Error extracting metadata for {"Items":{"obj/api":["C:/Users/david/Documents/Junk/docfx-seed/src/SampleClass1/SampleClass1.sln"]},"ApiFolderName":"","TocFileName":"toc.yml","IndexFileName":".manifest","PreserveRawInlineComments":false,"ForceRebuild":false,"ShouldSkipMarkup":false,"UseCompatibilityFileName":false,"MSBuildProperties":{"Configuration":"Release"}}: Unable to generate spec reference for !:CounterSampleCalculator ---> Microsoft.DocAsCode.Exceptions.DocfxException: Unable to generate spec reference for !:CounterSampleCalculator ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.DocAsCode.Metadata.ManagedReference.CSharpNameVisitor.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.NameVisitorCreator.GetName(ISymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.CSReferenceItemVisitor.AddLinkItems(INamedTypeSymbol symbol, Boolean withGenericeParameter)
at Microsoft.DocAsCode.Metadata.ManagedReference.ReferenceItemVisitor.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.CompositeYamlModelGenerator.GenerateReferenceInternal(ISymbol symbol, ReferenceItem reference, SymbolVisitorAdapter adapter, Boolean asOverload)
at Microsoft.DocAsCode.Metadata.ManagedReference.YamlModelGenerator.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters, Dictionary`2 references, SymbolVisitorAdapter adapter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters)
--- End of inner exception stack trace ---
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitProperty(IPropertySymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitDescendants[T](IEnumerable`1 children, Func`2 getChildren, Func`2 filter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitNamespace(INamespaceSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitDescendants[T](IEnumerable`1 children, Func`2 getChildren, Func`2 filter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitAssembly(IAssemblySymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.GenerateYamlMetadata(Compilation compilation, IAssemblySymbol assembly, Boolean preserveRawInlineComments, String filterConfigFile, IReadOnlyDictionary`2 extensionMethods)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<GetMetadataFromProjectLevelCacheAsync>d__43`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<SaveAllMembersFromCacheAsync>d__33.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<ExtractMetadataAsync>d__20.MoveNext()
--- End of inner exception stack trace ---
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<ExtractMetadataAsync>d__20.MoveNext()<---
Build failed.
[17-06-08 08:48:41.941]Error:System.AggregateException: One or more errors occurred. ---> Microsoft.DocAsCode.Exceptions.ExtractMetadataException: Error extracting metadata for {"Items":{"obj/api":["C:/Users/david/Documents/Junk/docfx-seed/src/SampleClass1/SampleClass1.sln"]},"ApiFolderName":"","TocFileName":"toc.yml","IndexFileName":".manifest","PreserveRawInlineComments":false,"ForceRebuild":false,"ShouldSkipMarkup":false,"UseCompatibilityFileName":false,"MSBuildProperties":{"Configuration":"Release"}}: Unable to generate spec reference for !:CounterSampleCalculator ---> Microsoft.DocAsCode.Exceptions.DocfxException: Unable to generate spec reference for !:CounterSampleCalculator ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.DocAsCode.Metadata.ManagedReference.CSharpNameVisitor.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.NameVisitorCreator.GetName(ISymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.CSReferenceItemVisitor.AddLinkItems(INamedTypeSymbol symbol, Boolean withGenericeParameter)
at Microsoft.DocAsCode.Metadata.ManagedReference.ReferenceItemVisitor.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.CompositeYamlModelGenerator.GenerateReferenceInternal(ISymbol symbol, ReferenceItem reference, SymbolVisitorAdapter adapter, Boolean asOverload)
at Microsoft.DocAsCode.Metadata.ManagedReference.YamlModelGenerator.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters, Dictionary`2 references, SymbolVisitorAdapter adapter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters)
--- End of inner exception stack trace ---
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitProperty(IPropertySymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitDescendants[T](IEnumerable`1 children, Func`2 getChildren, Func`2 filter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitNamespace(INamespaceSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitDescendants[T](IEnumerable`1 children, Func`2 getChildren, Func`2 filter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitAssembly(IAssemblySymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.GenerateYamlMetadata(Compilation compilation, IAssemblySymbol assembly, Boolean preserveRawInlineComments, String filterConfigFile, IReadOnlyDictionary`2 extensionMethods)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<GetMetadataFromProjectLevelCacheAsync>d__43`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<SaveAllMembersFromCacheAsync>d__33.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<ExtractMetadataAsync>d__20.MoveNext()
--- End of inner exception stack trace ---
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<ExtractMetadataAsync>d__20.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at Microsoft.DocAsCode.SubCommands.MetadataCommand.Exec(SubCommandRunningContext context)
at Microsoft.DocAsCode.SubCommands.CompositeCommand.Exec(SubCommandRunningContext context)
at Microsoft.DocAsCode.Program.ExecSubCommand(String[] args)
---> (Inner Exception #0) Microsoft.DocAsCode.Exceptions.ExtractMetadataException: Error extracting metadata for {"Items":{"obj/api":["C:/Users/david/Documents/Junk/docfx-seed/src/SampleClass1/SampleClass1.sln"]},"ApiFolderName":"","TocFileName":"toc.yml","IndexFileName":".manifest","PreserveRawInlineComments":false,"ForceRebuild":false,"ShouldSkipMarkup":false,"UseCompatibilityFileName":false,"MSBuildProperties":{"Configuration":"Release"}}: Unable to generate spec reference for !:CounterSampleCalculator ---> Microsoft.DocAsCode.Exceptions.DocfxException: Unable to generate spec reference for !:CounterSampleCalculator ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.DocAsCode.Metadata.ManagedReference.CSharpNameVisitor.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.NameVisitorCreator.GetName(ISymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.CSReferenceItemVisitor.AddLinkItems(INamedTypeSymbol symbol, Boolean withGenericeParameter)
at Microsoft.DocAsCode.Metadata.ManagedReference.ReferenceItemVisitor.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.CompositeYamlModelGenerator.GenerateReferenceInternal(ISymbol symbol, ReferenceItem reference, SymbolVisitorAdapter adapter, Boolean asOverload)
at Microsoft.DocAsCode.Metadata.ManagedReference.YamlModelGenerator.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters, Dictionary`2 references, SymbolVisitorAdapter adapter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters)
--- End of inner exception stack trace ---
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitProperty(IPropertySymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitDescendants[T](IEnumerable`1 children, Func`2 getChildren, Func`2 filter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitNamespace(INamespaceSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitDescendants[T](IEnumerable`1 children, Func`2 getChildren, Func`2 filter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitAssembly(IAssemblySymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.GenerateYamlMetadata(Compilation compilation, IAssemblySymbol assembly, Boolean preserveRawInlineComments, String filterConfigFile, IReadOnlyDictionary`2 extensionMethods)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<GetMetadataFromProjectLevelCacheAsync>d__43`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<SaveAllMembersFromCacheAsync>d__33.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<ExtractMetadataAsync>d__20.MoveNext()
--- End of inner exception stack trace ---
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<ExtractMetadataAsync>d__20.MoveNext()<---
0 Warning(s)
1 Error(s)
``` | 1.0 | docfx 1.18.3 crashes on Windows 10 with docfx-seed repo - I just upgraded to v2.18.3 (chocolatey package) and docfx now crashes when trying to run on the docfx-seed repository. Well, I guess it doesn't technically crash, but the logged error looks like an unhandled exception.
I'm running Windows 10 (creators) with Visual Studio 2017 Preview (15.3 preview 2).
```
[17-06-08 08:48:34.886]Info:Config file docfx.json found, start generating metadata...
[17-06-08 08:48:41.926]Info:Completed executing in 6865.4273 milliseconds.
[17-06-08 08:48:41.926]Error:System.AggregateException: One or more errors occurred. ---> Microsoft.DocAsCode.Exceptions.ExtractMetadataException: Error extracting metadata for {"Items":{"obj/api":["C:/Users/david/Documents/Junk/docfx-seed/src/SampleClass1/SampleClass1.sln"]},"ApiFolderName":"","TocFileName":"toc.yml","IndexFileName":".manifest","PreserveRawInlineComments":false,"ForceRebuild":false,"ShouldSkipMarkup":false,"UseCompatibilityFileName":false,"MSBuildProperties":{"Configuration":"Release"}}: Unable to generate spec reference for !:CounterSampleCalculator ---> Microsoft.DocAsCode.Exceptions.DocfxException: Unable to generate spec reference for !:CounterSampleCalculator ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.DocAsCode.Metadata.ManagedReference.CSharpNameVisitor.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.NameVisitorCreator.GetName(ISymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.CSReferenceItemVisitor.AddLinkItems(INamedTypeSymbol symbol, Boolean withGenericeParameter)
at Microsoft.DocAsCode.Metadata.ManagedReference.ReferenceItemVisitor.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.CompositeYamlModelGenerator.GenerateReferenceInternal(ISymbol symbol, ReferenceItem reference, SymbolVisitorAdapter adapter, Boolean asOverload)
at Microsoft.DocAsCode.Metadata.ManagedReference.YamlModelGenerator.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters, Dictionary`2 references, SymbolVisitorAdapter adapter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters)
--- End of inner exception stack trace ---
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitProperty(IPropertySymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitDescendants[T](IEnumerable`1 children, Func`2 getChildren, Func`2 filter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitNamespace(INamespaceSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitDescendants[T](IEnumerable`1 children, Func`2 getChildren, Func`2 filter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitAssembly(IAssemblySymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.GenerateYamlMetadata(Compilation compilation, IAssemblySymbol assembly, Boolean preserveRawInlineComments, String filterConfigFile, IReadOnlyDictionary`2 extensionMethods)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<GetMetadataFromProjectLevelCacheAsync>d__43`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<SaveAllMembersFromCacheAsync>d__33.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<ExtractMetadataAsync>d__20.MoveNext()
--- End of inner exception stack trace ---
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<ExtractMetadataAsync>d__20.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at Microsoft.DocAsCode.SubCommands.MetadataCommand.Exec(SubCommandRunningContext context)
at Microsoft.DocAsCode.SubCommands.CompositeCommand.Exec(SubCommandRunningContext context)
at Microsoft.DocAsCode.Program.ExecSubCommand(String[] args)
---> (Inner Exception #0) Microsoft.DocAsCode.Exceptions.ExtractMetadataException: Error extracting metadata for {"Items":{"obj/api":["C:/Users/david/Documents/Junk/docfx-seed/src/SampleClass1/SampleClass1.sln"]},"ApiFolderName":"","TocFileName":"toc.yml","IndexFileName":".manifest","PreserveRawInlineComments":false,"ForceRebuild":false,"ShouldSkipMarkup":false,"UseCompatibilityFileName":false,"MSBuildProperties":{"Configuration":"Release"}}: Unable to generate spec reference for !:CounterSampleCalculator ---> Microsoft.DocAsCode.Exceptions.DocfxException: Unable to generate spec reference for !:CounterSampleCalculator ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.DocAsCode.Metadata.ManagedReference.CSharpNameVisitor.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.NameVisitorCreator.GetName(ISymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.CSReferenceItemVisitor.AddLinkItems(INamedTypeSymbol symbol, Boolean withGenericeParameter)
at Microsoft.DocAsCode.Metadata.ManagedReference.ReferenceItemVisitor.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.CompositeYamlModelGenerator.GenerateReferenceInternal(ISymbol symbol, ReferenceItem reference, SymbolVisitorAdapter adapter, Boolean asOverload)
at Microsoft.DocAsCode.Metadata.ManagedReference.YamlModelGenerator.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters, Dictionary`2 references, SymbolVisitorAdapter adapter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters)
--- End of inner exception stack trace ---
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitProperty(IPropertySymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitDescendants[T](IEnumerable`1 children, Func`2 getChildren, Func`2 filter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitNamespace(INamespaceSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitDescendants[T](IEnumerable`1 children, Func`2 getChildren, Func`2 filter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitAssembly(IAssemblySymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.GenerateYamlMetadata(Compilation compilation, IAssemblySymbol assembly, Boolean preserveRawInlineComments, String filterConfigFile, IReadOnlyDictionary`2 extensionMethods)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<GetMetadataFromProjectLevelCacheAsync>d__43`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<SaveAllMembersFromCacheAsync>d__33.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<ExtractMetadataAsync>d__20.MoveNext()
--- End of inner exception stack trace ---
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<ExtractMetadataAsync>d__20.MoveNext()<---
Build failed.
[17-06-08 08:48:41.941]Error:System.AggregateException: One or more errors occurred. ---> Microsoft.DocAsCode.Exceptions.ExtractMetadataException: Error extracting metadata for {"Items":{"obj/api":["C:/Users/david/Documents/Junk/docfx-seed/src/SampleClass1/SampleClass1.sln"]},"ApiFolderName":"","TocFileName":"toc.yml","IndexFileName":".manifest","PreserveRawInlineComments":false,"ForceRebuild":false,"ShouldSkipMarkup":false,"UseCompatibilityFileName":false,"MSBuildProperties":{"Configuration":"Release"}}: Unable to generate spec reference for !:CounterSampleCalculator ---> Microsoft.DocAsCode.Exceptions.DocfxException: Unable to generate spec reference for !:CounterSampleCalculator ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.DocAsCode.Metadata.ManagedReference.CSharpNameVisitor.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.NameVisitorCreator.GetName(ISymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.CSReferenceItemVisitor.AddLinkItems(INamedTypeSymbol symbol, Boolean withGenericeParameter)
at Microsoft.DocAsCode.Metadata.ManagedReference.ReferenceItemVisitor.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.CompositeYamlModelGenerator.GenerateReferenceInternal(ISymbol symbol, ReferenceItem reference, SymbolVisitorAdapter adapter, Boolean asOverload)
at Microsoft.DocAsCode.Metadata.ManagedReference.YamlModelGenerator.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters, Dictionary`2 references, SymbolVisitorAdapter adapter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters)
--- End of inner exception stack trace ---
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitProperty(IPropertySymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitDescendants[T](IEnumerable`1 children, Func`2 getChildren, Func`2 filter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitNamespace(INamespaceSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitDescendants[T](IEnumerable`1 children, Func`2 getChildren, Func`2 filter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitAssembly(IAssemblySymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.GenerateYamlMetadata(Compilation compilation, IAssemblySymbol assembly, Boolean preserveRawInlineComments, String filterConfigFile, IReadOnlyDictionary`2 extensionMethods)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<GetMetadataFromProjectLevelCacheAsync>d__43`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<SaveAllMembersFromCacheAsync>d__33.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<ExtractMetadataAsync>d__20.MoveNext()
--- End of inner exception stack trace ---
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<ExtractMetadataAsync>d__20.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at Microsoft.DocAsCode.SubCommands.MetadataCommand.Exec(SubCommandRunningContext context)
at Microsoft.DocAsCode.SubCommands.CompositeCommand.Exec(SubCommandRunningContext context)
at Microsoft.DocAsCode.Program.ExecSubCommand(String[] args)
---> (Inner Exception #0) Microsoft.DocAsCode.Exceptions.ExtractMetadataException: Error extracting metadata for {"Items":{"obj/api":["C:/Users/david/Documents/Junk/docfx-seed/src/SampleClass1/SampleClass1.sln"]},"ApiFolderName":"","TocFileName":"toc.yml","IndexFileName":".manifest","PreserveRawInlineComments":false,"ForceRebuild":false,"ShouldSkipMarkup":false,"UseCompatibilityFileName":false,"MSBuildProperties":{"Configuration":"Release"}}: Unable to generate spec reference for !:CounterSampleCalculator ---> Microsoft.DocAsCode.Exceptions.DocfxException: Unable to generate spec reference for !:CounterSampleCalculator ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.DocAsCode.Metadata.ManagedReference.CSharpNameVisitor.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.NameVisitorCreator.GetName(ISymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.CSReferenceItemVisitor.AddLinkItems(INamedTypeSymbol symbol, Boolean withGenericeParameter)
at Microsoft.DocAsCode.Metadata.ManagedReference.ReferenceItemVisitor.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.CompositeYamlModelGenerator.GenerateReferenceInternal(ISymbol symbol, ReferenceItem reference, SymbolVisitorAdapter adapter, Boolean asOverload)
at Microsoft.DocAsCode.Metadata.ManagedReference.YamlModelGenerator.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters, Dictionary`2 references, SymbolVisitorAdapter adapter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters)
--- End of inner exception stack trace ---
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.AddSpecReference(ISymbol symbol, IReadOnlyList`1 typeGenericParameters, IReadOnlyList`1 methodGenericParameters)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitProperty(IPropertySymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitNamedType(INamedTypeSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitDescendants[T](IEnumerable`1 children, Func`2 getChildren, Func`2 filter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitNamespace(INamespaceSymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitDescendants[T](IEnumerable`1 children, Func`2 getChildren, Func`2 filter)
at Microsoft.DocAsCode.Metadata.ManagedReference.SymbolVisitorAdapter.VisitAssembly(IAssemblySymbol symbol)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.GenerateYamlMetadata(Compilation compilation, IAssemblySymbol assembly, Boolean preserveRawInlineComments, String filterConfigFile, IReadOnlyDictionary`2 extensionMethods)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<GetMetadataFromProjectLevelCacheAsync>d__43`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<SaveAllMembersFromCacheAsync>d__33.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<ExtractMetadataAsync>d__20.MoveNext()
--- End of inner exception stack trace ---
at Microsoft.DocAsCode.Metadata.ManagedReference.ExtractMetadataWorker.<ExtractMetadataAsync>d__20.MoveNext()<---
0 Warning(s)
1 Error(s)
``` | non_infrastructure | docfx crashes on windows with docfx seed repo i just upgraded to chocolatey package and docfx now crashes when trying to run on the docfx seed repository well i guess it doesn t technically crash but the logged error looks like an unhandled exception i m running windows creators with visual studio preview preview info config file docfx json found start generating metadata info completed executing in milliseconds error system aggregateexception one or more errors occurred microsoft docascode exceptions extractmetadataexception error extracting metadata for items obj api apifoldername tocfilename toc yml indexfilename manifest preserverawinlinecomments false forcerebuild false shouldskipmarkup false usecompatibilityfilename false msbuildproperties configuration release unable to generate spec reference for countersamplecalculator microsoft docascode exceptions docfxexception unable to generate spec reference for countersamplecalculator system nullreferenceexception object reference not set to an instance of an object at microsoft docascode metadata managedreference csharpnamevisitor visitnamedtype inamedtypesymbol symbol at microsoft docascode metadata managedreference namevisitorcreator getname isymbol symbol at microsoft docascode metadata managedreference csreferenceitemvisitor addlinkitems inamedtypesymbol symbol boolean withgenericeparameter at microsoft docascode metadata managedreference referenceitemvisitor visitnamedtype inamedtypesymbol symbol at microsoft docascode metadata managedreference compositeyamlmodelgenerator generatereferenceinternal isymbol symbol referenceitem reference symbolvisitoradapter adapter boolean asoverload at microsoft docascode metadata managedreference yamlmodelgenerator addspecreference isymbol symbol ireadonlylist typegenericparameters ireadonlylist methodgenericparameters dictionary references symbolvisitoradapter adapter at microsoft docascode metadata managedreference symbolvisitoradapter addspecreference isymbol symbol ireadonlylist typegenericparameters ireadonlylist methodgenericparameters end of inner exception stack trace at microsoft docascode metadata managedreference symbolvisitoradapter addspecreference isymbol symbol ireadonlylist typegenericparameters ireadonlylist methodgenericparameters at microsoft docascode metadata managedreference symbolvisitoradapter visitproperty ipropertysymbol symbol at microsoft docascode metadata managedreference symbolvisitoradapter visitnamedtype inamedtypesymbol symbol at microsoft docascode metadata managedreference symbolvisitoradapter visitdescendants ienumerable children func getchildren func filter at microsoft docascode metadata managedreference symbolvisitoradapter visitnamespace inamespacesymbol symbol at microsoft docascode metadata managedreference symbolvisitoradapter visitdescendants ienumerable children func getchildren func filter at microsoft docascode metadata managedreference symbolvisitoradapter visitassembly iassemblysymbol symbol at microsoft docascode metadata managedreference extractmetadataworker generateyamlmetadata compilation compilation iassemblysymbol assembly boolean preserverawinlinecomments string filterconfigfile ireadonlydictionary extensionmethods at microsoft docascode metadata managedreference extractmetadataworker d movenext end of stack trace from previous location where exception was thrown at system runtime exceptionservices exceptiondispatchinfo throw at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at microsoft docascode metadata managedreference extractmetadataworker d movenext end of stack trace from previous location where exception was thrown at system runtime exceptionservices exceptiondispatchinfo throw at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at microsoft docascode metadata managedreference extractmetadataworker d movenext end of inner exception stack trace at microsoft docascode metadata managedreference extractmetadataworker d movenext end of inner exception stack trace at system threading tasks task throwifexceptional boolean includetaskcanceledexceptions at system threading tasks task wait millisecondstimeout cancellationtoken cancellationtoken at microsoft docascode subcommands metadatacommand exec subcommandrunningcontext context at microsoft docascode subcommands compositecommand exec subcommandrunningcontext context at microsoft docascode program execsubcommand string args inner exception microsoft docascode exceptions extractmetadataexception error extracting metadata for items obj api apifoldername tocfilename toc yml indexfilename manifest preserverawinlinecomments false forcerebuild false shouldskipmarkup false usecompatibilityfilename false msbuildproperties configuration release unable to generate spec reference for countersamplecalculator microsoft docascode exceptions docfxexception unable to generate spec reference for countersamplecalculator system nullreferenceexception object reference not set to an instance of an object at microsoft docascode metadata managedreference csharpnamevisitor visitnamedtype inamedtypesymbol symbol at microsoft docascode metadata managedreference namevisitorcreator getname isymbol symbol at microsoft docascode metadata managedreference csreferenceitemvisitor addlinkitems inamedtypesymbol symbol boolean withgenericeparameter at microsoft docascode metadata managedreference referenceitemvisitor visitnamedtype inamedtypesymbol symbol at microsoft docascode metadata managedreference compositeyamlmodelgenerator generatereferenceinternal isymbol symbol referenceitem reference symbolvisitoradapter adapter boolean asoverload at microsoft docascode metadata managedreference yamlmodelgenerator addspecreference isymbol symbol ireadonlylist typegenericparameters ireadonlylist methodgenericparameters dictionary references symbolvisitoradapter adapter at microsoft docascode metadata managedreference symbolvisitoradapter addspecreference isymbol symbol ireadonlylist typegenericparameters ireadonlylist methodgenericparameters end of inner exception stack trace at microsoft docascode metadata managedreference symbolvisitoradapter addspecreference isymbol symbol ireadonlylist typegenericparameters ireadonlylist methodgenericparameters at microsoft docascode metadata managedreference symbolvisitoradapter visitproperty ipropertysymbol symbol at microsoft docascode metadata managedreference symbolvisitoradapter visitnamedtype inamedtypesymbol symbol at microsoft docascode metadata managedreference symbolvisitoradapter visitdescendants ienumerable children func getchildren func filter at microsoft docascode metadata managedreference symbolvisitoradapter visitnamespace inamespacesymbol symbol at microsoft docascode metadata managedreference symbolvisitoradapter visitdescendants ienumerable children func getchildren func filter at microsoft docascode metadata managedreference symbolvisitoradapter visitassembly iassemblysymbol symbol at microsoft docascode metadata managedreference extractmetadataworker generateyamlmetadata compilation compilation iassemblysymbol assembly boolean preserverawinlinecomments string filterconfigfile ireadonlydictionary extensionmethods at microsoft docascode metadata managedreference extractmetadataworker d movenext end of stack trace from previous location where exception was thrown at system runtime exceptionservices exceptiondispatchinfo throw at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at microsoft docascode metadata managedreference extractmetadataworker d movenext end of stack trace from previous location where exception was thrown at system runtime exceptionservices exceptiondispatchinfo throw at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at microsoft docascode metadata managedreference extractmetadataworker d movenext end of inner exception stack trace at microsoft docascode metadata managedreference extractmetadataworker d movenext build failed error system aggregateexception one or more errors occurred microsoft docascode exceptions extractmetadataexception error extracting metadata for items obj api apifoldername tocfilename toc yml indexfilename manifest preserverawinlinecomments false forcerebuild false shouldskipmarkup false usecompatibilityfilename false msbuildproperties configuration release unable to generate spec reference for countersamplecalculator microsoft docascode exceptions docfxexception unable to generate spec reference for countersamplecalculator system nullreferenceexception object reference not set to an instance of an object at microsoft docascode metadata managedreference csharpnamevisitor visitnamedtype inamedtypesymbol symbol at microsoft docascode metadata managedreference namevisitorcreator getname isymbol symbol at microsoft docascode metadata managedreference csreferenceitemvisitor addlinkitems inamedtypesymbol symbol boolean withgenericeparameter at microsoft docascode metadata managedreference referenceitemvisitor visitnamedtype inamedtypesymbol symbol at microsoft docascode metadata managedreference compositeyamlmodelgenerator generatereferenceinternal isymbol symbol referenceitem reference symbolvisitoradapter adapter boolean asoverload at microsoft docascode metadata managedreference yamlmodelgenerator addspecreference isymbol symbol ireadonlylist typegenericparameters ireadonlylist methodgenericparameters dictionary references symbolvisitoradapter adapter at microsoft docascode metadata managedreference symbolvisitoradapter addspecreference isymbol symbol ireadonlylist typegenericparameters ireadonlylist methodgenericparameters end of inner exception stack trace at microsoft docascode metadata managedreference symbolvisitoradapter addspecreference isymbol symbol ireadonlylist typegenericparameters ireadonlylist methodgenericparameters at microsoft docascode metadata managedreference symbolvisitoradapter visitproperty ipropertysymbol symbol at microsoft docascode metadata managedreference symbolvisitoradapter visitnamedtype inamedtypesymbol symbol at microsoft docascode metadata managedreference symbolvisitoradapter visitdescendants ienumerable children func getchildren func filter at microsoft docascode metadata managedreference symbolvisitoradapter visitnamespace inamespacesymbol symbol at microsoft docascode metadata managedreference symbolvisitoradapter visitdescendants ienumerable children func getchildren func filter at microsoft docascode metadata managedreference symbolvisitoradapter visitassembly iassemblysymbol symbol at microsoft docascode metadata managedreference extractmetadataworker generateyamlmetadata compilation compilation iassemblysymbol assembly boolean preserverawinlinecomments string filterconfigfile ireadonlydictionary extensionmethods at microsoft docascode metadata managedreference extractmetadataworker d movenext end of stack trace from previous location where exception was thrown at system runtime exceptionservices exceptiondispatchinfo throw at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at microsoft docascode metadata managedreference extractmetadataworker d movenext end of stack trace from previous location where exception was thrown at system runtime exceptionservices exceptiondispatchinfo throw at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at microsoft docascode metadata managedreference extractmetadataworker d movenext end of inner exception stack trace at microsoft docascode metadata managedreference extractmetadataworker d movenext end of inner exception stack trace at system threading tasks task throwifexceptional boolean includetaskcanceledexceptions at system threading tasks task wait millisecondstimeout cancellationtoken cancellationtoken at microsoft docascode subcommands metadatacommand exec subcommandrunningcontext context at microsoft docascode subcommands compositecommand exec subcommandrunningcontext context at microsoft docascode program execsubcommand string args inner exception microsoft docascode exceptions extractmetadataexception error extracting metadata for items obj api apifoldername tocfilename toc yml indexfilename manifest preserverawinlinecomments false forcerebuild false shouldskipmarkup false usecompatibilityfilename false msbuildproperties configuration release unable to generate spec reference for countersamplecalculator microsoft docascode exceptions docfxexception unable to generate spec reference for countersamplecalculator system nullreferenceexception object reference not set to an instance of an object at microsoft docascode metadata managedreference csharpnamevisitor visitnamedtype inamedtypesymbol symbol at microsoft docascode metadata managedreference namevisitorcreator getname isymbol symbol at microsoft docascode metadata managedreference csreferenceitemvisitor addlinkitems inamedtypesymbol symbol boolean withgenericeparameter at microsoft docascode metadata managedreference referenceitemvisitor visitnamedtype inamedtypesymbol symbol at microsoft docascode metadata managedreference compositeyamlmodelgenerator generatereferenceinternal isymbol symbol referenceitem reference symbolvisitoradapter adapter boolean asoverload at microsoft docascode metadata managedreference yamlmodelgenerator addspecreference isymbol symbol ireadonlylist typegenericparameters ireadonlylist methodgenericparameters dictionary references symbolvisitoradapter adapter at microsoft docascode metadata managedreference symbolvisitoradapter addspecreference isymbol symbol ireadonlylist typegenericparameters ireadonlylist methodgenericparameters end of inner exception stack trace at microsoft docascode metadata managedreference symbolvisitoradapter addspecreference isymbol symbol ireadonlylist typegenericparameters ireadonlylist methodgenericparameters at microsoft docascode metadata managedreference symbolvisitoradapter visitproperty ipropertysymbol symbol at microsoft docascode metadata managedreference symbolvisitoradapter visitnamedtype inamedtypesymbol symbol at microsoft docascode metadata managedreference symbolvisitoradapter visitdescendants ienumerable children func getchildren func filter at microsoft docascode metadata managedreference symbolvisitoradapter visitnamespace inamespacesymbol symbol at microsoft docascode metadata managedreference symbolvisitoradapter visitdescendants ienumerable children func getchildren func filter at microsoft docascode metadata managedreference symbolvisitoradapter visitassembly iassemblysymbol symbol at microsoft docascode metadata managedreference extractmetadataworker generateyamlmetadata compilation compilation iassemblysymbol assembly boolean preserverawinlinecomments string filterconfigfile ireadonlydictionary extensionmethods at microsoft docascode metadata managedreference extractmetadataworker d movenext end of stack trace from previous location where exception was thrown at system runtime exceptionservices exceptiondispatchinfo throw at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at microsoft docascode metadata managedreference extractmetadataworker d movenext end of stack trace from previous location where exception was thrown at system runtime exceptionservices exceptiondispatchinfo throw at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at microsoft docascode metadata managedreference extractmetadataworker d movenext end of inner exception stack trace at microsoft docascode metadata managedreference extractmetadataworker d movenext warning s error s | 0 |
162,610 | 25,566,057,710 | IssuesEvent | 2022-11-30 14:23:06 | department-of-veterans-affairs/va.gov-team | https://api.github.com/repos/department-of-veterans-affairs/va.gov-team | closed | Update Customer Insights guidance page | service-design | ## Issue Description
Due to the dissolution of the Fixed Tech teams, the [page](https://vfs.atlassian.net/wiki/spaces/PMCP/pages/2001698924/Customer+Insights+for+Quarterly+Planning) that advises on how teams should use the Customer Insights data needs to be updated.
---
## Tasks
- [x] Update info to reflect current processes
## Acceptance Criteria
- [x] Updated page is published | 1.0 | Update Customer Insights guidance page - ## Issue Description
Due to the dissolution of the Fixed Tech teams, the [page](https://vfs.atlassian.net/wiki/spaces/PMCP/pages/2001698924/Customer+Insights+for+Quarterly+Planning) that advises on how teams should use the Customer Insights data needs to be updated.
---
## Tasks
- [x] Update info to reflect current processes
## Acceptance Criteria
- [x] Updated page is published | non_infrastructure | update customer insights guidance page issue description due to the dissolution of the fixed tech teams the that advises on how teams should use the customer insights data needs to be updated tasks update info to reflect current processes acceptance criteria updated page is published | 0 |
104,280 | 16,613,577,408 | IssuesEvent | 2021-06-02 14:16:13 | Thanraj/linux-4.1.15 | https://api.github.com/repos/Thanraj/linux-4.1.15 | opened | CVE-2021-0447 (Medium) detected in linux-stable-rtv4.1.33 | security vulnerability | ## CVE-2021-0447 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://api.github.com/repos/Thanraj/linux-4.1.15/commits/5e3fb3e332499e1ad10a0969e55582af1027b085">5e3fb3e332499e1ad10a0969e55582af1027b085</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>linux-4.1.15/net/l2tp/l2tp_ppp.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>linux-4.1.15/net/l2tp/l2tp_ppp.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A security vulnerability was found in Linux Kernel before 3.2.99, 3.16.54, 4.4.225, 4.9.225 and 4.14.182. Pppol2tp_session_create() registers sessions that can't have their
corresponding socket initialised.
<p>Publish Date: 2020-11-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-0447>CVE-2021-0447</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>4.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- 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://www.linuxkernelcves.com/cves/CVE-2021-0447">https://www.linuxkernelcves.com/cves/CVE-2021-0447</a></p>
<p>Release Date: 2020-11-07</p>
<p>Fix Resolution: 3.2.99,v3.16.54,v4.4.225,v4.9.225,v4.14.182</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-0447 (Medium) detected in linux-stable-rtv4.1.33 - ## CVE-2021-0447 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://api.github.com/repos/Thanraj/linux-4.1.15/commits/5e3fb3e332499e1ad10a0969e55582af1027b085">5e3fb3e332499e1ad10a0969e55582af1027b085</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>linux-4.1.15/net/l2tp/l2tp_ppp.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>linux-4.1.15/net/l2tp/l2tp_ppp.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A security vulnerability was found in Linux Kernel before 3.2.99, 3.16.54, 4.4.225, 4.9.225 and 4.14.182. Pppol2tp_session_create() registers sessions that can't have their
corresponding socket initialised.
<p>Publish Date: 2020-11-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-0447>CVE-2021-0447</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>4.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- 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://www.linuxkernelcves.com/cves/CVE-2021-0447">https://www.linuxkernelcves.com/cves/CVE-2021-0447</a></p>
<p>Release Date: 2020-11-07</p>
<p>Fix Resolution: 3.2.99,v3.16.54,v4.4.225,v4.9.225,v4.14.182</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_infrastructure | cve medium detected in linux stable cve medium severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href found in base branch master vulnerable source files linux net ppp c linux net ppp c vulnerability details a security vulnerability was found in linux kernel before and session create registers sessions that can t have their corresponding socket initialised publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction required scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
1,738 | 3,356,285,013 | IssuesEvent | 2015-11-18 19:51:17 | rust-lang/rust | https://api.github.com/repos/rust-lang/rust | closed | Add beta/stable integration testing | A-infrastructure P-high T-tools | Right now our beta and stable branches have no automatic integration testing set up for them. Requires changes to homu and rust-buildbot, as well as decisions about what the workflow is.
Originally part of #16677. Won't be finished for 1.0 beta. | 1.0 | Add beta/stable integration testing - Right now our beta and stable branches have no automatic integration testing set up for them. Requires changes to homu and rust-buildbot, as well as decisions about what the workflow is.
Originally part of #16677. Won't be finished for 1.0 beta. | infrastructure | add beta stable integration testing right now our beta and stable branches have no automatic integration testing set up for them requires changes to homu and rust buildbot as well as decisions about what the workflow is originally part of won t be finished for beta | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.