Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3 values | title stringlengths 1 844 | labels stringlengths 4 721 | body stringlengths 1 261k | index stringclasses 12 values | text_combine stringlengths 96 261k | label stringclasses 2 values | text stringlengths 96 248k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
107,924 | 23,505,140,271 | IssuesEvent | 2022-08-18 11:59:11 | HMIS/LSASampleCode | https://api.github.com/repos/HMIS/LSASampleCode | closed | Section 11.7: [DisablingCond] discrepancy between Sample Code and Spec | Sample code | Hi @MollyMcEvilley ,
1. could you please remove distinct to not make sql server work on unnecessary calculations?
2. Spec requires using [DisabilityStat] value, but sample code uses [hn.DisablingCondition]. Could you please update so both Sample Code and Spec use the same conditions?
Thank you!
Natalie | 1.0 | Section 11.7: [DisablingCond] discrepancy between Sample Code and Spec - Hi @MollyMcEvilley ,
1. could you please remove distinct to not make sql server work on unnecessary calculations?
2. Spec requires using [DisabilityStat] value, but sample code uses [hn.DisablingCondition]. Could you please update so both Sample Code and Spec use the same conditions?
Thank you!
Natalie | non_priority | section discrepancy between sample code and spec hi mollymcevilley could you please remove distinct to not make sql server work on unnecessary calculations spec requires using value but sample code uses could you please update so both sample code and spec use the same conditions thank you natalie | 0 |
199,292 | 15,761,696,774 | IssuesEvent | 2021-03-31 10:15:30 | OpenNebula/one | https://api.github.com/repos/OpenNebula/one | closed | Add references to (both) MySQL/MariaDB across documentation | Category: Documentation | **Description**
Make sure that documentation displays, when appropriate, a parity of references to both MySQL and MariaDB ("MySQL/MariaDB") as supported DB solutions for OpenNebula.
**Use case**
This is part of an internal process to improve OpenNebula's documentation.
**Interface Changes**
Aiming at OpenNebula 6.0
**Additional Context**
N/A
<!--////////////////////////////////////////////-->
<!-- THIS SECTION IS FOR THE DEVELOPMENT TEAM -->
<!-- BOTH FOR BUGS AND ENHANCEMENT REQUESTS -->
<!-- PROGRESS WILL BE REFLECTED HERE -->
<!--////////////////////////////////////////////-->
## Progress Status
- [ ] Branch created
- [ ] Code committed to development branch
- [ ] Testing - QA
- [ ] Documentation
- [ ] Release notes - resolved issues, compatibility, known issues
- [ ] Code committed to upstream release/hotfix branches
- [ ] Documentation committed to upstream release/hotfix branches
| 1.0 | Add references to (both) MySQL/MariaDB across documentation - **Description**
Make sure that documentation displays, when appropriate, a parity of references to both MySQL and MariaDB ("MySQL/MariaDB") as supported DB solutions for OpenNebula.
**Use case**
This is part of an internal process to improve OpenNebula's documentation.
**Interface Changes**
Aiming at OpenNebula 6.0
**Additional Context**
N/A
<!--////////////////////////////////////////////-->
<!-- THIS SECTION IS FOR THE DEVELOPMENT TEAM -->
<!-- BOTH FOR BUGS AND ENHANCEMENT REQUESTS -->
<!-- PROGRESS WILL BE REFLECTED HERE -->
<!--////////////////////////////////////////////-->
## Progress Status
- [ ] Branch created
- [ ] Code committed to development branch
- [ ] Testing - QA
- [ ] Documentation
- [ ] Release notes - resolved issues, compatibility, known issues
- [ ] Code committed to upstream release/hotfix branches
- [ ] Documentation committed to upstream release/hotfix branches
| non_priority | add references to both mysql mariadb across documentation description make sure that documentation displays when appropriate a parity of references to both mysql and mariadb mysql mariadb as supported db solutions for opennebula use case this is part of an internal process to improve opennebula s documentation interface changes aiming at opennebula additional context n a progress status branch created code committed to development branch testing qa documentation release notes resolved issues compatibility known issues code committed to upstream release hotfix branches documentation committed to upstream release hotfix branches | 0 |
247,261 | 26,688,945,818 | IssuesEvent | 2023-01-27 01:37:49 | Satheesh575555/linux-4.1.15 | https://api.github.com/repos/Satheesh575555/linux-4.1.15 | reopened | CVE-2022-3621 (High) detected in linuxlinux-4.6 | security vulnerability | ## CVE-2022-3621 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.6</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A vulnerability was found in Linux Kernel. It has been classified as problematic. Affected is the function nilfs_bmap_lookup_at_level of the file fs/nilfs2/inode.c of the component nilfs2. The manipulation leads to null pointer dereference. It is possible to launch the attack remotely. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-211920.
<p>Publish Date: 2022-10-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3621>CVE-2022-3621</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2022-3621">https://www.linuxkernelcves.com/cves/CVE-2022-3621</a></p>
<p>Release Date: 2022-10-20</p>
<p>Fix Resolution: v5.4.218,v5.10.148,v5.15.74,v6.0.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-3621 (High) detected in linuxlinux-4.6 - ## CVE-2022-3621 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.6</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A vulnerability was found in Linux Kernel. It has been classified as problematic. Affected is the function nilfs_bmap_lookup_at_level of the file fs/nilfs2/inode.c of the component nilfs2. The manipulation leads to null pointer dereference. It is possible to launch the attack remotely. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-211920.
<p>Publish Date: 2022-10-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3621>CVE-2022-3621</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2022-3621">https://www.linuxkernelcves.com/cves/CVE-2022-3621</a></p>
<p>Release Date: 2022-10-20</p>
<p>Fix Resolution: v5.4.218,v5.10.148,v5.15.74,v6.0.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in linuxlinux cve high severity vulnerability vulnerable library linuxlinux the linux kernel library home page a href found in base branch master vulnerable source files vulnerability details a vulnerability was found in linux kernel it has been classified as problematic affected is the function nilfs bmap lookup at level of the file fs inode c of the component the manipulation leads to null pointer dereference it is possible to launch the attack remotely it is recommended to apply a patch to fix this issue the identifier of this vulnerability is vdb publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
289,120 | 21,769,505,531 | IssuesEvent | 2022-05-13 07:37:56 | casper-network/docs | https://api.github.com/repos/casper-network/docs | opened | Update the serialization standard to include `UnbondingPurse` and `WithdrawPurse` | documentation L2 | Update the serialization standard to include `UnbondingPurse` and `WithdrawPurse` .
- Release 1.5.0 will introduce the Redelegate feature which introduces the `UnbondingPurse` and renders the historical data represented as `WithdrawPurse` as defunct
- Please note that the **SDK** and **serialization standards** both need to be updated in accordance with these changes
Target Release - v1.5.0 | 1.0 | Update the serialization standard to include `UnbondingPurse` and `WithdrawPurse` - Update the serialization standard to include `UnbondingPurse` and `WithdrawPurse` .
- Release 1.5.0 will introduce the Redelegate feature which introduces the `UnbondingPurse` and renders the historical data represented as `WithdrawPurse` as defunct
- Please note that the **SDK** and **serialization standards** both need to be updated in accordance with these changes
Target Release - v1.5.0 | non_priority | update the serialization standard to include unbondingpurse and withdrawpurse update the serialization standard to include unbondingpurse and withdrawpurse release will introduce the redelegate feature which introduces the unbondingpurse and renders the historical data represented as withdrawpurse as defunct please note that the sdk and serialization standards both need to be updated in accordance with these changes target release | 0 |
39,270 | 6,733,295,857 | IssuesEvent | 2017-10-18 14:26:08 | gem/oq-engine | https://api.github.com/repos/gem/oq-engine | closed | Updates required for the user manual for v2.7 | documentation | ### Hazard
- [x] There is a reference to `oq export hcurves/all` which now is spelled `oq extract hazard/all`
- [x] **§2**: Update the link to hazardlib
- [x] Add an example realizations output file
- [x] Update the gmfs xml output file
### Risk
- [x] **§9.5.1**: Replace the benefit-cost ratio map xml example with csv
- [x] Describe the parameter `time_event` for scenarios
- [x] Change the event loss table example adding the column rlzi
- [x] Document asset tags in the exposure model | 1.0 | Updates required for the user manual for v2.7 - ### Hazard
- [x] There is a reference to `oq export hcurves/all` which now is spelled `oq extract hazard/all`
- [x] **§2**: Update the link to hazardlib
- [x] Add an example realizations output file
- [x] Update the gmfs xml output file
### Risk
- [x] **§9.5.1**: Replace the benefit-cost ratio map xml example with csv
- [x] Describe the parameter `time_event` for scenarios
- [x] Change the event loss table example adding the column rlzi
- [x] Document asset tags in the exposure model | non_priority | updates required for the user manual for hazard there is a reference to oq export hcurves all which now is spelled oq extract hazard all § update the link to hazardlib add an example realizations output file update the gmfs xml output file risk § replace the benefit cost ratio map xml example with csv describe the parameter time event for scenarios change the event loss table example adding the column rlzi document asset tags in the exposure model | 0 |
83,796 | 16,372,453,022 | IssuesEvent | 2021-05-15 12:16:59 | dotnet/roslyn-analyzers | https://api.github.com/repos/dotnet/roslyn-analyzers | closed | CA2217 False positive if setting value of enum using shift operator | Area-Microsoft.CodeQuality.Analyzers Bug False_Positive help wanted | ### Analyzer
**Diagnostic ID**: [CA2217](https://docs.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca2217): `Do not mark enums with FlagsAttribute`
### Analyzer source
**NuGet Package**: [Microsoft.CodeAnalysis.NetAnalyzers](https://www.nuget.org/packages/Microsoft.CodeAnalysis.NetAnalyzers)
**Version**: 5.0.3 (Latest)
### Describe the bug
False positive
### Steps To Reproduce
Analyse code like this:
```csharp
[Flags]
public enum Something
{
None = 0,
First = 1 << 0,
Second = 1 << 1,
Third = 1 << 2,
Fourth = 1 << 3,
Last = 1 << 4,
}
```
### Expected behavior
No violation
### Actual behavior
Violation:
error CA2217: Do not mark enums with FlagsAttribute
| 1.0 | CA2217 False positive if setting value of enum using shift operator - ### Analyzer
**Diagnostic ID**: [CA2217](https://docs.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca2217): `Do not mark enums with FlagsAttribute`
### Analyzer source
**NuGet Package**: [Microsoft.CodeAnalysis.NetAnalyzers](https://www.nuget.org/packages/Microsoft.CodeAnalysis.NetAnalyzers)
**Version**: 5.0.3 (Latest)
### Describe the bug
False positive
### Steps To Reproduce
Analyse code like this:
```csharp
[Flags]
public enum Something
{
None = 0,
First = 1 << 0,
Second = 1 << 1,
Third = 1 << 2,
Fourth = 1 << 3,
Last = 1 << 4,
}
```
### Expected behavior
No violation
### Actual behavior
Violation:
error CA2217: Do not mark enums with FlagsAttribute
| non_priority | false positive if setting value of enum using shift operator analyzer diagnostic id do not mark enums with flagsattribute analyzer source nuget package version latest describe the bug false positive steps to reproduce analyse code like this csharp public enum something none first second third fourth last expected behavior no violation actual behavior violation error do not mark enums with flagsattribute | 0 |
127,712 | 17,355,946,150 | IssuesEvent | 2021-07-29 14:25:10 | AlaskaAirlines/auro-input | https://api.github.com/repos/AlaskaAirlines/auro-input | opened | auro-input: redesign of common interface | Type: Design | # General Support Request
The auro-input is being reviewed for a new redesign of the common interface.
## Support request
Review the current state of the auro-input design and develop a concept for a new interface.
## Possible Solution
Design to review current UI for new design opportunities | 1.0 | auro-input: redesign of common interface - # General Support Request
The auro-input is being reviewed for a new redesign of the common interface.
## Support request
Review the current state of the auro-input design and develop a concept for a new interface.
## Possible Solution
Design to review current UI for new design opportunities | non_priority | auro input redesign of common interface general support request the auro input is being reviewed for a new redesign of the common interface support request review the current state of the auro input design and develop a concept for a new interface possible solution design to review current ui for new design opportunities | 0 |
100,072 | 30,609,710,564 | IssuesEvent | 2023-07-23 13:02:54 | icsharpcode/AvaloniaILSpy | https://api.github.com/repos/icsharpcode/AvaloniaILSpy | closed | Update Cake | issue-enhancement area-build | Seems we have a rather old version of Cake instead of the newer dotnet cake tooling (see folder /tools).
This leads to a mismatch with ./.github/workflows/build.yml that uses cake-build/cake-action@v1 - with dotnet cake one sees the exact same error as on the GH actions build. | 1.0 | Update Cake - Seems we have a rather old version of Cake instead of the newer dotnet cake tooling (see folder /tools).
This leads to a mismatch with ./.github/workflows/build.yml that uses cake-build/cake-action@v1 - with dotnet cake one sees the exact same error as on the GH actions build. | non_priority | update cake seems we have a rather old version of cake instead of the newer dotnet cake tooling see folder tools this leads to a mismatch with github workflows build yml that uses cake build cake action with dotnet cake one sees the exact same error as on the gh actions build | 0 |
290,420 | 21,877,810,667 | IssuesEvent | 2022-05-19 11:52:03 | stevenkfirth/xgbxml | https://api.github.com/repos/stevenkfirth/xgbxml | closed | Add all the auto-generated properties and methods to the documentation | documentation | This could be done by creating a separate page for each class (i.e. each gbXML element) and having an index page to link to them.
This will also need to be done for each version of the schema. | 1.0 | Add all the auto-generated properties and methods to the documentation - This could be done by creating a separate page for each class (i.e. each gbXML element) and having an index page to link to them.
This will also need to be done for each version of the schema. | non_priority | add all the auto generated properties and methods to the documentation this could be done by creating a separate page for each class i e each gbxml element and having an index page to link to them this will also need to be done for each version of the schema | 0 |
135,165 | 12,677,143,147 | IssuesEvent | 2020-06-19 07:07:52 | forkdelta/tokenbase | https://api.github.com/repos/forkdelta/tokenbase | closed | Formalize removal process of OLD tokens | documentation help wanted stale | We need to have some sort of procedure for removing all of the OLD tokens.
I propose that when we make announcements about contract changes, we state that the token is preserved under TICKER_OLD for 2 weeks. After 2 weeks, TICKER_OLD will be removed.
When TICKER_OLD is removed, we can make a second announcement about its removal. | 1.0 | Formalize removal process of OLD tokens - We need to have some sort of procedure for removing all of the OLD tokens.
I propose that when we make announcements about contract changes, we state that the token is preserved under TICKER_OLD for 2 weeks. After 2 weeks, TICKER_OLD will be removed.
When TICKER_OLD is removed, we can make a second announcement about its removal. | non_priority | formalize removal process of old tokens we need to have some sort of procedure for removing all of the old tokens i propose that when we make announcements about contract changes we state that the token is preserved under ticker old for weeks after weeks ticker old will be removed when ticker old is removed we can make a second announcement about its removal | 0 |
143,840 | 13,086,999,611 | IssuesEvent | 2020-08-02 09:40:02 | Oiangu9/XOA_QuantumDynamicsEngine | https://api.github.com/repos/Oiangu9/XOA_QuantumDynamicsEngine | opened | Write the documentation for the TUI 3 | Documentation TUI | - All the necessary dependencies to install for the software to work as expected and how to install them. | 1.0 | Write the documentation for the TUI 3 - - All the necessary dependencies to install for the software to work as expected and how to install them. | non_priority | write the documentation for the tui all the necessary dependencies to install for the software to work as expected and how to install them | 0 |
15,693 | 3,481,393,547 | IssuesEvent | 2015-12-29 15:51:51 | slivne/try_git | https://api.github.com/repos/slivne/try_git | opened | repair : repair_while_nodes_are_down_2_test | dtest repair | Check that repair is able to complete if one replica of data exists
1. Create a cluster of 4 nodes with rf=3
2. Stop node 2
3. Insert data
4. Stop node 3
5. Start node 2
6. Start repair on node 2
7. Check if repair is succesfull
| 1.0 | repair : repair_while_nodes_are_down_2_test - Check that repair is able to complete if one replica of data exists
1. Create a cluster of 4 nodes with rf=3
2. Stop node 2
3. Insert data
4. Stop node 3
5. Start node 2
6. Start repair on node 2
7. Check if repair is succesfull
| non_priority | repair repair while nodes are down test check that repair is able to complete if one replica of data exists create a cluster of nodes with rf stop node insert data stop node start node start repair on node check if repair is succesfull | 0 |
312,677 | 26,873,900,131 | IssuesEvent | 2023-02-04 20:11:53 | MPMG-DCC-UFMG/F01 | https://api.github.com/repos/MPMG-DCC-UFMG/F01 | closed | Teste de generalizacao para a tag Informações Institucionais - Leis Municipais - Várzea da Palma | generalization test development template - Síntese tecnologia e informatica (88) tag - Informações Institucionais subtag - Leis Municipais | DoD: Realizar o teste de Generalização do validador da tag Informações Institucionais - Leis Municipais para o Município de Várzea da Palma. | 1.0 | Teste de generalizacao para a tag Informações Institucionais - Leis Municipais - Várzea da Palma - DoD: Realizar o teste de Generalização do validador da tag Informações Institucionais - Leis Municipais para o Município de Várzea da Palma. | non_priority | teste de generalizacao para a tag informações institucionais leis municipais várzea da palma dod realizar o teste de generalização do validador da tag informações institucionais leis municipais para o município de várzea da palma | 0 |
442,593 | 30,844,674,577 | IssuesEvent | 2023-08-02 13:01:50 | zrdzn/GreatLifeSteal | https://api.github.com/repos/zrdzn/GreatLifeSteal | opened | Web panel specification | documentation | Features
- All eliminated players tab
- Eliminate specific online players
- Revive eliminated players
Stack
- Spring
- Next.JS
- ChakraUI | 1.0 | Web panel specification - Features
- All eliminated players tab
- Eliminate specific online players
- Revive eliminated players
Stack
- Spring
- Next.JS
- ChakraUI | non_priority | web panel specification features all eliminated players tab eliminate specific online players revive eliminated players stack spring next js chakraui | 0 |
267,864 | 28,509,379,152 | IssuesEvent | 2023-04-19 01:58:53 | RG4421/ampere-centos-kernel | https://api.github.com/repos/RG4421/ampere-centos-kernel | closed | CVE-2023-1078 (High) detected in linuxv5.2 - autoclosed | Mend: dependency security vulnerability | ## CVE-2023-1078 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxv5.2</b></p></summary>
<p>
<p>Linux kernel source tree</p>
<p>Library home page: <a href=https://github.com/torvalds/linux.git>https://github.com/torvalds/linux.git</a></p>
<p>Found in base branch: <b>amp-centos-8.0-kernel</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/rds/message.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was found in the Linux Kernel in RDS (Reliable Datagram Sockets) protocol. The rds_rm_zerocopy_callback() uses list_entry() on the head of a list causing a type confusion. Local user can trigger this with rds_message_put(). Type confusion leads to `struct rds_msg_zcopy_info *info` actually points to something else that is potentially controlled by local user. It is known how to trigger this, which causes an out of bounds access, and a lock corruption.
<p>Publish Date: 2023-03-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-1078>CVE-2023-1078</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2023-1078">https://www.linuxkernelcves.com/cves/CVE-2023-1078</a></p>
<p>Release Date: 2023-02-28</p>
<p>Fix Resolution: v4.19.273,v5.4.232,v5.10.168,v5.15.94,v6.1.12,v6.2-rc8</p>
</p>
</details>
<p></p>
| True | CVE-2023-1078 (High) detected in linuxv5.2 - autoclosed - ## CVE-2023-1078 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxv5.2</b></p></summary>
<p>
<p>Linux kernel source tree</p>
<p>Library home page: <a href=https://github.com/torvalds/linux.git>https://github.com/torvalds/linux.git</a></p>
<p>Found in base branch: <b>amp-centos-8.0-kernel</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/rds/message.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was found in the Linux Kernel in RDS (Reliable Datagram Sockets) protocol. The rds_rm_zerocopy_callback() uses list_entry() on the head of a list causing a type confusion. Local user can trigger this with rds_message_put(). Type confusion leads to `struct rds_msg_zcopy_info *info` actually points to something else that is potentially controlled by local user. It is known how to trigger this, which causes an out of bounds access, and a lock corruption.
<p>Publish Date: 2023-03-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-1078>CVE-2023-1078</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2023-1078">https://www.linuxkernelcves.com/cves/CVE-2023-1078</a></p>
<p>Release Date: 2023-02-28</p>
<p>Fix Resolution: v4.19.273,v5.4.232,v5.10.168,v5.15.94,v6.1.12,v6.2-rc8</p>
</p>
</details>
<p></p>
| non_priority | cve high detected in autoclosed cve high severity vulnerability vulnerable library linux kernel source tree library home page a href found in base branch amp centos kernel vulnerable source files net rds message c vulnerability details a flaw was found in the linux kernel in rds reliable datagram sockets protocol the rds rm zerocopy callback uses list entry on the head of a list causing a type confusion local user can trigger this with rds message put type confusion leads to struct rds msg zcopy info info actually points to something else that is potentially controlled by local user it is known how to trigger this which causes an out of bounds access and a lock corruption publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution | 0 |
102,604 | 8,850,289,210 | IssuesEvent | 2019-01-08 12:51:01 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | teamcity: failed test: TestInternalExecAppNameInitialization | C-test-failure O-robot | The following tests appear to have failed on master (testrace): TestInternalExecAppNameInitialization/session_bound_exec, TestInternalExecAppNameInitialization/root_internal_exec, TestInternalExecAppNameInitialization
You may want to check [for open issues](https://github.com/cockroachdb/cockroach/issues?q=is%3Aissue+is%3Aopen+TestInternalExecAppNameInitialization).
[#1083937](https://teamcity.cockroachdb.com/viewLog.html?buildId=1083937):
```
TestInternalExecAppNameInitialization
--- FAIL: test/TestInternalExecAppNameInitialization (0.520s)
Test ended in panic.
TestInternalExecAppNameInitialization/session_bound_exec
...builder.go:148 +0x1b2
github.com/cockroachdb/cockroach/pkg/sql.(*optPlanningCtx).buildExecMemo()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/plan_opt.go:290 +0x33b
github.com/cockroachdb/cockroach/pkg/sql.(*planner).makeOptimizerPlan()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/plan_opt.go:87 +0x137
github.com/cockroachdb/cockroach/pkg/sql.(*connExecutor).makeExecPlan()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:883 +0x1d0
github.com/cockroachdb/cockroach/pkg/sql.(*connExecutor).dispatchToExecutionEngine()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:789 +0x1e3
github.com/cockroachdb/cockroach/pkg/sql.(*connExecutor).execStmtInOpenState()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:420 +0x1083
github.com/cockroachdb/cockroach/pkg/sql.(*connExecutor).execStmt()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:97 +0x463
github.com/cockroachdb/cockroach/pkg/sql.(*connExecutor).run()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:1173 +0x343d
github.com/cockroachdb/cockroach/pkg/sql.(*internalExecutorImpl).initConnEx.func1()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/internal.go:204 +0x7d
Goroutine 1186 (running) created at:
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).serveStreams.func1()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:678 +0xb8
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/transport.(*http2Server).operateHeaders()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/transport/http2_server.go:424 +0x1483
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/transport.(*http2Server).HandleStreams()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/transport/http2_server.go:464 +0x87a
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).serveStreams()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:676 +0x16e
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).handleRawConn.func2()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:631 +0x53
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).handleRawConn.func3()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:639 +0x34
Goroutine 987 (running) created at:
github.com/cockroachdb/cockroach/pkg/sql.(*internalExecutorImpl).initConnEx()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/internal.go:203 +0x596
github.com/cockroachdb/cockroach/pkg/sql.(*internalExecutorImpl).execInternal()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/internal.go:490 +0x766
github.com/cockroachdb/cockroach/pkg/sql.(*internalExecutorImpl).queryInternal()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/internal.go:240 +0x141
github.com/cockroachdb/cockroach/pkg/sql.(*InternalExecutor).Query()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/internal.go:224 +0x10e
github.com/cockroachdb/cockroach/pkg/sql.(*LeaseManager).DeleteOrphanedLeases.func1.1()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/lease.go:1793 +0x139
github.com/cockroachdb/cockroach/pkg/util/retry.WithMaxAttempts()
/go/src/github.com/cockroachdb/cockroach/pkg/util/retry/retry.go:163 +0x142
github.com/cockroachdb/cockroach/pkg/sql.(*LeaseManager).DeleteOrphanedLeases.func1()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/lease.go:1791 +0x392
github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunWorker.func1()
/go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:198 +0x14a
==================
? github.com/cockroachdb/cockroach/pkg/sql/backfill [no test files]
TestInternalExecAppNameInitialization/root_internal_exec
...
I190108 02:28:09.641655 64360 server/status/recorder.go:610 [n1] available memory from cgroups (8.0 EiB) exceeds system memory 16 GiB, using system memory
I190108 02:28:09.641747 64360 server/server.go:1862 [n1] Could not start heap profiler worker due to: directory to store profiles could not be determined
I190108 02:28:09.660468 64360 server/server.go:1559 [n1] starting http server at 127.152.81.236:38263 (use: 127.152.81.236:38263)
I190108 02:28:09.660694 64360 server/server.go:1561 [n1] starting grpc/postgres server at 127.152.81.236:42531
I190108 02:28:09.660762 64360 server/server.go:1562 [n1] advertising CockroachDB node at 127.152.81.236:42531
W190108 02:28:09.680503 64555 storage/store.go:1465 [n1,s1,r6/1:/Table/{SystemCon…-11}] could not gossip system config: [NotLeaseHolderError] r6: replica (n1,s1):1 not lease holder; lease holder unknown
I190108 02:28:10.084131 64606 sql/event_log.go:135 [n1,intExec=optInToDiagnosticsStatReporting] Event: "set_cluster_setting", target: 0, info: {SettingName:diagnostics.reporting.enabled Value:true User:root}
I190108 02:28:10.308482 64582 sql/event_log.go:135 [n1,intExec=set-setting] Event: "set_cluster_setting", target: 0, info: {SettingName:version Value:2.1-3 User:root}
I190108 02:28:10.491459 64629 sql/event_log.go:135 [n1,intExec=disableNetTrace] Event: "set_cluster_setting", target: 0, info: {SettingName:trace.debug.enable Value:false User:root}
I190108 02:28:10.742909 64652 storage/replica_consistency.go:126 [n1,consistencyChecker,s1,r4/1:/System/ts{d-e}] triggering stats recomputation to resolve delta of {ContainsEstimates:true LastUpdateNanos:1546914489755340912 IntentAge:0 GCBytesAge:0 LiveBytes:-24446 LiveCount:-503 KeyBytes:-23703 KeyCount:-503 ValBytes:-743 ValCount:-503 IntentBytes:0 IntentCount:0 SysBytes:0 SysCount:0 XXX_NoUnkeyedLiteral:{} XXX_sizecache:0}
I190108 02:28:10.809779 64570 sql/event_log.go:135 [n1,intExec=initializeClusterSecret] Event: "set_cluster_setting", target: 0, info: {SettingName:cluster.secret Value:8546bb15-d581-4ca9-a770-6e38101c2f9a User:root}
I190108 02:28:10.956282 64677 sql/event_log.go:135 [n1,intExec=create-default-db] Event: "create_database", target: 50, info: {DatabaseName:defaultdb Statement:CREATE DATABASE IF NOT EXISTS defaultdb User:root}
I190108 02:28:11.037510 64680 sql/event_log.go:135 [n1,intExec=create-default-db] Event: "create_database", target: 51, info: {DatabaseName:postgres Statement:CREATE DATABASE IF NOT EXISTS postgres User:root}
I190108 02:28:11.052417 64430 gossip/gossip.go:1513 [n1] node has connected to cluster via gossip
I190108 02:28:11.053159 64430 storage/stores.go:262 [n1] wrote 0 node addresses to persistent storage
I190108 02:28:11.182143 64684 storage/replica_command.go:349 [n1,split,s1,r19/1:/{Table/23-Max}] initiating a split of this range at key /Table/24 [r20]
I190108 02:28:11.200553 64360 server/server.go:1620 [n1] done ensuring all necessary migrations have run
I190108 02:28:11.200836 64360 server/server.go:1623 [n1] serving sql connections
I190108 02:28:11.252382 64592 sql/event_log.go:135 [n1] Event: "node_join", target: 1, info: {Descriptor:{NodeID:1 Address:127.152.81.236:42531 Attrs: Locality: ServerVersion:2.1-3 BuildTag:v2.2.0-alpha.20181217-468-gdadcaa4 StartedAt:1546914489581102706 LocalityAddress:[] XXX_NoUnkeyedLiteral:{} XXX_sizecache:0} ClusterID:2b2fc0df-5c16-4e02-bc81-65056c8fb2d0 StartedAt:1546914489581102706 LastUp:1546914489581102706}
I190108 02:28:11.285313 64589 server/server_update.go:66 [n1] no need to upgrade, cluster already at the newest version
I190108 02:28:11.376267 64360 util/stop/stopper.go:536 quiescing; tasks left:
1 [async] transport racer
1 [async] closedts-rangefeed-subscriber
I190108 02:28:11.383311 64360 util/stop/stopper.go:536 quiescing; tasks left:
1 [async] transport racer
I190108 02:28:11.434358 64569 kv/transport_race.go:113 transport race promotion: ran 19 iterations on up to 319 requests
TestInternalExecAppNameInitialization
--- FAIL: testrace/TestInternalExecAppNameInitialization (0.000s)
Test ended in panic.
```
Please assign, take a look and update the issue accordingly.
| 1.0 | teamcity: failed test: TestInternalExecAppNameInitialization - The following tests appear to have failed on master (testrace): TestInternalExecAppNameInitialization/session_bound_exec, TestInternalExecAppNameInitialization/root_internal_exec, TestInternalExecAppNameInitialization
You may want to check [for open issues](https://github.com/cockroachdb/cockroach/issues?q=is%3Aissue+is%3Aopen+TestInternalExecAppNameInitialization).
[#1083937](https://teamcity.cockroachdb.com/viewLog.html?buildId=1083937):
```
TestInternalExecAppNameInitialization
--- FAIL: test/TestInternalExecAppNameInitialization (0.520s)
Test ended in panic.
TestInternalExecAppNameInitialization/session_bound_exec
...builder.go:148 +0x1b2
github.com/cockroachdb/cockroach/pkg/sql.(*optPlanningCtx).buildExecMemo()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/plan_opt.go:290 +0x33b
github.com/cockroachdb/cockroach/pkg/sql.(*planner).makeOptimizerPlan()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/plan_opt.go:87 +0x137
github.com/cockroachdb/cockroach/pkg/sql.(*connExecutor).makeExecPlan()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:883 +0x1d0
github.com/cockroachdb/cockroach/pkg/sql.(*connExecutor).dispatchToExecutionEngine()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:789 +0x1e3
github.com/cockroachdb/cockroach/pkg/sql.(*connExecutor).execStmtInOpenState()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:420 +0x1083
github.com/cockroachdb/cockroach/pkg/sql.(*connExecutor).execStmt()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:97 +0x463
github.com/cockroachdb/cockroach/pkg/sql.(*connExecutor).run()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:1173 +0x343d
github.com/cockroachdb/cockroach/pkg/sql.(*internalExecutorImpl).initConnEx.func1()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/internal.go:204 +0x7d
Goroutine 1186 (running) created at:
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).serveStreams.func1()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:678 +0xb8
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/transport.(*http2Server).operateHeaders()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/transport/http2_server.go:424 +0x1483
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/transport.(*http2Server).HandleStreams()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/transport/http2_server.go:464 +0x87a
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).serveStreams()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:676 +0x16e
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).handleRawConn.func2()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:631 +0x53
github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc.(*Server).handleRawConn.func3()
/go/src/github.com/cockroachdb/cockroach/vendor/google.golang.org/grpc/server.go:639 +0x34
Goroutine 987 (running) created at:
github.com/cockroachdb/cockroach/pkg/sql.(*internalExecutorImpl).initConnEx()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/internal.go:203 +0x596
github.com/cockroachdb/cockroach/pkg/sql.(*internalExecutorImpl).execInternal()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/internal.go:490 +0x766
github.com/cockroachdb/cockroach/pkg/sql.(*internalExecutorImpl).queryInternal()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/internal.go:240 +0x141
github.com/cockroachdb/cockroach/pkg/sql.(*InternalExecutor).Query()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/internal.go:224 +0x10e
github.com/cockroachdb/cockroach/pkg/sql.(*LeaseManager).DeleteOrphanedLeases.func1.1()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/lease.go:1793 +0x139
github.com/cockroachdb/cockroach/pkg/util/retry.WithMaxAttempts()
/go/src/github.com/cockroachdb/cockroach/pkg/util/retry/retry.go:163 +0x142
github.com/cockroachdb/cockroach/pkg/sql.(*LeaseManager).DeleteOrphanedLeases.func1()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/lease.go:1791 +0x392
github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunWorker.func1()
/go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:198 +0x14a
==================
? github.com/cockroachdb/cockroach/pkg/sql/backfill [no test files]
TestInternalExecAppNameInitialization/root_internal_exec
...
I190108 02:28:09.641655 64360 server/status/recorder.go:610 [n1] available memory from cgroups (8.0 EiB) exceeds system memory 16 GiB, using system memory
I190108 02:28:09.641747 64360 server/server.go:1862 [n1] Could not start heap profiler worker due to: directory to store profiles could not be determined
I190108 02:28:09.660468 64360 server/server.go:1559 [n1] starting http server at 127.152.81.236:38263 (use: 127.152.81.236:38263)
I190108 02:28:09.660694 64360 server/server.go:1561 [n1] starting grpc/postgres server at 127.152.81.236:42531
I190108 02:28:09.660762 64360 server/server.go:1562 [n1] advertising CockroachDB node at 127.152.81.236:42531
W190108 02:28:09.680503 64555 storage/store.go:1465 [n1,s1,r6/1:/Table/{SystemCon…-11}] could not gossip system config: [NotLeaseHolderError] r6: replica (n1,s1):1 not lease holder; lease holder unknown
I190108 02:28:10.084131 64606 sql/event_log.go:135 [n1,intExec=optInToDiagnosticsStatReporting] Event: "set_cluster_setting", target: 0, info: {SettingName:diagnostics.reporting.enabled Value:true User:root}
I190108 02:28:10.308482 64582 sql/event_log.go:135 [n1,intExec=set-setting] Event: "set_cluster_setting", target: 0, info: {SettingName:version Value:2.1-3 User:root}
I190108 02:28:10.491459 64629 sql/event_log.go:135 [n1,intExec=disableNetTrace] Event: "set_cluster_setting", target: 0, info: {SettingName:trace.debug.enable Value:false User:root}
I190108 02:28:10.742909 64652 storage/replica_consistency.go:126 [n1,consistencyChecker,s1,r4/1:/System/ts{d-e}] triggering stats recomputation to resolve delta of {ContainsEstimates:true LastUpdateNanos:1546914489755340912 IntentAge:0 GCBytesAge:0 LiveBytes:-24446 LiveCount:-503 KeyBytes:-23703 KeyCount:-503 ValBytes:-743 ValCount:-503 IntentBytes:0 IntentCount:0 SysBytes:0 SysCount:0 XXX_NoUnkeyedLiteral:{} XXX_sizecache:0}
I190108 02:28:10.809779 64570 sql/event_log.go:135 [n1,intExec=initializeClusterSecret] Event: "set_cluster_setting", target: 0, info: {SettingName:cluster.secret Value:8546bb15-d581-4ca9-a770-6e38101c2f9a User:root}
I190108 02:28:10.956282 64677 sql/event_log.go:135 [n1,intExec=create-default-db] Event: "create_database", target: 50, info: {DatabaseName:defaultdb Statement:CREATE DATABASE IF NOT EXISTS defaultdb User:root}
I190108 02:28:11.037510 64680 sql/event_log.go:135 [n1,intExec=create-default-db] Event: "create_database", target: 51, info: {DatabaseName:postgres Statement:CREATE DATABASE IF NOT EXISTS postgres User:root}
I190108 02:28:11.052417 64430 gossip/gossip.go:1513 [n1] node has connected to cluster via gossip
I190108 02:28:11.053159 64430 storage/stores.go:262 [n1] wrote 0 node addresses to persistent storage
I190108 02:28:11.182143 64684 storage/replica_command.go:349 [n1,split,s1,r19/1:/{Table/23-Max}] initiating a split of this range at key /Table/24 [r20]
I190108 02:28:11.200553 64360 server/server.go:1620 [n1] done ensuring all necessary migrations have run
I190108 02:28:11.200836 64360 server/server.go:1623 [n1] serving sql connections
I190108 02:28:11.252382 64592 sql/event_log.go:135 [n1] Event: "node_join", target: 1, info: {Descriptor:{NodeID:1 Address:127.152.81.236:42531 Attrs: Locality: ServerVersion:2.1-3 BuildTag:v2.2.0-alpha.20181217-468-gdadcaa4 StartedAt:1546914489581102706 LocalityAddress:[] XXX_NoUnkeyedLiteral:{} XXX_sizecache:0} ClusterID:2b2fc0df-5c16-4e02-bc81-65056c8fb2d0 StartedAt:1546914489581102706 LastUp:1546914489581102706}
I190108 02:28:11.285313 64589 server/server_update.go:66 [n1] no need to upgrade, cluster already at the newest version
I190108 02:28:11.376267 64360 util/stop/stopper.go:536 quiescing; tasks left:
1 [async] transport racer
1 [async] closedts-rangefeed-subscriber
I190108 02:28:11.383311 64360 util/stop/stopper.go:536 quiescing; tasks left:
1 [async] transport racer
I190108 02:28:11.434358 64569 kv/transport_race.go:113 transport race promotion: ran 19 iterations on up to 319 requests
TestInternalExecAppNameInitialization
--- FAIL: testrace/TestInternalExecAppNameInitialization (0.000s)
Test ended in panic.
```
Please assign, take a look and update the issue accordingly.
| non_priority | teamcity failed test testinternalexecappnameinitialization the following tests appear to have failed on master testrace testinternalexecappnameinitialization session bound exec testinternalexecappnameinitialization root internal exec testinternalexecappnameinitialization you may want to check testinternalexecappnameinitialization fail test testinternalexecappnameinitialization test ended in panic testinternalexecappnameinitialization session bound exec builder go github com cockroachdb cockroach pkg sql optplanningctx buildexecmemo go src github com cockroachdb cockroach pkg sql plan opt go github com cockroachdb cockroach pkg sql planner makeoptimizerplan go src github com cockroachdb cockroach pkg sql plan opt go github com cockroachdb cockroach pkg sql connexecutor makeexecplan go src github com cockroachdb cockroach pkg sql conn executor exec go github com cockroachdb cockroach pkg sql connexecutor dispatchtoexecutionengine go src github com cockroachdb cockroach pkg sql conn executor exec go github com cockroachdb cockroach pkg sql connexecutor execstmtinopenstate go src github com cockroachdb cockroach pkg sql conn executor exec go github com cockroachdb cockroach pkg sql connexecutor execstmt go src github com cockroachdb cockroach pkg sql conn executor exec go github com cockroachdb cockroach pkg sql connexecutor run go src github com cockroachdb cockroach pkg sql conn executor go github com cockroachdb cockroach pkg sql internalexecutorimpl initconnex go src github com cockroachdb cockroach pkg sql internal go goroutine running created at github com cockroachdb cockroach vendor google golang org grpc server servestreams go src github com cockroachdb cockroach vendor google golang org grpc server go github com cockroachdb cockroach vendor google golang org grpc transport operateheaders go src github com cockroachdb cockroach vendor google golang org grpc transport server go github com cockroachdb cockroach vendor google golang org grpc transport handlestreams go src github com cockroachdb cockroach vendor google golang org grpc transport server go github com cockroachdb cockroach vendor google golang org grpc server servestreams go src github com cockroachdb cockroach vendor google golang org grpc server go github com cockroachdb cockroach vendor google golang org grpc server handlerawconn go src github com cockroachdb cockroach vendor google golang org grpc server go github com cockroachdb cockroach vendor google golang org grpc server handlerawconn go src github com cockroachdb cockroach vendor google golang org grpc server go goroutine running created at github com cockroachdb cockroach pkg sql internalexecutorimpl initconnex go src github com cockroachdb cockroach pkg sql internal go github com cockroachdb cockroach pkg sql internalexecutorimpl execinternal go src github com cockroachdb cockroach pkg sql internal go github com cockroachdb cockroach pkg sql internalexecutorimpl queryinternal go src github com cockroachdb cockroach pkg sql internal go github com cockroachdb cockroach pkg sql internalexecutor query go src github com cockroachdb cockroach pkg sql internal go github com cockroachdb cockroach pkg sql leasemanager deleteorphanedleases go src github com cockroachdb cockroach pkg sql lease go github com cockroachdb cockroach pkg util retry withmaxattempts go src github com cockroachdb cockroach pkg util retry retry go github com cockroachdb cockroach pkg sql leasemanager deleteorphanedleases go src github com cockroachdb cockroach pkg sql lease go github com cockroachdb cockroach pkg util stop stopper runworker go src github com cockroachdb cockroach pkg util stop stopper go github com cockroachdb cockroach pkg sql backfill testinternalexecappnameinitialization root internal exec server status recorder go available memory from cgroups eib exceeds system memory gib using system memory server server go could not start heap profiler worker due to directory to store profiles could not be determined server server go starting http server at use server server go starting grpc postgres server at server server go advertising cockroachdb node at storage store go could not gossip system config replica not lease holder lease holder unknown sql event log go event set cluster setting target info settingname diagnostics reporting enabled value true user root sql event log go event set cluster setting target info settingname version value user root sql event log go event set cluster setting target info settingname trace debug enable value false user root storage replica consistency go triggering stats recomputation to resolve delta of containsestimates true lastupdatenanos intentage gcbytesage livebytes livecount keybytes keycount valbytes valcount intentbytes intentcount sysbytes syscount xxx nounkeyedliteral xxx sizecache sql event log go event set cluster setting target info settingname cluster secret value user root sql event log go event create database target info databasename defaultdb statement create database if not exists defaultdb user root sql event log go event create database target info databasename postgres statement create database if not exists postgres user root gossip gossip go node has connected to cluster via gossip storage stores go wrote node addresses to persistent storage storage replica command go initiating a split of this range at key table server server go done ensuring all necessary migrations have run server server go serving sql connections sql event log go event node join target info descriptor nodeid address attrs locality serverversion buildtag alpha startedat localityaddress xxx nounkeyedliteral xxx sizecache clusterid startedat lastup server server update go no need to upgrade cluster already at the newest version util stop stopper go quiescing tasks left transport racer closedts rangefeed subscriber util stop stopper go quiescing tasks left transport racer kv transport race go transport race promotion ran iterations on up to requests testinternalexecappnameinitialization fail testrace testinternalexecappnameinitialization test ended in panic please assign take a look and update the issue accordingly | 0 |
125,258 | 12,255,218,586 | IssuesEvent | 2020-05-06 09:49:37 | zuzu59/alarm_telegram | https://api.github.com/repos/zuzu59/alarm_telegram | closed | DOC: documenter la création et gestion de BOT dans le readme | documentation | Il faut documenter la création et gestion de BOT dans le readme peut-être simplement en indiquant le document gdoc mais c'est si simple ;-)
| 1.0 | DOC: documenter la création et gestion de BOT dans le readme - Il faut documenter la création et gestion de BOT dans le readme peut-être simplement en indiquant le document gdoc mais c'est si simple ;-)
| non_priority | doc documenter la création et gestion de bot dans le readme il faut documenter la création et gestion de bot dans le readme peut être simplement en indiquant le document gdoc mais c est si simple | 0 |
177,751 | 14,644,120,489 | IssuesEvent | 2020-12-25 21:05:14 | keepassxreboot/keepassxc | https://api.github.com/repos/keepassxreboot/keepassxc | closed | Explain KeeShare protocol in Docs | documentation :bookmark_tabs: | ## Summary
Please provide documentation on how KeeShare works, it seems rather complex and undocumented at the moment. Technical details are almost non-existent. Thus not much can be determined about it without diving into the source, which isn't efficient.
## Context
Currently I cannot find any documentation regarding KeeShare, on the developer side at least. I plan on working on a keepass2android plugin to hopefully work with KeeShare files.
To ensure this is implemented correctly and securely, I'll need to know how all the crypto works.
| 1.0 | Explain KeeShare protocol in Docs - ## Summary
Please provide documentation on how KeeShare works, it seems rather complex and undocumented at the moment. Technical details are almost non-existent. Thus not much can be determined about it without diving into the source, which isn't efficient.
## Context
Currently I cannot find any documentation regarding KeeShare, on the developer side at least. I plan on working on a keepass2android plugin to hopefully work with KeeShare files.
To ensure this is implemented correctly and securely, I'll need to know how all the crypto works.
| non_priority | explain keeshare protocol in docs summary please provide documentation on how keeshare works it seems rather complex and undocumented at the moment technical details are almost non existent thus not much can be determined about it without diving into the source which isn t efficient context currently i cannot find any documentation regarding keeshare on the developer side at least i plan on working on a plugin to hopefully work with keeshare files to ensure this is implemented correctly and securely i ll need to know how all the crypto works | 0 |
13,911 | 8,403,934,146 | IssuesEvent | 2018-10-11 11:18:08 | src-d/go-git | https://api.github.com/repos/src-d/go-git | opened | performance: difftree is sorting treeEntries but they might be already sorted | enhancement performance | Rescuing this performance improvement proposal by @alcortesm:
A significant part of difftree execution time is spent in lexicographically sorting by name the treeEntries of every tree.
A couple of not very reliable sources mention treeEntries are already sorted lexicographically in every git tree.
If this is true, the performance of difftree can be improved by removing the sorting of the treeEntries.
- [ ] confirm that treeEntries are already lexicographically sorted in every tree
- [ ] confirm this has always been the case, this is, all valid packfiles have their entries sorted, no matter how old they are.
- [ ] add the sort assumption to noder.Children
- [ ] add the sorting code to fsnoder implementation
- [ ] remove the sorting code from difftree | True | performance: difftree is sorting treeEntries but they might be already sorted - Rescuing this performance improvement proposal by @alcortesm:
A significant part of difftree execution time is spent in lexicographically sorting by name the treeEntries of every tree.
A couple of not very reliable sources mention treeEntries are already sorted lexicographically in every git tree.
If this is true, the performance of difftree can be improved by removing the sorting of the treeEntries.
- [ ] confirm that treeEntries are already lexicographically sorted in every tree
- [ ] confirm this has always been the case, this is, all valid packfiles have their entries sorted, no matter how old they are.
- [ ] add the sort assumption to noder.Children
- [ ] add the sorting code to fsnoder implementation
- [ ] remove the sorting code from difftree | non_priority | performance difftree is sorting treeentries but they might be already sorted rescuing this performance improvement proposal by alcortesm a significant part of difftree execution time is spent in lexicographically sorting by name the treeentries of every tree a couple of not very reliable sources mention treeentries are already sorted lexicographically in every git tree if this is true the performance of difftree can be improved by removing the sorting of the treeentries confirm that treeentries are already lexicographically sorted in every tree confirm this has always been the case this is all valid packfiles have their entries sorted no matter how old they are add the sort assumption to noder children add the sorting code to fsnoder implementation remove the sorting code from difftree | 0 |
8,893 | 2,612,926,688 | IssuesEvent | 2015-02-27 17:33:18 | chrsmith/windows-package-manager | https://api.github.com/repos/chrsmith/windows-package-manager | closed | Npackd Package Folder Location | auto-migrated Type-Defect | ```
Hello,
Great software. We are very happy with the basic functionality Npackd provides
so far.
We currently use Npackdcl with a private Repository XML hosted from an internal
server. We are seeing the following behavior:
1.) Package installation creates a folder named after the package name in
C:\Program Files (x86)\[PACKAGE_NAME] even though the actual installation
directory for the software does not reside there.
Example package xml:
===
<package name="com.jamsoftware.TreeSizeFree">
<title>Tree Size Free</title>
<url></url>
<description>Tree Size Free</description>
<icon></icon>
<license>org.gnu.GPLv3</license>
<category>Diag Tools</category>
</package>
<version name="2.7" package="com.jamsoftware.TreeSizeFree" type="one-file">
<important-file path="TreeSizeFreeSetup.exe" title="Installer" />
<file path=".Npackd\Install.bat">TreeSizeFreeSetup.exe /SILENT</file>
<file path=".Npackd\Uninstall.bat">unins000.exe</file>
<url>https://[WEB_SERVER]/packages/com.jamsoftware.TreeSizeFree/2.7/TreeSizeFreeSetup.exe</url>
<detect-file>
<path>C:\Program Files (x86)\JAM Software\TreeSize Free</path>
<sha1>0c0979cec865d66b4c459473765c059d8aaca3e1</sha1>
</detect-file>
</version>
===
The actual software gets installed in "C:\Program Files (x86)\JAM
Software\TreeSize Free" while Npackd creates a folder called "C:\Program Files
(x86)\Tree_Size_Free"
We are using Npackd CL 1.17.9 with a repository.xml file hosted from IIS7
How do we either:
1.) Keep Npackd from generating its own package directory under Program
Files(x86) -or-
2.) Dictate where the Npackd package directory gets placed
The current behavior is a bit messy at this point generating additional folders
on the filesystem without much logic to their placement. If anything, shouldn't
this "Package Folder" be held within the Npackd installation folder so it make
a bit more sense why its there?
Thank you for your time.
```
Original issue reported on code.google.com by `rlait...@gmail.com` on 21 Oct 2013 at 4:00 | 1.0 | Npackd Package Folder Location - ```
Hello,
Great software. We are very happy with the basic functionality Npackd provides
so far.
We currently use Npackdcl with a private Repository XML hosted from an internal
server. We are seeing the following behavior:
1.) Package installation creates a folder named after the package name in
C:\Program Files (x86)\[PACKAGE_NAME] even though the actual installation
directory for the software does not reside there.
Example package xml:
===
<package name="com.jamsoftware.TreeSizeFree">
<title>Tree Size Free</title>
<url></url>
<description>Tree Size Free</description>
<icon></icon>
<license>org.gnu.GPLv3</license>
<category>Diag Tools</category>
</package>
<version name="2.7" package="com.jamsoftware.TreeSizeFree" type="one-file">
<important-file path="TreeSizeFreeSetup.exe" title="Installer" />
<file path=".Npackd\Install.bat">TreeSizeFreeSetup.exe /SILENT</file>
<file path=".Npackd\Uninstall.bat">unins000.exe</file>
<url>https://[WEB_SERVER]/packages/com.jamsoftware.TreeSizeFree/2.7/TreeSizeFreeSetup.exe</url>
<detect-file>
<path>C:\Program Files (x86)\JAM Software\TreeSize Free</path>
<sha1>0c0979cec865d66b4c459473765c059d8aaca3e1</sha1>
</detect-file>
</version>
===
The actual software gets installed in "C:\Program Files (x86)\JAM
Software\TreeSize Free" while Npackd creates a folder called "C:\Program Files
(x86)\Tree_Size_Free"
We are using Npackd CL 1.17.9 with a repository.xml file hosted from IIS7
How do we either:
1.) Keep Npackd from generating its own package directory under Program
Files(x86) -or-
2.) Dictate where the Npackd package directory gets placed
The current behavior is a bit messy at this point generating additional folders
on the filesystem without much logic to their placement. If anything, shouldn't
this "Package Folder" be held within the Npackd installation folder so it make
a bit more sense why its there?
Thank you for your time.
```
Original issue reported on code.google.com by `rlait...@gmail.com` on 21 Oct 2013 at 4:00 | non_priority | npackd package folder location hello great software we are very happy with the basic functionality npackd provides so far we currently use npackdcl with a private repository xml hosted from an internal server we are seeing the following behavior package installation creates a folder named after the package name in c program files even though the actual installation directory for the software does not reside there example package xml tree size free tree size free org gnu diag tools treesizefreesetup exe silent exe https packages com jamsoftware treesizefree treesizefreesetup exe c program files jam software treesize free the actual software gets installed in c program files jam software treesize free while npackd creates a folder called c program files tree size free we are using npackd cl with a repository xml file hosted from how do we either keep npackd from generating its own package directory under program files or dictate where the npackd package directory gets placed the current behavior is a bit messy at this point generating additional folders on the filesystem without much logic to their placement if anything shouldn t this package folder be held within the npackd installation folder so it make a bit more sense why its there thank you for your time original issue reported on code google com by rlait gmail com on oct at | 0 |
63,939 | 7,753,508,827 | IssuesEvent | 2018-05-31 01:05:27 | learningequality/kolibri | https://api.github.com/repos/learningequality/kolibri | closed | pressing 'enter' doesn't submit 'new lesson' modal from description field | TAG: needs design TASK: bug fix TASK: ux update |
### Observed behavior
When creating a new lesson, pressing 'enter' adds a new line instead of submitting:
However, new lines are ignored anyway:
### Expected behavior
'Description' field should ignore 'Enter' keypress and allow the modal to handle it
### User-facing consequences
* more button presses necessary to create a new lesson using the keyboard
* unexpected behavior because newlines are allowed on input and ignored on output
### Steps to reproduce
Create a new lesson with newlines in the description
### Context
k0.9.0
| 1.0 | pressing 'enter' doesn't submit 'new lesson' modal from description field -
### Observed behavior
When creating a new lesson, pressing 'enter' adds a new line instead of submitting:
However, new lines are ignored anyway:
### Expected behavior
'Description' field should ignore 'Enter' keypress and allow the modal to handle it
### User-facing consequences
* more button presses necessary to create a new lesson using the keyboard
* unexpected behavior because newlines are allowed on input and ignored on output
### Steps to reproduce
Create a new lesson with newlines in the description
### Context
k0.9.0
| non_priority | pressing enter doesn t submit new lesson modal from description field observed behavior when creating a new lesson pressing enter adds a new line instead of submitting however new lines are ignored anyway expected behavior description field should ignore enter keypress and allow the modal to handle it user facing consequences more button presses necessary to create a new lesson using the keyboard unexpected behavior because newlines are allowed on input and ignored on output steps to reproduce create a new lesson with newlines in the description context | 0 |
50,035 | 10,441,715,179 | IssuesEvent | 2019-09-18 11:29:36 | akamsteeg/AtleX.CommandLineArguments | https://api.github.com/repos/akamsteeg/AtleX.CommandLineArguments | closed | Remove cached types from HelpWriter | code quality enhancement | In `HelpWriter`, we cache the types of `DisplayAttribute` and `RequiredAttribute` but that serves no purpose besides making the object bigger.
https://github.com/akamsteeg/AtleX.CommandLineArguments/blob/b3934eebb28f48825a0b90c8addebfc6a7c25ff6/src/AtleX.CommandLineArguments/Help/HelpWriter.cs#L14-L22
We should remove those cached instances. | 1.0 | Remove cached types from HelpWriter - In `HelpWriter`, we cache the types of `DisplayAttribute` and `RequiredAttribute` but that serves no purpose besides making the object bigger.
https://github.com/akamsteeg/AtleX.CommandLineArguments/blob/b3934eebb28f48825a0b90c8addebfc6a7c25ff6/src/AtleX.CommandLineArguments/Help/HelpWriter.cs#L14-L22
We should remove those cached instances. | non_priority | remove cached types from helpwriter in helpwriter we cache the types of displayattribute and requiredattribute but that serves no purpose besides making the object bigger we should remove those cached instances | 0 |
221,143 | 24,590,722,599 | IssuesEvent | 2022-10-14 01:45:42 | mcaj-git/nextcloud-dev | https://api.github.com/repos/mcaj-git/nextcloud-dev | opened | CVE-2022-37601 (High) detected in loader-utils-1.0.4.tgz, loader-utils-1.4.0.tgz | security vulnerability | ## CVE-2022-37601 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>loader-utils-1.0.4.tgz</b>, <b>loader-utils-1.4.0.tgz</b></p></summary>
<p>
<details><summary><b>loader-utils-1.0.4.tgz</b></p></summary>
<p>utils for webpack loaders</p>
<p>Library home page: <a href="https://registry.npmjs.org/loader-utils/-/loader-utils-1.0.4.tgz">https://registry.npmjs.org/loader-utils/-/loader-utils-1.0.4.tgz</a></p>
<p>
Dependency Hierarchy:
- handlebars-loader-1.7.1.tgz (Root Library)
- :x: **loader-utils-1.0.4.tgz** (Vulnerable Library)
</details>
<details><summary><b>loader-utils-1.4.0.tgz</b></p></summary>
<p>utils for webpack loaders</p>
<p>Library home page: <a href="https://registry.npmjs.org/loader-utils/-/loader-utils-1.4.0.tgz">https://registry.npmjs.org/loader-utils/-/loader-utils-1.4.0.tgz</a></p>
<p>
Dependency Hierarchy:
- babel-loader-8.2.2.tgz (Root Library)
- :x: **loader-utils-1.4.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/mcaj-git/nextcloud-dev/commit/593644825e582dbe07983985c91cfa4f02afa3bc">593644825e582dbe07983985c91cfa4f02afa3bc</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 vulnerability in function parseQuery in parseQuery.js in webpack loader-utils 2.0.0 via the name variable in parseQuery.js.
<p>Publish Date: 2022-10-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-37601>CVE-2022-37601</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-12</p>
<p>Fix Resolution (loader-utils): 2.0.0</p>
<p>Direct dependency fix Resolution (babel-loader): 8.2.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-37601 (High) detected in loader-utils-1.0.4.tgz, loader-utils-1.4.0.tgz - ## CVE-2022-37601 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>loader-utils-1.0.4.tgz</b>, <b>loader-utils-1.4.0.tgz</b></p></summary>
<p>
<details><summary><b>loader-utils-1.0.4.tgz</b></p></summary>
<p>utils for webpack loaders</p>
<p>Library home page: <a href="https://registry.npmjs.org/loader-utils/-/loader-utils-1.0.4.tgz">https://registry.npmjs.org/loader-utils/-/loader-utils-1.0.4.tgz</a></p>
<p>
Dependency Hierarchy:
- handlebars-loader-1.7.1.tgz (Root Library)
- :x: **loader-utils-1.0.4.tgz** (Vulnerable Library)
</details>
<details><summary><b>loader-utils-1.4.0.tgz</b></p></summary>
<p>utils for webpack loaders</p>
<p>Library home page: <a href="https://registry.npmjs.org/loader-utils/-/loader-utils-1.4.0.tgz">https://registry.npmjs.org/loader-utils/-/loader-utils-1.4.0.tgz</a></p>
<p>
Dependency Hierarchy:
- babel-loader-8.2.2.tgz (Root Library)
- :x: **loader-utils-1.4.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/mcaj-git/nextcloud-dev/commit/593644825e582dbe07983985c91cfa4f02afa3bc">593644825e582dbe07983985c91cfa4f02afa3bc</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 vulnerability in function parseQuery in parseQuery.js in webpack loader-utils 2.0.0 via the name variable in parseQuery.js.
<p>Publish Date: 2022-10-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-37601>CVE-2022-37601</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-12</p>
<p>Fix Resolution (loader-utils): 2.0.0</p>
<p>Direct dependency fix Resolution (babel-loader): 8.2.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in loader utils tgz loader utils tgz cve high severity vulnerability vulnerable libraries loader utils tgz loader utils tgz loader utils tgz utils for webpack loaders library home page a href dependency hierarchy handlebars loader tgz root library x loader utils tgz vulnerable library loader utils tgz utils for webpack loaders library home page a href dependency hierarchy babel loader tgz root library x loader utils tgz vulnerable library found in head commit a href found in base branch master vulnerability details prototype pollution vulnerability in function parsequery in parsequery js in webpack loader utils via the name variable in parsequery js publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution loader utils direct dependency fix resolution babel loader step up your open source security game with mend | 0 |
4,636 | 5,221,210,847 | IssuesEvent | 2017-01-27 00:28:21 | leo-project/leofs | https://api.github.com/repos/leo-project/leofs | closed | [1.3.0] [1.3.1] Delete Bucket does not remove the objects stored in it | Bug Security v1.3 _leo_manager | ## Description
Delete a bucket in LeoFS should also remove all the objects in it, but from 1.3.0, those objects are not removed. Creating a bucket with the same name and the file can then be easily accessed. A potential security problem.
## Analysis
This is because of a change in `leo_manager_api:delete_bucket`, during the step of removing all the objects.
https://github.com/leo-project/leofs/blob/master/apps/leo_manager/src/leo_manager_api.erl#L2285
This was a change introduced in 1.4 (at that time) development, when we added the metadata cache for "directories"
https://github.com/leo-project/leo_manager/commit/cca7c4618fe86dd8874c00f9bd13c657b69ce366
it calls `leo_storage_handler_directory:delete` instead of `leo_storage_handler_directory:delete_objects_in_parent_dir`
The call does not exist in 1.3 branch of `leo_storage` as we do not merge the metadata cache into 1.3
| True | [1.3.0] [1.3.1] Delete Bucket does not remove the objects stored in it - ## Description
Delete a bucket in LeoFS should also remove all the objects in it, but from 1.3.0, those objects are not removed. Creating a bucket with the same name and the file can then be easily accessed. A potential security problem.
## Analysis
This is because of a change in `leo_manager_api:delete_bucket`, during the step of removing all the objects.
https://github.com/leo-project/leofs/blob/master/apps/leo_manager/src/leo_manager_api.erl#L2285
This was a change introduced in 1.4 (at that time) development, when we added the metadata cache for "directories"
https://github.com/leo-project/leo_manager/commit/cca7c4618fe86dd8874c00f9bd13c657b69ce366
it calls `leo_storage_handler_directory:delete` instead of `leo_storage_handler_directory:delete_objects_in_parent_dir`
The call does not exist in 1.3 branch of `leo_storage` as we do not merge the metadata cache into 1.3
| non_priority | delete bucket does not remove the objects stored in it description delete a bucket in leofs should also remove all the objects in it but from those objects are not removed creating a bucket with the same name and the file can then be easily accessed a potential security problem analysis this is because of a change in leo manager api delete bucket during the step of removing all the objects this was a change introduced in at that time development when we added the metadata cache for directories it calls leo storage handler directory delete instead of leo storage handler directory delete objects in parent dir the call does not exist in branch of leo storage as we do not merge the metadata cache into | 0 |
62,651 | 6,802,324,461 | IssuesEvent | 2017-11-02 19:47:44 | WikiWatershed/model-my-watershed | https://api.github.com/repos/WikiWatershed/model-my-watershed | closed | Remove DRB-specific layers from BiG CZ layer selector | BiG CZ November demo BigCZ tested/verified | @emiliom to provide list of layers to keep. | 1.0 | Remove DRB-specific layers from BiG CZ layer selector - @emiliom to provide list of layers to keep. | non_priority | remove drb specific layers from big cz layer selector emiliom to provide list of layers to keep | 0 |
26,570 | 4,233,258,131 | IssuesEvent | 2016-07-05 06:58:09 | Microsoft/vsts-tasks | https://api.github.com/repos/Microsoft/vsts-tasks | closed | Sometimes exception loading assembly when running VSO online build in Run Functional Tests step | Area: Test | Hi,
I have a sometime issue when running build on VSO online in the Run Functional Tests step.
Run 10 times this issue happened about 3-4 times
I found the exception in DTAExecutionHost.exe log file when loading DLL.
The full log in attached file.
Thank you for any help.
`E, 10504, 18, 2016/06/24, 13:28:24.285, 291767473089, DTAExecutionHost.exe, TAEF Engine Execution: System.IO.FileNotFoundException: Could not load file or assembly 'LogiGear.TestArchitect.TAIntegrationLoader, Version=3.0.50.0, Culture=neutral, PublicKeyToken=12834fd652593218' or one of its dependencies. The system cannot find the file specified.
File name: 'LogiGear.TestArchitect.TAIntegrationLoader, Version=3.0.50.0, Culture=neutral, PublicKeyToken=12834fd652593218'
at System.ModuleHandle.ResolveType(RuntimeModule module, Int32 typeToken, IntPtr* typeInstArgs, Int32 typeInstCount, IntPtr* methodInstArgs, Int32 methodInstCount, ObjectHandleOnStack type)
at System.ModuleHandle.ResolveTypeHandleInternal(RuntimeModule module, Int32 typeToken, RuntimeTypeHandle[] typeInstantiationContext, RuntimeTypeHandle[] methodInstantiationContext)
at System.Reflection.RuntimeModule.ResolveType(Int32 metadataToken, Type[] genericTypeArguments, Type[] genericMethodArguments)
at System.Reflection.CustomAttribute.FilterCustomAttributeRecord(CustomAttributeRecord caRecord, MetadataImport scope, Assembly& lastAptcaOkAssembly, RuntimeModule decoratedModule, MetadataToken decoratedToken, RuntimeType attributeFilterType, Boolean mustBeInheritable, Object[] attributes, IList derivedAttributes, RuntimeType& attributeType, IRuntimeMethodInfo& ctor, Boolean& ctorHasParameters, Boolean& isVarArg)
at System.Reflection.CustomAttribute.IsCustomAttributeDefined(RuntimeModule decoratedModule, Int32 decoratedMetadataToken, RuntimeType attributeFilterType, Int32 attributeCtorToken, Boolean mustBeInheritable)
at System.Reflection.CustomAttribute.IsDefined(RuntimeMethodInfo method, RuntimeType caType, Boolean inherit)
at System.Reflection.RuntimeMethodInfo.IsDefined(Type attributeType, Boolean inherit)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.ReflectHelper.IsAttributeDefined(MemberInfo memberInfo, Type attributeType, Boolean inherit)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.TypeCache.UpdateInfoIfAssemblyInitializeMethod(TestAssemblyInfo assemblyInfo, MethodInfo methodInfo, Type assemblyInitializeType)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.TypeCache.GetAssemblyInfo(Type type)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.TypeCache.CreateClassInfo(Type classType, TestMethod testMethod)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.TypeCache.GetClassInfo(TestMethod testMethod)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.TypeCache.GetTestMethodInfo(TestMethod testMethod, Boolean isDataSource, TestContextImplementation testContext)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.UnitTestRunner.RunInternal(TestMethod testMethod, Boolean isDataDriven, Dictionary`2 runParameters)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.UnitTestRunner.RunSingleTest(String name, String fullClassName, Boolean isAsync, Dictionary`2 runParameters)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.UnitTestRunner.RunSingleTest(String name, String fullClassName, Boolean isAsync, Dictionary`2 runParameters)
at Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MixedModeExecutor.ExecuteTests(IEnumerable`1 tests, IRunContext runContext, ITestExecutionRecorder testExecutionRecorder, UnitTestRunner testRunner, TmiTestRun tmiTestRun)
at Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MixedModeExecutor.ExecuteDurontoTestsInternal(IEnumerable`1 tests, IRunContext runContext, ITestExecutionRecorder testExecutionRecorder, String source, TestRunDirectories runDirectories, TmiTestRun tmiTestRun)
at Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MixedModeExecutor.ExecuteDurontoTests(IEnumerable`1 tests, IRunContext runContext, IFrameworkHandle frameworkHandle, String source, TestRunDirectories runDirectories, TmiTestRun tmiTestRun)
at Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MixedModeExecutor.ExecuteTests(IEnumerable`1 tests, IRunContext runContext, IFrameworkHandle frameworkHandle, TestRunDirectories runDirectories, Boolean isDeploymentDone, String source)
at Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MixedModeExecutor.ExecuteTests(IEnumerable`1 tests, IRunContext runContext, IFrameworkHandle frameworkHandle, TestRunDirectories runDirectories, Boolean isDeploymentDone)
at Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MixedModeExecutor.RunTests(IEnumerable`1 tests, IRunContext runContext, IFrameworkHandle frameworkHandle, TestRunCancellationToken cancellationToken)
at Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MSTestExecutor.RunTests(IEnumerable`1 tests, IRunContext runContext, IFrameworkHandle frameworkHandle)
at WEX.TestExecution.ExecutionPlugin.ExecuteTests(IntPtr context, IntPtr logSessionPtr, IDictionary`2 rockSteadySettings)
at WEX.TestExecution.InteropMethods.ExecuteTests(String[] rockSteadySettings, Int32 rockSteadySettingsSize, IntPtr context, IntPtr logSessionPtr)
[DTAExecutionHost.exe - Log.txt](https://github.com/Microsoft/vsts-tasks/files/331576/DTAExecutionHost.exe.-.Log.txt)
| 1.0 | Sometimes exception loading assembly when running VSO online build in Run Functional Tests step - Hi,
I have a sometime issue when running build on VSO online in the Run Functional Tests step.
Run 10 times this issue happened about 3-4 times
I found the exception in DTAExecutionHost.exe log file when loading DLL.
The full log in attached file.
Thank you for any help.
`E, 10504, 18, 2016/06/24, 13:28:24.285, 291767473089, DTAExecutionHost.exe, TAEF Engine Execution: System.IO.FileNotFoundException: Could not load file or assembly 'LogiGear.TestArchitect.TAIntegrationLoader, Version=3.0.50.0, Culture=neutral, PublicKeyToken=12834fd652593218' or one of its dependencies. The system cannot find the file specified.
File name: 'LogiGear.TestArchitect.TAIntegrationLoader, Version=3.0.50.0, Culture=neutral, PublicKeyToken=12834fd652593218'
at System.ModuleHandle.ResolveType(RuntimeModule module, Int32 typeToken, IntPtr* typeInstArgs, Int32 typeInstCount, IntPtr* methodInstArgs, Int32 methodInstCount, ObjectHandleOnStack type)
at System.ModuleHandle.ResolveTypeHandleInternal(RuntimeModule module, Int32 typeToken, RuntimeTypeHandle[] typeInstantiationContext, RuntimeTypeHandle[] methodInstantiationContext)
at System.Reflection.RuntimeModule.ResolveType(Int32 metadataToken, Type[] genericTypeArguments, Type[] genericMethodArguments)
at System.Reflection.CustomAttribute.FilterCustomAttributeRecord(CustomAttributeRecord caRecord, MetadataImport scope, Assembly& lastAptcaOkAssembly, RuntimeModule decoratedModule, MetadataToken decoratedToken, RuntimeType attributeFilterType, Boolean mustBeInheritable, Object[] attributes, IList derivedAttributes, RuntimeType& attributeType, IRuntimeMethodInfo& ctor, Boolean& ctorHasParameters, Boolean& isVarArg)
at System.Reflection.CustomAttribute.IsCustomAttributeDefined(RuntimeModule decoratedModule, Int32 decoratedMetadataToken, RuntimeType attributeFilterType, Int32 attributeCtorToken, Boolean mustBeInheritable)
at System.Reflection.CustomAttribute.IsDefined(RuntimeMethodInfo method, RuntimeType caType, Boolean inherit)
at System.Reflection.RuntimeMethodInfo.IsDefined(Type attributeType, Boolean inherit)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.ReflectHelper.IsAttributeDefined(MemberInfo memberInfo, Type attributeType, Boolean inherit)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.TypeCache.UpdateInfoIfAssemblyInitializeMethod(TestAssemblyInfo assemblyInfo, MethodInfo methodInfo, Type assemblyInitializeType)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.TypeCache.GetAssemblyInfo(Type type)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.TypeCache.CreateClassInfo(Type classType, TestMethod testMethod)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.TypeCache.GetClassInfo(TestMethod testMethod)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.TypeCache.GetTestMethodInfo(TestMethod testMethod, Boolean isDataSource, TestContextImplementation testContext)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.UnitTestRunner.RunInternal(TestMethod testMethod, Boolean isDataDriven, Dictionary`2 runParameters)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.UnitTestRunner.RunSingleTest(String name, String fullClassName, Boolean isAsync, Dictionary`2 runParameters)
at Microsoft.VisualStudio.TestPlatform.MSTestFramework.UnitTestRunner.RunSingleTest(String name, String fullClassName, Boolean isAsync, Dictionary`2 runParameters)
at Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MixedModeExecutor.ExecuteTests(IEnumerable`1 tests, IRunContext runContext, ITestExecutionRecorder testExecutionRecorder, UnitTestRunner testRunner, TmiTestRun tmiTestRun)
at Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MixedModeExecutor.ExecuteDurontoTestsInternal(IEnumerable`1 tests, IRunContext runContext, ITestExecutionRecorder testExecutionRecorder, String source, TestRunDirectories runDirectories, TmiTestRun tmiTestRun)
at Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MixedModeExecutor.ExecuteDurontoTests(IEnumerable`1 tests, IRunContext runContext, IFrameworkHandle frameworkHandle, String source, TestRunDirectories runDirectories, TmiTestRun tmiTestRun)
at Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MixedModeExecutor.ExecuteTests(IEnumerable`1 tests, IRunContext runContext, IFrameworkHandle frameworkHandle, TestRunDirectories runDirectories, Boolean isDeploymentDone, String source)
at Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MixedModeExecutor.ExecuteTests(IEnumerable`1 tests, IRunContext runContext, IFrameworkHandle frameworkHandle, TestRunDirectories runDirectories, Boolean isDeploymentDone)
at Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MixedModeExecutor.RunTests(IEnumerable`1 tests, IRunContext runContext, IFrameworkHandle frameworkHandle, TestRunCancellationToken cancellationToken)
at Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MSTestExecutor.RunTests(IEnumerable`1 tests, IRunContext runContext, IFrameworkHandle frameworkHandle)
at WEX.TestExecution.ExecutionPlugin.ExecuteTests(IntPtr context, IntPtr logSessionPtr, IDictionary`2 rockSteadySettings)
at WEX.TestExecution.InteropMethods.ExecuteTests(String[] rockSteadySettings, Int32 rockSteadySettingsSize, IntPtr context, IntPtr logSessionPtr)
[DTAExecutionHost.exe - Log.txt](https://github.com/Microsoft/vsts-tasks/files/331576/DTAExecutionHost.exe.-.Log.txt)
| non_priority | sometimes exception loading assembly when running vso online build in run functional tests step hi i have a sometime issue when running build on vso online in the run functional tests step run times this issue happened about times i found the exception in dtaexecutionhost exe log file when loading dll the full log in attached file thank you for any help e dtaexecutionhost exe taef engine execution system io filenotfoundexception could not load file or assembly logigear testarchitect taintegrationloader version culture neutral publickeytoken or one of its dependencies the system cannot find the file specified file name logigear testarchitect taintegrationloader version culture neutral publickeytoken at system modulehandle resolvetype runtimemodule module typetoken intptr typeinstargs typeinstcount intptr methodinstargs methodinstcount objecthandleonstack type at system modulehandle resolvetypehandleinternal runtimemodule module typetoken runtimetypehandle typeinstantiationcontext runtimetypehandle methodinstantiationcontext at system reflection runtimemodule resolvetype metadatatoken type generictypearguments type genericmethodarguments at system reflection customattribute filtercustomattributerecord customattributerecord carecord metadataimport scope assembly lastaptcaokassembly runtimemodule decoratedmodule metadatatoken decoratedtoken runtimetype attributefiltertype boolean mustbeinheritable object attributes ilist derivedattributes runtimetype attributetype iruntimemethodinfo ctor boolean ctorhasparameters boolean isvararg at system reflection customattribute iscustomattributedefined runtimemodule decoratedmodule decoratedmetadatatoken runtimetype attributefiltertype attributectortoken boolean mustbeinheritable at system reflection customattribute isdefined runtimemethodinfo method runtimetype catype boolean inherit at system reflection runtimemethodinfo isdefined type attributetype boolean inherit at microsoft visualstudio testplatform mstestframework reflecthelper isattributedefined memberinfo memberinfo type attributetype boolean inherit at microsoft visualstudio testplatform mstestframework typecache updateinfoifassemblyinitializemethod testassemblyinfo assemblyinfo methodinfo methodinfo type assemblyinitializetype at microsoft visualstudio testplatform mstestframework typecache getassemblyinfo type type at microsoft visualstudio testplatform mstestframework typecache createclassinfo type classtype testmethod testmethod at microsoft visualstudio testplatform mstestframework typecache getclassinfo testmethod testmethod at microsoft visualstudio testplatform mstestframework typecache gettestmethodinfo testmethod testmethod boolean isdatasource testcontextimplementation testcontext at microsoft visualstudio testplatform mstestframework unittestrunner runinternal testmethod testmethod boolean isdatadriven dictionary runparameters at microsoft visualstudio testplatform mstestframework unittestrunner runsingletest string name string fullclassname boolean isasync dictionary runparameters at microsoft visualstudio testplatform mstestframework unittestrunner runsingletest string name string fullclassname boolean isasync dictionary runparameters at microsoft visualstudio testplatform extensions vstestintegration mixedmodeexecutor executetests ienumerable tests iruncontext runcontext itestexecutionrecorder testexecutionrecorder unittestrunner testrunner tmitestrun tmitestrun at microsoft visualstudio testplatform extensions vstestintegration mixedmodeexecutor executedurontotestsinternal ienumerable tests iruncontext runcontext itestexecutionrecorder testexecutionrecorder string source testrundirectories rundirectories tmitestrun tmitestrun at microsoft visualstudio testplatform extensions vstestintegration mixedmodeexecutor executedurontotests ienumerable tests iruncontext runcontext iframeworkhandle frameworkhandle string source testrundirectories rundirectories tmitestrun tmitestrun at microsoft visualstudio testplatform extensions vstestintegration mixedmodeexecutor executetests ienumerable tests iruncontext runcontext iframeworkhandle frameworkhandle testrundirectories rundirectories boolean isdeploymentdone string source at microsoft visualstudio testplatform extensions vstestintegration mixedmodeexecutor executetests ienumerable tests iruncontext runcontext iframeworkhandle frameworkhandle testrundirectories rundirectories boolean isdeploymentdone at microsoft visualstudio testplatform extensions vstestintegration mixedmodeexecutor runtests ienumerable tests iruncontext runcontext iframeworkhandle frameworkhandle testruncancellationtoken cancellationtoken at microsoft visualstudio testplatform extensions vstestintegration mstestexecutor runtests ienumerable tests iruncontext runcontext iframeworkhandle frameworkhandle at wex testexecution executionplugin executetests intptr context intptr logsessionptr idictionary rocksteadysettings at wex testexecution interopmethods executetests string rocksteadysettings rocksteadysettingssize intptr context intptr logsessionptr | 0 |
233,475 | 18,989,590,284 | IssuesEvent | 2021-11-22 04:38:38 | RasaHQ/rasa | https://api.github.com/repos/RasaHQ/rasa | opened | Scheduled Model Regression Test Failed | type:bug :bug: tool:model-regression-tests | *This PR is automatically created by the Scheduled Model Regression Test workflow. Checkout the Github Action Run [here](https://github.com/RasaHQ/rasa/actions/runs/1487942302).* <br> --- <br> **Description of Problem:** <br> Scheduled Model Regression Test failed. <br> **Configuration**: `Rules + AugMemo` <br> **Dataset**: `Sara` | 1.0 | Scheduled Model Regression Test Failed - *This PR is automatically created by the Scheduled Model Regression Test workflow. Checkout the Github Action Run [here](https://github.com/RasaHQ/rasa/actions/runs/1487942302).* <br> --- <br> **Description of Problem:** <br> Scheduled Model Regression Test failed. <br> **Configuration**: `Rules + AugMemo` <br> **Dataset**: `Sara` | non_priority | scheduled model regression test failed this pr is automatically created by the scheduled model regression test workflow checkout the github action run description of problem scheduled model regression test failed configuration rules augmemo dataset sara | 0 |
297,713 | 25,758,208,549 | IssuesEvent | 2022-12-08 18:06:20 | CSC207-2022F-UofT/course-project-team-tree-dog | https://api.github.com/repos/CSC207-2022F-UofT/course-project-team-tree-dog | closed | [Unit Test] Thread Lock Architecture | Test | - Write a test suite which tests all use cases as they interact with each other! Start multiple use case threads, think through the possible expected outcomes that can occur depending on the order in which each thread catches locks first (wins the lock race), add randomized sleeps and thread start order to ensure that every scenario can occur, and assert that only one of the expected scenarios occur.
- Set `fairness = true` for all Reentrant locks created across the project. this ensures that locks will give priority to threads that have been waiting the longest, ensuring that every thread gets their chance to take the lock and use the resource.
- See Bracket diagram in Conventions doc. There is a potential rare deadlock where JPL acquires its own "lock" and SP acquires "pool" and "game". Now JPL is waiting on "pool" and SP is waiting on "lock". This occurrence is very rare since each JPL thread has its own lock, so the "lock" would have to match for the same JPL for the deadlock to occur, and of course, the race conditions have to have a specific outcome. Still, this is a possible issue and should be fixed. | 1.0 | [Unit Test] Thread Lock Architecture - - Write a test suite which tests all use cases as they interact with each other! Start multiple use case threads, think through the possible expected outcomes that can occur depending on the order in which each thread catches locks first (wins the lock race), add randomized sleeps and thread start order to ensure that every scenario can occur, and assert that only one of the expected scenarios occur.
- Set `fairness = true` for all Reentrant locks created across the project. this ensures that locks will give priority to threads that have been waiting the longest, ensuring that every thread gets their chance to take the lock and use the resource.
- See Bracket diagram in Conventions doc. There is a potential rare deadlock where JPL acquires its own "lock" and SP acquires "pool" and "game". Now JPL is waiting on "pool" and SP is waiting on "lock". This occurrence is very rare since each JPL thread has its own lock, so the "lock" would have to match for the same JPL for the deadlock to occur, and of course, the race conditions have to have a specific outcome. Still, this is a possible issue and should be fixed. | non_priority | thread lock architecture write a test suite which tests all use cases as they interact with each other start multiple use case threads think through the possible expected outcomes that can occur depending on the order in which each thread catches locks first wins the lock race add randomized sleeps and thread start order to ensure that every scenario can occur and assert that only one of the expected scenarios occur set fairness true for all reentrant locks created across the project this ensures that locks will give priority to threads that have been waiting the longest ensuring that every thread gets their chance to take the lock and use the resource see bracket diagram in conventions doc there is a potential rare deadlock where jpl acquires its own lock and sp acquires pool and game now jpl is waiting on pool and sp is waiting on lock this occurrence is very rare since each jpl thread has its own lock so the lock would have to match for the same jpl for the deadlock to occur and of course the race conditions have to have a specific outcome still this is a possible issue and should be fixed | 0 |
434,054 | 30,441,594,366 | IssuesEvent | 2023-07-15 05:48:35 | sinProject-Inc/talk | https://api.github.com/repos/sinProject-Inc/talk | closed | Docs: Fix English | documentation | # Tasks
- [ ]
# Writing the Issue
- [x] Write each task for this issue using checkboxes
- [x] Write all verbal instructions as tasks
# Before Working on the Issue
- [x] Assign yourself
- [x] Share your screen on Discord
- [x] Write which issue you are starting on Slack
- [x] Git: Fetch the latest main
- [x] Git: Create a branch with the name of the issue
# Pre-PR Checks
- [x] Insure that changes include only what is necessary for this PR
- [x] Implement necessary Unit tests
- [x] Implement necessary E2E tests
- [x] Perform functionality checks
| 1.0 | Docs: Fix English - # Tasks
- [ ]
# Writing the Issue
- [x] Write each task for this issue using checkboxes
- [x] Write all verbal instructions as tasks
# Before Working on the Issue
- [x] Assign yourself
- [x] Share your screen on Discord
- [x] Write which issue you are starting on Slack
- [x] Git: Fetch the latest main
- [x] Git: Create a branch with the name of the issue
# Pre-PR Checks
- [x] Insure that changes include only what is necessary for this PR
- [x] Implement necessary Unit tests
- [x] Implement necessary E2E tests
- [x] Perform functionality checks
| non_priority | docs fix english tasks writing the issue write each task for this issue using checkboxes write all verbal instructions as tasks before working on the issue assign yourself share your screen on discord write which issue you are starting on slack git fetch the latest main git create a branch with the name of the issue pre pr checks insure that changes include only what is necessary for this pr implement necessary unit tests implement necessary tests perform functionality checks | 0 |
224,760 | 24,785,778,793 | IssuesEvent | 2022-10-24 09:38:26 | lukebrogan-mend/easybuggy | https://api.github.com/repos/lukebrogan-mend/easybuggy | closed | CVE-2017-14735 (Medium) detected in antisamy-1.5.3.jar - autoclosed | security vulnerability | ## CVE-2017-14735 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>antisamy-1.5.3.jar</b></p></summary>
<p>The OWASP AntiSamy project is a collection of APIs for safely allowing users to supply their own HTML
and CSS without exposing the site to XSS vulnerabilities.</p>
<p>Library home page: <a href="http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project">http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/owasp/antisamy/antisamy/1.5.3/antisamy-1.5.3.jar</p>
<p>
Dependency Hierarchy:
- esapi-2.1.0.1.jar (Root Library)
- :x: **antisamy-1.5.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/lukebrogan-mend/easybuggy/commit/8425a65d16fef03a6c3a407c7a480ab44726e8a5">8425a65d16fef03a6c3a407c7a480ab44726e8a5</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>
OWASP AntiSamy before 1.5.7 allows XSS via HTML5 entities, as demonstrated by use of : to construct a javascript: URL.
<p>Publish Date: 2017-09-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-14735>CVE-2017-14735</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14735">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14735</a></p>
<p>Release Date: 2017-09-25</p>
<p>Fix Resolution (org.owasp.antisamy:antisamy): 1.5.7</p>
<p>Direct dependency fix Resolution (org.owasp.esapi:esapi): 2.2.0.0</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue | True | CVE-2017-14735 (Medium) detected in antisamy-1.5.3.jar - autoclosed - ## CVE-2017-14735 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>antisamy-1.5.3.jar</b></p></summary>
<p>The OWASP AntiSamy project is a collection of APIs for safely allowing users to supply their own HTML
and CSS without exposing the site to XSS vulnerabilities.</p>
<p>Library home page: <a href="http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project">http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/owasp/antisamy/antisamy/1.5.3/antisamy-1.5.3.jar</p>
<p>
Dependency Hierarchy:
- esapi-2.1.0.1.jar (Root Library)
- :x: **antisamy-1.5.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/lukebrogan-mend/easybuggy/commit/8425a65d16fef03a6c3a407c7a480ab44726e8a5">8425a65d16fef03a6c3a407c7a480ab44726e8a5</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>
OWASP AntiSamy before 1.5.7 allows XSS via HTML5 entities, as demonstrated by use of : to construct a javascript: URL.
<p>Publish Date: 2017-09-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-14735>CVE-2017-14735</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14735">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14735</a></p>
<p>Release Date: 2017-09-25</p>
<p>Fix Resolution (org.owasp.antisamy:antisamy): 1.5.7</p>
<p>Direct dependency fix Resolution (org.owasp.esapi:esapi): 2.2.0.0</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue | non_priority | cve medium detected in antisamy jar autoclosed cve medium severity vulnerability vulnerable library antisamy jar the owasp antisamy project is a collection of apis for safely allowing users to supply their own html and css without exposing the site to xss vulnerabilities library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org owasp antisamy antisamy antisamy jar dependency hierarchy esapi jar root library x antisamy jar vulnerable library found in head commit a href found in base branch master vulnerability details owasp antisamy before allows xss via entities as demonstrated by use of colon to construct a javascript url publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org owasp antisamy antisamy direct dependency fix resolution org owasp esapi esapi rescue worker helmet automatic remediation is available for this issue | 0 |
275,504 | 23,919,167,476 | IssuesEvent | 2022-09-09 15:12:47 | blockframes/blockframes | https://api.github.com/repos/blockframes/blockframes | closed | [Feat]: Add password reset email workflow E2E test for Financier App | TODO Dev - Test / Quality Assurance July clean up | Add tests to check password reset by email scenario.
To start with we will use the Financier App and then introduce this for other apps.
| 1.0 | [Feat]: Add password reset email workflow E2E test for Financier App - Add tests to check password reset by email scenario.
To start with we will use the Financier App and then introduce this for other apps.
| non_priority | add password reset email workflow test for financier app add tests to check password reset by email scenario to start with we will use the financier app and then introduce this for other apps | 0 |
273,654 | 23,774,682,519 | IssuesEvent | 2022-09-01 19:41:02 | appium/appium | https://api.github.com/repos/appium/appium | closed | Implement '-ios class chain' on all clients | Enhancement iOS XCUITest P1 | Currently, not all appium clients support `-ios class chain` selectors. In light of the performance troubles we're having with XPath on XCUITest, I think it's important that we add these to our client libraries.
Acceptance Criteria
* [x] WebDriverIO (http://webdriver.io/guide/usage/selectors.html#Class-Name)
* [ ] WD
* [ ] PHP
* [x] .NET
* [x] Update `appium-desktop` recorder to use class chain
(Ruby, Java, Python are done already) | 1.0 | Implement '-ios class chain' on all clients - Currently, not all appium clients support `-ios class chain` selectors. In light of the performance troubles we're having with XPath on XCUITest, I think it's important that we add these to our client libraries.
Acceptance Criteria
* [x] WebDriverIO (http://webdriver.io/guide/usage/selectors.html#Class-Name)
* [ ] WD
* [ ] PHP
* [x] .NET
* [x] Update `appium-desktop` recorder to use class chain
(Ruby, Java, Python are done already) | non_priority | implement ios class chain on all clients currently not all appium clients support ios class chain selectors in light of the performance troubles we re having with xpath on xcuitest i think it s important that we add these to our client libraries acceptance criteria webdriverio wd php net update appium desktop recorder to use class chain ruby java python are done already | 0 |
329,977 | 24,241,238,969 | IssuesEvent | 2022-09-27 06:53:10 | Sarmash/FastAPI-solution | https://api.github.com/repos/Sarmash/FastAPI-solution | closed | Сделать сервис для страницы фильма. | documentation | 1. Полная информация по фильму. Эндпоинт: /api/v1/films/<uuid:UUID>/
2. Похожие фильмы. Показать фильмы того же жанра. Эндпоинт: /api/v1/films?... | 1.0 | Сделать сервис для страницы фильма. - 1. Полная информация по фильму. Эндпоинт: /api/v1/films/<uuid:UUID>/
2. Похожие фильмы. Показать фильмы того же жанра. Эндпоинт: /api/v1/films?... | non_priority | сделать сервис для страницы фильма полная информация по фильму эндпоинт api films похожие фильмы показать фильмы того же жанра эндпоинт api films | 0 |
281,440 | 21,315,404,950 | IssuesEvent | 2022-04-16 07:20:20 | brian16600/pe | https://api.github.com/repos/brian16600/pe | opened | Inconsistency with "the" prefix in front of Mr Agent in UG | severity.VeryLow type.DocumentationBug | These examples in 3.2 do not have "the" in front of Mr Agent
Whereas in 3.1, there is "the" prefix in front.
<!--session: 1650087604666-a1d11fe1-d251-4419-8612-b6b9b1cbcb7c-->
<!--Version: Web v3.4.2--> | 1.0 | Inconsistency with "the" prefix in front of Mr Agent in UG - These examples in 3.2 do not have "the" in front of Mr Agent
Whereas in 3.1, there is "the" prefix in front.
<!--session: 1650087604666-a1d11fe1-d251-4419-8612-b6b9b1cbcb7c-->
<!--Version: Web v3.4.2--> | non_priority | inconsistency with the prefix in front of mr agent in ug these examples in do not have the in front of mr agent whereas in there is the prefix in front | 0 |
214,097 | 16,546,978,305 | IssuesEvent | 2021-05-28 02:02:57 | supabase/ui | https://api.github.com/repos/supabase/ui | closed | Supabase UI Auth example (readme) - doesn't work as is | documentation | # Improve documentation
## Link
https://github.com/supabase/ui/blob/develop/README.md
## Describe the problem
The Auth UI example doesn't work as is. Specifically, `supabaseClient` needs to be passed in to the `Auth` component. Also the `Container` component is not actually used in the example.
```
export default function Home() {
return (
<Auth.UserContextProvider supabaseClient={supabase}>
<Auth providers={['facebook', 'github']}/>
</Auth.UserContextProvider>
);
};
```
## Describe the improvement
This is what worked for me:
```
export default function Home() {
return (
<Auth.UserContextProvider supabaseClient={supabase}>
<Container supabaseClient={supabase}>
<Auth providers={['facebook', 'github']} supabaseClient={supabase}/>
</Container>
</Auth.UserContextProvider>
);
};
```
## Additional context
Add any other context or screenshots that help clarify your question. | 1.0 | Supabase UI Auth example (readme) - doesn't work as is - # Improve documentation
## Link
https://github.com/supabase/ui/blob/develop/README.md
## Describe the problem
The Auth UI example doesn't work as is. Specifically, `supabaseClient` needs to be passed in to the `Auth` component. Also the `Container` component is not actually used in the example.
```
export default function Home() {
return (
<Auth.UserContextProvider supabaseClient={supabase}>
<Auth providers={['facebook', 'github']}/>
</Auth.UserContextProvider>
);
};
```
## Describe the improvement
This is what worked for me:
```
export default function Home() {
return (
<Auth.UserContextProvider supabaseClient={supabase}>
<Container supabaseClient={supabase}>
<Auth providers={['facebook', 'github']} supabaseClient={supabase}/>
</Container>
</Auth.UserContextProvider>
);
};
```
## Additional context
Add any other context or screenshots that help clarify your question. | non_priority | supabase ui auth example readme doesn t work as is improve documentation link describe the problem the auth ui example doesn t work as is specifically supabaseclient needs to be passed in to the auth component also the container component is not actually used in the example export default function home return describe the improvement this is what worked for me export default function home return additional context add any other context or screenshots that help clarify your question | 0 |
67,608 | 12,978,150,139 | IssuesEvent | 2020-07-21 22:08:43 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | [mono][Browser] Interpreter doesn't fully support UnmanagedCallersOnly | arch-wasm area-Codegen-Interpreter-mono | Currently, the only way to pass a managed callback to a pinvoke in Mono-Wasm-Interp is to use `IntPtr` + `Marshal.GetFunctionPointerForDelegate` + `MonoPinvokeCallbackAttribute`.
/cc @vargaz
I will use link to this issue for workarounds. | 1.0 | [mono][Browser] Interpreter doesn't fully support UnmanagedCallersOnly - Currently, the only way to pass a managed callback to a pinvoke in Mono-Wasm-Interp is to use `IntPtr` + `Marshal.GetFunctionPointerForDelegate` + `MonoPinvokeCallbackAttribute`.
/cc @vargaz
I will use link to this issue for workarounds. | non_priority | interpreter doesn t fully support unmanagedcallersonly currently the only way to pass a managed callback to a pinvoke in mono wasm interp is to use intptr marshal getfunctionpointerfordelegate monopinvokecallbackattribute cc vargaz i will use link to this issue for workarounds | 0 |
77,367 | 15,528,260,300 | IssuesEvent | 2021-03-13 10:06:52 | jonathan-wiens/hwr-kurs19a-g2 | https://api.github.com/repos/jonathan-wiens/hwr-kurs19a-g2 | opened | CVE-2018-19797 (Medium) detected in opennmsopennms-source-26.0.0-1, node-sass-4.14.1.tgz | security vulnerability | ## CVE-2018-19797 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>opennmsopennms-source-26.0.0-1</b>, <b>node-sass-4.14.1.tgz</b></p></summary>
<p>
<details><summary><b>node-sass-4.14.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz</a></p>
<p>Path to dependency file: hwr-kurs19a-g2/package.json</p>
<p>Path to vulnerable library: hwr-kurs19a-g2/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.14.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/jonathan-wiens/hwr-kurs19a-g2/commit/e8dc35c22b4d589d2941dc86cb947a0137795c70">e8dc35c22b4d589d2941dc86cb947a0137795c70</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>
In LibSass 3.5.5, a NULL Pointer Dereference in the function Sass::Selector_List::populate_extends in SharedPtr.hpp (used by ast.cpp and ast_selectors.cpp) may cause a Denial of Service (application crash) via a crafted sass input file.
<p>Publish Date: 2018-12-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19797>CVE-2018-19797</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19797">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19797</a></p>
<p>Release Date: 2018-12-03</p>
<p>Fix Resolution: libsass-3.6.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-19797 (Medium) detected in opennmsopennms-source-26.0.0-1, node-sass-4.14.1.tgz - ## CVE-2018-19797 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>opennmsopennms-source-26.0.0-1</b>, <b>node-sass-4.14.1.tgz</b></p></summary>
<p>
<details><summary><b>node-sass-4.14.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz</a></p>
<p>Path to dependency file: hwr-kurs19a-g2/package.json</p>
<p>Path to vulnerable library: hwr-kurs19a-g2/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.14.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/jonathan-wiens/hwr-kurs19a-g2/commit/e8dc35c22b4d589d2941dc86cb947a0137795c70">e8dc35c22b4d589d2941dc86cb947a0137795c70</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>
In LibSass 3.5.5, a NULL Pointer Dereference in the function Sass::Selector_List::populate_extends in SharedPtr.hpp (used by ast.cpp and ast_selectors.cpp) may cause a Denial of Service (application crash) via a crafted sass input file.
<p>Publish Date: 2018-12-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19797>CVE-2018-19797</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19797">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19797</a></p>
<p>Release Date: 2018-12-03</p>
<p>Fix Resolution: libsass-3.6.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in opennmsopennms source node sass tgz cve medium severity vulnerability vulnerable libraries opennmsopennms source node sass tgz node sass tgz wrapper around libsass library home page a href path to dependency file hwr package json path to vulnerable library hwr node modules node sass package json dependency hierarchy x node sass tgz vulnerable library found in head commit a href found in base branch master vulnerability details in libsass a null pointer dereference in the function sass selector list populate extends in sharedptr hpp used by ast cpp and ast selectors cpp may cause a denial of service application crash via a crafted sass input file publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution libsass step up your open source security game with whitesource | 0 |
79,215 | 7,698,629,818 | IssuesEvent | 2018-05-19 01:05:49 | VictorArnaud/sdcurve | https://api.github.com/repos/VictorArnaud/sdcurve | closed | Testes do microserviço | atenção teste | ### Motivação
Eu como usuário, gostaria de utilizar o microserviço totalmente testado.
### Critérios de aceitação
- [x] Teste para curva de crescimento (altura)
- [x] Teste para curva de crescimento (peso)
- [x] Teste para curva de crescimento (perímetro cefálico)
- [x] Teste para curva de crescimento (IMC)
| 1.0 | Testes do microserviço - ### Motivação
Eu como usuário, gostaria de utilizar o microserviço totalmente testado.
### Critérios de aceitação
- [x] Teste para curva de crescimento (altura)
- [x] Teste para curva de crescimento (peso)
- [x] Teste para curva de crescimento (perímetro cefálico)
- [x] Teste para curva de crescimento (IMC)
| non_priority | testes do microserviço motivação eu como usuário gostaria de utilizar o microserviço totalmente testado critérios de aceitação teste para curva de crescimento altura teste para curva de crescimento peso teste para curva de crescimento perímetro cefálico teste para curva de crescimento imc | 0 |
22,778 | 20,144,994,464 | IssuesEvent | 2022-02-09 06:07:35 | mosaicml/composer | https://api.github.com/repos/mosaicml/composer | closed | Script to run the tests locally such that they all pass | enhancement usability/API | ## Motivation
If a user downloads composer and wants to either:
1. make sure everything installed okay, or
2. try modifying it without breaking everything (e.g., to add a new method),
it's really helpful to be able to run the full test suite and know whether failures are because of your code. I know this is helpful (at least for case 2) based on my experience developing methods.
Also, having a command to run the tests post-install is just a pretty common element of installation documentation.
## [Optional] Implementation
Below is equivalent to what I run to get everything passing locally. I say "equivalent" because I don't setup the environment and reinstall pillow-simd regularly; I just run the last command.
The sketchy part here is getting pillow-simd installed so that test_pillow_simd passes. Might be more robust to just have it skip that test.
```
# this block is so that test_pillow_simd passes
pip uninstall pillow
pip uninstall pillow-simd
pip install pillow-simd # needs certain deps; might choke
# this block is to avoid a few torch.distributed failures in test_checkpoint, test_ddp, and a couple other files
export NODE_RANK=0
export LOCAL_RANK=0
export LOCAL_WORLD_SIZE=1
# actual testing command
pytest -s --tb=short --disable-pytest-warnings --test_duration all tests/
```
## Additional context
`bash scripts/test.sh` doesn't currently allow the desired behavior :
```
~/code/composer $ bash scripts/test.sh
+ JUNIT_PREFIX=build/output/composer
++ dirname build/output/composer
+ mkdir -p build/output
+ python -m composer.cli.launcher -n 1 --master_port 26000 -m coverage run -m pytest --junitxml build/output/composer.n1.junit.xml
/Users/davis/.pyenv/versions/3.8.6/bin/python: No module named coverage
Waiting up to 30 seconds for all training processes to terminate...
Process 1566 excited with code 1
ERROR:__main__:Subprocess 1566 exited with code 1
``` | True | Script to run the tests locally such that they all pass - ## Motivation
If a user downloads composer and wants to either:
1. make sure everything installed okay, or
2. try modifying it without breaking everything (e.g., to add a new method),
it's really helpful to be able to run the full test suite and know whether failures are because of your code. I know this is helpful (at least for case 2) based on my experience developing methods.
Also, having a command to run the tests post-install is just a pretty common element of installation documentation.
## [Optional] Implementation
Below is equivalent to what I run to get everything passing locally. I say "equivalent" because I don't setup the environment and reinstall pillow-simd regularly; I just run the last command.
The sketchy part here is getting pillow-simd installed so that test_pillow_simd passes. Might be more robust to just have it skip that test.
```
# this block is so that test_pillow_simd passes
pip uninstall pillow
pip uninstall pillow-simd
pip install pillow-simd # needs certain deps; might choke
# this block is to avoid a few torch.distributed failures in test_checkpoint, test_ddp, and a couple other files
export NODE_RANK=0
export LOCAL_RANK=0
export LOCAL_WORLD_SIZE=1
# actual testing command
pytest -s --tb=short --disable-pytest-warnings --test_duration all tests/
```
## Additional context
`bash scripts/test.sh` doesn't currently allow the desired behavior :
```
~/code/composer $ bash scripts/test.sh
+ JUNIT_PREFIX=build/output/composer
++ dirname build/output/composer
+ mkdir -p build/output
+ python -m composer.cli.launcher -n 1 --master_port 26000 -m coverage run -m pytest --junitxml build/output/composer.n1.junit.xml
/Users/davis/.pyenv/versions/3.8.6/bin/python: No module named coverage
Waiting up to 30 seconds for all training processes to terminate...
Process 1566 excited with code 1
ERROR:__main__:Subprocess 1566 exited with code 1
``` | non_priority | script to run the tests locally such that they all pass motivation if a user downloads composer and wants to either make sure everything installed okay or try modifying it without breaking everything e g to add a new method it s really helpful to be able to run the full test suite and know whether failures are because of your code i know this is helpful at least for case based on my experience developing methods also having a command to run the tests post install is just a pretty common element of installation documentation implementation below is equivalent to what i run to get everything passing locally i say equivalent because i don t setup the environment and reinstall pillow simd regularly i just run the last command the sketchy part here is getting pillow simd installed so that test pillow simd passes might be more robust to just have it skip that test this block is so that test pillow simd passes pip uninstall pillow pip uninstall pillow simd pip install pillow simd needs certain deps might choke this block is to avoid a few torch distributed failures in test checkpoint test ddp and a couple other files export node rank export local rank export local world size actual testing command pytest s tb short disable pytest warnings test duration all tests additional context bash scripts test sh doesn t currently allow the desired behavior code composer bash scripts test sh junit prefix build output composer dirname build output composer mkdir p build output python m composer cli launcher n master port m coverage run m pytest junitxml build output composer junit xml users davis pyenv versions bin python no module named coverage waiting up to seconds for all training processes to terminate process excited with code error main subprocess exited with code | 0 |
250,562 | 21,315,268,131 | IssuesEvent | 2022-04-16 06:49:59 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | roachtest: clearrange/checks=true failed | C-test-failure O-robot O-roachtest branch-master release-blocker | roachtest.clearrange/checks=true [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=4907635&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=4907635&tab=artifacts#/clearrange/checks=true) on master @ [771432d1099e516dbc11827c5458886c176e73e3](https://github.com/cockroachdb/cockroach/commits/771432d1099e516dbc11827c5458886c176e73e3):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /artifacts/clearrange/checks=true/run_1
cluster.go:1928,clearrange.go:70,clearrange.go:39,test_runner.go:875: output in run_062106.929773513_n1_cockroach_workload_fixtures_import_bank: ./cockroach workload fixtures import bank --payload-bytes=10240 --ranges=10 --rows=65104166 --seed=4 --db=bigbank returned: COMMAND_PROBLEM: exit status 1
(1) attached stack trace
-- stack trace:
| main.(*clusterImpl).RunE
| main/pkg/cmd/roachtest/cluster.go:1962
| main.(*clusterImpl).Run
| main/pkg/cmd/roachtest/cluster.go:1926
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.runClearRange
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/clearrange.go:70
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerClearRange.func1
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/clearrange.go:39
| main.(*testRunner).runTest.func2
| main/pkg/cmd/roachtest/test_runner.go:875
| runtime.goexit
| GOROOT/src/runtime/asm_amd64.s:1581
Wraps: (2) output in run_062106.929773513_n1_cockroach_workload_fixtures_import_bank
Wraps: (3) ./cockroach workload fixtures import bank --payload-bytes=10240 --ranges=10 --rows=65104166 --seed=4 --db=bigbank returned
| stderr:
| I220416 06:21:07.829453 1 ccl/workloadccl/fixture.go:318 [-] 1 starting import of 1 tables
| Error: importing fixture: importing table bank: pq: reverting execution from '2022-04-16 06:38:11.736056' to '2022-04-16 06:38:13.985624' on 1 failed: replica unavailable: (n1,s1):1 unable to serve request to r6:/Table/{SystemConfigSpan/Start-11} [(n1,s1):1, (n3,s3):2, (n2,s2):3, (n5,s5):4, (n4,s4):5, next=6, gen=8]: lost quorum (down: (n2,s2):3,(n5,s5):4,(n4,s4):5); closed timestamp: 1650091013.405426990,0 (2022-04-16 06:36:53); raft status: {"id":"1","term":8,"vote":"5","commit":77,"lead":"0","raftState":"StatePreCandidate","applied":77,"progress":{},"leadtransferee":"0"}: have been waiting 60.60s for slow proposal RequestLease [/Table/SystemConfigSpan/Start,/Min)
|
| stdout:
Wraps: (4) COMMAND_PROBLEM
Wraps: (5) Node 1. Command with error:
| ``````
| ./cockroach workload fixtures import bank --payload-bytes=10240 --ranges=10 --rows=65104166 --seed=4 --db=bigbank
| ``````
Wraps: (6) exit status 1
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *cluster.WithCommandDetails (4) errors.Cmd (5) *hintdetail.withDetail (6) *exec.ExitError
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/storage
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*clearrange/checks=true.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 2.0 | roachtest: clearrange/checks=true failed - roachtest.clearrange/checks=true [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=4907635&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=4907635&tab=artifacts#/clearrange/checks=true) on master @ [771432d1099e516dbc11827c5458886c176e73e3](https://github.com/cockroachdb/cockroach/commits/771432d1099e516dbc11827c5458886c176e73e3):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /artifacts/clearrange/checks=true/run_1
cluster.go:1928,clearrange.go:70,clearrange.go:39,test_runner.go:875: output in run_062106.929773513_n1_cockroach_workload_fixtures_import_bank: ./cockroach workload fixtures import bank --payload-bytes=10240 --ranges=10 --rows=65104166 --seed=4 --db=bigbank returned: COMMAND_PROBLEM: exit status 1
(1) attached stack trace
-- stack trace:
| main.(*clusterImpl).RunE
| main/pkg/cmd/roachtest/cluster.go:1962
| main.(*clusterImpl).Run
| main/pkg/cmd/roachtest/cluster.go:1926
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.runClearRange
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/clearrange.go:70
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerClearRange.func1
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/clearrange.go:39
| main.(*testRunner).runTest.func2
| main/pkg/cmd/roachtest/test_runner.go:875
| runtime.goexit
| GOROOT/src/runtime/asm_amd64.s:1581
Wraps: (2) output in run_062106.929773513_n1_cockroach_workload_fixtures_import_bank
Wraps: (3) ./cockroach workload fixtures import bank --payload-bytes=10240 --ranges=10 --rows=65104166 --seed=4 --db=bigbank returned
| stderr:
| I220416 06:21:07.829453 1 ccl/workloadccl/fixture.go:318 [-] 1 starting import of 1 tables
| Error: importing fixture: importing table bank: pq: reverting execution from '2022-04-16 06:38:11.736056' to '2022-04-16 06:38:13.985624' on 1 failed: replica unavailable: (n1,s1):1 unable to serve request to r6:/Table/{SystemConfigSpan/Start-11} [(n1,s1):1, (n3,s3):2, (n2,s2):3, (n5,s5):4, (n4,s4):5, next=6, gen=8]: lost quorum (down: (n2,s2):3,(n5,s5):4,(n4,s4):5); closed timestamp: 1650091013.405426990,0 (2022-04-16 06:36:53); raft status: {"id":"1","term":8,"vote":"5","commit":77,"lead":"0","raftState":"StatePreCandidate","applied":77,"progress":{},"leadtransferee":"0"}: have been waiting 60.60s for slow proposal RequestLease [/Table/SystemConfigSpan/Start,/Min)
|
| stdout:
Wraps: (4) COMMAND_PROBLEM
Wraps: (5) Node 1. Command with error:
| ``````
| ./cockroach workload fixtures import bank --payload-bytes=10240 --ranges=10 --rows=65104166 --seed=4 --db=bigbank
| ``````
Wraps: (6) exit status 1
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *cluster.WithCommandDetails (4) errors.Cmd (5) *hintdetail.withDetail (6) *exec.ExitError
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/storage
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*clearrange/checks=true.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| non_priority | roachtest clearrange checks true failed roachtest clearrange checks true with on master the test failed on branch master cloud gce test artifacts and logs in artifacts clearrange checks true run cluster go clearrange go clearrange go test runner go output in run cockroach workload fixtures import bank cockroach workload fixtures import bank payload bytes ranges rows seed db bigbank returned command problem exit status attached stack trace stack trace main clusterimpl rune main pkg cmd roachtest cluster go main clusterimpl run main pkg cmd roachtest cluster go github com cockroachdb cockroach pkg cmd roachtest tests runclearrange github com cockroachdb cockroach pkg cmd roachtest tests clearrange go github com cockroachdb cockroach pkg cmd roachtest tests registerclearrange github com cockroachdb cockroach pkg cmd roachtest tests clearrange go main testrunner runtest main pkg cmd roachtest test runner go runtime goexit goroot src runtime asm s wraps output in run cockroach workload fixtures import bank wraps cockroach workload fixtures import bank payload bytes ranges rows seed db bigbank returned stderr ccl workloadccl fixture go starting import of tables error importing fixture importing table bank pq reverting execution from to on failed replica unavailable unable to serve request to table systemconfigspan start lost quorum down closed timestamp raft status id term vote commit lead raftstate stateprecandidate applied progress leadtransferee have been waiting for slow proposal requestlease table systemconfigspan start min stdout wraps command problem wraps node command with error cockroach workload fixtures import bank payload bytes ranges rows seed db bigbank wraps exit status error types withstack withstack errutil withprefix cluster withcommanddetails errors cmd hintdetail withdetail exec exiterror help see see cc cockroachdb storage | 0 |
145,383 | 22,678,770,197 | IssuesEvent | 2022-07-04 08:00:25 | microsoft/AdaptiveCards | https://api.github.com/repos/microsoft/AdaptiveCards | opened | [Designer]Bug 35714425: [V1.0-> Scenarios - FoodOrder.json]: "Your registration is almost complete" is not defined as a heading on 'FoodOrder.Json' card. | Bug Area-Designer | ### Problem Description
[Bug 35714425](https://microsoft.visualstudio.com/OS/_workitems/edit/35714425): [V1.0-> Scenarios - FoodOrder.json]: "Your registration is almost complete" is not defined as a heading on 'FoodOrder.Json' card.
Test Environment:
Device: iPhone x
iOS: 14.7.1
Application: Adaptive Cards
App Version: Version 1.0 (2.3.1-beta.20210823.1)
Screen Reader: Voice Over
Repro Steps:
1. Launch Adaptive Cards iOS application.
2. Home screen will appear.
3. Navigate to "V1.0" control and select it.
4. Navigate on "V1.0" screen and select "Scenarios" button.
5. 'Scenario' screen will appear.
6. Navigate to "FoodOrder.json" control and select it.
7. Navigate the 'FoodOrder.json' screen and enable Voiceover for the ease of access.
8. Navigate till 'Your registration is almost complete' and hear screen reader narration.
Actual Result:
"Your registration is almost complete" is not defined as a heading on 'FoodOrder.Json' card. Screen reader is only announcing as, "Your registration is almost complete text field double tap to edit Use the rotor to access Misspelt Words".
Expected Result:
"Your registration is almost complete" should be defined under a heading. Screen reader should announce as, "Your registration is almost complete heading Use the rotor to access headings".
Note:
Same issue is also repro for 'Malt and Vine' text on FoodOrder.json card. (Please refer attachment)
v1.0 -Element -AdaptiveCard.json- Issue is repro for 'Publish Adaptive Card Schema'. (Please refer attachment)
v1.0-Element-ColumnSet.Spacing.json- issue is repro for 'ColumnSet Spacing'. (Please refer attachment)
v1.0-Element-Container.Spacing.json- issue is repro for 'Container Spacing'.
Issue is repro throughout application. Headings is not defined as heading.
User Experience:
It will be confusing & difficult for the users if Heading will not be defined inside the adaptive card.
"Have feedback to share on Bugs ? Please help fill [Trusted Tester Bug Feedback (office.com)](https://nam06.safelinks.protection.outlook.com/?url=https://forms.office.com/pages/responsepage.aspx?id%3Dv4j5cvGGr0GRqy180BHbR5dUqGQgJ9lItv-jqY8F09lURVdYTENIRkY2UzlCR0NKV1E2VUE5OVpDVy4u&data=04%7c01%7cv-apoorva%40microsoft.com%7c551850210d444be9b28308d9691e3dde%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c637656400998658942%7cUnknown%7cTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7c1000&sdata=l6w0SvVcMSvyGnJ6%2B6uSSgd3braF2dZ7/AdBrqqzIR8%3D&reserved=0) “
### Card JSON
```JSON
Also, repro on UWP
```
### Screenshot
_No response_ | 1.0 | [Designer]Bug 35714425: [V1.0-> Scenarios - FoodOrder.json]: "Your registration is almost complete" is not defined as a heading on 'FoodOrder.Json' card. - ### Problem Description
[Bug 35714425](https://microsoft.visualstudio.com/OS/_workitems/edit/35714425): [V1.0-> Scenarios - FoodOrder.json]: "Your registration is almost complete" is not defined as a heading on 'FoodOrder.Json' card.
Test Environment:
Device: iPhone x
iOS: 14.7.1
Application: Adaptive Cards
App Version: Version 1.0 (2.3.1-beta.20210823.1)
Screen Reader: Voice Over
Repro Steps:
1. Launch Adaptive Cards iOS application.
2. Home screen will appear.
3. Navigate to "V1.0" control and select it.
4. Navigate on "V1.0" screen and select "Scenarios" button.
5. 'Scenario' screen will appear.
6. Navigate to "FoodOrder.json" control and select it.
7. Navigate the 'FoodOrder.json' screen and enable Voiceover for the ease of access.
8. Navigate till 'Your registration is almost complete' and hear screen reader narration.
Actual Result:
"Your registration is almost complete" is not defined as a heading on 'FoodOrder.Json' card. Screen reader is only announcing as, "Your registration is almost complete text field double tap to edit Use the rotor to access Misspelt Words".
Expected Result:
"Your registration is almost complete" should be defined under a heading. Screen reader should announce as, "Your registration is almost complete heading Use the rotor to access headings".
Note:
Same issue is also repro for 'Malt and Vine' text on FoodOrder.json card. (Please refer attachment)
v1.0 -Element -AdaptiveCard.json- Issue is repro for 'Publish Adaptive Card Schema'. (Please refer attachment)
v1.0-Element-ColumnSet.Spacing.json- issue is repro for 'ColumnSet Spacing'. (Please refer attachment)
v1.0-Element-Container.Spacing.json- issue is repro for 'Container Spacing'.
Issue is repro throughout application. Headings is not defined as heading.
User Experience:
It will be confusing & difficult for the users if Heading will not be defined inside the adaptive card.
"Have feedback to share on Bugs ? Please help fill [Trusted Tester Bug Feedback (office.com)](https://nam06.safelinks.protection.outlook.com/?url=https://forms.office.com/pages/responsepage.aspx?id%3Dv4j5cvGGr0GRqy180BHbR5dUqGQgJ9lItv-jqY8F09lURVdYTENIRkY2UzlCR0NKV1E2VUE5OVpDVy4u&data=04%7c01%7cv-apoorva%40microsoft.com%7c551850210d444be9b28308d9691e3dde%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c637656400998658942%7cUnknown%7cTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7c1000&sdata=l6w0SvVcMSvyGnJ6%2B6uSSgd3braF2dZ7/AdBrqqzIR8%3D&reserved=0) “
### Card JSON
```JSON
Also, repro on UWP
```
### Screenshot
_No response_ | non_priority | bug your registration is almost complete is not defined as a heading on foodorder json card problem description your registration is almost complete is not defined as a heading on foodorder json card test environment device iphone x ios application adaptive cards app version version beta screen reader voice over repro steps launch adaptive cards ios application home screen will appear navigate to control and select it navigate on screen and select scenarios button scenario screen will appear navigate to foodorder json control and select it navigate the foodorder json screen and enable voiceover for the ease of access navigate till your registration is almost complete and hear screen reader narration actual result your registration is almost complete is not defined as a heading on foodorder json card screen reader is only announcing as your registration is almost complete text field double tap to edit use the rotor to access misspelt words expected result your registration is almost complete should be defined under a heading screen reader should announce as your registration is almost complete heading use the rotor to access headings note same issue is also repro for malt and vine text on foodorder json card please refer attachment element adaptivecard json issue is repro for publish adaptive card schema please refer attachment element columnset spacing json issue is repro for columnset spacing please refer attachment element container spacing json issue is repro for container spacing issue is repro throughout application headings is not defined as heading user experience it will be confusing difficult for the users if heading will not be defined inside the adaptive card have feedback to share on bugs please help fill “ card json json also repro on uwp screenshot no response | 0 |
421,654 | 28,351,598,654 | IssuesEvent | 2023-04-12 03:08:16 | iberis2/Todo-App | https://api.github.com/repos/iberis2/Todo-App | closed | Todo App 요구사항 명세서 작성 | documentation | ### 만들고자 하는 기능이 무엇인가요?
Todo 생성기능
### 해당 기능 구현을 위해 할 일이 무엇인가요?
1. [ ] Todo App 틀 만들기
2. [ ] API로 데이터 받아와서 CRUD 구현하기
3. [ ] Router 로 페이지 구분해서 다른 기능 추가하기
### 예상작업 시간
1 day | 1.0 | Todo App 요구사항 명세서 작성 - ### 만들고자 하는 기능이 무엇인가요?
Todo 생성기능
### 해당 기능 구현을 위해 할 일이 무엇인가요?
1. [ ] Todo App 틀 만들기
2. [ ] API로 데이터 받아와서 CRUD 구현하기
3. [ ] Router 로 페이지 구분해서 다른 기능 추가하기
### 예상작업 시간
1 day | non_priority | todo app 요구사항 명세서 작성 만들고자 하는 기능이 무엇인가요 todo 생성기능 해당 기능 구현을 위해 할 일이 무엇인가요 todo app 틀 만들기 api로 데이터 받아와서 crud 구현하기 router 로 페이지 구분해서 다른 기능 추가하기 예상작업 시간 day | 0 |
341,898 | 30,605,472,341 | IssuesEvent | 2023-07-23 00:11:14 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | closed | Fix truth_value_testing.test_numpy_isrealobj | NumPy Frontend Sub Task Failing Test | | | |
|---|---|
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5633280439/job/15261988995"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5633280439/job/15261988995"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5633280439/job/15261988995"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5633280439/job/15261988995"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5633280439/job/15261988995"><img src=https://img.shields.io/badge/-success-success></a>
| 1.0 | Fix truth_value_testing.test_numpy_isrealobj - | | |
|---|---|
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5633280439/job/15261988995"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5633280439/job/15261988995"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5633280439/job/15261988995"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5633280439/job/15261988995"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5633280439/job/15261988995"><img src=https://img.shields.io/badge/-success-success></a>
| non_priority | fix truth value testing test numpy isrealobj jax a href src numpy a href src tensorflow a href src torch a href src paddle a href src | 0 |
100,167 | 12,507,224,272 | IssuesEvent | 2020-06-02 13:49:17 | pernstrong/now-what | https://api.github.com/repos/pernstrong/now-what | closed | 5/31 - Change display | ux/ui design | Should show the item you searched for as well as similar items in the search results | 1.0 | 5/31 - Change display - Should show the item you searched for as well as similar items in the search results | non_priority | change display should show the item you searched for as well as similar items in the search results | 0 |
40,314 | 10,500,740,343 | IssuesEvent | 2019-09-26 11:13:06 | ROCm-Developer-Tools/HIP | https://api.github.com/repos/ROCm-Developer-Tools/HIP | closed | [HIPIFY] Cannot build hipify clang | hipify type:build type:question | I am using llvm+clang 6.01 on linux 18.0 LTS.
I have cuda 8.0 installed as clang 6.01 support cuda 8.0.
I am able to successfully build llvm +clang but when I try to build hipify clang it fails.
It seems like clang is not able to find the headers.
I am attaching the log of my build:-
```
[ 3%] Building CXX object CMakeFiles/hipify-clang.dir/src/ArgParse.cpp.o
[ 6%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP.cpp.o
[ 10%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_BLAS_API_functions.cpp.o
[ 13%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_CAFFE2_API_functions.cpp.o
[ 17%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_BLAS_API_types.cpp.o
[ 20%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Complex_API_functions.cpp.o
[ 24%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_CAFFE2_API_types.cpp.o
[ 27%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Driver_API_types.cpp.o
[ 31%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Complex_API_types.cpp.o
[ 34%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_DNN_API_functions.cpp.o
[ 37%] Building CXX object CMakeFiles/hipify-clang.dir/src/HipifyAction.cpp.o
[ 44%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Runtime_API_types.cpp.o
[ 44%] Building CXX object CMakeFiles/hipify-clang.dir/src/Statistics.cpp.o
[ 51%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_DNN_API_types.cpp.o
[ 51%] Building CXX object CMakeFiles/hipify-clang.dir/src/main.cpp.o
[ 55%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Device_functions.cpp.o
[ 58%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_SPARSE_API_types.cpp.o
[ 62%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Runtime_API_functions.cpp.o
[ 65%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_RAND_API_functions.cpp.o
[ 68%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_FFT_API_functions.cpp.o
[ 72%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_SPARSE_API_functions.cpp.o
In file included from In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Complex_API_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/HipifyAction.cpp:23:
/home/amol/HIP/HIP/hipify-clang/src/HipifyAction.h:25:10: [ 75%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_FFT_API_types.cpp.o
fatal error: 'clang/Lex/PPCallbacks.h' file not found
#include "clang/Lex/PPCallbacks.h"
^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/ArgParse.cpp:23:
/home/amol/HIP/HIP/hipify-clang/src/ArgParse.h:25:10: fatal error: 'clang/Tooling/CommonOptionsParser.h' file not found
#include "clang/Tooling/CommonOptionsParser.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[ 96%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Python.cpp.o
[ 79%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_RAND_API_types.cpp.o
[ 82%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Driver_API_functions.cpp.o
[ 86%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Perl.cpp.o
[ 89%] Building CXX object CMakeFiles/hipify-clang.dir/src/StringUtils.cpp.o
[ 93%] Building CXX object CMakeFiles/hipify-clang.dir/src/LLVMCompat.cpp.o
In file included from In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Runtime_API_types.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Runtime_API_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h/home/amol/HIP/HIP/hipify-clang/src/main.cpp:23:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstdio:42:
/usr/include/stdio.h:33:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_CAFFE2_API_types.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_SPARSE_API_types.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
/home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_CAFFE2_API_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_BLAS_API_types.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Driver_API_types.cpp:23In file included from In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Perl.cpp:23:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/sstream:38:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/istream:38:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/ios:38:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/iosfwd:40:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/postypes.h:40:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cwchar:44:
/usr/include/wchar.h:35:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Device_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_BLAS_API_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_DNN_API_functions.cpp:In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_DNN_API_types.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file23 not:
foundIn file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h
:#include <stddef.h>25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h
:20:
^~~~~~~~~~
In file included from /usr/local/include/llvm/ADT/Optional.hIn file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_FFT_API_types.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Complex_API_types.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_RAND_API_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
/home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Driver_API_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/LLVMCompat.cpp:23:
:
:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/ArgParse.h:25:10: fatal error: 'clang/Tooling/CommonOptionsParser.h' file not found
#include "clang/Tooling/CommonOptionsParser.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_FFT_API_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_RAND_API_types.cpp:23:
In file included from In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Python.cpp:23:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/sstream:38:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/istream:38:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/ios:38:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/iosfwd:40:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/postypes.h:40:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cwchar:44:
/usr/include/wchar.h:35:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_SPARSE_API_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>/home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h
^~~~~~~~~~
:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/Statistics.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/Statistics.h:25:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/chrono:41:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/ctime:42:
/usr/include/time.h:29:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:140: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Complex_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Complex_API_functions.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
1 error generated.
In file included from /home/amol/HIP/HIP/hipify-clang/src/StringUtils.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/StringUtils.h:25:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/string:40:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/char_traits.h:40:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/postypes.h:40:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cwchar:44:
/usr/include/wchar.h:35:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
CMakeFiles/hipify-clang.dir/build.make:361: recipe for target 'CMakeFiles/hipify-clang.dir/src/HipifyAction.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/HipifyAction.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:322: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Runtime_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Runtime_API_types.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:127: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_CAFFE2_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_CAFFE2_API_types.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:75: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:88: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_BLAS_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_BLAS_API_functions.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:257: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Perl.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Perl.cpp.o] Error 1
1clang++: /home/amol/HIP/new_llvm_clang/llvm-8.0.1.src/tools/clang/lib/AST/Decl.cpp:2342: bool clang::VarDecl::checkInitIsICE() const: Assertion `!Init->isValueDependent()' failed.
error generated.
Stack dump:
0. Program arguments: /usr/local/bin/clang++ -cc1 -triple x86_64-unknown-linux-gnu -emit-obj -disable-free -main-file-name Statistics.cpp -mrelocation-model static -mthread-model posix -fmath-errno -masm-verbose -mconstructor-aliases -munwind-tables -fuse-init-array -target-cpu x86-64 -dwarf-column-info -debugger-tuning=gdb -momit-leaf-frame-pointer -coverage-notes-file /home/amol/HIP/HIP/hipify-clang/build/CMakeFiles/hipify-clang.dir/src/Statistics.cpp.gcno -resource-dir /usr/local/lib/clang/8.0.1 -D GTEST_HAS_RTTI=0 -D HIPIFY_CLANG_RES="/usr/local/lib/clang/6.0.1" -D NDEBUG -D _GNU_SOURCE -D _DEBUG -D __STDC_CONSTANT_MACROS -D __STDC_FORMAT_MACROS -D __STDC_LIMIT_MACROS -internal-isystem /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0 -internal-isystem /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/x86_64-linux-gnu/c++/7.4.0 -internal-isystem /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/x86_64-linux-gnu/c++/7.4.0 -internal-isystem /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/backward -internal-isystem /usr/local/include -internal-isystem /usr/local/lib/clang/8.0.1/include -internal-externc-isystem /usr/include/x86_64-linux-gnu -internal-externc-isystem /include -internal-externc-isystem /usr/include -O3 -std=c++11 -fdeprecated-macro -fdebug-compilation-dir /home/amol/HIP/HIP/hipify-clang/build -ferror-limit 19 -fmessage-length 204 -fvisibility-inlines-hidden -pthread -fno-rtti -fobjc-runtime=gcc -fdiagnostics-show-option -fcolor-diagnostics -vectorize-loops -vectorize-slp -o CMakeFiles/hipify-clang.dir/src/Statistics.cpp.o -xCMakeFiles/hipify-clang.dir/build.make:62: recipe for target 'CMakeFiles/hipify-clang.dir/src/ArgParse.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/ArgParse.cpp.o] Error 1
c++ /home/amol/HIP/HIP/hipify-clang/src/Statistics.cpp -faddrsig
1. /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/locale_facets_nonio.tcc:647:8: current parser token '__ctype'
2. /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/ostream:41:1: parsing namespace 'std'
3. /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/locale_facets_nonio.tcc:35:1: parsing namespace 'std::std'
4. /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/locale_facets_nonio.tcc:637:5: parsing function body
5. /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/locale_facets_nonio.tcc:637:5: in compound statement ('{}')
6. /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/locale_facets_nonio.tcc:646:2: in compound statement ('{}')
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:192: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Device_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Device_functions.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:179: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_DNN_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_DNN_API_types.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:283: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_RAND_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_RAND_API_functions.cpp.o] Error 1
1 error generated.
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:218: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Driver_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Driver_API_types.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:348: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_SPARSE_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_SPARSE_API_types.cpp.o] Error 1
CMakeFiles/hipify-clang.dir/build.make:166: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_DNN_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_DNN_API_functions.cpp.o] Error 1
1 error generated.
1 error generated.
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:153: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Complex_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Complex_API_types.cpp.o] Error 1
CMakeFiles/hipify-clang.dir/build.make:114: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_CAFFE2_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_CAFFE2_API_functions.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:205: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Driver_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Driver_API_functions.cpp.o] Error 1
CMakeFiles/hipify-clang.dir/build.make:335: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_SPARSE_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_SPARSE_API_functions.cpp.o] Error 1
1 error generated.
1 error generated.
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:101: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_BLAS_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_BLAS_API_types.cpp.o] Error 1
CMakeFiles/hipify-clang.dir/build.make:309: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Runtime_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Runtime_API_functions.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:296: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_RAND_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_RAND_API_types.cpp.o] Error 1
CMakeFiles/hipify-clang.dir/build.make:244: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_FFT_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_FFT_API_types.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:231: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_FFT_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_FFT_API_functions.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:400: recipe for target 'CMakeFiles/hipify-clang.dir/src/StringUtils.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/StringUtils.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:270: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Python.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Python.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:413: recipe for target 'CMakeFiles/hipify-clang.dir/src/main.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/main.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:374: recipe for target 'CMakeFiles/hipify-clang.dir/src/LLVMCompat.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/LLVMCompat.cpp.o] Error 1
#0 0x000055608fb19d6a llvm::sys::PrintStackTrace(llvm::raw_ostream&) (/usr/local/bin/clang+++0x1576d6a)
#1 0x000055608fb17be4 llvm::sys::RunSignalHandlers() (/usr/local/bin/clang+++0x1574be4)
#2 0x000055608fb17d22 SignalHandler(int) (/usr/local/bin/clang+++0x1574d22)
#3 0x00007fd4885b5890 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x12890)
#4 0x00007fd487266e97 gsignal /build/glibc-OTsEL5/glibc-2.27/signal/../sysdeps/unix/sysv/linux/raise.c:51:0
#5 0x00007fd487268801 abort /build/glibc-OTsEL5/glibc-2.27/stdlib/abort.c:81:0
#6 0x00007fd48725839a __assert_fail_base /build/glibc-OTsEL5/glibc-2.27/assert/assert.c:89:0
#7 0x00007fd487258412 (/lib/x86_64-linux-gnu/libc.so.6+0x30412)
#8 0x000055609179a712 clang::VarDecl::checkInitIsICE() const (/usr/local/bin/clang+++0x31f7712)
#9 0x0000556091251a96 DoMarkVarDeclReferenced(clang::Sema&, clang::SourceLocation, clang::VarDecl*, clang::Expr*) (/usr/local/bin/clang+++0x2caea96)
#10 0x00005560912523ee clang::Sema::BuildDeclRefExpr(clang::ValueDecl*, clang::QualType, clang::ExprValueKind, clang::DeclarationNameInfo const&, clang::CXXScopeSpec const*, clang::NamedDecl*, clang::TemplateArgumentListInfo const*) (/usr/local/bin/clang+++0x2caf3ee)
#11 0x0000556091252cea clang::Sema::BuildDeclarationNameExpr(clang::CXXScopeSpec const&, clang::DeclarationNameInfo const&, clang::NamedDecl*, clang::NamedDecl*, clang::TemplateArgumentListInfo const*, bool) (/usr/local/bin/clang+++0x2cafcea)
#12 0x000055609125331b clang::Sema::BuildDeclarationNameExpr(clang::CXXScopeSpec const&, clang::LookupResult&, bool, bool) (/usr/local/bin/clang+++0x2cb031b)
#13 0x000055609113e6e6 clang::Sema::ClassifyName(clang::Scope*, clang::CXXScopeSpec&, clang::IdentifierInfo*&, clang::SourceLocation, clang::Token const&, bool, std::unique_ptr<clang::CorrectionCandidateCallback, std::default_delete<clang::CorrectionCandidateCallback> >) (/usr/local/bin/clang+++0x2b9b6e6)
#14 0x0000556090f0f6e9 clang::Parser::TryAnnotateName(bool, std::unique_ptr<clang::CorrectionCandidateCallback, std::default_delete<clang::CorrectionCandidateCallback> >) (/usr/local/bin/clang+++0x296c6e9)
#15 0x0000556090faa299 clang::Parser::isCXXDeclarationSpecifier(clang::Parser::TPResult, bool*) (/usr/local/bin/clang+++0x2a07299)
#16 0x0000556090fac99f clang::Parser::isCXXConditionDeclarationOrInitStatement(bool, bool) (/usr/local/bin/clang+++0x2a0999f)
#17 0x0000556090f5b891 clang::Parser::ParseCXXCondition(clang::ActionResult<clang::Stmt*, true>*, clang::SourceLocation, clang::Sema::ConditionKind, clang::Parser::ForRangeInfo*) (/usr/local/bin/clang+++0x29b8891)
#18 0x0000556090f8de2c clang::Parser::ParseParenExprOrCondition(clang::ActionResult<clang::Stmt*, true>*, clang::Sema::ConditionResult&, clang::SourceLocation, clang::Sema::ConditionKind) (/usr/local/bin/clang+++0x29eae2c)
#19 0x0000556090f93c7d clang::Parser::ParseIfStatement(clang::SourceLocation*) (/usr/local/bin/clang+++0x29f0c7d)
#20 0x0000556090f913bb clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::AllowedConstructsKind, clang::SourceLocation*, clang::Parser::ParsedAttributesWithRange&) (/usr/local/bin/clang+++0x29ee3bb)
#21 0x0000556090f91fa9 clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::AllowedConstructsKind, clang::SourceLocation*) (/usr/local/bin/clang+++0x29eefa9)
#22 0x0000556090f8e979 clang::Parser::ParseCompoundStatementBody(bool) (/usr/local/bin/clang+++0x29eb979)
#23 0x0000556090f8eea5 clang::Parser::ParseCompoundStatement(bool, unsigned int) (/usr/local/bin/clang+++0x29ebea5)
#24 0x0000556090f914ca clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::AllowedConstructsKind, clang::SourceLocation*, clang::Parser::ParsedAttributesWithRange&) (/usr/local/bin/clang+++0x29ee4ca)
#25 0x0000556090f91fa9 clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::AllowedConstructsKind, clang::SourceLocation*) (/usr/local/bin/clang+++0x29eefa9)
#26 0x0000556090f92287 clang::Parser::ParseStatement(clang::SourceLocation*, bool) (/usr/local/bin/clang+++0x29ef287)
#27 0x0000556090f954fc clang::Parser::ParseForStatement(clang::SourceLocation*) (/usr/local/bin/clang+++0x29f24fc)
#28 0x0000556090f913eb clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::AllowedConstructsKind, clang::SourceLocation*, clang::Parser::ParsedAttributesWithRange&) (/usr/local/bin/clang+++0x29ee3eb)
#29 0x0000556090f91fa9 clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::AllowedConstructsKind, clang::SourceLocation*) (/usr/local/bin/clang+++0x29eefa9)
#30 0x0000556090f8e979 clang::Parser::ParseCompoundStatementBody(bool) (/usr/local/bin/clang+++0x29eb979)
#31 0x0000556090f969e4 clang::Parser::ParseFunctionStatementBody(clang::Decl*, clang::Parser::ParseScope&) (/usr/local/bin/clang+++0x29f39e4)
#32 0x0000556090f0c4cc clang::Parser::ParseFunctionDefinition(clang::ParsingDeclarator&, clang::Parser::ParsedTemplateInfo const&, clang::Parser::LateParsedAttrList*) (/usr/local/bin/clang+++0x29694cc)
#33 0x0000556090fa6ea2 clang::Parser::ParseSingleDeclarationAfterTemplate(clang::DeclaratorContext, clang::Parser::ParsedTemplateInfo const&, clang::ParsingDeclRAIIObject&, clang::SourceLocation&, clang::ParsedAttributes&, clang::AccessSpecifier) (/usr/local/bin/clang+++0x2a03ea2)
#34 0x0000556090fa78ec clang::Parser::ParseTemplateDeclarationOrSpecialization(clang::DeclaratorContext, clang::SourceLocation&, clang::ParsedAttributes&, clang::AccessSpecifier) (/usr/local/bin/clang+++0x2a048ec)
#35 0x0000556090fa7ebd clang::Parser::ParseDeclarationStartingWithTemplate(clang::DeclaratorContext, clang::SourceLocation&, clang::ParsedAttributes&, clang::AccessSpecifier) (/usr/local/bin/clang+++0x2a04ebd)
#36 0x0000556090f30e67 clang::Parser::ParseDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&) (/usr/local/bin/clang+++0x298de67)
#37 0x0000556090f0d6ba clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*) (/usr/local/bin/clang+++0x296a6ba)
#38 0x0000556090f40ade clang::Parser::ParseInnerNamespace(llvm::SmallVector<clang::Parser::InnerNamespaceInfo, 4u> const&, unsigned int, clang::SourceLocation&, clang::ParsedAttributes&, clang::BalancedDelimiterTracker&) (/usr/local/bin/clang+++0x299dade)
#39 0x0000556090f416f3 clang::Parser::ParseNamespace(clang::DeclaratorContext, clang::SourceLocation&, clang::SourceLocation) (/usr/local/bin/clang+++0x299e6f3)
#40 0x0000556090f30e90 clang::Parser::ParseDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&) (/usr/local/bin/clang+++0x298de90)
#41 0x0000556090f0d6ba clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*) (/usr/local/bin/clang+++0x296a6ba)
#42 0x0000556090f40ade clang::Parser::ParseInnerNamespace(llvm::SmallVector<clang::Parser::InnerNamespaceInfo, 4u> const&, unsigned int, clang::SourceLocation&, clang::ParsedAttributes&, clang::BalancedDelimiterTracker&) (/usr/local/bin/clang+++0x299dade)
#43 0x0000556090f416f3 clang::Parser::ParseNamespace(clang::DeclaratorContext, clang::SourceLocation&, clang::SourceLocation) (/usr/local/bin/clang+++0x299e6f3)
#44 0x0000556090f30e90 clang::Parser::ParseDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&) (/usr/local/bin/clang+++0x298de90)
#45 0x0000556090f0d6ba clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*) (/usr/local/bin/clang+++0x296a6ba)
#46 0x0000556090f0e859 clang::Parser::ParseTopLevelDecl(clang::OpaquePtr<clang::DeclGroupRef>&) (/usr/local/bin/clang+++0x296b859)
#47 0x0000556090f04527 clang::ParseAST(clang::Sema&, bool, bool) (/usr/local/bin/clang+++0x2961527)
#48 0x000055609064a828 clang::CodeGenAction::ExecuteAction() (/usr/local/bin/clang+++0x20a7828)
#49 0x00005560901c0b2e clang::FrontendAction::Execute() (/usr/local/bin/clang+++0x1c1db2e)
#50 0x00005560901821b6 clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) (/usr/local/bin/clang+++0x1bdf1b6)
#51 0x0000556090263f6d clang::ExecuteCompilerInvocation(clang::CompilerInstance*) (/usr/local/bin/clang+++0x1cc0f6d)
#52 0x000055608ee66b08 cc1_main(llvm::ArrayRef<char const*>, char const*, void*) (/usr/local/bin/clang+++0x8c3b08)
#53 0x000055608ee09e2d main (/usr/local/bin/clang+++0x866e2d)
#54 0x00007fd487249b97 __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:344:0
#55 0x000055608ee6285a _start (/usr/local/bin/clang+++0x8bf85a)
clang++: error: unable to execute command: Aborted (core dumped)
clang++: error: clang frontend command failed due to signal (use -v to see invocation)
clang version 8.0.1 (tags/RELEASE_801/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/local/bin
clang++: note: diagnostic msg: PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace, preprocessed source, and associated run script.
clang++: note: diagnostic msg: Error generating preprocessed source(s).
CMakeFiles/hipify-clang.dir/build.make:387: recipe for target 'CMakeFiles/hipify-clang.dir/src/Statistics.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/Statistics.cpp.o] Error 254
CMakeFiles/Makefile2:78: recipe for target 'CMakeFiles/hipify-clang.dir/all' failed
make[1]: *** [CMakeFiles/hipify-clang.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2
``` | 1.0 | [HIPIFY] Cannot build hipify clang - I am using llvm+clang 6.01 on linux 18.0 LTS.
I have cuda 8.0 installed as clang 6.01 support cuda 8.0.
I am able to successfully build llvm +clang but when I try to build hipify clang it fails.
It seems like clang is not able to find the headers.
I am attaching the log of my build:-
```
[ 3%] Building CXX object CMakeFiles/hipify-clang.dir/src/ArgParse.cpp.o
[ 6%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP.cpp.o
[ 10%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_BLAS_API_functions.cpp.o
[ 13%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_CAFFE2_API_functions.cpp.o
[ 17%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_BLAS_API_types.cpp.o
[ 20%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Complex_API_functions.cpp.o
[ 24%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_CAFFE2_API_types.cpp.o
[ 27%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Driver_API_types.cpp.o
[ 31%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Complex_API_types.cpp.o
[ 34%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_DNN_API_functions.cpp.o
[ 37%] Building CXX object CMakeFiles/hipify-clang.dir/src/HipifyAction.cpp.o
[ 44%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Runtime_API_types.cpp.o
[ 44%] Building CXX object CMakeFiles/hipify-clang.dir/src/Statistics.cpp.o
[ 51%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_DNN_API_types.cpp.o
[ 51%] Building CXX object CMakeFiles/hipify-clang.dir/src/main.cpp.o
[ 55%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Device_functions.cpp.o
[ 58%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_SPARSE_API_types.cpp.o
[ 62%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Runtime_API_functions.cpp.o
[ 65%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_RAND_API_functions.cpp.o
[ 68%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_FFT_API_functions.cpp.o
[ 72%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_SPARSE_API_functions.cpp.o
In file included from In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Complex_API_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/HipifyAction.cpp:23:
/home/amol/HIP/HIP/hipify-clang/src/HipifyAction.h:25:10: [ 75%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_FFT_API_types.cpp.o
fatal error: 'clang/Lex/PPCallbacks.h' file not found
#include "clang/Lex/PPCallbacks.h"
^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/ArgParse.cpp:23:
/home/amol/HIP/HIP/hipify-clang/src/ArgParse.h:25:10: fatal error: 'clang/Tooling/CommonOptionsParser.h' file not found
#include "clang/Tooling/CommonOptionsParser.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[ 96%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Python.cpp.o
[ 79%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_RAND_API_types.cpp.o
[ 82%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Driver_API_functions.cpp.o
[ 86%] Building CXX object CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Perl.cpp.o
[ 89%] Building CXX object CMakeFiles/hipify-clang.dir/src/StringUtils.cpp.o
[ 93%] Building CXX object CMakeFiles/hipify-clang.dir/src/LLVMCompat.cpp.o
In file included from In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Runtime_API_types.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Runtime_API_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h/home/amol/HIP/HIP/hipify-clang/src/main.cpp:23:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstdio:42:
/usr/include/stdio.h:33:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_CAFFE2_API_types.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_SPARSE_API_types.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
/home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_CAFFE2_API_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_BLAS_API_types.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Driver_API_types.cpp:23In file included from In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Perl.cpp:23:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/sstream:38:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/istream:38:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/ios:38:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/iosfwd:40:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/postypes.h:40:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cwchar:44:
/usr/include/wchar.h:35:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Device_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_BLAS_API_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_DNN_API_functions.cpp:In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_DNN_API_types.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file23 not:
foundIn file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h
:#include <stddef.h>25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h
:20:
^~~~~~~~~~
In file included from /usr/local/include/llvm/ADT/Optional.hIn file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_FFT_API_types.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Complex_API_types.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_RAND_API_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
/home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Driver_API_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/LLVMCompat.cpp:23:
:
:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/ArgParse.h:25:10: fatal error: 'clang/Tooling/CommonOptionsParser.h' file not found
#include "clang/Tooling/CommonOptionsParser.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_FFT_API_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_RAND_API_types.cpp:23:
In file included from In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_Python.cpp:23:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/sstream:38:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/istream:38:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/ios:38:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/iosfwd:40:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/postypes.h:40:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cwchar:44:
/usr/include/wchar.h:35:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP_SPARSE_API_functions.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>/home/amol/HIP/HIP/hipify-clang/src/CUDA2HIP.h
^~~~~~~~~~
:25:
In file included from /usr/local/include/llvm/ADT/StringRef.h:13:
In file included from /usr/local/include/llvm/ADT/STLExtras.h:20:
In file included from /usr/local/include/llvm/ADT/Optional.h:20:
In file included from /usr/local/include/llvm/Support/AlignOf.h:18:
/usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cstddef:50:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
In file included from /home/amol/HIP/HIP/hipify-clang/src/Statistics.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/Statistics.h:25:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/chrono:41:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/ctime:42:
/usr/include/time.h:29:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:140: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Complex_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Complex_API_functions.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
1 error generated.
In file included from /home/amol/HIP/HIP/hipify-clang/src/StringUtils.cpp:23:
In file included from /home/amol/HIP/HIP/hipify-clang/src/StringUtils.h:25:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/string:40:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/char_traits.h:40:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/postypes.h:40:
In file included from /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/cwchar:44:
/usr/include/wchar.h:35:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
^~~~~~~~~~
CMakeFiles/hipify-clang.dir/build.make:361: recipe for target 'CMakeFiles/hipify-clang.dir/src/HipifyAction.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/HipifyAction.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:322: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Runtime_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Runtime_API_types.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:127: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_CAFFE2_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_CAFFE2_API_types.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:75: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:88: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_BLAS_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_BLAS_API_functions.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:257: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Perl.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Perl.cpp.o] Error 1
1clang++: /home/amol/HIP/new_llvm_clang/llvm-8.0.1.src/tools/clang/lib/AST/Decl.cpp:2342: bool clang::VarDecl::checkInitIsICE() const: Assertion `!Init->isValueDependent()' failed.
error generated.
Stack dump:
0. Program arguments: /usr/local/bin/clang++ -cc1 -triple x86_64-unknown-linux-gnu -emit-obj -disable-free -main-file-name Statistics.cpp -mrelocation-model static -mthread-model posix -fmath-errno -masm-verbose -mconstructor-aliases -munwind-tables -fuse-init-array -target-cpu x86-64 -dwarf-column-info -debugger-tuning=gdb -momit-leaf-frame-pointer -coverage-notes-file /home/amol/HIP/HIP/hipify-clang/build/CMakeFiles/hipify-clang.dir/src/Statistics.cpp.gcno -resource-dir /usr/local/lib/clang/8.0.1 -D GTEST_HAS_RTTI=0 -D HIPIFY_CLANG_RES="/usr/local/lib/clang/6.0.1" -D NDEBUG -D _GNU_SOURCE -D _DEBUG -D __STDC_CONSTANT_MACROS -D __STDC_FORMAT_MACROS -D __STDC_LIMIT_MACROS -internal-isystem /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0 -internal-isystem /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/x86_64-linux-gnu/c++/7.4.0 -internal-isystem /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/x86_64-linux-gnu/c++/7.4.0 -internal-isystem /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/backward -internal-isystem /usr/local/include -internal-isystem /usr/local/lib/clang/8.0.1/include -internal-externc-isystem /usr/include/x86_64-linux-gnu -internal-externc-isystem /include -internal-externc-isystem /usr/include -O3 -std=c++11 -fdeprecated-macro -fdebug-compilation-dir /home/amol/HIP/HIP/hipify-clang/build -ferror-limit 19 -fmessage-length 204 -fvisibility-inlines-hidden -pthread -fno-rtti -fobjc-runtime=gcc -fdiagnostics-show-option -fcolor-diagnostics -vectorize-loops -vectorize-slp -o CMakeFiles/hipify-clang.dir/src/Statistics.cpp.o -xCMakeFiles/hipify-clang.dir/build.make:62: recipe for target 'CMakeFiles/hipify-clang.dir/src/ArgParse.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/ArgParse.cpp.o] Error 1
c++ /home/amol/HIP/HIP/hipify-clang/src/Statistics.cpp -faddrsig
1. /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/locale_facets_nonio.tcc:647:8: current parser token '__ctype'
2. /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/ostream:41:1: parsing namespace 'std'
3. /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/locale_facets_nonio.tcc:35:1: parsing namespace 'std::std'
4. /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/locale_facets_nonio.tcc:637:5: parsing function body
5. /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/locale_facets_nonio.tcc:637:5: in compound statement ('{}')
6. /usr/lib/gcc/x86_64-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/locale_facets_nonio.tcc:646:2: in compound statement ('{}')
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:192: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Device_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Device_functions.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:179: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_DNN_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_DNN_API_types.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:283: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_RAND_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_RAND_API_functions.cpp.o] Error 1
1 error generated.
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:218: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Driver_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Driver_API_types.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:348: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_SPARSE_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_SPARSE_API_types.cpp.o] Error 1
CMakeFiles/hipify-clang.dir/build.make:166: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_DNN_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_DNN_API_functions.cpp.o] Error 1
1 error generated.
1 error generated.
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:153: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Complex_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Complex_API_types.cpp.o] Error 1
CMakeFiles/hipify-clang.dir/build.make:114: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_CAFFE2_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_CAFFE2_API_functions.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:205: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Driver_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Driver_API_functions.cpp.o] Error 1
CMakeFiles/hipify-clang.dir/build.make:335: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_SPARSE_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_SPARSE_API_functions.cpp.o] Error 1
1 error generated.
1 error generated.
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:101: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_BLAS_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_BLAS_API_types.cpp.o] Error 1
CMakeFiles/hipify-clang.dir/build.make:309: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Runtime_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Runtime_API_functions.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:296: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_RAND_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_RAND_API_types.cpp.o] Error 1
CMakeFiles/hipify-clang.dir/build.make:244: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_FFT_API_types.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_FFT_API_types.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:231: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_FFT_API_functions.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_FFT_API_functions.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:400: recipe for target 'CMakeFiles/hipify-clang.dir/src/StringUtils.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/StringUtils.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:270: recipe for target 'CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Python.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/CUDA2HIP_Python.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:413: recipe for target 'CMakeFiles/hipify-clang.dir/src/main.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/main.cpp.o] Error 1
1 error generated.
CMakeFiles/hipify-clang.dir/build.make:374: recipe for target 'CMakeFiles/hipify-clang.dir/src/LLVMCompat.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/LLVMCompat.cpp.o] Error 1
#0 0x000055608fb19d6a llvm::sys::PrintStackTrace(llvm::raw_ostream&) (/usr/local/bin/clang+++0x1576d6a)
#1 0x000055608fb17be4 llvm::sys::RunSignalHandlers() (/usr/local/bin/clang+++0x1574be4)
#2 0x000055608fb17d22 SignalHandler(int) (/usr/local/bin/clang+++0x1574d22)
#3 0x00007fd4885b5890 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x12890)
#4 0x00007fd487266e97 gsignal /build/glibc-OTsEL5/glibc-2.27/signal/../sysdeps/unix/sysv/linux/raise.c:51:0
#5 0x00007fd487268801 abort /build/glibc-OTsEL5/glibc-2.27/stdlib/abort.c:81:0
#6 0x00007fd48725839a __assert_fail_base /build/glibc-OTsEL5/glibc-2.27/assert/assert.c:89:0
#7 0x00007fd487258412 (/lib/x86_64-linux-gnu/libc.so.6+0x30412)
#8 0x000055609179a712 clang::VarDecl::checkInitIsICE() const (/usr/local/bin/clang+++0x31f7712)
#9 0x0000556091251a96 DoMarkVarDeclReferenced(clang::Sema&, clang::SourceLocation, clang::VarDecl*, clang::Expr*) (/usr/local/bin/clang+++0x2caea96)
#10 0x00005560912523ee clang::Sema::BuildDeclRefExpr(clang::ValueDecl*, clang::QualType, clang::ExprValueKind, clang::DeclarationNameInfo const&, clang::CXXScopeSpec const*, clang::NamedDecl*, clang::TemplateArgumentListInfo const*) (/usr/local/bin/clang+++0x2caf3ee)
#11 0x0000556091252cea clang::Sema::BuildDeclarationNameExpr(clang::CXXScopeSpec const&, clang::DeclarationNameInfo const&, clang::NamedDecl*, clang::NamedDecl*, clang::TemplateArgumentListInfo const*, bool) (/usr/local/bin/clang+++0x2cafcea)
#12 0x000055609125331b clang::Sema::BuildDeclarationNameExpr(clang::CXXScopeSpec const&, clang::LookupResult&, bool, bool) (/usr/local/bin/clang+++0x2cb031b)
#13 0x000055609113e6e6 clang::Sema::ClassifyName(clang::Scope*, clang::CXXScopeSpec&, clang::IdentifierInfo*&, clang::SourceLocation, clang::Token const&, bool, std::unique_ptr<clang::CorrectionCandidateCallback, std::default_delete<clang::CorrectionCandidateCallback> >) (/usr/local/bin/clang+++0x2b9b6e6)
#14 0x0000556090f0f6e9 clang::Parser::TryAnnotateName(bool, std::unique_ptr<clang::CorrectionCandidateCallback, std::default_delete<clang::CorrectionCandidateCallback> >) (/usr/local/bin/clang+++0x296c6e9)
#15 0x0000556090faa299 clang::Parser::isCXXDeclarationSpecifier(clang::Parser::TPResult, bool*) (/usr/local/bin/clang+++0x2a07299)
#16 0x0000556090fac99f clang::Parser::isCXXConditionDeclarationOrInitStatement(bool, bool) (/usr/local/bin/clang+++0x2a0999f)
#17 0x0000556090f5b891 clang::Parser::ParseCXXCondition(clang::ActionResult<clang::Stmt*, true>*, clang::SourceLocation, clang::Sema::ConditionKind, clang::Parser::ForRangeInfo*) (/usr/local/bin/clang+++0x29b8891)
#18 0x0000556090f8de2c clang::Parser::ParseParenExprOrCondition(clang::ActionResult<clang::Stmt*, true>*, clang::Sema::ConditionResult&, clang::SourceLocation, clang::Sema::ConditionKind) (/usr/local/bin/clang+++0x29eae2c)
#19 0x0000556090f93c7d clang::Parser::ParseIfStatement(clang::SourceLocation*) (/usr/local/bin/clang+++0x29f0c7d)
#20 0x0000556090f913bb clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::AllowedConstructsKind, clang::SourceLocation*, clang::Parser::ParsedAttributesWithRange&) (/usr/local/bin/clang+++0x29ee3bb)
#21 0x0000556090f91fa9 clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::AllowedConstructsKind, clang::SourceLocation*) (/usr/local/bin/clang+++0x29eefa9)
#22 0x0000556090f8e979 clang::Parser::ParseCompoundStatementBody(bool) (/usr/local/bin/clang+++0x29eb979)
#23 0x0000556090f8eea5 clang::Parser::ParseCompoundStatement(bool, unsigned int) (/usr/local/bin/clang+++0x29ebea5)
#24 0x0000556090f914ca clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::AllowedConstructsKind, clang::SourceLocation*, clang::Parser::ParsedAttributesWithRange&) (/usr/local/bin/clang+++0x29ee4ca)
#25 0x0000556090f91fa9 clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::AllowedConstructsKind, clang::SourceLocation*) (/usr/local/bin/clang+++0x29eefa9)
#26 0x0000556090f92287 clang::Parser::ParseStatement(clang::SourceLocation*, bool) (/usr/local/bin/clang+++0x29ef287)
#27 0x0000556090f954fc clang::Parser::ParseForStatement(clang::SourceLocation*) (/usr/local/bin/clang+++0x29f24fc)
#28 0x0000556090f913eb clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::AllowedConstructsKind, clang::SourceLocation*, clang::Parser::ParsedAttributesWithRange&) (/usr/local/bin/clang+++0x29ee3eb)
#29 0x0000556090f91fa9 clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector<clang::Stmt*, 32u>&, clang::Parser::AllowedConstructsKind, clang::SourceLocation*) (/usr/local/bin/clang+++0x29eefa9)
#30 0x0000556090f8e979 clang::Parser::ParseCompoundStatementBody(bool) (/usr/local/bin/clang+++0x29eb979)
#31 0x0000556090f969e4 clang::Parser::ParseFunctionStatementBody(clang::Decl*, clang::Parser::ParseScope&) (/usr/local/bin/clang+++0x29f39e4)
#32 0x0000556090f0c4cc clang::Parser::ParseFunctionDefinition(clang::ParsingDeclarator&, clang::Parser::ParsedTemplateInfo const&, clang::Parser::LateParsedAttrList*) (/usr/local/bin/clang+++0x29694cc)
#33 0x0000556090fa6ea2 clang::Parser::ParseSingleDeclarationAfterTemplate(clang::DeclaratorContext, clang::Parser::ParsedTemplateInfo const&, clang::ParsingDeclRAIIObject&, clang::SourceLocation&, clang::ParsedAttributes&, clang::AccessSpecifier) (/usr/local/bin/clang+++0x2a03ea2)
#34 0x0000556090fa78ec clang::Parser::ParseTemplateDeclarationOrSpecialization(clang::DeclaratorContext, clang::SourceLocation&, clang::ParsedAttributes&, clang::AccessSpecifier) (/usr/local/bin/clang+++0x2a048ec)
#35 0x0000556090fa7ebd clang::Parser::ParseDeclarationStartingWithTemplate(clang::DeclaratorContext, clang::SourceLocation&, clang::ParsedAttributes&, clang::AccessSpecifier) (/usr/local/bin/clang+++0x2a04ebd)
#36 0x0000556090f30e67 clang::Parser::ParseDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&) (/usr/local/bin/clang+++0x298de67)
#37 0x0000556090f0d6ba clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*) (/usr/local/bin/clang+++0x296a6ba)
#38 0x0000556090f40ade clang::Parser::ParseInnerNamespace(llvm::SmallVector<clang::Parser::InnerNamespaceInfo, 4u> const&, unsigned int, clang::SourceLocation&, clang::ParsedAttributes&, clang::BalancedDelimiterTracker&) (/usr/local/bin/clang+++0x299dade)
#39 0x0000556090f416f3 clang::Parser::ParseNamespace(clang::DeclaratorContext, clang::SourceLocation&, clang::SourceLocation) (/usr/local/bin/clang+++0x299e6f3)
#40 0x0000556090f30e90 clang::Parser::ParseDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&) (/usr/local/bin/clang+++0x298de90)
#41 0x0000556090f0d6ba clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*) (/usr/local/bin/clang+++0x296a6ba)
#42 0x0000556090f40ade clang::Parser::ParseInnerNamespace(llvm::SmallVector<clang::Parser::InnerNamespaceInfo, 4u> const&, unsigned int, clang::SourceLocation&, clang::ParsedAttributes&, clang::BalancedDelimiterTracker&) (/usr/local/bin/clang+++0x299dade)
#43 0x0000556090f416f3 clang::Parser::ParseNamespace(clang::DeclaratorContext, clang::SourceLocation&, clang::SourceLocation) (/usr/local/bin/clang+++0x299e6f3)
#44 0x0000556090f30e90 clang::Parser::ParseDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&) (/usr/local/bin/clang+++0x298de90)
#45 0x0000556090f0d6ba clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*) (/usr/local/bin/clang+++0x296a6ba)
#46 0x0000556090f0e859 clang::Parser::ParseTopLevelDecl(clang::OpaquePtr<clang::DeclGroupRef>&) (/usr/local/bin/clang+++0x296b859)
#47 0x0000556090f04527 clang::ParseAST(clang::Sema&, bool, bool) (/usr/local/bin/clang+++0x2961527)
#48 0x000055609064a828 clang::CodeGenAction::ExecuteAction() (/usr/local/bin/clang+++0x20a7828)
#49 0x00005560901c0b2e clang::FrontendAction::Execute() (/usr/local/bin/clang+++0x1c1db2e)
#50 0x00005560901821b6 clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) (/usr/local/bin/clang+++0x1bdf1b6)
#51 0x0000556090263f6d clang::ExecuteCompilerInvocation(clang::CompilerInstance*) (/usr/local/bin/clang+++0x1cc0f6d)
#52 0x000055608ee66b08 cc1_main(llvm::ArrayRef<char const*>, char const*, void*) (/usr/local/bin/clang+++0x8c3b08)
#53 0x000055608ee09e2d main (/usr/local/bin/clang+++0x866e2d)
#54 0x00007fd487249b97 __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:344:0
#55 0x000055608ee6285a _start (/usr/local/bin/clang+++0x8bf85a)
clang++: error: unable to execute command: Aborted (core dumped)
clang++: error: clang frontend command failed due to signal (use -v to see invocation)
clang version 8.0.1 (tags/RELEASE_801/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/local/bin
clang++: note: diagnostic msg: PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace, preprocessed source, and associated run script.
clang++: note: diagnostic msg: Error generating preprocessed source(s).
CMakeFiles/hipify-clang.dir/build.make:387: recipe for target 'CMakeFiles/hipify-clang.dir/src/Statistics.cpp.o' failed
make[2]: *** [CMakeFiles/hipify-clang.dir/src/Statistics.cpp.o] Error 254
CMakeFiles/Makefile2:78: recipe for target 'CMakeFiles/hipify-clang.dir/all' failed
make[1]: *** [CMakeFiles/hipify-clang.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2
``` | non_priority | cannot build hipify clang i am using llvm clang on linux lts i have cuda installed as clang support cuda i am able to successfully build llvm clang but when i try to build hipify clang it fails it seems like clang is not able to find the headers i am attaching the log of my build building cxx object cmakefiles hipify clang dir src argparse cpp o building cxx object cmakefiles hipify clang dir src cpp o building cxx object cmakefiles hipify clang dir src blas api functions cpp o building cxx object cmakefiles hipify clang dir src api functions cpp o building cxx object cmakefiles hipify clang dir src blas api types cpp o building cxx object cmakefiles hipify clang dir src complex api functions cpp o building cxx object cmakefiles hipify clang dir src api types cpp o building cxx object cmakefiles hipify clang dir src driver api types cpp o building cxx object cmakefiles hipify clang dir src complex api types cpp o building cxx object cmakefiles hipify clang dir src dnn api functions cpp o building cxx object cmakefiles hipify clang dir src hipifyaction cpp o building cxx object cmakefiles hipify clang dir src runtime api types cpp o building cxx object cmakefiles hipify clang dir src statistics cpp o building cxx object cmakefiles hipify clang dir src dnn api types cpp o building cxx object cmakefiles hipify clang dir src main cpp o building cxx object cmakefiles hipify clang dir src device functions cpp o building cxx object cmakefiles hipify clang dir src sparse api types cpp o building cxx object cmakefiles hipify clang dir src runtime api functions cpp o building cxx object cmakefiles hipify clang dir src rand api functions cpp o building cxx object cmakefiles hipify clang dir src fft api functions cpp o building cxx object cmakefiles hipify clang dir src sparse api functions cpp o in file included from in file included from home amol hip hip hipify clang src complex api functions cpp in file included from home amol hip hip hipify clang src h in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include in file included from home amol hip hip hipify clang src hipifyaction cpp home amol hip hip hipify clang src hipifyaction h building cxx object cmakefiles hipify clang dir src fft api types cpp o fatal error clang lex ppcallbacks h file not found include clang lex ppcallbacks h in file included from home amol hip hip hipify clang src argparse cpp home amol hip hip hipify clang src argparse h fatal error clang tooling commonoptionsparser h file not found include clang tooling commonoptionsparser h building cxx object cmakefiles hipify clang dir src python cpp o building cxx object cmakefiles hipify clang dir src rand api types cpp o building cxx object cmakefiles hipify clang dir src driver api functions cpp o building cxx object cmakefiles hipify clang dir src perl cpp o building cxx object cmakefiles hipify clang dir src stringutils cpp o building cxx object cmakefiles hipify clang dir src llvmcompat cpp o in file included from in file included from home amol hip hip hipify clang src runtime api types cpp in file included from home amol hip hip hipify clang src h in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include in file included from home amol hip hip hipify clang src runtime api functions cpp in file included from home amol hip hip hipify clang src h home amol hip hip hipify clang src main cpp in file included from usr lib gcc linux gnu include c cstdio usr include stdio h fatal error stddef h file not found include in file included from home amol hip hip hipify clang src api types cpp in file included from home amol hip hip hipify clang src h in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include in file included from home amol hip hip hipify clang src sparse api types cpp in file included from home amol hip hip hipify clang src h in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include home amol hip hip hipify clang src api functions cpp in file included from home amol hip hip hipify clang src h in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include in file included from home amol hip hip hipify clang src cpp in file included from home amol hip hip hipify clang src h in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include in file included from home amol hip hip hipify clang src blas api types cpp in file included from home amol hip hip hipify clang src h in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include in file included from home amol hip hip hipify clang src driver api types cpp file included from in file included from home amol hip hip hipify clang src perl cpp in file included from usr lib gcc linux gnu include c sstream in file included from usr lib gcc linux gnu include c istream in file included from usr lib gcc linux gnu include c ios in file included from usr lib gcc linux gnu include c iosfwd in file included from usr lib gcc linux gnu include c bits postypes h in file included from usr lib gcc linux gnu include c cwchar usr include wchar h fatal error stddef h file not found include in file included from home amol hip hip hipify clang src device functions cpp in file included from home amol hip hip hipify clang src h in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h in file included from home amol hip hip hipify clang src blas api functions cpp in file included from home amol hip hip hipify clang src h in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include in file included from home amol hip hip hipify clang src dnn api functions cpp in file included from home amol hip hip hipify clang src dnn api types cpp in file included from home amol hip hip hipify clang src h in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h not foundin file included from home amol hip hip hipify clang src h include in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional hin file included from home amol hip hip hipify clang src fft api types cpp in file included from home amol hip hip hipify clang src h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include in file included from home amol hip hip hipify clang src complex api types cpp in file included from home amol hip hip hipify clang src h in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include in file included from home amol hip hip hipify clang src rand api functions cpp in file included from home amol hip hip hipify clang src h in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include home amol hip hip hipify clang src driver api functions cpp in file included from home amol hip hip hipify clang src h in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include in file included from home amol hip hip hipify clang src llvmcompat cpp in file included from home amol hip hip hipify clang src h in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include in file included from home amol hip hip hipify clang src argparse h fatal error clang tooling commonoptionsparser h file not found include clang tooling commonoptionsparser h home amol hip hip hipify clang src fft api functions cpp in file included from home amol hip hip hipify clang src h in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include in file included from home amol hip hip hipify clang src rand api types cpp in file included from in file included from home amol hip hip hipify clang src python cpp in file included from usr lib gcc linux gnu include c sstream in file included from usr lib gcc linux gnu include c istream in file included from usr lib gcc linux gnu include c ios in file included from usr lib gcc linux gnu include c iosfwd in file included from usr lib gcc linux gnu include c bits postypes h in file included from usr lib gcc linux gnu include c cwchar usr include wchar h fatal error stddef h file not found include in file included from home amol hip hip hipify clang src sparse api functions cpp in file included from home amol hip hip hipify clang src h in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include home amol hip hip hipify clang src h in file included from usr local include llvm adt stringref h in file included from usr local include llvm adt stlextras h in file included from usr local include llvm adt optional h in file included from usr local include llvm support alignof h usr lib gcc linux gnu include c cstddef fatal error stddef h file not found include in file included from home amol hip hip hipify clang src statistics cpp in file included from home amol hip hip hipify clang src statistics h in file included from usr lib gcc linux gnu include c chrono in file included from usr lib gcc linux gnu include c ctime usr include time h fatal error stddef h file not found include error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src complex api functions cpp o failed make error make waiting for unfinished jobs error generated in file included from home amol hip hip hipify clang src stringutils cpp in file included from home amol hip hip hipify clang src stringutils h in file included from usr lib gcc linux gnu include c string in file included from usr lib gcc linux gnu include c bits char traits h in file included from usr lib gcc linux gnu include c bits postypes h in file included from usr lib gcc linux gnu include c cwchar usr include wchar h fatal error stddef h file not found include cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src hipifyaction cpp o failed make error error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src runtime api types cpp o failed make error error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src api types cpp o failed make error error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src cpp o failed make error error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src blas api functions cpp o failed make error error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src perl cpp o failed make error home amol hip new llvm clang llvm src tools clang lib ast decl cpp bool clang vardecl checkinitisice const assertion init isvaluedependent failed error generated stack dump program arguments usr local bin clang triple unknown linux gnu emit obj disable free main file name statistics cpp mrelocation model static mthread model posix fmath errno masm verbose mconstructor aliases munwind tables fuse init array target cpu dwarf column info debugger tuning gdb momit leaf frame pointer coverage notes file home amol hip hip hipify clang build cmakefiles hipify clang dir src statistics cpp gcno resource dir usr local lib clang d gtest has rtti d hipify clang res usr local lib clang d ndebug d gnu source d debug d stdc constant macros d stdc format macros d stdc limit macros internal isystem usr lib gcc linux gnu include c internal isystem usr lib gcc linux gnu include linux gnu c internal isystem usr lib gcc linux gnu include linux gnu c internal isystem usr lib gcc linux gnu include c backward internal isystem usr local include internal isystem usr local lib clang include internal externc isystem usr include linux gnu internal externc isystem include internal externc isystem usr include std c fdeprecated macro fdebug compilation dir home amol hip hip hipify clang build ferror limit fmessage length fvisibility inlines hidden pthread fno rtti fobjc runtime gcc fdiagnostics show option fcolor diagnostics vectorize loops vectorize slp o cmakefiles hipify clang dir src statistics cpp o xcmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src argparse cpp o failed make error c home amol hip hip hipify clang src statistics cpp faddrsig usr lib gcc linux gnu include c bits locale facets nonio tcc current parser token ctype usr lib gcc linux gnu include c ostream parsing namespace std usr lib gcc linux gnu include c bits locale facets nonio tcc parsing namespace std std usr lib gcc linux gnu include c bits locale facets nonio tcc parsing function body usr lib gcc linux gnu include c bits locale facets nonio tcc in compound statement usr lib gcc linux gnu include c bits locale facets nonio tcc in compound statement error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src device functions cpp o failed make error error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src dnn api types cpp o failed make error error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src rand api functions cpp o failed make error error generated error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src driver api types cpp o failed make error error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src sparse api types cpp o failed make error cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src dnn api functions cpp o failed make error error generated error generated error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src complex api types cpp o failed make error cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src api functions cpp o failed make error error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src driver api functions cpp o failed make error cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src sparse api functions cpp o failed make error error generated error generated error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src blas api types cpp o failed make error cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src runtime api functions cpp o failed make error error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src rand api types cpp o failed make error cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src fft api types cpp o failed make error error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src fft api functions cpp o failed make error error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src stringutils cpp o failed make error error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src python cpp o failed make error error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src main cpp o failed make error error generated cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src llvmcompat cpp o failed make error llvm sys printstacktrace llvm raw ostream usr local bin clang llvm sys runsignalhandlers usr local bin clang signalhandler int usr local bin clang restore rt lib linux gnu libpthread so gsignal build glibc glibc signal sysdeps unix sysv linux raise c abort build glibc glibc stdlib abort c assert fail base build glibc glibc assert assert c lib linux gnu libc so clang vardecl checkinitisice const usr local bin clang domarkvardeclreferenced clang sema clang sourcelocation clang vardecl clang expr usr local bin clang clang sema builddeclrefexpr clang valuedecl clang qualtype clang exprvaluekind clang declarationnameinfo const clang cxxscopespec const clang nameddecl clang templateargumentlistinfo const usr local bin clang clang sema builddeclarationnameexpr clang cxxscopespec const clang declarationnameinfo const clang nameddecl clang nameddecl clang templateargumentlistinfo const bool usr local bin clang clang sema builddeclarationnameexpr clang cxxscopespec const clang lookupresult bool bool usr local bin clang clang sema classifyname clang scope clang cxxscopespec clang identifierinfo clang sourcelocation clang token const bool std unique ptr usr local bin clang clang parser tryannotatename bool std unique ptr usr local bin clang clang parser iscxxdeclarationspecifier clang parser tpresult bool usr local bin clang clang parser iscxxconditiondeclarationorinitstatement bool bool usr local bin clang clang parser parsecxxcondition clang actionresult clang sourcelocation clang sema conditionkind clang parser forrangeinfo usr local bin clang clang parser parseparenexprorcondition clang actionresult clang sema conditionresult clang sourcelocation clang sema conditionkind usr local bin clang clang parser parseifstatement clang sourcelocation usr local bin clang clang parser parsestatementordeclarationafterattributes llvm smallvector clang parser allowedconstructskind clang sourcelocation clang parser parsedattributeswithrange usr local bin clang clang parser parsestatementordeclaration llvm smallvector clang parser allowedconstructskind clang sourcelocation usr local bin clang clang parser parsecompoundstatementbody bool usr local bin clang clang parser parsecompoundstatement bool unsigned int usr local bin clang clang parser parsestatementordeclarationafterattributes llvm smallvector clang parser allowedconstructskind clang sourcelocation clang parser parsedattributeswithrange usr local bin clang clang parser parsestatementordeclaration llvm smallvector clang parser allowedconstructskind clang sourcelocation usr local bin clang clang parser parsestatement clang sourcelocation bool usr local bin clang clang parser parseforstatement clang sourcelocation usr local bin clang clang parser parsestatementordeclarationafterattributes llvm smallvector clang parser allowedconstructskind clang sourcelocation clang parser parsedattributeswithrange usr local bin clang clang parser parsestatementordeclaration llvm smallvector clang parser allowedconstructskind clang sourcelocation usr local bin clang clang parser parsecompoundstatementbody bool usr local bin clang clang parser parsefunctionstatementbody clang decl clang parser parsescope usr local bin clang clang parser parsefunctiondefinition clang parsingdeclarator clang parser parsedtemplateinfo const clang parser lateparsedattrlist usr local bin clang clang parser parsesingledeclarationaftertemplate clang declaratorcontext clang parser parsedtemplateinfo const clang parsingdeclraiiobject clang sourcelocation clang parsedattributes clang accessspecifier usr local bin clang clang parser parsetemplatedeclarationorspecialization clang declaratorcontext clang sourcelocation clang parsedattributes clang accessspecifier usr local bin clang clang parser parsedeclarationstartingwithtemplate clang declaratorcontext clang sourcelocation clang parsedattributes clang accessspecifier usr local bin clang clang parser parsedeclaration clang declaratorcontext clang sourcelocation clang parser parsedattributeswithrange usr local bin clang clang parser parseexternaldeclaration clang parser parsedattributeswithrange clang parsingdeclspec usr local bin clang clang parser parseinnernamespace llvm smallvector const unsigned int clang sourcelocation clang parsedattributes clang balanceddelimitertracker usr local bin clang clang parser parsenamespace clang declaratorcontext clang sourcelocation clang sourcelocation usr local bin clang clang parser parsedeclaration clang declaratorcontext clang sourcelocation clang parser parsedattributeswithrange usr local bin clang clang parser parseexternaldeclaration clang parser parsedattributeswithrange clang parsingdeclspec usr local bin clang clang parser parseinnernamespace llvm smallvector const unsigned int clang sourcelocation clang parsedattributes clang balanceddelimitertracker usr local bin clang clang parser parsenamespace clang declaratorcontext clang sourcelocation clang sourcelocation usr local bin clang clang parser parsedeclaration clang declaratorcontext clang sourcelocation clang parser parsedattributeswithrange usr local bin clang clang parser parseexternaldeclaration clang parser parsedattributeswithrange clang parsingdeclspec usr local bin clang clang parser parsetopleveldecl clang opaqueptr usr local bin clang clang parseast clang sema bool bool usr local bin clang clang codegenaction executeaction usr local bin clang clang frontendaction execute usr local bin clang clang compilerinstance executeaction clang frontendaction usr local bin clang clang executecompilerinvocation clang compilerinstance usr local bin clang main llvm arrayref char const void usr local bin clang main usr local bin clang libc start main build glibc glibc csu csu libc start c start usr local bin clang clang error unable to execute command aborted core dumped clang error clang frontend command failed due to signal use v to see invocation clang version tags release final target unknown linux gnu thread model posix installeddir usr local bin clang note diagnostic msg please submit a bug report to and include the crash backtrace preprocessed source and associated run script clang note diagnostic msg error generating preprocessed source s cmakefiles hipify clang dir build make recipe for target cmakefiles hipify clang dir src statistics cpp o failed make error cmakefiles recipe for target cmakefiles hipify clang dir all failed make error makefile recipe for target all failed make error | 0 |
7,921 | 7,084,957,359 | IssuesEvent | 2018-01-11 09:16:40 | DiscipleTools/disciple-tools-theme | https://api.github.com/repos/DiscipleTools/disciple-tools-theme | closed | [CLOSED] fix email Security Issue | security | <a href="https://github.com/corsacca"><img src="https://avatars1.githubusercontent.com/u/24901539?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [corsacca](https://github.com/corsacca)**
_Friday Oct 20, 2017 at 12:03 GMT_
_Originally opened as https://github.com/DiscipleTools/disciple-tools/issues/211_
----
described here: https://www.bleepingcomputer.com/news/security/wordpress-zero-day-could-expose-password-reset-emails/
This hack involves sending reset password emails hoping that email server will reply or bounce the email back to the hackers email address.
| True | [CLOSED] fix email Security Issue - <a href="https://github.com/corsacca"><img src="https://avatars1.githubusercontent.com/u/24901539?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [corsacca](https://github.com/corsacca)**
_Friday Oct 20, 2017 at 12:03 GMT_
_Originally opened as https://github.com/DiscipleTools/disciple-tools/issues/211_
----
described here: https://www.bleepingcomputer.com/news/security/wordpress-zero-day-could-expose-password-reset-emails/
This hack involves sending reset password emails hoping that email server will reply or bounce the email back to the hackers email address.
| non_priority | fix email security issue issue by friday oct at gmt originally opened as described here this hack involves sending reset password emails hoping that email server will reply or bounce the email back to the hackers email address | 0 |
308,398 | 23,246,422,444 | IssuesEvent | 2022-08-03 20:40:05 | jhipster/jhipster-lite | https://api.github.com/repos/jhipster/jhipster-lite | closed | Add keycloak startup command | area: documentation:books: theme: security server: spring boot server: java | Add keycloak startup command in Spring OAuth2 module
```
docker-compose -f src/main/docker/keycloak.yml up -d
``` | 1.0 | Add keycloak startup command - Add keycloak startup command in Spring OAuth2 module
```
docker-compose -f src/main/docker/keycloak.yml up -d
``` | non_priority | add keycloak startup command add keycloak startup command in spring module docker compose f src main docker keycloak yml up d | 0 |
67,130 | 8,074,999,014 | IssuesEvent | 2018-08-07 02:48:14 | GitHawkApp/GitHawk | https://api.github.com/repos/GitHawkApp/GitHawk | closed | Resign keyboard when tapping manage button | design starter-task | Kind of annoying to have the kb flying around
<details>
<summary>Bug Report Dump (Auto-generated)</summary>
<pre>
Version 1.22.0 (1532006598)
Device: iPhone X (iOS 11.4.1)
TestFlight: true
</pre>
</details> | 1.0 | Resign keyboard when tapping manage button - Kind of annoying to have the kb flying around
<details>
<summary>Bug Report Dump (Auto-generated)</summary>
<pre>
Version 1.22.0 (1532006598)
Device: iPhone X (iOS 11.4.1)
TestFlight: true
</pre>
</details> | non_priority | resign keyboard when tapping manage button kind of annoying to have the kb flying around bug report dump auto generated version device iphone x ios testflight true | 0 |
129,206 | 27,418,479,335 | IssuesEvent | 2023-03-01 15:14:10 | strangerstudios/pmpro-mailchimp | https://api.github.com/repos/strangerstudios/pmpro-mailchimp | closed | Formatting Improvements for the "Join our mailing list" section at checkout | Type: Localization Type: Enhancement Status: Needs Code Difficulty: Easy Blocking Next Release | After our move to table-free checkout page, this Add On was not updated to reflect new core styling, specifically: https://github.com/strangerstudios/pmpro-mailchimp/blob/master/pmpro-mailchimp.php#L495-L508
Also, the "textdomain" should be updated in the translation strings from 'pmpro' to 'pmpro-mailchimp'. | 1.0 | Formatting Improvements for the "Join our mailing list" section at checkout - After our move to table-free checkout page, this Add On was not updated to reflect new core styling, specifically: https://github.com/strangerstudios/pmpro-mailchimp/blob/master/pmpro-mailchimp.php#L495-L508
Also, the "textdomain" should be updated in the translation strings from 'pmpro' to 'pmpro-mailchimp'. | non_priority | formatting improvements for the join our mailing list section at checkout after our move to table free checkout page this add on was not updated to reflect new core styling specifically also the textdomain should be updated in the translation strings from pmpro to pmpro mailchimp | 0 |
438,996 | 30,672,890,185 | IssuesEvent | 2023-07-26 01:02:05 | Arize-ai/open-inference-spec | https://api.github.com/repos/Arize-ai/open-inference-spec | closed | [OpenInference] add new data types and specifiers | documentation | New Data Types:
- [ ] ID
- [ ] URL
- [ ] List types
Data Types to Remove:
- [ ] vector
New Specifiers:
- [ ] embedding
- [ ] retrieved_document_ids
- [ ] retrieved_document_scores | 1.0 | [OpenInference] add new data types and specifiers - New Data Types:
- [ ] ID
- [ ] URL
- [ ] List types
Data Types to Remove:
- [ ] vector
New Specifiers:
- [ ] embedding
- [ ] retrieved_document_ids
- [ ] retrieved_document_scores | non_priority | add new data types and specifiers new data types id url list types data types to remove vector new specifiers embedding retrieved document ids retrieved document scores | 0 |
43,014 | 5,561,039,502 | IssuesEvent | 2017-03-24 21:13:00 | dotnet/roslyn | https://api.github.com/repos/dotnet/roslyn | closed | Enhanced C#: a friendly hello | Area-Language Design Discussion | I'm terribly embarrassed.
For the last few months I've been working on a tool called LeMP that adds new features to C#. I recently published its "macro" reference manual. This month I was going to start publicizing my "Enhanced C#" project when I discovered that the design of C# 7 had already started well before C# 6 was officially released - and even more shocking, that this design work was being done "in public" right on GitHub!
It kills me that I didn't realize I could have participated in this process, and that "my" C# was drifting apart from C# 7 for over a year. Oh well - it is what it is, and I hope that something useful can still be salvaged out of my work.
So, this post is to inform you about Enhanced C# - where it came from, and what it offers that C# 7 does not.
## A brief history
As a class project in my final year of university, I extended a compiler with a new feature (unit type inference with implicit polymorphism), but (to make a short story shorter) the authors of the language weren't interested in adding that feature to their language. This got me thinking about our "benevolent dictatorship" model of language development and how it stopped me, as a developer, from making improvements to the languages I relied on. Since I had already been coding for 15 years by that time, I was getting quite annoyed about writing boilerplate, and finding bugs at runtime that a "sufficiently smart compiler" could have found given a better type system.
So in 2007 I thought of a concept for a compiler called "Loyc" - Language of your choice - in which I wanted to create the magical ability to compile different languages with a single compiler, and also allow users to add syntax and semantics to existing languages. This system would democratize language design, by allowing third parties to add features to existing languages, and allowing language prototypes and DSLs to seamlessly interoperate with "grown up" languages like C#. But my ideas proved too hard to flesh out. I wanted to be able to combine unrelated language extensions written by different people and have them "just work together", but that's easier said than done.
After a couple years I got discouraged and gave up awhile (instead I worked on [data structures](http://core.ecsharp.net/collections/) ([alt link](http://core.loyc.net/collections/)), among other things), but in 2012 I changed course with a project that I thought would be easier and more fun: enhancing C# with all the features I thought it ought to have. I simply called it Enhanced C#. It started as a simple and [very, very long wish list](https://github.com/qwertie/ecsharp/blob/master/Doc/EC%23.cs), with a quick design sketch of each new feature. Having done that I reviewed all the feature requests on UserVoice and noticed a big gaping hole: I hadn't satisfied one of the most popular requests, ["INotifyPropertyChanged"](https://visualstudio.uservoice.com/forums/121579-visual-studio-2015/suggestions/2255378-inotifypropertychanged). So at that point I finally went out and spent three weeks learning about LISP (as I should have done years ago), and some time learning about Nemerle macros. At that point (Oct. 2012) I quickly refocused my plans around a macro processor and called it EC# 2.0, even though 1.0 was never written. I realized that many of the features I wanted in C# could be accomplished with macros (and that a macro processor doesn't require a full compiler, which was nice since I didn't have one) so the macro processor became my first priority.
So "Loyc", I eventually decided, would not be a compiler anymore, but just a loose collection of concepts and libraries related to (i) interoperability, (ii) conversions between programming languages, (iii) parsing and other compiler technology, which I now call the "Loyc initiative"; I've had trouble articulating the theme of it... today I'll say the theme of Loyc is "code that applies to multiple languages", because I want to (1) write tools that are embedded in compilers for multiple langauges, and (2) enable people, especially library authors, to write one piece of code that cross-compiles into many langauges. One guy wants to call it [acmeism](http://acmeism.org/) but that doesn't seem like the right name - I'd call it, I dunno, multiglotism or simply, well, loyc.
## EC# and Roslyn
Roslyn's timing didn't work out for me. When I conceived EC#, Roslyn was closed source. I researched it a bit and found that it would only be useful for analysis tasks - not to change C# in any way. That wasn't so bad; but I wanted to explore "radical" ideas, which might be difficult if I had to do things the "Roslyn way". That said, I was _inspired_ by Roslyn; for instance the original implementation of "Loyc trees" - the AST of EC# - was a home-grown Red-Green tree, although I found my mutable syntax trees to be inconvenient in practice (probably I didn't design them right the first time) and rewrote them as green-trees-only (immutable - I thought I might rewrite the "red" part later, but I got used to working with immutable trees and now I don't feel a strong need for mutable ones.)
By the time MS announced they were open-sourcing Roslyn (April 2014), I had been working on Enhanced C# and related projects (LLLPG, Loyc trees and LES) for well over a year, and by that point I felt I had gone too far down my own path to consider trying to build on top of Roslyn (today I wish I could have Roslyn as a back-end, but I don't think I have time, nor a volunteer willing to work on it).
## LeMP
EC# still is not a "compiler" in the traditonal sense, but it's still useful and usable as-is thanks to its key feature, the Lexical Macro Processor, or LeMP for short. It is typically used as a Visual Studio extension, but is also available as a command-line tool and a Linux-compatible GUI.
Through macros, I implemented (in the past few months) several of the features that you guys have been discussing for more than a year:
- Creating ‘out’ variables in-situ, e.g. `int? Parse(string s) => int.Parse(s, out int x) ? (int?)x : null;`
- Code Contracts via annotations on the method signature
- Tuples (positional only) with deconstruction
- Algebraic data types
- Patern matching
(They aren't as polished as the C# 7 features will be, because of techical limitations of lexical macros and because I'm just one guy.)
It also has numerous other features:
- A maximally flexible alternative to "primary constructors"
- Code quotations and code pattern matching (comparable to LISP and Nemerle), which is useful for writing macros, for code analysis, code generation and even (potentially) reading/writing JSON and LES files (a use case I haven't written about yet).
- Method forwarding, for doing the decorator pattern more easily.
- Declaring variables and writing code sequences in expressions (like the `;` operator that was sadly not added to C# 6)
- The "quick binding" operator
- `on_finally` which works like Swift's `defer`, and related macros (`on_return`, `on_throw`)
- `replace` and `unroll` for generating boilerplate (although after reading about Nim, I think there's a better way to do the `unroll` feature)
- A `with` statement based on the `With` statement in Visual Basic
- An LL(k) parser generator called LLLPG (massive chicken-and-egg problem there: you write LLLPG grammars in EC#, while the EC# grammar is written in LLLPG)
- And last but not least, users can write their own macros.
The other parts of EC# that exist - the parser and "pretty printer" - support some interesting additional features such as symbols, triple-quoted string literals, attributes on any expression, etc. However, the majority of the syntactic differences between EC# and C# 6 are designed to support the macro processor.
An important theoretical innovation of Enhanced C# is the use of simple syntax trees internally, vaguely like LISP. This is intended to make it easier to (1) convert code between programming languages and (2) to communicate syntax trees compactly.
## What now?
Well, I'm not 100% decided about what to do now, knowing that the C# open design process exists and that C# 7 is shaping up to be really nice.
I don't intend to throw the whole thing away, especially since there are major use cases for EC# that C# 7 doesn't address. So in the coming weeks I will change the pattern matching syntax to that planned for C# 7, implement the new syntax for tuple types (minus named parameters, which cannot be well-supported in a _lexical_ macro), and add those "record class" thingies (even though I don't think the C# team has taken the right approach on those.)
But in the long run, is it worthwhile to continue working on EC#, or should I instead devote my time to lobbying the C# team to do the features I want? (beware, I can talk a lot...)
In fact, those are far from my only options - I've been closely following the development of WebAssembly and I'd like to do something related to interoperability and WebAssembly, mainly because .NET has not turned out to be the cross-language interoperability panacea that the world needs. And I'd love to make the world's most widely useful programming language (which is not EC#, because we all know how hard it is to improve a language given the backward compatibility constraint). The main reasons to keep going with EC# are (1) that I have a large codebase already written, and (2) that after 8 years alone I finally have a volunteer that wants to help build it (hi @jonathanvdc!)
I do suspect (hope) there are some developers that would find value in EC# as a "desugaring" compiler that converts much of C# 7 to C# 5. Plus, LeMP is a neat tool for reducing boilerplate, "code find and replace" operations, and metaprogramming, so I really want to polish it up enough that I finally win some users.
There is so much more I could say, would have liked to say, and would still like to say to the C# design team... but in case this is the first you've heard of Enhanced C# or LeMP, you might find this to be a lot to take in - just like for me, C# 7 was a lot to take in! So I'll avoid rambling much longer. I hope that, in time, I can win your respect and that you will not "write me off" in a sentence or two, or without saying a word, an eventuality I have learned to emotionally brace for. I definitely have some opinions that would be opposed by the usual commentators here - but on the other hand, I think the new C# 7 features are mostly really nice and I'll be glad to have them.
So if this wasn't TLDR enough for you, I hope you'll enjoy learning about EC# - think of it as how C# 7 might have looked in a parallel universe.
Links:
- [EC# for normal coders](http://ecsharp.net/ecs/for-normal-coders.html) (because [EC# for programming language nerds](http://ecsharp.net/ecs/for-programming-language-pundits.html) is a bit old)
- [LeMP macro reference manual](http://ecsharp.net/lemp/reference.html)
| 1.0 | Enhanced C#: a friendly hello - I'm terribly embarrassed.
For the last few months I've been working on a tool called LeMP that adds new features to C#. I recently published its "macro" reference manual. This month I was going to start publicizing my "Enhanced C#" project when I discovered that the design of C# 7 had already started well before C# 6 was officially released - and even more shocking, that this design work was being done "in public" right on GitHub!
It kills me that I didn't realize I could have participated in this process, and that "my" C# was drifting apart from C# 7 for over a year. Oh well - it is what it is, and I hope that something useful can still be salvaged out of my work.
So, this post is to inform you about Enhanced C# - where it came from, and what it offers that C# 7 does not.
## A brief history
As a class project in my final year of university, I extended a compiler with a new feature (unit type inference with implicit polymorphism), but (to make a short story shorter) the authors of the language weren't interested in adding that feature to their language. This got me thinking about our "benevolent dictatorship" model of language development and how it stopped me, as a developer, from making improvements to the languages I relied on. Since I had already been coding for 15 years by that time, I was getting quite annoyed about writing boilerplate, and finding bugs at runtime that a "sufficiently smart compiler" could have found given a better type system.
So in 2007 I thought of a concept for a compiler called "Loyc" - Language of your choice - in which I wanted to create the magical ability to compile different languages with a single compiler, and also allow users to add syntax and semantics to existing languages. This system would democratize language design, by allowing third parties to add features to existing languages, and allowing language prototypes and DSLs to seamlessly interoperate with "grown up" languages like C#. But my ideas proved too hard to flesh out. I wanted to be able to combine unrelated language extensions written by different people and have them "just work together", but that's easier said than done.
After a couple years I got discouraged and gave up awhile (instead I worked on [data structures](http://core.ecsharp.net/collections/) ([alt link](http://core.loyc.net/collections/)), among other things), but in 2012 I changed course with a project that I thought would be easier and more fun: enhancing C# with all the features I thought it ought to have. I simply called it Enhanced C#. It started as a simple and [very, very long wish list](https://github.com/qwertie/ecsharp/blob/master/Doc/EC%23.cs), with a quick design sketch of each new feature. Having done that I reviewed all the feature requests on UserVoice and noticed a big gaping hole: I hadn't satisfied one of the most popular requests, ["INotifyPropertyChanged"](https://visualstudio.uservoice.com/forums/121579-visual-studio-2015/suggestions/2255378-inotifypropertychanged). So at that point I finally went out and spent three weeks learning about LISP (as I should have done years ago), and some time learning about Nemerle macros. At that point (Oct. 2012) I quickly refocused my plans around a macro processor and called it EC# 2.0, even though 1.0 was never written. I realized that many of the features I wanted in C# could be accomplished with macros (and that a macro processor doesn't require a full compiler, which was nice since I didn't have one) so the macro processor became my first priority.
So "Loyc", I eventually decided, would not be a compiler anymore, but just a loose collection of concepts and libraries related to (i) interoperability, (ii) conversions between programming languages, (iii) parsing and other compiler technology, which I now call the "Loyc initiative"; I've had trouble articulating the theme of it... today I'll say the theme of Loyc is "code that applies to multiple languages", because I want to (1) write tools that are embedded in compilers for multiple langauges, and (2) enable people, especially library authors, to write one piece of code that cross-compiles into many langauges. One guy wants to call it [acmeism](http://acmeism.org/) but that doesn't seem like the right name - I'd call it, I dunno, multiglotism or simply, well, loyc.
## EC# and Roslyn
Roslyn's timing didn't work out for me. When I conceived EC#, Roslyn was closed source. I researched it a bit and found that it would only be useful for analysis tasks - not to change C# in any way. That wasn't so bad; but I wanted to explore "radical" ideas, which might be difficult if I had to do things the "Roslyn way". That said, I was _inspired_ by Roslyn; for instance the original implementation of "Loyc trees" - the AST of EC# - was a home-grown Red-Green tree, although I found my mutable syntax trees to be inconvenient in practice (probably I didn't design them right the first time) and rewrote them as green-trees-only (immutable - I thought I might rewrite the "red" part later, but I got used to working with immutable trees and now I don't feel a strong need for mutable ones.)
By the time MS announced they were open-sourcing Roslyn (April 2014), I had been working on Enhanced C# and related projects (LLLPG, Loyc trees and LES) for well over a year, and by that point I felt I had gone too far down my own path to consider trying to build on top of Roslyn (today I wish I could have Roslyn as a back-end, but I don't think I have time, nor a volunteer willing to work on it).
## LeMP
EC# still is not a "compiler" in the traditonal sense, but it's still useful and usable as-is thanks to its key feature, the Lexical Macro Processor, or LeMP for short. It is typically used as a Visual Studio extension, but is also available as a command-line tool and a Linux-compatible GUI.
Through macros, I implemented (in the past few months) several of the features that you guys have been discussing for more than a year:
- Creating ‘out’ variables in-situ, e.g. `int? Parse(string s) => int.Parse(s, out int x) ? (int?)x : null;`
- Code Contracts via annotations on the method signature
- Tuples (positional only) with deconstruction
- Algebraic data types
- Patern matching
(They aren't as polished as the C# 7 features will be, because of techical limitations of lexical macros and because I'm just one guy.)
It also has numerous other features:
- A maximally flexible alternative to "primary constructors"
- Code quotations and code pattern matching (comparable to LISP and Nemerle), which is useful for writing macros, for code analysis, code generation and even (potentially) reading/writing JSON and LES files (a use case I haven't written about yet).
- Method forwarding, for doing the decorator pattern more easily.
- Declaring variables and writing code sequences in expressions (like the `;` operator that was sadly not added to C# 6)
- The "quick binding" operator
- `on_finally` which works like Swift's `defer`, and related macros (`on_return`, `on_throw`)
- `replace` and `unroll` for generating boilerplate (although after reading about Nim, I think there's a better way to do the `unroll` feature)
- A `with` statement based on the `With` statement in Visual Basic
- An LL(k) parser generator called LLLPG (massive chicken-and-egg problem there: you write LLLPG grammars in EC#, while the EC# grammar is written in LLLPG)
- And last but not least, users can write their own macros.
The other parts of EC# that exist - the parser and "pretty printer" - support some interesting additional features such as symbols, triple-quoted string literals, attributes on any expression, etc. However, the majority of the syntactic differences between EC# and C# 6 are designed to support the macro processor.
An important theoretical innovation of Enhanced C# is the use of simple syntax trees internally, vaguely like LISP. This is intended to make it easier to (1) convert code between programming languages and (2) to communicate syntax trees compactly.
## What now?
Well, I'm not 100% decided about what to do now, knowing that the C# open design process exists and that C# 7 is shaping up to be really nice.
I don't intend to throw the whole thing away, especially since there are major use cases for EC# that C# 7 doesn't address. So in the coming weeks I will change the pattern matching syntax to that planned for C# 7, implement the new syntax for tuple types (minus named parameters, which cannot be well-supported in a _lexical_ macro), and add those "record class" thingies (even though I don't think the C# team has taken the right approach on those.)
But in the long run, is it worthwhile to continue working on EC#, or should I instead devote my time to lobbying the C# team to do the features I want? (beware, I can talk a lot...)
In fact, those are far from my only options - I've been closely following the development of WebAssembly and I'd like to do something related to interoperability and WebAssembly, mainly because .NET has not turned out to be the cross-language interoperability panacea that the world needs. And I'd love to make the world's most widely useful programming language (which is not EC#, because we all know how hard it is to improve a language given the backward compatibility constraint). The main reasons to keep going with EC# are (1) that I have a large codebase already written, and (2) that after 8 years alone I finally have a volunteer that wants to help build it (hi @jonathanvdc!)
I do suspect (hope) there are some developers that would find value in EC# as a "desugaring" compiler that converts much of C# 7 to C# 5. Plus, LeMP is a neat tool for reducing boilerplate, "code find and replace" operations, and metaprogramming, so I really want to polish it up enough that I finally win some users.
There is so much more I could say, would have liked to say, and would still like to say to the C# design team... but in case this is the first you've heard of Enhanced C# or LeMP, you might find this to be a lot to take in - just like for me, C# 7 was a lot to take in! So I'll avoid rambling much longer. I hope that, in time, I can win your respect and that you will not "write me off" in a sentence or two, or without saying a word, an eventuality I have learned to emotionally brace for. I definitely have some opinions that would be opposed by the usual commentators here - but on the other hand, I think the new C# 7 features are mostly really nice and I'll be glad to have them.
So if this wasn't TLDR enough for you, I hope you'll enjoy learning about EC# - think of it as how C# 7 might have looked in a parallel universe.
Links:
- [EC# for normal coders](http://ecsharp.net/ecs/for-normal-coders.html) (because [EC# for programming language nerds](http://ecsharp.net/ecs/for-programming-language-pundits.html) is a bit old)
- [LeMP macro reference manual](http://ecsharp.net/lemp/reference.html)
| non_priority | enhanced c a friendly hello i m terribly embarrassed for the last few months i ve been working on a tool called lemp that adds new features to c i recently published its macro reference manual this month i was going to start publicizing my enhanced c project when i discovered that the design of c had already started well before c was officially released and even more shocking that this design work was being done in public right on github it kills me that i didn t realize i could have participated in this process and that my c was drifting apart from c for over a year oh well it is what it is and i hope that something useful can still be salvaged out of my work so this post is to inform you about enhanced c where it came from and what it offers that c does not a brief history as a class project in my final year of university i extended a compiler with a new feature unit type inference with implicit polymorphism but to make a short story shorter the authors of the language weren t interested in adding that feature to their language this got me thinking about our benevolent dictatorship model of language development and how it stopped me as a developer from making improvements to the languages i relied on since i had already been coding for years by that time i was getting quite annoyed about writing boilerplate and finding bugs at runtime that a sufficiently smart compiler could have found given a better type system so in i thought of a concept for a compiler called loyc language of your choice in which i wanted to create the magical ability to compile different languages with a single compiler and also allow users to add syntax and semantics to existing languages this system would democratize language design by allowing third parties to add features to existing languages and allowing language prototypes and dsls to seamlessly interoperate with grown up languages like c but my ideas proved too hard to flesh out i wanted to be able to combine unrelated language extensions written by different people and have them just work together but that s easier said than done after a couple years i got discouraged and gave up awhile instead i worked on among other things but in i changed course with a project that i thought would be easier and more fun enhancing c with all the features i thought it ought to have i simply called it enhanced c it started as a simple and with a quick design sketch of each new feature having done that i reviewed all the feature requests on uservoice and noticed a big gaping hole i hadn t satisfied one of the most popular requests so at that point i finally went out and spent three weeks learning about lisp as i should have done years ago and some time learning about nemerle macros at that point oct i quickly refocused my plans around a macro processor and called it ec even though was never written i realized that many of the features i wanted in c could be accomplished with macros and that a macro processor doesn t require a full compiler which was nice since i didn t have one so the macro processor became my first priority so loyc i eventually decided would not be a compiler anymore but just a loose collection of concepts and libraries related to i interoperability ii conversions between programming languages iii parsing and other compiler technology which i now call the loyc initiative i ve had trouble articulating the theme of it today i ll say the theme of loyc is code that applies to multiple languages because i want to write tools that are embedded in compilers for multiple langauges and enable people especially library authors to write one piece of code that cross compiles into many langauges one guy wants to call it but that doesn t seem like the right name i d call it i dunno multiglotism or simply well loyc ec and roslyn roslyn s timing didn t work out for me when i conceived ec roslyn was closed source i researched it a bit and found that it would only be useful for analysis tasks not to change c in any way that wasn t so bad but i wanted to explore radical ideas which might be difficult if i had to do things the roslyn way that said i was inspired by roslyn for instance the original implementation of loyc trees the ast of ec was a home grown red green tree although i found my mutable syntax trees to be inconvenient in practice probably i didn t design them right the first time and rewrote them as green trees only immutable i thought i might rewrite the red part later but i got used to working with immutable trees and now i don t feel a strong need for mutable ones by the time ms announced they were open sourcing roslyn april i had been working on enhanced c and related projects lllpg loyc trees and les for well over a year and by that point i felt i had gone too far down my own path to consider trying to build on top of roslyn today i wish i could have roslyn as a back end but i don t think i have time nor a volunteer willing to work on it lemp ec still is not a compiler in the traditonal sense but it s still useful and usable as is thanks to its key feature the lexical macro processor or lemp for short it is typically used as a visual studio extension but is also available as a command line tool and a linux compatible gui through macros i implemented in the past few months several of the features that you guys have been discussing for more than a year creating ‘out’ variables in situ e g int parse string s int parse s out int x int x null code contracts via annotations on the method signature tuples positional only with deconstruction algebraic data types patern matching they aren t as polished as the c features will be because of techical limitations of lexical macros and because i m just one guy it also has numerous other features a maximally flexible alternative to primary constructors code quotations and code pattern matching comparable to lisp and nemerle which is useful for writing macros for code analysis code generation and even potentially reading writing json and les files a use case i haven t written about yet method forwarding for doing the decorator pattern more easily declaring variables and writing code sequences in expressions like the operator that was sadly not added to c the quick binding operator on finally which works like swift s defer and related macros on return on throw replace and unroll for generating boilerplate although after reading about nim i think there s a better way to do the unroll feature a with statement based on the with statement in visual basic an ll k parser generator called lllpg massive chicken and egg problem there you write lllpg grammars in ec while the ec grammar is written in lllpg and last but not least users can write their own macros the other parts of ec that exist the parser and pretty printer support some interesting additional features such as symbols triple quoted string literals attributes on any expression etc however the majority of the syntactic differences between ec and c are designed to support the macro processor an important theoretical innovation of enhanced c is the use of simple syntax trees internally vaguely like lisp this is intended to make it easier to convert code between programming languages and to communicate syntax trees compactly what now well i m not decided about what to do now knowing that the c open design process exists and that c is shaping up to be really nice i don t intend to throw the whole thing away especially since there are major use cases for ec that c doesn t address so in the coming weeks i will change the pattern matching syntax to that planned for c implement the new syntax for tuple types minus named parameters which cannot be well supported in a lexical macro and add those record class thingies even though i don t think the c team has taken the right approach on those but in the long run is it worthwhile to continue working on ec or should i instead devote my time to lobbying the c team to do the features i want beware i can talk a lot in fact those are far from my only options i ve been closely following the development of webassembly and i d like to do something related to interoperability and webassembly mainly because net has not turned out to be the cross language interoperability panacea that the world needs and i d love to make the world s most widely useful programming language which is not ec because we all know how hard it is to improve a language given the backward compatibility constraint the main reasons to keep going with ec are that i have a large codebase already written and that after years alone i finally have a volunteer that wants to help build it hi jonathanvdc i do suspect hope there are some developers that would find value in ec as a desugaring compiler that converts much of c to c plus lemp is a neat tool for reducing boilerplate code find and replace operations and metaprogramming so i really want to polish it up enough that i finally win some users there is so much more i could say would have liked to say and would still like to say to the c design team but in case this is the first you ve heard of enhanced c or lemp you might find this to be a lot to take in just like for me c was a lot to take in so i ll avoid rambling much longer i hope that in time i can win your respect and that you will not write me off in a sentence or two or without saying a word an eventuality i have learned to emotionally brace for i definitely have some opinions that would be opposed by the usual commentators here but on the other hand i think the new c features are mostly really nice and i ll be glad to have them so if this wasn t tldr enough for you i hope you ll enjoy learning about ec think of it as how c might have looked in a parallel universe links because is a bit old | 0 |
162,355 | 12,652,535,579 | IssuesEvent | 2020-06-17 03:54:42 | eclipse/openj9 | https://api.github.com/repos/eclipse/openj9 | closed | AArch64: Failure in system test SC_Softmx_JitAot_Linux_0 | arch:aarch64 comp:jit:aot test excluded test failure | Failure link
https://ci.eclipse.org/openj9/job/Test_openjdk11_j9_extended.system_aarch64_linux_Personal/4/
SC_Softmx_JitAot_Linux_0
The test runs the VM with `-Xscmaxaot10k -Xscmaxjitdata10k`, and expects the AOT data space to be full. But the file `stderr_combined.txt` says the JIT data store is full instead with AArch64, as shown below.
```
[-Xshareclasses persistent cache enabled]
[-Xshareclasses verbose output enabled]
JVMSHRC236I Created shared classes persistent cache SCC_SysTest_Workload_Cache
JVMSHRC246I Attached shared classes persistent cache SCC_SysTest_Workload_Cache
JVMSHRC765I Memory page protection on runtime data, string read-write data and partially filled pages is successfully enabled
JVMSHRC168I Total shared class bytes read=6513136. Total bytes stored=6229620
JVMSHRC818I Total unstored bytes due to the setting of shared cache soft max is 0. Unstored AOT bytes due to the setting of -Xscmaxaot is 0. Unstored JIT bytes due to the setting of -Xscmaxjitdata is 1380352.
[-Xshareclasses persistent cache enabled]
[-Xshareclasses verbose output enabled]
JVMSHRC237I Opened shared classes persistent cache SCC_SysTest_Workload_Cache
JVMSHRC246I Attached shared classes persistent cache SCC_SysTest_Workload_Cache
JVMSHRC765I Memory page protection on runtime data, string read-write data and partially filled pages is successfully enabled
JVMSHRC774I The space for JIT data in shared cache "SCC_SysTest_Workload_Cache" is full.
JVMSHRC168I Total shared class bytes read=10141164. Total bytes stored=4182444
JVMSHRC818I Total unstored bytes due to the setting of shared cache soft max is 0. Unstored AOT bytes due to the setting of -Xscmaxaot is 0. Unstored JIT bytes due to the setting of -Xscmaxjitdata is 1355776.
```
AOT is enabled in the AArch64 runtime. | 2.0 | AArch64: Failure in system test SC_Softmx_JitAot_Linux_0 - Failure link
https://ci.eclipse.org/openj9/job/Test_openjdk11_j9_extended.system_aarch64_linux_Personal/4/
SC_Softmx_JitAot_Linux_0
The test runs the VM with `-Xscmaxaot10k -Xscmaxjitdata10k`, and expects the AOT data space to be full. But the file `stderr_combined.txt` says the JIT data store is full instead with AArch64, as shown below.
```
[-Xshareclasses persistent cache enabled]
[-Xshareclasses verbose output enabled]
JVMSHRC236I Created shared classes persistent cache SCC_SysTest_Workload_Cache
JVMSHRC246I Attached shared classes persistent cache SCC_SysTest_Workload_Cache
JVMSHRC765I Memory page protection on runtime data, string read-write data and partially filled pages is successfully enabled
JVMSHRC168I Total shared class bytes read=6513136. Total bytes stored=6229620
JVMSHRC818I Total unstored bytes due to the setting of shared cache soft max is 0. Unstored AOT bytes due to the setting of -Xscmaxaot is 0. Unstored JIT bytes due to the setting of -Xscmaxjitdata is 1380352.
[-Xshareclasses persistent cache enabled]
[-Xshareclasses verbose output enabled]
JVMSHRC237I Opened shared classes persistent cache SCC_SysTest_Workload_Cache
JVMSHRC246I Attached shared classes persistent cache SCC_SysTest_Workload_Cache
JVMSHRC765I Memory page protection on runtime data, string read-write data and partially filled pages is successfully enabled
JVMSHRC774I The space for JIT data in shared cache "SCC_SysTest_Workload_Cache" is full.
JVMSHRC168I Total shared class bytes read=10141164. Total bytes stored=4182444
JVMSHRC818I Total unstored bytes due to the setting of shared cache soft max is 0. Unstored AOT bytes due to the setting of -Xscmaxaot is 0. Unstored JIT bytes due to the setting of -Xscmaxjitdata is 1355776.
```
AOT is enabled in the AArch64 runtime. | non_priority | failure in system test sc softmx jitaot linux failure link sc softmx jitaot linux the test runs the vm with and expects the aot data space to be full but the file stderr combined txt says the jit data store is full instead with as shown below created shared classes persistent cache scc systest workload cache attached shared classes persistent cache scc systest workload cache memory page protection on runtime data string read write data and partially filled pages is successfully enabled total shared class bytes read total bytes stored total unstored bytes due to the setting of shared cache soft max is unstored aot bytes due to the setting of xscmaxaot is unstored jit bytes due to the setting of xscmaxjitdata is opened shared classes persistent cache scc systest workload cache attached shared classes persistent cache scc systest workload cache memory page protection on runtime data string read write data and partially filled pages is successfully enabled the space for jit data in shared cache scc systest workload cache is full total shared class bytes read total bytes stored total unstored bytes due to the setting of shared cache soft max is unstored aot bytes due to the setting of xscmaxaot is unstored jit bytes due to the setting of xscmaxjitdata is aot is enabled in the runtime | 0 |
74,241 | 15,325,439,518 | IssuesEvent | 2021-02-26 01:19:01 | idonthaveafifaaddiction/MapLoom | https://api.github.com/repos/idonthaveafifaaddiction/MapLoom | opened | WS-2017-0116 (Medium) detected in angular-v1.2.21 | security vulnerability | ## WS-2017-0116 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>angular-v1.2.21</b></p></summary>
<p>null</p>
<p>Path to dependency file: MapLoom/bower.json</p>
<p>Path to vulnerable library: MapLoom/vendor/angular/.bower.json,MapLoom/vendor/angular/.bower.json</p>
<p>
Dependency Hierarchy:
- :x: **angular-v1.2.21** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The use element can reference external svg's (same origin) and can include xlink javascript urls or foreign object that can execute xss.
<p>Publish Date: 2015-12-05
<p>URL: <a href=https://github.com/angular/angular.js/commit/7a668cdd7d08a7016883eb3c671cbcd586223ae8>WS-2017-0116</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.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- 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/angular/angular.js/pull/13453">https://github.com/angular/angular.js/pull/13453</a></p>
<p>Release Date: 2015-12-05</p>
<p>Fix Resolution: angular - 1.5.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Bower","packageName":"angular","packageVersion":"v1.2.21","packageFilePaths":["/bower.json"],"isTransitiveDependency":false,"dependencyTree":"angular:v1.2.21","isMinimumFixVersionAvailable":true,"minimumFixVersion":"angular - 1.5.0"}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2017-0116","vulnerabilityDetails":"The use element can reference external svg\u0027s (same origin) and can include xlink javascript urls or foreign object that can execute xss.","vulnerabilityUrl":"https://github.com/angular/angular.js/commit/7a668cdd7d08a7016883eb3c671cbcd586223ae8","cvss3Severity":"medium","cvss3Score":"5.8","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | WS-2017-0116 (Medium) detected in angular-v1.2.21 - ## WS-2017-0116 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>angular-v1.2.21</b></p></summary>
<p>null</p>
<p>Path to dependency file: MapLoom/bower.json</p>
<p>Path to vulnerable library: MapLoom/vendor/angular/.bower.json,MapLoom/vendor/angular/.bower.json</p>
<p>
Dependency Hierarchy:
- :x: **angular-v1.2.21** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The use element can reference external svg's (same origin) and can include xlink javascript urls or foreign object that can execute xss.
<p>Publish Date: 2015-12-05
<p>URL: <a href=https://github.com/angular/angular.js/commit/7a668cdd7d08a7016883eb3c671cbcd586223ae8>WS-2017-0116</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.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- 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/angular/angular.js/pull/13453">https://github.com/angular/angular.js/pull/13453</a></p>
<p>Release Date: 2015-12-05</p>
<p>Fix Resolution: angular - 1.5.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Bower","packageName":"angular","packageVersion":"v1.2.21","packageFilePaths":["/bower.json"],"isTransitiveDependency":false,"dependencyTree":"angular:v1.2.21","isMinimumFixVersionAvailable":true,"minimumFixVersion":"angular - 1.5.0"}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2017-0116","vulnerabilityDetails":"The use element can reference external svg\u0027s (same origin) and can include xlink javascript urls or foreign object that can execute xss.","vulnerabilityUrl":"https://github.com/angular/angular.js/commit/7a668cdd7d08a7016883eb3c671cbcd586223ae8","cvss3Severity":"medium","cvss3Score":"5.8","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | ws medium detected in angular ws medium severity vulnerability vulnerable library angular null path to dependency file maploom bower json path to vulnerable library maploom vendor angular bower json maploom vendor angular bower json dependency hierarchy x angular vulnerable library found in base branch master vulnerability details the use element can reference external svg s same origin and can include xlink javascript urls or foreign object that can execute xss publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope changed impact metrics confidentiality impact low 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 angular isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree angular isminimumfixversionavailable true minimumfixversion angular basebranches vulnerabilityidentifier ws vulnerabilitydetails the use element can reference external svg same origin and can include xlink javascript urls or foreign object that can execute xss vulnerabilityurl | 0 |
3,321 | 6,288,564,299 | IssuesEvent | 2017-07-19 17:15:39 | STEllAR-GROUP/hpx | https://api.github.com/repos/STEllAR-GROUP/hpx | closed | Why Projection is needed in parallel algorithms? | category: algorithms type: compatibility issue type: feature request | Why projection is needed in interface of parallel algorithms?
https://github.com/STEllAR-GROUP/hpx/blob/383eab90cad8a29dfd66f930d97bd50c77569689/hpx/parallel/algorithms/partition.hpp#L271
I know that it is for invoking some procedure before invoking predicate.
But, I can't understand if we really need it.
Is there anyone to demonstrate the reason for me?
I didn't use ```Proj``` when I implemented ```is_heap``` and ```is_heap_until```.
Should I use ```Proj```?
https://github.com/STEllAR-GROUP/hpx/blob/383eab90cad8a29dfd66f930d97bd50c77569689/hpx/parallel/algorithms/is_heap.hpp#L176
I'm confused because some algorithms use ```Proj```` and others don't.
https://github.com/STEllAR-GROUP/hpx/blob/383eab90cad8a29dfd66f930d97bd50c77569689/hpx/parallel/algorithms/equal.hpp#L403 | True | Why Projection is needed in parallel algorithms? - Why projection is needed in interface of parallel algorithms?
https://github.com/STEllAR-GROUP/hpx/blob/383eab90cad8a29dfd66f930d97bd50c77569689/hpx/parallel/algorithms/partition.hpp#L271
I know that it is for invoking some procedure before invoking predicate.
But, I can't understand if we really need it.
Is there anyone to demonstrate the reason for me?
I didn't use ```Proj``` when I implemented ```is_heap``` and ```is_heap_until```.
Should I use ```Proj```?
https://github.com/STEllAR-GROUP/hpx/blob/383eab90cad8a29dfd66f930d97bd50c77569689/hpx/parallel/algorithms/is_heap.hpp#L176
I'm confused because some algorithms use ```Proj```` and others don't.
https://github.com/STEllAR-GROUP/hpx/blob/383eab90cad8a29dfd66f930d97bd50c77569689/hpx/parallel/algorithms/equal.hpp#L403 | non_priority | why projection is needed in parallel algorithms why projection is needed in interface of parallel algorithms i know that it is for invoking some procedure before invoking predicate but i can t understand if we really need it is there anyone to demonstrate the reason for me i didn t use proj when i implemented is heap and is heap until should i use proj i m confused because some algorithms use proj and others don t | 0 |
106,172 | 16,668,813,557 | IssuesEvent | 2021-06-07 08:22:17 | AOSC-Dev/aosc-os-abbs | https://api.github.com/repos/AOSC-Dev/aosc-os-abbs | closed | firefox: security update to 89.0 | 0day security upgrade | **CVE IDs:** CVE-2021-29959, CVE-2021-29960, CVE-2021-29961, CVE-2021-29962, CVE-2021-29963, CVE-2021-29964, CVE-2021-29965, CVE-2021-29966, CVE-2021-29967
**Other security advisory IDs:** [MFSA2021-23](https://www.mozilla.org/en-US/security/advisories/mfsa2021-23)
**Description:**
See [MFSA2021-23](https://www.mozilla.org/en-US/security/advisories/mfsa2021-23).
**Patches:** N/A
**PoC(s):** N/A | True | firefox: security update to 89.0 - **CVE IDs:** CVE-2021-29959, CVE-2021-29960, CVE-2021-29961, CVE-2021-29962, CVE-2021-29963, CVE-2021-29964, CVE-2021-29965, CVE-2021-29966, CVE-2021-29967
**Other security advisory IDs:** [MFSA2021-23](https://www.mozilla.org/en-US/security/advisories/mfsa2021-23)
**Description:**
See [MFSA2021-23](https://www.mozilla.org/en-US/security/advisories/mfsa2021-23).
**Patches:** N/A
**PoC(s):** N/A | non_priority | firefox security update to cve ids cve cve cve cve cve cve cve cve cve other security advisory ids description see patches n a poc s n a | 0 |
315,800 | 27,107,719,557 | IssuesEvent | 2023-02-15 13:19:35 | ventoy/Ventoy | https://api.github.com/repos/ventoy/Ventoy | closed | [Success Image Report]: Ubuntu Kylin 22.04 Enhanced / Pro Version x64 Bit | 【Tested Image Report】 | ### Official Website List
- [X] I have checked the list in official website and the image file is not listed there.
### Ventoy Version
1.0.88
### BIOS Mode
Both
### Partition Style
MBR
### Image file name
ubuntukylin-22.04-pro-amd64.iso
### Image file checksum type
MD5
### Image file checksum value
0145d61dcea77cd7e7ced4020e09c840
### Image file download link (if applicable)
https://mirrors.aliyun.com/ubuntukylin-cdimage/22.04/ubuntukylin-22.04-pro-amd64.iso/
### Test environment
Lenovo ThinkPad X230 Laptop
### More Details?
This image file booted successfully in Ventoy and no errors were seen.
Laptop Specs: - Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 2601 Mhz, 2 Core(s), 4 Logical Processor(s)
x64-based PC
8.00 GB RAM
500 GB SSD | 1.0 | [Success Image Report]: Ubuntu Kylin 22.04 Enhanced / Pro Version x64 Bit - ### Official Website List
- [X] I have checked the list in official website and the image file is not listed there.
### Ventoy Version
1.0.88
### BIOS Mode
Both
### Partition Style
MBR
### Image file name
ubuntukylin-22.04-pro-amd64.iso
### Image file checksum type
MD5
### Image file checksum value
0145d61dcea77cd7e7ced4020e09c840
### Image file download link (if applicable)
https://mirrors.aliyun.com/ubuntukylin-cdimage/22.04/ubuntukylin-22.04-pro-amd64.iso/
### Test environment
Lenovo ThinkPad X230 Laptop
### More Details?
This image file booted successfully in Ventoy and no errors were seen.
Laptop Specs: - Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 2601 Mhz, 2 Core(s), 4 Logical Processor(s)
x64-based PC
8.00 GB RAM
500 GB SSD | non_priority | ubuntu kylin enhanced pro version bit official website list i have checked the list in official website and the image file is not listed there ventoy version bios mode both partition style mbr image file name ubuntukylin pro iso image file checksum type image file checksum value image file download link if applicable test environment lenovo thinkpad laptop more details this image file booted successfully in ventoy and no errors were seen laptop specs intel r core tm cpu mhz core s logical processor s based pc gb ram gb ssd | 0 |
24,337 | 3,900,778,595 | IssuesEvent | 2016-04-18 08:04:05 | geetsisbac/WCVVENIXYFVIRBXH3BYTI6TE | https://api.github.com/repos/geetsisbac/WCVVENIXYFVIRBXH3BYTI6TE | closed | G+r36omqGgVrc/X5y5fJdTnXUmSIeGZe3b02fvTlAfPOt5YhvyMxbH/tnvENVEAF+AjOYxHn414qNi2ohu05AaLnyceCYQ1cTEdaXgZipiNxav4yoscVis7LFc3oxXZPZWeWgzYn36i5y7bs6+1cQ7RkGYD/MW2FkMXoG5IILUs= | design | VEFAi63WMg7q48WvQkRKMoq8yYiNqX1PLeogTSc2f9r8D4X+1XmMbqMaFD4sUTEYmGzyOJ40kUKBNOzNy1JUbYZBZJcEe0QAEWty4hMR4rLaF4J7d1hV3ApDoUbSZ7ltsAm6yVKxBfjwKhEQMCguVmmrnbd0LaJr1XiXCgGP6IAlj+KZA4bMLheMsp8oA0cANQu1WUQ7YNkn+jKZioSmkMlr2G2lP2W0zfHw2VIIel1CHMKLGBzK4f5V+9W17RaFUqADXdOLR5P5eIxRpdhAN6GQ7rWy/pxhwK3D5s6Mb0AU8G1a3OzypqVUkTJ/D6eX6CTDG/COF8DdpBWueJ4fIfBr7dbAcRv9TF0CFwWF9tPci/PnBxZO4VGyNF442DO0pnfbg1lrH6VVg2uUtbO9T8BXLBjNyIfs2/a5S1n+5cAU0Sn7ijoKvUo8bSpROgrQFMFu6uV3HHg5fOSKEzD2zv5YvR6R/AVB0AbgVkFh5k0np2AkHgAdbPiNpVjz9AfXL+fMg4nLYd1aA7jqoeJPl8OJjW3/rhff45ZS4H57SgEMLcuq6nJWdS3/qP3bF3jP4H2/EksHXDphWOUosZWDwi9CVw7Tn5/FHmI/o6n7YiQ0Q/gV7U1tIWGJJsxiHU/JcKDOYNGGLT0VShy/F6vAMUSPHqma5UAw1ix6r4h24VMwYkRFHohYqxJ1vcCOZajAk5ScdpJOpBY7Nm+BngFVmrrs4neBVv0MTGFKzgOC4AzuqZjT7W8UyoUrkeWR7/O7XfxJMYlLJPQYLfbyckKi8pOUnHaSTqQWOzZvgZ4BVZq67OJ3gVb9DExhSs4DguAM4OalJGM6ZXXDfkvaoILld88ZW/b6T2wd/VdEWXN63rVvl8b41IuY1E9qy5TY65MCKto3ndb4DHpS9HRUj3soMM+j0o2jT/73XnEnJNrt2duGZtS2rGCXhxscS0nN9ad2/4/FQGXs1y6TEJBUbVKZREPb+35tGCD4LJhk5t3rcFRYbuBphff/kJKhiUIVFuvx/jvQ3ip62D1nMIRy/obuvEUi/DS2we6kv0bP1qb4LvcmoA3Qc+1oMrF4IHZiAeRzgvvdmYFU0Kju39v9+NkwsmW9pyc54Qm3x1jt7ZvEvEBpPlkNwEiVV1EJz+KSelaa5c99K7x/lmx5AESy6yEyxw1BN4ogzTfRCBYtcPEqjXhpbLtl2bbbLSD7cDaPH4ycBF0fUO68f8hbRMWFQfPnu8dMCVSWoTe7hX6D5cXOlCGr5+7cIP1BErd1gYYITexhlnVznU2t2Bylj3ER9xYmTH2W21acC/d5eXwpsHWAgtFvefs/IttCYNM6bMtj+ocKHeFcNZyXjZ77A3Bh6Nvvdd/5vsA6N4TLfUGY8e586Pp4gIIe4NduD1vE/ED2BViqe3ErG5pgERi4Qx7iV2JC21gwoUW72TF18sqBXDvAZjGN8lv3iTSuK5McjEC1RN6X3QX1t5bN0dLtJa4/dTiMos348uWCObzK5lAYl4OCkrWHLkNV9Wv15O62cWkBsdz3yuNpyOpBPzNYJEG8V/43i6hvgLSGzDia7Ohtfq2Duakl9ONRCXHDwJWlv3p6Jo1t/mvuamKvS9YTVGcCtWdKs3y76shks935V/3/l+O2TDVZzFmcxPysmRA23K6hfm7xfojAQXwR4PAWSxiiZzo6iE0T0yIV8HlLTF5w2F56gYCZQk8YupcZvDunZwqeprO03/JEvR5gYChAh1jg8p86cqwZvLKjxU9m6JJdjhgDcWqYVk01s/l631bfXMUvNEAdPdnQH4els0lWov/RYvHGOkNSlsS7tTMCT6zASSCIgWk= | 1.0 | G+r36omqGgVrc/X5y5fJdTnXUmSIeGZe3b02fvTlAfPOt5YhvyMxbH/tnvENVEAF+AjOYxHn414qNi2ohu05AaLnyceCYQ1cTEdaXgZipiNxav4yoscVis7LFc3oxXZPZWeWgzYn36i5y7bs6+1cQ7RkGYD/MW2FkMXoG5IILUs= - VEFAi63WMg7q48WvQkRKMoq8yYiNqX1PLeogTSc2f9r8D4X+1XmMbqMaFD4sUTEYmGzyOJ40kUKBNOzNy1JUbYZBZJcEe0QAEWty4hMR4rLaF4J7d1hV3ApDoUbSZ7ltsAm6yVKxBfjwKhEQMCguVmmrnbd0LaJr1XiXCgGP6IAlj+KZA4bMLheMsp8oA0cANQu1WUQ7YNkn+jKZioSmkMlr2G2lP2W0zfHw2VIIel1CHMKLGBzK4f5V+9W17RaFUqADXdOLR5P5eIxRpdhAN6GQ7rWy/pxhwK3D5s6Mb0AU8G1a3OzypqVUkTJ/D6eX6CTDG/COF8DdpBWueJ4fIfBr7dbAcRv9TF0CFwWF9tPci/PnBxZO4VGyNF442DO0pnfbg1lrH6VVg2uUtbO9T8BXLBjNyIfs2/a5S1n+5cAU0Sn7ijoKvUo8bSpROgrQFMFu6uV3HHg5fOSKEzD2zv5YvR6R/AVB0AbgVkFh5k0np2AkHgAdbPiNpVjz9AfXL+fMg4nLYd1aA7jqoeJPl8OJjW3/rhff45ZS4H57SgEMLcuq6nJWdS3/qP3bF3jP4H2/EksHXDphWOUosZWDwi9CVw7Tn5/FHmI/o6n7YiQ0Q/gV7U1tIWGJJsxiHU/JcKDOYNGGLT0VShy/F6vAMUSPHqma5UAw1ix6r4h24VMwYkRFHohYqxJ1vcCOZajAk5ScdpJOpBY7Nm+BngFVmrrs4neBVv0MTGFKzgOC4AzuqZjT7W8UyoUrkeWR7/O7XfxJMYlLJPQYLfbyckKi8pOUnHaSTqQWOzZvgZ4BVZq67OJ3gVb9DExhSs4DguAM4OalJGM6ZXXDfkvaoILld88ZW/b6T2wd/VdEWXN63rVvl8b41IuY1E9qy5TY65MCKto3ndb4DHpS9HRUj3soMM+j0o2jT/73XnEnJNrt2duGZtS2rGCXhxscS0nN9ad2/4/FQGXs1y6TEJBUbVKZREPb+35tGCD4LJhk5t3rcFRYbuBphff/kJKhiUIVFuvx/jvQ3ip62D1nMIRy/obuvEUi/DS2we6kv0bP1qb4LvcmoA3Qc+1oMrF4IHZiAeRzgvvdmYFU0Kju39v9+NkwsmW9pyc54Qm3x1jt7ZvEvEBpPlkNwEiVV1EJz+KSelaa5c99K7x/lmx5AESy6yEyxw1BN4ogzTfRCBYtcPEqjXhpbLtl2bbbLSD7cDaPH4ycBF0fUO68f8hbRMWFQfPnu8dMCVSWoTe7hX6D5cXOlCGr5+7cIP1BErd1gYYITexhlnVznU2t2Bylj3ER9xYmTH2W21acC/d5eXwpsHWAgtFvefs/IttCYNM6bMtj+ocKHeFcNZyXjZ77A3Bh6Nvvdd/5vsA6N4TLfUGY8e586Pp4gIIe4NduD1vE/ED2BViqe3ErG5pgERi4Qx7iV2JC21gwoUW72TF18sqBXDvAZjGN8lv3iTSuK5McjEC1RN6X3QX1t5bN0dLtJa4/dTiMos348uWCObzK5lAYl4OCkrWHLkNV9Wv15O62cWkBsdz3yuNpyOpBPzNYJEG8V/43i6hvgLSGzDia7Ohtfq2Duakl9ONRCXHDwJWlv3p6Jo1t/mvuamKvS9YTVGcCtWdKs3y76shks935V/3/l+O2TDVZzFmcxPysmRA23K6hfm7xfojAQXwR4PAWSxiiZzo6iE0T0yIV8HlLTF5w2F56gYCZQk8YupcZvDunZwqeprO03/JEvR5gYChAh1jg8p86cqwZvLKjxU9m6JJdjhgDcWqYVk01s/l631bfXMUvNEAdPdnQH4els0lWov/RYvHGOkNSlsS7tTMCT6zASSCIgWk= | non_priority | g tnvenveaf fhmi kjkhiuivfuvx obuveui l | 0 |
168,886 | 14,175,080,283 | IssuesEvent | 2020-11-12 20:58:33 | hashicorp/terraform-provider-kubernetes | https://api.github.com/repos/hashicorp/terraform-provider-kubernetes | closed | FR: Support HostAlias in PodSpec | bug documentation help wanted | Currently, the [HostAlias](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.11/#hostalias-v1-core) object isn't supported for all resources, that include the PodSpec.
This is available since v1.7 according to the [official documentation](https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/).
### Terraform Version
Terraform v0.11.11
### Affected Resource(s)
Basically every resource supporting the podspec:
- kubernetes_pod
- kubernetes_deployment
- kubernetes_stateful_set
- kubernetes_replication_controller
| 1.0 | FR: Support HostAlias in PodSpec - Currently, the [HostAlias](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.11/#hostalias-v1-core) object isn't supported for all resources, that include the PodSpec.
This is available since v1.7 according to the [official documentation](https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/).
### Terraform Version
Terraform v0.11.11
### Affected Resource(s)
Basically every resource supporting the podspec:
- kubernetes_pod
- kubernetes_deployment
- kubernetes_stateful_set
- kubernetes_replication_controller
| non_priority | fr support hostalias in podspec currently the object isn t supported for all resources that include the podspec this is available since according to the terraform version terraform affected resource s basically every resource supporting the podspec kubernetes pod kubernetes deployment kubernetes stateful set kubernetes replication controller | 0 |
226,168 | 17,955,309,803 | IssuesEvent | 2021-09-13 06:40:36 | vaadin/flow-components | https://api.github.com/repos/vaadin/flow-components | closed | SelectElement sometimes refer to the wrong popup | vaadin-select Severity: Minor Impact: Low testing | ### Description
If you first use `SelectElement.selectByText()` on one select and then open another popup and try to use `selectByText`, it will search for the text string in the popup of the first select. The reason is this implementation
```
public Stream<ItemElement> getItemsStream() {
openPopup();
List<WebElement> elements = getDriver().findElement(By.tagName("vaadin-select-overlay"))
.findElement(By.tagName("vaadin-list-box"))
.findElements(By.tagName("vaadin-item"));
```
and the fact that the overlay of the first select is moved to a child of the select after being closed so it is still in the DOM and will be matched when looking for `vaadin-select-overlay` on the whole page.
Potential fix would be something like
```
List<WebElement> elements = getPropertyElement("_overlayElement").findElement(By.tagName("vaadin-list-box"))
.findElements(By.tagName("vaadin-item"));
```
| 1.0 | SelectElement sometimes refer to the wrong popup - ### Description
If you first use `SelectElement.selectByText()` on one select and then open another popup and try to use `selectByText`, it will search for the text string in the popup of the first select. The reason is this implementation
```
public Stream<ItemElement> getItemsStream() {
openPopup();
List<WebElement> elements = getDriver().findElement(By.tagName("vaadin-select-overlay"))
.findElement(By.tagName("vaadin-list-box"))
.findElements(By.tagName("vaadin-item"));
```
and the fact that the overlay of the first select is moved to a child of the select after being closed so it is still in the DOM and will be matched when looking for `vaadin-select-overlay` on the whole page.
Potential fix would be something like
```
List<WebElement> elements = getPropertyElement("_overlayElement").findElement(By.tagName("vaadin-list-box"))
.findElements(By.tagName("vaadin-item"));
```
| non_priority | selectelement sometimes refer to the wrong popup description if you first use selectelement selectbytext on one select and then open another popup and try to use selectbytext it will search for the text string in the popup of the first select the reason is this implementation public stream getitemsstream openpopup list elements getdriver findelement by tagname vaadin select overlay findelement by tagname vaadin list box findelements by tagname vaadin item and the fact that the overlay of the first select is moved to a child of the select after being closed so it is still in the dom and will be matched when looking for vaadin select overlay on the whole page potential fix would be something like list elements getpropertyelement overlayelement findelement by tagname vaadin list box findelements by tagname vaadin item | 0 |
12,637 | 14,929,701,422 | IssuesEvent | 2021-01-25 00:30:12 | PMEAL/porespy | https://api.github.com/repos/PMEAL/porespy | closed | Using openpnm conduit length and shape factors in get_net is a problem | backwards incompatible | We did this to make the extraction easier to import into openpnm, but having these values hard coded in the network is a problem. It would be better to leave these out then add the models in openpnm, even though this is a pain. We should insist that people the proper import/export functions to get these models added. | True | Using openpnm conduit length and shape factors in get_net is a problem - We did this to make the extraction easier to import into openpnm, but having these values hard coded in the network is a problem. It would be better to leave these out then add the models in openpnm, even though this is a pain. We should insist that people the proper import/export functions to get these models added. | non_priority | using openpnm conduit length and shape factors in get net is a problem we did this to make the extraction easier to import into openpnm but having these values hard coded in the network is a problem it would be better to leave these out then add the models in openpnm even though this is a pain we should insist that people the proper import export functions to get these models added | 0 |
25,860 | 4,478,492,505 | IssuesEvent | 2016-08-27 02:22:35 | eczarny/spectacle | https://api.github.com/repos/eczarny/spectacle | closed | Shortcut for Next Display doesn't appear in menu | defect ★ | When using "space" as a key. Probably an OS X issue with long shortcut sequences, feel free to 'wontfix`.
| 1.0 | Shortcut for Next Display doesn't appear in menu - When using "space" as a key. Probably an OS X issue with long shortcut sequences, feel free to 'wontfix`.
| non_priority | shortcut for next display doesn t appear in menu when using space as a key probably an os x issue with long shortcut sequences feel free to wontfix | 0 |
76,551 | 9,461,940,187 | IssuesEvent | 2019-04-17 14:28:33 | BirdBrainTechnologies/flutter-kindle-sttr2 | https://api.github.com/repos/BirdBrainTechnologies/flutter-kindle-sttr2 | opened | Larger text for compare drop down menu. | CubeTower design - fix/clarification | Can the text in the drop down menu be bigger? (Observed 4/16/19, 2nd grade pilot) | 1.0 | Larger text for compare drop down menu. - Can the text in the drop down menu be bigger? (Observed 4/16/19, 2nd grade pilot) | non_priority | larger text for compare drop down menu can the text in the drop down menu be bigger observed grade pilot | 0 |
300,323 | 22,668,082,376 | IssuesEvent | 2022-07-03 07:28:21 | pdpipe/pdpipe | https://api.github.com/repos/pdpipe/pdpipe | opened | Doc Site: Class docstring examples are not presented correctly | bug documentation | On [the project's docsite](https://pdpipe.readthedocs.io/en/latest/), class docstring examples are not presented correctly.
I'm pretty sure this is the last inheritance from `pydoc3`, the way the doc site was compiled before, which required extra indentation of the `Example` portion of docstring to compile. Removing the indent should solve this.
## Expected Result
Nice, syntax-highlighted, code example.
## Actual Result
See for example:
https://pdpipe.readthedocs.io/en/latest/reference/sklearn/#pdpipe.sklearn_stages.Scale
<img width="674" alt="image" src="https://user-images.githubusercontent.com/917954/177029723-41147e5a-e140-4ab0-a51c-734666ff438a.png">
| 1.0 | Doc Site: Class docstring examples are not presented correctly - On [the project's docsite](https://pdpipe.readthedocs.io/en/latest/), class docstring examples are not presented correctly.
I'm pretty sure this is the last inheritance from `pydoc3`, the way the doc site was compiled before, which required extra indentation of the `Example` portion of docstring to compile. Removing the indent should solve this.
## Expected Result
Nice, syntax-highlighted, code example.
## Actual Result
See for example:
https://pdpipe.readthedocs.io/en/latest/reference/sklearn/#pdpipe.sklearn_stages.Scale
<img width="674" alt="image" src="https://user-images.githubusercontent.com/917954/177029723-41147e5a-e140-4ab0-a51c-734666ff438a.png">
| non_priority | doc site class docstring examples are not presented correctly on class docstring examples are not presented correctly i m pretty sure this is the last inheritance from the way the doc site was compiled before which required extra indentation of the example portion of docstring to compile removing the indent should solve this expected result nice syntax highlighted code example actual result see for example img width alt image src | 0 |
300,870 | 22,701,622,538 | IssuesEvent | 2022-07-05 11:12:41 | withastro/docs | https://api.github.com/repos/withastro/docs | closed | Basics>Markdown: Markdown Drafts | improve documentation PR'd | # Problem
[Relative Path](https://github.com/withastro/docs/blob/main/src/pages/en/guides/markdown-content.md)
## Issue 1:
These section is a bit confusing to [read](https://docs.astro.build/en/guides/markdown-content/#markdown-drafts).
### Suggestion
>To exclude a `.md` page or post from site build you can assign `draft: true` in the frontmatter properties. By default, site build will ignore this page.
>
>Pages not assigned a `draft:` property or if the value is set to `draft: false` will be included.
>
## Issue 2:
I have read over this several times and absolutely can't grasp what this is trying to get across.
As a new user of the framework I keep seeing Astro.glob(), but no references to it. Which could be linked to [this](https://docs.astro.build/en/reference/api-reference/) page. The other reference I found was in the [troubleshoot](https://docs.astro.build/en/guides/troubleshooting/#astroglob---no-matches-found).
However, both of these do not provided any clarity on how to filter `data` via the `Astro.glob()` as this sentence suggests.
>Aside: I just realized that the "filters to exclude any draft posts" is bold. It's not easily seen. Possible to set a CSS styling to these?
| 1.0 | Basics>Markdown: Markdown Drafts - # Problem
[Relative Path](https://github.com/withastro/docs/blob/main/src/pages/en/guides/markdown-content.md)
## Issue 1:
These section is a bit confusing to [read](https://docs.astro.build/en/guides/markdown-content/#markdown-drafts).
### Suggestion
>To exclude a `.md` page or post from site build you can assign `draft: true` in the frontmatter properties. By default, site build will ignore this page.
>
>Pages not assigned a `draft:` property or if the value is set to `draft: false` will be included.
>
## Issue 2:
I have read over this several times and absolutely can't grasp what this is trying to get across.
As a new user of the framework I keep seeing Astro.glob(), but no references to it. Which could be linked to [this](https://docs.astro.build/en/reference/api-reference/) page. The other reference I found was in the [troubleshoot](https://docs.astro.build/en/guides/troubleshooting/#astroglob---no-matches-found).
However, both of these do not provided any clarity on how to filter `data` via the `Astro.glob()` as this sentence suggests.
>Aside: I just realized that the "filters to exclude any draft posts" is bold. It's not easily seen. Possible to set a CSS styling to these?
| non_priority | basics markdown markdown drafts problem issue these section is a bit confusing to suggestion to exclude a md page or post from site build you can assign draft true in the frontmatter properties by default site build will ignore this page pages not assigned a draft property or if the value is set to draft false will be included issue i have read over this several times and absolutely can t grasp what this is trying to get across as a new user of the framework i keep seeing astro glob but no references to it which could be linked to page the other reference i found was in the however both of these do not provided any clarity on how to filter data via the astro glob as this sentence suggests aside i just realized that the filters to exclude any draft posts is bold it s not easily seen possible to set a css styling to these | 0 |
190,641 | 14,566,273,604 | IssuesEvent | 2020-12-17 08:39:56 | kalexmills/github-vet-tests-dec2020 | https://api.github.com/repos/kalexmills/github-vet-tests-dec2020 | closed | golang/gofrontend: libgo/go/strings/builder_test.go; 10 LoC | fresh test tiny |
Found a possible issue in [golang/gofrontend](https://www.github.com/golang/gofrontend) at [libgo/go/strings/builder_test.go](https://github.com/golang/gofrontend/blob/526037336231593939a517b7c0b2892d413adb40/libgo/go/strings/builder_test.go#L299-L308)
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.
> range-loop variable tt used in defer or goroutine at line 303
[Click here to see the code in its original context.](https://github.com/golang/gofrontend/blob/526037336231593939a517b7c0b2892d413adb40/libgo/go/strings/builder_test.go#L299-L308)
<details>
<summary>Click here to show the 10 line(s) of Go which triggered the analyzer.</summary>
```go
for _, tt := range tests {
didPanic := make(chan bool)
go func() {
defer func() { didPanic <- recover() != nil }()
tt.fn()
}()
if got := <-didPanic; got != tt.wantPanic {
t.Errorf("%s: panicked = %v; want %v", tt.name, got, tt.wantPanic)
}
}
```
</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: 526037336231593939a517b7c0b2892d413adb40
| 1.0 | golang/gofrontend: libgo/go/strings/builder_test.go; 10 LoC -
Found a possible issue in [golang/gofrontend](https://www.github.com/golang/gofrontend) at [libgo/go/strings/builder_test.go](https://github.com/golang/gofrontend/blob/526037336231593939a517b7c0b2892d413adb40/libgo/go/strings/builder_test.go#L299-L308)
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.
> range-loop variable tt used in defer or goroutine at line 303
[Click here to see the code in its original context.](https://github.com/golang/gofrontend/blob/526037336231593939a517b7c0b2892d413adb40/libgo/go/strings/builder_test.go#L299-L308)
<details>
<summary>Click here to show the 10 line(s) of Go which triggered the analyzer.</summary>
```go
for _, tt := range tests {
didPanic := make(chan bool)
go func() {
defer func() { didPanic <- recover() != nil }()
tt.fn()
}()
if got := <-didPanic; got != tt.wantPanic {
t.Errorf("%s: panicked = %v; want %v", tt.name, got, tt.wantPanic)
}
}
```
</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: 526037336231593939a517b7c0b2892d413adb40
| non_priority | golang gofrontend libgo go strings builder 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 range loop variable tt used in defer or goroutine at line click here to show the line s of go which triggered the analyzer go for tt range tests didpanic make chan bool go func defer func didpanic recover nil tt fn if got didpanic got tt wantpanic t errorf s panicked v want v tt name got tt wantpanic 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 |
260,834 | 19,686,909,077 | IssuesEvent | 2022-01-11 23:35:58 | alexmfritz/overlook-hotel | https://api.github.com/repos/alexmfritz/overlook-hotel | closed | #### DAY ONE DELIVERABLES | documentation | - [x] Create all files in the overlook-hotel directory
- [x] Create Project Board
- [x] Link all necessary associates to repo
- [x] Create wireframe
- [x] https://miro.com/app/board/uXjVOWBzoNM=/?invite_link_id=196116816775 | 1.0 | #### DAY ONE DELIVERABLES - - [x] Create all files in the overlook-hotel directory
- [x] Create Project Board
- [x] Link all necessary associates to repo
- [x] Create wireframe
- [x] https://miro.com/app/board/uXjVOWBzoNM=/?invite_link_id=196116816775 | non_priority | day one deliverables create all files in the overlook hotel directory create project board link all necessary associates to repo create wireframe | 0 |
121,204 | 25,939,819,001 | IssuesEvent | 2022-12-16 17:14:41 | microsoft/vscode | https://api.github.com/repos/microsoft/vscode | closed | Download of the vscode cli via the terminal (wget) does not work - returns a 404 | feature-request vscode-website | <!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Dear vscode team,
I was eager to try the new(?) vscode cli today to set up a tunnel to my virtual machine.
Hoping that it fixes my download/update extensions issues with the currently used `code-server`.
However, it looks like the direct download link is not wget friendly?
See error report below.
Does this issue occur when all extensions are disabled?: not applicable
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: not applicable
- OS Version: CentOS Stream 8 x86_64
Steps to Reproduce:
1. Open in your browser: https://code.visualstudio.com/docs/?dv=linux64cli
2. Copy the link address of "Try this [direct download link.](https://code.visualstudio.com/sha/download?build=stable&os=cli-alpine-x64)"
3. Use wget in the virtual machine to download the cli:
`wget https://code.visualstudio.com/sha/download?build=stable&os=cli-alpine-x64`
wget-log output:
> https://code.visualstudio.com/sha/download?build=stable
> Resolving code.visualstudio.com (code.visualstudio.com)... 13.69.68.34
> Connecting to code.visualstudio.com (code.visualstudio.com)|13.69.68.34|:443... connected.
> HTTP request sent, awaiting response... 404 Not Found
| 1.0 | Download of the vscode cli via the terminal (wget) does not work - returns a 404 - <!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Dear vscode team,
I was eager to try the new(?) vscode cli today to set up a tunnel to my virtual machine.
Hoping that it fixes my download/update extensions issues with the currently used `code-server`.
However, it looks like the direct download link is not wget friendly?
See error report below.
Does this issue occur when all extensions are disabled?: not applicable
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: not applicable
- OS Version: CentOS Stream 8 x86_64
Steps to Reproduce:
1. Open in your browser: https://code.visualstudio.com/docs/?dv=linux64cli
2. Copy the link address of "Try this [direct download link.](https://code.visualstudio.com/sha/download?build=stable&os=cli-alpine-x64)"
3. Use wget in the virtual machine to download the cli:
`wget https://code.visualstudio.com/sha/download?build=stable&os=cli-alpine-x64`
wget-log output:
> https://code.visualstudio.com/sha/download?build=stable
> Resolving code.visualstudio.com (code.visualstudio.com)... 13.69.68.34
> Connecting to code.visualstudio.com (code.visualstudio.com)|13.69.68.34|:443... connected.
> HTTP request sent, awaiting response... 404 Not Found
| non_priority | download of the vscode cli via the terminal wget does not work returns a dear vscode team i was eager to try the new vscode cli today to set up a tunnel to my virtual machine hoping that it fixes my download update extensions issues with the currently used code server however it looks like the direct download link is not wget friendly see error report below does this issue occur when all extensions are disabled not applicable report issue dialog can assist with this vs code version not applicable os version centos stream steps to reproduce open in your browser copy the link address of try this use wget in the virtual machine to download the cli wget wget log output resolving code visualstudio com code visualstudio com connecting to code visualstudio com code visualstudio com connected http request sent awaiting response not found | 0 |
134,399 | 10,914,014,012 | IssuesEvent | 2019-11-21 08:12:17 | flutter/devtools | https://api.github.com/repos/flutter/devtools | opened | Remove "serverDevToolsLaunchViaStdin" flag after next publish | testing | The server tests that use `launch.DevTools` via the stdin API are only enabled for bots using the local dependencies because this feature has not been published to pub yet. After the next publish we can remove the `serverDevToolsLaunchViaStdin` flag from the source code (and consider it always true where it's being used). | 1.0 | Remove "serverDevToolsLaunchViaStdin" flag after next publish - The server tests that use `launch.DevTools` via the stdin API are only enabled for bots using the local dependencies because this feature has not been published to pub yet. After the next publish we can remove the `serverDevToolsLaunchViaStdin` flag from the source code (and consider it always true where it's being used). | non_priority | remove serverdevtoolslaunchviastdin flag after next publish the server tests that use launch devtools via the stdin api are only enabled for bots using the local dependencies because this feature has not been published to pub yet after the next publish we can remove the serverdevtoolslaunchviastdin flag from the source code and consider it always true where it s being used | 0 |
125,994 | 10,372,778,214 | IssuesEvent | 2019-09-09 04:46:16 | microsoft/azure-tools-for-java | https://api.github.com/repos/microsoft/azure-tools-for-java | opened | [intelliJ][Report to Microsoft][Spark on Arcadia]Get error when run interactive console with empty computes. | HDInsight IntelliJ Internal Test System Telemetry | Build:
azure-toolkit-for-intellij-2019.2.develop.1234.09-05-2019
Repro Steps:
1. Create an Arcadia configuration, do not choose value.
2. Run interactive console from Tools/Spark console
Result:
Get error.
Expectation:
java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.microsoft.azure.hdinsight.spark.console.RunSparkConsoleActionDelegate.actionPerformed(RunSparkConsoleActionDelegate.kt:59)
at com.intellij.openapi.actionSystem.ex.ActionUtil$1.run(ActionUtil.java:265)
at com.intellij.openapi.actionSystem.ex.ActionUtil.performActionDumbAware(ActionUtil.java:282)
at com.intellij.openapi.actionSystem.impl.ActionMenuItem$ActionTransmitter.lambda$actionPerformed$0(ActionMenuItem.java:292)
at com.intellij.openapi.wm.impl.FocusManagerImpl.runOnOwnContext(FocusManagerImpl.java:265)
at com.intellij.openapi.wm.impl.IdeFocusManagerImpl.runOnOwnContext(IdeFocusManagerImpl.java:107)
at com.intellij.openapi.actionSystem.impl.ActionMenuItem$ActionTransmitter.actionPerformed(ActionMenuItem.java:282)
at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967)
at com.intellij.openapi.actionSystem.impl.ActionMenuItem.lambda$fireActionPerformed$0(ActionMenuItem.java:111)
at com.intellij.openapi.application.TransactionGuardImpl.runSyncTransaction(TransactionGuardImpl.java:82)
at com.intellij.openapi.application.TransactionGuardImpl.lambda$submitTransaction$1(TransactionGuardImpl.java:106)
at com.intellij.openapi.application.TransactionGuardImpl.submitTransaction(TransactionGuardImpl.java:115)
at com.intellij.openapi.application.TransactionGuard.submitTransaction(TransactionGuard.java:121)
at com.intellij.openapi.actionSystem.impl.ActionMenuItem.fireActionPerformed(ActionMenuItem.java:111)
at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308)
at java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405)
at java.desktop/javax.swing.JToggleButton$ToggleButtonModel.setPressed(JToggleButton.java:401)
at java.desktop/javax.swing.AbstractButton.doClick(AbstractButton.java:369)
at java.desktop/javax.swing.AbstractButton.doClick(AbstractButton.java:349)
at com.intellij.openapi.wm.impl.GlobalMenuLinux.lambda$_handleEvent$13(GlobalMenuLinux.java:698)
at com.intellij.openapi.application.TransactionGuardImpl$2.run(TransactionGuardImpl.java:312)
at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.doRun(LaterInvocator.java:433)
at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.runNextEvent(LaterInvocator.java:416)
at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.run(LaterInvocator.java:399)
at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:776)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:727)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:746)
at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java:878)
at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:827)
at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$8(IdeEventQueue.java:466)
at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:704)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:465)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
Caused by: kotlin.UninitializedPropertyAccessException: lateinit property tenantId has not been initialized
at com.microsoft.azure.hdinsight.spark.run.configuration.ArcadiaSparkSubmitModel.getTenantId(ArcadiaSparkSubmitModel.kt:37)
at com.microsoft.azure.projectarcadia.spark.console.ArcadiaSparkScalaLivyConsoleRunConfiguration.checkRunnerSettings(ArcadiaSparkScalaLivyConsoleRunConfiguration.kt:71)
at com.microsoft.azure.hdinsight.spark.run.action.RunConfigurationActionUtils.checkRunnerSettings(RunConfigurationActionUtils.kt:87)
at com.microsoft.azure.hdinsight.spark.run.action.RunConfigurationActionUtils.getRunConfigurationError(RunConfigurationActionUtils.kt:92)
at com.microsoft.azure.hdinsight.spark.run.action.RunConfigurationActionUtils.runEnvironmentProfileWithCheckSettings(RunConfigurationActionUtils.kt:53)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction.runFromSetting(RunSparkScalaConsoleAction.kt:144)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction.access$runFromSetting(RunSparkScalaConsoleAction.kt:52)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction$runExisting$1.invoke(RunSparkScalaConsoleAction.kt:119)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction$runExisting$1.invoke(RunSparkScalaConsoleAction.kt:52)
at com.microsoft.intellij.util.ApplicationHelpersKt.runInReadAction(ApplicationHelpers.kt:42)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction.runExisting(RunSparkScalaConsoleAction.kt:118)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction.onActionPerformed(RunSparkScalaConsoleAction.kt:71)
at com.microsoft.azuretools.ijidea.utility.AzureAnAction.actionPerformed(AzureAnAction.java:75)
... 46 more
| 1.0 | [intelliJ][Report to Microsoft][Spark on Arcadia]Get error when run interactive console with empty computes. - Build:
azure-toolkit-for-intellij-2019.2.develop.1234.09-05-2019
Repro Steps:
1. Create an Arcadia configuration, do not choose value.
2. Run interactive console from Tools/Spark console
Result:
Get error.
Expectation:
java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.microsoft.azure.hdinsight.spark.console.RunSparkConsoleActionDelegate.actionPerformed(RunSparkConsoleActionDelegate.kt:59)
at com.intellij.openapi.actionSystem.ex.ActionUtil$1.run(ActionUtil.java:265)
at com.intellij.openapi.actionSystem.ex.ActionUtil.performActionDumbAware(ActionUtil.java:282)
at com.intellij.openapi.actionSystem.impl.ActionMenuItem$ActionTransmitter.lambda$actionPerformed$0(ActionMenuItem.java:292)
at com.intellij.openapi.wm.impl.FocusManagerImpl.runOnOwnContext(FocusManagerImpl.java:265)
at com.intellij.openapi.wm.impl.IdeFocusManagerImpl.runOnOwnContext(IdeFocusManagerImpl.java:107)
at com.intellij.openapi.actionSystem.impl.ActionMenuItem$ActionTransmitter.actionPerformed(ActionMenuItem.java:282)
at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967)
at com.intellij.openapi.actionSystem.impl.ActionMenuItem.lambda$fireActionPerformed$0(ActionMenuItem.java:111)
at com.intellij.openapi.application.TransactionGuardImpl.runSyncTransaction(TransactionGuardImpl.java:82)
at com.intellij.openapi.application.TransactionGuardImpl.lambda$submitTransaction$1(TransactionGuardImpl.java:106)
at com.intellij.openapi.application.TransactionGuardImpl.submitTransaction(TransactionGuardImpl.java:115)
at com.intellij.openapi.application.TransactionGuard.submitTransaction(TransactionGuard.java:121)
at com.intellij.openapi.actionSystem.impl.ActionMenuItem.fireActionPerformed(ActionMenuItem.java:111)
at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308)
at java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405)
at java.desktop/javax.swing.JToggleButton$ToggleButtonModel.setPressed(JToggleButton.java:401)
at java.desktop/javax.swing.AbstractButton.doClick(AbstractButton.java:369)
at java.desktop/javax.swing.AbstractButton.doClick(AbstractButton.java:349)
at com.intellij.openapi.wm.impl.GlobalMenuLinux.lambda$_handleEvent$13(GlobalMenuLinux.java:698)
at com.intellij.openapi.application.TransactionGuardImpl$2.run(TransactionGuardImpl.java:312)
at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.doRun(LaterInvocator.java:433)
at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.runNextEvent(LaterInvocator.java:416)
at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.run(LaterInvocator.java:399)
at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:776)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:727)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:746)
at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java:878)
at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:827)
at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$8(IdeEventQueue.java:466)
at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:704)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:465)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
Caused by: kotlin.UninitializedPropertyAccessException: lateinit property tenantId has not been initialized
at com.microsoft.azure.hdinsight.spark.run.configuration.ArcadiaSparkSubmitModel.getTenantId(ArcadiaSparkSubmitModel.kt:37)
at com.microsoft.azure.projectarcadia.spark.console.ArcadiaSparkScalaLivyConsoleRunConfiguration.checkRunnerSettings(ArcadiaSparkScalaLivyConsoleRunConfiguration.kt:71)
at com.microsoft.azure.hdinsight.spark.run.action.RunConfigurationActionUtils.checkRunnerSettings(RunConfigurationActionUtils.kt:87)
at com.microsoft.azure.hdinsight.spark.run.action.RunConfigurationActionUtils.getRunConfigurationError(RunConfigurationActionUtils.kt:92)
at com.microsoft.azure.hdinsight.spark.run.action.RunConfigurationActionUtils.runEnvironmentProfileWithCheckSettings(RunConfigurationActionUtils.kt:53)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction.runFromSetting(RunSparkScalaConsoleAction.kt:144)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction.access$runFromSetting(RunSparkScalaConsoleAction.kt:52)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction$runExisting$1.invoke(RunSparkScalaConsoleAction.kt:119)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction$runExisting$1.invoke(RunSparkScalaConsoleAction.kt:52)
at com.microsoft.intellij.util.ApplicationHelpersKt.runInReadAction(ApplicationHelpers.kt:42)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction.runExisting(RunSparkScalaConsoleAction.kt:118)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction.onActionPerformed(RunSparkScalaConsoleAction.kt:71)
at com.microsoft.azuretools.ijidea.utility.AzureAnAction.actionPerformed(AzureAnAction.java:75)
... 46 more
| non_priority | get error when run interactive console with empty computes build azure toolkit for intellij develop repro steps create an arcadia configuration do not choose value run interactive console from tools spark console result get error expectation java lang reflect invocationtargetexception at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at com microsoft azure hdinsight spark console runsparkconsoleactiondelegate actionperformed runsparkconsoleactiondelegate kt at com intellij openapi actionsystem ex actionutil run actionutil java at com intellij openapi actionsystem ex actionutil performactiondumbaware actionutil java at com intellij openapi actionsystem impl actionmenuitem actiontransmitter lambda actionperformed actionmenuitem java at com intellij openapi wm impl focusmanagerimpl runonowncontext focusmanagerimpl java at com intellij openapi wm impl idefocusmanagerimpl runonowncontext idefocusmanagerimpl java at com intellij openapi actionsystem impl actionmenuitem actiontransmitter actionperformed actionmenuitem java at java desktop javax swing abstractbutton fireactionperformed abstractbutton java at com intellij openapi actionsystem impl actionmenuitem lambda fireactionperformed actionmenuitem java at com intellij openapi application transactionguardimpl runsynctransaction transactionguardimpl java at com intellij openapi application transactionguardimpl lambda submittransaction transactionguardimpl java at com intellij openapi application transactionguardimpl submittransaction transactionguardimpl java at com intellij openapi application transactionguard submittransaction transactionguard java at com intellij openapi actionsystem impl actionmenuitem fireactionperformed actionmenuitem java at java desktop javax swing abstractbutton handler actionperformed abstractbutton java at java desktop javax swing defaultbuttonmodel fireactionperformed defaultbuttonmodel java at java desktop javax swing jtogglebutton togglebuttonmodel setpressed jtogglebutton java at java desktop javax swing abstractbutton doclick abstractbutton java at java desktop javax swing abstractbutton doclick abstractbutton java at com intellij openapi wm impl globalmenulinux lambda handleevent globalmenulinux java at com intellij openapi application transactionguardimpl run transactionguardimpl java at com intellij openapi application impl laterinvocator flushqueue dorun laterinvocator java at com intellij openapi application impl laterinvocator flushqueue runnextevent laterinvocator java at com intellij openapi application impl laterinvocator flushqueue run laterinvocator java at java desktop java awt event invocationevent dispatch invocationevent java at java desktop java awt eventqueue dispatcheventimpl eventqueue java at java desktop java awt eventqueue run eventqueue java at java desktop java awt eventqueue run eventqueue java at java base java security accesscontroller doprivileged native method at java base java security protectiondomain javasecurityaccessimpl dointersectionprivilege protectiondomain java at java desktop java awt eventqueue dispatchevent eventqueue java at com intellij ide ideeventqueue defaultdispatchevent ideeventqueue java at com intellij ide ideeventqueue dispatchevent ideeventqueue java at com intellij ide ideeventqueue lambda dispatchevent ideeventqueue java at com intellij openapi progress impl coreprogressmanager computeprioritized coreprogressmanager java at com intellij ide ideeventqueue dispatchevent ideeventqueue java at java desktop java awt eventdispatchthread pumponeeventforfilters eventdispatchthread java at java desktop java awt eventdispatchthread pumpeventsforfilter eventdispatchthread java at java desktop java awt eventdispatchthread pumpeventsforhierarchy eventdispatchthread java at java desktop java awt eventdispatchthread pumpevents eventdispatchthread java at java desktop java awt eventdispatchthread pumpevents eventdispatchthread java at java desktop java awt eventdispatchthread run eventdispatchthread java caused by kotlin uninitializedpropertyaccessexception lateinit property tenantid has not been initialized at com microsoft azure hdinsight spark run configuration arcadiasparksubmitmodel gettenantid arcadiasparksubmitmodel kt at com microsoft azure projectarcadia spark console arcadiasparkscalalivyconsolerunconfiguration checkrunnersettings arcadiasparkscalalivyconsolerunconfiguration kt at com microsoft azure hdinsight spark run action runconfigurationactionutils checkrunnersettings runconfigurationactionutils kt at com microsoft azure hdinsight spark run action runconfigurationactionutils getrunconfigurationerror runconfigurationactionutils kt at com microsoft azure hdinsight spark run action runconfigurationactionutils runenvironmentprofilewithchecksettings runconfigurationactionutils kt at com microsoft azure hdinsight spark console runsparkscalaconsoleaction runfromsetting runsparkscalaconsoleaction kt at com microsoft azure hdinsight spark console runsparkscalaconsoleaction access runfromsetting runsparkscalaconsoleaction kt at com microsoft azure hdinsight spark console runsparkscalaconsoleaction runexisting invoke runsparkscalaconsoleaction kt at com microsoft azure hdinsight spark console runsparkscalaconsoleaction runexisting invoke runsparkscalaconsoleaction kt at com microsoft intellij util applicationhelperskt runinreadaction applicationhelpers kt at com microsoft azure hdinsight spark console runsparkscalaconsoleaction runexisting runsparkscalaconsoleaction kt at com microsoft azure hdinsight spark console runsparkscalaconsoleaction onactionperformed runsparkscalaconsoleaction kt at com microsoft azuretools ijidea utility azureanaction actionperformed azureanaction java more | 0 |
263,489 | 19,912,869,693 | IssuesEvent | 2022-01-25 19:03:01 | WordPress/Documentation-Issue-Tracker | https://api.github.com/repos/WordPress/Documentation-Issue-Tracker | closed | User doc comparing Patterns vs Reusable Blocks vs Template Parts | user documentation 5.9 new document block editor | There seems to be widespread confusion around when to use each of these options. Writing a quick doc with an overall explanation comparing/contrasting each with links to respective docs would likely go a long way to help folks make good decisions :)
Adding the 5.9 label but it's not required for 5.9 IMO. | 1.0 | User doc comparing Patterns vs Reusable Blocks vs Template Parts - There seems to be widespread confusion around when to use each of these options. Writing a quick doc with an overall explanation comparing/contrasting each with links to respective docs would likely go a long way to help folks make good decisions :)
Adding the 5.9 label but it's not required for 5.9 IMO. | non_priority | user doc comparing patterns vs reusable blocks vs template parts there seems to be widespread confusion around when to use each of these options writing a quick doc with an overall explanation comparing contrasting each with links to respective docs would likely go a long way to help folks make good decisions adding the label but it s not required for imo | 0 |
357,417 | 25,176,382,458 | IssuesEvent | 2022-11-11 09:37:55 | PangKuangWei/pe | https://api.github.com/repos/PangKuangWei/pe | opened | UG Bug: Grammar Mistake (Comma Usage for 2 independent clauses) | severity.VeryLow type.DocumentationBug | There is a missing comma before the word `but` shown in the screenshot below. There should be a comma here because these 2 parts are independent clauses.
<!--session: 1668152656976-1bbc2a95-284a-4da4-b139-83a160afbe25-->
<!--Version: Web v3.4.4--> | 1.0 | UG Bug: Grammar Mistake (Comma Usage for 2 independent clauses) - There is a missing comma before the word `but` shown in the screenshot below. There should be a comma here because these 2 parts are independent clauses.
<!--session: 1668152656976-1bbc2a95-284a-4da4-b139-83a160afbe25-->
<!--Version: Web v3.4.4--> | non_priority | ug bug grammar mistake comma usage for independent clauses there is a missing comma before the word but shown in the screenshot below there should be a comma here because these parts are independent clauses | 0 |
274,518 | 23,845,192,017 | IssuesEvent | 2022-09-06 13:32:54 | sourcegraph/sourcegraph | https://api.github.com/repos/sourcegraph/sourcegraph | closed | RFC 697: Testing - Code intelligence user story | rfc-697 rfc-697-testing | See [RFC 697: Multiple version upgrades](https://docs.google.com/document/d/1eNiwzWZmfpvzFhs9IDcM7Sbchv_Hm8Uj-6bI-3TDlvg).
See the [testing strategy announcement in slack](https://sourcegraph.slack.com/archives/C02KZ941RNX/p1660748283465879).
This PR tracks general testing of multi-version upgrades as well as Code intelligence-specific test scenarios.
**Core story (altered for code intelligence specifics)**:
Prior to upgrading, run the upload portion of the codeintel-qa suite so that precise data exists.
_Note_: `oobmigrations.yaml` should be edited so that the introduced version of code intelligence-related oobmigrations start _after_ the original version, as all existing code intelligence oobmigrations start prior to 3.29. In order to ensure that the migrator has a chance to run the oobmigrations that the instance hasn't finished, this should be changed locally prior to the test.
1. Run a search for the `sourcegraph/sourcegraph` repository
2. Search for the term `GetUploads` on `HEAD`
3. Open a result and ensure the file renders
4. Check that file sidebar and symbols sidebars are populated
5. Ensure code navigation (go to definition and find references) work as expected
6. Repeat steps 2-5 on an old tag to ensure that unindexed paths are also functional
7. Visit each site-admin page to ensure there are no obvious error banners
8. **Code intelligence migration test**: Run the query portion of the codeintel-qa suite
9. **Code intelligence feature test**: Upload an index for another repository and ensure that precise intel is available
**Instructions**:
1. Start a local instance of Sourcegraph at version 3.35.0. The `docker-compose.yaml` artifact, below, provides an easy way to link a `sourcegraph/server` image with three container-based Postgres instances. The frontend, codeintel, and codeinsights databases are available on the host via ports 7777, 7778, and 7779, respectively.
2. Perform whatever steps listed above that need to be performed prior to upgrading (available on the host via port 7080).
3. Stop the `sourcegraph/server` container, but leave the three database containers running.
4. In a clone of the `sg/sg` repo, run the following commands to upgrade your local instance to version 4.0.
```bash
export PGDATASOURCE=postgres://sg:sg@127.0.0.1:7777/sg
export CODEINTEL_PGDATASOURCE=postgres://sg:sg@127.0.0.1:7778/sg
export CODEINSIGHTS_PGDATASOURCE=postgres://sg:sg@127.0.0.1:7779/sg
go run ./enterprise/cmd/migrator upgrade --from 3.35 --to 4.0
```
5. Update the tag on the `sourcegraph/server` image to point to the "pre-release" of version 4.0. The particular commit that we're treating as the 4.0 release prior to the creation of the tag in git can be found [here](https://sourcegraph.com/github.com/sourcegraph/sourcegraph/-/blob/internal/database/migration/stitch/git.go?L128=).
**Artifacts**:
`docker-compose.yaml`:
```yaml
version: '2.4'
services:
sourcegraph:
image: sourcegraph/server:{{TAG GOES HERE}}
environment:
- PGDATASOURCE=postgres://sg:sg@pgsql-frontend:5432/sg
- CODEINTEL_PGDATASOURCE=postgres://sg:sg@pgsql-codeintel:5432/sg
- CODEINSIGHTS_PGDATASOURCE=postgres://sg:sg@pgsql-codeinsights:5432/sg
ports:
- 7080:7080
networks:
- sourcegraph
depends_on:
- pgsql-frontend
- pgsql-codeintel
- pgsql-codeinsights
pgsql-frontend:
image: sourcegraph/postgres-12-alpine
volumes:
- 'pgsql-frontend:/data'
ports:
- 7777:5432
networks:
- sourcegraph
pgsql-codeintel:
image: sourcegraph/postgres-12-alpine
volumes:
- 'pgsql-codeintel:/data'
ports:
- 7778:5432
networks:
- sourcegraph
pgsql-codeinsights:
image: sourcegraph/postgres-12-alpine
volumes:
- 'pgsql-codeinsights:/data'
ports:
- 7779:5432
networks:
- sourcegraph
volumes:
sourcegraph:
pgsql-frontend:
pgsql-codeintel:
pgsql-codeinsights:
networks:
sourcegraph:
```
| 1.0 | RFC 697: Testing - Code intelligence user story - See [RFC 697: Multiple version upgrades](https://docs.google.com/document/d/1eNiwzWZmfpvzFhs9IDcM7Sbchv_Hm8Uj-6bI-3TDlvg).
See the [testing strategy announcement in slack](https://sourcegraph.slack.com/archives/C02KZ941RNX/p1660748283465879).
This PR tracks general testing of multi-version upgrades as well as Code intelligence-specific test scenarios.
**Core story (altered for code intelligence specifics)**:
Prior to upgrading, run the upload portion of the codeintel-qa suite so that precise data exists.
_Note_: `oobmigrations.yaml` should be edited so that the introduced version of code intelligence-related oobmigrations start _after_ the original version, as all existing code intelligence oobmigrations start prior to 3.29. In order to ensure that the migrator has a chance to run the oobmigrations that the instance hasn't finished, this should be changed locally prior to the test.
1. Run a search for the `sourcegraph/sourcegraph` repository
2. Search for the term `GetUploads` on `HEAD`
3. Open a result and ensure the file renders
4. Check that file sidebar and symbols sidebars are populated
5. Ensure code navigation (go to definition and find references) work as expected
6. Repeat steps 2-5 on an old tag to ensure that unindexed paths are also functional
7. Visit each site-admin page to ensure there are no obvious error banners
8. **Code intelligence migration test**: Run the query portion of the codeintel-qa suite
9. **Code intelligence feature test**: Upload an index for another repository and ensure that precise intel is available
**Instructions**:
1. Start a local instance of Sourcegraph at version 3.35.0. The `docker-compose.yaml` artifact, below, provides an easy way to link a `sourcegraph/server` image with three container-based Postgres instances. The frontend, codeintel, and codeinsights databases are available on the host via ports 7777, 7778, and 7779, respectively.
2. Perform whatever steps listed above that need to be performed prior to upgrading (available on the host via port 7080).
3. Stop the `sourcegraph/server` container, but leave the three database containers running.
4. In a clone of the `sg/sg` repo, run the following commands to upgrade your local instance to version 4.0.
```bash
export PGDATASOURCE=postgres://sg:sg@127.0.0.1:7777/sg
export CODEINTEL_PGDATASOURCE=postgres://sg:sg@127.0.0.1:7778/sg
export CODEINSIGHTS_PGDATASOURCE=postgres://sg:sg@127.0.0.1:7779/sg
go run ./enterprise/cmd/migrator upgrade --from 3.35 --to 4.0
```
5. Update the tag on the `sourcegraph/server` image to point to the "pre-release" of version 4.0. The particular commit that we're treating as the 4.0 release prior to the creation of the tag in git can be found [here](https://sourcegraph.com/github.com/sourcegraph/sourcegraph/-/blob/internal/database/migration/stitch/git.go?L128=).
**Artifacts**:
`docker-compose.yaml`:
```yaml
version: '2.4'
services:
sourcegraph:
image: sourcegraph/server:{{TAG GOES HERE}}
environment:
- PGDATASOURCE=postgres://sg:sg@pgsql-frontend:5432/sg
- CODEINTEL_PGDATASOURCE=postgres://sg:sg@pgsql-codeintel:5432/sg
- CODEINSIGHTS_PGDATASOURCE=postgres://sg:sg@pgsql-codeinsights:5432/sg
ports:
- 7080:7080
networks:
- sourcegraph
depends_on:
- pgsql-frontend
- pgsql-codeintel
- pgsql-codeinsights
pgsql-frontend:
image: sourcegraph/postgres-12-alpine
volumes:
- 'pgsql-frontend:/data'
ports:
- 7777:5432
networks:
- sourcegraph
pgsql-codeintel:
image: sourcegraph/postgres-12-alpine
volumes:
- 'pgsql-codeintel:/data'
ports:
- 7778:5432
networks:
- sourcegraph
pgsql-codeinsights:
image: sourcegraph/postgres-12-alpine
volumes:
- 'pgsql-codeinsights:/data'
ports:
- 7779:5432
networks:
- sourcegraph
volumes:
sourcegraph:
pgsql-frontend:
pgsql-codeintel:
pgsql-codeinsights:
networks:
sourcegraph:
```
| non_priority | rfc testing code intelligence user story see see the this pr tracks general testing of multi version upgrades as well as code intelligence specific test scenarios core story altered for code intelligence specifics prior to upgrading run the upload portion of the codeintel qa suite so that precise data exists note oobmigrations yaml should be edited so that the introduced version of code intelligence related oobmigrations start after the original version as all existing code intelligence oobmigrations start prior to in order to ensure that the migrator has a chance to run the oobmigrations that the instance hasn t finished this should be changed locally prior to the test run a search for the sourcegraph sourcegraph repository search for the term getuploads on head open a result and ensure the file renders check that file sidebar and symbols sidebars are populated ensure code navigation go to definition and find references work as expected repeat steps on an old tag to ensure that unindexed paths are also functional visit each site admin page to ensure there are no obvious error banners code intelligence migration test run the query portion of the codeintel qa suite code intelligence feature test upload an index for another repository and ensure that precise intel is available instructions start a local instance of sourcegraph at version the docker compose yaml artifact below provides an easy way to link a sourcegraph server image with three container based postgres instances the frontend codeintel and codeinsights databases are available on the host via ports and respectively perform whatever steps listed above that need to be performed prior to upgrading available on the host via port stop the sourcegraph server container but leave the three database containers running in a clone of the sg sg repo run the following commands to upgrade your local instance to version bash export pgdatasource postgres sg sg sg export codeintel pgdatasource postgres sg sg sg export codeinsights pgdatasource postgres sg sg sg go run enterprise cmd migrator upgrade from to update the tag on the sourcegraph server image to point to the pre release of version the particular commit that we re treating as the release prior to the creation of the tag in git can be found artifacts docker compose yaml yaml version services sourcegraph image sourcegraph server tag goes here environment pgdatasource postgres sg sg pgsql frontend sg codeintel pgdatasource postgres sg sg pgsql codeintel sg codeinsights pgdatasource postgres sg sg pgsql codeinsights sg ports networks sourcegraph depends on pgsql frontend pgsql codeintel pgsql codeinsights pgsql frontend image sourcegraph postgres alpine volumes pgsql frontend data ports networks sourcegraph pgsql codeintel image sourcegraph postgres alpine volumes pgsql codeintel data ports networks sourcegraph pgsql codeinsights image sourcegraph postgres alpine volumes pgsql codeinsights data ports networks sourcegraph volumes sourcegraph pgsql frontend pgsql codeintel pgsql codeinsights networks sourcegraph | 0 |
56,110 | 11,504,450,732 | IssuesEvent | 2020-02-12 23:20:50 | microsoft/vscode-python | https://api.github.com/repos/microsoft/vscode-python | closed | Recommend nvm for managing node in CONTRIBUTING.md. | feature-* needs PR type-code health | The extension requires node 8.9.1 (for now), but linux distros may install a newer version (e.g. 8.10 on Ubuntu). You can use `nvm` to manage the node version. The `.travis.yml` file shows what you'll need to do. This should be explained specifically in CONTRIBUTING.md.
Also see #1186. | 1.0 | Recommend nvm for managing node in CONTRIBUTING.md. - The extension requires node 8.9.1 (for now), but linux distros may install a newer version (e.g. 8.10 on Ubuntu). You can use `nvm` to manage the node version. The `.travis.yml` file shows what you'll need to do. This should be explained specifically in CONTRIBUTING.md.
Also see #1186. | non_priority | recommend nvm for managing node in contributing md the extension requires node for now but linux distros may install a newer version e g on ubuntu you can use nvm to manage the node version the travis yml file shows what you ll need to do this should be explained specifically in contributing md also see | 0 |
20,178 | 10,618,899,122 | IssuesEvent | 2019-10-13 08:59:31 | JuliaDynamics/RecurrenceAnalysis.jl | https://api.github.com/repos/JuliaDynamics/RecurrenceAnalysis.jl | closed | Specialized method for `_recurrence_matrix(::Vector, ::Vector)` | Hacktoberfest good first issue performance | Currently all recurrence_matrix calls transform data to Datasets in all cases. This is always faster for Matrices but I do not believe that this does not induce a performance regression for vectors.
A method should be added to the low level function `_recurrence_matrix` that does not do this transformation and also does not care about the metric and instead uses `abs(xi - yi)`
(notice: to get the gist of this issue is straightforward, but requires you to have a look at the source file: https://github.com/JuliaDynamics/RecurrenceAnalysis.jl/blob/master/src/matrices.jl
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/69047699-specialized-method-for-_recurrence_matrix-vector-vector?utm_campaign=plugin&utm_content=tracker%2F28405688&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F28405688&utm_medium=issues&utm_source=github).
</bountysource-plugin> | True | Specialized method for `_recurrence_matrix(::Vector, ::Vector)` - Currently all recurrence_matrix calls transform data to Datasets in all cases. This is always faster for Matrices but I do not believe that this does not induce a performance regression for vectors.
A method should be added to the low level function `_recurrence_matrix` that does not do this transformation and also does not care about the metric and instead uses `abs(xi - yi)`
(notice: to get the gist of this issue is straightforward, but requires you to have a look at the source file: https://github.com/JuliaDynamics/RecurrenceAnalysis.jl/blob/master/src/matrices.jl
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/69047699-specialized-method-for-_recurrence_matrix-vector-vector?utm_campaign=plugin&utm_content=tracker%2F28405688&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F28405688&utm_medium=issues&utm_source=github).
</bountysource-plugin> | non_priority | specialized method for recurrence matrix vector vector currently all recurrence matrix calls transform data to datasets in all cases this is always faster for matrices but i do not believe that this does not induce a performance regression for vectors a method should be added to the low level function recurrence matrix that does not do this transformation and also does not care about the metric and instead uses abs xi yi notice to get the gist of this issue is straightforward but requires you to have a look at the source file want to back this issue we accept bounties via | 0 |
1,341 | 2,731,406,585 | IssuesEvent | 2015-04-16 20:10:47 | ContinuumIO/blaze | https://api.github.com/repos/ContinuumIO/blaze | closed | cytoolz is required to import blaze, but it's not listed in requirements_strict.txt | bug build dev experience user experience | In a fresh virtualenv, `pip install blaze && python -c "import blaze"` fails with:
```
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/ssanderson/.virtualenvs/blaze/local/lib/python2.7/site-packages/blaze/__init__.py", line 18, in <module>
from .utils import ignoring
File "/home/ssanderson/.virtualenvs/blaze/local/lib/python2.7/site-packages/blaze/utils.py", line 7, in <module>
from cytoolz import nth
ImportError: No module named cytoolz
```
Is there a reason cytoolz isn't in the strict requirements if it's necessary to even import the top-level module? | 1.0 | cytoolz is required to import blaze, but it's not listed in requirements_strict.txt - In a fresh virtualenv, `pip install blaze && python -c "import blaze"` fails with:
```
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/ssanderson/.virtualenvs/blaze/local/lib/python2.7/site-packages/blaze/__init__.py", line 18, in <module>
from .utils import ignoring
File "/home/ssanderson/.virtualenvs/blaze/local/lib/python2.7/site-packages/blaze/utils.py", line 7, in <module>
from cytoolz import nth
ImportError: No module named cytoolz
```
Is there a reason cytoolz isn't in the strict requirements if it's necessary to even import the top-level module? | non_priority | cytoolz is required to import blaze but it s not listed in requirements strict txt in a fresh virtualenv pip install blaze python c import blaze fails with traceback most recent call last file line in file home ssanderson virtualenvs blaze local lib site packages blaze init py line in from utils import ignoring file home ssanderson virtualenvs blaze local lib site packages blaze utils py line in from cytoolz import nth importerror no module named cytoolz is there a reason cytoolz isn t in the strict requirements if it s necessary to even import the top level module | 0 |
363,886 | 25,472,481,958 | IssuesEvent | 2022-11-25 11:24:42 | UnBArqDsw2022-2/2022.2_G4_IDotPet | https://api.github.com/repos/UnBArqDsw2022-2/2022.2_G4_IDotPet | opened | Diagrama de Estados | documentation | <!-- Certifique-se de ser uma tarefa bem contida. Certifique-se da possibilidade de desmembrar a issue em issues melhores e, caso seja possível, o faça -->
# Descrição:
<!-- Dê os objetivos da issue, para quê serve, qual issue afeta, que artefato é criado/alterado. Ao citar outras issues, utilize o código delas: #Número_da_issue -->
Essa issue tem como objetivo a elaboração do documento de Diagrama de Estados.
# Tarefas:
<!-- Não economize na listagem de tarefas -->
- [ ] Elaborar Diagrama de Estados (Pedro e Herick)
- [ ] Revisar Diagrama de Estados (Eduardo e Kayro)
# Critério de aceitação:
<!-- O revisor da issue deve marcar esses critérios antes de fechá-la -->
- [ ] Documento de Diagrama de Estados confeccionado.
- [ ] Documento de Diagrama de Estados revisado.
| 1.0 | Diagrama de Estados - <!-- Certifique-se de ser uma tarefa bem contida. Certifique-se da possibilidade de desmembrar a issue em issues melhores e, caso seja possível, o faça -->
# Descrição:
<!-- Dê os objetivos da issue, para quê serve, qual issue afeta, que artefato é criado/alterado. Ao citar outras issues, utilize o código delas: #Número_da_issue -->
Essa issue tem como objetivo a elaboração do documento de Diagrama de Estados.
# Tarefas:
<!-- Não economize na listagem de tarefas -->
- [ ] Elaborar Diagrama de Estados (Pedro e Herick)
- [ ] Revisar Diagrama de Estados (Eduardo e Kayro)
# Critério de aceitação:
<!-- O revisor da issue deve marcar esses critérios antes de fechá-la -->
- [ ] Documento de Diagrama de Estados confeccionado.
- [ ] Documento de Diagrama de Estados revisado.
| non_priority | diagrama de estados descrição essa issue tem como objetivo a elaboração do documento de diagrama de estados tarefas elaborar diagrama de estados pedro e herick revisar diagrama de estados eduardo e kayro critério de aceitação documento de diagrama de estados confeccionado documento de diagrama de estados revisado | 0 |
335,049 | 30,007,610,863 | IssuesEvent | 2023-06-26 13:24:58 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | Failing test: APM API Integration tests (basic).x-pack/test/apm_api_integration/tests/dependencies/top_spans·spec·ts - APM API tests basic no data Top dependency spans when data is loaded without a kuery or environment returns the correct spans for the requested spanName | Team:APM failed-test apm:needs-test | A test failed on a tracked branch
```
Error: expected { '@timestamp': 1609459620000,
spanName: '/_search',
serviceName: 'java',
agentName: 'java',
duration: 100000,
outcome: 'success',
transactionType: 'request',
transactionName: 'GET /api/my-endpoint' } to sort of equal { '@timestamp': 1609459200000,
agentName: 'java',
duration: 100000,
serviceName: 'java',
spanName: '/_search',
transactionName: 'GET /api/my-endpoint',
transactionType: 'request',
outcome: 'success' }
at Assertion.assert (expect.js:100:11)
at Assertion.eql (expect.js:244:8)
at Context.<anonymous> (top_spans.spec.ts:158:79)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Object.apply (wrap_function.js:73:16) {
actual: '{\n' +
' "@timestamp": 1609459620000\n' +
' "agentName": "java"\n' +
' "duration": 100000\n' +
' "outcome": "success"\n' +
' "serviceName": "java"\n' +
' "spanName": "/_search"\n' +
' "transactionName": "GET /api/my-endpoint"\n' +
' "transactionType": "request"\n' +
'}',
expected: '{\n' +
' "@timestamp": 1609459200000\n' +
' "agentName": "java"\n' +
' "duration": 100000\n' +
' "outcome": "success"\n' +
' "serviceName": "java"\n' +
' "spanName": "/_search"\n' +
' "transactionName": "GET /api/my-endpoint"\n' +
' "transactionType": "request"\n' +
'}',
showDiff: true
}
```
First failure: [CI Build - 8.7](https://buildkite.com/elastic/kibana-on-merge/builds/28263#01870bd3-68a9-4165-88bf-11841fc76c4f)
<!-- kibanaCiData = {"failed-test":{"test.class":"APM API Integration tests (basic).x-pack/test/apm_api_integration/tests/dependencies/top_spans·spec·ts","test.name":"APM API tests basic no data Top dependency spans when data is loaded without a kuery or environment returns the correct spans for the requested spanName","test.failCount":1}} --> | 2.0 | Failing test: APM API Integration tests (basic).x-pack/test/apm_api_integration/tests/dependencies/top_spans·spec·ts - APM API tests basic no data Top dependency spans when data is loaded without a kuery or environment returns the correct spans for the requested spanName - A test failed on a tracked branch
```
Error: expected { '@timestamp': 1609459620000,
spanName: '/_search',
serviceName: 'java',
agentName: 'java',
duration: 100000,
outcome: 'success',
transactionType: 'request',
transactionName: 'GET /api/my-endpoint' } to sort of equal { '@timestamp': 1609459200000,
agentName: 'java',
duration: 100000,
serviceName: 'java',
spanName: '/_search',
transactionName: 'GET /api/my-endpoint',
transactionType: 'request',
outcome: 'success' }
at Assertion.assert (expect.js:100:11)
at Assertion.eql (expect.js:244:8)
at Context.<anonymous> (top_spans.spec.ts:158:79)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Object.apply (wrap_function.js:73:16) {
actual: '{\n' +
' "@timestamp": 1609459620000\n' +
' "agentName": "java"\n' +
' "duration": 100000\n' +
' "outcome": "success"\n' +
' "serviceName": "java"\n' +
' "spanName": "/_search"\n' +
' "transactionName": "GET /api/my-endpoint"\n' +
' "transactionType": "request"\n' +
'}',
expected: '{\n' +
' "@timestamp": 1609459200000\n' +
' "agentName": "java"\n' +
' "duration": 100000\n' +
' "outcome": "success"\n' +
' "serviceName": "java"\n' +
' "spanName": "/_search"\n' +
' "transactionName": "GET /api/my-endpoint"\n' +
' "transactionType": "request"\n' +
'}',
showDiff: true
}
```
First failure: [CI Build - 8.7](https://buildkite.com/elastic/kibana-on-merge/builds/28263#01870bd3-68a9-4165-88bf-11841fc76c4f)
<!-- kibanaCiData = {"failed-test":{"test.class":"APM API Integration tests (basic).x-pack/test/apm_api_integration/tests/dependencies/top_spans·spec·ts","test.name":"APM API tests basic no data Top dependency spans when data is loaded without a kuery or environment returns the correct spans for the requested spanName","test.failCount":1}} --> | non_priority | failing test apm api integration tests basic x pack test apm api integration tests dependencies top spans·spec·ts apm api tests basic no data top dependency spans when data is loaded without a kuery or environment returns the correct spans for the requested spanname a test failed on a tracked branch error expected timestamp spanname search servicename java agentname java duration outcome success transactiontype request transactionname get api my endpoint to sort of equal timestamp agentname java duration servicename java spanname search transactionname get api my endpoint transactiontype request outcome success at assertion assert expect js at assertion eql expect js at context top spans spec ts at runmicrotasks at processticksandrejections node internal process task queues at object apply wrap function js actual n timestamp n agentname java n duration n outcome success n servicename java n spanname search n transactionname get api my endpoint n transactiontype request n expected n timestamp n agentname java n duration n outcome success n servicename java n spanname search n transactionname get api my endpoint n transactiontype request n showdiff true first failure | 0 |
179,842 | 14,723,482,283 | IssuesEvent | 2021-01-06 00:32:14 | Perl/perl5 | https://api.github.com/repos/Perl/perl5 | opened | [doc] Make clear \p{Decomposition_Type: wide} etc. possible | Needs Triage documentation | On perlunicode,
```
"\p{Decomposition_Type: Non_Canonical}" (Short: "\p{Dt=NonCanon}")
```
needs to be changed to e.g.,
```
"\p{Decomposition_Type: type}" (Short: "\p{Dt=type}")
where type is one of "wide", "compat", "Non_Canonical" (or short: "Non_Canon"), ...
```
otherwise only clever readers will realize that more type than just
Non_Canonical can be used here!
| 1.0 | [doc] Make clear \p{Decomposition_Type: wide} etc. possible - On perlunicode,
```
"\p{Decomposition_Type: Non_Canonical}" (Short: "\p{Dt=NonCanon}")
```
needs to be changed to e.g.,
```
"\p{Decomposition_Type: type}" (Short: "\p{Dt=type}")
where type is one of "wide", "compat", "Non_Canonical" (or short: "Non_Canon"), ...
```
otherwise only clever readers will realize that more type than just
Non_Canonical can be used here!
| non_priority | make clear p decomposition type wide etc possible on perlunicode p decomposition type non canonical short p dt noncanon needs to be changed to e g p decomposition type type short p dt type where type is one of wide compat non canonical or short non canon otherwise only clever readers will realize that more type than just non canonical can be used here | 0 |
431,719 | 30,248,051,183 | IssuesEvent | 2023-07-06 18:05:36 | orb-community/orb | https://api.github.com/repos/orb-community/orb | closed | Website: suggestions for the content of "Documentation" part | documentation | This issue refers to the results of a review of the orb documentation. The idea is that the points are not lost/forgotten and can be revisited. THERE IS NO ACTION TO BE TAKEN BEFORE ANY FINAL DECISION OF THE PO/PM/VP.
## "Documentation" content:
- Configuration files information is missing:
New:
Old:
- This orb policy description is missing:
- This second header could be like "Orb + Pktvisor Policy Reference"
- This link is invalid:
- DHCP metrics description is empty:
- These link are invalid:
_Originally posted by @manrodrigues in https://github.com/ns1labs/orb/issues/1860#issuecomment-1289350892_
| 1.0 | Website: suggestions for the content of "Documentation" part - This issue refers to the results of a review of the orb documentation. The idea is that the points are not lost/forgotten and can be revisited. THERE IS NO ACTION TO BE TAKEN BEFORE ANY FINAL DECISION OF THE PO/PM/VP.
## "Documentation" content:
- Configuration files information is missing:
New:
Old:
- This orb policy description is missing:
- This second header could be like "Orb + Pktvisor Policy Reference"
- This link is invalid:
- DHCP metrics description is empty:
- These link are invalid:
_Originally posted by @manrodrigues in https://github.com/ns1labs/orb/issues/1860#issuecomment-1289350892_
| non_priority | website suggestions for the content of documentation part this issue refers to the results of a review of the orb documentation the idea is that the points are not lost forgotten and can be revisited there is no action to be taken before any final decision of the po pm vp documentation content configuration files information is missing new old this orb policy description is missing this second header could be like orb pktvisor policy reference this link is invalid dhcp metrics description is empty these link are invalid originally posted by manrodrigues in | 0 |
796 | 2,515,186,190 | IssuesEvent | 2015-01-15 16:57:56 | Hemisphere-Project/HPlayer | https://api.github.com/repos/Hemisphere-Project/HPlayer | closed | status sent recursively after first s/getStatus call | testing | When the s/getStatus OSC message is sent, /status response comes recursively (instead of one call / one response as it might be expected) | 1.0 | status sent recursively after first s/getStatus call - When the s/getStatus OSC message is sent, /status response comes recursively (instead of one call / one response as it might be expected) | non_priority | status sent recursively after first s getstatus call when the s getstatus osc message is sent status response comes recursively instead of one call one response as it might be expected | 0 |
89,869 | 15,855,949,161 | IssuesEvent | 2021-04-08 01:09:05 | rsoreq/django-DefectDojo | https://api.github.com/repos/rsoreq/django-DefectDojo | opened | CVE-2021-21238 (Medium) detected in pysaml2-6.4.0-py2.py3-none-any.whl | security vulnerability | ## CVE-2021-21238 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>pysaml2-6.4.0-py2.py3-none-any.whl</b></p></summary>
<p>Python implementation of SAML Version 2 Standard</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/0b/6c/6e3dac20536b2838a546d36ddae9dcd80b3b6f09cc3dc94ccc83c0c5bc69/pysaml2-6.4.0-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/0b/6c/6e3dac20536b2838a546d36ddae9dcd80b3b6f09cc3dc94ccc83c0c5bc69/pysaml2-6.4.0-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: django-DefectDojo</p>
<p>Path to vulnerable library: django-DefectDojo,django-DefectDojo/requirements.txt</p>
<p>
Dependency Hierarchy:
- django_saml2_auth-2.2.1.tar.gz (Root Library)
- :x: **pysaml2-6.4.0-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
PySAML2 is a pure python implementation of SAML Version 2 Standard. PySAML2 before 6.5.0 has an improper verification of cryptographic signature vulnerability. All users of pysaml2 that need to validate signed SAML documents are impacted. The vulnerability is a variant of XML Signature wrapping because it did not validate the SAML document against an XML schema. This allowed invalid XML documents to be processed and such a document can trick pysaml2 with a wrapped signature. This is fixed in PySAML2 6.5.0.
<p>Publish Date: 2021-01-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21238>CVE-2021-21238</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/IdentityPython/pysaml2/security/advisories/GHSA-f4g9-h89h-jgv9">https://github.com/IdentityPython/pysaml2/security/advisories/GHSA-f4g9-h89h-jgv9</a></p>
<p>Release Date: 2021-01-21</p>
<p>Fix Resolution: pysaml2 - 6.5.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Python","packageName":"pysaml2","packageVersion":"6.4.0","packageFilePaths":["django-DefectDojo","/requirements.txt"],"isTransitiveDependency":true,"dependencyTree":"django-saml2-auth:2.2.1;pysaml2:6.4.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"pysaml2 - 6.5.0"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-21238","vulnerabilityDetails":"PySAML2 is a pure python implementation of SAML Version 2 Standard. PySAML2 before 6.5.0 has an improper verification of cryptographic signature vulnerability. All users of pysaml2 that need to validate signed SAML documents are impacted. The vulnerability is a variant of XML Signature wrapping because it did not validate the SAML document against an XML schema. This allowed invalid XML documents to be processed and such a document can trick pysaml2 with a wrapped signature. This is fixed in PySAML2 6.5.0.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21238","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2021-21238 (Medium) detected in pysaml2-6.4.0-py2.py3-none-any.whl - ## CVE-2021-21238 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>pysaml2-6.4.0-py2.py3-none-any.whl</b></p></summary>
<p>Python implementation of SAML Version 2 Standard</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/0b/6c/6e3dac20536b2838a546d36ddae9dcd80b3b6f09cc3dc94ccc83c0c5bc69/pysaml2-6.4.0-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/0b/6c/6e3dac20536b2838a546d36ddae9dcd80b3b6f09cc3dc94ccc83c0c5bc69/pysaml2-6.4.0-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: django-DefectDojo</p>
<p>Path to vulnerable library: django-DefectDojo,django-DefectDojo/requirements.txt</p>
<p>
Dependency Hierarchy:
- django_saml2_auth-2.2.1.tar.gz (Root Library)
- :x: **pysaml2-6.4.0-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
PySAML2 is a pure python implementation of SAML Version 2 Standard. PySAML2 before 6.5.0 has an improper verification of cryptographic signature vulnerability. All users of pysaml2 that need to validate signed SAML documents are impacted. The vulnerability is a variant of XML Signature wrapping because it did not validate the SAML document against an XML schema. This allowed invalid XML documents to be processed and such a document can trick pysaml2 with a wrapped signature. This is fixed in PySAML2 6.5.0.
<p>Publish Date: 2021-01-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21238>CVE-2021-21238</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/IdentityPython/pysaml2/security/advisories/GHSA-f4g9-h89h-jgv9">https://github.com/IdentityPython/pysaml2/security/advisories/GHSA-f4g9-h89h-jgv9</a></p>
<p>Release Date: 2021-01-21</p>
<p>Fix Resolution: pysaml2 - 6.5.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Python","packageName":"pysaml2","packageVersion":"6.4.0","packageFilePaths":["django-DefectDojo","/requirements.txt"],"isTransitiveDependency":true,"dependencyTree":"django-saml2-auth:2.2.1;pysaml2:6.4.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"pysaml2 - 6.5.0"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-21238","vulnerabilityDetails":"PySAML2 is a pure python implementation of SAML Version 2 Standard. PySAML2 before 6.5.0 has an improper verification of cryptographic signature vulnerability. All users of pysaml2 that need to validate signed SAML documents are impacted. The vulnerability is a variant of XML Signature wrapping because it did not validate the SAML document against an XML schema. This allowed invalid XML documents to be processed and such a document can trick pysaml2 with a wrapped signature. This is fixed in PySAML2 6.5.0.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21238","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in none any whl cve medium severity vulnerability vulnerable library none any whl python implementation of saml version standard library home page a href path to dependency file django defectdojo path to vulnerable library django defectdojo django defectdojo requirements txt dependency hierarchy django auth tar gz root library x none any whl vulnerable library found in base branch master vulnerability details is a pure python implementation of saml version standard before has an improper verification of cryptographic signature vulnerability all users of that need to validate signed saml documents are impacted the vulnerability is a variant of xml signature wrapping because it did not validate the saml document against an xml schema this allowed invalid xml documents to be processed and such a document can trick with a wrapped signature this is fixed in publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree django auth isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier cve vulnerabilitydetails is a pure python implementation of saml version standard before has an improper verification of cryptographic signature vulnerability all users of that need to validate signed saml documents are impacted the vulnerability is a variant of xml signature wrapping because it did not validate the saml document against an xml schema this allowed invalid xml documents to be processed and such a document can trick with a wrapped signature this is fixed in vulnerabilityurl | 0 |
7,622 | 18,677,492,106 | IssuesEvent | 2021-10-31 20:08:25 | kubernetes/test-infra | https://api.github.com/repos/kubernetes/test-infra | closed | Create a label "do-not-merge/flake-free-test-needed" for Conformance Promotion PR's | sig/testing sig/architecture kind/feature sig/contributor-experience lifecycle/rotten area/conformance | **Why we need this label:**
To increase participation on Conformance Promotion PR's.
The Promotion PR will be created directly after the e2e test PR merge and the `do-not-merge/flake-free-test-needed` label will be added manually.
- This increases the exposure time of the Promotion PR in the community before merging.
- Allow discussion/correction of code merged in an e2e test,
**Automation** - **Non**
The label is planned to be added and removed **by humans with no automation** currently.
/sig testing
/sig architecture
/area conformance | 1.0 | Create a label "do-not-merge/flake-free-test-needed" for Conformance Promotion PR's - **Why we need this label:**
To increase participation on Conformance Promotion PR's.
The Promotion PR will be created directly after the e2e test PR merge and the `do-not-merge/flake-free-test-needed` label will be added manually.
- This increases the exposure time of the Promotion PR in the community before merging.
- Allow discussion/correction of code merged in an e2e test,
**Automation** - **Non**
The label is planned to be added and removed **by humans with no automation** currently.
/sig testing
/sig architecture
/area conformance | non_priority | create a label do not merge flake free test needed for conformance promotion pr s why we need this label to increase participation on conformance promotion pr s the promotion pr will be created directly after the test pr merge and the do not merge flake free test needed label will be added manually this increases the exposure time of the promotion pr in the community before merging allow discussion correction of code merged in an test automation non the label is planned to be added and removed by humans with no automation currently sig testing sig architecture area conformance | 0 |
5,973 | 5,240,999,162 | IssuesEvent | 2017-01-31 14:41:16 | letsencrypt/boulder | https://api.github.com/repos/letsencrypt/boulder | closed | Optimize `certificateStatus` Table Usage | area/tools kind/performance status/blocked | The [SQL Query](https://github.com/letsencrypt/boulder/blob/master/cmd/ocsp-updater/main.go#L199:L206) used by the `findStaleOCSPResponses` function of `cmd/ocsp-updater.go` is appearing in the slow query logs with runtime exceeding what we would expect.
An `explain` from production shows:
```
MariaDB> EXPLAIN
-> SELECT cs.*
-> FROM certificateStatus AS cs
-> JOIN certificates AS cert
-> ON cs.serial = cert.serial
-> WHERE cs.ocspLastUpdated < '2016-05-28 12:09:53.377823'
-> AND cert.expires > now()
-> ORDER BY cs.ocspLastUpdated ASC
-> LIMIT 6000;
+------+-------------+-------+--------+-----------------------------------------------+---------------------------------------+---------+-----------------------+---------+-----------------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+------+-------------+-------+--------+-----------------------------------------------+---------------------------------------+---------+-----------------------+---------+-----------------------+
| 1 | SIMPLE | cs | range | PRIMARY,ocspLastUpdated_certificateStatus_idx | ocspLastUpdated_certificateStatus_idx | 8 | NULL | 1890210 | Using index condition |
| 1 | SIMPLE | cert | eq_ref | PRIMARY | PRIMARY | 767 | cs.serial | 1 | Using where |
+------+-------------+-------+--------+-----------------------------------------------+---------------------------------------+---------+-----------------------+---------+-----------------------+
```
Of particular note is the `rows` count on the first join, showing a whopping `1890210` rows being evaluated. Presumably this includes a great deal of expired certificates. The intention of the query is to exclude expired entries by using the `AND cert.expires > now()` clause but this is happening after the join is completed and the `cert` table rows are under consideration.
We should restructure this query such that `certificateStatus` rows corresponding to expired certificates can be discarded prior to the first join. This should improve the query performance and hopefully address some RPC timeouts we are seeing that may be caused by the increased database contention from the slow stale OCSP responses query.
| True | Optimize `certificateStatus` Table Usage - The [SQL Query](https://github.com/letsencrypt/boulder/blob/master/cmd/ocsp-updater/main.go#L199:L206) used by the `findStaleOCSPResponses` function of `cmd/ocsp-updater.go` is appearing in the slow query logs with runtime exceeding what we would expect.
An `explain` from production shows:
```
MariaDB> EXPLAIN
-> SELECT cs.*
-> FROM certificateStatus AS cs
-> JOIN certificates AS cert
-> ON cs.serial = cert.serial
-> WHERE cs.ocspLastUpdated < '2016-05-28 12:09:53.377823'
-> AND cert.expires > now()
-> ORDER BY cs.ocspLastUpdated ASC
-> LIMIT 6000;
+------+-------------+-------+--------+-----------------------------------------------+---------------------------------------+---------+-----------------------+---------+-----------------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+------+-------------+-------+--------+-----------------------------------------------+---------------------------------------+---------+-----------------------+---------+-----------------------+
| 1 | SIMPLE | cs | range | PRIMARY,ocspLastUpdated_certificateStatus_idx | ocspLastUpdated_certificateStatus_idx | 8 | NULL | 1890210 | Using index condition |
| 1 | SIMPLE | cert | eq_ref | PRIMARY | PRIMARY | 767 | cs.serial | 1 | Using where |
+------+-------------+-------+--------+-----------------------------------------------+---------------------------------------+---------+-----------------------+---------+-----------------------+
```
Of particular note is the `rows` count on the first join, showing a whopping `1890210` rows being evaluated. Presumably this includes a great deal of expired certificates. The intention of the query is to exclude expired entries by using the `AND cert.expires > now()` clause but this is happening after the join is completed and the `cert` table rows are under consideration.
We should restructure this query such that `certificateStatus` rows corresponding to expired certificates can be discarded prior to the first join. This should improve the query performance and hopefully address some RPC timeouts we are seeing that may be caused by the increased database contention from the slow stale OCSP responses query.
| non_priority | optimize certificatestatus table usage the used by the findstaleocspresponses function of cmd ocsp updater go is appearing in the slow query logs with runtime exceeding what we would expect an explain from production shows mariadb explain select cs from certificatestatus as cs join certificates as cert on cs serial cert serial where cs ocsplastupdated and cert expires now order by cs ocsplastupdated asc limit id select type table type possible keys key key len ref rows extra simple cs range primary ocsplastupdated certificatestatus idx ocsplastupdated certificatestatus idx null using index condition simple cert eq ref primary primary cs serial using where of particular note is the rows count on the first join showing a whopping rows being evaluated presumably this includes a great deal of expired certificates the intention of the query is to exclude expired entries by using the and cert expires now clause but this is happening after the join is completed and the cert table rows are under consideration we should restructure this query such that certificatestatus rows corresponding to expired certificates can be discarded prior to the first join this should improve the query performance and hopefully address some rpc timeouts we are seeing that may be caused by the increased database contention from the slow stale ocsp responses query | 0 |
31,432 | 8,695,213,114 | IssuesEvent | 2018-12-04 14:40:17 | bazelbuild/continuous-integration | https://api.github.com/repos/bazelbuild/continuous-integration | closed | Windows: buildkite user doesn't have read permission to C:\android_sdk and C:\android_ndk | P1 bug buildkite | This is causing https://buildkite.com/bazel/android-testing/builds/53 and https://github.com/bazelbuild/bazel/pull/6699#issuecomment-439667509
@fweikert Can you help rebuild the Windows image and grant bk user the necessary permission to `C:\android_sdk` and `C:\android_ndk`?
`icacls "C:\android_sdk" /grant bk-worker-windo\b:F /T & icacls "C:\android_ndk" /grant bk-worker-windo\b:F /T
` can fix the problem but I'm not sure full permission is necessary.
| 1.0 | Windows: buildkite user doesn't have read permission to C:\android_sdk and C:\android_ndk - This is causing https://buildkite.com/bazel/android-testing/builds/53 and https://github.com/bazelbuild/bazel/pull/6699#issuecomment-439667509
@fweikert Can you help rebuild the Windows image and grant bk user the necessary permission to `C:\android_sdk` and `C:\android_ndk`?
`icacls "C:\android_sdk" /grant bk-worker-windo\b:F /T & icacls "C:\android_ndk" /grant bk-worker-windo\b:F /T
` can fix the problem but I'm not sure full permission is necessary.
| non_priority | windows buildkite user doesn t have read permission to c android sdk and c android ndk this is causing and fweikert can you help rebuild the windows image and grant bk user the necessary permission to c android sdk and c android ndk icacls c android sdk grant bk worker windo b f t icacls c android ndk grant bk worker windo b f t can fix the problem but i m not sure full permission is necessary | 0 |
41,418 | 12,832,094,360 | IssuesEvent | 2020-07-07 07:00:33 | rvvergara/javascript-weather-app | https://api.github.com/repos/rvvergara/javascript-weather-app | closed | CVE-2019-15657 (High) detected in eslint-utils-1.3.1.tgz | security vulnerability | ## CVE-2019-15657 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>eslint-utils-1.3.1.tgz</b></p></summary>
<p>Utilities for ESLint plugins.</p>
<p>Library home page: <a href="https://registry.npmjs.org/eslint-utils/-/eslint-utils-1.3.1.tgz">https://registry.npmjs.org/eslint-utils/-/eslint-utils-1.3.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/javascript-weather-app/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/javascript-weather-app/node_modules/eslint-utils/package.json</p>
<p>
Dependency Hierarchy:
- eslint-5.14.1.tgz (Root Library)
- :x: **eslint-utils-1.3.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rvvergara/javascript-weather-app/commit/df7c850d057a4428a074b3a4087d7492939d7b33">df7c850d057a4428a074b3a4087d7492939d7b33</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In eslint-utils before 1.4.1, the getStaticValue function can execute arbitrary code.
<p>Publish Date: 2019-08-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-15657>CVE-2019-15657</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15657">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15657</a></p>
<p>Release Date: 2019-08-26</p>
<p>Fix Resolution: eslint-utils - 1.4.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2019-15657 (High) detected in eslint-utils-1.3.1.tgz - ## CVE-2019-15657 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>eslint-utils-1.3.1.tgz</b></p></summary>
<p>Utilities for ESLint plugins.</p>
<p>Library home page: <a href="https://registry.npmjs.org/eslint-utils/-/eslint-utils-1.3.1.tgz">https://registry.npmjs.org/eslint-utils/-/eslint-utils-1.3.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/javascript-weather-app/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/javascript-weather-app/node_modules/eslint-utils/package.json</p>
<p>
Dependency Hierarchy:
- eslint-5.14.1.tgz (Root Library)
- :x: **eslint-utils-1.3.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rvvergara/javascript-weather-app/commit/df7c850d057a4428a074b3a4087d7492939d7b33">df7c850d057a4428a074b3a4087d7492939d7b33</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In eslint-utils before 1.4.1, the getStaticValue function can execute arbitrary code.
<p>Publish Date: 2019-08-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-15657>CVE-2019-15657</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15657">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15657</a></p>
<p>Release Date: 2019-08-26</p>
<p>Fix Resolution: eslint-utils - 1.4.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in eslint utils tgz cve high severity vulnerability vulnerable library eslint utils tgz utilities for eslint plugins library home page a href path to dependency file tmp ws scm javascript weather app package json path to vulnerable library tmp ws scm javascript weather app node modules eslint utils package json dependency hierarchy eslint tgz root library x eslint utils tgz vulnerable library found in head commit a href vulnerability details in eslint utils before the getstaticvalue function can execute arbitrary code publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution eslint utils step up your open source security game with whitesource | 0 |
66,635 | 14,790,239,701 | IssuesEvent | 2021-01-12 11:44:25 | turkdevops/update-electron-app | https://api.github.com/repos/turkdevops/update-electron-app | opened | CVE-2020-26226 (High) detected in semantic-release-15.14.0.tgz | security vulnerability | ## CVE-2020-26226 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>semantic-release-15.14.0.tgz</b></p></summary>
<p>Automated semver compliant package publishing</p>
<p>Library home page: <a href="https://registry.npmjs.org/semantic-release/-/semantic-release-15.14.0.tgz">https://registry.npmjs.org/semantic-release/-/semantic-release-15.14.0.tgz</a></p>
<p>Path to dependency file: update-electron-app/package.json</p>
<p>Path to vulnerable library: update-electron-app/node_modules/semantic-release/package.json</p>
<p>
Dependency Hierarchy:
- :x: **semantic-release-15.14.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/update-electron-app/commit/970df96c18d5acb77ddd8361f6533bd4301267dc">970df96c18d5acb77ddd8361f6533bd4301267dc</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>
In the npm package semantic-release before version 17.2.3, secrets that would normally be masked by `semantic-release` can be accidentally disclosed if they contain characters that become encoded when included in a URL. Secrets that do not contain characters that become encoded when included in a URL are already masked properly. The issue is fixed in version 17.2.3.
<p>Publish Date: 2020-11-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26226>CVE-2020-26226</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/semantic-release/semantic-release/security/advisories/GHSA-r2j6-p67h-q639">https://github.com/semantic-release/semantic-release/security/advisories/GHSA-r2j6-p67h-q639</a></p>
<p>Release Date: 2020-11-18</p>
<p>Fix Resolution: 17.2.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-26226 (High) detected in semantic-release-15.14.0.tgz - ## CVE-2020-26226 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>semantic-release-15.14.0.tgz</b></p></summary>
<p>Automated semver compliant package publishing</p>
<p>Library home page: <a href="https://registry.npmjs.org/semantic-release/-/semantic-release-15.14.0.tgz">https://registry.npmjs.org/semantic-release/-/semantic-release-15.14.0.tgz</a></p>
<p>Path to dependency file: update-electron-app/package.json</p>
<p>Path to vulnerable library: update-electron-app/node_modules/semantic-release/package.json</p>
<p>
Dependency Hierarchy:
- :x: **semantic-release-15.14.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/update-electron-app/commit/970df96c18d5acb77ddd8361f6533bd4301267dc">970df96c18d5acb77ddd8361f6533bd4301267dc</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>
In the npm package semantic-release before version 17.2.3, secrets that would normally be masked by `semantic-release` can be accidentally disclosed if they contain characters that become encoded when included in a URL. Secrets that do not contain characters that become encoded when included in a URL are already masked properly. The issue is fixed in version 17.2.3.
<p>Publish Date: 2020-11-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26226>CVE-2020-26226</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/semantic-release/semantic-release/security/advisories/GHSA-r2j6-p67h-q639">https://github.com/semantic-release/semantic-release/security/advisories/GHSA-r2j6-p67h-q639</a></p>
<p>Release Date: 2020-11-18</p>
<p>Fix Resolution: 17.2.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in semantic release tgz cve high severity vulnerability vulnerable library semantic release tgz automated semver compliant package publishing library home page a href path to dependency file update electron app package json path to vulnerable library update electron app node modules semantic release package json dependency hierarchy x semantic release tgz vulnerable library found in head commit a href found in base branch master vulnerability details in the npm package semantic release before version secrets that would normally be masked by semantic release can be accidentally disclosed if they contain characters that become encoded when included in a url secrets that do not contain characters that become encoded when included in a url are already masked properly the issue is fixed in version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
230,501 | 18,672,934,765 | IssuesEvent | 2021-10-31 03:00:48 | pandas-dev/pandas | https://api.github.com/repos/pandas-dev/pandas | closed | Unexpected result when setting a row by a dict | good first issue Needs Tests | #### Code Sample, a copy-pastable example if possible
```python
import numpy as np
import pandas as pd
persons = [
{
'name': ''.join([
np.random.choice([chr(x) for x in range(97, 97 + 26)])
for i in range(5)
]),
'age': np.random.randint(0, 100),
'sex': np.random.choice(['male', 'female']),
'job': np.random.choice(['staff', 'cook', 'student']),
'birthday': np.random.choice(pd.date_range('1990-01-01', '2010-01-01')),
'hobby': np.random.choice(['cs', 'war3', 'dota'])
}
for i in range(10)
]
df = pd.DataFrame(persons)
df.set_index('birthday', inplace=True)
print(df)
df.iloc[0] = {
'name': 'john',
'age': int(10),
'sex': 'male',
'hobby': 'nohobby',
'job': 'haha'
}
print(df)
```
#### Problem description
```
age hobby job name sex
birthday
2007-12-31 name age sex hobby job
2004-07-31 20 dota student uwxhn female
2001-10-22 34 war3 cook udknv female
2002-10-13 91 dota cook bofcv female
1992-05-25 54 war3 cook tcqew male
2009-09-02 95 war3 staff jcolr female
1998-12-15 61 war3 student dibkw female
2004-07-03 4 war3 student mntqh male
2000-06-08 88 war3 staff jknxm female
2006-10-19 82 cs student asrpz male
```
Have no idea why the keys are set to the rows.
#### Expected Output
```
age hobby job name sex
birthday
2007-12-31 10 nohobby haha john male
2004-07-31 20 dota student uwxhn female
2001-10-22 34 war3 cook udknv female
2002-10-13 91 dota cook bofcv female
1992-05-25 54 war3 cook tcqew male
2009-09-02 95 war3 staff jcolr female
1998-12-15 61 war3 student dibkw female
2004-07-03 4 war3 student mntqh male
2000-06-08 88 war3 staff jknxm female
2006-10-19 82 cs student asrpz male
```
#### Output of ``pd.show_versions()``
<details>
INSTALLED VERSIONS
------------------
commit: None
python: 3.6.1.final.0
python-bits: 64
OS: Darwin
OS-release: 16.6.0
machine: x86_64
processor: i386
byteorder: little
LC_ALL: en_US.UTF-8
LANG: en_US.UTF-8
LOCALE: en_US.UTF-8
pandas: 0.20.1
pytest: 3.0.7
pip: 9.0.1
setuptools: 35.0.2
Cython: 0.25.2
numpy: 1.12.1
scipy: 0.19.0
xarray: 0.9.5
IPython: 6.0.0
sphinx: 1.5.5
patsy: 0.4.1
dateutil: 2.6.0
pytz: 2017.2
blosc: None
bottleneck: 1.2.0
tables: 3.4.2
numexpr: 2.6.2
feather: None
matplotlib: 2.0.2
openpyxl: 2.4.7
xlrd: 1.0.0
xlwt: None
xlsxwriter: None
lxml: 3.7.3
bs4: 4.6.0
html5lib: 0.999999999
sqlalchemy: 1.1.9
pymysql: None
psycopg2: None
jinja2: 2.9.6
s3fs: None
pandas_gbq: None
pandas_datareader: None
</details>
| 1.0 | Unexpected result when setting a row by a dict - #### Code Sample, a copy-pastable example if possible
```python
import numpy as np
import pandas as pd
persons = [
{
'name': ''.join([
np.random.choice([chr(x) for x in range(97, 97 + 26)])
for i in range(5)
]),
'age': np.random.randint(0, 100),
'sex': np.random.choice(['male', 'female']),
'job': np.random.choice(['staff', 'cook', 'student']),
'birthday': np.random.choice(pd.date_range('1990-01-01', '2010-01-01')),
'hobby': np.random.choice(['cs', 'war3', 'dota'])
}
for i in range(10)
]
df = pd.DataFrame(persons)
df.set_index('birthday', inplace=True)
print(df)
df.iloc[0] = {
'name': 'john',
'age': int(10),
'sex': 'male',
'hobby': 'nohobby',
'job': 'haha'
}
print(df)
```
#### Problem description
```
age hobby job name sex
birthday
2007-12-31 name age sex hobby job
2004-07-31 20 dota student uwxhn female
2001-10-22 34 war3 cook udknv female
2002-10-13 91 dota cook bofcv female
1992-05-25 54 war3 cook tcqew male
2009-09-02 95 war3 staff jcolr female
1998-12-15 61 war3 student dibkw female
2004-07-03 4 war3 student mntqh male
2000-06-08 88 war3 staff jknxm female
2006-10-19 82 cs student asrpz male
```
Have no idea why the keys are set to the rows.
#### Expected Output
```
age hobby job name sex
birthday
2007-12-31 10 nohobby haha john male
2004-07-31 20 dota student uwxhn female
2001-10-22 34 war3 cook udknv female
2002-10-13 91 dota cook bofcv female
1992-05-25 54 war3 cook tcqew male
2009-09-02 95 war3 staff jcolr female
1998-12-15 61 war3 student dibkw female
2004-07-03 4 war3 student mntqh male
2000-06-08 88 war3 staff jknxm female
2006-10-19 82 cs student asrpz male
```
#### Output of ``pd.show_versions()``
<details>
INSTALLED VERSIONS
------------------
commit: None
python: 3.6.1.final.0
python-bits: 64
OS: Darwin
OS-release: 16.6.0
machine: x86_64
processor: i386
byteorder: little
LC_ALL: en_US.UTF-8
LANG: en_US.UTF-8
LOCALE: en_US.UTF-8
pandas: 0.20.1
pytest: 3.0.7
pip: 9.0.1
setuptools: 35.0.2
Cython: 0.25.2
numpy: 1.12.1
scipy: 0.19.0
xarray: 0.9.5
IPython: 6.0.0
sphinx: 1.5.5
patsy: 0.4.1
dateutil: 2.6.0
pytz: 2017.2
blosc: None
bottleneck: 1.2.0
tables: 3.4.2
numexpr: 2.6.2
feather: None
matplotlib: 2.0.2
openpyxl: 2.4.7
xlrd: 1.0.0
xlwt: None
xlsxwriter: None
lxml: 3.7.3
bs4: 4.6.0
html5lib: 0.999999999
sqlalchemy: 1.1.9
pymysql: None
psycopg2: None
jinja2: 2.9.6
s3fs: None
pandas_gbq: None
pandas_datareader: None
</details>
| non_priority | unexpected result when setting a row by a dict code sample a copy pastable example if possible python import numpy as np import pandas as pd persons name join np random choice for i in range age np random randint sex np random choice job np random choice birthday np random choice pd date range hobby np random choice for i in range df pd dataframe persons df set index birthday inplace true print df df iloc name john age int sex male hobby nohobby job haha print df problem description age hobby job name sex birthday name age sex hobby job dota student uwxhn female cook udknv female dota cook bofcv female cook tcqew male staff jcolr female student dibkw female student mntqh male staff jknxm female cs student asrpz male have no idea why the keys are set to the rows expected output age hobby job name sex birthday nohobby haha john male dota student uwxhn female cook udknv female dota cook bofcv female cook tcqew male staff jcolr female student dibkw female student mntqh male staff jknxm female cs student asrpz male output of pd show versions installed versions commit none python final python bits os darwin os release machine processor byteorder little lc all en us utf lang en us utf locale en us utf pandas pytest pip setuptools cython numpy scipy xarray ipython sphinx patsy dateutil pytz blosc none bottleneck tables numexpr feather none matplotlib openpyxl xlrd xlwt none xlsxwriter none lxml sqlalchemy pymysql none none none pandas gbq none pandas datareader none | 0 |
241,612 | 26,256,854,850 | IssuesEvent | 2023-01-06 02:03:20 | Baneeishaque/ask-med-pharma_Wordpress | https://api.github.com/repos/Baneeishaque/ask-med-pharma_Wordpress | opened | CVE-2021-23382 (High) detected in postcss-7.0.18.tgz, postcss-7.0.17.tgz | security vulnerability | ## CVE-2021-23382 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>postcss-7.0.18.tgz</b>, <b>postcss-7.0.17.tgz</b></p></summary>
<p>
<details><summary><b>postcss-7.0.18.tgz</b></p></summary>
<p>Tool for transforming styles with JS plugins</p>
<p>Library home page: <a href="https://registry.npmjs.org/postcss/-/postcss-7.0.18.tgz">https://registry.npmjs.org/postcss/-/postcss-7.0.18.tgz</a></p>
<p>Path to dependency file: /wp-content/themes/twentytwenty/package.json</p>
<p>Path to vulnerable library: /wp-content/themes/twentytwenty/node_modules/postcss-cli/node_modules/postcss/package.json</p>
<p>
Dependency Hierarchy:
- postcss-cli-6.1.3.tgz (Root Library)
- :x: **postcss-7.0.18.tgz** (Vulnerable Library)
</details>
<details><summary><b>postcss-7.0.17.tgz</b></p></summary>
<p>Tool for transforming styles with JS plugins</p>
<p>Library home page: <a href="https://registry.npmjs.org/postcss/-/postcss-7.0.17.tgz">https://registry.npmjs.org/postcss/-/postcss-7.0.17.tgz</a></p>
<p>Path to dependency file: /wp-content/themes/twentynineteen/package.json</p>
<p>Path to vulnerable library: /wp-content/themes/twentynineteen/node_modules/postcss/package.json</p>
<p>
Dependency Hierarchy:
- autoprefixer-9.6.0.tgz (Root Library)
- :x: **postcss-7.0.17.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Baneeishaque/ask-med-pharma_Wordpress/commit/6464f631e15c1e1c888b6d505d934cf06ab4d0a2">6464f631e15c1e1c888b6d505d934cf06ab4d0a2</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>
The package postcss before 8.2.13 are vulnerable to Regular Expression Denial of Service (ReDoS) via getAnnotationURL() and loadAnnotation() in lib/previous-map.js. The vulnerable regexes are caused mainly by the sub-pattern \/\*\s* sourceMappingURL=(.*).
<p>Publish Date: 2021-04-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23382>CVE-2021-23382</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382</a></p>
<p>Release Date: 2021-04-26</p>
<p>Fix Resolution (postcss): 7.0.36</p>
<p>Direct dependency fix Resolution (postcss-cli): 7.0.0</p><p>Fix Resolution (postcss): 7.0.36</p>
<p>Direct dependency fix Resolution (autoprefixer): 9.6.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-23382 (High) detected in postcss-7.0.18.tgz, postcss-7.0.17.tgz - ## CVE-2021-23382 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>postcss-7.0.18.tgz</b>, <b>postcss-7.0.17.tgz</b></p></summary>
<p>
<details><summary><b>postcss-7.0.18.tgz</b></p></summary>
<p>Tool for transforming styles with JS plugins</p>
<p>Library home page: <a href="https://registry.npmjs.org/postcss/-/postcss-7.0.18.tgz">https://registry.npmjs.org/postcss/-/postcss-7.0.18.tgz</a></p>
<p>Path to dependency file: /wp-content/themes/twentytwenty/package.json</p>
<p>Path to vulnerable library: /wp-content/themes/twentytwenty/node_modules/postcss-cli/node_modules/postcss/package.json</p>
<p>
Dependency Hierarchy:
- postcss-cli-6.1.3.tgz (Root Library)
- :x: **postcss-7.0.18.tgz** (Vulnerable Library)
</details>
<details><summary><b>postcss-7.0.17.tgz</b></p></summary>
<p>Tool for transforming styles with JS plugins</p>
<p>Library home page: <a href="https://registry.npmjs.org/postcss/-/postcss-7.0.17.tgz">https://registry.npmjs.org/postcss/-/postcss-7.0.17.tgz</a></p>
<p>Path to dependency file: /wp-content/themes/twentynineteen/package.json</p>
<p>Path to vulnerable library: /wp-content/themes/twentynineteen/node_modules/postcss/package.json</p>
<p>
Dependency Hierarchy:
- autoprefixer-9.6.0.tgz (Root Library)
- :x: **postcss-7.0.17.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Baneeishaque/ask-med-pharma_Wordpress/commit/6464f631e15c1e1c888b6d505d934cf06ab4d0a2">6464f631e15c1e1c888b6d505d934cf06ab4d0a2</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>
The package postcss before 8.2.13 are vulnerable to Regular Expression Denial of Service (ReDoS) via getAnnotationURL() and loadAnnotation() in lib/previous-map.js. The vulnerable regexes are caused mainly by the sub-pattern \/\*\s* sourceMappingURL=(.*).
<p>Publish Date: 2021-04-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23382>CVE-2021-23382</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382</a></p>
<p>Release Date: 2021-04-26</p>
<p>Fix Resolution (postcss): 7.0.36</p>
<p>Direct dependency fix Resolution (postcss-cli): 7.0.0</p><p>Fix Resolution (postcss): 7.0.36</p>
<p>Direct dependency fix Resolution (autoprefixer): 9.6.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in postcss tgz postcss tgz cve high severity vulnerability vulnerable libraries postcss tgz postcss tgz postcss tgz tool for transforming styles with js plugins library home page a href path to dependency file wp content themes twentytwenty package json path to vulnerable library wp content themes twentytwenty node modules postcss cli node modules postcss package json dependency hierarchy postcss cli tgz root library x postcss tgz vulnerable library postcss tgz tool for transforming styles with js plugins library home page a href path to dependency file wp content themes twentynineteen package json path to vulnerable library wp content themes twentynineteen node modules postcss package json dependency hierarchy autoprefixer tgz root library x postcss tgz vulnerable library found in head commit a href found in base branch master vulnerability details the package postcss before are vulnerable to regular expression denial of service redos via getannotationurl and loadannotation in lib previous map js the vulnerable regexes are caused mainly by the sub pattern s sourcemappingurl publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution postcss direct dependency fix resolution postcss cli fix resolution postcss direct dependency fix resolution autoprefixer step up your open source security game with mend | 0 |
194,509 | 22,262,010,552 | IssuesEvent | 2022-06-10 01:58:55 | Nivaskumark/kernel_v4.19.72 | https://api.github.com/repos/Nivaskumark/kernel_v4.19.72 | reopened | CVE-2020-0432 (High) detected in linuxlinux-4.19.83 | security vulnerability | ## CVE-2020-0432 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.19.83</b></p></summary>
<p>
<p>Apache Software Foundation (ASF)</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Nivaskumark/kernel_v4.19.72/commit/7665378059da10e5ded7efbfccc88efce9e51dfc">7665378059da10e5ded7efbfccc88efce9e51dfc</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>/drivers/staging/most/net/net.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/staging/most/net/net.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In skb_to_mamac of networking.c, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-143560807
<p>Publish Date: 2020-09-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-0432>CVE-2020-0432</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2020-0432">https://www.linuxkernelcves.com/cves/CVE-2020-0432</a></p>
<p>Release Date: 2020-09-17</p>
<p>Fix Resolution: v4.4.213,v4.9.213,v4.14.170,v4.19.101,v5.4.17,v5.5.1,v5.6-rc1</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-0432 (High) detected in linuxlinux-4.19.83 - ## CVE-2020-0432 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.19.83</b></p></summary>
<p>
<p>Apache Software Foundation (ASF)</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Nivaskumark/kernel_v4.19.72/commit/7665378059da10e5ded7efbfccc88efce9e51dfc">7665378059da10e5ded7efbfccc88efce9e51dfc</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>/drivers/staging/most/net/net.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/staging/most/net/net.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In skb_to_mamac of networking.c, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-143560807
<p>Publish Date: 2020-09-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-0432>CVE-2020-0432</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2020-0432">https://www.linuxkernelcves.com/cves/CVE-2020-0432</a></p>
<p>Release Date: 2020-09-17</p>
<p>Fix Resolution: v4.4.213,v4.9.213,v4.14.170,v4.19.101,v5.4.17,v5.5.1,v5.6-rc1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in linuxlinux cve high severity vulnerability vulnerable library linuxlinux apache software foundation asf library home page a href found in head commit a href found in base branch master vulnerable source files drivers staging most net net c drivers staging most net net c vulnerability details in skb to mamac of networking c there is a possible out of bounds write due to an integer overflow this could lead to local escalation of privilege with no additional execution privileges needed user interaction is not needed for exploitation product androidversions android kernelandroid id a publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
39,575 | 20,074,215,488 | IssuesEvent | 2022-02-04 10:48:31 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | reopened | Linq count is slower than linq where count | area-System.Linq tenet-performance untriaged | Linq Where before count is a lot faster than count with a predicate.
```c#
[MemoryDiagnoser]
[Orderer(SummaryOrderPolicy.FastestToSlowest)]
public class Benchmarks
{
private static List<int> Numbers = new(1000);
static Benchmarks()
{
Random random = new Random(10);
for (int i = 0; i < 1000; i++)
{
Numbers.Add(random.Next(int.MinValue, int.MaxValue));
}
}
[Benchmark]
public int LinqCount()
{
return Numbers.Count(num => num > int.MaxValue / 2);
}
[Benchmark]
public int LinqWhereCount()
{
return Numbers.Where(num => num > int.MaxValue / 2).Count();
}
}
```
I came across a reason for this is the `WhereListIterator<TSource>` which has a `GetCount` method. This method uses a normal indexer-based forloop. This `GetCount` method is used by the `Count` method without predicate parameters. But the count with predicate will use a normal for each loop.
So the general solution would be to check if the source collection is an `IList` or `IReadonlyList`. If it is then just use the indexer-based forloop because most of the time it would be an `IList` or `IReadonlyList` | True | Linq count is slower than linq where count - Linq Where before count is a lot faster than count with a predicate.
```c#
[MemoryDiagnoser]
[Orderer(SummaryOrderPolicy.FastestToSlowest)]
public class Benchmarks
{
private static List<int> Numbers = new(1000);
static Benchmarks()
{
Random random = new Random(10);
for (int i = 0; i < 1000; i++)
{
Numbers.Add(random.Next(int.MinValue, int.MaxValue));
}
}
[Benchmark]
public int LinqCount()
{
return Numbers.Count(num => num > int.MaxValue / 2);
}
[Benchmark]
public int LinqWhereCount()
{
return Numbers.Where(num => num > int.MaxValue / 2).Count();
}
}
```
I came across a reason for this is the `WhereListIterator<TSource>` which has a `GetCount` method. This method uses a normal indexer-based forloop. This `GetCount` method is used by the `Count` method without predicate parameters. But the count with predicate will use a normal for each loop.
So the general solution would be to check if the source collection is an `IList` or `IReadonlyList`. If it is then just use the indexer-based forloop because most of the time it would be an `IList` or `IReadonlyList` | non_priority | linq count is slower than linq where count linq where before count is a lot faster than count with a predicate c public class benchmarks private static list numbers new static benchmarks random random new random for int i i i numbers add random next int minvalue int maxvalue public int linqcount return numbers count num num int maxvalue public int linqwherecount return numbers where num num int maxvalue count i came across a reason for this is the wherelistiterator which has a getcount method this method uses a normal indexer based forloop this getcount method is used by the count method without predicate parameters but the count with predicate will use a normal for each loop so the general solution would be to check if the source collection is an ilist or ireadonlylist if it is then just use the indexer based forloop because most of the time it would be an ilist or ireadonlylist | 0 |
152,758 | 12,125,989,433 | IssuesEvent | 2020-04-22 16:19:42 | Arquisoft/viade_en2b | https://api.github.com/repos/Arquisoft/viade_en2b | closed | Setup Gatling environment | enhancement testing | ## Feature description
Correctly install and setup Gatling to perform load tests against the application.
**Expected behaviour**: Gatling functions correctly and tests work as expected.
**Other development information, extensions and problems**:
* The Gatling installation will be added as another Docker container, in combination with the node-solid-server and Viade ones.
### Testing scenarios
#### Linked pull requests
| 1.0 | Setup Gatling environment - ## Feature description
Correctly install and setup Gatling to perform load tests against the application.
**Expected behaviour**: Gatling functions correctly and tests work as expected.
**Other development information, extensions and problems**:
* The Gatling installation will be added as another Docker container, in combination with the node-solid-server and Viade ones.
### Testing scenarios
#### Linked pull requests
| non_priority | setup gatling environment feature description correctly install and setup gatling to perform load tests against the application expected behaviour gatling functions correctly and tests work as expected other development information extensions and problems the gatling installation will be added as another docker container in combination with the node solid server and viade ones testing scenarios linked pull requests | 0 |
71,136 | 9,480,499,195 | IssuesEvent | 2019-04-20 18:21:34 | NourDjihan/ClassNameAnalyser | https://api.github.com/repos/NourDjihan/ClassNameAnalyser | closed | Add an example to README.md explaining how to use your tool | documentation | Something like this:
```Smalltalk
featureSelector := DMFeatureSelector new.
blueprintBuilder := DMClassNameBlueprintBuilder new.
"Packages to be analysed"
packages := #(PackageName1 PackageName2).
"Extracting features from packages"
conceptualModel := featureSelector applyFeaturesOn: packages.
"Building a model of a ClassNameBlueprint visualization"
viewModel := blueprintBuilder buildModelFrom: conceptualModel.
``` | 1.0 | Add an example to README.md explaining how to use your tool - Something like this:
```Smalltalk
featureSelector := DMFeatureSelector new.
blueprintBuilder := DMClassNameBlueprintBuilder new.
"Packages to be analysed"
packages := #(PackageName1 PackageName2).
"Extracting features from packages"
conceptualModel := featureSelector applyFeaturesOn: packages.
"Building a model of a ClassNameBlueprint visualization"
viewModel := blueprintBuilder buildModelFrom: conceptualModel.
``` | non_priority | add an example to readme md explaining how to use your tool something like this smalltalk featureselector dmfeatureselector new blueprintbuilder dmclassnameblueprintbuilder new packages to be analysed packages extracting features from packages conceptualmodel featureselector applyfeatureson packages building a model of a classnameblueprint visualization viewmodel blueprintbuilder buildmodelfrom conceptualmodel | 0 |
94,037 | 27,101,211,165 | IssuesEvent | 2023-02-15 08:48:54 | alibaba/MNN | https://api.github.com/repos/alibaba/MNN | closed | Pod 'MNN'的问题 | building iOS | 在iOS工程中使用 pod 'MNN', :git => 'https://github.com/alibaba/MNN.git'， 发现Pods库中的3rd_party中没有half/half.hpp。然后在Xcode的编译中就会显示找不到half.hpp文件。必须手动添加这个文件到Pods中才能编译通过。
想问下这个是不是mnn.podspec编写中的bug。 | 1.0 | Pod 'MNN'的问题 - 在iOS工程中使用 pod 'MNN', :git => 'https://github.com/alibaba/MNN.git'， 发现Pods库中的3rd_party中没有half/half.hpp。然后在Xcode的编译中就会显示找不到half.hpp文件。必须手动添加这个文件到Pods中才能编译通过。
想问下这个是不是mnn.podspec编写中的bug。 | non_priority | pod mnn 的问题 在ios工程中使用 pod mnn git party中没有half half hpp。然后在xcode的编译中就会显示找不到half hpp文件。必须手动添加这个文件到pods中才能编译通过。 想问下这个是不是mnn podspec编写中的bug。 | 0 |
234,396 | 19,178,605,577 | IssuesEvent | 2021-12-04 02:09:57 | dotnet/aspnetcore | https://api.github.com/repos/dotnet/aspnetcore | closed | FileLoggerProcessorTests.RollsTextFiles | test-failure area-runtime | ## Failing Test(s)
Microsoft.AspNetCore.HttpLogging.FileLoggerProcessorTests.RollsTextFiles
## Error Message
```text
Assert.Equal() Failure
↓ (pos 0)
Expected: Message two\n
Actual:
↑ (pos 0)
Stack Trace:
at Microsoft.AspNetCore.HttpLogging.FileLoggerProcessorTests.RollsTextFiles() in /_/src/Middleware/HttpLogging/test/FileLoggerProcessorTests.cs:line 117
```
https://github.com/dotnet/aspnetcore/blob/69eb4b38bca90bb830f290a6eaa5a61650dc87ac/src/Middleware/HttpLogging/test/FileLoggerProcessorTests.cs#L117
## Build
https://dev.azure.com/dnceng/public/_build/results?buildId=1231336&view=ms.vss-test-web.build-test-results-tab&runId=36670362&resultId=110218&paneView=debug
(Alpine.312.Amd64.Open)Ubuntu.1804.Amd64.Open | 1.0 | FileLoggerProcessorTests.RollsTextFiles - ## Failing Test(s)
Microsoft.AspNetCore.HttpLogging.FileLoggerProcessorTests.RollsTextFiles
## Error Message
```text
Assert.Equal() Failure
↓ (pos 0)
Expected: Message two\n
Actual:
↑ (pos 0)
Stack Trace:
at Microsoft.AspNetCore.HttpLogging.FileLoggerProcessorTests.RollsTextFiles() in /_/src/Middleware/HttpLogging/test/FileLoggerProcessorTests.cs:line 117
```
https://github.com/dotnet/aspnetcore/blob/69eb4b38bca90bb830f290a6eaa5a61650dc87ac/src/Middleware/HttpLogging/test/FileLoggerProcessorTests.cs#L117
## Build
https://dev.azure.com/dnceng/public/_build/results?buildId=1231336&view=ms.vss-test-web.build-test-results-tab&runId=36670362&resultId=110218&paneView=debug
(Alpine.312.Amd64.Open)Ubuntu.1804.Amd64.Open | non_priority | fileloggerprocessortests rollstextfiles failing test s microsoft aspnetcore httplogging fileloggerprocessortests rollstextfiles error message text assert equal failure ↓ pos expected message two n actual ↑ pos stack trace at microsoft aspnetcore httplogging fileloggerprocessortests rollstextfiles in src middleware httplogging test fileloggerprocessortests cs line build alpine open ubuntu open | 0 |
24,631 | 6,557,463,488 | IssuesEvent | 2017-09-06 17:31:50 | xhqiao89/hydrocatalogtest | https://api.github.com/repos/xhqiao89/hydrocatalogtest | opened | NWIS DV no time zone | CodePlex | <b>valentinedwv[CodePlex]</b> <br />USGS daily values does not have a time zone on the data value.
| 1.0 | NWIS DV no time zone - <b>valentinedwv[CodePlex]</b> <br />USGS daily values does not have a time zone on the data value.
| non_priority | nwis dv no time zone valentinedwv usgs daily values does not have a time zone on the data value | 0 |
439,617 | 30,706,485,126 | IssuesEvent | 2023-07-27 06:39:17 | public-ui/kolibri | https://api.github.com/repos/public-ui/kolibri | closed | Vereinheitlichung: _list komplett deprecaten | Documentation good first issue vor V2 API | Abhängig von:
- https://github.com/public-ui/kolibri/issues/4201
- https://github.com/public-ui/kolibri/issues/4200
Für alle Input, Select, Textarea das Property _list deprecaten.
Kommentar: Wird ersatzlos gestrichen, weil die Breite i.d.R. mit CSS gemacht wird. | 1.0 | Vereinheitlichung: _list komplett deprecaten - Abhängig von:
- https://github.com/public-ui/kolibri/issues/4201
- https://github.com/public-ui/kolibri/issues/4200
Für alle Input, Select, Textarea das Property _list deprecaten.
Kommentar: Wird ersatzlos gestrichen, weil die Breite i.d.R. mit CSS gemacht wird. | non_priority | vereinheitlichung list komplett deprecaten abhängig von für alle input select textarea das property list deprecaten kommentar wird ersatzlos gestrichen weil die breite i d r mit css gemacht wird | 0 |
6,824 | 10,004,869,655 | IssuesEvent | 2019-07-13 08:31:44 | renovatebot/renovate | https://api.github.com/repos/renovatebot/renovate | closed | [Question] Bitbucket-server removes approvals on update | #bitbucket help wanted needs-requirements pri4-low | ### Which Renovate are you using? CLI, App, or Pro
CLI
### Which platform are you using? GitHub, GitLab, Bitbucket Azure DevOps
Bitbucket Server v5.16.6
### Have you checked the logs? Don't forget to include them if relevant
If I can get the issue to show up again I will. Maybe a few days though.
### What is your question?
A bit of background into the scenario, assuming there are two PRs to the same project:
1. User approves both PRs
2. Renovate runs and merges one
3. Renovate runs and rebases
Note: This causes the approval to be removed
4. Renovate runs but doesn't merge because PR no longer has approvals
Under Pull Requests -> General we do have the following settings
But to my knowledge Renovate doesn't change the source branch when rebasing so I'm unsure why we are losing the approvals. Other information that maybe useful:
- We have turned everything off in Merge checks
- Merge strategy is Fast-forward--ff
- The only workflow hooks that are enabled are a commit checker to make sure an issue is attached to the PR and the Jenkins CI hook
The ultimate question here is what config can I setup so that upon rebase, I don't lose approvals? | 1.0 | [Question] Bitbucket-server removes approvals on update - ### Which Renovate are you using? CLI, App, or Pro
CLI
### Which platform are you using? GitHub, GitLab, Bitbucket Azure DevOps
Bitbucket Server v5.16.6
### Have you checked the logs? Don't forget to include them if relevant
If I can get the issue to show up again I will. Maybe a few days though.
### What is your question?
A bit of background into the scenario, assuming there are two PRs to the same project:
1. User approves both PRs
2. Renovate runs and merges one
3. Renovate runs and rebases
Note: This causes the approval to be removed
4. Renovate runs but doesn't merge because PR no longer has approvals
Under Pull Requests -> General we do have the following settings
But to my knowledge Renovate doesn't change the source branch when rebasing so I'm unsure why we are losing the approvals. Other information that maybe useful:
- We have turned everything off in Merge checks
- Merge strategy is Fast-forward--ff
- The only workflow hooks that are enabled are a commit checker to make sure an issue is attached to the PR and the Jenkins CI hook
The ultimate question here is what config can I setup so that upon rebase, I don't lose approvals? | non_priority | bitbucket server removes approvals on update which renovate are you using cli app or pro cli which platform are you using github gitlab bitbucket azure devops bitbucket server have you checked the logs don t forget to include them if relevant if i can get the issue to show up again i will maybe a few days though what is your question a bit of background into the scenario assuming there are two prs to the same project user approves both prs renovate runs and merges one renovate runs and rebases note this causes the approval to be removed renovate runs but doesn t merge because pr no longer has approvals under pull requests general we do have the following settings but to my knowledge renovate doesn t change the source branch when rebasing so i m unsure why we are losing the approvals other information that maybe useful we have turned everything off in merge checks merge strategy is fast forward ff the only workflow hooks that are enabled are a commit checker to make sure an issue is attached to the pr and the jenkins ci hook the ultimate question here is what config can i setup so that upon rebase i don t lose approvals | 0 |
100,167 | 16,484,052,816 | IssuesEvent | 2021-05-24 15:25:26 | gdcorp-action-public-forks/keep-a-changelog-new-release | https://api.github.com/repos/gdcorp-action-public-forks/keep-a-changelog-new-release | closed | CVE-2019-20149 (High) detected in kind-of-6.0.2.tgz - autoclosed | security vulnerability | ## CVE-2019-20149 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>kind-of-6.0.2.tgz</b></p></summary>
<p>Get the native type of a value.</p>
<p>Library home page: <a href="https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz">https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz</a></p>
<p>Path to dependency file: keep-a-changelog-new-release/package.json</p>
<p>Path to vulnerable library: keep-a-changelog-new-release/node_modules/kind-of</p>
<p>
Dependency Hierarchy:
- webpack-cli-3.3.10.tgz (Root Library)
- global-modules-2.0.0.tgz
- global-prefix-3.0.0.tgz
- :x: **kind-of-6.0.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/gdcorp-action-public-forks/keep-a-changelog-new-release/commit/0e201c270deac5c59f9e4ea7726d6ee5225ab235">0e201c270deac5c59f9e4ea7726d6ee5225ab235</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>
ctorName in index.js in kind-of v6.0.2 allows external user input to overwrite certain internal attributes via a conflicting name, as demonstrated by 'constructor': {'name':'Symbol'}. Hence, a crafted payload can overwrite this builtin attribute to manipulate the type detection result.
<p>Publish Date: 2019-12-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20149>CVE-2019-20149</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20149">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20149</a></p>
<p>Release Date: 2019-12-30</p>
<p>Fix Resolution: 6.0.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"kind-of","packageVersion":"6.0.2","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"webpack-cli:3.3.10;global-modules:2.0.0;global-prefix:3.0.0;kind-of:6.0.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"6.0.3"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-20149","vulnerabilityDetails":"ctorName in index.js in kind-of v6.0.2 allows external user input to overwrite certain internal attributes via a conflicting name, as demonstrated by \u0027constructor\u0027: {\u0027name\u0027:\u0027Symbol\u0027}. Hence, a crafted payload can overwrite this builtin attribute to manipulate the type detection result.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20149","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2019-20149 (High) detected in kind-of-6.0.2.tgz - autoclosed - ## CVE-2019-20149 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>kind-of-6.0.2.tgz</b></p></summary>
<p>Get the native type of a value.</p>
<p>Library home page: <a href="https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz">https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz</a></p>
<p>Path to dependency file: keep-a-changelog-new-release/package.json</p>
<p>Path to vulnerable library: keep-a-changelog-new-release/node_modules/kind-of</p>
<p>
Dependency Hierarchy:
- webpack-cli-3.3.10.tgz (Root Library)
- global-modules-2.0.0.tgz
- global-prefix-3.0.0.tgz
- :x: **kind-of-6.0.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/gdcorp-action-public-forks/keep-a-changelog-new-release/commit/0e201c270deac5c59f9e4ea7726d6ee5225ab235">0e201c270deac5c59f9e4ea7726d6ee5225ab235</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>
ctorName in index.js in kind-of v6.0.2 allows external user input to overwrite certain internal attributes via a conflicting name, as demonstrated by 'constructor': {'name':'Symbol'}. Hence, a crafted payload can overwrite this builtin attribute to manipulate the type detection result.
<p>Publish Date: 2019-12-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20149>CVE-2019-20149</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20149">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20149</a></p>
<p>Release Date: 2019-12-30</p>
<p>Fix Resolution: 6.0.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"kind-of","packageVersion":"6.0.2","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"webpack-cli:3.3.10;global-modules:2.0.0;global-prefix:3.0.0;kind-of:6.0.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"6.0.3"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-20149","vulnerabilityDetails":"ctorName in index.js in kind-of v6.0.2 allows external user input to overwrite certain internal attributes via a conflicting name, as demonstrated by \u0027constructor\u0027: {\u0027name\u0027:\u0027Symbol\u0027}. Hence, a crafted payload can overwrite this builtin attribute to manipulate the type detection result.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20149","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in kind of tgz autoclosed cve high severity vulnerability vulnerable library kind of tgz get the native type of a value library home page a href path to dependency file keep a changelog new release package json path to vulnerable library keep a changelog new release node modules kind of dependency hierarchy webpack cli tgz root library global modules tgz global prefix tgz x kind of tgz vulnerable library found in head commit a href found in base branch master vulnerability details ctorname in index js in kind of allows external user input to overwrite certain internal attributes via a conflicting name as demonstrated by constructor name symbol hence a crafted payload can overwrite this builtin attribute to manipulate the type detection result publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree webpack cli global modules global prefix kind of isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier cve vulnerabilitydetails ctorname in index js in kind of allows external user input to overwrite certain internal attributes via a conflicting name as demonstrated by hence a crafted payload can overwrite this builtin attribute to manipulate the type detection result vulnerabilityurl | 0 |
163,371 | 13,916,231,109 | IssuesEvent | 2020-10-21 02:47:38 | aws/aws-sdk-java-v2 | https://api.github.com/repos/aws/aws-sdk-java-v2 | closed | Cannot support Chinese | documentation needs-triage | <!--- Provide a general summary of the issue in the Title above -->
I am currently working on a speech recognition project, but the enumeration type in the languagecode class is not Chinese. Can I add the enumeration type “zn-CH” to the transcribeStreaming service?
## Describe the issue
<!--- A clear and concise description of the issue -->
## Links
<!-- Include links to affected documentation page(s) -->
| 1.0 | Cannot support Chinese - <!--- Provide a general summary of the issue in the Title above -->
I am currently working on a speech recognition project, but the enumeration type in the languagecode class is not Chinese. Can I add the enumeration type “zn-CH” to the transcribeStreaming service?
## Describe the issue
<!--- A clear and concise description of the issue -->
## Links
<!-- Include links to affected documentation page(s) -->
| non_priority | cannot support chinese i am currently working on a speech recognition project but the enumeration type in the languagecode class is not chinese can i add the enumeration type “zn ch” to the transcribestreaming service describe the issue links | 0 |
130,301 | 10,604,969,704 | IssuesEvent | 2019-10-10 19:22:47 | AnalyticalGraphicsInc/cesium | https://api.github.com/repos/AnalyticalGraphicsInc/cesium | closed | CI requestRenderMode tests suddenly randomly failing pretty often | test failure | I've had to restart travis several times because the below tests seem to randomly fail in all branches
```
1) moving the camera causes a new frame to be rendered in requestRenderMode
Scene/Scene
Error: Expected 2019-10-07T12:37:58.5349999999998545Z not to equal 2019-10-07T12:37:58.5349999999998545Z.
at <Jasmine>
at Build/Specs/Specs.js:162885:46
at UserContext.<anonymous> (Build/Specs/karma-main.js:943:34)
at <Jasmine>
2) successful completed requests causes a new frame to be rendered in requestRenderMode
Scene/Scene
Error: Expected 2019-10-07T12:37:58.5540000000000873Z not to equal 2019-10-07T12:37:58.5540000000000873Z.
at <Jasmine>
at Build/Specs/Specs.js:162935:46
at UserContext.<anonymous> (Build/Specs/karma-main.js:943:34)
at <Jasmine>
```
The top of the render function looks a little odd to me, why are we doing so much work before deciding to render? Why do we update the framestate even when a new frame isn't needed? And why don't we return if `shouldRender` is false? @ggetz I know you wrote this feature initially, do you have any thoughts here? Of course it doesn't look like this code has changed in several months (@loshjawrence you were the last person in here) so I'm not sure why this is a problem now.
https://github.com/AnalyticalGraphicsInc/cesium/blob/b5cf72aa3fbffb6e94ae93a46b8f24df7e97c5b5/Source/Scene/Scene.js#L3278-L3311 | 1.0 | CI requestRenderMode tests suddenly randomly failing pretty often - I've had to restart travis several times because the below tests seem to randomly fail in all branches
```
1) moving the camera causes a new frame to be rendered in requestRenderMode
Scene/Scene
Error: Expected 2019-10-07T12:37:58.5349999999998545Z not to equal 2019-10-07T12:37:58.5349999999998545Z.
at <Jasmine>
at Build/Specs/Specs.js:162885:46
at UserContext.<anonymous> (Build/Specs/karma-main.js:943:34)
at <Jasmine>
2) successful completed requests causes a new frame to be rendered in requestRenderMode
Scene/Scene
Error: Expected 2019-10-07T12:37:58.5540000000000873Z not to equal 2019-10-07T12:37:58.5540000000000873Z.
at <Jasmine>
at Build/Specs/Specs.js:162935:46
at UserContext.<anonymous> (Build/Specs/karma-main.js:943:34)
at <Jasmine>
```
The top of the render function looks a little odd to me, why are we doing so much work before deciding to render? Why do we update the framestate even when a new frame isn't needed? And why don't we return if `shouldRender` is false? @ggetz I know you wrote this feature initially, do you have any thoughts here? Of course it doesn't look like this code has changed in several months (@loshjawrence you were the last person in here) so I'm not sure why this is a problem now.
https://github.com/AnalyticalGraphicsInc/cesium/blob/b5cf72aa3fbffb6e94ae93a46b8f24df7e97c5b5/Source/Scene/Scene.js#L3278-L3311 | non_priority | ci requestrendermode tests suddenly randomly failing pretty often i ve had to restart travis several times because the below tests seem to randomly fail in all branches moving the camera causes a new frame to be rendered in requestrendermode scene scene error expected not to equal at at build specs specs js at usercontext build specs karma main js at successful completed requests causes a new frame to be rendered in requestrendermode scene scene error expected not to equal at at build specs specs js at usercontext build specs karma main js at the top of the render function looks a little odd to me why are we doing so much work before deciding to render why do we update the framestate even when a new frame isn t needed and why don t we return if shouldrender is false ggetz i know you wrote this feature initially do you have any thoughts here of course it doesn t look like this code has changed in several months loshjawrence you were the last person in here so i m not sure why this is a problem now | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.