Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 7 112 | repo_url stringlengths 36 141 | action stringclasses 3 values | title stringlengths 2 665 | labels stringlengths 4 554 | body stringlengths 3 235k | index stringclasses 6 values | text_combine stringlengths 96 235k | label stringclasses 2 values | text stringlengths 96 196k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
229,131 | 25,291,730,463 | IssuesEvent | 2022-11-17 01:08:47 | turkdevops/deploy-sourcegraph | https://api.github.com/repos/turkdevops/deploy-sourcegraph | closed | CVE-2018-16875 (High) detected in github.com/moby/moby-v1.13.1 - autoclosed | security vulnerability | ## CVE-2018-16875 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/moby/moby-v1.13.1</b></p></summary>
<p>Moby Project - a collaborative project for the container ecosystem to assemble container-based systems</p>
<p>
Dependency Hierarchy:
- github.com/pulumi/pulumi-v1.12.0 (Root Library)
- :x: **github.com/moby/moby-v1.13.1** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/deploy-sourcegraph/commit/5229a328bacd506bfc40230e7e5c497b323e9b8f">5229a328bacd506bfc40230e7e5c497b323e9b8f</a></p>
<p>Found in base branch: <b>pipeline/skip-integration-tests-for-renovate-insiders</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 crypto/x509 package of Go before 1.10.6 and 1.11.x before 1.11.3 does not limit the amount of work performed for each chain verification, which might allow attackers to craft pathological inputs leading to a CPU denial of service. Go TLS servers accepting client certificates and TLS clients are affected.
<p>Publish Date: 2018-12-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16875>CVE-2018-16875</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://nvd.nist.gov/vuln/detail/CVE-2018-16875">https://nvd.nist.gov/vuln/detail/CVE-2018-16875</a></p>
<p>Release Date: 2018-12-14</p>
<p>Fix Resolution: 1.10.6,1.11.3</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-2018-16875 (High) detected in github.com/moby/moby-v1.13.1 - autoclosed - ## CVE-2018-16875 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/moby/moby-v1.13.1</b></p></summary>
<p>Moby Project - a collaborative project for the container ecosystem to assemble container-based systems</p>
<p>
Dependency Hierarchy:
- github.com/pulumi/pulumi-v1.12.0 (Root Library)
- :x: **github.com/moby/moby-v1.13.1** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/deploy-sourcegraph/commit/5229a328bacd506bfc40230e7e5c497b323e9b8f">5229a328bacd506bfc40230e7e5c497b323e9b8f</a></p>
<p>Found in base branch: <b>pipeline/skip-integration-tests-for-renovate-insiders</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 crypto/x509 package of Go before 1.10.6 and 1.11.x before 1.11.3 does not limit the amount of work performed for each chain verification, which might allow attackers to craft pathological inputs leading to a CPU denial of service. Go TLS servers accepting client certificates and TLS clients are affected.
<p>Publish Date: 2018-12-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16875>CVE-2018-16875</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://nvd.nist.gov/vuln/detail/CVE-2018-16875">https://nvd.nist.gov/vuln/detail/CVE-2018-16875</a></p>
<p>Release Date: 2018-12-14</p>
<p>Fix Resolution: 1.10.6,1.11.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_infrastructure | cve high detected in github com moby moby autoclosed cve high severity vulnerability vulnerable library github com moby moby moby project a collaborative project for the container ecosystem to assemble container based systems dependency hierarchy github com pulumi pulumi root library x github com moby moby vulnerable library found in head commit a href found in base branch pipeline skip integration tests for renovate insiders vulnerability details the crypto package of go before and x before does not limit the amount of work performed for each chain verification which might allow attackers to craft pathological inputs leading to a cpu denial of service go tls servers accepting client certificates and tls clients are affected 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 |
36,086 | 17,439,940,035 | IssuesEvent | 2021-08-05 02:22:38 | infinyon/fluvio | https://api.github.com/repos/infinyon/fluvio | opened | [Tracking] Fluvio perf test harness integration | Performance tracking | The changes from the performance testing drafts need to be included in the repo but the scope of the branch is too broad for a single [PR](https://github.com/infinyon/fluvio/pull/1252). This issue is tracking each component so we can keep track of their merge status.
Several of these changes should be built with a feature flag. Perhaps split via: performance measurement support, data vis/export, and other cluster clients.
### Create generic Test driver for test instrumentation
- [ ] Centralize producer and consumer configuration (orig from Smoke test) so it could be reused in other tests
- [ ] Centralize producer send / consumer receive so it could be reused in other tests
- [ ] Configurable producer batch record size
- [ ] Configurable producer batch time period
- [ ] Record latency of producer traffic
- [ ] Record latency of consumer traffic
### Test reporting improvements
- [ ] Structured test data as csv row
- [ ] Default print performance stats
- [ ] Fix panic behavior to return more debugging info from panic or assert
### Interpret producer/consumer traffic characteristics, in terms of
- [ ] Latency as Percentile(50, 90, 99, 99.9) over test duration
- [ ] Throughput over test duration (Mbps x time)
### Rough draft graphs from test
- [ ] One set of data on a graph at a time (Scaling is not fixed)
- [ ] Raw CSV data export
- [ ] Tech debt: Better graphs
### Collect apples-to-apples test data for Fluvio
- [ ] x Kafka
- [ ] x Pulsar
Tech debt:
- Performance specific test harness (Design considerations vs flv-test including all the testing functions)
- Measurement sanity tests | True | [Tracking] Fluvio perf test harness integration - The changes from the performance testing drafts need to be included in the repo but the scope of the branch is too broad for a single [PR](https://github.com/infinyon/fluvio/pull/1252). This issue is tracking each component so we can keep track of their merge status.
Several of these changes should be built with a feature flag. Perhaps split via: performance measurement support, data vis/export, and other cluster clients.
### Create generic Test driver for test instrumentation
- [ ] Centralize producer and consumer configuration (orig from Smoke test) so it could be reused in other tests
- [ ] Centralize producer send / consumer receive so it could be reused in other tests
- [ ] Configurable producer batch record size
- [ ] Configurable producer batch time period
- [ ] Record latency of producer traffic
- [ ] Record latency of consumer traffic
### Test reporting improvements
- [ ] Structured test data as csv row
- [ ] Default print performance stats
- [ ] Fix panic behavior to return more debugging info from panic or assert
### Interpret producer/consumer traffic characteristics, in terms of
- [ ] Latency as Percentile(50, 90, 99, 99.9) over test duration
- [ ] Throughput over test duration (Mbps x time)
### Rough draft graphs from test
- [ ] One set of data on a graph at a time (Scaling is not fixed)
- [ ] Raw CSV data export
- [ ] Tech debt: Better graphs
### Collect apples-to-apples test data for Fluvio
- [ ] x Kafka
- [ ] x Pulsar
Tech debt:
- Performance specific test harness (Design considerations vs flv-test including all the testing functions)
- Measurement sanity tests | non_infrastructure | fluvio perf test harness integration the changes from the performance testing drafts need to be included in the repo but the scope of the branch is too broad for a single this issue is tracking each component so we can keep track of their merge status several of these changes should be built with a feature flag perhaps split via performance measurement support data vis export and other cluster clients create generic test driver for test instrumentation centralize producer and consumer configuration orig from smoke test so it could be reused in other tests centralize producer send consumer receive so it could be reused in other tests configurable producer batch record size configurable producer batch time period record latency of producer traffic record latency of consumer traffic test reporting improvements structured test data as csv row default print performance stats fix panic behavior to return more debugging info from panic or assert interpret producer consumer traffic characteristics in terms of latency as percentile over test duration throughput over test duration mbps x time rough draft graphs from test one set of data on a graph at a time scaling is not fixed raw csv data export tech debt better graphs collect apples to apples test data for fluvio x kafka x pulsar tech debt performance specific test harness design considerations vs flv test including all the testing functions measurement sanity tests | 0 |
33,998 | 28,076,786,910 | IssuesEvent | 2023-03-30 00:49:06 | dotnet/roslyn | https://api.github.com/repos/dotnet/roslyn | opened | [Infra] Re-enable tests that utilize `DotNetSdkMSBuildInstalled` | Area-Infrastructure Disabled Test | In order to re-enable we need an updated version of RoslynTools.MSBuild and we need to update our MSBuild version to 17.5.0: https://dev.azure.com/dnceng/public/_artifacts/feed/dotnet-eng/NuGet/RoslynTools.MSBuild/ | 1.0 | [Infra] Re-enable tests that utilize `DotNetSdkMSBuildInstalled` - In order to re-enable we need an updated version of RoslynTools.MSBuild and we need to update our MSBuild version to 17.5.0: https://dev.azure.com/dnceng/public/_artifacts/feed/dotnet-eng/NuGet/RoslynTools.MSBuild/ | infrastructure | re enable tests that utilize dotnetsdkmsbuildinstalled in order to re enable we need an updated version of roslyntools msbuild and we need to update our msbuild version to | 1 |
369,396 | 10,904,806,090 | IssuesEvent | 2019-11-20 09:30:25 | geosolutions-it/MapStore2 | https://api.github.com/repos/geosolutions-it/MapStore2 | closed | Layer filter issue when CRS changed | Accepted CRS Selector Priority: High bug geOrchestra | ### Description
With layer filters everything is fine until you try to edit the shape of a filter. Circle and rectangle shapes don't work correctly when you switch to one of the newly added projections. When you try to edit, for example, radius of a circle it disappears. With rectangles this problem persists even if one were to switch between the default projections(4326 and 3857).
### In case of Bug (otherwise remove this paragraph)
*Browser Affected*
(use this site: https://www.whatsmybrowser.org/ for non expert users)
- [x] Internet Explorer
- [x] Chrome
- [x] Firefox
- [x] Safari
*Steps to reproduce*
- Open a map with a vector layer
- Select the layer and open the layer filter tool
- Do a spatial filter and apply it then save and close the filter tool
- Change CRS from the CRS selector
- Select again the layer to open the layer filter tool
- Edit the spatial filter
*Expected Result*
- The filter ramains in the map and is updated according to user updates
*Current Result*
- The geometry on the map disappears
### Other useful information (optional):
| 1.0 | Layer filter issue when CRS changed - ### Description
With layer filters everything is fine until you try to edit the shape of a filter. Circle and rectangle shapes don't work correctly when you switch to one of the newly added projections. When you try to edit, for example, radius of a circle it disappears. With rectangles this problem persists even if one were to switch between the default projections(4326 and 3857).
### In case of Bug (otherwise remove this paragraph)
*Browser Affected*
(use this site: https://www.whatsmybrowser.org/ for non expert users)
- [x] Internet Explorer
- [x] Chrome
- [x] Firefox
- [x] Safari
*Steps to reproduce*
- Open a map with a vector layer
- Select the layer and open the layer filter tool
- Do a spatial filter and apply it then save and close the filter tool
- Change CRS from the CRS selector
- Select again the layer to open the layer filter tool
- Edit the spatial filter
*Expected Result*
- The filter ramains in the map and is updated according to user updates
*Current Result*
- The geometry on the map disappears
### Other useful information (optional):
| non_infrastructure | layer filter issue when crs changed description with layer filters everything is fine until you try to edit the shape of a filter circle and rectangle shapes don t work correctly when you switch to one of the newly added projections when you try to edit for example radius of a circle it disappears with rectangles this problem persists even if one were to switch between the default projections and in case of bug otherwise remove this paragraph browser affected use this site for non expert users internet explorer chrome firefox safari steps to reproduce open a map with a vector layer select the layer and open the layer filter tool do a spatial filter and apply it then save and close the filter tool change crs from the crs selector select again the layer to open the layer filter tool edit the spatial filter expected result the filter ramains in the map and is updated according to user updates current result the geometry on the map disappears other useful information optional | 0 |
546,378 | 16,010,740,806 | IssuesEvent | 2021-04-20 10:12:48 | datavisyn/tdp_core | https://api.github.com/repos/datavisyn/tdp_core | opened | FormDialog should allow access to Form instance | priority: medium type: bug | * Release number or git hash: 3916867f2d11b84d7a43e463f6c360fab092ef2f
* Web browser version and OS: Chrome 89
* Environment (local or deployed): both
### Steps to reproduce
1. Have a look at the implementation of a Score Dialog
2. Try to access the elements in the underlying form
### Observed behavior
* In order to get the selected values in a SELECT3 field for example, it is necessary to search for them manually in the HTML using selectors and `dialog.builder.form`. This is an unfortunate workaround because the code will break if there are any changes in the HTML.
### Expected behavior
* Add an accessor to the FormDialog class in order to be able to use functions such as `getElementById()`
| 1.0 | FormDialog should allow access to Form instance - * Release number or git hash: 3916867f2d11b84d7a43e463f6c360fab092ef2f
* Web browser version and OS: Chrome 89
* Environment (local or deployed): both
### Steps to reproduce
1. Have a look at the implementation of a Score Dialog
2. Try to access the elements in the underlying form
### Observed behavior
* In order to get the selected values in a SELECT3 field for example, it is necessary to search for them manually in the HTML using selectors and `dialog.builder.form`. This is an unfortunate workaround because the code will break if there are any changes in the HTML.
### Expected behavior
* Add an accessor to the FormDialog class in order to be able to use functions such as `getElementById()`
| non_infrastructure | formdialog should allow access to form instance release number or git hash web browser version and os chrome environment local or deployed both steps to reproduce have a look at the implementation of a score dialog try to access the elements in the underlying form observed behavior in order to get the selected values in a field for example it is necessary to search for them manually in the html using selectors and dialog builder form this is an unfortunate workaround because the code will break if there are any changes in the html expected behavior add an accessor to the formdialog class in order to be able to use functions such as getelementbyid | 0 |
13,913 | 10,544,105,590 | IssuesEvent | 2019-10-02 16:13:05 | angular/components | https://api.github.com/repos/angular/components | closed | build(release): generates invalid semver versions and breaks material.angular.io builds | P1 has pr infrastructure | #### Reproduction
Steps to reproduce:
1. Release a new version
#### Expected Behavior
Only valid semver should be used for the versions in https://github.com/angular/material2-docs-content/blob/8.2.x/package.json
#### Actual Behavior
We’re appending partial commit SHAs to the end of the versions, i.e. `8.2.0-c29c507`, `8.2.1-a5d2ed8`, and the latest `8.2.2-0462599`.
However, `8.2.2-0462599` is not valid semver, so yarn won’t install it.
You can check using this validator: https://jubianchi.github.io/semver-check/#/8.2.2-0462599/8.2.2-0462599
The leading `0` is the issue. It doesn’t accept versions like `01.02.03`, it has to be `1.2.3`.
Checking with the `0` removed, says valid semver (https://jubianchi.github.io/semver-check/#/8.2.2-462599/8.2.2-462599).
The related commits:
- https://github.com/angular/material2-docs-content/commit/069a66bd81564f6e6f96d6a5737a4c5d99db02bb#diff-b9cfc7f2cdf78a7f4b91a753d10865a2
- https://github.com/angular/components/commit/04625994e04120a42a5608140898868293de2f09
#### What is seen when trying to build material.angular.io
```sh
$ yarn install
yarn install v1.17.3
[1/4] 🔍 Resolving packages...
error Can't add "@angular/material-examples": invalid package version "8.2.2-0462599".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
``` | 1.0 | build(release): generates invalid semver versions and breaks material.angular.io builds - #### Reproduction
Steps to reproduce:
1. Release a new version
#### Expected Behavior
Only valid semver should be used for the versions in https://github.com/angular/material2-docs-content/blob/8.2.x/package.json
#### Actual Behavior
We’re appending partial commit SHAs to the end of the versions, i.e. `8.2.0-c29c507`, `8.2.1-a5d2ed8`, and the latest `8.2.2-0462599`.
However, `8.2.2-0462599` is not valid semver, so yarn won’t install it.
You can check using this validator: https://jubianchi.github.io/semver-check/#/8.2.2-0462599/8.2.2-0462599
The leading `0` is the issue. It doesn’t accept versions like `01.02.03`, it has to be `1.2.3`.
Checking with the `0` removed, says valid semver (https://jubianchi.github.io/semver-check/#/8.2.2-462599/8.2.2-462599).
The related commits:
- https://github.com/angular/material2-docs-content/commit/069a66bd81564f6e6f96d6a5737a4c5d99db02bb#diff-b9cfc7f2cdf78a7f4b91a753d10865a2
- https://github.com/angular/components/commit/04625994e04120a42a5608140898868293de2f09
#### What is seen when trying to build material.angular.io
```sh
$ yarn install
yarn install v1.17.3
[1/4] 🔍 Resolving packages...
error Can't add "@angular/material-examples": invalid package version "8.2.2-0462599".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
``` | infrastructure | build release generates invalid semver versions and breaks material angular io builds reproduction steps to reproduce release a new version expected behavior only valid semver should be used for the versions in actual behavior we’re appending partial commit shas to the end of the versions i e and the latest however is not valid semver so yarn won’t install it you can check using this validator the leading is the issue it doesn’t accept versions like it has to be checking with the removed says valid semver the related commits what is seen when trying to build material angular io sh yarn install yarn install 🔍 resolving packages error can t add angular material examples invalid package version info visit for documentation about this command | 1 |
280,715 | 21,315,131,384 | IssuesEvent | 2022-04-16 06:17:35 | zechajw/pe | https://api.github.com/repos/zechajw/pe | opened | Subheader cut off in the User Guide | type.DocumentationBug severity.VeryLow | Floating 2.3 Subheader in the PDF of the User Guide that might impact the reading flow of the user
<!--session: 1650088579064-6ec12d58-866f-40b4-9c7e-de462eaa301b-->
<!--Version: Web v3.4.2--> | 1.0 | Subheader cut off in the User Guide - Floating 2.3 Subheader in the PDF of the User Guide that might impact the reading flow of the user
<!--session: 1650088579064-6ec12d58-866f-40b4-9c7e-de462eaa301b-->
<!--Version: Web v3.4.2--> | non_infrastructure | subheader cut off in the user guide floating subheader in the pdf of the user guide that might impact the reading flow of the user | 0 |
11,559 | 9,284,545,735 | IssuesEvent | 2019-03-21 02:12:10 | uccser/cs-field-guide | https://api.github.com/repos/uccser/cs-field-guide | opened | Old chapter link syntax in Algorithms chapter | bug infrastructure | On [the dev site](https://cs-field-guide-dev.appspot.com/en/chapters/algorithms/) there is a link in the Algorithms chapter to a different section that still uses syntax from V2 of the site
`"The whole story!"` links to
https://cs-field-guide-dev.appspot.com/en/chapters/algorithms/chapters/algorithms.html#the-whole-story (which is itself broken similarly to #889)
When it should link to
https://cs-field-guide-dev.appspot.com/en/chapters/algorithms/the-whole-story/
| 1.0 | Old chapter link syntax in Algorithms chapter - On [the dev site](https://cs-field-guide-dev.appspot.com/en/chapters/algorithms/) there is a link in the Algorithms chapter to a different section that still uses syntax from V2 of the site
`"The whole story!"` links to
https://cs-field-guide-dev.appspot.com/en/chapters/algorithms/chapters/algorithms.html#the-whole-story (which is itself broken similarly to #889)
When it should link to
https://cs-field-guide-dev.appspot.com/en/chapters/algorithms/the-whole-story/
| infrastructure | old chapter link syntax in algorithms chapter on there is a link in the algorithms chapter to a different section that still uses syntax from of the site the whole story links to which is itself broken similarly to when it should link to | 1 |
9,070 | 7,801,249,038 | IssuesEvent | 2018-06-09 18:47:48 | qutebrowser/qutebrowser | https://api.github.com/repos/qutebrowser/qutebrowser | opened | Automate bumping version for the release | component: infrastructure easy priority: 2 - low | Using e.g. [bumpversion](https://pypi.org/project/bumpversion/) we could automatically increase version numbers and do git commit/tags. It could hopefully also be used to add new versions to qutebrowser.appdata.xml, see #3926. | 1.0 | Automate bumping version for the release - Using e.g. [bumpversion](https://pypi.org/project/bumpversion/) we could automatically increase version numbers and do git commit/tags. It could hopefully also be used to add new versions to qutebrowser.appdata.xml, see #3926. | infrastructure | automate bumping version for the release using e g we could automatically increase version numbers and do git commit tags it could hopefully also be used to add new versions to qutebrowser appdata xml see | 1 |
20,011 | 13,630,107,734 | IssuesEvent | 2020-09-24 15:59:03 | SteeltoeOSS/Steeltoe | https://api.github.com/repos/SteeltoeOSS/Steeltoe | closed | Code Coverage step randomly fails in CI builds | 2.x 3.x Infrastructure bug | [This known issue](https://github.com/coverlet-coverage/coverlet/blob/master/Documentation/KnownIssues.md#1-vstest-stops-process-execution-earlydotnet-test) happens intermittently, but sometimes for most builds, all day [like this](https://dev.azure.com/SteeltoeOSS/Steeltoe/_build/results?buildId=3684&view=logs&j=16ffdd8b-53e5-508b-7e4c-edc4792830b9).
Try switching to the [collectors integration](https://github.com/coverlet-coverage/coverlet/blob/master/Documentation/KnownIssues.md#1-vstest-stops-process-execution-earlydotnet-test).
Also, see if this warning can be resolved if it doesn't disappear with the above change:
```
C:\Users\VssAdministrator\.nuget\packages\coverlet.msbuild\2.9.0\build\coverlet.msbuild.targets(31,5): warning : [coverlet] Unable to instrument module: D:\a\1\s\src\Discovery\test\ClientBase.Test\bin\Release\netcoreapp3.1\Steeltoe.Common.dll because : AssemblyResolutionException for 'Microsoft.Extensions.DependencyInjection.Abstractions, Version=3.1.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. Try to add <PreserveCompilationContext>true</PreserveCompilationContext> to test projects </PropertyGroup> or pass '/p:CopyLocalLockFileAssemblies=true' option to the 'dotnet test' command-line [D:\a\1\s\src\Discovery\test\ClientBase.Test\Steeltoe.Discovery.ClientBase.Test.csproj]
``` | 1.0 | Code Coverage step randomly fails in CI builds - [This known issue](https://github.com/coverlet-coverage/coverlet/blob/master/Documentation/KnownIssues.md#1-vstest-stops-process-execution-earlydotnet-test) happens intermittently, but sometimes for most builds, all day [like this](https://dev.azure.com/SteeltoeOSS/Steeltoe/_build/results?buildId=3684&view=logs&j=16ffdd8b-53e5-508b-7e4c-edc4792830b9).
Try switching to the [collectors integration](https://github.com/coverlet-coverage/coverlet/blob/master/Documentation/KnownIssues.md#1-vstest-stops-process-execution-earlydotnet-test).
Also, see if this warning can be resolved if it doesn't disappear with the above change:
```
C:\Users\VssAdministrator\.nuget\packages\coverlet.msbuild\2.9.0\build\coverlet.msbuild.targets(31,5): warning : [coverlet] Unable to instrument module: D:\a\1\s\src\Discovery\test\ClientBase.Test\bin\Release\netcoreapp3.1\Steeltoe.Common.dll because : AssemblyResolutionException for 'Microsoft.Extensions.DependencyInjection.Abstractions, Version=3.1.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. Try to add <PreserveCompilationContext>true</PreserveCompilationContext> to test projects </PropertyGroup> or pass '/p:CopyLocalLockFileAssemblies=true' option to the 'dotnet test' command-line [D:\a\1\s\src\Discovery\test\ClientBase.Test\Steeltoe.Discovery.ClientBase.Test.csproj]
``` | infrastructure | code coverage step randomly fails in ci builds happens intermittently but sometimes for most builds all day try switching to the also see if this warning can be resolved if it doesn t disappear with the above change c users vssadministrator nuget packages coverlet msbuild build coverlet msbuild targets warning unable to instrument module d a s src discovery test clientbase test bin release steeltoe common dll because assemblyresolutionexception for microsoft extensions dependencyinjection abstractions version culture neutral publickeytoken try to add true to test projects or pass p copylocallockfileassemblies true option to the dotnet test command line | 1 |
23,704 | 7,370,135,622 | IssuesEvent | 2018-03-13 07:05:40 | ShaikASK/Testing | https://api.github.com/repos/ShaikASK/Testing | reopened | Branding : "Drop file here and click to upload" text is not visible under "Logo" and "Background image" section after removing the the uploaded document | Build Version#10 Defect P3 Reopen on Build #11 SumFive Team | Steps :
1.Launch the URL
2.Sign in as HR admin user
3.Go to settings
4.Click on Branding tab
5.Upload the document under logo and background image section
6.Remove the uploaded document from the sections
Experienced Behaviour : Observed that "Drop file here and click to upload" text is not visible under "Logo" and "Background image" sections after removing the the uploaded document (Refer Screen Shot)
Expected Behaviour : Ensue that "Drop file here and click to upload" text should be visible under "Logo" and "Background image" sections after removing the the uploaded document
| 2.0 | Branding : "Drop file here and click to upload" text is not visible under "Logo" and "Background image" section after removing the the uploaded document - Steps :
1.Launch the URL
2.Sign in as HR admin user
3.Go to settings
4.Click on Branding tab
5.Upload the document under logo and background image section
6.Remove the uploaded document from the sections
Experienced Behaviour : Observed that "Drop file here and click to upload" text is not visible under "Logo" and "Background image" sections after removing the the uploaded document (Refer Screen Shot)
Expected Behaviour : Ensue that "Drop file here and click to upload" text should be visible under "Logo" and "Background image" sections after removing the the uploaded document
| non_infrastructure | branding drop file here and click to upload text is not visible under logo and background image section after removing the the uploaded document steps launch the url sign in as hr admin user go to settings click on branding tab upload the document under logo and background image section remove the uploaded document from the sections experienced behaviour observed that drop file here and click to upload text is not visible under logo and background image sections after removing the the uploaded document refer screen shot expected behaviour ensue that drop file here and click to upload text should be visible under logo and background image sections after removing the the uploaded document | 0 |
31,536 | 25,859,284,107 | IssuesEvent | 2022-12-13 15:50:07 | Chaste/Chaste | https://api.github.com/repos/Chaste/Chaste | opened | #3013 - Fix buildbot for coverage | component: infrastructure | This issue continues the discussion for legacy trac ticket 3013:
___
[jmpf](https://github.com/orgs/Chaste/people/jmpf) created the following ticket on 2022-07-27 at 09:35:17, it is owned by [jmpf](https://github.com/orgs/Chaste/people/jmpf)
There are two issues with coverage on buildbot@scoop
An upgrade from 16.04 to 20.04 caused the coverage tests to report some false negatives. These are mostly default: in switch statements: https://chaste.cs.ox.ac.uk/buildbot/Nightly%20Coverage/coverage1734/global/src/FileFinder.cpp.gcov.html
An recent upgrade to the PETSc version has caused the buildbot to stop being able to build (trac ticket 3075).
___
Comment by [jmpf](https://github.com/orgs/Chaste/people/jmpf) on 2022-07-27 at 09:45:26
16.04 had lcov 1.12-2
18.04 has lcov 1.13-3
20.04 has lcov 1.14-2
Comment by [jmpf](https://github.com/orgs/Chaste/people/jmpf) on 2022-07-27 at 10:07:48
During the upgrade and reconfiguration from PETSc 3.6.2 to PETSc 3.12.5 I made a build that is ready to use with lcov: https://chaste.cs.ox.ac.uk/trac/ticket/3075#comment:7 I guess that the old stale CMake files are interfering. Deleted configuration and retesting.
___
Comment by [jmpf](https://github.com/orgs/Chaste/people/jmpf) on 2022-07-27 at 12:54:41
Replying to jmpf@…:
Deleted configuration and retesting.
That worked for nightly coverage and for nightly memory testing too.
Comment by [jmpf](https://github.com/orgs/Chaste/people/jmpf) on 2022-07-28 at 14:31:04
Way to build coverage on Scoop
```
mkdir Debug_develop
export PETSC_ARCH=linux-gnu
export PETSC_DIR=/home/bob/petsc-3.12.5
export LD_LIBRARY_PATH=/home/bob/petsc-3.12.5/linux-gnu/lib
cmake -DCMAKE_BUILD_TYPE=Debug -DChaste_UPDATE_PROVENANCE=OFF -DChaste_COVERAGE_CPUS=11 ..
make -j12 Continuous Parallel
make -j6 coverage
# To repeat parts of post-processing from "make coverage"
usr/bin/lcov --config-file /home/jmpf/eclipse/workspace/Chaste/cmake/Config/lcovrc --directory . --capture --output-file coverage.info
/usr/bin/lcov --config-file /home/jmpf/eclipse/workspace/Chaste/cmake/Config/lcovrc --remove coverage.info "/home/bob/petsc*" "/usr/*" "*/fortests/*" "*/test/*" "*/3rdparty/*" "*/global/src/random/*" "Debug/*" "*/Debug_*/*" "cxxtest/*" --output-file coverage.info.cleaned set "(" _page_title "\"Chaste Coverage Results for commit \"" ")"
/usr/bin/genhtml --title "" --config-file /home/jmpf/eclipse/workspace/Chaste/cmake/Config/lcovrc --no-function-coverage -o coverage coverage.info.cleaned
#DON'T DO: /usr/bin/cmake -E remove coverage.info coverage.info.cleaned
/usr/bin/python3 /home/jmpf/eclipse/workspace/Chaste/cmake/process_coverage_output.py coverage
```
___
Comment by [jmpf](https://github.com/orgs/Chaste/people/jmpf) on 2022-07-28 at 14:34:22
The first issue with failing coverage from files which have been auto-generated. See top 3 lines of https://chaste.cs.ox.ac.uk/buildbot/Nightly%20Coverage/coverage1740/
This is caused by an incorrect wildcard/glob pattern and should be fixed by changing Debug_*/* to */Debug_*/* on line 844 of CMakeLists.txt.
___
Comment by [jmpf](https://github.com/orgs/Chaste/people/jmpf) on 2022-10-26 at 09:15:28
Note that existing work on this ticket is available:
```
git checkout ticket_3103
```
___
Comment by [mirams](https://github.com/orgs/Chaste/people/mirams) on 2022-10-26 at 10:14:08
For those not so familiar with LCOV and how we have it set up see (track ticket 2858) for previous work and how to mark files, lines or blocks as purposely excluded etc. | 1.0 | #3013 - Fix buildbot for coverage - This issue continues the discussion for legacy trac ticket 3013:
___
[jmpf](https://github.com/orgs/Chaste/people/jmpf) created the following ticket on 2022-07-27 at 09:35:17, it is owned by [jmpf](https://github.com/orgs/Chaste/people/jmpf)
There are two issues with coverage on buildbot@scoop
An upgrade from 16.04 to 20.04 caused the coverage tests to report some false negatives. These are mostly default: in switch statements: https://chaste.cs.ox.ac.uk/buildbot/Nightly%20Coverage/coverage1734/global/src/FileFinder.cpp.gcov.html
An recent upgrade to the PETSc version has caused the buildbot to stop being able to build (trac ticket 3075).
___
Comment by [jmpf](https://github.com/orgs/Chaste/people/jmpf) on 2022-07-27 at 09:45:26
16.04 had lcov 1.12-2
18.04 has lcov 1.13-3
20.04 has lcov 1.14-2
Comment by [jmpf](https://github.com/orgs/Chaste/people/jmpf) on 2022-07-27 at 10:07:48
During the upgrade and reconfiguration from PETSc 3.6.2 to PETSc 3.12.5 I made a build that is ready to use with lcov: https://chaste.cs.ox.ac.uk/trac/ticket/3075#comment:7 I guess that the old stale CMake files are interfering. Deleted configuration and retesting.
___
Comment by [jmpf](https://github.com/orgs/Chaste/people/jmpf) on 2022-07-27 at 12:54:41
Replying to jmpf@…:
Deleted configuration and retesting.
That worked for nightly coverage and for nightly memory testing too.
Comment by [jmpf](https://github.com/orgs/Chaste/people/jmpf) on 2022-07-28 at 14:31:04
Way to build coverage on Scoop
```
mkdir Debug_develop
export PETSC_ARCH=linux-gnu
export PETSC_DIR=/home/bob/petsc-3.12.5
export LD_LIBRARY_PATH=/home/bob/petsc-3.12.5/linux-gnu/lib
cmake -DCMAKE_BUILD_TYPE=Debug -DChaste_UPDATE_PROVENANCE=OFF -DChaste_COVERAGE_CPUS=11 ..
make -j12 Continuous Parallel
make -j6 coverage
# To repeat parts of post-processing from "make coverage"
usr/bin/lcov --config-file /home/jmpf/eclipse/workspace/Chaste/cmake/Config/lcovrc --directory . --capture --output-file coverage.info
/usr/bin/lcov --config-file /home/jmpf/eclipse/workspace/Chaste/cmake/Config/lcovrc --remove coverage.info "/home/bob/petsc*" "/usr/*" "*/fortests/*" "*/test/*" "*/3rdparty/*" "*/global/src/random/*" "Debug/*" "*/Debug_*/*" "cxxtest/*" --output-file coverage.info.cleaned set "(" _page_title "\"Chaste Coverage Results for commit \"" ")"
/usr/bin/genhtml --title "" --config-file /home/jmpf/eclipse/workspace/Chaste/cmake/Config/lcovrc --no-function-coverage -o coverage coverage.info.cleaned
#DON'T DO: /usr/bin/cmake -E remove coverage.info coverage.info.cleaned
/usr/bin/python3 /home/jmpf/eclipse/workspace/Chaste/cmake/process_coverage_output.py coverage
```
___
Comment by [jmpf](https://github.com/orgs/Chaste/people/jmpf) on 2022-07-28 at 14:34:22
The first issue with failing coverage from files which have been auto-generated. See top 3 lines of https://chaste.cs.ox.ac.uk/buildbot/Nightly%20Coverage/coverage1740/
This is caused by an incorrect wildcard/glob pattern and should be fixed by changing Debug_*/* to */Debug_*/* on line 844 of CMakeLists.txt.
___
Comment by [jmpf](https://github.com/orgs/Chaste/people/jmpf) on 2022-10-26 at 09:15:28
Note that existing work on this ticket is available:
```
git checkout ticket_3103
```
___
Comment by [mirams](https://github.com/orgs/Chaste/people/mirams) on 2022-10-26 at 10:14:08
For those not so familiar with LCOV and how we have it set up see (track ticket 2858) for previous work and how to mark files, lines or blocks as purposely excluded etc. | infrastructure | fix buildbot for coverage this issue continues the discussion for legacy trac ticket created the following ticket on at it is owned by there are two issues with coverage on buildbot scoop an upgrade from to caused the coverage tests to report some false negatives these are mostly default in switch statements an recent upgrade to the petsc version has caused the buildbot to stop being able to build trac ticket comment by on at had lcov has lcov has lcov comment by on at during the upgrade and reconfiguration from petsc to petsc i made a build that is ready to use with lcov i guess that the old stale cmake files are interfering deleted configuration and retesting comment by on at replying to jmpf … deleted configuration and retesting that worked for nightly coverage and for nightly memory testing too comment by on at way to build coverage on scoop mkdir debug develop export petsc arch linux gnu export petsc dir home bob petsc export ld library path home bob petsc linux gnu lib cmake dcmake build type debug dchaste update provenance off dchaste coverage cpus make continuous parallel make coverage to repeat parts of post processing from make coverage usr bin lcov config file home jmpf eclipse workspace chaste cmake config lcovrc directory capture output file coverage info usr bin lcov config file home jmpf eclipse workspace chaste cmake config lcovrc remove coverage info home bob petsc usr fortests test global src random debug debug cxxtest output file coverage info cleaned set page title chaste coverage results for commit usr bin genhtml title config file home jmpf eclipse workspace chaste cmake config lcovrc no function coverage o coverage coverage info cleaned don t do usr bin cmake e remove coverage info coverage info cleaned usr bin home jmpf eclipse workspace chaste cmake process coverage output py coverage comment by on at the first issue with failing coverage from files which have been auto generated see top lines of this is caused by an incorrect wildcard glob pattern and should be fixed by changing debug to debug on line of cmakelists txt comment by on at note that existing work on this ticket is available git checkout ticket comment by on at for those not so familiar with lcov and how we have it set up see track ticket for previous work and how to mark files lines or blocks as purposely excluded etc | 1 |
5,564 | 5,790,860,234 | IssuesEvent | 2017-05-02 02:40:48 | mymonero/mymonero-app-js | https://api.github.com/repos/mymonero/mymonero-app-js | closed | Implement Android signing | blocking android launch infrastructure / packaging | * https://cordova.apache.org/docs/en/dev/guide/platforms/android/index.html#signing-an-app
* "Android: "When you create a signing configuration, Android Studio adds your signing information in plain text to the module's build.gradle files. If you are working with a team or open-sourcing your code, you should move this sensitive information out of the build files so it is not easily accessible to others."
* https://developer.android.com/studio/publish/app-signing.html#secure-key
* remove the debuggable keyvalue from AndroidManifest.xml?
* http://stackoverflow.com/questions/26449512/how-to-create-a-signed-apk-file-using-cordova-command-line-interface | 1.0 | Implement Android signing - * https://cordova.apache.org/docs/en/dev/guide/platforms/android/index.html#signing-an-app
* "Android: "When you create a signing configuration, Android Studio adds your signing information in plain text to the module's build.gradle files. If you are working with a team or open-sourcing your code, you should move this sensitive information out of the build files so it is not easily accessible to others."
* https://developer.android.com/studio/publish/app-signing.html#secure-key
* remove the debuggable keyvalue from AndroidManifest.xml?
* http://stackoverflow.com/questions/26449512/how-to-create-a-signed-apk-file-using-cordova-command-line-interface | infrastructure | implement android signing android when you create a signing configuration android studio adds your signing information in plain text to the module s build gradle files if you are working with a team or open sourcing your code you should move this sensitive information out of the build files so it is not easily accessible to others remove the debuggable keyvalue from androidmanifest xml | 1 |
29,945 | 8,444,315,766 | IssuesEvent | 2018-10-18 18:04:55 | gimli-org/gimli | https://api.github.com/repos/gimli-org/gimli | closed | Fix install script for Mac OS | building and distribution | We should test the curl installer and give additional instructions on the website for manual compilation on MacOS. Any experiences & help from Mac users is welcome.
| 1.0 | Fix install script for Mac OS - We should test the curl installer and give additional instructions on the website for manual compilation on MacOS. Any experiences & help from Mac users is welcome.
| non_infrastructure | fix install script for mac os we should test the curl installer and give additional instructions on the website for manual compilation on macos any experiences help from mac users is welcome | 0 |
8,337 | 7,345,984,984 | IssuesEvent | 2018-03-07 19:11:38 | DMPRoadmap/roadmap | https://api.github.com/repos/DMPRoadmap/roadmap | closed | Replace gemfile for front-end translations with the underlying Jed library | infrastructure optimization | As part of moving all the assets to Webpack, the gem "gettext_i18n_rails_js" has to be replaced with Jed library directly. A separated issue to deal with this will allow progressing on the ticket #587 | 1.0 | Replace gemfile for front-end translations with the underlying Jed library - As part of moving all the assets to Webpack, the gem "gettext_i18n_rails_js" has to be replaced with Jed library directly. A separated issue to deal with this will allow progressing on the ticket #587 | infrastructure | replace gemfile for front end translations with the underlying jed library as part of moving all the assets to webpack the gem gettext rails js has to be replaced with jed library directly a separated issue to deal with this will allow progressing on the ticket | 1 |
99,414 | 20,961,078,331 | IssuesEvent | 2022-03-27 20:09:58 | yakra/DataProcessing | https://api.github.com/repos/yakra/DataProcessing | opened | HGEdge: delegating constructors | code organization C++ graph generation | HGEdge might be a good candidate for delegating constructors.
Are there any other classes with overloaded ctors? | 1.0 | HGEdge: delegating constructors - HGEdge might be a good candidate for delegating constructors.
Are there any other classes with overloaded ctors? | non_infrastructure | hgedge delegating constructors hgedge might be a good candidate for delegating constructors are there any other classes with overloaded ctors | 0 |
1,574 | 3,789,119,191 | IssuesEvent | 2016-03-21 16:49:00 | ngageoint/hootenanny | https://api.github.com/repos/ngageoint/hootenanny | closed | Move review bookmarks related code out of ReviewResource into its own http endpoint class | Category: Services Priority: Medium Type: Task | As a developer, I need to keep code classes focused on doing one thing well to promote better extensibility and easier debugging.
Steps to complete:
* refactor the code as described
Acceptance criteria:
* The code has been refactored as described. | 1.0 | Move review bookmarks related code out of ReviewResource into its own http endpoint class - As a developer, I need to keep code classes focused on doing one thing well to promote better extensibility and easier debugging.
Steps to complete:
* refactor the code as described
Acceptance criteria:
* The code has been refactored as described. | non_infrastructure | move review bookmarks related code out of reviewresource into its own http endpoint class as a developer i need to keep code classes focused on doing one thing well to promote better extensibility and easier debugging steps to complete refactor the code as described acceptance criteria the code has been refactored as described | 0 |
38,882 | 10,261,137,166 | IssuesEvent | 2019-08-22 09:08:42 | ShaikASK/Testing | https://api.github.com/repos/ShaikASK/Testing | closed | QA /Production : Safari : New Hire : Emails tab /Activities tab : Extra white space is being displayed against email tab and activities tab | Activities Beta Release #5 Build#4 Defect Emails Initiate On boarding New Hire P3 | Steps To Replicate
1.Launch the URL
2.Sign in as HR admin
3.Create a New Hire and Save it
4.Initiate the above created New Hire
5.Complete the onboarding process from candidate side
6.Check the Emails tab and Activities tab for above initiated New Hire
Experienced Behavior : Observed that Extra white space is being displayed against email tab and activities tab (Refer Screen Shot)
Expected Behavior :Ensure that Extra white space should not be displayed against email tab and activities tab
Emails Tab :
Activities Tab :
| 1.0 | QA /Production : Safari : New Hire : Emails tab /Activities tab : Extra white space is being displayed against email tab and activities tab - Steps To Replicate
1.Launch the URL
2.Sign in as HR admin
3.Create a New Hire and Save it
4.Initiate the above created New Hire
5.Complete the onboarding process from candidate side
6.Check the Emails tab and Activities tab for above initiated New Hire
Experienced Behavior : Observed that Extra white space is being displayed against email tab and activities tab (Refer Screen Shot)
Expected Behavior :Ensure that Extra white space should not be displayed against email tab and activities tab
Emails Tab :
Activities Tab :
| non_infrastructure | qa production safari new hire emails tab activities tab extra white space is being displayed against email tab and activities tab steps to replicate launch the url sign in as hr admin create a new hire and save it initiate the above created new hire complete the onboarding process from candidate side check the emails tab and activities tab for above initiated new hire experienced behavior observed that extra white space is being displayed against email tab and activities tab refer screen shot expected behavior ensure that extra white space should not be displayed against email tab and activities tab emails tab activities tab | 0 |
14,258 | 10,729,680,303 | IssuesEvent | 2019-10-28 16:00:36 | zowe/zlux | https://api.github.com/repos/zowe/zlux | opened | Support constructor injectibles via iframe adapter | Client Infrastructure | non-iframe apps are given plugin def & launch context & a logger when they start. iframes do not start synchronously, so you can't do this in the same way, but the iframe should be informed of initialization objects when is ready, via the adapter.
Acceptance criteria:
Iframe can get a handle on its:
Logger
plugin definition object
app2app launch object, if exists | 1.0 | Support constructor injectibles via iframe adapter - non-iframe apps are given plugin def & launch context & a logger when they start. iframes do not start synchronously, so you can't do this in the same way, but the iframe should be informed of initialization objects when is ready, via the adapter.
Acceptance criteria:
Iframe can get a handle on its:
Logger
plugin definition object
app2app launch object, if exists | infrastructure | support constructor injectibles via iframe adapter non iframe apps are given plugin def launch context a logger when they start iframes do not start synchronously so you can t do this in the same way but the iframe should be informed of initialization objects when is ready via the adapter acceptance criteria iframe can get a handle on its logger plugin definition object launch object if exists | 1 |
359,663 | 10,679,267,813 | IssuesEvent | 2019-10-21 18:55:35 | kubernetes/steering | https://api.github.com/repos/kubernetes/steering | closed | Committee decision-making process | help wanted lifecycle/frozen priority/important-longterm | - Committee decision-making process (e.g., modified lazy consensus seeking) and quorum requirement | 1.0 | Committee decision-making process - - Committee decision-making process (e.g., modified lazy consensus seeking) and quorum requirement | non_infrastructure | committee decision making process committee decision making process e g modified lazy consensus seeking and quorum requirement | 0 |
15,302 | 11,454,328,310 | IssuesEvent | 2020-02-06 16:52:45 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | opened | VS hangs when opening Microsoft.VisualBasic.Core.sln | area-Infrastructure-libraries | Possibly related to the new config system? That sln contains a vbproj.
cc @Anipik @ericstj | 1.0 | VS hangs when opening Microsoft.VisualBasic.Core.sln - Possibly related to the new config system? That sln contains a vbproj.
cc @Anipik @ericstj | infrastructure | vs hangs when opening microsoft visualbasic core sln possibly related to the new config system that sln contains a vbproj cc anipik ericstj | 1 |
52,558 | 10,881,345,032 | IssuesEvent | 2019-11-17 17:09:38 | WarEmu/WarBugs | https://api.github.com/repos/WarEmu/WarBugs | closed | Instant Kill after jumping | Known Issue - Review again. Sourcecode | I was just in the Golden Tor PQ in Blighted Isle Dark Elf Chapter 3 region. I was just jumping out of a nest and as soon as I landed outside the nest I was killed instantly. There were no mobs attacking me and no long drop. I was just jumping out of a nest and landing on the ground outside the nest.
| 1.0 | Instant Kill after jumping - I was just in the Golden Tor PQ in Blighted Isle Dark Elf Chapter 3 region. I was just jumping out of a nest and as soon as I landed outside the nest I was killed instantly. There were no mobs attacking me and no long drop. I was just jumping out of a nest and landing on the ground outside the nest.
| non_infrastructure | instant kill after jumping i was just in the golden tor pq in blighted isle dark elf chapter region i was just jumping out of a nest and as soon as i landed outside the nest i was killed instantly there were no mobs attacking me and no long drop i was just jumping out of a nest and landing on the ground outside the nest | 0 |
34,329 | 29,494,063,471 | IssuesEvent | 2023-06-02 15:27:44 | dart-lang/site-www | https://api.github.com/repos/dart-lang/site-www | opened | Out dated Markdown files with broken links | infrastructure | ### Describe the problem
Lots of Markdown files under [src](https://github.com/dart-lang/site-www/tree/main/src) are outdated and links are broken and images are also used there are outdated. lots of files need small reviews and checking if they are working correctly.
ps: I am a beginner issuer so if there is something I don't know please tell me.of
### Expected fix
according to me as far as i know we should check all the markdown files one by one and check all the links on other pages and images. as well as we should check if the images used there are updated or not.
### Additional context
[index.md](https://github.com/dart-lang/site-www/blob/main/src/web/index.md)
this an example of one of the broken markdown files | 1.0 | Out dated Markdown files with broken links - ### Describe the problem
Lots of Markdown files under [src](https://github.com/dart-lang/site-www/tree/main/src) are outdated and links are broken and images are also used there are outdated. lots of files need small reviews and checking if they are working correctly.
ps: I am a beginner issuer so if there is something I don't know please tell me.of
### Expected fix
according to me as far as i know we should check all the markdown files one by one and check all the links on other pages and images. as well as we should check if the images used there are updated or not.
### Additional context
[index.md](https://github.com/dart-lang/site-www/blob/main/src/web/index.md)
this an example of one of the broken markdown files | infrastructure | out dated markdown files with broken links describe the problem lots of markdown files under are outdated and links are broken and images are also used there are outdated lots of files need small reviews and checking if they are working correctly ps i am a beginner issuer so if there is something i don t know please tell me of expected fix according to me as far as i know we should check all the markdown files one by one and check all the links on other pages and images as well as we should check if the images used there are updated or not additional context this an example of one of the broken markdown files | 1 |
252,220 | 8,033,255,985 | IssuesEvent | 2018-07-29 02:48:06 | kubeflow/tf-operator | https://api.github.com/repos/kubeflow/tf-operator | closed | Events don't show up in kubectl describe tfjobs | area/monitoring area/tfjob priority/p2 release/0.3.0 | Below is the output of running kubectl describe for a TFJob that is running.
The job is running successfully (pods exist) but events don't show up in output of `kubectl describe`
The events don't show up with `kubectl get events`; but they do show up in stackdriver. I wonder if the problem is that the events are tool old.
```
kubectl describe tfjobs tfjob
Name: tfjob
Namespace: kubeflow
Labels: app.kubernetes.io/deploy-manager=ksonnet
Annotations: ksonnet.io/managed={"pristine":"H4sIAAAAAAAA/+yRz27UMBDG7zzGnJ3NbkoFjZQTqEIcYEUrekBVNHEmWbOObY3HqcJq3x05UC1/ngCJHKKZbz6P5e93AgzmM3E03kENx9TRYP3TxvNYzju04YAVKDga10MN97fvfQcKJhLsURDqEzicCGqQ4es6ym0MqOmX...
API Version: kubeflow.org/v1alpha2
Kind: TFJob
Metadata:
Cluster Name:
Creation Timestamp: 2018-07-29T00:31:12Z
Generation: 1
Resource Version: 25561
Self Link: /apis/kubeflow.org/v1alpha2/namespaces/kubeflow/tfjobs/tfjob
UID: b20c924b-92c6-11e8-b3ca-42010a80019c
Spec:
Tf Replica Specs:
PS:
Replicas: 1
Template:
Metadata:
Creation Timestamp: <nil>
Spec:
Containers:
Args:
python
tf_cnn_benchmarks.py
--batch_size=32
--model=resnet50
--variable_update=parameter_server
--flush_stdout=true
--num_gpus=1
--local_parameter_device=cpu
--device=cpu
--data_format=NHWC
Image: gcr.io/kubeflow/tf-benchmarks-cpu:v20171202-bdab599-dirty-284af3
Name: tensorflow
Ports:
Container Port: 2222
Name: tfjob-port
Resources:
Working Dir: /opt/tf-benchmarks/scripts/tf_cnn_benchmarks
Restart Policy: OnFailure
Worker:
Replicas: 1
Template:
Metadata:
Creation Timestamp: <nil>
Spec:
Containers:
Args:
python
tf_cnn_benchmarks.py
--batch_size=32
--model=resnet50
--variable_update=parameter_server
--flush_stdout=true
--num_gpus=1
--local_parameter_device=cpu
--device=cpu
--data_format=NHWC
Image: gcr.io/kubeflow/tf-benchmarks-cpu:v20171202-bdab599-dirty-284af3
Name: tensorflow
Ports:
Container Port: 2222
Name: tfjob-port
Resources:
Working Dir: /opt/tf-benchmarks/scripts/tf_cnn_benchmarks
Restart Policy: OnFailure
Status:
Conditions:
Last Transition Time: 2018-07-29T00:31:48Z
Last Update Time: 2018-07-29T00:31:48Z
Message: TFJob tfjob is running.
Reason: TFJobRunning
Status: True
Type: Running
Start Time: 2018-07-29T02:38:43Z
Tf Replica Statuses:
PS:
Active: 1
Worker:
Active: 1
Events: <none>
```` | 1.0 | Events don't show up in kubectl describe tfjobs - Below is the output of running kubectl describe for a TFJob that is running.
The job is running successfully (pods exist) but events don't show up in output of `kubectl describe`
The events don't show up with `kubectl get events`; but they do show up in stackdriver. I wonder if the problem is that the events are tool old.
```
kubectl describe tfjobs tfjob
Name: tfjob
Namespace: kubeflow
Labels: app.kubernetes.io/deploy-manager=ksonnet
Annotations: ksonnet.io/managed={"pristine":"H4sIAAAAAAAA/+yRz27UMBDG7zzGnJ3NbkoFjZQTqEIcYEUrekBVNHEmWbOObY3HqcJq3x05UC1/ngCJHKKZbz6P5e93AgzmM3E03kENx9TRYP3TxvNYzju04YAVKDga10MN97fvfQcKJhLsURDqEzicCGqQ4es6ym0MqOmX...
API Version: kubeflow.org/v1alpha2
Kind: TFJob
Metadata:
Cluster Name:
Creation Timestamp: 2018-07-29T00:31:12Z
Generation: 1
Resource Version: 25561
Self Link: /apis/kubeflow.org/v1alpha2/namespaces/kubeflow/tfjobs/tfjob
UID: b20c924b-92c6-11e8-b3ca-42010a80019c
Spec:
Tf Replica Specs:
PS:
Replicas: 1
Template:
Metadata:
Creation Timestamp: <nil>
Spec:
Containers:
Args:
python
tf_cnn_benchmarks.py
--batch_size=32
--model=resnet50
--variable_update=parameter_server
--flush_stdout=true
--num_gpus=1
--local_parameter_device=cpu
--device=cpu
--data_format=NHWC
Image: gcr.io/kubeflow/tf-benchmarks-cpu:v20171202-bdab599-dirty-284af3
Name: tensorflow
Ports:
Container Port: 2222
Name: tfjob-port
Resources:
Working Dir: /opt/tf-benchmarks/scripts/tf_cnn_benchmarks
Restart Policy: OnFailure
Worker:
Replicas: 1
Template:
Metadata:
Creation Timestamp: <nil>
Spec:
Containers:
Args:
python
tf_cnn_benchmarks.py
--batch_size=32
--model=resnet50
--variable_update=parameter_server
--flush_stdout=true
--num_gpus=1
--local_parameter_device=cpu
--device=cpu
--data_format=NHWC
Image: gcr.io/kubeflow/tf-benchmarks-cpu:v20171202-bdab599-dirty-284af3
Name: tensorflow
Ports:
Container Port: 2222
Name: tfjob-port
Resources:
Working Dir: /opt/tf-benchmarks/scripts/tf_cnn_benchmarks
Restart Policy: OnFailure
Status:
Conditions:
Last Transition Time: 2018-07-29T00:31:48Z
Last Update Time: 2018-07-29T00:31:48Z
Message: TFJob tfjob is running.
Reason: TFJobRunning
Status: True
Type: Running
Start Time: 2018-07-29T02:38:43Z
Tf Replica Statuses:
PS:
Active: 1
Worker:
Active: 1
Events: <none>
```` | non_infrastructure | events don t show up in kubectl describe tfjobs below is the output of running kubectl describe for a tfjob that is running the job is running successfully pods exist but events don t show up in output of kubectl describe the events don t show up with kubectl get events but they do show up in stackdriver i wonder if the problem is that the events are tool old kubectl describe tfjobs tfjob name tfjob namespace kubeflow labels app kubernetes io deploy manager ksonnet annotations ksonnet io managed pristine api version kubeflow org kind tfjob metadata cluster name creation timestamp generation resource version self link apis kubeflow org namespaces kubeflow tfjobs tfjob uid spec tf replica specs ps replicas template metadata creation timestamp spec containers args python tf cnn benchmarks py batch size model variable update parameter server flush stdout true num gpus local parameter device cpu device cpu data format nhwc image gcr io kubeflow tf benchmarks cpu dirty name tensorflow ports container port name tfjob port resources working dir opt tf benchmarks scripts tf cnn benchmarks restart policy onfailure worker replicas template metadata creation timestamp spec containers args python tf cnn benchmarks py batch size model variable update parameter server flush stdout true num gpus local parameter device cpu device cpu data format nhwc image gcr io kubeflow tf benchmarks cpu dirty name tensorflow ports container port name tfjob port resources working dir opt tf benchmarks scripts tf cnn benchmarks restart policy onfailure status conditions last transition time last update time message tfjob tfjob is running reason tfjobrunning status true type running start time tf replica statuses ps active worker active events | 0 |
7,939 | 7,156,895,906 | IssuesEvent | 2018-01-26 17:52:18 | edgi-govdata-archiving/overview | https://api.github.com/repos/edgi-govdata-archiving/overview | reopened | Set up visual script-runner platform | coordination infrastructure | Often when someone wants tasks to run regularly, they set up a script to run via "cron" on a server. This is convenient, but is also very hard to share. Is the script failing? Do people know it's running? What's the log output? What environment variables are set? What servers is it acting on? All of this information is by default hidden away on the system, accessible only to privileged technical persons.
Tools have been built that create a visual interface on top of scripts, so they can be inspected and even triggered by less technical users.
## Useful for
- Run a script to download Zoom calls and upload them to YouTube, then delete them from Zoom.
- Make backups regularly of critical systems, in a way that anyone can confirm.
- ???
- Profit!
## Platform options
All self-hosted.
- Rundeck
- Stackstorm
- Airflow
- Jenkins :new:
- [script-server](https://github.com/bugy/script-server) :new:
Leaning toward rundeck, as it's been around awhile.
## Nice-to-haves
Features that would suit how we hope to use the tool.
| feature | rundeck | stackstorm | airflow |
|--|--|--|--|
| 1. public list of scripts | :question: | :question: | :question: |
| 2. API | :question: | :question: | :question: |
Feature Notes:
1. this wouldn't make private details public, but would let any non-logged-in member (and yes, anyone) see that names of the scripts we're running, and perhaps when they run. This would allow people to see what runs in the background, without seeing privileged variables. | 1.0 | Set up visual script-runner platform - Often when someone wants tasks to run regularly, they set up a script to run via "cron" on a server. This is convenient, but is also very hard to share. Is the script failing? Do people know it's running? What's the log output? What environment variables are set? What servers is it acting on? All of this information is by default hidden away on the system, accessible only to privileged technical persons.
Tools have been built that create a visual interface on top of scripts, so they can be inspected and even triggered by less technical users.
## Useful for
- Run a script to download Zoom calls and upload them to YouTube, then delete them from Zoom.
- Make backups regularly of critical systems, in a way that anyone can confirm.
- ???
- Profit!
## Platform options
All self-hosted.
- Rundeck
- Stackstorm
- Airflow
- Jenkins :new:
- [script-server](https://github.com/bugy/script-server) :new:
Leaning toward rundeck, as it's been around awhile.
## Nice-to-haves
Features that would suit how we hope to use the tool.
| feature | rundeck | stackstorm | airflow |
|--|--|--|--|
| 1. public list of scripts | :question: | :question: | :question: |
| 2. API | :question: | :question: | :question: |
Feature Notes:
1. this wouldn't make private details public, but would let any non-logged-in member (and yes, anyone) see that names of the scripts we're running, and perhaps when they run. This would allow people to see what runs in the background, without seeing privileged variables. | infrastructure | set up visual script runner platform often when someone wants tasks to run regularly they set up a script to run via cron on a server this is convenient but is also very hard to share is the script failing do people know it s running what s the log output what environment variables are set what servers is it acting on all of this information is by default hidden away on the system accessible only to privileged technical persons tools have been built that create a visual interface on top of scripts so they can be inspected and even triggered by less technical users useful for run a script to download zoom calls and upload them to youtube then delete them from zoom make backups regularly of critical systems in a way that anyone can confirm profit platform options all self hosted rundeck stackstorm airflow jenkins new new leaning toward rundeck as it s been around awhile nice to haves features that would suit how we hope to use the tool feature rundeck stackstorm airflow public list of scripts question question question api question question question feature notes this wouldn t make private details public but would let any non logged in member and yes anyone see that names of the scripts we re running and perhaps when they run this would allow people to see what runs in the background without seeing privileged variables | 1 |
212,879 | 7,243,622,780 | IssuesEvent | 2018-02-14 12:27:19 | grmToolbox/grmpy | https://api.github.com/repos/grmToolbox/grmpy | closed | assess pei_edits | bug priority-high size-M | I created a new branch to do some required edits/fixes for my lecture on Thursday. Please review my edits the week after and then decide whether to integrate them into master or not ... | 1.0 | assess pei_edits - I created a new branch to do some required edits/fixes for my lecture on Thursday. Please review my edits the week after and then decide whether to integrate them into master or not ... | non_infrastructure | assess pei edits i created a new branch to do some required edits fixes for my lecture on thursday please review my edits the week after and then decide whether to integrate them into master or not | 0 |
3,481 | 4,343,599,453 | IssuesEvent | 2016-07-29 02:56:35 | ProjectCopilot/mailroom | https://api.github.com/repos/ProjectCopilot/mailroom | closed | Firebase Key is expected in CWD and not the basedir | bug infrastructure | This makes deployment difficult and needs to be fixed. | 1.0 | Firebase Key is expected in CWD and not the basedir - This makes deployment difficult and needs to be fixed. | infrastructure | firebase key is expected in cwd and not the basedir this makes deployment difficult and needs to be fixed | 1 |
23,711 | 16,540,075,657 | IssuesEvent | 2021-05-27 15:45:37 | YAPP-18th/Android-Team-1-Backend | https://api.github.com/repos/YAPP-18th/Android-Team-1-Backend | closed | [기능] 오늘의 질문 변경하는 배치 어플리케이션 작성 | application feature infrastructure | ## 기능
사용자 설정마다 하루가 끝나는 시간이 모두 다르며, 그 시간이 지났다면 오늘의 질문을 갱신시켜 줘야 하는 비즈니스 로직이 있다. 이 부분은 배치 어플리케이션을 새로 작성해서 관리하는 것으로 한다.
## 할 일
## 마감기한
| 1.0 | [기능] 오늘의 질문 변경하는 배치 어플리케이션 작성 - ## 기능
사용자 설정마다 하루가 끝나는 시간이 모두 다르며, 그 시간이 지났다면 오늘의 질문을 갱신시켜 줘야 하는 비즈니스 로직이 있다. 이 부분은 배치 어플리케이션을 새로 작성해서 관리하는 것으로 한다.
## 할 일
## 마감기한
| infrastructure | 오늘의 질문 변경하는 배치 어플리케이션 작성 기능 사용자 설정마다 하루가 끝나는 시간이 모두 다르며 그 시간이 지났다면 오늘의 질문을 갱신시켜 줘야 하는 비즈니스 로직이 있다 이 부분은 배치 어플리케이션을 새로 작성해서 관리하는 것으로 한다 할 일 마감기한 | 1 |
3,896 | 4,700,881,493 | IssuesEvent | 2016-10-12 19:53:08 | google/WebFundamentals | https://api.github.com/repos/google/WebFundamentals | closed | Add support for Hindi content | P2 type-Infrastructure | Work that needs to be done:
* [x] Update local templates to include Hindi in language pickers
* [x] Verify files are served properly from local staging env
* [x] Update gulp tasks that handle any language specific stuff
* [x] Update deployment tasks | 1.0 | Add support for Hindi content - Work that needs to be done:
* [x] Update local templates to include Hindi in language pickers
* [x] Verify files are served properly from local staging env
* [x] Update gulp tasks that handle any language specific stuff
* [x] Update deployment tasks | infrastructure | add support for hindi content work that needs to be done update local templates to include hindi in language pickers verify files are served properly from local staging env update gulp tasks that handle any language specific stuff update deployment tasks | 1 |
117,959 | 11,959,402,919 | IssuesEvent | 2020-04-04 21:50:12 | Michielu/true-badge-ui | https://api.github.com/repos/Michielu/true-badge-ui | closed | Research on deploy | documentation small | Initial brain dump:
- [x] Check enviroment to determine where to run
- [x] Research building pipelines
Blocked by hosting server | 1.0 | Research on deploy - Initial brain dump:
- [x] Check enviroment to determine where to run
- [x] Research building pipelines
Blocked by hosting server | non_infrastructure | research on deploy initial brain dump check enviroment to determine where to run research building pipelines blocked by hosting server | 0 |
545,637 | 15,954,321,592 | IssuesEvent | 2021-04-15 13:28:00 | blchelle/board-games | https://api.github.com/repos/blchelle/board-games | closed | Crashes in the `Stats`, `Login`, `Connect-4`, `TOOT-and-OTTO` pages | Length: Less than 5 hours Priority: Critical Status: Complete Type: Bug | ## Description
Both the `/login` & `/stats` routes crash when navigating to them in the browser.
Both the `/connect-4` & `/toot-and-otto` routes crash when the user completes a game.
The corresponding errors are:
* **Login:** panicked at 'called `Option::unwrap()` on a `None` value', src/components/login.rs:118:59
* **Stats:** panicked at 'called `Option::unwrap()` on a `None` value', src/components/stats.rs:60:59
* **TOOT-and-OTTO:** panicked at 'called `Option::unwrap()` on a `None` value', src/components/toot_and_otto_board.rs:37:63
* **Connect 4:** panicked at 'called `Option::unwrap()` on a `None` value', src/components/connect4_board.rs:38:63
My initial guess is that these errors come from trying to fetch a value out of local storage using a key that doesn't exist. Try clearing your cache/local storage if you're unable to reproduce these errors. The local storage key that doesn't exist for both pages is `user_logged_in`. Perhaps this only get's set when the user logs in for the first time? | 1.0 | Crashes in the `Stats`, `Login`, `Connect-4`, `TOOT-and-OTTO` pages - ## Description
Both the `/login` & `/stats` routes crash when navigating to them in the browser.
Both the `/connect-4` & `/toot-and-otto` routes crash when the user completes a game.
The corresponding errors are:
* **Login:** panicked at 'called `Option::unwrap()` on a `None` value', src/components/login.rs:118:59
* **Stats:** panicked at 'called `Option::unwrap()` on a `None` value', src/components/stats.rs:60:59
* **TOOT-and-OTTO:** panicked at 'called `Option::unwrap()` on a `None` value', src/components/toot_and_otto_board.rs:37:63
* **Connect 4:** panicked at 'called `Option::unwrap()` on a `None` value', src/components/connect4_board.rs:38:63
My initial guess is that these errors come from trying to fetch a value out of local storage using a key that doesn't exist. Try clearing your cache/local storage if you're unable to reproduce these errors. The local storage key that doesn't exist for both pages is `user_logged_in`. Perhaps this only get's set when the user logs in for the first time? | non_infrastructure | crashes in the stats login connect toot and otto pages description both the login stats routes crash when navigating to them in the browser both the connect toot and otto routes crash when the user completes a game the corresponding errors are login panicked at called option unwrap on a none value src components login rs stats panicked at called option unwrap on a none value src components stats rs toot and otto panicked at called option unwrap on a none value src components toot and otto board rs connect panicked at called option unwrap on a none value src components board rs my initial guess is that these errors come from trying to fetch a value out of local storage using a key that doesn t exist try clearing your cache local storage if you re unable to reproduce these errors the local storage key that doesn t exist for both pages is user logged in perhaps this only get s set when the user logs in for the first time | 0 |
8,653 | 7,545,328,577 | IssuesEvent | 2018-04-17 21:15:31 | cmu-mars/issues | https://api.github.com/repos/cmu-mars/issues | closed | tool for autogen gazebo plugin | CP1 infrastructure | do we need a tool that takes whatever xml representation of the function we're learning for the battery model and produces a version of https://github.com/cmu-mars/brass-energy-monitor for that mathematical function? | 1.0 | tool for autogen gazebo plugin - do we need a tool that takes whatever xml representation of the function we're learning for the battery model and produces a version of https://github.com/cmu-mars/brass-energy-monitor for that mathematical function? | infrastructure | tool for autogen gazebo plugin do we need a tool that takes whatever xml representation of the function we re learning for the battery model and produces a version of for that mathematical function | 1 |
13,473 | 10,271,844,287 | IssuesEvent | 2019-08-23 15:00:35 | HumanCellAtlas/secondary-analysis | https://api.github.com/repos/HumanCellAtlas/secondary-analysis | opened | Fix "unknown" analysis file types | infrastructure | When submitting analysis file metadata, we refer to a mapping of file extensions to file types and any file extension not in the map is marked as "unknown". Update the mapping to include any missing file extensions.
https://github.com/HumanCellAtlas/pipeline-tools/blob/master/adapter_pipelines/format_map_example.json
┆Issue is synchronized with this [Jira Story](https://broadinstitute.atlassian.net/browse/GH-483)
| 1.0 | Fix "unknown" analysis file types - When submitting analysis file metadata, we refer to a mapping of file extensions to file types and any file extension not in the map is marked as "unknown". Update the mapping to include any missing file extensions.
https://github.com/HumanCellAtlas/pipeline-tools/blob/master/adapter_pipelines/format_map_example.json
┆Issue is synchronized with this [Jira Story](https://broadinstitute.atlassian.net/browse/GH-483)
| infrastructure | fix unknown analysis file types when submitting analysis file metadata we refer to a mapping of file extensions to file types and any file extension not in the map is marked as unknown update the mapping to include any missing file extensions ┆issue is synchronized with this | 1 |
33,741 | 27,766,158,252 | IssuesEvent | 2023-03-16 11:36:30 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | Live apphost not being used by crossgen2 with source build | area-Infrastructure-coreclr | ### Description
.NET 7 in source-build does not currently use NativeAOT. Thus, when building Crossgen2 from source on platforms without apphost in nuget feeds, build of runtime fails with:
```
/var/build/dotnet7/testing/dotnet7-stage0/src/bootstrap/sdk/7.0.100/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(135,5): error NETSDK1084: There is no application host available for the specified RuntimeIdentifier 'linux-musl-x86'. [/var/build/dotnet7/testing/dotnet7-stage0/src/dotnet-e6dd91c290b808f971a1ac69c2fb29395bbf1051/src/runtime/src/coreclr/tools/aot/crossgen2/crossgen2.csproj]
```
### Reproduction Steps
Crossbuild from `x64` to `x86`, crossgen2 build will fail.
### Expected behavior
Crossgen2 should be able to use to live apphost built previously by runtime
### Actual behavior
Build fails due to no apphost for that RID
### Regression?
Per https://github.com/dotnet/runtime/issues/7335 and https://github.com/dotnet/runtime/issues/66866, there was a time when this was a non-issue. With move to NativeAOT, `UseLiveBuiltDotNetHost` was dropped, and this use-case seems to have been removed.
### Known Workarounds
None for now. I attempted to build runtime in two steps, to no avail:
```
ROOTFS_DIR="$CBUILDROOT" ./build.sh $args -subset Clr.Native+Host.Native
ROOTFS_DIR="$CBUILDROOT" ./build.sh $args /p:AppHostSourcePath="$builddir"/src/runtime/artifacts/obj/linux-musl-$_dotnet_target.Release/apphost/standalone/apphost
```
### Configuration
.NET 7.0.100-rtm.22519.39
Alpine Linux Edge
x64 to x86 crossbuild
### Other information
_No response_ | 1.0 | Live apphost not being used by crossgen2 with source build - ### Description
.NET 7 in source-build does not currently use NativeAOT. Thus, when building Crossgen2 from source on platforms without apphost in nuget feeds, build of runtime fails with:
```
/var/build/dotnet7/testing/dotnet7-stage0/src/bootstrap/sdk/7.0.100/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(135,5): error NETSDK1084: There is no application host available for the specified RuntimeIdentifier 'linux-musl-x86'. [/var/build/dotnet7/testing/dotnet7-stage0/src/dotnet-e6dd91c290b808f971a1ac69c2fb29395bbf1051/src/runtime/src/coreclr/tools/aot/crossgen2/crossgen2.csproj]
```
### Reproduction Steps
Crossbuild from `x64` to `x86`, crossgen2 build will fail.
### Expected behavior
Crossgen2 should be able to use to live apphost built previously by runtime
### Actual behavior
Build fails due to no apphost for that RID
### Regression?
Per https://github.com/dotnet/runtime/issues/7335 and https://github.com/dotnet/runtime/issues/66866, there was a time when this was a non-issue. With move to NativeAOT, `UseLiveBuiltDotNetHost` was dropped, and this use-case seems to have been removed.
### Known Workarounds
None for now. I attempted to build runtime in two steps, to no avail:
```
ROOTFS_DIR="$CBUILDROOT" ./build.sh $args -subset Clr.Native+Host.Native
ROOTFS_DIR="$CBUILDROOT" ./build.sh $args /p:AppHostSourcePath="$builddir"/src/runtime/artifacts/obj/linux-musl-$_dotnet_target.Release/apphost/standalone/apphost
```
### Configuration
.NET 7.0.100-rtm.22519.39
Alpine Linux Edge
x64 to x86 crossbuild
### Other information
_No response_ | infrastructure | live apphost not being used by with source build description net in source build does not currently use nativeaot thus when building from source on platforms without apphost in nuget feeds build of runtime fails with var build testing src bootstrap sdk sdks microsoft net sdk targets microsoft net sdk frameworkreferenceresolution targets error there is no application host available for the specified runtimeidentifier linux musl reproduction steps crossbuild from to build will fail expected behavior should be able to use to live apphost built previously by runtime actual behavior build fails due to no apphost for that rid regression per and there was a time when this was a non issue with move to nativeaot uselivebuiltdotnethost was dropped and this use case seems to have been removed known workarounds none for now i attempted to build runtime in two steps to no avail rootfs dir cbuildroot build sh args subset clr native host native rootfs dir cbuildroot build sh args p apphostsourcepath builddir src runtime artifacts obj linux musl dotnet target release apphost standalone apphost configuration net rtm alpine linux edge to crossbuild other information no response | 1 |
28,428 | 23,246,125,773 | IssuesEvent | 2022-08-03 20:21:51 | surge-synthesizer/surge | https://api.github.com/repos/surge-synthesizer/surge | closed | Make all those tiny url files in the pipeline | Infrastructure Bug Report Resolved | Which, as we found on 1.0 install day, I had not done! | 1.0 | Make all those tiny url files in the pipeline - Which, as we found on 1.0 install day, I had not done! | infrastructure | make all those tiny url files in the pipeline which as we found on install day i had not done | 1 |
167,687 | 26,534,412,843 | IssuesEvent | 2023-01-19 14:43:32 | kubermatic/dashboard | https://api.github.com/repos/kubermatic/dashboard | closed | KubeOne Import | priority/high Epic kind/design sig/ui | Kubeone Import includes:
- [x] import: view the cluster
- [x] upgrade: upgrading the cluster version
- [x] migrate container runtime
[KubeOne Create Draft](https://www.figma.com/file/dJQKgUPzIDND36o2Nq8dct/Loodse-UI?node-id=6516%3A54056) | 1.0 | KubeOne Import - Kubeone Import includes:
- [x] import: view the cluster
- [x] upgrade: upgrading the cluster version
- [x] migrate container runtime
[KubeOne Create Draft](https://www.figma.com/file/dJQKgUPzIDND36o2Nq8dct/Loodse-UI?node-id=6516%3A54056) | non_infrastructure | kubeone import kubeone import includes import view the cluster upgrade upgrading the cluster version migrate container runtime | 0 |
176,849 | 6,565,759,885 | IssuesEvent | 2017-09-08 09:38:23 | threefoldfoundation/app_backend | https://api.github.com/repos/threefoldfoundation/app_backend | closed | Review invite email that contains referral code | priority_minor state_verification type_bug | Current version of invite email:
Hi,
I'd like to invite you the ThreeFold community. You can download the Android or iOS app at https://rogerth.at/install?a=em-be-threefold-token
To become a registered user in the app, you can use my invitation code dda45e.
Welcome on board!
Bart Pede
Issue:
It has a typo on the first line: Let's make it "I'd like to invite you to join the ThreeFold community." | 1.0 | Review invite email that contains referral code - Current version of invite email:
Hi,
I'd like to invite you the ThreeFold community. You can download the Android or iOS app at https://rogerth.at/install?a=em-be-threefold-token
To become a registered user in the app, you can use my invitation code dda45e.
Welcome on board!
Bart Pede
Issue:
It has a typo on the first line: Let's make it "I'd like to invite you to join the ThreeFold community." | non_infrastructure | review invite email that contains referral code current version of invite email hi i d like to invite you the threefold community you can download the android or ios app at to become a registered user in the app you can use my invitation code welcome on board bart pede issue it has a typo on the first line let s make it i d like to invite you to join the threefold community | 0 |
263,514 | 28,037,684,928 | IssuesEvent | 2023-03-28 16:07:16 | Mend-developer-platform-load/7938212_8_rerun | https://api.github.com/repos/Mend-developer-platform-load/7938212_8_rerun | opened | express-4.13.4.tgz: 3 vulnerabilities (highest severity is: 7.5) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>express-4.13.4.tgz</b></p></summary>
<p></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/mime/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/7938212_8_rerun/commit/31892cdf7eeff7f5f66c472afba02dfa3d31779d">31892cdf7eeff7f5f66c472afba02dfa3d31779d</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (express version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2016-10539](https://www.mend.io/vulnerability-database/CVE-2016-10539) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | negotiator-0.5.3.tgz | Transitive | N/A* | ❌ |
| [CVE-2017-16138](https://www.mend.io/vulnerability-database/CVE-2017-16138) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | mime-1.3.4.tgz | Transitive | N/A* | ❌ |
| [CVE-2017-16119](https://www.mend.io/vulnerability-database/CVE-2017-16119) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | fresh-0.3.0.tgz | Transitive | N/A* | ❌ |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-10539</summary>
### Vulnerable Library - <b>negotiator-0.5.3.tgz</b></p>
<p>HTTP content negotiation</p>
<p>Library home page: <a href="https://registry.npmjs.org/negotiator/-/negotiator-0.5.3.tgz">https://registry.npmjs.org/negotiator/-/negotiator-0.5.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/negotiator/package.json</p>
<p>
Dependency Hierarchy:
- express-4.13.4.tgz (Root Library)
- accepts-1.2.13.tgz
- :x: **negotiator-0.5.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/7938212_8_rerun/commit/31892cdf7eeff7f5f66c472afba02dfa3d31779d">31892cdf7eeff7f5f66c472afba02dfa3d31779d</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
negotiator is an HTTP content negotiator for Node.js and is used by many modules and frameworks including Express and Koa. The header for "Accept-Language", when parsed by negotiator 0.6.0 and earlier is vulnerable to Regular Expression Denial of Service via a specially crafted string.
<p>Publish Date: 2018-05-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-10539>CVE-2016-10539</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/106">https://www.npmjs.com/advisories/106</a></p>
<p>Release Date: 2018-05-31</p>
<p>Fix Resolution: 0.6.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-16138</summary>
### Vulnerable Library - <b>mime-1.3.4.tgz</b></p>
<p>A comprehensive library for mime-type mapping</p>
<p>Library home page: <a href="https://registry.npmjs.org/mime/-/mime-1.3.4.tgz">https://registry.npmjs.org/mime/-/mime-1.3.4.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/mime/package.json</p>
<p>
Dependency Hierarchy:
- express-4.13.4.tgz (Root Library)
- send-0.13.1.tgz
- :x: **mime-1.3.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/7938212_8_rerun/commit/31892cdf7eeff7f5f66c472afba02dfa3d31779d">31892cdf7eeff7f5f66c472afba02dfa3d31779d</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The mime module < 1.4.1, 2.0.1, 2.0.2 is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-16138>CVE-2017-16138</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 1.4.1,2.0.3</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-16119</summary>
### Vulnerable Library - <b>fresh-0.3.0.tgz</b></p>
<p>HTTP response freshness testing</p>
<p>Library home page: <a href="https://registry.npmjs.org/fresh/-/fresh-0.3.0.tgz">https://registry.npmjs.org/fresh/-/fresh-0.3.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/fresh/package.json</p>
<p>
Dependency Hierarchy:
- express-4.13.4.tgz (Root Library)
- :x: **fresh-0.3.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/7938212_8_rerun/commit/31892cdf7eeff7f5f66c472afba02dfa3d31779d">31892cdf7eeff7f5f66c472afba02dfa3d31779d</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Fresh is a module used by the Express.js framework for HTTP response freshness testing. It is vulnerable to a regular expression denial of service when it is passed specially crafted input to parse. This causes the event loop to be blocked causing a denial of service condition.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-16119>CVE-2017-16119</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/526">https://www.npmjs.com/advisories/526</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: fresh - 0.5.2</p>
</p>
<p></p>
</details> | True | express-4.13.4.tgz: 3 vulnerabilities (highest severity is: 7.5) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>express-4.13.4.tgz</b></p></summary>
<p></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/mime/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/7938212_8_rerun/commit/31892cdf7eeff7f5f66c472afba02dfa3d31779d">31892cdf7eeff7f5f66c472afba02dfa3d31779d</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (express version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2016-10539](https://www.mend.io/vulnerability-database/CVE-2016-10539) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | negotiator-0.5.3.tgz | Transitive | N/A* | ❌ |
| [CVE-2017-16138](https://www.mend.io/vulnerability-database/CVE-2017-16138) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | mime-1.3.4.tgz | Transitive | N/A* | ❌ |
| [CVE-2017-16119](https://www.mend.io/vulnerability-database/CVE-2017-16119) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | fresh-0.3.0.tgz | Transitive | N/A* | ❌ |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-10539</summary>
### Vulnerable Library - <b>negotiator-0.5.3.tgz</b></p>
<p>HTTP content negotiation</p>
<p>Library home page: <a href="https://registry.npmjs.org/negotiator/-/negotiator-0.5.3.tgz">https://registry.npmjs.org/negotiator/-/negotiator-0.5.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/negotiator/package.json</p>
<p>
Dependency Hierarchy:
- express-4.13.4.tgz (Root Library)
- accepts-1.2.13.tgz
- :x: **negotiator-0.5.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/7938212_8_rerun/commit/31892cdf7eeff7f5f66c472afba02dfa3d31779d">31892cdf7eeff7f5f66c472afba02dfa3d31779d</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
negotiator is an HTTP content negotiator for Node.js and is used by many modules and frameworks including Express and Koa. The header for "Accept-Language", when parsed by negotiator 0.6.0 and earlier is vulnerable to Regular Expression Denial of Service via a specially crafted string.
<p>Publish Date: 2018-05-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-10539>CVE-2016-10539</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/106">https://www.npmjs.com/advisories/106</a></p>
<p>Release Date: 2018-05-31</p>
<p>Fix Resolution: 0.6.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-16138</summary>
### Vulnerable Library - <b>mime-1.3.4.tgz</b></p>
<p>A comprehensive library for mime-type mapping</p>
<p>Library home page: <a href="https://registry.npmjs.org/mime/-/mime-1.3.4.tgz">https://registry.npmjs.org/mime/-/mime-1.3.4.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/mime/package.json</p>
<p>
Dependency Hierarchy:
- express-4.13.4.tgz (Root Library)
- send-0.13.1.tgz
- :x: **mime-1.3.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/7938212_8_rerun/commit/31892cdf7eeff7f5f66c472afba02dfa3d31779d">31892cdf7eeff7f5f66c472afba02dfa3d31779d</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The mime module < 1.4.1, 2.0.1, 2.0.2 is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-16138>CVE-2017-16138</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 1.4.1,2.0.3</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-16119</summary>
### Vulnerable Library - <b>fresh-0.3.0.tgz</b></p>
<p>HTTP response freshness testing</p>
<p>Library home page: <a href="https://registry.npmjs.org/fresh/-/fresh-0.3.0.tgz">https://registry.npmjs.org/fresh/-/fresh-0.3.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/fresh/package.json</p>
<p>
Dependency Hierarchy:
- express-4.13.4.tgz (Root Library)
- :x: **fresh-0.3.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/7938212_8_rerun/commit/31892cdf7eeff7f5f66c472afba02dfa3d31779d">31892cdf7eeff7f5f66c472afba02dfa3d31779d</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Fresh is a module used by the Express.js framework for HTTP response freshness testing. It is vulnerable to a regular expression denial of service when it is passed specially crafted input to parse. This causes the event loop to be blocked causing a denial of service condition.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-16119>CVE-2017-16119</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/526">https://www.npmjs.com/advisories/526</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: fresh - 0.5.2</p>
</p>
<p></p>
</details> | non_infrastructure | express tgz vulnerabilities highest severity is vulnerable library express tgz path to dependency file package json path to vulnerable library node modules mime package json found in head commit a href vulnerabilities cve severity cvss dependency type fixed in express version remediation available high negotiator tgz transitive n a high mime tgz transitive n a high fresh tgz transitive n a for some transitive vulnerabilities there is no version of direct dependency with a fix check the details section below to see if there is a version of transitive dependency where vulnerability is fixed details cve vulnerable library negotiator tgz http content negotiation library home page a href path to dependency file package json path to vulnerable library node modules negotiator package json dependency hierarchy express tgz root library accepts tgz x negotiator tgz vulnerable library found in head commit a href found in base branch main vulnerability details negotiator is an http content negotiator for node js and is used by many modules and frameworks including express and koa the header for accept language when parsed by negotiator and earlier is vulnerable to regular expression denial of service via a specially crafted string publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution cve vulnerable library mime tgz a comprehensive library for mime type mapping library home page a href path to dependency file package json path to vulnerable library node modules mime package json dependency hierarchy express tgz root library send tgz x mime tgz vulnerable library found in head commit a href found in base branch main vulnerability details the mime module is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input 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 cve vulnerable library fresh tgz http response freshness testing library home page a href path to dependency file package json path to vulnerable library node modules fresh package json dependency hierarchy express tgz root library x fresh tgz vulnerable library found in head commit a href found in base branch main vulnerability details fresh is a module used by the express js framework for http response freshness testing it is vulnerable to a regular expression denial of service when it is passed specially crafted input to parse this causes the event loop to be blocked causing a denial of service condition 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 fresh | 0 |
22,561 | 11,746,533,728 | IssuesEvent | 2020-03-12 11:56:20 | sourcegraph/sourcegraph | https://api.github.com/repos/sourcegraph/sourcegraph | closed | campaigns: Allow filtering/sorting of campaigns and changesets in campaigns | campaigns estimate/3d planned/3.14 team/core-services team/web | This is a feature request from a customer:
- [ ] **Sort `changesets`** on a campaign page:
- [ ] status: open/closed/merged
- [ ] CI status
- [ ] review status
- ?
- [x] **Filter `changesets`** on a campaign page:
- [x] status: open/closed/merged
- [x] CI status
- [x] review status
- ?
- [ ] **Filter `Campaigns`** on the campaigns overview by:
- [x] status: open/closed
- ?
- [ ] **Sort `Campaigns`** on the campaigns overview by:
- [ ] status: open/closed
- [ ] creation date
- [ ] last updated
For all of these we probably need:
- [ ] GraphQL schema
- [ ] pagination of changesets
- [ ] pagination of campaigns
Regarding the backend implementation: we need to think about whether this means
the end of our "denormalization" (we currently keep everything in
`changesets.metadata`) and whether we need to normalize the data we want to
filter by to separate columns. | 1.0 | campaigns: Allow filtering/sorting of campaigns and changesets in campaigns - This is a feature request from a customer:
- [ ] **Sort `changesets`** on a campaign page:
- [ ] status: open/closed/merged
- [ ] CI status
- [ ] review status
- ?
- [x] **Filter `changesets`** on a campaign page:
- [x] status: open/closed/merged
- [x] CI status
- [x] review status
- ?
- [ ] **Filter `Campaigns`** on the campaigns overview by:
- [x] status: open/closed
- ?
- [ ] **Sort `Campaigns`** on the campaigns overview by:
- [ ] status: open/closed
- [ ] creation date
- [ ] last updated
For all of these we probably need:
- [ ] GraphQL schema
- [ ] pagination of changesets
- [ ] pagination of campaigns
Regarding the backend implementation: we need to think about whether this means
the end of our "denormalization" (we currently keep everything in
`changesets.metadata`) and whether we need to normalize the data we want to
filter by to separate columns. | non_infrastructure | campaigns allow filtering sorting of campaigns and changesets in campaigns this is a feature request from a customer sort changesets on a campaign page status open closed merged ci status review status filter changesets on a campaign page status open closed merged ci status review status filter campaigns on the campaigns overview by status open closed sort campaigns on the campaigns overview by status open closed creation date last updated for all of these we probably need graphql schema pagination of changesets pagination of campaigns regarding the backend implementation we need to think about whether this means the end of our denormalization we currently keep everything in changesets metadata and whether we need to normalize the data we want to filter by to separate columns | 0 |
271,770 | 29,659,386,492 | IssuesEvent | 2023-06-10 01:25:02 | pazhanivel07/linux-4.19.72 | https://api.github.com/repos/pazhanivel07/linux-4.19.72 | closed | CVE-2019-19080 (Medium) detected in linuxlinux-4.19.83 - autoclosed | Mend: dependency security vulnerability | ## CVE-2019-19080 - Medium 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/pazhanivel07/linux-4.19.72/commit/ce28e4f7a922d93d9b737061ae46827305c8c30a">ce28e4f7a922d93d9b737061ae46827305c8c30a</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/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
Four memory leaks in the nfp_flower_spawn_phy_reprs() function in drivers/net/ethernet/netronome/nfp/flower/main.c in the Linux kernel before 5.3.4 allow attackers to cause a denial of service (memory consumption), aka CID-8572cea1461a.
<p>Publish Date: 2019-11-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-19080>CVE-2019-19080</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.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19080">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19080</a></p>
<p>Release Date: 2020-08-24</p>
<p>Fix Resolution: v5.4-rc1</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-2019-19080 (Medium) detected in linuxlinux-4.19.83 - autoclosed - ## CVE-2019-19080 - Medium 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/pazhanivel07/linux-4.19.72/commit/ce28e4f7a922d93d9b737061ae46827305c8c30a">ce28e4f7a922d93d9b737061ae46827305c8c30a</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/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
Four memory leaks in the nfp_flower_spawn_phy_reprs() function in drivers/net/ethernet/netronome/nfp/flower/main.c in the Linux kernel before 5.3.4 allow attackers to cause a denial of service (memory consumption), aka CID-8572cea1461a.
<p>Publish Date: 2019-11-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-19080>CVE-2019-19080</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.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19080">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19080</a></p>
<p>Release Date: 2020-08-24</p>
<p>Fix Resolution: v5.4-rc1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_infrastructure | cve medium detected in linuxlinux autoclosed cve medium 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 vulnerability details four memory leaks in the nfp flower spawn phy reprs function in drivers net ethernet netronome nfp flower main c in the linux kernel before allow attackers to cause a denial of service memory consumption aka cid publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact 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 |
22,910 | 15,624,249,227 | IssuesEvent | 2021-03-21 01:18:01 | sunpy/sunpy | https://api.github.com/repos/sunpy/sunpy | closed | Figure tests are affected by failures of other figure tests | Bug(?) Effort Medium Infrastructure Package Expert Priority Medium Tests Upstream Fix Required | This is almost certainly an upstream bug in `pytest-mpl`, but I'm logging it here until that's confirmed.
When a figure test has created a figure but does not complete due to raising an error, the next figure test run in the same run may use the partially created figure for the hash, and thus fail. Since the false failure depends on the first figure test raising an error, this is only a critical issue if the first figure test has been marked with `xfail`. However, it can still be annoying when developing since figure tests that shouldn't be failing can fail. | 1.0 | Figure tests are affected by failures of other figure tests - This is almost certainly an upstream bug in `pytest-mpl`, but I'm logging it here until that's confirmed.
When a figure test has created a figure but does not complete due to raising an error, the next figure test run in the same run may use the partially created figure for the hash, and thus fail. Since the false failure depends on the first figure test raising an error, this is only a critical issue if the first figure test has been marked with `xfail`. However, it can still be annoying when developing since figure tests that shouldn't be failing can fail. | infrastructure | figure tests are affected by failures of other figure tests this is almost certainly an upstream bug in pytest mpl but i m logging it here until that s confirmed when a figure test has created a figure but does not complete due to raising an error the next figure test run in the same run may use the partially created figure for the hash and thus fail since the false failure depends on the first figure test raising an error this is only a critical issue if the first figure test has been marked with xfail however it can still be annoying when developing since figure tests that shouldn t be failing can fail | 1 |
15,032 | 11,303,341,046 | IssuesEvent | 2020-01-17 19:52:13 | weecology/MATSS | https://api.github.com/repos/weecology/MATSS | opened | Retrieve external data | dataset enhancement infrastructure | Since many analyses are likely to want covariates - we can build in some default functions that help with this.
* from taxonomic ID, get life history traits or other functional characteristics
* from geographical location and date of sampling, retrieve environmental data | 1.0 | Retrieve external data - Since many analyses are likely to want covariates - we can build in some default functions that help with this.
* from taxonomic ID, get life history traits or other functional characteristics
* from geographical location and date of sampling, retrieve environmental data | infrastructure | retrieve external data since many analyses are likely to want covariates we can build in some default functions that help with this from taxonomic id get life history traits or other functional characteristics from geographical location and date of sampling retrieve environmental data | 1 |
5,100 | 5,435,848,397 | IssuesEvent | 2017-03-05 20:22:12 | The-Lounge/TheLounge | https://api.github.com/repos/The-Lounge/TheLounge | opened | Package App in Native Android Wrapper | API feature Infrastructure UI | Users should be able to download TheLounge through the Google Play Store
- The Angular UI is packaged in hybrid wrapper ([Adobe PhoneGap](http://phonegap.com/) or [Apache Cordova](https://cordova.apache.org/))
- The app can be run on modern Android phones and successfully connects to the hosted API
- this will likely involve configuring the API and UI to handle CORS requests
- The app is registered in the Google play store
- the build pipeline is adjusted to facilitate publishing to the play store | 1.0 | Package App in Native Android Wrapper - Users should be able to download TheLounge through the Google Play Store
- The Angular UI is packaged in hybrid wrapper ([Adobe PhoneGap](http://phonegap.com/) or [Apache Cordova](https://cordova.apache.org/))
- The app can be run on modern Android phones and successfully connects to the hosted API
- this will likely involve configuring the API and UI to handle CORS requests
- The app is registered in the Google play store
- the build pipeline is adjusted to facilitate publishing to the play store | infrastructure | package app in native android wrapper users should be able to download thelounge through the google play store the angular ui is packaged in hybrid wrapper or the app can be run on modern android phones and successfully connects to the hosted api this will likely involve configuring the api and ui to handle cors requests the app is registered in the google play store the build pipeline is adjusted to facilitate publishing to the play store | 1 |
104,407 | 16,615,837,961 | IssuesEvent | 2021-06-02 16:32:19 | idonthaveafifaaddiction/minio | https://api.github.com/repos/idonthaveafifaaddiction/minio | opened | CVE-2021-33587 (Medium) detected in css-what-2.1.3.tgz | security vulnerability | ## CVE-2021-33587 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>css-what-2.1.3.tgz</b></p></summary>
<p>a CSS selector parser</p>
<p>Library home page: <a href="https://registry.npmjs.org/css-what/-/css-what-2.1.3.tgz">https://registry.npmjs.org/css-what/-/css-what-2.1.3.tgz</a></p>
<p>Path to dependency file: minio/browser/package.json</p>
<p>Path to vulnerable library: minio/browser/node_modules/css-what/package.json</p>
<p>
Dependency Hierarchy:
- enzyme-3.11.0.tgz (Root Library)
- cheerio-1.0.0-rc.3.tgz
- css-select-1.2.0.tgz
- :x: **css-what-2.1.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/idonthaveafifaaddiction/minio/commit/faa7ae734fc4db219ed0f110588840a84a6e277d">faa7ae734fc4db219ed0f110588840a84a6e277d</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>
The css-what package before 5.0.1 for Node.js does not ensure that attribute parsing has Linear Time Complexity relative to the size of the input.
<p>Publish Date: 2021-05-28
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33587>CVE-2021-33587</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: 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-2021-33587">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33587</a></p>
<p>Release Date: 2021-05-28</p>
<p>Fix Resolution: css-what - 5.0.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"css-what","packageVersion":"2.1.3","packageFilePaths":["/browser/package.json"],"isTransitiveDependency":true,"dependencyTree":"enzyme:3.11.0;cheerio:1.0.0-rc.3;css-select:1.2.0;css-what:2.1.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"css-what - 5.0.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-33587","vulnerabilityDetails":"The css-what package before 5.0.1 for Node.js does not ensure that attribute parsing has Linear Time Complexity relative to the size of the input.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33587","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | True | CVE-2021-33587 (Medium) detected in css-what-2.1.3.tgz - ## CVE-2021-33587 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>css-what-2.1.3.tgz</b></p></summary>
<p>a CSS selector parser</p>
<p>Library home page: <a href="https://registry.npmjs.org/css-what/-/css-what-2.1.3.tgz">https://registry.npmjs.org/css-what/-/css-what-2.1.3.tgz</a></p>
<p>Path to dependency file: minio/browser/package.json</p>
<p>Path to vulnerable library: minio/browser/node_modules/css-what/package.json</p>
<p>
Dependency Hierarchy:
- enzyme-3.11.0.tgz (Root Library)
- cheerio-1.0.0-rc.3.tgz
- css-select-1.2.0.tgz
- :x: **css-what-2.1.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/idonthaveafifaaddiction/minio/commit/faa7ae734fc4db219ed0f110588840a84a6e277d">faa7ae734fc4db219ed0f110588840a84a6e277d</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>
The css-what package before 5.0.1 for Node.js does not ensure that attribute parsing has Linear Time Complexity relative to the size of the input.
<p>Publish Date: 2021-05-28
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33587>CVE-2021-33587</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: 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-2021-33587">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33587</a></p>
<p>Release Date: 2021-05-28</p>
<p>Fix Resolution: css-what - 5.0.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"css-what","packageVersion":"2.1.3","packageFilePaths":["/browser/package.json"],"isTransitiveDependency":true,"dependencyTree":"enzyme:3.11.0;cheerio:1.0.0-rc.3;css-select:1.2.0;css-what:2.1.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"css-what - 5.0.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-33587","vulnerabilityDetails":"The css-what package before 5.0.1 for Node.js does not ensure that attribute parsing has Linear Time Complexity relative to the size of the input.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33587","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | non_infrastructure | cve medium detected in css what tgz cve medium severity vulnerability vulnerable library css what tgz a css selector parser library home page a href path to dependency file minio browser package json path to vulnerable library minio browser node modules css what package json dependency hierarchy enzyme tgz root library cheerio rc tgz css select tgz x css what tgz vulnerable library found in head commit a href found in base branch master vulnerability details the css what package before for node js does not ensure that attribute parsing has linear time complexity relative to the size of the input 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 low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution css what isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree enzyme cheerio rc css select css what isminimumfixversionavailable true minimumfixversion css what basebranches vulnerabilityidentifier cve vulnerabilitydetails the css what package before for node js does not ensure that attribute parsing has linear time complexity relative to the size of the input vulnerabilityurl | 0 |
29,370 | 23,952,152,812 | IssuesEvent | 2022-09-12 12:26:24 | Perl/perl5 | https://api.github.com/repos/Perl/perl5 | closed | make test_porting does not flag need to update t/porting/customized.dat | Infrastructure | (This issue stems from an [observation by Tony Cook](https://github.com/Perl/perl5/pull/20216#discussion_r961317924) in his review of https://github.com/Perl/perl5/pull/20216.)
Suppose I build blead as I did today at 741a5c7396a0ca90a22ea8d8e0761c70c14b0a77, and then run `make test_porting`. All tests will PASS, including, in particular, `t/porting/customized.t`.
```
porting/customized.t ...... ok
```
Now, in the absence of any *deep* study of that test program, I would assume that that means that the data in `t/porting/customized.dat` is up-to-date -- which in turn means that all the `CUSTOMIZED` entries in `Porting/Maintainers.pl` are up-to-date and that I do *not* need to regenerate that database with this command:
```
$ cd t; ./perl -I../lib porting/customized.t --regen; cd -
```
... which appears at the top of `t/porting/customized.dat`.
That assumption turns out to be incorrect. When I run the command above with the `--regen` switch, I get:
```
ok 1 - regenerated data file
1..1
...
$ git status
On branch blead
Your branch is up to date with 'origin/blead'.
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: t/porting/customized.dat
no changes added to commit (use "git add" and/or "git commit -a")
$ git diff |cat
diff --git a/t/porting/customized.dat b/t/porting/customized.dat
index dae5af2446..0c2c70e25a 100644
--- a/t/porting/customized.dat
+++ b/t/porting/customized.dat
@@ -4,17 +4,11 @@
AutoLoader cpan/AutoLoader/t/02AutoSplit.t bb90cda13b88599ad45de4b45799d5218afcb6d8
ExtUtils::Constant cpan/ExtUtils-Constant/lib/ExtUtils/Constant/Base.pm 7560e1018f806db5689dee78728ccb8374aea741
ExtUtils::Constant cpan/ExtUtils-Constant/t/Constant.t 165e9c7132b003fd192d32a737b0f51f9ba4999e
-Filter::Util::Call pod/perlfilter.pod 545265af2f45741a0e59eecdd0cfc0c9e490c1e8
Locale::Maketext::Simple cpan/Locale-Maketext-Simple/lib/Locale/Maketext/Simple.pm 57ed38905791a17c150210cd6f42ead22a7707b6
Math::Complex cpan/Math-Complex/lib/Math/Complex.pm 66f28a17647e2de166909ca66e4ced26f8a0a62e
Math::Complex cpan/Math-Complex/t/Complex.t 17039e03ee798539e770ea9a0d19a99364278306
Math::Complex cpan/Math-Complex/t/Trig.t 508f8e27373c08228be13ca5d42b28812ab0e020
Math::Complex cpan/Math-Complex/t/underbar.t 97e7b9615658eefc67a710d4b258349cc5bace63
-Memoize cpan/Memoize/Memoize.pm 902092ff91cdec9c7b4bd06202eb179e1ce26ca2
-Memoize cpan/Memoize/t/errors.t bcd0c02a4bc47dfda07a97d265d7210849871659
-Memoize cpan/Memoize/t/expmod_t.t a1c3d03fd3ec2e7c6c835f02316475756e1b16b7
-Memoize cpan/Memoize/t/speed.t 89fe8c8928f0164c9ed898b5a427dbbc814e9976
-Memoize cpan/Memoize/t/tie_gdbm.t d81c4f6208f6c925539b3878bff9a8ff1b73a37e
Net::Ping dist/Net-Ping/t/000_load.t deff5dc2ca54dae28cb19d3631427db127279ac2
Net::Ping dist/Net-Ping/t/001_new.t 7b24e05672e22edfe3e6b5cc0277f815efe557e5
Net::Ping dist/Net-Ping/t/010_pingecho.t 218d7a9ee5b6d03ba2544210acaf6585f8dc5503
```
This suggests that the database was *not* updated when Memoize was last synched with CPAN on August 17 -- and since I was the committer, the omission was mine.
```
commit 9c811e448b4468014d49999f6826d6d3f0ad2b21
Author: Aristotle Pagaltzis <pagaltzis@gmx.de>
AuthorDate: Sun Aug 14 19:35:41 2022
Commit: James E Keenan <jkeenan@cpan.org>
CommitDate: Wed Aug 17 12:20:19 2022
Memoize: sync with CPAN version 1.10
```
This further suggests that there's something amiss in `make test_porting`. I am certain that I would have run that before making the commit above on Aug 17 -- but it PASSed and did not indicate that there was anything amiss. So I was not nudged to regenerate that database.
In addition, this suggests that there's something peculiar about `pod/perlfilter.pod` that (i) warranted a `CUSTOMIZED` entry in `Porting/Maintainers.pl` and, accordingly, an entry in `t/porting/customized.dat`; and that (ii) under some circumstances, a regeneration of `customized.dat` would cause the database entry to be removed.
```
-Filter::Util::Call pod/perlfilter.pod 545265af2f45741a0e59eecdd0cfc0c9e490c1e8
```
There is indeed something ... unique about `pod/perlfilter.pod`. It is really [maintained upstream on CPAN](https://metacpan.org/release/RURBAN/Filter-1.64/source/perlfilter.pod) as part of the `Filter` distribution. However, it's been located under `pod/` in the core distribution at least since 2009:
```
commit 2b4f847434de297901e2c76921bae9eecb9a8929
Author: David Mitchell <davem@iabyn.com>
AuthorDate: Wed Jun 3 01:42:20 2009 +0100
Commit: David Mitchell <davem@iabyn.com>
CommitDate: Wed Jun 3 01:43:38 2009 +0100
add more EXCLUDED and MAP keys to Maintainers.pl
```
`pod/perlfilter.pod` was, however, modified in the core distribution recently as part of:
```
commit d84bd0bd478e7c7ff7f57eeb94fda30ee0e34296
Author: Paul Evans <leonerd@leonerd.org.uk>
AuthorDate: Wed Apr 6 12:47:26 2022 +0100
Commit: Paul Evans <leonerd@leonerd.org.uk>
CommitDate: Sat Apr 23 20:09:59 2022 +0100
Replace 'use strict; use warnings;' with 'use VERSION' in docs code examples
```
When I build perl at the commit *before* the above and run `make test_porting`, everything PASSes. If I then regenerate the customize database, I get:
```
$ cd t; ./perl -I../lib porting/customized.t --regen; cd -
ok 1 - regenerated data file
1..1
```
The timestamp indicates that `t/porting/customized.dat` was indeed updated, but there is no difference in its contents.
```
$ git diff
$
```
So my inference is that the manual edit to `pod/perlfilter.pod` triggers the removal of that file's entry in `t/porting/customized.dat` -- even though the file is still listed as `CUSTOMIZED` in `Porting/Maintainers.pl`.
Hence, at this particular moment, `make test_porting` is PASSing but is failing to reflect the need to regenerate `t/porting/customized.data`. This is an obstacle to the merge request in https://github.com/Perl/perl5/pull/20216 but is not relevant to the real subject matter of that p.r. This will also be a consideration for [the way we maintain Math-Complex](https://github.com/Perl/perl5/pull/20215) (though [I have questions](https://github.com/Perl/perl5/pull/20215#issuecomment-1235883618) about the current form of that pull request).
I have not yet studied `t/porting/customized.t` to diagnose the problem further.
| 1.0 | make test_porting does not flag need to update t/porting/customized.dat - (This issue stems from an [observation by Tony Cook](https://github.com/Perl/perl5/pull/20216#discussion_r961317924) in his review of https://github.com/Perl/perl5/pull/20216.)
Suppose I build blead as I did today at 741a5c7396a0ca90a22ea8d8e0761c70c14b0a77, and then run `make test_porting`. All tests will PASS, including, in particular, `t/porting/customized.t`.
```
porting/customized.t ...... ok
```
Now, in the absence of any *deep* study of that test program, I would assume that that means that the data in `t/porting/customized.dat` is up-to-date -- which in turn means that all the `CUSTOMIZED` entries in `Porting/Maintainers.pl` are up-to-date and that I do *not* need to regenerate that database with this command:
```
$ cd t; ./perl -I../lib porting/customized.t --regen; cd -
```
... which appears at the top of `t/porting/customized.dat`.
That assumption turns out to be incorrect. When I run the command above with the `--regen` switch, I get:
```
ok 1 - regenerated data file
1..1
...
$ git status
On branch blead
Your branch is up to date with 'origin/blead'.
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: t/porting/customized.dat
no changes added to commit (use "git add" and/or "git commit -a")
$ git diff |cat
diff --git a/t/porting/customized.dat b/t/porting/customized.dat
index dae5af2446..0c2c70e25a 100644
--- a/t/porting/customized.dat
+++ b/t/porting/customized.dat
@@ -4,17 +4,11 @@
AutoLoader cpan/AutoLoader/t/02AutoSplit.t bb90cda13b88599ad45de4b45799d5218afcb6d8
ExtUtils::Constant cpan/ExtUtils-Constant/lib/ExtUtils/Constant/Base.pm 7560e1018f806db5689dee78728ccb8374aea741
ExtUtils::Constant cpan/ExtUtils-Constant/t/Constant.t 165e9c7132b003fd192d32a737b0f51f9ba4999e
-Filter::Util::Call pod/perlfilter.pod 545265af2f45741a0e59eecdd0cfc0c9e490c1e8
Locale::Maketext::Simple cpan/Locale-Maketext-Simple/lib/Locale/Maketext/Simple.pm 57ed38905791a17c150210cd6f42ead22a7707b6
Math::Complex cpan/Math-Complex/lib/Math/Complex.pm 66f28a17647e2de166909ca66e4ced26f8a0a62e
Math::Complex cpan/Math-Complex/t/Complex.t 17039e03ee798539e770ea9a0d19a99364278306
Math::Complex cpan/Math-Complex/t/Trig.t 508f8e27373c08228be13ca5d42b28812ab0e020
Math::Complex cpan/Math-Complex/t/underbar.t 97e7b9615658eefc67a710d4b258349cc5bace63
-Memoize cpan/Memoize/Memoize.pm 902092ff91cdec9c7b4bd06202eb179e1ce26ca2
-Memoize cpan/Memoize/t/errors.t bcd0c02a4bc47dfda07a97d265d7210849871659
-Memoize cpan/Memoize/t/expmod_t.t a1c3d03fd3ec2e7c6c835f02316475756e1b16b7
-Memoize cpan/Memoize/t/speed.t 89fe8c8928f0164c9ed898b5a427dbbc814e9976
-Memoize cpan/Memoize/t/tie_gdbm.t d81c4f6208f6c925539b3878bff9a8ff1b73a37e
Net::Ping dist/Net-Ping/t/000_load.t deff5dc2ca54dae28cb19d3631427db127279ac2
Net::Ping dist/Net-Ping/t/001_new.t 7b24e05672e22edfe3e6b5cc0277f815efe557e5
Net::Ping dist/Net-Ping/t/010_pingecho.t 218d7a9ee5b6d03ba2544210acaf6585f8dc5503
```
This suggests that the database was *not* updated when Memoize was last synched with CPAN on August 17 -- and since I was the committer, the omission was mine.
```
commit 9c811e448b4468014d49999f6826d6d3f0ad2b21
Author: Aristotle Pagaltzis <pagaltzis@gmx.de>
AuthorDate: Sun Aug 14 19:35:41 2022
Commit: James E Keenan <jkeenan@cpan.org>
CommitDate: Wed Aug 17 12:20:19 2022
Memoize: sync with CPAN version 1.10
```
This further suggests that there's something amiss in `make test_porting`. I am certain that I would have run that before making the commit above on Aug 17 -- but it PASSed and did not indicate that there was anything amiss. So I was not nudged to regenerate that database.
In addition, this suggests that there's something peculiar about `pod/perlfilter.pod` that (i) warranted a `CUSTOMIZED` entry in `Porting/Maintainers.pl` and, accordingly, an entry in `t/porting/customized.dat`; and that (ii) under some circumstances, a regeneration of `customized.dat` would cause the database entry to be removed.
```
-Filter::Util::Call pod/perlfilter.pod 545265af2f45741a0e59eecdd0cfc0c9e490c1e8
```
There is indeed something ... unique about `pod/perlfilter.pod`. It is really [maintained upstream on CPAN](https://metacpan.org/release/RURBAN/Filter-1.64/source/perlfilter.pod) as part of the `Filter` distribution. However, it's been located under `pod/` in the core distribution at least since 2009:
```
commit 2b4f847434de297901e2c76921bae9eecb9a8929
Author: David Mitchell <davem@iabyn.com>
AuthorDate: Wed Jun 3 01:42:20 2009 +0100
Commit: David Mitchell <davem@iabyn.com>
CommitDate: Wed Jun 3 01:43:38 2009 +0100
add more EXCLUDED and MAP keys to Maintainers.pl
```
`pod/perlfilter.pod` was, however, modified in the core distribution recently as part of:
```
commit d84bd0bd478e7c7ff7f57eeb94fda30ee0e34296
Author: Paul Evans <leonerd@leonerd.org.uk>
AuthorDate: Wed Apr 6 12:47:26 2022 +0100
Commit: Paul Evans <leonerd@leonerd.org.uk>
CommitDate: Sat Apr 23 20:09:59 2022 +0100
Replace 'use strict; use warnings;' with 'use VERSION' in docs code examples
```
When I build perl at the commit *before* the above and run `make test_porting`, everything PASSes. If I then regenerate the customize database, I get:
```
$ cd t; ./perl -I../lib porting/customized.t --regen; cd -
ok 1 - regenerated data file
1..1
```
The timestamp indicates that `t/porting/customized.dat` was indeed updated, but there is no difference in its contents.
```
$ git diff
$
```
So my inference is that the manual edit to `pod/perlfilter.pod` triggers the removal of that file's entry in `t/porting/customized.dat` -- even though the file is still listed as `CUSTOMIZED` in `Porting/Maintainers.pl`.
Hence, at this particular moment, `make test_porting` is PASSing but is failing to reflect the need to regenerate `t/porting/customized.data`. This is an obstacle to the merge request in https://github.com/Perl/perl5/pull/20216 but is not relevant to the real subject matter of that p.r. This will also be a consideration for [the way we maintain Math-Complex](https://github.com/Perl/perl5/pull/20215) (though [I have questions](https://github.com/Perl/perl5/pull/20215#issuecomment-1235883618) about the current form of that pull request).
I have not yet studied `t/porting/customized.t` to diagnose the problem further.
| infrastructure | make test porting does not flag need to update t porting customized dat this issue stems from an in his review of suppose i build blead as i did today at and then run make test porting all tests will pass including in particular t porting customized t porting customized t ok now in the absence of any deep study of that test program i would assume that that means that the data in t porting customized dat is up to date which in turn means that all the customized entries in porting maintainers pl are up to date and that i do not need to regenerate that database with this command cd t perl i lib porting customized t regen cd which appears at the top of t porting customized dat that assumption turns out to be incorrect when i run the command above with the regen switch i get ok regenerated data file git status on branch blead your branch is up to date with origin blead changes not staged for commit use git add to update what will be committed use git restore to discard changes in working directory modified t porting customized dat no changes added to commit use git add and or git commit a git diff cat diff git a t porting customized dat b t porting customized dat index a t porting customized dat b t porting customized dat autoloader cpan autoloader t t extutils constant cpan extutils constant lib extutils constant base pm extutils constant cpan extutils constant t constant t filter util call pod perlfilter pod locale maketext simple cpan locale maketext simple lib locale maketext simple pm math complex cpan math complex lib math complex pm math complex cpan math complex t complex t math complex cpan math complex t trig t math complex cpan math complex t underbar t memoize cpan memoize memoize pm memoize cpan memoize t errors t memoize cpan memoize t expmod t t memoize cpan memoize t speed t memoize cpan memoize t tie gdbm t net ping dist net ping t load t net ping dist net ping t new t net ping dist net ping t pingecho t this suggests that the database was not updated when memoize was last synched with cpan on august and since i was the committer the omission was mine commit author aristotle pagaltzis authordate sun aug commit james e keenan commitdate wed aug memoize sync with cpan version this further suggests that there s something amiss in make test porting i am certain that i would have run that before making the commit above on aug but it passed and did not indicate that there was anything amiss so i was not nudged to regenerate that database in addition this suggests that there s something peculiar about pod perlfilter pod that i warranted a customized entry in porting maintainers pl and accordingly an entry in t porting customized dat and that ii under some circumstances a regeneration of customized dat would cause the database entry to be removed filter util call pod perlfilter pod there is indeed something unique about pod perlfilter pod it is really as part of the filter distribution however it s been located under pod in the core distribution at least since commit author david mitchell authordate wed jun commit david mitchell commitdate wed jun add more excluded and map keys to maintainers pl pod perlfilter pod was however modified in the core distribution recently as part of commit author paul evans authordate wed apr commit paul evans commitdate sat apr replace use strict use warnings with use version in docs code examples when i build perl at the commit before the above and run make test porting everything passes if i then regenerate the customize database i get cd t perl i lib porting customized t regen cd ok regenerated data file the timestamp indicates that t porting customized dat was indeed updated but there is no difference in its contents git diff so my inference is that the manual edit to pod perlfilter pod triggers the removal of that file s entry in t porting customized dat even though the file is still listed as customized in porting maintainers pl hence at this particular moment make test porting is passing but is failing to reflect the need to regenerate t porting customized data this is an obstacle to the merge request in but is not relevant to the real subject matter of that p r this will also be a consideration for though about the current form of that pull request i have not yet studied t porting customized t to diagnose the problem further | 1 |
8,093 | 7,214,763,705 | IssuesEvent | 2018-02-08 04:16:31 | mcvine/mcvine | https://api.github.com/repos/mcvine/mcvine | closed | restructure: move "instruments" to its own repository? | Infrastructure | This allows for easier developments of more instrument simulation applications and leave the core of mcvine in this repository.
| 1.0 | restructure: move "instruments" to its own repository? - This allows for easier developments of more instrument simulation applications and leave the core of mcvine in this repository.
| infrastructure | restructure move instruments to its own repository this allows for easier developments of more instrument simulation applications and leave the core of mcvine in this repository | 1 |
2,461 | 3,691,023,553 | IssuesEvent | 2016-02-25 22:13:34 | dotnet/wcf | https://api.github.com/repos/dotnet/wcf | closed | Remove 'AnyOS' builds from all WCF projects. | 2 - In Progress Infrastructure | The core issue is that if a test project builds as ‘AnyOS’ it will run against an ‘AnyOS’ flavor of WCF Core causing the failures we have seen. This is because of the build & run logic we have inherited from corefx.
Since we don’t support our product building against ‘AnyOS’ we should fix the issue on our side that triggers ‘AnyOS’ flavors to get build. This is most likely caused by test or related projects such as the Common or Infrastructure projects.
One point of clarification. WCF Core built against 'AnyOS' results in a build that works for Linus (Unix), the product forks based on whether it targets Windows. | 1.0 | Remove 'AnyOS' builds from all WCF projects. - The core issue is that if a test project builds as ‘AnyOS’ it will run against an ‘AnyOS’ flavor of WCF Core causing the failures we have seen. This is because of the build & run logic we have inherited from corefx.
Since we don’t support our product building against ‘AnyOS’ we should fix the issue on our side that triggers ‘AnyOS’ flavors to get build. This is most likely caused by test or related projects such as the Common or Infrastructure projects.
One point of clarification. WCF Core built against 'AnyOS' results in a build that works for Linus (Unix), the product forks based on whether it targets Windows. | infrastructure | remove anyos builds from all wcf projects the core issue is that if a test project builds as ‘anyos’ it will run against an ‘anyos’ flavor of wcf core causing the failures we have seen this is because of the build run logic we have inherited from corefx since we don’t support our product building against ‘anyos’ we should fix the issue on our side that triggers ‘anyos’ flavors to get build this is most likely caused by test or related projects such as the common or infrastructure projects one point of clarification wcf core built against anyos results in a build that works for linus unix the product forks based on whether it targets windows | 1 |
15,770 | 11,701,725,514 | IssuesEvent | 2020-03-06 20:20:10 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | Building dotnet/runtime fails with exit code 253 | area-Infrastructure-coreclr | Building the dotnet/runtime repo after `git clean -xdff` with `./coreclr.sh -c release` failed with
```
/Users/mdhwang/runtime/src/coreclr/crossgen-corelib.proj(17,5): error MSB3073: The command ""/Users/mdhwang/runtime/src/coreclr/crossgen-corelib.sh" -release" exited with code 253.
/Users/mdhwang/runtime/.dotnet/sdk/5.0.100-preview.2.20153.3/Microsoft.Common.CurrentVersion.targets(4643,5): error MSB3030: Could not copy the file "/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/libclrjit.dylib" because it was not found. [/Users/mdhwang/runtime/src/coreclr/src/tools/crossgen2/crossgen2/crossgen2.csproj]
/Users/mdhwang/runtime/.dotnet/sdk/5.0.100-preview.2.20153.3/Microsoft.Common.CurrentVersion.targets(4643,5): error MSB3030: Could not copy the file "/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/libjitinterface.dylib" because it was not found. [/Users/mdhwang/runtime/src/coreclr/src/tools/crossgen2/crossgen2/crossgen2.csproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget lib package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.ILAsm.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/ilasm'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget packed package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.ILAsm.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/ilasm'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget lib package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.ILDAsm.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/ildasm'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget packed package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.ILDAsm.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/ildasm'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget packed package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.ILDAsm.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/ildasm'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget packed package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.ILAsm.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/ilasm'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget lib package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.TestHost.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/corerun'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget packed package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.TestHost.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/corerun'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget packed package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.TestHost.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/corerun'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
0 Warning(s)
12 Error(s)
```
[Full build log](https://github.com/dotnet/runtime/files/4289140/coreclr_release_build.txt)
Running `uname -p` gave `i386`.
Forcing the architecture in `eng/native/init-os-and-arch.sh` by changing https://github.com/dotnet/runtime/blob/389835b1597180c0753c4daeb88afe008252dfe4/eng/native/init-os-and-arch.sh#L16 to `CPUName=x86_64` allows for a successful build.
There seems to be an inconsistency with the system detecting 32-bit, yet building with `amd64` paths. Changing `uname -p` to `uname-m` might help properly detect 64-bit.
##
System
macOS Catalina 10.15.3
| 1.0 | Building dotnet/runtime fails with exit code 253 - Building the dotnet/runtime repo after `git clean -xdff` with `./coreclr.sh -c release` failed with
```
/Users/mdhwang/runtime/src/coreclr/crossgen-corelib.proj(17,5): error MSB3073: The command ""/Users/mdhwang/runtime/src/coreclr/crossgen-corelib.sh" -release" exited with code 253.
/Users/mdhwang/runtime/.dotnet/sdk/5.0.100-preview.2.20153.3/Microsoft.Common.CurrentVersion.targets(4643,5): error MSB3030: Could not copy the file "/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/libclrjit.dylib" because it was not found. [/Users/mdhwang/runtime/src/coreclr/src/tools/crossgen2/crossgen2/crossgen2.csproj]
/Users/mdhwang/runtime/.dotnet/sdk/5.0.100-preview.2.20153.3/Microsoft.Common.CurrentVersion.targets(4643,5): error MSB3030: Could not copy the file "/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/libjitinterface.dylib" because it was not found. [/Users/mdhwang/runtime/src/coreclr/src/tools/crossgen2/crossgen2/crossgen2.csproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget lib package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.ILAsm.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/ilasm'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget packed package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.ILAsm.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/ilasm'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget lib package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.ILDAsm.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/ildasm'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget packed package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.ILDAsm.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/ildasm'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget packed package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.ILDAsm.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/ildasm'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILDAsm/Microsoft.NETCore.ILDAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget packed package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.ILAsm.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/ilasm'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.ILAsm/Microsoft.NETCore.ILAsm.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget lib package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.TestHost.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/corerun'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget packed package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.TestHost.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/corerun'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : Error when creating nuget packed package from /Users/mdhwang/runtime/artifacts/packages/Release/specs/runtime.osx-x86.Microsoft.NETCore.TestHost.nuspec. NuGet.Packaging.Core.PackagingException: File not found: '/Users/mdhwang/runtime/artifacts/bin/coreclr/OSX.x64.Release/corerun'. [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.AddFiles(String basePath, String source, String destination, String exclude) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at NuGet.Packaging.PackageBuilder.PopulateFiles(String basePath, IEnumerable`1 files) [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
/Users/mdhwang/.nuget/packages/microsoft.dotnet.build.tasks.packaging/5.0.0-beta.20152.4/build/Packaging.targets(1260,5): error : at Microsoft.DotNet.Build.Tasks.Packaging.NuGetPack.Pack(String nuspecPath, String nupkgPath, Manifest manifest, Boolean packSymbols) in /_/src/Microsoft.DotNet.Build.Tasks.Packaging/src/NuGetPack.cs:line 254 [/Users/mdhwang/runtime/src/coreclr/src/.nuget/Microsoft.NETCore.TestHost/Microsoft.NETCore.TestHost.pkgproj]
0 Warning(s)
12 Error(s)
```
[Full build log](https://github.com/dotnet/runtime/files/4289140/coreclr_release_build.txt)
Running `uname -p` gave `i386`.
Forcing the architecture in `eng/native/init-os-and-arch.sh` by changing https://github.com/dotnet/runtime/blob/389835b1597180c0753c4daeb88afe008252dfe4/eng/native/init-os-and-arch.sh#L16 to `CPUName=x86_64` allows for a successful build.
There seems to be an inconsistency with the system detecting 32-bit, yet building with `amd64` paths. Changing `uname -p` to `uname-m` might help properly detect 64-bit.
##
System
macOS Catalina 10.15.3
| infrastructure | building dotnet runtime fails with exit code building the dotnet runtime repo after git clean xdff with coreclr sh c release failed with users mdhwang runtime src coreclr crossgen corelib proj error the command users mdhwang runtime src coreclr crossgen corelib sh release exited with code users mdhwang runtime dotnet sdk preview microsoft common currentversion targets error could not copy the file users mdhwang runtime artifacts bin coreclr osx release libclrjit dylib because it was not found users mdhwang runtime dotnet sdk preview microsoft common currentversion targets error could not copy the file users mdhwang runtime artifacts bin coreclr osx release libjitinterface dylib because it was not found users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error error when creating nuget lib package from users mdhwang runtime artifacts packages release specs runtime osx microsoft netcore ilasm nuspec nuget packaging core packagingexception file not found users mdhwang runtime artifacts bin coreclr osx release ilasm users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder addfiles string basepath string source string destination string exclude users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder populatefiles string basepath ienumerable files users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at microsoft dotnet build tasks packaging nugetpack pack string nuspecpath string nupkgpath manifest manifest boolean packsymbols in src microsoft dotnet build tasks packaging src nugetpack cs line users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error error when creating nuget packed package from users mdhwang runtime artifacts packages release specs runtime osx microsoft netcore ilasm nuspec nuget packaging core packagingexception file not found users mdhwang runtime artifacts bin coreclr osx release ilasm users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder addfiles string basepath string source string destination string exclude users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder populatefiles string basepath ienumerable files users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at microsoft dotnet build tasks packaging nugetpack pack string nuspecpath string nupkgpath manifest manifest boolean packsymbols in src microsoft dotnet build tasks packaging src nugetpack cs line users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error error when creating nuget lib package from users mdhwang runtime artifacts packages release specs runtime osx microsoft netcore ildasm nuspec nuget packaging core packagingexception file not found users mdhwang runtime artifacts bin coreclr osx release ildasm users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder addfiles string basepath string source string destination string exclude users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder populatefiles string basepath ienumerable files users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at microsoft dotnet build tasks packaging nugetpack pack string nuspecpath string nupkgpath manifest manifest boolean packsymbols in src microsoft dotnet build tasks packaging src nugetpack cs line users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error error when creating nuget packed package from users mdhwang runtime artifacts packages release specs runtime osx microsoft netcore ildasm nuspec nuget packaging core packagingexception file not found users mdhwang runtime artifacts bin coreclr osx release ildasm users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder addfiles string basepath string source string destination string exclude users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder populatefiles string basepath ienumerable files users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at microsoft dotnet build tasks packaging nugetpack pack string nuspecpath string nupkgpath manifest manifest boolean packsymbols in src microsoft dotnet build tasks packaging src nugetpack cs line users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error error when creating nuget packed package from users mdhwang runtime artifacts packages release specs runtime osx microsoft netcore ildasm nuspec nuget packaging core packagingexception file not found users mdhwang runtime artifacts bin coreclr osx release ildasm users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder addfiles string basepath string source string destination string exclude users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder populatefiles string basepath ienumerable files users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at microsoft dotnet build tasks packaging nugetpack pack string nuspecpath string nupkgpath manifest manifest boolean packsymbols in src microsoft dotnet build tasks packaging src nugetpack cs line users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error error when creating nuget packed package from users mdhwang runtime artifacts packages release specs runtime osx microsoft netcore ilasm nuspec nuget packaging core packagingexception file not found users mdhwang runtime artifacts bin coreclr osx release ilasm users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder addfiles string basepath string source string destination string exclude users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder populatefiles string basepath ienumerable files users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at microsoft dotnet build tasks packaging nugetpack pack string nuspecpath string nupkgpath manifest manifest boolean packsymbols in src microsoft dotnet build tasks packaging src nugetpack cs line users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error error when creating nuget lib package from users mdhwang runtime artifacts packages release specs runtime osx microsoft netcore testhost nuspec nuget packaging core packagingexception file not found users mdhwang runtime artifacts bin coreclr osx release corerun users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder addfiles string basepath string source string destination string exclude users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder populatefiles string basepath ienumerable files users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at microsoft dotnet build tasks packaging nugetpack pack string nuspecpath string nupkgpath manifest manifest boolean packsymbols in src microsoft dotnet build tasks packaging src nugetpack cs line users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error error when creating nuget packed package from users mdhwang runtime artifacts packages release specs runtime osx microsoft netcore testhost nuspec nuget packaging core packagingexception file not found users mdhwang runtime artifacts bin coreclr osx release corerun users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder addfiles string basepath string source string destination string exclude users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder populatefiles string basepath ienumerable files users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at microsoft dotnet build tasks packaging nugetpack pack string nuspecpath string nupkgpath manifest manifest boolean packsymbols in src microsoft dotnet build tasks packaging src nugetpack cs line users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error error when creating nuget packed package from users mdhwang runtime artifacts packages release specs runtime osx microsoft netcore testhost nuspec nuget packaging core packagingexception file not found users mdhwang runtime artifacts bin coreclr osx release corerun users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder addfiles string basepath string source string destination string exclude users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at nuget packaging packagebuilder populatefiles string basepath ienumerable files users mdhwang nuget packages microsoft dotnet build tasks packaging beta build packaging targets error at microsoft dotnet build tasks packaging nugetpack pack string nuspecpath string nupkgpath manifest manifest boolean packsymbols in src microsoft dotnet build tasks packaging src nugetpack cs line warning s error s running uname p gave forcing the architecture in eng native init os and arch sh by changing to cpuname allows for a successful build there seems to be an inconsistency with the system detecting bit yet building with paths changing uname p to uname m might help properly detect bit system macos catalina | 1 |
383,713 | 26,562,344,724 | IssuesEvent | 2023-01-20 16:53:38 | w3c/rdf-canon | https://api.github.com/repos/w3c/rdf-canon | opened | Security considerations | documentation | This just a place where we can discuss any security issues that we think might arise from the spec. Looking at the [self-assessment form](https://www.w3.org/TR/security-privacy-questionnaire/) it doesn't look like we will have much to worry about but we need to consider this carefully. | 1.0 | Security considerations - This just a place where we can discuss any security issues that we think might arise from the spec. Looking at the [self-assessment form](https://www.w3.org/TR/security-privacy-questionnaire/) it doesn't look like we will have much to worry about but we need to consider this carefully. | non_infrastructure | security considerations this just a place where we can discuss any security issues that we think might arise from the spec looking at the it doesn t look like we will have much to worry about but we need to consider this carefully | 0 |
73,276 | 19,621,643,263 | IssuesEvent | 2022-01-07 07:38:31 | ClickHouse/ClickHouse | https://api.github.com/repos/ClickHouse/ClickHouse | closed | build clickhouse on Ubuntu error | build st-need-info | clickhouse-21.11.5.33
Ubuntu 21.10
cmake version 3.18.4
clang version 13.0.1-
ninja 1.10.1
cmake ../
ninja clickhouse
error output:
[7918/9990] Linking CXX executable base/base/tests/dump_variable
FAILED: base/base/tests/dump_variable
: && /usr/bin/clang++-13 -fdiagnostics-color=always -Xclang -fuse-ctor-homing -include /opt/softs/ClickHouse/base/glibc-compatibility/glibc-compat-2.32.h -fsized-deallocation -gdwarf-aranges -mssse3 -msse4.1 -msse4.2 -mpclmul -mpopcnt -fasynchronous-unwind-tables -falign-functions=32 -Wall -Wno-unused-command-line-argument -fdiagnostics-absolute-paths -fexperimental-new-pass-manager -Werror -Wextra -Wframe-larger-than=65536 -Wpedantic -Wno-vla-extension -Wno-zero-length-array -Wno-c11-extensions -Wcomma -Wconditional-uninitialized -Wcovered-switch-default -Wdeprecated -Wembedded-directive -Wempty-init-stmt -Wextra-semi-stmt -Wextra-semi -Wgnu-case-range -Winconsistent-missing-destructor-override -Wnewline-eof -Wold-style-cast -Wrange-loop-analysis -Wredundant-parens -Wreserved-id-macro -Wshadow-field -Wshadow-uncaptured-local -Wshadow -Wstring-plus-int -Wundef -Wunreachable-code-return -Wunreachable-code -Wunused-exception-parameter -Wunused-macros -Wunused-member-function -Wunneeded-internal-declaration -Wimplicit-int-float-conversion -Wanon-enum-enum-conversion -Wassign-enum -Wbitwise-op-parentheses -Wint-in-bool-context -Wsometimes-uninitialized -Wtautological-bitwise-compare -Wzero-as-null-pointer-constant -Weverything -Wno-c++98-compat-pedantic -Wno-c++98-compat -Wno-c99-extensions -Wno-conversion -Wno-ctad-maybe-unsupported -Wno-deprecated-dynamic-exception-spec -Wno-disabled-macro-expansion -Wno-documentation-unknown-command -Wno-double-promotion -Wno-exit-time-destructors -Wno-float-equal -Wno-global-constructors -Wno-missing-prototypes -Wno-missing-variable-declarations -Wno-nested-anon-types -Wno-packed -Wno-padded -Wno-shift-sign-overflow -Wno-sign-conversion -Wno-switch-enum -Wno-undefined-func-template -Wno-unused-template -Wno-vla -Wno-weak-template-vtables -Wno-weak-vtables -O2 -g -DNDEBUG -O3 -fno-pie --ld-path=/usr/bin/ld.lld-13 -rdynamic -Wl,--no-undefined -Wl,-no-pie src/CMakeFiles/clickhouse_malloc.dir/Common/malloc.cpp.o base/base/tests/CMakeFiles/dump_variable.dir/dump_variable.cpp.o -o base/base/tests/dump_variable src/libclickhouse_common_io.a contrib/jemalloc-cmake/libjemalloc.a src/Common/StringUtils/libstring_utils.a base/widechar_width/libwidechar_width.a base/base/libcommon.a contrib/poco-cmake/Net/SSL/lib_poco_net_ssl.a contrib/poco-cmake/Net/lib_poco_net.a contrib/poco-cmake/Crypto/lib_poco_crypto.a contrib/poco-cmake/Util/lib_poco_util.a contrib/poco-cmake/JSON/lib_poco_json.a contrib/poco-cmake/JSON/lib_poco_json_pdjson.a contrib/poco-cmake/XML/lib_poco_xml.a contrib/poco-cmake/XML/lib_poco_xml_expat.a contrib/replxx-cmake/libreplxx.a contrib/cctz-cmake/libcctz.a -Wl,--whole-archive /opt/softs/ClickHouse/build/contrib/cctz-cmake/libtzdata.a -Wl,--no-whole-archive contrib/fmtlib-cmake/libfmt.a contrib/double-conversion-cmake/libdouble-conversion.a contrib/dragonbox-cmake/libdragonbox_to_chars.a contrib/re2/libre2.a contrib/re2_st/libre2_st.a contrib/libcpuid-cmake/libcpuid.a contrib/boost-cmake/lib_boost_program_options.a contrib/boost-cmake/lib_boost_system.a contrib/cityhash102/libcityhash.a contrib/poco-cmake/Foundation/lib_poco_foundation.a contrib/zlib-ng/libz.a contrib/poco-cmake/Foundation/lib_poco_foundation_pcre.a contrib/zstd-cmake/libzstd.a contrib/xz/liblzma.a contrib/aws-s3-cmake/libaws_s3.a contrib/boringssl-cmake/libssl.a contrib/boringssl-cmake/libcrypto.a -lpthread contrib/aws-s3-cmake/libaws_s3_checksums.a contrib/brotli-cmake/libbrotli.a contrib/lz4-cmake/liblz4.a contrib/bzip2-cmake/libbzip2.a -Wl,--start-group base/glibc-compatibility/libglibc-compatibility.a base/glibc-compatibility/memcpy/libmemcpy.a contrib/libcxx-cmake/libcxx.a contrib/libcxxabi-cmake/libcxxabi.a contrib/libunwind-cmake/libunwind.a -Wl,--end-group -nodefaultlibs /usr/lib/llvm-13/lib/clang/13.0.1/lib/linux/libclang_rt.builtins-x86_64.a -lc -lm -lrt -lpthread -ldl && :
ld.lld-13: error: undefined symbol: __pthread_mutex_lock
>>> referenced by ThreadFuzzer.cpp:293 (../src/Common/ThreadFuzzer.cpp:293)
>>> ThreadFuzzer.cpp.o:(pthread_mutex_lock) in archive src/libclickhouse_common_io.a
>>> did you mean: __pthread_mutex_lock@GLIBC_2.2.5
>>> defined in: /lib/x86_64-linux-gnu/libc.so.6
ld.lld-13: error: undefined symbol: __pthread_mutex_unlock
>>> referenced by ThreadFuzzer.cpp:293 (../src/Common/ThreadFuzzer.cpp:293)
>>> ThreadFuzzer.cpp.o:(pthread_mutex_unlock) in archive src/libclickhouse_common_io.a
>>> did you mean: __pthread_mutex_unlock@GLIBC_2.2.5
>>> defined in: /lib/x86_64-linux-gnu/libc.so.6
clang: error: linker command failed with exit code 1 (use -v to see invocation)
[7919/9990] Building CXX object utils/keeper-bench/CMakeFiles/keeper-bench.dir/Runner.cpp.o
ninja: build stopped: subcommand failed.
| 1.0 | build clickhouse on Ubuntu error - clickhouse-21.11.5.33
Ubuntu 21.10
cmake version 3.18.4
clang version 13.0.1-
ninja 1.10.1
cmake ../
ninja clickhouse
error output:
[7918/9990] Linking CXX executable base/base/tests/dump_variable
FAILED: base/base/tests/dump_variable
: && /usr/bin/clang++-13 -fdiagnostics-color=always -Xclang -fuse-ctor-homing -include /opt/softs/ClickHouse/base/glibc-compatibility/glibc-compat-2.32.h -fsized-deallocation -gdwarf-aranges -mssse3 -msse4.1 -msse4.2 -mpclmul -mpopcnt -fasynchronous-unwind-tables -falign-functions=32 -Wall -Wno-unused-command-line-argument -fdiagnostics-absolute-paths -fexperimental-new-pass-manager -Werror -Wextra -Wframe-larger-than=65536 -Wpedantic -Wno-vla-extension -Wno-zero-length-array -Wno-c11-extensions -Wcomma -Wconditional-uninitialized -Wcovered-switch-default -Wdeprecated -Wembedded-directive -Wempty-init-stmt -Wextra-semi-stmt -Wextra-semi -Wgnu-case-range -Winconsistent-missing-destructor-override -Wnewline-eof -Wold-style-cast -Wrange-loop-analysis -Wredundant-parens -Wreserved-id-macro -Wshadow-field -Wshadow-uncaptured-local -Wshadow -Wstring-plus-int -Wundef -Wunreachable-code-return -Wunreachable-code -Wunused-exception-parameter -Wunused-macros -Wunused-member-function -Wunneeded-internal-declaration -Wimplicit-int-float-conversion -Wanon-enum-enum-conversion -Wassign-enum -Wbitwise-op-parentheses -Wint-in-bool-context -Wsometimes-uninitialized -Wtautological-bitwise-compare -Wzero-as-null-pointer-constant -Weverything -Wno-c++98-compat-pedantic -Wno-c++98-compat -Wno-c99-extensions -Wno-conversion -Wno-ctad-maybe-unsupported -Wno-deprecated-dynamic-exception-spec -Wno-disabled-macro-expansion -Wno-documentation-unknown-command -Wno-double-promotion -Wno-exit-time-destructors -Wno-float-equal -Wno-global-constructors -Wno-missing-prototypes -Wno-missing-variable-declarations -Wno-nested-anon-types -Wno-packed -Wno-padded -Wno-shift-sign-overflow -Wno-sign-conversion -Wno-switch-enum -Wno-undefined-func-template -Wno-unused-template -Wno-vla -Wno-weak-template-vtables -Wno-weak-vtables -O2 -g -DNDEBUG -O3 -fno-pie --ld-path=/usr/bin/ld.lld-13 -rdynamic -Wl,--no-undefined -Wl,-no-pie src/CMakeFiles/clickhouse_malloc.dir/Common/malloc.cpp.o base/base/tests/CMakeFiles/dump_variable.dir/dump_variable.cpp.o -o base/base/tests/dump_variable src/libclickhouse_common_io.a contrib/jemalloc-cmake/libjemalloc.a src/Common/StringUtils/libstring_utils.a base/widechar_width/libwidechar_width.a base/base/libcommon.a contrib/poco-cmake/Net/SSL/lib_poco_net_ssl.a contrib/poco-cmake/Net/lib_poco_net.a contrib/poco-cmake/Crypto/lib_poco_crypto.a contrib/poco-cmake/Util/lib_poco_util.a contrib/poco-cmake/JSON/lib_poco_json.a contrib/poco-cmake/JSON/lib_poco_json_pdjson.a contrib/poco-cmake/XML/lib_poco_xml.a contrib/poco-cmake/XML/lib_poco_xml_expat.a contrib/replxx-cmake/libreplxx.a contrib/cctz-cmake/libcctz.a -Wl,--whole-archive /opt/softs/ClickHouse/build/contrib/cctz-cmake/libtzdata.a -Wl,--no-whole-archive contrib/fmtlib-cmake/libfmt.a contrib/double-conversion-cmake/libdouble-conversion.a contrib/dragonbox-cmake/libdragonbox_to_chars.a contrib/re2/libre2.a contrib/re2_st/libre2_st.a contrib/libcpuid-cmake/libcpuid.a contrib/boost-cmake/lib_boost_program_options.a contrib/boost-cmake/lib_boost_system.a contrib/cityhash102/libcityhash.a contrib/poco-cmake/Foundation/lib_poco_foundation.a contrib/zlib-ng/libz.a contrib/poco-cmake/Foundation/lib_poco_foundation_pcre.a contrib/zstd-cmake/libzstd.a contrib/xz/liblzma.a contrib/aws-s3-cmake/libaws_s3.a contrib/boringssl-cmake/libssl.a contrib/boringssl-cmake/libcrypto.a -lpthread contrib/aws-s3-cmake/libaws_s3_checksums.a contrib/brotli-cmake/libbrotli.a contrib/lz4-cmake/liblz4.a contrib/bzip2-cmake/libbzip2.a -Wl,--start-group base/glibc-compatibility/libglibc-compatibility.a base/glibc-compatibility/memcpy/libmemcpy.a contrib/libcxx-cmake/libcxx.a contrib/libcxxabi-cmake/libcxxabi.a contrib/libunwind-cmake/libunwind.a -Wl,--end-group -nodefaultlibs /usr/lib/llvm-13/lib/clang/13.0.1/lib/linux/libclang_rt.builtins-x86_64.a -lc -lm -lrt -lpthread -ldl && :
ld.lld-13: error: undefined symbol: __pthread_mutex_lock
>>> referenced by ThreadFuzzer.cpp:293 (../src/Common/ThreadFuzzer.cpp:293)
>>> ThreadFuzzer.cpp.o:(pthread_mutex_lock) in archive src/libclickhouse_common_io.a
>>> did you mean: __pthread_mutex_lock@GLIBC_2.2.5
>>> defined in: /lib/x86_64-linux-gnu/libc.so.6
ld.lld-13: error: undefined symbol: __pthread_mutex_unlock
>>> referenced by ThreadFuzzer.cpp:293 (../src/Common/ThreadFuzzer.cpp:293)
>>> ThreadFuzzer.cpp.o:(pthread_mutex_unlock) in archive src/libclickhouse_common_io.a
>>> did you mean: __pthread_mutex_unlock@GLIBC_2.2.5
>>> defined in: /lib/x86_64-linux-gnu/libc.so.6
clang: error: linker command failed with exit code 1 (use -v to see invocation)
[7919/9990] Building CXX object utils/keeper-bench/CMakeFiles/keeper-bench.dir/Runner.cpp.o
ninja: build stopped: subcommand failed.
| non_infrastructure | build clickhouse on ubuntu error clickhouse ubuntu cmake version clang version ninja cmake ninja clickhouse error output linking cxx executable base base tests dump variable failed base base tests dump variable usr bin clang fdiagnostics color always xclang fuse ctor homing include opt softs clickhouse base glibc compatibility glibc compat h fsized deallocation gdwarf aranges mpclmul mpopcnt fasynchronous unwind tables falign functions wall wno unused command line argument fdiagnostics absolute paths fexperimental new pass manager werror wextra wframe larger than wpedantic wno vla extension wno zero length array wno extensions wcomma wconditional uninitialized wcovered switch default wdeprecated wembedded directive wempty init stmt wextra semi stmt wextra semi wgnu case range winconsistent missing destructor override wnewline eof wold style cast wrange loop analysis wredundant parens wreserved id macro wshadow field wshadow uncaptured local wshadow wstring plus int wundef wunreachable code return wunreachable code wunused exception parameter wunused macros wunused member function wunneeded internal declaration wimplicit int float conversion wanon enum enum conversion wassign enum wbitwise op parentheses wint in bool context wsometimes uninitialized wtautological bitwise compare wzero as null pointer constant weverything wno c compat pedantic wno c compat wno extensions wno conversion wno ctad maybe unsupported wno deprecated dynamic exception spec wno disabled macro expansion wno documentation unknown command wno double promotion wno exit time destructors wno float equal wno global constructors wno missing prototypes wno missing variable declarations wno nested anon types wno packed wno padded wno shift sign overflow wno sign conversion wno switch enum wno undefined func template wno unused template wno vla wno weak template vtables wno weak vtables g dndebug fno pie ld path usr bin ld lld rdynamic wl no undefined wl no pie src cmakefiles clickhouse malloc dir common malloc cpp o base base tests cmakefiles dump variable dir dump variable cpp o o base base tests dump variable src libclickhouse common io a contrib jemalloc cmake libjemalloc a src common stringutils libstring utils a base widechar width libwidechar width a base base libcommon a contrib poco cmake net ssl lib poco net ssl a contrib poco cmake net lib poco net a contrib poco cmake crypto lib poco crypto a contrib poco cmake util lib poco util a contrib poco cmake json lib poco json a contrib poco cmake json lib poco json pdjson a contrib poco cmake xml lib poco xml a contrib poco cmake xml lib poco xml expat a contrib replxx cmake libreplxx a contrib cctz cmake libcctz a wl whole archive opt softs clickhouse build contrib cctz cmake libtzdata a wl no whole archive contrib fmtlib cmake libfmt a contrib double conversion cmake libdouble conversion a contrib dragonbox cmake libdragonbox to chars a contrib a contrib st st a contrib libcpuid cmake libcpuid a contrib boost cmake lib boost program options a contrib boost cmake lib boost system a contrib libcityhash a contrib poco cmake foundation lib poco foundation a contrib zlib ng libz a contrib poco cmake foundation lib poco foundation pcre a contrib zstd cmake libzstd a contrib xz liblzma a contrib aws cmake libaws a contrib boringssl cmake libssl a contrib boringssl cmake libcrypto a lpthread contrib aws cmake libaws checksums a contrib brotli cmake libbrotli a contrib cmake a contrib cmake a wl start group base glibc compatibility libglibc compatibility a base glibc compatibility memcpy libmemcpy a contrib libcxx cmake libcxx a contrib libcxxabi cmake libcxxabi a contrib libunwind cmake libunwind a wl end group nodefaultlibs usr lib llvm lib clang lib linux libclang rt builtins a lc lm lrt lpthread ldl ld lld error undefined symbol pthread mutex lock referenced by threadfuzzer cpp src common threadfuzzer cpp threadfuzzer cpp o pthread mutex lock in archive src libclickhouse common io a did you mean pthread mutex lock glibc defined in lib linux gnu libc so ld lld error undefined symbol pthread mutex unlock referenced by threadfuzzer cpp src common threadfuzzer cpp threadfuzzer cpp o pthread mutex unlock in archive src libclickhouse common io a did you mean pthread mutex unlock glibc defined in lib linux gnu libc so clang error linker command failed with exit code use v to see invocation building cxx object utils keeper bench cmakefiles keeper bench dir runner cpp o ninja build stopped subcommand failed | 0 |
80,325 | 15,586,277,264 | IssuesEvent | 2021-03-18 01:34:28 | peterwkc85/Spock_Testing_Framework | https://api.github.com/repos/peterwkc85/Spock_Testing_Framework | opened | CVE-2019-14900 (Medium) detected in hibernate-core-4.3.10.Final.jar | security vulnerability | ## CVE-2019-14900 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hibernate-core-4.3.10.Final.jar</b></p></summary>
<p>The core O/RM functionality as provided by Hibernate</p>
<p>Library home page: <a href="http://hibernate.org">http://hibernate.org</a></p>
<p>Path to dependency file: Spock_Testing_Framework/java-testing-with-spock-master/java-testing-with-spock-master/chapter7/spring-standalone-swing/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/org/hibernate/hibernate-core/4.3.10.Final/hibernate-core-4.3.10.Final.jar,/root/.gradle/caches/modules-2/files-2.1/org.hibernate/hibernate-core/4.3.10.Final/6dbf5fe7a8cb307587ad4b4a97ae0933bba5e2a9/hibernate-core-4.3.10.Final.jar</p>
<p>
Dependency Hierarchy:
- hibernate-entitymanager-4.3.10.Final.jar (Root Library)
- :x: **hibernate-core-4.3.10.Final.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was found in Hibernate ORM in versions before 5.3.18, 5.4.18 and 5.5.0.Beta1. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SELECT or GROUP BY parts of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks.
<p>Publish Date: 2020-07-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14900>CVE-2019-14900</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: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14900">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14900</a></p>
<p>Release Date: 2020-07-06</p>
<p>Fix Resolution: org.hibernate:hibernate-core:5.4.18.Final</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-14900 (Medium) detected in hibernate-core-4.3.10.Final.jar - ## CVE-2019-14900 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hibernate-core-4.3.10.Final.jar</b></p></summary>
<p>The core O/RM functionality as provided by Hibernate</p>
<p>Library home page: <a href="http://hibernate.org">http://hibernate.org</a></p>
<p>Path to dependency file: Spock_Testing_Framework/java-testing-with-spock-master/java-testing-with-spock-master/chapter7/spring-standalone-swing/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/org/hibernate/hibernate-core/4.3.10.Final/hibernate-core-4.3.10.Final.jar,/root/.gradle/caches/modules-2/files-2.1/org.hibernate/hibernate-core/4.3.10.Final/6dbf5fe7a8cb307587ad4b4a97ae0933bba5e2a9/hibernate-core-4.3.10.Final.jar</p>
<p>
Dependency Hierarchy:
- hibernate-entitymanager-4.3.10.Final.jar (Root Library)
- :x: **hibernate-core-4.3.10.Final.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was found in Hibernate ORM in versions before 5.3.18, 5.4.18 and 5.5.0.Beta1. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SELECT or GROUP BY parts of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks.
<p>Publish Date: 2020-07-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14900>CVE-2019-14900</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: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14900">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14900</a></p>
<p>Release Date: 2020-07-06</p>
<p>Fix Resolution: org.hibernate:hibernate-core:5.4.18.Final</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_infrastructure | cve medium detected in hibernate core final jar cve medium severity vulnerability vulnerable library hibernate core final jar the core o rm functionality as provided by hibernate library home page a href path to dependency file spock testing framework java testing with spock master java testing with spock master spring standalone swing pom xml path to vulnerable library root repository org hibernate hibernate core final hibernate core final jar root gradle caches modules files org hibernate hibernate core final hibernate core final jar dependency hierarchy hibernate entitymanager final jar root library x hibernate core final jar vulnerable library vulnerability details a flaw was found in hibernate orm in versions before and a sql injection in the implementation of the jpa criteria api can permit unsanitized literals when a literal is used in the select or group by parts of the query this flaw could allow an attacker to access unauthorized information or possibly conduct further attacks publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org hibernate hibernate core final step up your open source security game with whitesource | 0 |
253,592 | 8,058,148,135 | IssuesEvent | 2018-08-02 17:32:35 | SparkDevNetwork/Rock | https://api.github.com/repos/SparkDevNetwork/Rock | closed | Registrant Email Not Updating in Event Registration | Priority: Critical Status: Available Status: Confirmed Type: Bug |
### Prerequisites
* [X] Put an X between the brackets on this line if you have done all of the following:
* Can you reproduce the problem on a fresh install or the [demo site](http://rock.rocksolidchurchdemo.com/)?
* Did you include your Rock version number and [client culture](https://github.com/SparkDevNetwork/Rock/wiki/Environment-and-Diagnostics-Information) setting?
* Did you [perform a cursory search](https://github.com/issues?q=is%3Aissue+user%3ASparkDevNetwork+-repo%3ASparkDevNetwork%2FSlack) to see if your bug or enhancement is already reported?
### Description
When registering for an event, if a person adds or changes an email address within registration, the change does not take effect in the database. This is in the registrant form, not the registered by form. We were testing with people that are logged in to our external website (or their family members).
### Steps to Reproduce
1. Register a person for an event.
2. Add or change an email address.
3. View person's profile to notice that the change was not made in the database.
**Expected behavior:**
We expect that the email will be automatically added or automatically changed based off of what was entered in registration.
**Actual behavior:**
The person is registered for the event, but the email address does not change in the database.
### Versions
* **Rock Version:** v7.3
* **Client Culture Setting:** en-US
| 1.0 | Registrant Email Not Updating in Event Registration -
### Prerequisites
* [X] Put an X between the brackets on this line if you have done all of the following:
* Can you reproduce the problem on a fresh install or the [demo site](http://rock.rocksolidchurchdemo.com/)?
* Did you include your Rock version number and [client culture](https://github.com/SparkDevNetwork/Rock/wiki/Environment-and-Diagnostics-Information) setting?
* Did you [perform a cursory search](https://github.com/issues?q=is%3Aissue+user%3ASparkDevNetwork+-repo%3ASparkDevNetwork%2FSlack) to see if your bug or enhancement is already reported?
### Description
When registering for an event, if a person adds or changes an email address within registration, the change does not take effect in the database. This is in the registrant form, not the registered by form. We were testing with people that are logged in to our external website (or their family members).
### Steps to Reproduce
1. Register a person for an event.
2. Add or change an email address.
3. View person's profile to notice that the change was not made in the database.
**Expected behavior:**
We expect that the email will be automatically added or automatically changed based off of what was entered in registration.
**Actual behavior:**
The person is registered for the event, but the email address does not change in the database.
### Versions
* **Rock Version:** v7.3
* **Client Culture Setting:** en-US
| non_infrastructure | registrant email not updating in event registration prerequisites put an x between the brackets on this line if you have done all of the following can you reproduce the problem on a fresh install or the did you include your rock version number and setting did you to see if your bug or enhancement is already reported description when registering for an event if a person adds or changes an email address within registration the change does not take effect in the database this is in the registrant form not the registered by form we were testing with people that are logged in to our external website or their family members steps to reproduce register a person for an event add or change an email address view person s profile to notice that the change was not made in the database expected behavior we expect that the email will be automatically added or automatically changed based off of what was entered in registration actual behavior the person is registered for the event but the email address does not change in the database versions rock version client culture setting en us | 0 |
17,805 | 12,598,136,619 | IssuesEvent | 2020-06-11 02:03:30 | niconoe/pyinaturalist | https://api.github.com/repos/niconoe/pyinaturalist | opened | Drop Python 3.4 | infrastructure | [Python 3.4 reached EOL in March 2019](https://devguide.python.org/devcycle/#end-of-life-branches). I'd like to drop this in the release after the next one (which would be `v0.11`).
Things to clean up/restrictions that would no longer apply:
- [ ] Remove from tests and classifiers
- [ ] Remove `typing` backport and use the stdlib version
- [ ] Remove `merge_two_dicts()` and use `{**dict, **dict}` and other [PEP 448](https://www.python.org/dev/peps/pep-0448/) syntax
- [ ] Use latest pytest (>=4.7)
- [ ] Use latest tox (>=3.15) | 1.0 | Drop Python 3.4 - [Python 3.4 reached EOL in March 2019](https://devguide.python.org/devcycle/#end-of-life-branches). I'd like to drop this in the release after the next one (which would be `v0.11`).
Things to clean up/restrictions that would no longer apply:
- [ ] Remove from tests and classifiers
- [ ] Remove `typing` backport and use the stdlib version
- [ ] Remove `merge_two_dicts()` and use `{**dict, **dict}` and other [PEP 448](https://www.python.org/dev/peps/pep-0448/) syntax
- [ ] Use latest pytest (>=4.7)
- [ ] Use latest tox (>=3.15) | infrastructure | drop python i d like to drop this in the release after the next one which would be things to clean up restrictions that would no longer apply remove from tests and classifiers remove typing backport and use the stdlib version remove merge two dicts and use dict dict and other syntax use latest pytest use latest tox | 1 |
14,675 | 11,046,739,381 | IssuesEvent | 2019-12-09 17:26:55 | algorand/go-algorand | https://api.github.com/repos/algorand/go-algorand | closed | ensure deb/rpm upgrades work | 2 infrastructure | ## Upgradable rpm installers
Our last release had some bumps in the generation of the rpm installers.
We need to figure out what need to be changed to support upgradable installers and integrate that into our scripts. | 1.0 | ensure deb/rpm upgrades work - ## Upgradable rpm installers
Our last release had some bumps in the generation of the rpm installers.
We need to figure out what need to be changed to support upgradable installers and integrate that into our scripts. | infrastructure | ensure deb rpm upgrades work upgradable rpm installers our last release had some bumps in the generation of the rpm installers we need to figure out what need to be changed to support upgradable installers and integrate that into our scripts | 1 |
594,340 | 18,043,401,013 | IssuesEvent | 2021-09-18 12:54:58 | hummingbird-jp/stat-web | https://api.github.com/repos/hummingbird-jp/stat-web | closed | Privacy policy and terms of service are hiding | bug priority: gold | **Describe the bug**
These are unnecessary after joining a meeting.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to Stat!
**Expected behavior**
These are unnecessary after joining a meeting.
**Screenshots**
**Additional context**
N/A. | 1.0 | Privacy policy and terms of service are hiding - **Describe the bug**
These are unnecessary after joining a meeting.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to Stat!
**Expected behavior**
These are unnecessary after joining a meeting.
**Screenshots**
**Additional context**
N/A. | non_infrastructure | privacy policy and terms of service are hiding describe the bug these are unnecessary after joining a meeting to reproduce steps to reproduce the behavior go to stat expected behavior these are unnecessary after joining a meeting screenshots additional context n a | 0 |
335,363 | 24,465,736,727 | IssuesEvent | 2022-10-07 14:51:55 | dhis2/hacktoberfest | https://api.github.com/repos/dhis2/hacktoberfest | opened | Add Algolia Search to UI Library Documentation | documentation hacktoberfest javascript react algolia | The UI Library Documentation runs on Docusaurus, it needs the same documentation setup as the developer portal documentation, including the same public key (as they will share the same index)
UI Library Repository: https://github.com/dhis2/ui
Developer Portal Config Reference: https://github.com/dhis2/developer-portal/blob/main/docusaurus.config.js#L96 | 1.0 | Add Algolia Search to UI Library Documentation - The UI Library Documentation runs on Docusaurus, it needs the same documentation setup as the developer portal documentation, including the same public key (as they will share the same index)
UI Library Repository: https://github.com/dhis2/ui
Developer Portal Config Reference: https://github.com/dhis2/developer-portal/blob/main/docusaurus.config.js#L96 | non_infrastructure | add algolia search to ui library documentation the ui library documentation runs on docusaurus it needs the same documentation setup as the developer portal documentation including the same public key as they will share the same index ui library repository developer portal config reference | 0 |
40,314 | 5,285,852,064 | IssuesEvent | 2017-02-08 07:04:41 | kakazuo/yimengtech | https://api.github.com/repos/kakazuo/yimengtech | opened | 测试明细导入显示成本列问题 | test 测试任务 翡翠厂 重庆 | 1、添加公司参数：07320 明细导入页面是否显示成本列 0-不允许，1-允许
一开始值为0-不允许：
页面显示结果：
2、修改公司参数值为1-允许：
| 1.0 | 测试明细导入显示成本列问题 - 1、添加公司参数：07320 明细导入页面是否显示成本列 0-不允许，1-允许
一开始值为0-不允许：
页面显示结果：
2、修改公司参数值为1-允许：
| non_infrastructure | 测试明细导入显示成本列问题 、添加公司参数： 明细导入页面是否显示成本列 不允许， 允许 不允许： 页面显示结果： 、 允许： | 0 |
3,251 | 12,401,598,111 | IssuesEvent | 2020-05-21 10:11:31 | permon/permon | https://api.github.com/repos/permon/permon | opened | make use of PETSc MATPRODUCT | enhancement maintainability | We should abandon our own implementation in favor of PETSc one, which seems to be under intensive development now (https://gitlab.com/petsc/petsc/-/merge_requests/2800).
If there is anything useful on our side, it should be contributed to PETSc. | True | make use of PETSc MATPRODUCT - We should abandon our own implementation in favor of PETSc one, which seems to be under intensive development now (https://gitlab.com/petsc/petsc/-/merge_requests/2800).
If there is anything useful on our side, it should be contributed to PETSc. | non_infrastructure | make use of petsc matproduct we should abandon our own implementation in favor of petsc one which seems to be under intensive development now if there is anything useful on our side it should be contributed to petsc | 0 |
742,918 | 25,878,190,044 | IssuesEvent | 2022-12-14 09:26:41 | NomicFoundation/hardhat | https://api.github.com/repos/NomicFoundation/hardhat | closed | hardhat-solhint dependency is outdated | type:chore package:hardhat-solhint priority:medium | Required `solhint` version is `^2.0.0`, but `3.x.x` has been released. | 1.0 | hardhat-solhint dependency is outdated - Required `solhint` version is `^2.0.0`, but `3.x.x` has been released. | non_infrastructure | hardhat solhint dependency is outdated required solhint version is but x x has been released | 0 |
26,275 | 19,900,096,202 | IssuesEvent | 2022-01-25 06:38:54 | GoogleForCreators/web-stories-wp | https://api.github.com/repos/GoogleForCreators/web-stories-wp | closed | Initial thumbnails disappear in storybook local media library pane | Type: Bug Type: Infrastructure Pod: WP & Infra |
## Bug Description
All initial thumbnails on the local media library pane disappeared on [storybook](http://localhost:50045/?path=/story/playground-stories-editor--default) recently however when you scroll down all media at the bottom do show up.
## Expected Behaviour
<!-- Please describe clearly and concisely what the expected behaviour should be. -->
## Steps to Reproduce
<!-- Please provide detailed steps on how to reproduce the bug. -->
## Screenshots
## Additional Context
<!-- Please complete the following information. -->
- Plugin Version: 1.17.0-alpha.0
- WordPress Version: 5.8.3
- Operating System: Mac OS
- Browser: Chrome, Safari
| 1.0 | Initial thumbnails disappear in storybook local media library pane -
## Bug Description
All initial thumbnails on the local media library pane disappeared on [storybook](http://localhost:50045/?path=/story/playground-stories-editor--default) recently however when you scroll down all media at the bottom do show up.
## Expected Behaviour
<!-- Please describe clearly and concisely what the expected behaviour should be. -->
## Steps to Reproduce
<!-- Please provide detailed steps on how to reproduce the bug. -->
## Screenshots
## Additional Context
<!-- Please complete the following information. -->
- Plugin Version: 1.17.0-alpha.0
- WordPress Version: 5.8.3
- Operating System: Mac OS
- Browser: Chrome, Safari
| infrastructure | initial thumbnails disappear in storybook local media library pane bug description all initial thumbnails on the local media library pane disappeared on recently however when you scroll down all media at the bottom do show up expected behaviour steps to reproduce screenshots additional context plugin version alpha wordpress version operating system mac os browser chrome safari | 1 |
30,151 | 24,587,466,416 | IssuesEvent | 2022-10-13 21:10:04 | microsoft/WindowsAppSDK | https://api.github.com/repos/microsoft/WindowsAppSDK | closed | Payload contains two deps.json | area-Infrastructure | ### Describe the bug
See [EF core github issue 27576](https://github.com/dotnet/efcore/issues/27576). The EF Core team has identified that this is a WinUI issue.
I am using Microsoft.EntityFrameworkCore and Microsoft.EntityFrameworkCore.Sqlite.
My Microsoft.WindowsAppSDK app consists of a packaged app and two libraries using WinUI 3.
It compiles fine using VS 2022 Community 17.1.0
But then when I add Microsoft.EntityFrameworkCore.Design, I get this compile error:
Error APPX1101 Payload contains two or more files with the same destination path 'App.deps.json'. Source files:
C:\Users[...]\App\obj\x64\Debug\net6.0-windows10.0.19041.0\win10-x64\App.deps.json
C:\Users[...]\App\bin\x64\Debug\net6.0-windows10.0.19041.0\win10-x64\App.deps.json
This happens with EFCore version 6.0.0 and 6.0.2.
### Steps to reproduce the bug
Steps to reproduce.
1. Install the configuration shown below and create a solution called Test with a single project called Test, using the project template "Blank App, Packaged (WinUI 3 in Desktop)".
2. Add references for Microsoft.EntityFrameworkCore 6.0.0 and Microsoft.EntityFrameworkCore.Sqlite 6.0.0
3. Add the code shown below.
4. Compile and run
5. Add a reference for Microsoft.EntityFrameworkCore.Design 6.0.0
6. Compile and observe the error.
Code
```
namespace Test
{
public sealed partial class MainWindow : Window
{
public MainWindow()
{
this.InitializeComponent();
}
private void MyButton_Click(object sender, RoutedEventArgs e)
{
myButton.Content = "Clicking...";
BloggingContext bc = new BloggingContext();
bc.Database.EnsureCreated();
bc.Dispose();
myButton.Content = "Clicked";
}
}
public class BloggingContext : DbContext
{
public DbSet<Blog> Blogs { get; set; }
public DbSet<Post> Posts { get; set; }
public string DbPath { get; }
public BloggingContext()
{
//string path = Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData);
string path = Environment.GetFolderPath(Environment.SpecialFolder.MyDocuments);
Debug.WriteLine($"path: {path}");
this.DbPath = System.IO.Path.Join(path, "blogging.db");
}
// The following configures EF to create a Sqlite database file in the
// special "local" folder for your platform.
protected override void OnConfiguring(DbContextOptionsBuilder options)
{
options.UseSqlite($"Data Source={this.DbPath}");
}
}
public class Blog
{
public int BlogId { get; set; }
public string Url { get; set; }
public List<Post> Posts { get; } = new();
}
public class Post
{
public int PostId { get; set; }
public string Title { get; set; }
public string Content { get; set; }
public int BlogId { get; set; }
public Blog Blog { get; set; }
}
}
```
Configuration
```
Microsoft Visual Studio Community 2022
Version 17.1.0
VisualStudio.17.Release/17.1.0+32210.238
Microsoft .NET Framework
Version 4.8.04084
Installed Version: Community
Visual C++ 2022 00482-90000-00000-AA995
Microsoft Visual C++ 2022
ASP.NET and Web Tools 2019 17.1.358.51495
ASP.NET and Web Tools 2019
Azure App Service Tools v3.0.0 17.1.358.51495
Azure App Service Tools v3.0.0
C# Tools 4.1.0-5.22109.6+0c82c4114a4e4b8b723b915eee3b13261db6717f
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Common Azure Tools 1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
Microsoft JVM Debugger 1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines
Microsoft MI-Based Debugger 1.0
Provides support for connecting Visual Studio to MI compatible debuggers
Microsoft Visual C++ Wizards 1.0
Microsoft Visual C++ Wizards
Microsoft Visual Studio VC Package 1.0
Microsoft Visual Studio VC Package
NuGet Package Manager 6.1.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/
TypeScript Tools 17.0.1229.2001
TypeScript Tools for Microsoft Visual Studio
Visual Basic Tools 4.1.0-5.22109.6+0c82c4114a4e4b8b723b915eee3b13261db6717f
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Visual F# Tools 17.1.0-beta.21610.4+07b5673e4f2fa7630e78abe37f16b372353a7242
Microsoft Visual F# Tools
Visual Studio Code Debug Adapter Host Package 1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio
Visual Studio IntelliCode 2.2
AI-assisted development for Visual Studio.
```
### Expected behavior
Expected no error on compile.
### Screenshots
_No response_
### NuGet package version
_No response_
### Windows app type
- [ ] UWP
- [ ] Win32
### Device form factor
_No response_
### Windows version
_No response_
### Additional context
_No response_ | 1.0 | Payload contains two deps.json - ### Describe the bug
See [EF core github issue 27576](https://github.com/dotnet/efcore/issues/27576). The EF Core team has identified that this is a WinUI issue.
I am using Microsoft.EntityFrameworkCore and Microsoft.EntityFrameworkCore.Sqlite.
My Microsoft.WindowsAppSDK app consists of a packaged app and two libraries using WinUI 3.
It compiles fine using VS 2022 Community 17.1.0
But then when I add Microsoft.EntityFrameworkCore.Design, I get this compile error:
Error APPX1101 Payload contains two or more files with the same destination path 'App.deps.json'. Source files:
C:\Users[...]\App\obj\x64\Debug\net6.0-windows10.0.19041.0\win10-x64\App.deps.json
C:\Users[...]\App\bin\x64\Debug\net6.0-windows10.0.19041.0\win10-x64\App.deps.json
This happens with EFCore version 6.0.0 and 6.0.2.
### Steps to reproduce the bug
Steps to reproduce.
1. Install the configuration shown below and create a solution called Test with a single project called Test, using the project template "Blank App, Packaged (WinUI 3 in Desktop)".
2. Add references for Microsoft.EntityFrameworkCore 6.0.0 and Microsoft.EntityFrameworkCore.Sqlite 6.0.0
3. Add the code shown below.
4. Compile and run
5. Add a reference for Microsoft.EntityFrameworkCore.Design 6.0.0
6. Compile and observe the error.
Code
```
namespace Test
{
public sealed partial class MainWindow : Window
{
public MainWindow()
{
this.InitializeComponent();
}
private void MyButton_Click(object sender, RoutedEventArgs e)
{
myButton.Content = "Clicking...";
BloggingContext bc = new BloggingContext();
bc.Database.EnsureCreated();
bc.Dispose();
myButton.Content = "Clicked";
}
}
public class BloggingContext : DbContext
{
public DbSet<Blog> Blogs { get; set; }
public DbSet<Post> Posts { get; set; }
public string DbPath { get; }
public BloggingContext()
{
//string path = Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData);
string path = Environment.GetFolderPath(Environment.SpecialFolder.MyDocuments);
Debug.WriteLine($"path: {path}");
this.DbPath = System.IO.Path.Join(path, "blogging.db");
}
// The following configures EF to create a Sqlite database file in the
// special "local" folder for your platform.
protected override void OnConfiguring(DbContextOptionsBuilder options)
{
options.UseSqlite($"Data Source={this.DbPath}");
}
}
public class Blog
{
public int BlogId { get; set; }
public string Url { get; set; }
public List<Post> Posts { get; } = new();
}
public class Post
{
public int PostId { get; set; }
public string Title { get; set; }
public string Content { get; set; }
public int BlogId { get; set; }
public Blog Blog { get; set; }
}
}
```
Configuration
```
Microsoft Visual Studio Community 2022
Version 17.1.0
VisualStudio.17.Release/17.1.0+32210.238
Microsoft .NET Framework
Version 4.8.04084
Installed Version: Community
Visual C++ 2022 00482-90000-00000-AA995
Microsoft Visual C++ 2022
ASP.NET and Web Tools 2019 17.1.358.51495
ASP.NET and Web Tools 2019
Azure App Service Tools v3.0.0 17.1.358.51495
Azure App Service Tools v3.0.0
C# Tools 4.1.0-5.22109.6+0c82c4114a4e4b8b723b915eee3b13261db6717f
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Common Azure Tools 1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
Microsoft JVM Debugger 1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines
Microsoft MI-Based Debugger 1.0
Provides support for connecting Visual Studio to MI compatible debuggers
Microsoft Visual C++ Wizards 1.0
Microsoft Visual C++ Wizards
Microsoft Visual Studio VC Package 1.0
Microsoft Visual Studio VC Package
NuGet Package Manager 6.1.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/
TypeScript Tools 17.0.1229.2001
TypeScript Tools for Microsoft Visual Studio
Visual Basic Tools 4.1.0-5.22109.6+0c82c4114a4e4b8b723b915eee3b13261db6717f
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Visual F# Tools 17.1.0-beta.21610.4+07b5673e4f2fa7630e78abe37f16b372353a7242
Microsoft Visual F# Tools
Visual Studio Code Debug Adapter Host Package 1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio
Visual Studio IntelliCode 2.2
AI-assisted development for Visual Studio.
```
### Expected behavior
Expected no error on compile.
### Screenshots
_No response_
### NuGet package version
_No response_
### Windows app type
- [ ] UWP
- [ ] Win32
### Device form factor
_No response_
### Windows version
_No response_
### Additional context
_No response_ | infrastructure | payload contains two deps json describe the bug see the ef core team has identified that this is a winui issue i am using microsoft entityframeworkcore and microsoft entityframeworkcore sqlite my microsoft windowsappsdk app consists of a packaged app and two libraries using winui it compiles fine using vs community but then when i add microsoft entityframeworkcore design i get this compile error error payload contains two or more files with the same destination path app deps json source files c users app obj debug app deps json c users app bin debug app deps json this happens with efcore version and steps to reproduce the bug steps to reproduce install the configuration shown below and create a solution called test with a single project called test using the project template blank app packaged winui in desktop add references for microsoft entityframeworkcore and microsoft entityframeworkcore sqlite add the code shown below compile and run add a reference for microsoft entityframeworkcore design compile and observe the error code namespace test public sealed partial class mainwindow window public mainwindow this initializecomponent private void mybutton click object sender routedeventargs e mybutton content clicking bloggingcontext bc new bloggingcontext bc database ensurecreated bc dispose mybutton content clicked public class bloggingcontext dbcontext public dbset blogs get set public dbset posts get set public string dbpath get public bloggingcontext string path environment getfolderpath environment specialfolder localapplicationdata string path environment getfolderpath environment specialfolder mydocuments debug writeline path path this dbpath system io path join path blogging db the following configures ef to create a sqlite database file in the special local folder for your platform protected override void onconfiguring dbcontextoptionsbuilder options options usesqlite data source this dbpath public class blog public int blogid get set public string url get set public list posts get new public class post public int postid get set public string title get set public string content get set public int blogid get set public blog blog get set configuration microsoft visual studio community version visualstudio release microsoft net framework version installed version community visual c microsoft visual c asp net and web tools asp net and web tools azure app service tools azure app service tools c tools c components used in the ide depending on your project type and settings a different version of the compiler may be used common azure tools provides common services for use by azure mobile services and microsoft azure tools microsoft jvm debugger provides support for connecting the visual studio debugger to jdwp compatible java virtual machines microsoft mi based debugger provides support for connecting visual studio to mi compatible debuggers microsoft visual c wizards microsoft visual c wizards microsoft visual studio vc package microsoft visual studio vc package nuget package manager nuget package manager in visual studio for more information about nuget visit typescript tools typescript tools for microsoft visual studio visual basic tools visual basic components used in the ide depending on your project type and settings a different version of the compiler may be used visual f tools beta microsoft visual f tools visual studio code debug adapter host package interop layer for hosting visual studio code debug adapters in visual studio visual studio intellicode ai assisted development for visual studio expected behavior expected no error on compile screenshots no response nuget package version no response windows app type uwp device form factor no response windows version no response additional context no response | 1 |
14,746 | 11,100,406,554 | IssuesEvent | 2019-12-16 19:08:06 | E3SM-Project/scream | https://api.github.com/repos/E3SM-Project/scream | closed | Make e3sm build with scream instead of cam | cmake infrastructure | We added a dummy `atm_mct.F90` file for mct to "build". Now we need to make cime/cmake machinery know how to build scream as atm component, instead of cam. | 1.0 | Make e3sm build with scream instead of cam - We added a dummy `atm_mct.F90` file for mct to "build". Now we need to make cime/cmake machinery know how to build scream as atm component, instead of cam. | infrastructure | make build with scream instead of cam we added a dummy atm mct file for mct to build now we need to make cime cmake machinery know how to build scream as atm component instead of cam | 1 |
15,105 | 3,925,039,509 | IssuesEvent | 2016-04-22 17:24:22 | RocketChat/Rocket.Chat | https://api.github.com/repos/RocketChat/Rocket.Chat | closed | check_mk notifications within RocketChat | type: documentation | Hi we liked to have an check_mk integration within Rocket.Chat. So we got our monitoring frontend within Rocket. So we build one based on an Bashscript.
So we did it: https://github.com/Againstreality/Rocket.Chat.check_mk-integration
You can use it if you want.
| 1.0 | check_mk notifications within RocketChat - Hi we liked to have an check_mk integration within Rocket.Chat. So we got our monitoring frontend within Rocket. So we build one based on an Bashscript.
So we did it: https://github.com/Againstreality/Rocket.Chat.check_mk-integration
You can use it if you want.
| non_infrastructure | check mk notifications within rocketchat hi we liked to have an check mk integration within rocket chat so we got our monitoring frontend within rocket so we build one based on an bashscript so we did it you can use it if you want | 0 |
88,738 | 3,785,017,698 | IssuesEvent | 2016-03-20 07:14:34 | Vannevelj/VSDiagnostics | https://api.github.com/repos/Vannevelj/VSDiagnostics | closed | Remove string checks | priority - high type - Improvement | These are brittle. We should check that they actually reference the members in question.
This refers to the implementation of https://github.com/Vannevelj/VSDiagnostics/blob/0ab29a302e74a8ce0e7309af4b0e0499d7ed6a91/VSDiagnostics/VSDiagnostics/VSDiagnostics/Diagnostics/General/SwitchDoesNotHandleAllEnumOptions/SwitchDoesNotHandleAllEnumOptionsAnalyzer.cs | 1.0 | Remove string checks - These are brittle. We should check that they actually reference the members in question.
This refers to the implementation of https://github.com/Vannevelj/VSDiagnostics/blob/0ab29a302e74a8ce0e7309af4b0e0499d7ed6a91/VSDiagnostics/VSDiagnostics/VSDiagnostics/Diagnostics/General/SwitchDoesNotHandleAllEnumOptions/SwitchDoesNotHandleAllEnumOptionsAnalyzer.cs | non_infrastructure | remove string checks these are brittle we should check that they actually reference the members in question this refers to the implementation of | 0 |
591,782 | 17,861,263,043 | IssuesEvent | 2021-09-06 01:02:06 | shoepro/server | https://api.github.com/repos/shoepro/server | closed | [Chore]: Delete user test | 0.5h Server Chore Priority: Middle | ### ISSUE
- Group: `Server`
- Type: `Chore`
- Time: `0.5h`
- Priority: `Middle`
### TODO
1. [x] Delete user.test.ts file | 1.0 | [Chore]: Delete user test - ### ISSUE
- Group: `Server`
- Type: `Chore`
- Time: `0.5h`
- Priority: `Middle`
### TODO
1. [x] Delete user.test.ts file | non_infrastructure | delete user test issue group server type chore time priority middle todo delete user test ts file | 0 |
462,614 | 13,250,202,030 | IssuesEvent | 2020-08-19 22:24:04 | clowdr-app/clowdr-web-app | https://api.github.com/repos/clowdr-app/clowdr-web-app | opened | The list of Users when adding to a chat room shows No Data initially | Bug Medium priority | The first time I click Add People and then click in the Users box, the list that pops up shows No Data. If I start typing, the users appear, and if I bring up the dialog again it works fine.
| 1.0 | The list of Users when adding to a chat room shows No Data initially - The first time I click Add People and then click in the Users box, the list that pops up shows No Data. If I start typing, the users appear, and if I bring up the dialog again it works fine.
| non_infrastructure | the list of users when adding to a chat room shows no data initially the first time i click add people and then click in the users box the list that pops up shows no data if i start typing the users appear and if i bring up the dialog again it works fine | 0 |
282,676 | 8,709,545,927 | IssuesEvent | 2018-12-06 14:15:58 | NREL/EnergyPlus | https://api.github.com/repos/NREL/EnergyPlus | closed | SetpointsNotMetWithTemperaturesMonthly table report all zeros unless the corresponding output:variable objects are added to the idf | PriorityLow SeverityLow | Issue overview
--------------
User noted that output for the SetpointsNotMetWithTemperaturesMonthly and ComfortReportSimple55Monthly were all zero, but the summary at the end of ABUPS was not.
### Workaround
Add the corresponding output:variable objects (any reporting frequency will work).
```
Output:Variable,*,Zone Thermal Comfort ASHRAE 55 Simple Model Summer Clothes Not Comfortable Time,annual; !- Zone Sum [hr]
Output:Variable,*,Zone Thermal Comfort ASHRAE 55 Simple Model Winter Clothes Not Comfortable Time,annual; !- Zone Sum [hr]
Output:Variable,*,Zone Thermal Comfort ASHRAE 55 Simple Model Summer or Winter Clothes Not Comfortable Time,annual; !- Zone Sum [hr]
Output:Variable,*,Zone Heating Setpoint Not Met Time,annual; !- Zone Sum [hr]
Output:Variable,*,Zone Heating Setpoint Not Met While Occupied Time,annual; !- Zone Sum [hr]
Output:Variable,*,Zone Cooling Setpoint Not Met Time,annual; !- Zone Sum [hr]
Output:Variable,*,Zone Cooling Setpoint Not Met While Occupied Time,annual; !- Zone Sum [hr]
```
### Details
Some additional details for this issue (if relevant):
- Platform Win64
- Version of EnergyPlus 9.0.1
- Helpdesk ticket number 13082.
### Checklist
Add to this list or remove from it as applicable. This is a simple templated set of guidelines.
- [x] Defect file added EnergyPlusDevSupport\DefectFiles
- [x] Ticket added to Pivotal for defect (development team task)
- [x] Pull request created (the pull request will have additional tasks related to reviewing changes that fix this defect)
| 1.0 | SetpointsNotMetWithTemperaturesMonthly table report all zeros unless the corresponding output:variable objects are added to the idf - Issue overview
--------------
User noted that output for the SetpointsNotMetWithTemperaturesMonthly and ComfortReportSimple55Monthly were all zero, but the summary at the end of ABUPS was not.
### Workaround
Add the corresponding output:variable objects (any reporting frequency will work).
```
Output:Variable,*,Zone Thermal Comfort ASHRAE 55 Simple Model Summer Clothes Not Comfortable Time,annual; !- Zone Sum [hr]
Output:Variable,*,Zone Thermal Comfort ASHRAE 55 Simple Model Winter Clothes Not Comfortable Time,annual; !- Zone Sum [hr]
Output:Variable,*,Zone Thermal Comfort ASHRAE 55 Simple Model Summer or Winter Clothes Not Comfortable Time,annual; !- Zone Sum [hr]
Output:Variable,*,Zone Heating Setpoint Not Met Time,annual; !- Zone Sum [hr]
Output:Variable,*,Zone Heating Setpoint Not Met While Occupied Time,annual; !- Zone Sum [hr]
Output:Variable,*,Zone Cooling Setpoint Not Met Time,annual; !- Zone Sum [hr]
Output:Variable,*,Zone Cooling Setpoint Not Met While Occupied Time,annual; !- Zone Sum [hr]
```
### Details
Some additional details for this issue (if relevant):
- Platform Win64
- Version of EnergyPlus 9.0.1
- Helpdesk ticket number 13082.
### Checklist
Add to this list or remove from it as applicable. This is a simple templated set of guidelines.
- [x] Defect file added EnergyPlusDevSupport\DefectFiles
- [x] Ticket added to Pivotal for defect (development team task)
- [x] Pull request created (the pull request will have additional tasks related to reviewing changes that fix this defect)
| non_infrastructure | setpointsnotmetwithtemperaturesmonthly table report all zeros unless the corresponding output variable objects are added to the idf issue overview user noted that output for the setpointsnotmetwithtemperaturesmonthly and were all zero but the summary at the end of abups was not workaround add the corresponding output variable objects any reporting frequency will work output variable zone thermal comfort ashrae simple model summer clothes not comfortable time annual zone sum output variable zone thermal comfort ashrae simple model winter clothes not comfortable time annual zone sum output variable zone thermal comfort ashrae simple model summer or winter clothes not comfortable time annual zone sum output variable zone heating setpoint not met time annual zone sum output variable zone heating setpoint not met while occupied time annual zone sum output variable zone cooling setpoint not met time annual zone sum output variable zone cooling setpoint not met while occupied time annual zone sum details some additional details for this issue if relevant platform version of energyplus helpdesk ticket number checklist add to this list or remove from it as applicable this is a simple templated set of guidelines defect file added energyplusdevsupport defectfiles ticket added to pivotal for defect development team task pull request created the pull request will have additional tasks related to reviewing changes that fix this defect | 0 |
629,129 | 20,024,134,643 | IssuesEvent | 2022-02-01 19:20:19 | EdricChan03/StudyBuddy-android | https://api.github.com/repos/EdricChan03/StudyBuddy-android | closed | Migrate to Coil | enhancement :star: priority: non-critical in progress has pr | # Overview
Migrating to [Coil](https://coil-kt.github.io/coil/) (Coroutines Image Loader) would leverage upon Kotlin Coroutines and handy extension functions, unlike existing libraries like [Glide](https://bumptech.github.io/glide/) which use a global `Glide` class.
## Resources
- [Android Developers Backstage #152: Image Loading with Coil](https://adbackstage.libsyn.com/episode-152-image-loading-with-coil)
- [Coil Docs: Migrating from Glide/Picasso to Coil](https://coil-kt.github.io/coil/migrating/) | 1.0 | Migrate to Coil - # Overview
Migrating to [Coil](https://coil-kt.github.io/coil/) (Coroutines Image Loader) would leverage upon Kotlin Coroutines and handy extension functions, unlike existing libraries like [Glide](https://bumptech.github.io/glide/) which use a global `Glide` class.
## Resources
- [Android Developers Backstage #152: Image Loading with Coil](https://adbackstage.libsyn.com/episode-152-image-loading-with-coil)
- [Coil Docs: Migrating from Glide/Picasso to Coil](https://coil-kt.github.io/coil/migrating/) | non_infrastructure | migrate to coil overview migrating to coroutines image loader would leverage upon kotlin coroutines and handy extension functions unlike existing libraries like which use a global glide class resources | 0 |
8,913 | 7,733,091,535 | IssuesEvent | 2018-05-26 07:00:39 | liamross/psiagram | https://api.github.com/repos/liamross/psiagram | closed | Convert to webpack? | 🏗 infrastructure 🙅wontfix | Converting to webpack 4 would allow the same non-config as Parcel but with the ability to add more configurations. Should give it a try?
https://www.valentinog.com/blog/webpack-4-tutorial/#webpack_4_as_a_zero_configuration_module_bundler
This tutorial gives a good incremental approach to adding config | 1.0 | Convert to webpack? - Converting to webpack 4 would allow the same non-config as Parcel but with the ability to add more configurations. Should give it a try?
https://www.valentinog.com/blog/webpack-4-tutorial/#webpack_4_as_a_zero_configuration_module_bundler
This tutorial gives a good incremental approach to adding config | infrastructure | convert to webpack converting to webpack would allow the same non config as parcel but with the ability to add more configurations should give it a try this tutorial gives a good incremental approach to adding config | 1 |
86,489 | 8,037,604,496 | IssuesEvent | 2018-07-30 13:11:01 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | roachtest: scaledata/distributed_semaphore/nodes=3 failed on master | C-test-failure O-robot | SHA: https://github.com/cockroachdb/cockroach/commits/4f21f583432bef4e5f9d634854248b835945d059
Parameters:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=803679&tab=buildLog
```
test.go:494,cluster.go:676,scaledata.go:81,scaledata.go:54: /home/agent/work/.go/bin/roachprod put teamcity-803679-scaledata-distributed-semaphore-nodes-3:1-3 /home/agent/work/.go/src/github.com/cockroachdb/cockroach/cockroach.linux-2.6.32-gnu-amd64 ./cockroach: exit status 1
``` | 1.0 | roachtest: scaledata/distributed_semaphore/nodes=3 failed on master - SHA: https://github.com/cockroachdb/cockroach/commits/4f21f583432bef4e5f9d634854248b835945d059
Parameters:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=803679&tab=buildLog
```
test.go:494,cluster.go:676,scaledata.go:81,scaledata.go:54: /home/agent/work/.go/bin/roachprod put teamcity-803679-scaledata-distributed-semaphore-nodes-3:1-3 /home/agent/work/.go/src/github.com/cockroachdb/cockroach/cockroach.linux-2.6.32-gnu-amd64 ./cockroach: exit status 1
``` | non_infrastructure | roachtest scaledata distributed semaphore nodes failed on master sha parameters failed test test go cluster go scaledata go scaledata go home agent work go bin roachprod put teamcity scaledata distributed semaphore nodes home agent work go src github com cockroachdb cockroach cockroach linux gnu cockroach exit status | 0 |
57,018 | 14,100,572,157 | IssuesEvent | 2020-11-06 04:35:05 | renfei/WinterEE | https://api.github.com/repos/renfei/WinterEE | opened | CVE-2012-5783 (Medium) detected in commons-httpclient-3.1.jar | security vulnerability | ## CVE-2012-5783 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>commons-httpclient-3.1.jar</b></p></summary>
<p>The HttpClient component supports the client-side of RFC 1945 (HTTP/1.0) and RFC 2616 (HTTP/1.1) , several related specifications (RFC 2109 (Cookies) , RFC 2617 (HTTP Authentication) , etc.), and provides a framework by which new request types (methods) or HTTP extensions can be created easily.</p>
<p>Library home page: <a href="https://hc.apache.org/httpcomponents-client-ga/">https://hc.apache.org/httpcomponents-client-ga/</a></p>
<p>Path to dependency file: WinterEE/WinterEE-Eureka-Serve/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar,/home/wss-scanner/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar,/home/wss-scanner/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar,/home/wss-scanner/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar,/home/wss-scanner/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar,/home/wss-scanner/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar,/home/wss-scanner/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar</p>
<p>
Dependency Hierarchy:
- jacoco-maven-plugin-0.8.6.jar (Root Library)
- maven-reporting-impl-2.1.jar
- doxia-core-1.1.2.jar
- :x: **commons-httpclient-3.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/renfei/WinterEE/commit/9d57f3481f4a0f678edb6631b7924d697b67b48b">9d57f3481f4a0f678edb6631b7924d697b67b48b</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>
Apache Commons HttpClient 3.x, as used in Amazon Flexible Payments Service (FPS) merchant Java SDK and other products, does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.
<p>Publish Date: 2012-11-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-5783>CVE-2012-5783</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.8</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://exchange.xforce.ibmcloud.com/vulnerabilities/79984">https://exchange.xforce.ibmcloud.com/vulnerabilities/79984</a></p>
<p>Fix Resolution: Apply the appropriate patch for your system. See References.</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-2012-5783 (Medium) detected in commons-httpclient-3.1.jar - ## CVE-2012-5783 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>commons-httpclient-3.1.jar</b></p></summary>
<p>The HttpClient component supports the client-side of RFC 1945 (HTTP/1.0) and RFC 2616 (HTTP/1.1) , several related specifications (RFC 2109 (Cookies) , RFC 2617 (HTTP Authentication) , etc.), and provides a framework by which new request types (methods) or HTTP extensions can be created easily.</p>
<p>Library home page: <a href="https://hc.apache.org/httpcomponents-client-ga/">https://hc.apache.org/httpcomponents-client-ga/</a></p>
<p>Path to dependency file: WinterEE/WinterEE-Eureka-Serve/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar,/home/wss-scanner/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar,/home/wss-scanner/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar,/home/wss-scanner/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar,/home/wss-scanner/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar,/home/wss-scanner/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar,/home/wss-scanner/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar</p>
<p>
Dependency Hierarchy:
- jacoco-maven-plugin-0.8.6.jar (Root Library)
- maven-reporting-impl-2.1.jar
- doxia-core-1.1.2.jar
- :x: **commons-httpclient-3.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/renfei/WinterEE/commit/9d57f3481f4a0f678edb6631b7924d697b67b48b">9d57f3481f4a0f678edb6631b7924d697b67b48b</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>
Apache Commons HttpClient 3.x, as used in Amazon Flexible Payments Service (FPS) merchant Java SDK and other products, does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.
<p>Publish Date: 2012-11-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-5783>CVE-2012-5783</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.8</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://exchange.xforce.ibmcloud.com/vulnerabilities/79984">https://exchange.xforce.ibmcloud.com/vulnerabilities/79984</a></p>
<p>Fix Resolution: Apply the appropriate patch for your system. See References.</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_infrastructure | cve medium detected in commons httpclient jar cve medium severity vulnerability vulnerable library commons httpclient jar the httpclient component supports the client side of rfc http and rfc http several related specifications rfc cookies rfc http authentication etc and provides a framework by which new request types methods or http extensions can be created easily library home page a href path to dependency file winteree winteree eureka serve pom xml path to vulnerable library home wss scanner repository commons httpclient commons httpclient commons httpclient jar home wss scanner repository commons httpclient commons httpclient commons httpclient jar home wss scanner repository commons httpclient commons httpclient commons httpclient jar home wss scanner repository commons httpclient commons httpclient commons httpclient jar home wss scanner repository commons httpclient commons httpclient commons httpclient jar home wss scanner repository commons httpclient commons httpclient commons httpclient jar home wss scanner repository commons httpclient commons httpclient commons httpclient jar dependency hierarchy jacoco maven plugin jar root library maven reporting impl jar doxia core jar x commons httpclient jar vulnerable library found in head commit a href found in base branch master vulnerability details apache commons httpclient x as used in amazon flexible payments service fps merchant java sdk and other products does not verify that the server hostname matches a domain name in the subject s common name cn or subjectaltname field of the x certificate which allows man in the middle attackers to spoof ssl servers via an arbitrary valid certificate publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href fix resolution apply the appropriate patch for your system see references step up your open source security game with whitesource | 0 |
145,411 | 11,688,927,292 | IssuesEvent | 2020-03-05 15:17:07 | ayumi-cloud/oc-security-module | https://api.github.com/repos/ayumi-cloud/oc-security-module | closed | Add GoDaddy + Media Temple module to firewall | Add to Blacklist Add to Whitelist FINSIHED Firewall Priority: Medium Testing - Passed enhancement | ### Enhancement idea
- [x] Add GoDaddy + Media Temple module to firewall.
- [x] Added down-stream channels as well.
| 1.0 | Add GoDaddy + Media Temple module to firewall - ### Enhancement idea
- [x] Add GoDaddy + Media Temple module to firewall.
- [x] Added down-stream channels as well.
| non_infrastructure | add godaddy media temple module to firewall enhancement idea add godaddy media temple module to firewall added down stream channels as well | 0 |
301,014 | 9,214,773,147 | IssuesEvent | 2019-03-10 22:31:00 | Arquisoft/dechat_es1b | https://api.github.com/repos/Arquisoft/dechat_es1b | closed | Update UI when a new message arrives | UI enhancement high-priority | When a new message arrives (already done), the UI should be updated to reflect the new messages | 1.0 | Update UI when a new message arrives - When a new message arrives (already done), the UI should be updated to reflect the new messages | non_infrastructure | update ui when a new message arrives when a new message arrives already done the ui should be updated to reflect the new messages | 0 |
26,960 | 20,963,518,653 | IssuesEvent | 2022-03-28 02:36:17 | OSOceanAcoustics/echopype | https://api.github.com/repos/OSOceanAcoustics/echopype | opened | Update `typing_extensions` version in requirements | infrastructure | Right now conda does not support the version specifier we have in `requirements.txt`
```
typing-extensions~=3.10
```
Changing it in 2 ways results in different behavior (as per [the pip example here](https://pip.pypa.io/en/stable/reference/requirements-file-format/#example)):
- With `typing-extensions>=3.10` I got version `4.1.1`
- With `typing-extensions==3.*` I got version `3.10.0.2`
We can fix this by using both `>=3.10` and `==3.*`, but I think we should test if `typing-extensions=4.X` works so we can keep up with updates of dependencies.
| 1.0 | Update `typing_extensions` version in requirements - Right now conda does not support the version specifier we have in `requirements.txt`
```
typing-extensions~=3.10
```
Changing it in 2 ways results in different behavior (as per [the pip example here](https://pip.pypa.io/en/stable/reference/requirements-file-format/#example)):
- With `typing-extensions>=3.10` I got version `4.1.1`
- With `typing-extensions==3.*` I got version `3.10.0.2`
We can fix this by using both `>=3.10` and `==3.*`, but I think we should test if `typing-extensions=4.X` works so we can keep up with updates of dependencies.
| infrastructure | update typing extensions version in requirements right now conda does not support the version specifier we have in requirements txt typing extensions changing it in ways results in different behavior as per with typing extensions i got version with typing extensions i got version we can fix this by using both and but i think we should test if typing extensions x works so we can keep up with updates of dependencies | 1 |
15,897 | 11,748,163,793 | IssuesEvent | 2020-03-12 14:47:37 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | Can we ignore CLSCompliantAttribute in our APICompat comparisons | area-Infrastructure untriaged | This attribute creates a ton of noise between ref/src differences and current/past differences. Depending on what the assembly level / type settings are we see differences.
We rarely care about the differences and they generate noise in our baseline files.
So: should we ignore these or should we care more? Follow up question: do we even care about using the attribute any more?
@terrajobst @stephentoub @jkotas @joperezr @danmosemsft | 1.0 | Can we ignore CLSCompliantAttribute in our APICompat comparisons - This attribute creates a ton of noise between ref/src differences and current/past differences. Depending on what the assembly level / type settings are we see differences.
We rarely care about the differences and they generate noise in our baseline files.
So: should we ignore these or should we care more? Follow up question: do we even care about using the attribute any more?
@terrajobst @stephentoub @jkotas @joperezr @danmosemsft | infrastructure | can we ignore clscompliantattribute in our apicompat comparisons this attribute creates a ton of noise between ref src differences and current past differences depending on what the assembly level type settings are we see differences we rarely care about the differences and they generate noise in our baseline files so should we ignore these or should we care more follow up question do we even care about using the attribute any more terrajobst stephentoub jkotas joperezr danmosemsft | 1 |
33,676 | 27,713,151,770 | IssuesEvent | 2023-03-14 15:22:50 | spdk/spdk | https://api.github.com/repos/spdk/spdk | closed | No test logs: java.io.FileNotFoundException | Infrastructure Intermittent Failure | No test logs were generated for these 5 test runs:
https://ci.spdk.io/public_build/autotest-per-patch_96474.html
https://ci.spdk.io/public_build/autotest-per-patch_96475.html
https://ci.spdk.io/public_build/autotest-per-patch_96476.html
https://ci.spdk.io/public_build/autotest-per-patch_96477.html
https://ci.spdk.io/public_build/autotest-per-patch_96463.html
In supplemental logs Java exception can be found:
```
00:04:40.166 [Pipeline] }
00:04:40.169 java.io.FileNotFoundException: /var/jenkins/workspace/autotest-per-patch@3/jbp/jenkins/jjb-config/jobs/autotest-upstream/autotest-per-patch-v23.01.json does not exist.
00:04:40.169 at org.jenkinsci.plugins.pipeline.utility.steps.json.ReadJSONStepExecution.doRun(ReadJSONStepExecution.java:83)
00:04:40.169 at org.jenkinsci.plugins.pipeline.utility.steps.AbstractFileOrTextStepExecution.run(AbstractFileOrTextStepExecution.java:29)
00:04:40.169 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
00:04:40.169 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
00:04:40.169 at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
00:04:40.169 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
00:04:40.169 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
00:04:40.169 at java.base/java.lang.Thread.run(Thread.java:829)
00:04:40.187 [Pipeline] // catchError
```
| 1.0 | No test logs: java.io.FileNotFoundException - No test logs were generated for these 5 test runs:
https://ci.spdk.io/public_build/autotest-per-patch_96474.html
https://ci.spdk.io/public_build/autotest-per-patch_96475.html
https://ci.spdk.io/public_build/autotest-per-patch_96476.html
https://ci.spdk.io/public_build/autotest-per-patch_96477.html
https://ci.spdk.io/public_build/autotest-per-patch_96463.html
In supplemental logs Java exception can be found:
```
00:04:40.166 [Pipeline] }
00:04:40.169 java.io.FileNotFoundException: /var/jenkins/workspace/autotest-per-patch@3/jbp/jenkins/jjb-config/jobs/autotest-upstream/autotest-per-patch-v23.01.json does not exist.
00:04:40.169 at org.jenkinsci.plugins.pipeline.utility.steps.json.ReadJSONStepExecution.doRun(ReadJSONStepExecution.java:83)
00:04:40.169 at org.jenkinsci.plugins.pipeline.utility.steps.AbstractFileOrTextStepExecution.run(AbstractFileOrTextStepExecution.java:29)
00:04:40.169 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
00:04:40.169 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
00:04:40.169 at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
00:04:40.169 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
00:04:40.169 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
00:04:40.169 at java.base/java.lang.Thread.run(Thread.java:829)
00:04:40.187 [Pipeline] // catchError
```
| infrastructure | no test logs java io filenotfoundexception no test logs were generated for these test runs in supplemental logs java exception can be found java io filenotfoundexception var jenkins workspace autotest per patch jbp jenkins jjb config jobs autotest upstream autotest per patch json does not exist at org jenkinsci plugins pipeline utility steps json readjsonstepexecution dorun readjsonstepexecution java at org jenkinsci plugins pipeline utility steps abstractfileortextstepexecution run abstractfileortextstepexecution java at org jenkinsci plugins workflow steps synchronousnonblockingstepexecution lambda start synchronousnonblockingstepexecution java at java base java util concurrent executors runnableadapter call executors java at java base java util concurrent futuretask run futuretask java at java base java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java base java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java base java lang thread run thread java catcherror | 1 |
34,181 | 28,439,834,284 | IssuesEvent | 2023-04-15 19:21:24 | ajsaraujo/my-health-app | https://api.github.com/repos/ajsaraujo/my-health-app | opened | Melhorar biblioteca de componentes de UI | feature infrastructure | - [ ] Melhorar estilo dos componentes já criados
- [ ] Adicionar novos componentes, vide:
- [ ] RadioButton
- [ ] Dropdown
- [ ] SecondaryButton | 1.0 | Melhorar biblioteca de componentes de UI - - [ ] Melhorar estilo dos componentes já criados
- [ ] Adicionar novos componentes, vide:
- [ ] RadioButton
- [ ] Dropdown
- [ ] SecondaryButton | infrastructure | melhorar biblioteca de componentes de ui melhorar estilo dos componentes já criados adicionar novos componentes vide radiobutton dropdown secondarybutton | 1 |
519,768 | 15,056,928,430 | IssuesEvent | 2021-02-03 20:54:24 | afids/afids-validator | https://api.github.com/repos/afids/afids-validator | opened | NHP vs Human Toggle | enhancement priority | ## The problem
To be clearer to the end user and ensure the database stays clean we need to ask the user if the data they are uploading is NHP or human. This can be done in a toggle or dropdown. Mixing organism and template should result in a warning.
_PR template was adopted from [appium](https://github.com/appium/appium/blob/master/.github/ISSUE_TEMPLATE.md)_ | 1.0 | NHP vs Human Toggle - ## The problem
To be clearer to the end user and ensure the database stays clean we need to ask the user if the data they are uploading is NHP or human. This can be done in a toggle or dropdown. Mixing organism and template should result in a warning.
_PR template was adopted from [appium](https://github.com/appium/appium/blob/master/.github/ISSUE_TEMPLATE.md)_ | non_infrastructure | nhp vs human toggle the problem to be clearer to the end user and ensure the database stays clean we need to ask the user if the data they are uploading is nhp or human this can be done in a toggle or dropdown mixing organism and template should result in a warning pr template was adopted from | 0 |
25,287 | 4,282,457,836 | IssuesEvent | 2016-07-15 09:14:14 | Cockatrice/Cockatrice | https://api.github.com/repos/Cockatrice/Cockatrice | closed | Layout bug when pasting deck | App - Cockatrice Defect - Basic UI / UX | Running the latest master branch (81006d5342c95e3aa25e6bfce790875e9aebf9c7).
When opening the program, have a decklist in your clipboard and press the paste key combination (ctrl/cmd + V) without clicking on anything else.
<img width="1680" alt="screen shot 2016-07-15 at 10 42 33" src="https://cloud.githubusercontent.com/assets/2134793/16868659/32a44e2a-4a79-11e6-923a-9b9f4f8134e9.png">
Here was the deck I used. Looks like all of the items went into the `Deck Name` edit.
```
2 Abrupt Decay
2 Blood Crypt
2 Bloodstained Mire
1 Clifftop Retreat
1 Damnation
1 Elesh Norn, Grand Cenobite
4 Faithless Looting
1 Forest
1 Godless Shrine
1 Grave Titan
3 Kitchen Finks
3 Lingering Souls
2 Marsh Flats
1 Mountain
2 Murderous Cut
1 Overgrown Tomb
3 Path to Exile
1 Plains
2 Rootbound Crag
1 Sacred Foundry
2 Satyr Wayfinder
2 Siege Rhino
1 Stomping Ground
1 Sunpetal Grove
1 Swamp
4 Tarmogoyf
2 Temple Garden
2 Thoughtseize
2 Thragtusk
3 Unburial Rites
1 Vault of the Archangel
2 Wooded Foothills
1 Woodland Cemetery
1 Wurmcoil Engine
sideboard
1 Ancient Grudge
1 Anger of the Gods
1 Elesh Norn, Grand Cenobite
1 Golgari Charm
2 Inquisition of Kozilek
1 Iona, Shield of Emeria
1 Maelstrom Pulse
1 Rakdos Charm
1 Ruric Thar, the Unbowed
1 Sigarda, Host of Herons
2 Slaughter Games
2 Timely Reinforcements
```
| 1.0 | Layout bug when pasting deck - Running the latest master branch (81006d5342c95e3aa25e6bfce790875e9aebf9c7).
When opening the program, have a decklist in your clipboard and press the paste key combination (ctrl/cmd + V) without clicking on anything else.
<img width="1680" alt="screen shot 2016-07-15 at 10 42 33" src="https://cloud.githubusercontent.com/assets/2134793/16868659/32a44e2a-4a79-11e6-923a-9b9f4f8134e9.png">
Here was the deck I used. Looks like all of the items went into the `Deck Name` edit.
```
2 Abrupt Decay
2 Blood Crypt
2 Bloodstained Mire
1 Clifftop Retreat
1 Damnation
1 Elesh Norn, Grand Cenobite
4 Faithless Looting
1 Forest
1 Godless Shrine
1 Grave Titan
3 Kitchen Finks
3 Lingering Souls
2 Marsh Flats
1 Mountain
2 Murderous Cut
1 Overgrown Tomb
3 Path to Exile
1 Plains
2 Rootbound Crag
1 Sacred Foundry
2 Satyr Wayfinder
2 Siege Rhino
1 Stomping Ground
1 Sunpetal Grove
1 Swamp
4 Tarmogoyf
2 Temple Garden
2 Thoughtseize
2 Thragtusk
3 Unburial Rites
1 Vault of the Archangel
2 Wooded Foothills
1 Woodland Cemetery
1 Wurmcoil Engine
sideboard
1 Ancient Grudge
1 Anger of the Gods
1 Elesh Norn, Grand Cenobite
1 Golgari Charm
2 Inquisition of Kozilek
1 Iona, Shield of Emeria
1 Maelstrom Pulse
1 Rakdos Charm
1 Ruric Thar, the Unbowed
1 Sigarda, Host of Herons
2 Slaughter Games
2 Timely Reinforcements
```
| non_infrastructure | layout bug when pasting deck running the latest master branch when opening the program have a decklist in your clipboard and press the paste key combination ctrl cmd v without clicking on anything else img width alt screen shot at src here was the deck i used looks like all of the items went into the deck name edit abrupt decay blood crypt bloodstained mire clifftop retreat damnation elesh norn grand cenobite faithless looting forest godless shrine grave titan kitchen finks lingering souls marsh flats mountain murderous cut overgrown tomb path to exile plains rootbound crag sacred foundry satyr wayfinder siege rhino stomping ground sunpetal grove swamp tarmogoyf temple garden thoughtseize thragtusk unburial rites vault of the archangel wooded foothills woodland cemetery wurmcoil engine sideboard ancient grudge anger of the gods elesh norn grand cenobite golgari charm inquisition of kozilek iona shield of emeria maelstrom pulse rakdos charm ruric thar the unbowed sigarda host of herons slaughter games timely reinforcements | 0 |
137,713 | 30,741,231,999 | IssuesEvent | 2023-07-28 11:41:02 | Qiskit/qiskit.org | https://api.github.com/repos/Qiskit/qiskit.org | closed | Create `.prettierrc` with rules | good first issue code quality | For consistency and so that IDEs / text editors like VS Code's auto-lint functionality works as expected, creating a `.prettierrc` file might be helpful.
We could take as an example the one that comes with the newest Nuxt versions:
```json
{
"semi": false,
"singleQuote": true
}
``` | 1.0 | Create `.prettierrc` with rules - For consistency and so that IDEs / text editors like VS Code's auto-lint functionality works as expected, creating a `.prettierrc` file might be helpful.
We could take as an example the one that comes with the newest Nuxt versions:
```json
{
"semi": false,
"singleQuote": true
}
``` | non_infrastructure | create prettierrc with rules for consistency and so that ides text editors like vs code s auto lint functionality works as expected creating a prettierrc file might be helpful we could take as an example the one that comes with the newest nuxt versions json semi false singlequote true | 0 |
31,022 | 25,260,731,695 | IssuesEvent | 2022-11-15 22:27:59 | PostHog/posthog | https://api.github.com/repos/PostHog/posthog | closed | State of "Protobuf" format schema for clickhouse | enhancement infrastructure performance | ## Is your feature request related to a problem?
In https://github.com/PostHog/posthog/pull/2254 @fuziontech introduced protobuf for the clickhouse_events topic. Exact motivation if unknown by me, but I assume it has to do with cost savings around kafka traffic.
We never rolled out the feature to other topics and since then we've:
- Introduced plugin-server
- Introduced new topics that facilitate events service <-> plugin server communication (including for communicating events data)
- Introduced dead letter queue and other topics
- Are considering significantly changing the events table structure, which in turn requires updating the existing protobuf schema and test deploying these changes. This in turn might create potential posthog upgrade barriers.
- Are considering supporting external clickhouse cloud providers (like altinity) which might not have support for using custom format schemas
- Might require hacks like https://github.com/PostHog/posthog/pull/8333 to land to support them well.
All of this makes the protobuf solution we have right now less than ideal. It also doesn't really serve the potential cost-saving purpose as events are json-encoded in at least one topic already.
The discussion point here is - what shall we do about it?
Do we want to invest more and get protobuf on other topics? Do we want to make it entirely optional/configurable? Do we want to drop it completely?
cc @fuziontech @hazzadous @guidoiaquinti @tiina303 @yakkomajuri @marcushyett-ph for team-platform context
cc @EDsCODE and @timgl who might have additional context
#### *Thank you* for your feature request – we love each and every one!
| 1.0 | State of "Protobuf" format schema for clickhouse - ## Is your feature request related to a problem?
In https://github.com/PostHog/posthog/pull/2254 @fuziontech introduced protobuf for the clickhouse_events topic. Exact motivation if unknown by me, but I assume it has to do with cost savings around kafka traffic.
We never rolled out the feature to other topics and since then we've:
- Introduced plugin-server
- Introduced new topics that facilitate events service <-> plugin server communication (including for communicating events data)
- Introduced dead letter queue and other topics
- Are considering significantly changing the events table structure, which in turn requires updating the existing protobuf schema and test deploying these changes. This in turn might create potential posthog upgrade barriers.
- Are considering supporting external clickhouse cloud providers (like altinity) which might not have support for using custom format schemas
- Might require hacks like https://github.com/PostHog/posthog/pull/8333 to land to support them well.
All of this makes the protobuf solution we have right now less than ideal. It also doesn't really serve the potential cost-saving purpose as events are json-encoded in at least one topic already.
The discussion point here is - what shall we do about it?
Do we want to invest more and get protobuf on other topics? Do we want to make it entirely optional/configurable? Do we want to drop it completely?
cc @fuziontech @hazzadous @guidoiaquinti @tiina303 @yakkomajuri @marcushyett-ph for team-platform context
cc @EDsCODE and @timgl who might have additional context
#### *Thank you* for your feature request – we love each and every one!
| infrastructure | state of protobuf format schema for clickhouse is your feature request related to a problem in fuziontech introduced protobuf for the clickhouse events topic exact motivation if unknown by me but i assume it has to do with cost savings around kafka traffic we never rolled out the feature to other topics and since then we ve introduced plugin server introduced new topics that facilitate events service plugin server communication including for communicating events data introduced dead letter queue and other topics are considering significantly changing the events table structure which in turn requires updating the existing protobuf schema and test deploying these changes this in turn might create potential posthog upgrade barriers are considering supporting external clickhouse cloud providers like altinity which might not have support for using custom format schemas might require hacks like to land to support them well all of this makes the protobuf solution we have right now less than ideal it also doesn t really serve the potential cost saving purpose as events are json encoded in at least one topic already the discussion point here is what shall we do about it do we want to invest more and get protobuf on other topics do we want to make it entirely optional configurable do we want to drop it completely cc fuziontech hazzadous guidoiaquinti yakkomajuri marcushyett ph for team platform context cc edscode and timgl who might have additional context thank you for your feature request – we love each and every one | 1 |
6,662 | 6,549,845,925 | IssuesEvent | 2017-09-05 08:43:11 | metoppv/improver | https://api.github.com/repos/metoppv/improver | closed | Threshold: agree and apply correct naming convention | Category: User Story Type: Investigative Type: Technical Infrastructure | As an IMPROVER data user I want the threshold plugin to correctly produce probability metadata when it is applied.
Related issues: #91, #54, #98
For example, `thickness_of_rainfall_amount` might become e.g. `probability_of_rainfall_amount_above_threshold` with a threshold value (naming to be decided). It will not be so neat for cubes with realization dimensions. When they are fed in (normally what we would expect), unless we collapse over realization (which is really a blend step) then we'll still have realization mixed with 'probability'.
Acceptance criteria:
* Apply temporary metadata conventions to the plugin and add unit tests to capture this
* Move threshold plugin out of utilities. | 1.0 | Threshold: agree and apply correct naming convention - As an IMPROVER data user I want the threshold plugin to correctly produce probability metadata when it is applied.
Related issues: #91, #54, #98
For example, `thickness_of_rainfall_amount` might become e.g. `probability_of_rainfall_amount_above_threshold` with a threshold value (naming to be decided). It will not be so neat for cubes with realization dimensions. When they are fed in (normally what we would expect), unless we collapse over realization (which is really a blend step) then we'll still have realization mixed with 'probability'.
Acceptance criteria:
* Apply temporary metadata conventions to the plugin and add unit tests to capture this
* Move threshold plugin out of utilities. | infrastructure | threshold agree and apply correct naming convention as an improver data user i want the threshold plugin to correctly produce probability metadata when it is applied related issues for example thickness of rainfall amount might become e g probability of rainfall amount above threshold with a threshold value naming to be decided it will not be so neat for cubes with realization dimensions when they are fed in normally what we would expect unless we collapse over realization which is really a blend step then we ll still have realization mixed with probability acceptance criteria apply temporary metadata conventions to the plugin and add unit tests to capture this move threshold plugin out of utilities | 1 |
29,009 | 23,664,499,703 | IssuesEvent | 2022-08-26 19:11:59 | mitodl/ol-infrastructure | https://api.github.com/repos/mitodl/ol-infrastructure | opened | Generate new vault recovery keys and store in keybase | DevOps Maintenance Infrastructure | Generate new vault recovery keys for all clusters and store in keybase. | 1.0 | Generate new vault recovery keys and store in keybase - Generate new vault recovery keys for all clusters and store in keybase. | infrastructure | generate new vault recovery keys and store in keybase generate new vault recovery keys for all clusters and store in keybase | 1 |
351,923 | 25,043,764,419 | IssuesEvent | 2022-11-05 01:52:02 | Daveiano/weewx-wdc | https://api.github.com/repos/Daveiano/weewx-wdc | closed | Make diagrams configurable per context (per period) / Refactor diagrams configuration | documentation enhancement | Currently, the skin only allows to define the diagrams once, this definition is then used on all pages (index, week, month, year, statistics). So it is not possible to show a specific diagram e.g. the outTemp min/max/avg diagram only on the statistics page. Every diagram is shown everywhere.
This should be configurable like in the default seasons skin `[ImageGenerator]` section:
```
[[day_images]]
x_label_format = %H:%M
bottom_label_format = %x %X
time_length = 97200 # 27 hours
[[[daybarometer]]]
[[[[barometer]]]]
[[[daytempdew]]]
[[[[outTemp]]]]
[[[[dewpoint]]]]
...
[[week_images]]
x_label_format = %d
bottom_label_format = %x %X
time_length = 604800 # 7 days
aggregate_type = avg
aggregate_interval = hour
[[[weekbarometer]]]
[[[[barometer]]]]
[[[weektempdew]]]
[[[[outTemp]]]]
[[[[dewpoint]]]]
...
```
**Things to consider**
~~- Refactor getDiagramProps methods to use `weeutil.config.accumulateLeaves` and `search_up`~~
~~- Expose `enableArea` and `areaOpacity` in skin.conf for diagrams~~
Related issues:
#25
#71
#75 | 1.0 | Make diagrams configurable per context (per period) / Refactor diagrams configuration - Currently, the skin only allows to define the diagrams once, this definition is then used on all pages (index, week, month, year, statistics). So it is not possible to show a specific diagram e.g. the outTemp min/max/avg diagram only on the statistics page. Every diagram is shown everywhere.
This should be configurable like in the default seasons skin `[ImageGenerator]` section:
```
[[day_images]]
x_label_format = %H:%M
bottom_label_format = %x %X
time_length = 97200 # 27 hours
[[[daybarometer]]]
[[[[barometer]]]]
[[[daytempdew]]]
[[[[outTemp]]]]
[[[[dewpoint]]]]
...
[[week_images]]
x_label_format = %d
bottom_label_format = %x %X
time_length = 604800 # 7 days
aggregate_type = avg
aggregate_interval = hour
[[[weekbarometer]]]
[[[[barometer]]]]
[[[weektempdew]]]
[[[[outTemp]]]]
[[[[dewpoint]]]]
...
```
**Things to consider**
~~- Refactor getDiagramProps methods to use `weeutil.config.accumulateLeaves` and `search_up`~~
~~- Expose `enableArea` and `areaOpacity` in skin.conf for diagrams~~
Related issues:
#25
#71
#75 | non_infrastructure | make diagrams configurable per context per period refactor diagrams configuration currently the skin only allows to define the diagrams once this definition is then used on all pages index week month year statistics so it is not possible to show a specific diagram e g the outtemp min max avg diagram only on the statistics page every diagram is shown everywhere this should be configurable like in the default seasons skin section x label format h m bottom label format x x time length hours x label format d bottom label format x x time length days aggregate type avg aggregate interval hour things to consider refactor getdiagramprops methods to use weeutil config accumulateleaves and search up expose enablearea and areaopacity in skin conf for diagrams related issues | 0 |
30,187 | 24,627,526,924 | IssuesEvent | 2022-10-16 18:04:34 | dotnet/efcore | https://api.github.com/repos/dotnet/efcore | closed | [Discussion] Moving EntityFrameworkCore repo to dotnet org 2020-01-07 | closed-no-further-action customer-reported area-infrastructure | As a first step towards the work describe [here](https://github.com/dotnet/announcements/issues/127), we're planning on migrating the EntityFrameworkCore repo to the dotnet org and renaming it to "efcore". We'd like to get this done ASAP.
We don't expect any significant issues for contributors, GitHub is great about adding redirects. However, it may impact our ability to produce nightly builds and flow dependencies for a few days.
Please let us know if you run into any other issues. | 1.0 | [Discussion] Moving EntityFrameworkCore repo to dotnet org 2020-01-07 - As a first step towards the work describe [here](https://github.com/dotnet/announcements/issues/127), we're planning on migrating the EntityFrameworkCore repo to the dotnet org and renaming it to "efcore". We'd like to get this done ASAP.
We don't expect any significant issues for contributors, GitHub is great about adding redirects. However, it may impact our ability to produce nightly builds and flow dependencies for a few days.
Please let us know if you run into any other issues. | infrastructure | moving entityframeworkcore repo to dotnet org as a first step towards the work describe we re planning on migrating the entityframeworkcore repo to the dotnet org and renaming it to efcore we d like to get this done asap we don t expect any significant issues for contributors github is great about adding redirects however it may impact our ability to produce nightly builds and flow dependencies for a few days please let us know if you run into any other issues | 1 |
19,488 | 13,255,753,546 | IssuesEvent | 2020-08-20 11:30:48 | nhsx/covid-chest-imaging-database | https://api.github.com/repos/nhsx/covid-chest-imaging-database | closed | Set retention period for fargate logs | enhancement infrastructure | ### Describe the feature request
Pipeline run logs don't need to be kept forever, should have an expiration date. Something like 24 months seems to be sufficient for the pipeline runs, to keep things simpler for now.
### Affected product area (please put an X in all the brackets that apply)
[ ] Documentation
[ ] Data access
[x] Infrastructure
[ ] Loader pipeline
[ ] Other (please describe)
### Additional context
The 24 months is coming from the Platform log retention period, so might need additional thinking. | 1.0 | Set retention period for fargate logs - ### Describe the feature request
Pipeline run logs don't need to be kept forever, should have an expiration date. Something like 24 months seems to be sufficient for the pipeline runs, to keep things simpler for now.
### Affected product area (please put an X in all the brackets that apply)
[ ] Documentation
[ ] Data access
[x] Infrastructure
[ ] Loader pipeline
[ ] Other (please describe)
### Additional context
The 24 months is coming from the Platform log retention period, so might need additional thinking. | infrastructure | set retention period for fargate logs describe the feature request pipeline run logs don t need to be kept forever should have an expiration date something like months seems to be sufficient for the pipeline runs to keep things simpler for now affected product area please put an x in all the brackets that apply documentation data access infrastructure loader pipeline other please describe additional context the months is coming from the platform log retention period so might need additional thinking | 1 |
764,780 | 26,816,905,046 | IssuesEvent | 2023-02-02 05:56:53 | digi-serve/cars_app | https://api.github.com/repos/digi-serve/cars_app | closed | Tenant cannot access her children's data. | bug high priority | **Describe the bug**
Tenant cannot access her children's data.
**To Reproduce**
1. Go to 'fcf.childatrisk.in.th'
2. Click on 'Login'
3. On 'main menu' and 'Children', click on each children tap, no response.
4. See error
**Expected behavior**
When tenant click on children tap, she can access to these data.
| 1.0 | Tenant cannot access her children's data. - **Describe the bug**
Tenant cannot access her children's data.
**To Reproduce**
1. Go to 'fcf.childatrisk.in.th'
2. Click on 'Login'
3. On 'main menu' and 'Children', click on each children tap, no response.
4. See error
**Expected behavior**
When tenant click on children tap, she can access to these data.
| non_infrastructure | tenant cannot access her children s data describe the bug tenant cannot access her children s data to reproduce go to fcf childatrisk in th click on login on main menu and children click on each children tap no response see error expected behavior when tenant click on children tap she can access to these data | 0 |
11,480 | 9,203,344,214 | IssuesEvent | 2019-03-08 02:02:23 | GSA/datagov-deploy | https://api.github.com/repos/GSA/datagov-deploy | closed | Document: Detail changes | infrastructure server web | Task: Document how repo should be used and how it integrates with its parent repo.
Repo: datagov-deploy-apache2 | 1.0 | Document: Detail changes - Task: Document how repo should be used and how it integrates with its parent repo.
Repo: datagov-deploy-apache2 | infrastructure | document detail changes task document how repo should be used and how it integrates with its parent repo repo datagov deploy | 1 |
13,156 | 10,131,775,874 | IssuesEvent | 2019-08-01 20:26:28 | HumanCellAtlas/secondary-analysis | https://api.github.com/repos/HumanCellAtlas/secondary-analysis | closed | An EDN to JSON translation tool might be handy. | infrastructure | Zero dx tools often produce EDN output.
A trivial edn->json translator will help it interoperate with JSON-based tools.
┆Issue is synchronized with this [Jira Story](https://broadinstitute.atlassian.net/browse/GH-252)
| 1.0 | An EDN to JSON translation tool might be handy. - Zero dx tools often produce EDN output.
A trivial edn->json translator will help it interoperate with JSON-based tools.
┆Issue is synchronized with this [Jira Story](https://broadinstitute.atlassian.net/browse/GH-252)
| infrastructure | an edn to json translation tool might be handy zero dx tools often produce edn output a trivial edn json translator will help it interoperate with json based tools ┆issue is synchronized with this | 1 |
12,824 | 9,966,624,564 | IssuesEvent | 2019-07-08 11:42:05 | coq/coq | https://api.github.com/repos/coq/coq | opened | [ci] [azure] [osx] Azure OSX build is broken due to gtk linking | kind: ci-failure kind: infrastructure | Since a few days the azure OSX workers do fail when trying to build coqide:
```
Undefined symbols for architecture x86_64:
"_GTK_SOCKET", referenced from:
_ml_gtk_socket_add_id in liblablgtk3_stubs.a(ml_gtk.o)
_ml_gtk_socket_get_id in liblablgtk3_stubs.a(ml_gtk.o)
_ml_gtk_socket_get_plug_window in liblablgtk3_stubs.a(ml_gtk.o)
OCAMLC parsing/notation_gram.ml
"_gtk_plug_get_type", referenced from:
_ml_gtkwindow_init in liblablgtk3_stubs.a(ml_gtk.o)
"_gtk_plug_new", referenced from:
_ml_gtk_plug_new in liblablgtk3_stubs.a(ml_gtk.o)
(maybe you meant: _ml_gtk_plug_new)
"_gtk_socket_add_id", referenced from:
_ml_gtk_socket_add_id in liblablgtk3_stubs.a(ml_gtk.o)
(maybe you meant: _ml_gtk_socket_add_id)
"_gtk_socket_get_id", referenced from:
_ml_gtk_socket_get_id in liblablgtk3_stubs.a(ml_gtk.o)
(maybe you meant: _ml_gtk_socket_get_id
)
"_gtk_socket_get_plug_window", referenced from:
_ml_gtk_socket_get_plug_window in liblablgtk3_stubs.a(ml_gtk.o)
(maybe you meant: _ml_gtk_socket_get_plug_window)
"_gtk_socket_get_type", referenced from:
_ml_gtkwindow_init in liblablgtk3_stubs.a(ml_gtk.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
File "caml_startup", line 1:
Error: Error during linking
make[1]: *** [bin/coqide] Error 2
```
https://dev.azure.com/coq/coq/_build/results?buildId=4065
I am unsure if this is due to the OSX images now using `clang` instead of gcc, I guess an OSX expert is required here. Maybe trying with Dune could be interesting, but I'm not very optimisitic that will fix it.
This highlights a fatal flaw of our Azure setup which is that the builds are not reproducible and indeed we get upgrades randomly. That has been biting us quite a bit lately [on the other hand we discover issues pretty quickly :(]
| 1.0 | [ci] [azure] [osx] Azure OSX build is broken due to gtk linking - Since a few days the azure OSX workers do fail when trying to build coqide:
```
Undefined symbols for architecture x86_64:
"_GTK_SOCKET", referenced from:
_ml_gtk_socket_add_id in liblablgtk3_stubs.a(ml_gtk.o)
_ml_gtk_socket_get_id in liblablgtk3_stubs.a(ml_gtk.o)
_ml_gtk_socket_get_plug_window in liblablgtk3_stubs.a(ml_gtk.o)
OCAMLC parsing/notation_gram.ml
"_gtk_plug_get_type", referenced from:
_ml_gtkwindow_init in liblablgtk3_stubs.a(ml_gtk.o)
"_gtk_plug_new", referenced from:
_ml_gtk_plug_new in liblablgtk3_stubs.a(ml_gtk.o)
(maybe you meant: _ml_gtk_plug_new)
"_gtk_socket_add_id", referenced from:
_ml_gtk_socket_add_id in liblablgtk3_stubs.a(ml_gtk.o)
(maybe you meant: _ml_gtk_socket_add_id)
"_gtk_socket_get_id", referenced from:
_ml_gtk_socket_get_id in liblablgtk3_stubs.a(ml_gtk.o)
(maybe you meant: _ml_gtk_socket_get_id
)
"_gtk_socket_get_plug_window", referenced from:
_ml_gtk_socket_get_plug_window in liblablgtk3_stubs.a(ml_gtk.o)
(maybe you meant: _ml_gtk_socket_get_plug_window)
"_gtk_socket_get_type", referenced from:
_ml_gtkwindow_init in liblablgtk3_stubs.a(ml_gtk.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
File "caml_startup", line 1:
Error: Error during linking
make[1]: *** [bin/coqide] Error 2
```
https://dev.azure.com/coq/coq/_build/results?buildId=4065
I am unsure if this is due to the OSX images now using `clang` instead of gcc, I guess an OSX expert is required here. Maybe trying with Dune could be interesting, but I'm not very optimisitic that will fix it.
This highlights a fatal flaw of our Azure setup which is that the builds are not reproducible and indeed we get upgrades randomly. That has been biting us quite a bit lately [on the other hand we discover issues pretty quickly :(]
| infrastructure | azure osx build is broken due to gtk linking since a few days the azure osx workers do fail when trying to build coqide undefined symbols for architecture gtk socket referenced from ml gtk socket add id in stubs a ml gtk o ml gtk socket get id in stubs a ml gtk o ml gtk socket get plug window in stubs a ml gtk o ocamlc parsing notation gram ml gtk plug get type referenced from ml gtkwindow init in stubs a ml gtk o gtk plug new referenced from ml gtk plug new in stubs a ml gtk o maybe you meant ml gtk plug new gtk socket add id referenced from ml gtk socket add id in stubs a ml gtk o maybe you meant ml gtk socket add id gtk socket get id referenced from ml gtk socket get id in stubs a ml gtk o maybe you meant ml gtk socket get id gtk socket get plug window referenced from ml gtk socket get plug window in stubs a ml gtk o maybe you meant ml gtk socket get plug window gtk socket get type referenced from ml gtkwindow init in stubs a ml gtk o ld symbol s not found for architecture clang error linker command failed with exit code use v to see invocation file caml startup line error error during linking make error i am unsure if this is due to the osx images now using clang instead of gcc i guess an osx expert is required here maybe trying with dune could be interesting but i m not very optimisitic that will fix it this highlights a fatal flaw of our azure setup which is that the builds are not reproducible and indeed we get upgrades randomly that has been biting us quite a bit lately | 1 |
6,427 | 2,587,975,870 | IssuesEvent | 2015-02-17 21:50:41 | firelab/windninja | https://api.github.com/repos/firelab/windninja | closed | NOMADS won't write to drives other than C:\ | bug component:core component:wx priority:high severity:high | The NOMADS writer fails to copy forecast data to drives other than C:\ (or possibly the driver WindNinja is installed). | 1.0 | NOMADS won't write to drives other than C:\ - The NOMADS writer fails to copy forecast data to drives other than C:\ (or possibly the driver WindNinja is installed). | non_infrastructure | nomads won t write to drives other than c the nomads writer fails to copy forecast data to drives other than c or possibly the driver windninja is installed | 0 |
6,441 | 6,411,952,859 | IssuesEvent | 2017-08-08 01:03:49 | OctopusDeploy/Issues | https://api.github.com/repos/OctopusDeploy/Issues | closed | Certificate generation does not work on Windows 2008 | area/infrastructure bug | It looks like certificate generation on Windows 2008 doesn't work anymore since server and tentacle `3.14.1`.
It is probably caused by the change to SHA256 hashes (in response to the SHA1 collision problem): https://github.com/OctopusDeploy/OctopusDeploy/commit/8f8fffb988e92f0cca9110c46789b0b3433d1481
The error is similar to:
```
==== NewCertificateCommand ====
===============================================================================
Exception from HRESULT: 0xC0000005
System.Runtime.InteropServices.COMException
```
Reports:
http://help.octopusdeploy.com/discussions/problems/56245-cant-install-tentacle-past-version-31310
(However this is using the unsupported 2008 SP1)
http://help.octopusdeploy.com/discussions/problems/56047-issues-with-installing-tentacle-window-2008-os-32-bit-certificate-generation
(Windows 2008 SP2) | 1.0 | Certificate generation does not work on Windows 2008 - It looks like certificate generation on Windows 2008 doesn't work anymore since server and tentacle `3.14.1`.
It is probably caused by the change to SHA256 hashes (in response to the SHA1 collision problem): https://github.com/OctopusDeploy/OctopusDeploy/commit/8f8fffb988e92f0cca9110c46789b0b3433d1481
The error is similar to:
```
==== NewCertificateCommand ====
===============================================================================
Exception from HRESULT: 0xC0000005
System.Runtime.InteropServices.COMException
```
Reports:
http://help.octopusdeploy.com/discussions/problems/56245-cant-install-tentacle-past-version-31310
(However this is using the unsupported 2008 SP1)
http://help.octopusdeploy.com/discussions/problems/56047-issues-with-installing-tentacle-window-2008-os-32-bit-certificate-generation
(Windows 2008 SP2) | infrastructure | certificate generation does not work on windows it looks like certificate generation on windows doesn t work anymore since server and tentacle it is probably caused by the change to hashes in response to the collision problem the error is similar to newcertificatecommand exception from hresult system runtime interopservices comexception reports however this is using the unsupported windows | 1 |
21,520 | 14,615,233,760 | IssuesEvent | 2020-12-22 11:11:50 | dotnet/iot | https://api.github.com/repos/dotnet/iot | closed | .NET IoT needs a logo | area-infrastructure enhancement help wanted up-for-grabs | This is more of a fun geek-out than anything, but it seems like this repo/project should have some type of logo to represent. You can see other project logos on the [.NET Foundation site](https://dotnetfoundation.org/) like Prism, etc.
/cc @joperezr @richlander any thoughts or resources that could design something? | 1.0 | .NET IoT needs a logo - This is more of a fun geek-out than anything, but it seems like this repo/project should have some type of logo to represent. You can see other project logos on the [.NET Foundation site](https://dotnetfoundation.org/) like Prism, etc.
/cc @joperezr @richlander any thoughts or resources that could design something? | infrastructure | net iot needs a logo this is more of a fun geek out than anything but it seems like this repo project should have some type of logo to represent you can see other project logos on the like prism etc cc joperezr richlander any thoughts or resources that could design something | 1 |
31,184 | 25,395,018,309 | IssuesEvent | 2022-11-22 07:58:20 | lisa-analyzer/lisa | https://api.github.com/repos/lisa-analyzer/lisa | closed | [FEATURE REQUEST] Passing `FileManager` and `LiSAConfiguration` to checks | 🎆 type:feature 🎊 resolution:resolved ⁉ priority:p2 🏨 scope:infrastructure | Checks might want to create files or read configuration options. They should have access to the `FileManager` and `LiSAConfiguration` instance for the analysis.
| 1.0 | [FEATURE REQUEST] Passing `FileManager` and `LiSAConfiguration` to checks - Checks might want to create files or read configuration options. They should have access to the `FileManager` and `LiSAConfiguration` instance for the analysis.
| infrastructure | passing filemanager and lisaconfiguration to checks checks might want to create files or read configuration options they should have access to the filemanager and lisaconfiguration instance for the analysis | 1 |
13,746 | 10,024,657,607 | IssuesEvent | 2019-07-16 22:40:44 | aws/aws-sdk-php | https://api.github.com/repos/aws/aws-sdk-php | closed | transactWriteItems returns An unknown operation was requested | closing-soon-if-no-response feature-request service-api | Hi, I'm trying to create a transaction with DynamoDb,
I have tried this:
```
$data = [
'id' => Uuid::uuid4()->toString(),
'uuid' => $domainMessage->getId(),
'playhead' => $domainMessage->getPlayhead(),
'metadata' => json_encode($this->metadataSerializer->serialize($domainMessage->getMetadata())),
'payload' => json_encode($this->payloadSerializer->serialize($domainMessage->getPayload())),
'recorded_on' => $domainMessage->getRecordedOn()->toString(),
'type' => $domainMessage->getType(),
];
$marshal = new Marshaler();
$data = $marshal->marshalJson(json_encode($data));
$this->client->transactWriteItems([
'TransactItems' => [
[
'Put' => [
'TableName' => $this->table,
'Item' => $data
]
]
]
]
);
```
But returns me this error:
```
Aws\DynamoDb\Exception\DynamoDbException: Error executing "TransactWriteItems" on "http://localhost:8000"; AWS HTTP error: Client error: `POST http://localhost:8000` resulted in a `400 Bad Request` response:
{"__type":"com.amazonaws.dynamodb.v20120810#UnknownOperationException","message":"An unknown operation was requested."}
UnknownOperationException (client): An unknown operation was requested. - {"__type":"com.amazonaws.dynamodb.v20120810#UnknownOperationException","message":"An unknown operation was requested."}
```
If I make a simple putItems with same data it's ok, What I miss or what is the error?
| 1.0 | transactWriteItems returns An unknown operation was requested - Hi, I'm trying to create a transaction with DynamoDb,
I have tried this:
```
$data = [
'id' => Uuid::uuid4()->toString(),
'uuid' => $domainMessage->getId(),
'playhead' => $domainMessage->getPlayhead(),
'metadata' => json_encode($this->metadataSerializer->serialize($domainMessage->getMetadata())),
'payload' => json_encode($this->payloadSerializer->serialize($domainMessage->getPayload())),
'recorded_on' => $domainMessage->getRecordedOn()->toString(),
'type' => $domainMessage->getType(),
];
$marshal = new Marshaler();
$data = $marshal->marshalJson(json_encode($data));
$this->client->transactWriteItems([
'TransactItems' => [
[
'Put' => [
'TableName' => $this->table,
'Item' => $data
]
]
]
]
);
```
But returns me this error:
```
Aws\DynamoDb\Exception\DynamoDbException: Error executing "TransactWriteItems" on "http://localhost:8000"; AWS HTTP error: Client error: `POST http://localhost:8000` resulted in a `400 Bad Request` response:
{"__type":"com.amazonaws.dynamodb.v20120810#UnknownOperationException","message":"An unknown operation was requested."}
UnknownOperationException (client): An unknown operation was requested. - {"__type":"com.amazonaws.dynamodb.v20120810#UnknownOperationException","message":"An unknown operation was requested."}
```
If I make a simple putItems with same data it's ok, What I miss or what is the error?
| non_infrastructure | transactwriteitems returns an unknown operation was requested hi i m trying to create a transaction with dynamodb i have tried this data id uuid tostring uuid domainmessage getid playhead domainmessage getplayhead metadata json encode this metadataserializer serialize domainmessage getmetadata payload json encode this payloadserializer serialize domainmessage getpayload recorded on domainmessage getrecordedon tostring type domainmessage gettype marshal new marshaler data marshal marshaljson json encode data this client transactwriteitems transactitems put tablename this table item data but returns me this error aws dynamodb exception dynamodbexception error executing transactwriteitems on aws http error client error post resulted in a bad request response type com amazonaws dynamodb unknownoperationexception message an unknown operation was requested unknownoperationexception client an unknown operation was requested type com amazonaws dynamodb unknownoperationexception message an unknown operation was requested if i make a simple putitems with same data it s ok what i miss or what is the error | 0 |
697,601 | 23,945,631,225 | IssuesEvent | 2022-09-12 07:01:12 | aquasecurity/trivy-operator | https://api.github.com/repos/aquasecurity/trivy-operator | closed | Allow configuration of trivy-operator pod priorityClassName | kind/feature priority/backlog target/kubernetes | Hi, I need to be able to manage scheduling priority in my cluster. It would be great if the `priorityClassName` of the operator pod could be made configurable.
| 1.0 | Allow configuration of trivy-operator pod priorityClassName - Hi, I need to be able to manage scheduling priority in my cluster. It would be great if the `priorityClassName` of the operator pod could be made configurable.
| non_infrastructure | allow configuration of trivy operator pod priorityclassname hi i need to be able to manage scheduling priority in my cluster it would be great if the priorityclassname of the operator pod could be made configurable | 0 |
13,049 | 10,091,382,120 | IssuesEvent | 2019-07-26 14:07:53 | code4romania/civichq-client | https://api.github.com/repos/code4romania/civichq-client | opened | [Infrastructure] Run app in Docker container | docker infrastructure | The client CivicHQ application should be run in a Docker container. | 1.0 | [Infrastructure] Run app in Docker container - The client CivicHQ application should be run in a Docker container. | infrastructure | run app in docker container the client civichq application should be run in a docker container | 1 |
19,733 | 13,435,360,506 | IssuesEvent | 2020-09-07 12:49:40 | ruqqus/ruqqus | https://api.github.com/repos/ruqqus/ruqqus | closed | Cloudflare returns 525 upon attempting to access the ruqqus site | bug infrastructure | Issue tracker is **ONLY** used for reporting bugs.
<!--- Provide a general summary of the issue in the Title above -->
I try to access `https://ruqqus.com` and I get this:
## Expected Behavior
<!--- Tell us what should happen -->
Should load the browse feed
## Current Behavior
<!--- Tell us what happens instead of the expected behavior -->
Cloudflare serves an HTTP 525 error
## Possible Solution
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
Heroku is down; heroku servers need better uptime assurance.
## Steps to Reproduce
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this bug. Include code to reproduce, if relevant -->
1. Access `https://ruqqus.com/
| 1.0 | Cloudflare returns 525 upon attempting to access the ruqqus site - Issue tracker is **ONLY** used for reporting bugs.
<!--- Provide a general summary of the issue in the Title above -->
I try to access `https://ruqqus.com` and I get this:
## Expected Behavior
<!--- Tell us what should happen -->
Should load the browse feed
## Current Behavior
<!--- Tell us what happens instead of the expected behavior -->
Cloudflare serves an HTTP 525 error
## Possible Solution
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
Heroku is down; heroku servers need better uptime assurance.
## Steps to Reproduce
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this bug. Include code to reproduce, if relevant -->
1. Access `https://ruqqus.com/
| infrastructure | cloudflare returns upon attempting to access the ruqqus site issue tracker is only used for reporting bugs i try to access and i get this expected behavior should load the browse feed current behavior cloudflare serves an http error possible solution heroku is down heroku servers need better uptime assurance steps to reproduce access | 1 |
12,918 | 10,018,662,586 | IssuesEvent | 2019-07-16 08:21:01 | hzi-braunschweig/SORMAS-Project | https://api.github.com/repos/hzi-braunschweig/SORMAS-Project | closed | Add import function for points of entry | Infrastructure Management sormas-api sormas-backend sormas-ui | - [x] Fix bug that prevented the duplicate person popup to appear when importing cases | 1.0 | Add import function for points of entry - - [x] Fix bug that prevented the duplicate person popup to appear when importing cases | infrastructure | add import function for points of entry fix bug that prevented the duplicate person popup to appear when importing cases | 1 |
28,637 | 12,892,466,305 | IssuesEvent | 2020-07-13 19:40:48 | terraform-providers/terraform-provider-aws | https://api.github.com/repos/terraform-providers/terraform-provider-aws | closed | aws_spot_fleet_request valid_until doesn't support indefinite requests | breaking-change enhancement service/ec2 | <!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Terraform Version
Terraform v0.12.24
+ provider.aws v2.56.0
### Affected Resource(s)
* aws_spot_fleet_request
### Terraform Configuration Files
```hcl
resource "aws_spot_fleet_request" "cluster" {
...
valid_until = "2020-05-06T23:53:38Z"
...
}
```
### Expected Behavior
The AWS API says valid_until is an optional parameter. Unfortunately the terraform implementation defaults to 24 hours. I don't see a way I can configure this resource to get it to behave like the aws default behaviour of "until the spot request is cancelled" - see ValidUntil in https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_SpotFleetRequestConfigData.html
### Actual Behavior
defaults to 24 hours, has no obvious way to set it to "until the request is cancelled"
Potential workarounds I thought of short term are:
* Set a ridiculous date in the future, not sure if the AWS API has issues with that.
* Have a null_resource call the aws api to remove the value and set that value as a ignore_changes proeprty in tf. | 1.0 | aws_spot_fleet_request valid_until doesn't support indefinite requests - <!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Terraform Version
Terraform v0.12.24
+ provider.aws v2.56.0
### Affected Resource(s)
* aws_spot_fleet_request
### Terraform Configuration Files
```hcl
resource "aws_spot_fleet_request" "cluster" {
...
valid_until = "2020-05-06T23:53:38Z"
...
}
```
### Expected Behavior
The AWS API says valid_until is an optional parameter. Unfortunately the terraform implementation defaults to 24 hours. I don't see a way I can configure this resource to get it to behave like the aws default behaviour of "until the spot request is cancelled" - see ValidUntil in https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_SpotFleetRequestConfigData.html
### Actual Behavior
defaults to 24 hours, has no obvious way to set it to "until the request is cancelled"
Potential workarounds I thought of short term are:
* Set a ridiculous date in the future, not sure if the AWS API has issues with that.
* Have a null_resource call the aws api to remove the value and set that value as a ignore_changes proeprty in tf. | non_infrastructure | aws spot fleet request valid until doesn t support indefinite requests community note please vote on this issue by adding a 👍 to the original issue to help the community and maintainers prioritize this request please do not leave or other comments that do not add relevant new information or questions they generate extra noise for issue followers and do not help prioritize the request if you are interested in working on this issue or have submitted a pull request please leave a comment terraform version terraform provider aws affected resource s aws spot fleet request terraform configuration files hcl resource aws spot fleet request cluster valid until expected behavior the aws api says valid until is an optional parameter unfortunately the terraform implementation defaults to hours i don t see a way i can configure this resource to get it to behave like the aws default behaviour of until the spot request is cancelled see validuntil in actual behavior defaults to hours has no obvious way to set it to until the request is cancelled potential workarounds i thought of short term are set a ridiculous date in the future not sure if the aws api has issues with that have a null resource call the aws api to remove the value and set that value as a ignore changes proeprty in tf | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.