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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
6,808
| 6,619,742,653
|
IssuesEvent
|
2017-09-21 13:23:46
|
krlmlr/styler
|
https://api.github.com/repos/krlmlr/styler
|
closed
|
Verify lossless parse + serialize (without transforms)
|
Priority: Low Type: Infrastructure
|
A run without any transformers enabled should yield exactly the same results as the input, minus spaces at EOL and conversion of tabs to spaces. This should be tested separately on all input files, for easier isolation of parse/serialize problems from transformer problems during later refactorings.
Reference: https://github.com/krlmlr/styler/pull/79#discussion_r129269504
|
1.0
|
Verify lossless parse + serialize (without transforms) - A run without any transformers enabled should yield exactly the same results as the input, minus spaces at EOL and conversion of tabs to spaces. This should be tested separately on all input files, for easier isolation of parse/serialize problems from transformer problems during later refactorings.
Reference: https://github.com/krlmlr/styler/pull/79#discussion_r129269504
|
infrastructure
|
verify lossless parse serialize without transforms a run without any transformers enabled should yield exactly the same results as the input minus spaces at eol and conversion of tabs to spaces this should be tested separately on all input files for easier isolation of parse serialize problems from transformer problems during later refactorings reference
| 1
|
780,687
| 27,404,341,600
|
IssuesEvent
|
2023-03-01 04:58:46
|
ballerina-platform/ballerina-lang
|
https://api.github.com/repos/ballerina-platform/ballerina-lang
|
closed
|
[Linter] Detect overuse of type cast
|
Type/Improvement Priority/High Team/CompilerFE Area/CompilerLinter Deferred
|
This is an anti-pattern. Use conditional type narrowing or `ensureType` instead
Rule: `warn`
|
1.0
|
[Linter] Detect overuse of type cast - This is an anti-pattern. Use conditional type narrowing or `ensureType` instead
Rule: `warn`
|
non_infrastructure
|
detect overuse of type cast this is an anti pattern use conditional type narrowing or ensuretype instead rule warn
| 0
|
26,828
| 20,755,845,850
|
IssuesEvent
|
2022-03-15 12:08:07
|
conan-io/conan-center-index
|
https://api.github.com/repos/conan-io/conan-center-index
|
closed
|
[🤖 INFRA] CI relaunched, many jobs expected to fail (everything is working)
|
infrastructure
|
Hi,
Today we have redeployed the jobs in Jenkins and, as a consequence, all of them have been triggered again. Our servers are not prepared for such a volume of jobs (all PRs at once!) and many of them will fail unexpectedly, some others will be canceled by us trying to keep the load under some threshold that will guarantee that running jobs can succeed.
In the following hours (today, tomorrow) we will be retrying all these PRs and trying to leave them in the expected status: green, failed, or pending on some infrastructure changes, but no one should be _running forever_ or with UnexpectedError label after those retriggers.
You can **keep using the repository as always**, but there is no need for you to trigger again past PRs, we will take care of them. I would ask you to have some patience.
Thanks
PS.- Should we start a bulletin? 🗞️
|
1.0
|
[🤖 INFRA] CI relaunched, many jobs expected to fail (everything is working) - Hi,
Today we have redeployed the jobs in Jenkins and, as a consequence, all of them have been triggered again. Our servers are not prepared for such a volume of jobs (all PRs at once!) and many of them will fail unexpectedly, some others will be canceled by us trying to keep the load under some threshold that will guarantee that running jobs can succeed.
In the following hours (today, tomorrow) we will be retrying all these PRs and trying to leave them in the expected status: green, failed, or pending on some infrastructure changes, but no one should be _running forever_ or with UnexpectedError label after those retriggers.
You can **keep using the repository as always**, but there is no need for you to trigger again past PRs, we will take care of them. I would ask you to have some patience.
Thanks
PS.- Should we start a bulletin? 🗞️
|
infrastructure
|
ci relaunched many jobs expected to fail everything is working hi today we have redeployed the jobs in jenkins and as a consequence all of them have been triggered again our servers are not prepared for such a volume of jobs all prs at once and many of them will fail unexpectedly some others will be canceled by us trying to keep the load under some threshold that will guarantee that running jobs can succeed in the following hours today tomorrow we will be retrying all these prs and trying to leave them in the expected status green failed or pending on some infrastructure changes but no one should be running forever or with unexpectederror label after those retriggers you can keep using the repository as always but there is no need for you to trigger again past prs we will take care of them i would ask you to have some patience thanks ps should we start a bulletin 🗞️
| 1
|
813,355
| 30,454,953,548
|
IssuesEvent
|
2023-07-16 19:19:45
|
AdguardTeam/AdguardForWindows
|
https://api.github.com/repos/AdguardTeam/AdguardForWindows
|
closed
|
Proton VPN Chrome Extension Doesn't Work with Adguard DNS Protection
|
bug waiting for repro Priority: P4
|
### AdGuard version
Extension
### Browser version
Edge 113.0.1774.57
### OS version
Windows 11 22H2 build 22621.1702
### Issue Details
Proton VPN Chrome Extension (https://chrome.google.com/webstore/detail/proton-vpn-a-swiss-vpn-yo/jplgfhpmjnbigmhklmmbgecoobifkmpa) Doesn't Work with Adguard DNS Protection
### Expected Behavior
Detect ProtonVPN Chrome Extension https://chrome.google.com/webstore/detail/proton-vpn-a-swiss-vpn-yo/jplgfhpmjnbigmhklmmbgecoobifkmpa is enabled, so temp disable Adguard DNS Protection.
|
1.0
|
Proton VPN Chrome Extension Doesn't Work with Adguard DNS Protection - ### AdGuard version
Extension
### Browser version
Edge 113.0.1774.57
### OS version
Windows 11 22H2 build 22621.1702
### Issue Details
Proton VPN Chrome Extension (https://chrome.google.com/webstore/detail/proton-vpn-a-swiss-vpn-yo/jplgfhpmjnbigmhklmmbgecoobifkmpa) Doesn't Work with Adguard DNS Protection
### Expected Behavior
Detect ProtonVPN Chrome Extension https://chrome.google.com/webstore/detail/proton-vpn-a-swiss-vpn-yo/jplgfhpmjnbigmhklmmbgecoobifkmpa is enabled, so temp disable Adguard DNS Protection.
|
non_infrastructure
|
proton vpn chrome extension doesn t work with adguard dns protection adguard version extension browser version edge os version windows build issue details proton vpn chrome extension doesn t work with adguard dns protection expected behavior detect protonvpn chrome extension is enabled so temp disable adguard dns protection
| 0
|
15,255
| 11,430,201,457
|
IssuesEvent
|
2020-02-04 09:38:39
|
ystia/yorc
|
https://api.github.com/repos/ystia/yorc
|
closed
|
Tosca public_ip_address attribute is wrongly set with private address for hosts pool computes
|
bug infrastructure/HostsPool
|
# Bug Report
## Description
Tosca public_ip_address attribute is wrongly set with private address for hosts pool computes
|
1.0
|
Tosca public_ip_address attribute is wrongly set with private address for hosts pool computes - # Bug Report
## Description
Tosca public_ip_address attribute is wrongly set with private address for hosts pool computes
|
infrastructure
|
tosca public ip address attribute is wrongly set with private address for hosts pool computes bug report description tosca public ip address attribute is wrongly set with private address for hosts pool computes
| 1
|
126,172
| 26,792,958,366
|
IssuesEvent
|
2023-02-01 09:51:26
|
eclipse/che
|
https://api.github.com/repos/eclipse/che
|
closed
|
Remove connection security token for Che-Code `main` endpoint
|
kind/task severity/P2 area/editor/vscode
|
### Is your task related to a problem? Please describe
VS Code used to require setting the connection security token.
Currently, it's optional and Che-Code doesn't use that by providing [the `--without-connection-token` startup parameter](https://github.com/che-incubator/che-code/blob/f9a955461d67010e26c102e08f26cefba713a5f7/build/scripts/entrypoint-volume.sh#L82).
But we still have the token specified in [Che-Code `main` endpoint](https://github.com/eclipse-che/che-plugin-registry/blob/760d0f3ccef48e69eb1f5b55c17070e2f968030a/che-editors.yaml#L523).
### Describe the solution you'd like
Remove `?tkn=eclipse-che` URL parameter from Che-Code `main` endpoint. It still used in the following places:
- https://github.com/eclipse-che/che-plugin-registry/blob/760d0f3ccef48e69eb1f5b55c17070e2f968030a/che-editors.yaml#L523
- https://github.com/eclipse-che/che-plugin-registry/blob/760d0f3ccef48e69eb1f5b55c17070e2f968030a/che-editors.yaml#L605
- https://github.com/redhat-developer/devspaces/blob/767b1ae4a5eb19bb3e3ed2a9c91320835233705d/dependencies/che-plugin-registry/che-editors.yaml#L313
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
|
1.0
|
Remove connection security token for Che-Code `main` endpoint - ### Is your task related to a problem? Please describe
VS Code used to require setting the connection security token.
Currently, it's optional and Che-Code doesn't use that by providing [the `--without-connection-token` startup parameter](https://github.com/che-incubator/che-code/blob/f9a955461d67010e26c102e08f26cefba713a5f7/build/scripts/entrypoint-volume.sh#L82).
But we still have the token specified in [Che-Code `main` endpoint](https://github.com/eclipse-che/che-plugin-registry/blob/760d0f3ccef48e69eb1f5b55c17070e2f968030a/che-editors.yaml#L523).
### Describe the solution you'd like
Remove `?tkn=eclipse-che` URL parameter from Che-Code `main` endpoint. It still used in the following places:
- https://github.com/eclipse-che/che-plugin-registry/blob/760d0f3ccef48e69eb1f5b55c17070e2f968030a/che-editors.yaml#L523
- https://github.com/eclipse-che/che-plugin-registry/blob/760d0f3ccef48e69eb1f5b55c17070e2f968030a/che-editors.yaml#L605
- https://github.com/redhat-developer/devspaces/blob/767b1ae4a5eb19bb3e3ed2a9c91320835233705d/dependencies/che-plugin-registry/che-editors.yaml#L313
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
|
non_infrastructure
|
remove connection security token for che code main endpoint is your task related to a problem please describe vs code used to require setting the connection security token currently it s optional and che code doesn t use that by providing but we still have the token specified in describe the solution you d like remove tkn eclipse che url parameter from che code main endpoint it still used in the following places describe alternatives you ve considered no response additional context no response
| 0
|
24,976
| 6,612,748,982
|
IssuesEvent
|
2017-09-20 06:10:48
|
PapirusDevelopmentTeam/papirus-icon-theme
|
https://api.github.com/repos/PapirusDevelopmentTeam/papirus-icon-theme
|
closed
|
Icon request: wallpaper_creator
|
completed hardcoded icon request
|
```desktop
[Desktop Entry]
Name=Wallpaper Creator
Comment=Create wallpapers for Komorebi
Keywords=wallpaper; settings; preferences;
Icon=/System/Resources/Komorebi/wallpaper_creator.svg
Exec=/System/Applications/komorebi-wallpaper-creator
Terminal=false
Type=Application
StartupNotify=true
Categories=GNOME;GTK;System;
X-GNOME-Autostart-enabled=false
```
- - -
**Icon name**: `komorebi`
|
1.0
|
Icon request: wallpaper_creator - ```desktop
[Desktop Entry]
Name=Wallpaper Creator
Comment=Create wallpapers for Komorebi
Keywords=wallpaper; settings; preferences;
Icon=/System/Resources/Komorebi/wallpaper_creator.svg
Exec=/System/Applications/komorebi-wallpaper-creator
Terminal=false
Type=Application
StartupNotify=true
Categories=GNOME;GTK;System;
X-GNOME-Autostart-enabled=false
```
- - -
**Icon name**: `komorebi`
|
non_infrastructure
|
icon request wallpaper creator desktop name wallpaper creator comment create wallpapers for komorebi keywords wallpaper settings preferences icon system resources komorebi wallpaper creator svg exec system applications komorebi wallpaper creator terminal false type application startupnotify true categories gnome gtk system x gnome autostart enabled false icon name komorebi
| 0
|
23,756
| 16,563,535,902
|
IssuesEvent
|
2021-05-29 01:38:10
|
onivim/oni2
|
https://api.github.com/repos/onivim/oni2
|
closed
|
Windows 10: esy bootstrap "hangs" on esy-autoconf
|
A-infrastructure bug
|
When building from source, running esy bootstrap appears to hang after building esy-autoconf. I waited about 10 minutes and then, assuming that it had failed, hit `ctrl+c` to kill the bootstrap process. This didn't kill bootstrap, but it did resume the build process. My hunch is that there was some kind of warning or dialog that isn't being displayed in the build output, but that's just a guess.
As an aside, the build process is slooooooow on windows 10. I've been trying to get it to build for almost an hour now, which is mostly due to the very long build times for each package (is this normal?). It's difficult to tell if a package build has hanged when some of them can take over five minutes to finish (at the moment I've been waiting for esy-skia to build for about 10 minutes and I have no idea if it failed or if I should go make lunch instead).
|
1.0
|
Windows 10: esy bootstrap "hangs" on esy-autoconf - When building from source, running esy bootstrap appears to hang after building esy-autoconf. I waited about 10 minutes and then, assuming that it had failed, hit `ctrl+c` to kill the bootstrap process. This didn't kill bootstrap, but it did resume the build process. My hunch is that there was some kind of warning or dialog that isn't being displayed in the build output, but that's just a guess.
As an aside, the build process is slooooooow on windows 10. I've been trying to get it to build for almost an hour now, which is mostly due to the very long build times for each package (is this normal?). It's difficult to tell if a package build has hanged when some of them can take over five minutes to finish (at the moment I've been waiting for esy-skia to build for about 10 minutes and I have no idea if it failed or if I should go make lunch instead).
|
infrastructure
|
windows esy bootstrap hangs on esy autoconf when building from source running esy bootstrap appears to hang after building esy autoconf i waited about minutes and then assuming that it had failed hit ctrl c to kill the bootstrap process this didn t kill bootstrap but it did resume the build process my hunch is that there was some kind of warning or dialog that isn t being displayed in the build output but that s just a guess as an aside the build process is slooooooow on windows i ve been trying to get it to build for almost an hour now which is mostly due to the very long build times for each package is this normal it s difficult to tell if a package build has hanged when some of them can take over five minutes to finish at the moment i ve been waiting for esy skia to build for about minutes and i have no idea if it failed or if i should go make lunch instead
| 1
|
18,221
| 12,837,121,770
|
IssuesEvent
|
2020-07-07 15:18:53
|
wellcomecollection/platform
|
https://api.github.com/repos/wellcomecollection/platform
|
closed
|
Several of the storage apps aren't scaling up/down properly
|
🐛 Bug 💸 Costs 📦 Storage service 🚧 Infrastructure
|
Checking the cluster just now, I see several services including the bag tagger which don't have any autoscaling configured. Should be a quick fix.
|
1.0
|
Several of the storage apps aren't scaling up/down properly - Checking the cluster just now, I see several services including the bag tagger which don't have any autoscaling configured. Should be a quick fix.
|
infrastructure
|
several of the storage apps aren t scaling up down properly checking the cluster just now i see several services including the bag tagger which don t have any autoscaling configured should be a quick fix
| 1
|
423,853
| 12,303,051,448
|
IssuesEvent
|
2020-05-11 18:01:03
|
initc3/HoneyBadgerMPC
|
https://api.github.com/repos/initc3/HoneyBadgerMPC
|
reopened
|
Move from travis-ci.org to travis-ci.com
|
maintenance priority:low
|
**Why?** There is currently on issue with getting the build status for pull requests:
> **GitHub status may not be posted on commits occasionally from builds using the legacy Services integration**
See full description of the status at https://www.traviscistatus.com/incidents/rx6fhs3wqcln
The incident report points out:
> The issue **only affects** those repositories using the **legacy** Services integration (i.e., all **.org** repositories and some .com ones), and only under some circumstances. **You can migrate your repositories to GitHub Apps on https://travis-ci.com/account/repositories.**
Open source projects can now ([since May 2018](https://docs.travis-ci.com/user/migrate/open-source-on-travis-ci-com/)) be managed under travis-ci.com and this may be a good opportunity or reason to perform the migration.
See https://docs.travis-ci.com/user/migrate/open-source-repository-migration for information on how to proceed.
|
1.0
|
Move from travis-ci.org to travis-ci.com - **Why?** There is currently on issue with getting the build status for pull requests:
> **GitHub status may not be posted on commits occasionally from builds using the legacy Services integration**
See full description of the status at https://www.traviscistatus.com/incidents/rx6fhs3wqcln
The incident report points out:
> The issue **only affects** those repositories using the **legacy** Services integration (i.e., all **.org** repositories and some .com ones), and only under some circumstances. **You can migrate your repositories to GitHub Apps on https://travis-ci.com/account/repositories.**
Open source projects can now ([since May 2018](https://docs.travis-ci.com/user/migrate/open-source-on-travis-ci-com/)) be managed under travis-ci.com and this may be a good opportunity or reason to perform the migration.
See https://docs.travis-ci.com/user/migrate/open-source-repository-migration for information on how to proceed.
|
non_infrastructure
|
move from travis ci org to travis ci com why there is currently on issue with getting the build status for pull requests github status may not be posted on commits occasionally from builds using the legacy services integration see full description of the status at the incident report points out the issue only affects those repositories using the legacy services integration i e all org repositories and some com ones and only under some circumstances you can migrate your repositories to github apps on open source projects can now be managed under travis ci com and this may be a good opportunity or reason to perform the migration see for information on how to proceed
| 0
|
23,398
| 16,108,556,680
|
IssuesEvent
|
2021-04-27 17:55:09
|
bootstrapworld/curriculum
|
https://api.github.com/repos/bootstrapworld/curriculum
|
opened
|
Try to preserve newlines inside sexp->code
|
Infrastructure
|
Use case: lessons/defining-functions-new/en-us/pages/pyret/create-contracts-examples-2.adoc
DORAI: report back on how painful this looks _first_. Do NOT go and implement it!
|
1.0
|
Try to preserve newlines inside sexp->code - Use case: lessons/defining-functions-new/en-us/pages/pyret/create-contracts-examples-2.adoc
DORAI: report back on how painful this looks _first_. Do NOT go and implement it!
|
infrastructure
|
try to preserve newlines inside sexp code use case lessons defining functions new en us pages pyret create contracts examples adoc dorai report back on how painful this looks first do not go and implement it
| 1
|
2,939
| 8,584,028,313
|
IssuesEvent
|
2018-11-13 21:29:08
|
poanetwork/blockscout
|
https://api.github.com/repos/poanetwork/blockscout
|
closed
|
Fix Parity Internal Transactions
|
bug :bug: client: parity in progress priority: high severity: 3 team: architecture
|
The `input` value is not currently being imported by the internal transactions fetcher. We should also check for other fields that may not be validated on import.
### Environment
* Client: Parity
* Fetcher: Internal Transactions
|
1.0
|
Fix Parity Internal Transactions - The `input` value is not currently being imported by the internal transactions fetcher. We should also check for other fields that may not be validated on import.
### Environment
* Client: Parity
* Fetcher: Internal Transactions
|
non_infrastructure
|
fix parity internal transactions the input value is not currently being imported by the internal transactions fetcher we should also check for other fields that may not be validated on import environment client parity fetcher internal transactions
| 0
|
26,818
| 20,747,324,308
|
IssuesEvent
|
2022-03-15 01:24:38
|
dotnet/project-system
|
https://api.github.com/repos/dotnet/project-system
|
opened
|
Consolidate build pipeline orgs and use consistent pipeline naming
|
Area-Infrastructure
|
Relates to: https://github.com/dotnet/project-system/issues/7915
This issue extends beyond this repo, but to all the repos our team owns. We own these repos:
- https://github.com/dotnet/project-system
- https://github.com/dotnet/project-system-tools
- https://github.com/dotnet/NuGet.BuildTasks
- https://github.com/dotnet/ProjFileTools
We currently use 2 different DevOps orgs (1 project within each org). They are:
- https://dev.azure.com/devdiv/DevDiv
- Org: `devdiv`
- Project: `DevDiv`
- https://dev.azure.com/dnceng/public
- Org: `dnceng`
- Project: `public`
The specific reason for this is they have different access settings: [private vs public](https://docs.microsoft.com/en-us/azure/devops/organizations/projects/about-projects#private-and-public-projects). The `DevDiv` project is **private** (aka *Enterprise*) and the `public` project is **public**. For our GitHub pull-request pipelines, we require a **public** project. For our build (signing, packaging, etc.), we require a **private** project.
As it currently stands, every project in the `devdiv` org is **private**. However, in the `dnceng` org, contains both a **public** (`public`) and **private** (`internal`) project. From my understanding, our Microsoft org, **.NET**, would be billed to the `dnceng` (DotNet Engineering) DevOps org. Technically speaking, the only thing that is required to be in the `devdiv` org is our insertion PRs to Visual Studio since the VS repo exists within that org. One restriction to that is the amount of *variable groups* we rely on in our pipelines to make them function. Since we create VS components, we rely on their variables. However, there might be similar variables in the `dnceng` org.
This issue would be to investigate if it is possible to consolidate the pipelines into the same org or if that is even worthwhile. Right now, the downside of using 2 orgs is:
- Different variable groups (for secrets primarily)
- Different pipeline images/image pools
- (Potentially) using resources that we aren't billed for
- Confusion when investigating infrastructure issues or documenting infrastructure
- Different naming and folder conventions for pipelines
This issue would also see consistent naming of pipelines. Here are the current names (and folders) of pipelines, separated by pipeline type and repo:
- GitHub PR build pipeline
- `project-system`: dotnet\project-system: [**unit-tests**](https://dev.azure.com/dnceng/public/_build?definitionId=406)
- `project-system-tools`: dotnet\project-system-tools: [**build**](https://dev.azure.com/dnceng/public/_build?definitionId=446)
- `NuGet.BuildTasks`: dotnet\NuGet.BuildTasks: [**dotnet.NuGet.BuildTasks-CI**](https://dev.azure.com/dnceng/public/_build?definitionId=567)
- `ProjFileTools`: *None*
- GitHub PR RichNav pipeline
- `project-system`: dotnet\project-system: [**project-system-richnav**](https://dev.azure.com/dnceng/public/_build?definitionId=910)
- `project-system-tools`: *None*
- `NuGet.BuildTasks`: *None*
- `ProjFileTools`: *None*
- Localization pipeline (after PR merge)
- `project-system`: dotnet\project-system: [**one-loc-build**](https://dev.azure.com/dnceng/public/_build?definitionId=981)
- `project-system-tools`: *None*
- `NuGet.BuildTasks`: *None*
- `ProjFileTools`: *None*
- Signed build/packaging pipeline (after PR merge)
- `project-system`: DotNet\project-system: [**DotNet-Project-System**](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=9675)
- `project-system-tools`: DotNet\project-system-tools: [**project-system-tools**](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=7294)
- `NuGet.BuildTasks`: *No Folder*: [**dotnet.NuGet.BuildTasks**](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=11797)
- `ProjFileTools`: *None*
- Compliance pipeline (after PR merge)
- `project-system`: DotNet\project-system: [**DotNet-Project-System-Compliance**](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=15013)
- `project-system-tools`: *None*
- `NuGet.BuildTasks`: *No Folder*: [**DotNet.NuGet.BuildTasks-Compliance**](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=15125)
- `ProjFileTools`: *None*
- VS Insertion release pipeline
- `project-system`: Managed Languages\Project System: [**Project System Insertion (main -> main)**](https://dev.azure.com/devdiv/DevDiv/_release?view=all&_a=releases&definitionId=1242)
- `project-system-tools`: *None*
- `NuGet.BuildTasks`: Managed Languages: [**Nuget.BuildTasks**](https://dev.azure.com/devdiv/DevDiv/_release?view=all&_a=releases&definitionId=1937)
- `ProjFileTools`: *None*
- *Additional pipelines*
- `project-system`: dotnet\project-system: [**integration-tests**](https://dev.azure.com/dnceng/public/_build?definitionId=417) (standard pipeline)
- `project-system`: Managed Languages\Project System: [**Project System - OptProf**](https://dev.azure.com/devdiv/DevDiv/_release?view=all&_a=releases&definitionId=3197) (release pipeline)
|
1.0
|
Consolidate build pipeline orgs and use consistent pipeline naming - Relates to: https://github.com/dotnet/project-system/issues/7915
This issue extends beyond this repo, but to all the repos our team owns. We own these repos:
- https://github.com/dotnet/project-system
- https://github.com/dotnet/project-system-tools
- https://github.com/dotnet/NuGet.BuildTasks
- https://github.com/dotnet/ProjFileTools
We currently use 2 different DevOps orgs (1 project within each org). They are:
- https://dev.azure.com/devdiv/DevDiv
- Org: `devdiv`
- Project: `DevDiv`
- https://dev.azure.com/dnceng/public
- Org: `dnceng`
- Project: `public`
The specific reason for this is they have different access settings: [private vs public](https://docs.microsoft.com/en-us/azure/devops/organizations/projects/about-projects#private-and-public-projects). The `DevDiv` project is **private** (aka *Enterprise*) and the `public` project is **public**. For our GitHub pull-request pipelines, we require a **public** project. For our build (signing, packaging, etc.), we require a **private** project.
As it currently stands, every project in the `devdiv` org is **private**. However, in the `dnceng` org, contains both a **public** (`public`) and **private** (`internal`) project. From my understanding, our Microsoft org, **.NET**, would be billed to the `dnceng` (DotNet Engineering) DevOps org. Technically speaking, the only thing that is required to be in the `devdiv` org is our insertion PRs to Visual Studio since the VS repo exists within that org. One restriction to that is the amount of *variable groups* we rely on in our pipelines to make them function. Since we create VS components, we rely on their variables. However, there might be similar variables in the `dnceng` org.
This issue would be to investigate if it is possible to consolidate the pipelines into the same org or if that is even worthwhile. Right now, the downside of using 2 orgs is:
- Different variable groups (for secrets primarily)
- Different pipeline images/image pools
- (Potentially) using resources that we aren't billed for
- Confusion when investigating infrastructure issues or documenting infrastructure
- Different naming and folder conventions for pipelines
This issue would also see consistent naming of pipelines. Here are the current names (and folders) of pipelines, separated by pipeline type and repo:
- GitHub PR build pipeline
- `project-system`: dotnet\project-system: [**unit-tests**](https://dev.azure.com/dnceng/public/_build?definitionId=406)
- `project-system-tools`: dotnet\project-system-tools: [**build**](https://dev.azure.com/dnceng/public/_build?definitionId=446)
- `NuGet.BuildTasks`: dotnet\NuGet.BuildTasks: [**dotnet.NuGet.BuildTasks-CI**](https://dev.azure.com/dnceng/public/_build?definitionId=567)
- `ProjFileTools`: *None*
- GitHub PR RichNav pipeline
- `project-system`: dotnet\project-system: [**project-system-richnav**](https://dev.azure.com/dnceng/public/_build?definitionId=910)
- `project-system-tools`: *None*
- `NuGet.BuildTasks`: *None*
- `ProjFileTools`: *None*
- Localization pipeline (after PR merge)
- `project-system`: dotnet\project-system: [**one-loc-build**](https://dev.azure.com/dnceng/public/_build?definitionId=981)
- `project-system-tools`: *None*
- `NuGet.BuildTasks`: *None*
- `ProjFileTools`: *None*
- Signed build/packaging pipeline (after PR merge)
- `project-system`: DotNet\project-system: [**DotNet-Project-System**](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=9675)
- `project-system-tools`: DotNet\project-system-tools: [**project-system-tools**](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=7294)
- `NuGet.BuildTasks`: *No Folder*: [**dotnet.NuGet.BuildTasks**](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=11797)
- `ProjFileTools`: *None*
- Compliance pipeline (after PR merge)
- `project-system`: DotNet\project-system: [**DotNet-Project-System-Compliance**](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=15013)
- `project-system-tools`: *None*
- `NuGet.BuildTasks`: *No Folder*: [**DotNet.NuGet.BuildTasks-Compliance**](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=15125)
- `ProjFileTools`: *None*
- VS Insertion release pipeline
- `project-system`: Managed Languages\Project System: [**Project System Insertion (main -> main)**](https://dev.azure.com/devdiv/DevDiv/_release?view=all&_a=releases&definitionId=1242)
- `project-system-tools`: *None*
- `NuGet.BuildTasks`: Managed Languages: [**Nuget.BuildTasks**](https://dev.azure.com/devdiv/DevDiv/_release?view=all&_a=releases&definitionId=1937)
- `ProjFileTools`: *None*
- *Additional pipelines*
- `project-system`: dotnet\project-system: [**integration-tests**](https://dev.azure.com/dnceng/public/_build?definitionId=417) (standard pipeline)
- `project-system`: Managed Languages\Project System: [**Project System - OptProf**](https://dev.azure.com/devdiv/DevDiv/_release?view=all&_a=releases&definitionId=3197) (release pipeline)
|
infrastructure
|
consolidate build pipeline orgs and use consistent pipeline naming relates to this issue extends beyond this repo but to all the repos our team owns we own these repos we currently use different devops orgs project within each org they are org devdiv project devdiv org dnceng project public the specific reason for this is they have different access settings the devdiv project is private aka enterprise and the public project is public for our github pull request pipelines we require a public project for our build signing packaging etc we require a private project as it currently stands every project in the devdiv org is private however in the dnceng org contains both a public public and private internal project from my understanding our microsoft org net would be billed to the dnceng dotnet engineering devops org technically speaking the only thing that is required to be in the devdiv org is our insertion prs to visual studio since the vs repo exists within that org one restriction to that is the amount of variable groups we rely on in our pipelines to make them function since we create vs components we rely on their variables however there might be similar variables in the dnceng org this issue would be to investigate if it is possible to consolidate the pipelines into the same org or if that is even worthwhile right now the downside of using orgs is different variable groups for secrets primarily different pipeline images image pools potentially using resources that we aren t billed for confusion when investigating infrastructure issues or documenting infrastructure different naming and folder conventions for pipelines this issue would also see consistent naming of pipelines here are the current names and folders of pipelines separated by pipeline type and repo github pr build pipeline project system dotnet project system project system tools dotnet project system tools nuget buildtasks dotnet nuget buildtasks projfiletools none github pr richnav pipeline project system dotnet project system project system tools none nuget buildtasks none projfiletools none localization pipeline after pr merge project system dotnet project system project system tools none nuget buildtasks none projfiletools none signed build packaging pipeline after pr merge project system dotnet project system project system tools dotnet project system tools nuget buildtasks no folder projfiletools none compliance pipeline after pr merge project system dotnet project system project system tools none nuget buildtasks no folder projfiletools none vs insertion release pipeline project system managed languages project system project system tools none nuget buildtasks managed languages projfiletools none additional pipelines project system dotnet project system standard pipeline project system managed languages project system release pipeline
| 1
|
533,833
| 15,603,822,137
|
IssuesEvent
|
2021-03-19 02:38:30
|
amqkv/SOEN-341
|
https://api.github.com/repos/amqkv/SOEN-341
|
closed
|
Access and display the comments
|
2 Front-End Low Risk Medium Priority Task
|
Epic: #5
**Description**
-Access the comments on the post
-Display those comments on the post
Notes:
-Modify the Post template to be able to display comments
-To access the comments on the post, have to wait for the back-end to be set up
|
1.0
|
Access and display the comments - Epic: #5
**Description**
-Access the comments on the post
-Display those comments on the post
Notes:
-Modify the Post template to be able to display comments
-To access the comments on the post, have to wait for the back-end to be set up
|
non_infrastructure
|
access and display the comments epic description access the comments on the post display those comments on the post notes modify the post template to be able to display comments to access the comments on the post have to wait for the back end to be set up
| 0
|
11,275
| 9,048,667,831
|
IssuesEvent
|
2019-02-12 01:03:13
|
servo/webrender
|
https://api.github.com/repos/servo/webrender
|
closed
|
Support processing the shaders at build time
|
area: infrastructure area: performance bugzilled type: bug
|
Shader compilation time is a big problem on all platforms. We hit this every time you open a new window.
On Windows I'm hoping that we can precompile the shaders to D3D bytecode. This seems to mostly fix the problem: https://bugzilla.mozilla.org/show_bug.cgi?id=1391159#c8.
On Mac we don't have any lower level ir and so need to use glsl. We also don't currently have a good way to reuse shaders across different windows. (This can be fixed by switching to CoreAnimation because we can bind the gl context to different IOSurfaces) I'm hoping that using a glsl optimizer will be sufficient to get things under control here.
On Linux the situation is similar to Mac, but we should be able to use glProgramBinary to reuse the shader between windows.
|
1.0
|
Support processing the shaders at build time - Shader compilation time is a big problem on all platforms. We hit this every time you open a new window.
On Windows I'm hoping that we can precompile the shaders to D3D bytecode. This seems to mostly fix the problem: https://bugzilla.mozilla.org/show_bug.cgi?id=1391159#c8.
On Mac we don't have any lower level ir and so need to use glsl. We also don't currently have a good way to reuse shaders across different windows. (This can be fixed by switching to CoreAnimation because we can bind the gl context to different IOSurfaces) I'm hoping that using a glsl optimizer will be sufficient to get things under control here.
On Linux the situation is similar to Mac, but we should be able to use glProgramBinary to reuse the shader between windows.
|
infrastructure
|
support processing the shaders at build time shader compilation time is a big problem on all platforms we hit this every time you open a new window on windows i m hoping that we can precompile the shaders to bytecode this seems to mostly fix the problem on mac we don t have any lower level ir and so need to use glsl we also don t currently have a good way to reuse shaders across different windows this can be fixed by switching to coreanimation because we can bind the gl context to different iosurfaces i m hoping that using a glsl optimizer will be sufficient to get things under control here on linux the situation is similar to mac but we should be able to use glprogrambinary to reuse the shader between windows
| 1
|
86,507
| 10,759,300,513
|
IssuesEvent
|
2019-10-31 16:23:42
|
carbon-design-system/carbon-for-ibm-website
|
https://api.github.com/repos/carbon-design-system/carbon-for-ibm-website
|
closed
|
Update the Cupcake website Guidelines/Grid page content
|
content design website: cupcake
|
**Is your feature request related to a problem? Please describe.**
Carbon [2x Grid](https://www.carbondesignsystem.com/guidelines/2x-grid/implementation) page content is updated and to not get our adopters confused, we need to update what we have.
**Describe the solution you'd like**
Update the Gird page content.
**Describe alternatives you've considered**
We can also update the content via markdowns.
**Additional context**
- Grid guideline was worked on via [issue 463](
https://app.zenhub.com/workspaces/ibmcom-library-5d449f3642eb1962336cbe52/issues/carbon-design-system/ibm-dotcom-library/463) in sprint 18.
|
1.0
|
Update the Cupcake website Guidelines/Grid page content - **Is your feature request related to a problem? Please describe.**
Carbon [2x Grid](https://www.carbondesignsystem.com/guidelines/2x-grid/implementation) page content is updated and to not get our adopters confused, we need to update what we have.
**Describe the solution you'd like**
Update the Gird page content.
**Describe alternatives you've considered**
We can also update the content via markdowns.
**Additional context**
- Grid guideline was worked on via [issue 463](
https://app.zenhub.com/workspaces/ibmcom-library-5d449f3642eb1962336cbe52/issues/carbon-design-system/ibm-dotcom-library/463) in sprint 18.
|
non_infrastructure
|
update the cupcake website guidelines grid page content is your feature request related to a problem please describe carbon page content is updated and to not get our adopters confused we need to update what we have describe the solution you d like update the gird page content describe alternatives you ve considered we can also update the content via markdowns additional context grid guideline was worked on via in sprint
| 0
|
31,702
| 26,022,685,996
|
IssuesEvent
|
2022-12-21 13:57:45
|
google/site-kit-wp
|
https://api.github.com/repos/google/site-kit-wp
|
opened
|
Use Storybook Actions addon to provide consistent monitoring of events triggered in stories.
|
P2 Type: Infrastructure
|
## Feature Description
Storybook provides the Actions addon, which allows automatic logging of events triggered in stories, via `args`. We should make use of this addon to provide a consistent way of logging events, including a UI rather than monitoring the JS console, and to reduce boilerplate.
See https://storybook.js.org/docs/6.3/react/essentials/actions
---------------
_Do not alter or remove anything below. The following sections will be managed by moderators only._
## Acceptance criteria
* <!-- One or more bullet points for acceptance criteria. -->
## Implementation Brief
* <!-- One or more bullet points for how to technically implement the feature. Make sure to include changes to Storybook and visual regression tests where relevant. -->
### Test Coverage
* <!-- One or more bullet points for how to implement automated tests to verify the feature works. -->
## QA Brief
* <!-- One or more bullet points for how to test that the feature works as expected. -->
## Changelog entry
* <!-- One sentence summarizing the PR, to be used in the changelog. -->
|
1.0
|
Use Storybook Actions addon to provide consistent monitoring of events triggered in stories. - ## Feature Description
Storybook provides the Actions addon, which allows automatic logging of events triggered in stories, via `args`. We should make use of this addon to provide a consistent way of logging events, including a UI rather than monitoring the JS console, and to reduce boilerplate.
See https://storybook.js.org/docs/6.3/react/essentials/actions
---------------
_Do not alter or remove anything below. The following sections will be managed by moderators only._
## Acceptance criteria
* <!-- One or more bullet points for acceptance criteria. -->
## Implementation Brief
* <!-- One or more bullet points for how to technically implement the feature. Make sure to include changes to Storybook and visual regression tests where relevant. -->
### Test Coverage
* <!-- One or more bullet points for how to implement automated tests to verify the feature works. -->
## QA Brief
* <!-- One or more bullet points for how to test that the feature works as expected. -->
## Changelog entry
* <!-- One sentence summarizing the PR, to be used in the changelog. -->
|
infrastructure
|
use storybook actions addon to provide consistent monitoring of events triggered in stories feature description storybook provides the actions addon which allows automatic logging of events triggered in stories via args we should make use of this addon to provide a consistent way of logging events including a ui rather than monitoring the js console and to reduce boilerplate see do not alter or remove anything below the following sections will be managed by moderators only acceptance criteria implementation brief test coverage qa brief changelog entry
| 1
|
271,759
| 8,489,052,574
|
IssuesEvent
|
2018-10-26 18:36:28
|
ualbertalib/Hydranorth2
|
https://api.github.com/repos/ualbertalib/Hydranorth2
|
closed
|
Evaluate whether or not we can tease out some shibd/omniauth integration to send back to community
|
priority:high
|
Evaluate whether or not we can tease out some shibd/omniauth integration that isn't site-specific that could be pushed back to the community. If we think there's anything there, float the idea by the community.
|
1.0
|
Evaluate whether or not we can tease out some shibd/omniauth integration to send back to community - Evaluate whether or not we can tease out some shibd/omniauth integration that isn't site-specific that could be pushed back to the community. If we think there's anything there, float the idea by the community.
|
non_infrastructure
|
evaluate whether or not we can tease out some shibd omniauth integration to send back to community evaluate whether or not we can tease out some shibd omniauth integration that isn t site specific that could be pushed back to the community if we think there s anything there float the idea by the community
| 0
|
13,391
| 22,952,328,200
|
IssuesEvent
|
2022-07-19 08:32:42
|
renovatebot/renovate
|
https://api.github.com/repos/renovatebot/renovate
|
closed
|
Renovate still create PRs against main after changing default branch
|
type:bug status:requirements priority-5-triage
|
### How are you running Renovate?
Mend Renovate hosted app on github.com
### If you're self-hosting Renovate, tell us what version of Renovate you run.
_No response_
### Please select which platform you are using if self-hosting.
_No response_
### If you're self-hosting Renovate, tell us what version of the platform you run.
_No response_
### Was this something which used to work for you, and then stopped?
I never saw this working
### Describe the bug
I have changed the default branch from `main` to `hubdle` and Renovate still creates the PR against main.
### Relevant debug logs
<details><summary>Logs</summary>
```
Copy/paste the relevant log(s) here, between the starting and ending backticks
```
</details>
### Have you created a minimal reproduction repository?
No reproduction repository
|
1.0
|
Renovate still create PRs against main after changing default branch - ### How are you running Renovate?
Mend Renovate hosted app on github.com
### If you're self-hosting Renovate, tell us what version of Renovate you run.
_No response_
### Please select which platform you are using if self-hosting.
_No response_
### If you're self-hosting Renovate, tell us what version of the platform you run.
_No response_
### Was this something which used to work for you, and then stopped?
I never saw this working
### Describe the bug
I have changed the default branch from `main` to `hubdle` and Renovate still creates the PR against main.
### Relevant debug logs
<details><summary>Logs</summary>
```
Copy/paste the relevant log(s) here, between the starting and ending backticks
```
</details>
### Have you created a minimal reproduction repository?
No reproduction repository
|
non_infrastructure
|
renovate still create prs against main after changing default branch how are you running renovate mend renovate hosted app on github com if you re self hosting renovate tell us what version of renovate you run no response please select which platform you are using if self hosting no response if you re self hosting renovate tell us what version of the platform you run no response was this something which used to work for you and then stopped i never saw this working describe the bug i have changed the default branch from main to hubdle and renovate still creates the pr against main relevant debug logs logs copy paste the relevant log s here between the starting and ending backticks have you created a minimal reproduction repository no reproduction repository
| 0
|
15,618
| 11,616,860,197
|
IssuesEvent
|
2020-02-26 16:21:36
|
department-of-veterans-affairs/va.gov-cms
|
https://api.github.com/repos/department-of-veterans-affairs/va.gov-cms
|
closed
|
Change githook to validate branch name as VACMS-issueId not VAGOV-issueId
|
Infrastructure Task
|
githook currently specifies
> Aborting commit. Your branch must start start with a VAGOV-* Jira issue number format, e.g. 'VAGOV-123 or VAGOV-123-issue-name. Use `git branch --move <VAGOV-000-new-name>` to rename.
it should specify VACMS instead of VAGOV, to help distinguish between CMS branches and other VAGOV work. The transition to Github seems like a good time to make this shift.
|
1.0
|
Change githook to validate branch name as VACMS-issueId not VAGOV-issueId - githook currently specifies
> Aborting commit. Your branch must start start with a VAGOV-* Jira issue number format, e.g. 'VAGOV-123 or VAGOV-123-issue-name. Use `git branch --move <VAGOV-000-new-name>` to rename.
it should specify VACMS instead of VAGOV, to help distinguish between CMS branches and other VAGOV work. The transition to Github seems like a good time to make this shift.
|
infrastructure
|
change githook to validate branch name as vacms issueid not vagov issueid githook currently specifies aborting commit your branch must start start with a vagov jira issue number format e g vagov or vagov issue name use git branch move to rename it should specify vacms instead of vagov to help distinguish between cms branches and other vagov work the transition to github seems like a good time to make this shift
| 1
|
27,663
| 11,541,700,954
|
IssuesEvent
|
2020-02-18 05:02:44
|
istio/istio
|
https://api.github.com/repos/istio/istio
|
closed
|
Missing cert mountpoint with Citadel, SDS and Vault CA
|
area/security lifecycle/stale
|
(NOTE: This is used to report product bugs:
To report a security vulnerability, please visit <https://istio.io/about/security-vulnerabilities/>
To ask questions about how to use Istio, please visit <https://discuss.istio.io>
)
**Bug description**
I've deployed K8S 1.13 in EKS along with Istio 1.2.4 using Hashicorp Vault 1.0.0 to issue certificates however after following all of the mTLS and Vault documentation the istio-proxy sidecars for the sample bookinfo and httpbin deployments do not get certificates. Vault is setup correctly.
> 2019-08-22T01:24:47.889739Z info Monitored certs: []string{"/etc/certs/cert-chain.pem", "/etc/certs/key.pem", "/etc/certs/root-cert.pem"}
> 2019-08-22T01:24:47.889781Z info PilotSAN []string(nil)
> 2019-08-22T01:24:47.891394Z info Opening status port 15020
> 2019-08-22T01:24:47.891656Z info Starting proxy agent
> 2019-08-22T01:24:47.891817Z warn watching /etc/certs encountered an error no such file or directory
> 2019-08-22T01:24:47.891826Z info Received new config, resetting budget
>
On the node agent:
> 2019-08-22T00:56:39.154111Z info created Vault client for Vault address: http://xxxxx:8200, TLS: true
> 2019-08-22T00:56:39.284102Z info SDS gRPC server for workload UDS starts, listening on "/var/run/sds/uds_path"
> 2019-08-22T00:56:39.284187Z info Start SDS grpc server
> 2019-08-22T00:56:59.975030Z info Root cert has changed
Also logs from httpbin istio-proxy sidecar:
> 2019-08-22T19:57:16.388206Z info Monitored certs: []string{"/etc/certs/cert-chain.pem", "/etc/certs/key.pem", "/etc/certs/root-cert.pem"}
> 2019-08-22T19:57:16.388217Z info PilotSAN []string(nil)
> 2019-08-22T19:57:16.388282Z info Opening status port 15020
> 2019-08-22T19:57:16.388319Z info Starting proxy agent
> 2019-08-22T19:57:16.388414Z warn watching /etc/certs encountered an error no such file or directory
> 2019-08-22T19:57:16.388421Z info Received new config, resetting budget
**Affected product area (please put an X in all that apply)**
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[x ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
**Expected behavior**
I would expect the normal behavior as per the documentation. Certificates should be issued from Vault CA and provisioned to envoy sidecars.
**Steps to reproduce the bug**
**Version (include the output of `istioctl version --remote` and `kubectl version`)**
**istioctl version --remote**
> client version: 1.2.4
> citadel version: 1.2.4
> egressgateway version: 94746ccd404a8e056483dd02e4e478097b950da6-dirty
> galley version: 1.2.4
> ingressgateway version: 94746ccd404a8e056483dd02e4e478097b950da6-dirty
> nodeagent version:
> nodeagent version:
> pilot version: 1.2.4
> policy version: 1.2.4
> sidecar-injector version: 1.2.4
> telemetry version: 1.2.4
**kubectl version**
> Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T11:13:54Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
> Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.8-eks-a977ba", GitCommit:"a977bab148535ec195f12edc8720913c7b943f9c", GitTreeState:"clean", BuildDate:"2019-07-29T20:47:04Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
**How was Istio installed?**
Followed this doc: https://istio.io/docs/tasks/security/vault-ca/
**Environment where bug was observed (cloud vendor, OS, etc)**
EKS in AWS
Additionally, please consider attaching a [cluster state archive](http://istio.io/help/bugs/#generating-a-cluster-state-archive) by attaching
the dump file to this issue.
|
True
|
Missing cert mountpoint with Citadel, SDS and Vault CA - (NOTE: This is used to report product bugs:
To report a security vulnerability, please visit <https://istio.io/about/security-vulnerabilities/>
To ask questions about how to use Istio, please visit <https://discuss.istio.io>
)
**Bug description**
I've deployed K8S 1.13 in EKS along with Istio 1.2.4 using Hashicorp Vault 1.0.0 to issue certificates however after following all of the mTLS and Vault documentation the istio-proxy sidecars for the sample bookinfo and httpbin deployments do not get certificates. Vault is setup correctly.
> 2019-08-22T01:24:47.889739Z info Monitored certs: []string{"/etc/certs/cert-chain.pem", "/etc/certs/key.pem", "/etc/certs/root-cert.pem"}
> 2019-08-22T01:24:47.889781Z info PilotSAN []string(nil)
> 2019-08-22T01:24:47.891394Z info Opening status port 15020
> 2019-08-22T01:24:47.891656Z info Starting proxy agent
> 2019-08-22T01:24:47.891817Z warn watching /etc/certs encountered an error no such file or directory
> 2019-08-22T01:24:47.891826Z info Received new config, resetting budget
>
On the node agent:
> 2019-08-22T00:56:39.154111Z info created Vault client for Vault address: http://xxxxx:8200, TLS: true
> 2019-08-22T00:56:39.284102Z info SDS gRPC server for workload UDS starts, listening on "/var/run/sds/uds_path"
> 2019-08-22T00:56:39.284187Z info Start SDS grpc server
> 2019-08-22T00:56:59.975030Z info Root cert has changed
Also logs from httpbin istio-proxy sidecar:
> 2019-08-22T19:57:16.388206Z info Monitored certs: []string{"/etc/certs/cert-chain.pem", "/etc/certs/key.pem", "/etc/certs/root-cert.pem"}
> 2019-08-22T19:57:16.388217Z info PilotSAN []string(nil)
> 2019-08-22T19:57:16.388282Z info Opening status port 15020
> 2019-08-22T19:57:16.388319Z info Starting proxy agent
> 2019-08-22T19:57:16.388414Z warn watching /etc/certs encountered an error no such file or directory
> 2019-08-22T19:57:16.388421Z info Received new config, resetting budget
**Affected product area (please put an X in all that apply)**
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[x ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
**Expected behavior**
I would expect the normal behavior as per the documentation. Certificates should be issued from Vault CA and provisioned to envoy sidecars.
**Steps to reproduce the bug**
**Version (include the output of `istioctl version --remote` and `kubectl version`)**
**istioctl version --remote**
> client version: 1.2.4
> citadel version: 1.2.4
> egressgateway version: 94746ccd404a8e056483dd02e4e478097b950da6-dirty
> galley version: 1.2.4
> ingressgateway version: 94746ccd404a8e056483dd02e4e478097b950da6-dirty
> nodeagent version:
> nodeagent version:
> pilot version: 1.2.4
> policy version: 1.2.4
> sidecar-injector version: 1.2.4
> telemetry version: 1.2.4
**kubectl version**
> Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T11:13:54Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
> Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.8-eks-a977ba", GitCommit:"a977bab148535ec195f12edc8720913c7b943f9c", GitTreeState:"clean", BuildDate:"2019-07-29T20:47:04Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
**How was Istio installed?**
Followed this doc: https://istio.io/docs/tasks/security/vault-ca/
**Environment where bug was observed (cloud vendor, OS, etc)**
EKS in AWS
Additionally, please consider attaching a [cluster state archive](http://istio.io/help/bugs/#generating-a-cluster-state-archive) by attaching
the dump file to this issue.
|
non_infrastructure
|
missing cert mountpoint with citadel sds and vault ca note this is used to report product bugs to report a security vulnerability please visit to ask questions about how to use istio please visit bug description i ve deployed in eks along with istio using hashicorp vault to issue certificates however after following all of the mtls and vault documentation the istio proxy sidecars for the sample bookinfo and httpbin deployments do not get certificates vault is setup correctly info monitored certs string etc certs cert chain pem etc certs key pem etc certs root cert pem info pilotsan string nil info opening status port info starting proxy agent warn watching etc certs encountered an error no such file or directory info received new config resetting budget on the node agent info created vault client for vault address tls true info sds grpc server for workload uds starts listening on var run sds uds path info start sds grpc server info root cert has changed also logs from httpbin istio proxy sidecar info monitored certs string etc certs cert chain pem etc certs key pem etc certs root cert pem info pilotsan string nil info opening status port info starting proxy agent warn watching etc certs encountered an error no such file or directory info received new config resetting budget affected product area please put an x in all that apply configuration infrastructure docs installation networking performance and scalability policies and telemetry security test and release user experience developer infrastructure expected behavior i would expect the normal behavior as per the documentation certificates should be issued from vault ca and provisioned to envoy sidecars steps to reproduce the bug version include the output of istioctl version remote and kubectl version istioctl version remote client version citadel version egressgateway version dirty galley version ingressgateway version dirty nodeagent version nodeagent version pilot version policy version sidecar injector version telemetry version kubectl version client version version info major minor gitversion gitcommit gittreestate clean builddate goversion compiler gc platform linux server version version info major minor gitversion eks gitcommit gittreestate clean builddate goversion compiler gc platform linux how was istio installed followed this doc environment where bug was observed cloud vendor os etc eks in aws additionally please consider attaching a by attaching the dump file to this issue
| 0
|
411,812
| 27,831,301,760
|
IssuesEvent
|
2023-03-20 05:16:08
|
se6-njit/mywebclass-simulation-intermediate
|
https://api.github.com/repos/se6-njit/mywebclass-simulation-intermediate
|
closed
|
Creating a new task for backend testing
|
documentation points: 1 priority: low
|
As the quality assurance and sire reliability engineer. I am creating a task to document how to do backend testing.
Link: https://github.com/se6-njit/mywebclass-simulation-intermediate/blob/master/team_productivity_log.md
|
1.0
|
Creating a new task for backend testing - As the quality assurance and sire reliability engineer. I am creating a task to document how to do backend testing.
Link: https://github.com/se6-njit/mywebclass-simulation-intermediate/blob/master/team_productivity_log.md
|
non_infrastructure
|
creating a new task for backend testing as the quality assurance and sire reliability engineer i am creating a task to document how to do backend testing link
| 0
|
30,440
| 24,824,711,201
|
IssuesEvent
|
2022-10-25 19:32:37
|
zowe/zlux
|
https://api.github.com/repos/zowe/zlux
|
closed
|
Customization of clock on launchbar
|
Client Infrastructure stale-reopen-if-needed
|
Rather than just use localization detection to determine clock format, people may want to:
1) choose a different format perhaps from a different localization
2) show or hide seconds
3) show or hide date
4) show or hide day
5) open a calendar
|
1.0
|
Customization of clock on launchbar - Rather than just use localization detection to determine clock format, people may want to:
1) choose a different format perhaps from a different localization
2) show or hide seconds
3) show or hide date
4) show or hide day
5) open a calendar
|
infrastructure
|
customization of clock on launchbar rather than just use localization detection to determine clock format people may want to choose a different format perhaps from a different localization show or hide seconds show or hide date show or hide day open a calendar
| 1
|
11,076
| 8,914,861,389
|
IssuesEvent
|
2019-01-19 00:08:08
|
LibreTime/libretime
|
https://api.github.com/repos/LibreTime/libretime
|
closed
|
Problem: Vagrant base boxes lacks libvirt support for ubuntu xenial
|
feature-request infrastructure
|
The Bento base Ubuntu Xenial box does not support libvirt. This causes issues with Debian vagrant boxes, as this is the default provider. This could also affect the other base boxes, but I still need to check...
Documentation of how to use Vagrant for LT also needs updating:
http://libretime.org/vagrant/
https://github.com/LibreTime/libretime/wiki/Vagrant-Developer-Setup (to be merged into the website docs)
|
1.0
|
Problem: Vagrant base boxes lacks libvirt support for ubuntu xenial - The Bento base Ubuntu Xenial box does not support libvirt. This causes issues with Debian vagrant boxes, as this is the default provider. This could also affect the other base boxes, but I still need to check...
Documentation of how to use Vagrant for LT also needs updating:
http://libretime.org/vagrant/
https://github.com/LibreTime/libretime/wiki/Vagrant-Developer-Setup (to be merged into the website docs)
|
infrastructure
|
problem vagrant base boxes lacks libvirt support for ubuntu xenial the bento base ubuntu xenial box does not support libvirt this causes issues with debian vagrant boxes as this is the default provider this could also affect the other base boxes but i still need to check documentation of how to use vagrant for lt also needs updating to be merged into the website docs
| 1
|
201,149
| 22,946,812,095
|
IssuesEvent
|
2022-07-19 01:23:34
|
Chiencc/Spring5-Login_Prioritize-Sample
|
https://api.github.com/repos/Chiencc/Spring5-Login_Prioritize-Sample
|
closed
|
CVE-2019-14379 (High) detected in jackson-databind-2.9.6.jar - autoclosed
|
security vulnerability
|
## CVE-2019-14379 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.6.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.6/jackson-databind-2.9.6.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.0.3.RELEASE.jar (Root Library)
- spring-boot-starter-json-2.0.3.RELEASE.jar
- :x: **jackson-databind-2.9.6.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/Spring5-Login_Prioritize-Sample/commit/0c3ecc11668698a0cc14027974dc1381483dcfa8">0c3ecc11668698a0cc14027974dc1381483dcfa8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
SubTypeValidator.java in FasterXML jackson-databind before 2.9.9.2 mishandles default typing when ehcache is used (because of net.sf.ehcache.transaction.manager.DefaultTransactionManagerLookup), leading to remote code execution.
<p>Publish Date: 2019-07-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14379>CVE-2019-14379</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14379">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14379</a></p>
<p>Release Date: 2019-07-29</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.9.9.2</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.1.10.RELEASE</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-14379 (High) detected in jackson-databind-2.9.6.jar - autoclosed - ## CVE-2019-14379 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.6.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.6/jackson-databind-2.9.6.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.0.3.RELEASE.jar (Root Library)
- spring-boot-starter-json-2.0.3.RELEASE.jar
- :x: **jackson-databind-2.9.6.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/Spring5-Login_Prioritize-Sample/commit/0c3ecc11668698a0cc14027974dc1381483dcfa8">0c3ecc11668698a0cc14027974dc1381483dcfa8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
SubTypeValidator.java in FasterXML jackson-databind before 2.9.9.2 mishandles default typing when ehcache is used (because of net.sf.ehcache.transaction.manager.DefaultTransactionManagerLookup), leading to remote code execution.
<p>Publish Date: 2019-07-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14379>CVE-2019-14379</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14379">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14379</a></p>
<p>Release Date: 2019-07-29</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.9.9.2</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.1.10.RELEASE</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 high detected in jackson databind jar autoclosed cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy spring boot starter web release jar root library spring boot starter json release jar x jackson databind jar vulnerable library found in head commit a href found in base branch master vulnerability details subtypevalidator java in fasterxml jackson databind before mishandles default typing when ehcache is used because of net sf ehcache transaction manager defaulttransactionmanagerlookup leading to remote code execution publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution com fasterxml jackson core jackson databind direct dependency fix resolution org springframework boot spring boot starter web release step up your open source security game with whitesource
| 0
|
18,502
| 13,039,377,146
|
IssuesEvent
|
2020-07-28 16:38:52
|
intel/dffml
|
https://api.github.com/repos/intel/dffml
|
opened
|
ci: TensorFlow doesn't work with numpy
|
bug kind/infrastructure
|
```
2020-07-27T19:25:00.0718202Z pkg_resources.ContextualVersionConflict: (numpy 1.19.1 (/usr/share/miniconda/lib/python3.7/site-packages), Requirement.parse('numpy<1.19.0,>=1.16.0'), {'tensorflow'})
```
Temporary fix: Pin TensorFlow to 2.2.0
|
1.0
|
ci: TensorFlow doesn't work with numpy - ```
2020-07-27T19:25:00.0718202Z pkg_resources.ContextualVersionConflict: (numpy 1.19.1 (/usr/share/miniconda/lib/python3.7/site-packages), Requirement.parse('numpy<1.19.0,>=1.16.0'), {'tensorflow'})
```
Temporary fix: Pin TensorFlow to 2.2.0
|
infrastructure
|
ci tensorflow doesn t work with numpy pkg resources contextualversionconflict numpy usr share miniconda lib site packages requirement parse numpy tensorflow temporary fix pin tensorflow to
| 1
|
51,520
| 12,743,305,095
|
IssuesEvent
|
2020-06-26 10:08:03
|
cake-build/frosting
|
https://api.github.com/repos/cake-build/frosting
|
closed
|
Fix iconUrl and licenseUrl in nuget packages
|
build help wanted
|
- Cake.Frosting
- [ ] icon
- Cake.Frosting.Template
- [ ] licence
- [ ] icon
To address:
```diff
- WARNING: The <iconUrl> element is deprecated.
- Consider using the <icon> element instead. https://aka.ms/deprecateIconUrl
- WARNING: The <licenseUrl> element is deprecated.
- Consider using the <license> element instead. Learn more: https://aka.ms/deprecateLicenseUrl.
```
|
1.0
|
Fix iconUrl and licenseUrl in nuget packages - - Cake.Frosting
- [ ] icon
- Cake.Frosting.Template
- [ ] licence
- [ ] icon
To address:
```diff
- WARNING: The <iconUrl> element is deprecated.
- Consider using the <icon> element instead. https://aka.ms/deprecateIconUrl
- WARNING: The <licenseUrl> element is deprecated.
- Consider using the <license> element instead. Learn more: https://aka.ms/deprecateLicenseUrl.
```
|
non_infrastructure
|
fix iconurl and licenseurl in nuget packages cake frosting icon cake frosting template licence icon to address diff warning the element is deprecated consider using the element instead warning the element is deprecated consider using the element instead learn more
| 0
|
30,665
| 24,985,552,818
|
IssuesEvent
|
2022-11-02 14:50:10
|
OpenLiberty/openliberty.io
|
https://api.github.com/repos/OpenLiberty/openliberty.io
|
closed
|
Build logs are not enough to triage failures
|
infrastructure
|
The container based builds are failing and there is not enough logs triage the failure.
Due to the build having scripts calling scripts, I suspect the error is not being surfaced to the top.
```
...
/root/.nvm/versions/node/v12.13.0/lib
└── npm@6.12.0
Total execution time for installing Node: '00:00:09'
Now using node v18.12.0 (npm v)
npm analysis during build
node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by node)
node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by node)
node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by node)
The command '/bin/bash -c $BUILD_SCRIPTS_DIR/docs_part_1.sh' returned a non-zero code: 1
Step failed
```
|
1.0
|
Build logs are not enough to triage failures - The container based builds are failing and there is not enough logs triage the failure.
Due to the build having scripts calling scripts, I suspect the error is not being surfaced to the top.
```
...
/root/.nvm/versions/node/v12.13.0/lib
└── npm@6.12.0
Total execution time for installing Node: '00:00:09'
Now using node v18.12.0 (npm v)
npm analysis during build
node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by node)
node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by node)
node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by node)
The command '/bin/bash -c $BUILD_SCRIPTS_DIR/docs_part_1.sh' returned a non-zero code: 1
Step failed
```
|
infrastructure
|
build logs are not enough to triage failures the container based builds are failing and there is not enough logs triage the failure due to the build having scripts calling scripts i suspect the error is not being surfaced to the top root nvm versions node lib └── npm total execution time for installing node now using node npm v npm analysis during build node lib linux gnu libm so version glibc not found required by node node lib linux gnu libc so version glibc not found required by node node lib linux gnu libc so version glibc not found required by node the command bin bash c build scripts dir docs part sh returned a non zero code step failed
| 1
|
27,182
| 4,287,113,496
|
IssuesEvent
|
2016-07-16 15:01:00
|
NorthBridge/nexus-community
|
https://api.github.com/repos/NorthBridge/nexus-community
|
closed
|
Using the guest pass and entering an email in the Name field causes an XML error.
|
priority 2 ready to test
|
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<response>
<returncode>FAILED</returncode>
<messageKey>missingParamFullName</messageKey>
<message>
You must specify a name for the attendee who will be joining the meeting.
</message>
</response>
|
1.0
|
Using the guest pass and entering an email in the Name field causes an XML error. - This XML file does not appear to have any style information associated with it. The document tree is shown below.
<response>
<returncode>FAILED</returncode>
<messageKey>missingParamFullName</messageKey>
<message>
You must specify a name for the attendee who will be joining the meeting.
</message>
</response>
|
non_infrastructure
|
using the guest pass and entering an email in the name field causes an xml error this xml file does not appear to have any style information associated with it the document tree is shown below failed missingparamfullname you must specify a name for the attendee who will be joining the meeting
| 0
|
69,588
| 15,017,212,036
|
IssuesEvent
|
2021-02-01 10:33:30
|
dileepa-adl/asais
|
https://api.github.com/repos/dileepa-adl/asais
|
closed
|
Link all the created vulnerabilities to the relevant behaviours
|
enhancement security ext
|
Link all the created vulnerabilities to the relevant behaviour based on the diagrams from the VM
|
True
|
Link all the created vulnerabilities to the relevant behaviours - Link all the created vulnerabilities to the relevant behaviour based on the diagrams from the VM
|
non_infrastructure
|
link all the created vulnerabilities to the relevant behaviours link all the created vulnerabilities to the relevant behaviour based on the diagrams from the vm
| 0
|
35,342
| 31,022,465,857
|
IssuesEvent
|
2023-08-10 06:45:45
|
dotnet/runtime
|
https://api.github.com/repos/dotnet/runtime
|
closed
|
Merged tests progress message looks broken
|
area-Infrastructure-coreclr
|
Looks like it always prints:
```
06:06:17.190 Running test: JIT/Directed/StructPromote/Unsafe/AccessInvalidFieldOffset/AccessInvalidFieldOffset.dll
HH:mm:ssfff Passed test: 1
```
Shouldn't it print something like:
```
06:06:17.200 Passed test: JIT/Directed/StructPromote/Unsafe/AccessInvalidFieldOffset/AccessInvalidFieldOffset.dll
```
?
|
1.0
|
Merged tests progress message looks broken - Looks like it always prints:
```
06:06:17.190 Running test: JIT/Directed/StructPromote/Unsafe/AccessInvalidFieldOffset/AccessInvalidFieldOffset.dll
HH:mm:ssfff Passed test: 1
```
Shouldn't it print something like:
```
06:06:17.200 Passed test: JIT/Directed/StructPromote/Unsafe/AccessInvalidFieldOffset/AccessInvalidFieldOffset.dll
```
?
|
infrastructure
|
merged tests progress message looks broken looks like it always prints running test jit directed structpromote unsafe accessinvalidfieldoffset accessinvalidfieldoffset dll hh mm ssfff passed test shouldn t it print something like passed test jit directed structpromote unsafe accessinvalidfieldoffset accessinvalidfieldoffset dll
| 1
|
28,220
| 23,095,247,290
|
IssuesEvent
|
2022-07-26 18:51:41
|
google/docsy
|
https://api.github.com/repos/google/docsy
|
opened
|
Offer Docsy as a single Hugo Module
|
infrastructure module
|
The intent would be to **streamline use of Docsy for Hugo Module users**, something which (IMHO) makes sense to do now that [Git submodules]() were removed in [0.4.0](https://github.com/google/docsy/blob/main/CHANGELOG.md#040), and NPM-package support is available (#949).
@deining - I can't find the thread, but at some point we discussed the possibility of eliminating the `dependencies` module, which was introduced as a means of addressing:
- #848
This issue is to record that intent, and offer a place for discussing it.
|
1.0
|
Offer Docsy as a single Hugo Module - The intent would be to **streamline use of Docsy for Hugo Module users**, something which (IMHO) makes sense to do now that [Git submodules]() were removed in [0.4.0](https://github.com/google/docsy/blob/main/CHANGELOG.md#040), and NPM-package support is available (#949).
@deining - I can't find the thread, but at some point we discussed the possibility of eliminating the `dependencies` module, which was introduced as a means of addressing:
- #848
This issue is to record that intent, and offer a place for discussing it.
|
infrastructure
|
offer docsy as a single hugo module the intent would be to streamline use of docsy for hugo module users something which imho makes sense to do now that were removed in and npm package support is available deining i can t find the thread but at some point we discussed the possibility of eliminating the dependencies module which was introduced as a means of addressing this issue is to record that intent and offer a place for discussing it
| 1
|
22,833
| 15,554,117,217
|
IssuesEvent
|
2021-03-16 03:03:33
|
astropy/photutils
|
https://api.github.com/repos/astropy/photutils
|
closed
|
MNT: Rename default branch from master to main
|
infrastructure
|
Please rename your default branch from `master` to `main` as part of astropy/astropy-project#151 , preferably by 2021-03-22. Also a friendly reminder to check documentation, workflows, etc., and update them accordingly. Please don't forget to communicate this change to your users and stakeholders. To summarize:
- [x] Rename branch from `master` to `main`, preferably by 2021-03-22.
- [x] Update documentation, workflows, etc., accordingly. -- See #1178
- [ ] Communicate this change to your users and stakeholders.
Once this is taken care of, you may close this issue.
*This is an automated issue. If this is opened in error, please let @pllim know!*
|
1.0
|
MNT: Rename default branch from master to main - Please rename your default branch from `master` to `main` as part of astropy/astropy-project#151 , preferably by 2021-03-22. Also a friendly reminder to check documentation, workflows, etc., and update them accordingly. Please don't forget to communicate this change to your users and stakeholders. To summarize:
- [x] Rename branch from `master` to `main`, preferably by 2021-03-22.
- [x] Update documentation, workflows, etc., accordingly. -- See #1178
- [ ] Communicate this change to your users and stakeholders.
Once this is taken care of, you may close this issue.
*This is an automated issue. If this is opened in error, please let @pllim know!*
|
infrastructure
|
mnt rename default branch from master to main please rename your default branch from master to main as part of astropy astropy project preferably by also a friendly reminder to check documentation workflows etc and update them accordingly please don t forget to communicate this change to your users and stakeholders to summarize rename branch from master to main preferably by update documentation workflows etc accordingly see communicate this change to your users and stakeholders once this is taken care of you may close this issue this is an automated issue if this is opened in error please let pllim know
| 1
|
75,546
| 15,434,110,318
|
IssuesEvent
|
2021-03-07 01:22:34
|
kadirselcuk/sanity-nextjs-landing-pages
|
https://api.github.com/repos/kadirselcuk/sanity-nextjs-landing-pages
|
opened
|
CVE-2021-27515 (Medium) detected in url-parse-1.4.7.tgz
|
security vulnerability
|
## CVE-2021-27515 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>url-parse-1.4.7.tgz</b></p></summary>
<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href="https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz">https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz</a></p>
<p>Path to dependency file: sanity-nextjs-landing-pages/studio/package.json</p>
<p>Path to vulnerable library: sanity-nextjs-landing-pages/studio/node_modules/url-parse/package.json,sanity-nextjs-landing-pages/web/node_modules/url-parse/package.json</p>
<p>
Dependency Hierarchy:
- client-2.1.0.tgz (Root Library)
- get-it-5.0.3.tgz
- :x: **url-parse-1.4.7.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kadirselcuk/sanity-nextjs-landing-pages/commit/bc6ec564f0e4906fb1e6248504c4f99b34941cd1">bc6ec564f0e4906fb1e6248504c4f99b34941cd1</a></p>
<p>Found in base branch: <b>main</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>
url-parse before 1.5.0 mishandles certain uses of backslash such as http:\/ and interprets the URI as a relative path.
<p>Publish Date: 2021-02-22
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-27515>CVE-2021-27515</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-27515">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27515</a></p>
<p>Release Date: 2021-02-22</p>
<p>Fix Resolution: 1.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2021-27515 (Medium) detected in url-parse-1.4.7.tgz - ## CVE-2021-27515 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>url-parse-1.4.7.tgz</b></p></summary>
<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href="https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz">https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz</a></p>
<p>Path to dependency file: sanity-nextjs-landing-pages/studio/package.json</p>
<p>Path to vulnerable library: sanity-nextjs-landing-pages/studio/node_modules/url-parse/package.json,sanity-nextjs-landing-pages/web/node_modules/url-parse/package.json</p>
<p>
Dependency Hierarchy:
- client-2.1.0.tgz (Root Library)
- get-it-5.0.3.tgz
- :x: **url-parse-1.4.7.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kadirselcuk/sanity-nextjs-landing-pages/commit/bc6ec564f0e4906fb1e6248504c4f99b34941cd1">bc6ec564f0e4906fb1e6248504c4f99b34941cd1</a></p>
<p>Found in base branch: <b>main</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>
url-parse before 1.5.0 mishandles certain uses of backslash such as http:\/ and interprets the URI as a relative path.
<p>Publish Date: 2021-02-22
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-27515>CVE-2021-27515</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-27515">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27515</a></p>
<p>Release Date: 2021-02-22</p>
<p>Fix Resolution: 1.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_infrastructure
|
cve medium detected in url parse tgz cve medium severity vulnerability vulnerable library url parse tgz small footprint url parser that works seamlessly across node js and browser environments library home page a href path to dependency file sanity nextjs landing pages studio package json path to vulnerable library sanity nextjs landing pages studio node modules url parse package json sanity nextjs landing pages web node modules url parse package json dependency hierarchy client tgz root library get it tgz x url parse tgz vulnerable library found in head commit a href found in base branch main vulnerability details url parse before mishandles certain uses of backslash such as http and interprets the uri as a relative path publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
27,822
| 22,360,071,187
|
IssuesEvent
|
2022-06-15 19:32:31
|
WordPress/performance
|
https://api.github.com/repos/WordPress/performance
|
closed
|
Use `wp_filesize` instead of `filesize` if available
|
[Type] Enhancement Infrastructure Good First Issue
|
WordPress 6.0 introduced the `wp_filesize()` function which should be used in favor of PHP's `filesize()` going forward. We should use it in this plugin where available.
Since we currently support WordPress 5.8 and 5.9 as well, it's probably not worth bumping up the requirement just for that. I suggest we instead create a backward compatibility layer. Maybe the easiest approach would be to implement a "polyfill", where we re-implement `wp_filesize()` in the main plugin file if the function does not exist (yet).
We can then update all module code that calls `filesize()` to instead unconditionally call `wp_filesize()`.
|
1.0
|
Use `wp_filesize` instead of `filesize` if available - WordPress 6.0 introduced the `wp_filesize()` function which should be used in favor of PHP's `filesize()` going forward. We should use it in this plugin where available.
Since we currently support WordPress 5.8 and 5.9 as well, it's probably not worth bumping up the requirement just for that. I suggest we instead create a backward compatibility layer. Maybe the easiest approach would be to implement a "polyfill", where we re-implement `wp_filesize()` in the main plugin file if the function does not exist (yet).
We can then update all module code that calls `filesize()` to instead unconditionally call `wp_filesize()`.
|
infrastructure
|
use wp filesize instead of filesize if available wordpress introduced the wp filesize function which should be used in favor of php s filesize going forward we should use it in this plugin where available since we currently support wordpress and as well it s probably not worth bumping up the requirement just for that i suggest we instead create a backward compatibility layer maybe the easiest approach would be to implement a polyfill where we re implement wp filesize in the main plugin file if the function does not exist yet we can then update all module code that calls filesize to instead unconditionally call wp filesize
| 1
|
9,768
| 8,147,758,522
|
IssuesEvent
|
2018-08-22 01:39:42
|
bit-badger/myPrayerJournal
|
https://api.github.com/repos/bit-badger/myPrayerJournal
|
closed
|
Update to Vue CLI 3.0
|
infrastructure
|
The new Vue CLI brings many upgrades; take the time to update the app for this new layout/configuration, and update the build process to utilize [modern mode](https://cli.vuejs.org/guide/browser-compatibility.html#modern-mode).
|
1.0
|
Update to Vue CLI 3.0 - The new Vue CLI brings many upgrades; take the time to update the app for this new layout/configuration, and update the build process to utilize [modern mode](https://cli.vuejs.org/guide/browser-compatibility.html#modern-mode).
|
infrastructure
|
update to vue cli the new vue cli brings many upgrades take the time to update the app for this new layout configuration and update the build process to utilize
| 1
|
27,047
| 21,053,565,856
|
IssuesEvent
|
2022-03-31 23:10:48
|
dotnet/runtime
|
https://api.github.com/repos/dotnet/runtime
|
opened
|
SegFault while trying to Copy native test components in monointerpreter test run build
|
blocking-clean-ci area-Infrastructure-mono
|
Latest dotnet\runtime Rolling Build failed due to a problem when trying to copy native test components on the `Mono monointerpreter Pri0 Runtime Tests Run OSX x64 release` job. Bellow are more details to help with diagnosing.
Builds affected
[20220331.4](https://dev.azure.com/dnceng/public/_build/results?buildId=1692244) => [Log](https://dev.azure.com/dnceng/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/_apis/build/builds/1692244/logs/1965)
```
2022-03-31T09:09:29.3477940Z Copying native test binaries...
2022-03-31T09:09:46.6888520Z /Users/runner/work/1/s/dotnet.sh: line 27: 2070 Segmentation fault: 11 ${dotnetPath} "$@"
2022-03-31T09:09:46.6991160Z /Users/runner/work/1/s/src/tests/build.proj(494,5): error MSB3073: The command ""/Users/runner/work/1/s/dotnet.sh" msbuild /Users/runner/work/1/s/src/tests/build.proj /t:CopyAllNativeTestProjectBinaries "/p:TargetArchitecture=x64" "/p:Configuration=Release" "/p:LibrariesConfiguration=Release" "/p:TargetOS=OSX" "/p:RuntimeOS=" "/p:RuntimeFlavor=mono" "/p:RuntimeVariant=" "/p:CLRTestBuildAllTargets=" "/p:__TestGroupToBuild=1" "/p:__SkipRestorePackages=1" /nodeReuse:false /maxcpucount /bl:/Users/runner/work/1/s/artifacts//log/Release/InnerManagedTestBuild.1.binlog" exited with code 139.
2022-03-31T09:09:46.7194120Z
2022-03-31T09:09:46.7256460Z Build FAILED.
```
cc: @radical can you please take a look and tag relevant folks?
|
1.0
|
SegFault while trying to Copy native test components in monointerpreter test run build - Latest dotnet\runtime Rolling Build failed due to a problem when trying to copy native test components on the `Mono monointerpreter Pri0 Runtime Tests Run OSX x64 release` job. Bellow are more details to help with diagnosing.
Builds affected
[20220331.4](https://dev.azure.com/dnceng/public/_build/results?buildId=1692244) => [Log](https://dev.azure.com/dnceng/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/_apis/build/builds/1692244/logs/1965)
```
2022-03-31T09:09:29.3477940Z Copying native test binaries...
2022-03-31T09:09:46.6888520Z /Users/runner/work/1/s/dotnet.sh: line 27: 2070 Segmentation fault: 11 ${dotnetPath} "$@"
2022-03-31T09:09:46.6991160Z /Users/runner/work/1/s/src/tests/build.proj(494,5): error MSB3073: The command ""/Users/runner/work/1/s/dotnet.sh" msbuild /Users/runner/work/1/s/src/tests/build.proj /t:CopyAllNativeTestProjectBinaries "/p:TargetArchitecture=x64" "/p:Configuration=Release" "/p:LibrariesConfiguration=Release" "/p:TargetOS=OSX" "/p:RuntimeOS=" "/p:RuntimeFlavor=mono" "/p:RuntimeVariant=" "/p:CLRTestBuildAllTargets=" "/p:__TestGroupToBuild=1" "/p:__SkipRestorePackages=1" /nodeReuse:false /maxcpucount /bl:/Users/runner/work/1/s/artifacts//log/Release/InnerManagedTestBuild.1.binlog" exited with code 139.
2022-03-31T09:09:46.7194120Z
2022-03-31T09:09:46.7256460Z Build FAILED.
```
cc: @radical can you please take a look and tag relevant folks?
|
infrastructure
|
segfault while trying to copy native test components in monointerpreter test run build latest dotnet runtime rolling build failed due to a problem when trying to copy native test components on the mono monointerpreter runtime tests run osx release job bellow are more details to help with diagnosing builds affected copying native test binaries users runner work s dotnet sh line segmentation fault dotnetpath users runner work s src tests build proj error the command users runner work s dotnet sh msbuild users runner work s src tests build proj t copyallnativetestprojectbinaries p targetarchitecture p configuration release p librariesconfiguration release p targetos osx p runtimeos p runtimeflavor mono p runtimevariant p clrtestbuildalltargets p testgrouptobuild p skiprestorepackages nodereuse false maxcpucount bl users runner work s artifacts log release innermanagedtestbuild binlog exited with code build failed cc radical can you please take a look and tag relevant folks
| 1
|
16,524
| 12,016,121,976
|
IssuesEvent
|
2020-04-10 15:25:59
|
eventespresso/event-espresso-core
|
https://api.github.com/repos/eventespresso/event-espresso-core
|
reopened
|
Add option to select the separator value used within the CSV Reports
|
category:admin-pages category:models-and-data-infrastructure type:feature-request 🙏
|
<!--
BEFORE POSTING YOUR ISSUE:
- These comments won't show up when you submit the issue.
- Please ensure that what you are reporting is specific to this project.
- Try to add as much detail as possible. Be specific!
- Make sure you read the README.md for the project regarding posting issues.
- Search this repository for issues and pull requests and whether it has been fixed or reported already.
- Ensure you are using the latest code before reporting bugs (unless you are reporting an issue disovered in a branch).
- Disable all plugins and switch to a default theme to ensure its not a plugin/theme conflict issue.
- To report a security issue, please visit this page: https://eventespresso.com/report-a-security-vulnerability/
-->
## Issue Overview
<!-- Describe what this issue is about. -->
Brent put this outline together for a [related ticket](https://events.codebasehq.com/projects/event-espresso/tickets/8783) in codebase:
* on the **EE General Settings** > **Admin Options** tab at the very top of the page
* add a heading called **Import / Export**
* add a set of radio buttons similar to this: https://monosnap.com/file/HiWhQM5PJw4VGsU9ZxOIGBQnznpMm2
* label it **CSV File Data Separator**
* add the following options (but only if they will work with the rest of our code):
* **comma**
* **semicolon**
* **space**
* **tab**
* **other** which will be followed by a small text field input set to accept only one character (might be tricky with the form system)
* save the results of this option to the EE_Admin_Config object, which can then be used for setting the separator when importing or exporting
|
1.0
|
Add option to select the separator value used within the CSV Reports - <!--
BEFORE POSTING YOUR ISSUE:
- These comments won't show up when you submit the issue.
- Please ensure that what you are reporting is specific to this project.
- Try to add as much detail as possible. Be specific!
- Make sure you read the README.md for the project regarding posting issues.
- Search this repository for issues and pull requests and whether it has been fixed or reported already.
- Ensure you are using the latest code before reporting bugs (unless you are reporting an issue disovered in a branch).
- Disable all plugins and switch to a default theme to ensure its not a plugin/theme conflict issue.
- To report a security issue, please visit this page: https://eventespresso.com/report-a-security-vulnerability/
-->
## Issue Overview
<!-- Describe what this issue is about. -->
Brent put this outline together for a [related ticket](https://events.codebasehq.com/projects/event-espresso/tickets/8783) in codebase:
* on the **EE General Settings** > **Admin Options** tab at the very top of the page
* add a heading called **Import / Export**
* add a set of radio buttons similar to this: https://monosnap.com/file/HiWhQM5PJw4VGsU9ZxOIGBQnznpMm2
* label it **CSV File Data Separator**
* add the following options (but only if they will work with the rest of our code):
* **comma**
* **semicolon**
* **space**
* **tab**
* **other** which will be followed by a small text field input set to accept only one character (might be tricky with the form system)
* save the results of this option to the EE_Admin_Config object, which can then be used for setting the separator when importing or exporting
|
infrastructure
|
add option to select the separator value used within the csv reports before posting your issue these comments won t show up when you submit the issue please ensure that what you are reporting is specific to this project try to add as much detail as possible be specific make sure you read the readme md for the project regarding posting issues search this repository for issues and pull requests and whether it has been fixed or reported already ensure you are using the latest code before reporting bugs unless you are reporting an issue disovered in a branch disable all plugins and switch to a default theme to ensure its not a plugin theme conflict issue to report a security issue please visit this page issue overview brent put this outline together for a in codebase on the ee general settings admin options tab at the very top of the page add a heading called import export add a set of radio buttons similar to this label it csv file data separator add the following options but only if they will work with the rest of our code comma semicolon space tab other which will be followed by a small text field input set to accept only one character might be tricky with the form system save the results of this option to the ee admin config object which can then be used for setting the separator when importing or exporting
| 1
|
21,398
| 14,543,377,154
|
IssuesEvent
|
2020-12-15 16:48:22
|
department-of-veterans-affairs/va.gov-team
|
https://api.github.com/repos/department-of-veterans-affairs/va.gov-team
|
closed
|
EKS - deploy "platform-tools" cluster in DEV
|
infrastructure operations
|
## Description
Deploy a `platform-tools` EKS cluster in `dev`.
This will be a permanent cluster and used by both VSP Operations and other teams to host tools/services to support the VSP Platform (ie: Sentry, Grafana, Loki, etc..)
## Background/context/resources
* Should use the terraform module to provision cluster
* Should pre-provision authentication configmap with Ops team members
* Manually deployed node groups are fine for this cluster.
* May need to update tf module to support creating namespaces and SA's in order to make it usable by other teams.
## Technical notes
EKS Module: https://github.com/department-of-veterans-affairs/terraform-aws-vsp-eks
---
## Tasks
- [x] Deploy a permanent EKS cluster in `dev` for platform-tools
- [x] Create node group and worker nodes in cluster
## Definition of Done
- [x] Everyone in VSP Ops can access/use test EKS cluster as validated by `kubeconfig`
---
### Reminders
- [X] Please attach your team label and any other appropriate label(s)
- [X] Please connect to an epic
|
1.0
|
EKS - deploy "platform-tools" cluster in DEV - ## Description
Deploy a `platform-tools` EKS cluster in `dev`.
This will be a permanent cluster and used by both VSP Operations and other teams to host tools/services to support the VSP Platform (ie: Sentry, Grafana, Loki, etc..)
## Background/context/resources
* Should use the terraform module to provision cluster
* Should pre-provision authentication configmap with Ops team members
* Manually deployed node groups are fine for this cluster.
* May need to update tf module to support creating namespaces and SA's in order to make it usable by other teams.
## Technical notes
EKS Module: https://github.com/department-of-veterans-affairs/terraform-aws-vsp-eks
---
## Tasks
- [x] Deploy a permanent EKS cluster in `dev` for platform-tools
- [x] Create node group and worker nodes in cluster
## Definition of Done
- [x] Everyone in VSP Ops can access/use test EKS cluster as validated by `kubeconfig`
---
### Reminders
- [X] Please attach your team label and any other appropriate label(s)
- [X] Please connect to an epic
|
infrastructure
|
eks deploy platform tools cluster in dev description deploy a platform tools eks cluster in dev this will be a permanent cluster and used by both vsp operations and other teams to host tools services to support the vsp platform ie sentry grafana loki etc background context resources should use the terraform module to provision cluster should pre provision authentication configmap with ops team members manually deployed node groups are fine for this cluster may need to update tf module to support creating namespaces and sa s in order to make it usable by other teams technical notes eks module tasks deploy a permanent eks cluster in dev for platform tools create node group and worker nodes in cluster definition of done everyone in vsp ops can access use test eks cluster as validated by kubeconfig reminders please attach your team label and any other appropriate label s please connect to an epic
| 1
|
15,029
| 11,302,968,957
|
IssuesEvent
|
2020-01-17 18:57:13
|
python-gsoc/gsoc
|
https://api.github.com/repos/python-gsoc/gsoc
|
closed
|
Improve our volunteer information management
|
PSF infrastructure help wanted wishlist
|
PSF mentors have to sign up using a google form so that we can keep track of stuff like email addresses (which melange doesn't let admins see) and sub-orgs (which melange doesn't track at all).
Unfortunately, the google form generates a spreadsheet, which can't be updated by participants and is kind of obnoxious when we want to get a list of mentors for a given sub-org and some mentors work with many sub-orgs. Plus, there's no way for sub-org admins to manage their mentor list. We should see if there's a better way to track info to address these problems, or ways we can tweak the existing setup to make it better.
|
1.0
|
Improve our volunteer information management - PSF mentors have to sign up using a google form so that we can keep track of stuff like email addresses (which melange doesn't let admins see) and sub-orgs (which melange doesn't track at all).
Unfortunately, the google form generates a spreadsheet, which can't be updated by participants and is kind of obnoxious when we want to get a list of mentors for a given sub-org and some mentors work with many sub-orgs. Plus, there's no way for sub-org admins to manage their mentor list. We should see if there's a better way to track info to address these problems, or ways we can tweak the existing setup to make it better.
|
infrastructure
|
improve our volunteer information management psf mentors have to sign up using a google form so that we can keep track of stuff like email addresses which melange doesn t let admins see and sub orgs which melange doesn t track at all unfortunately the google form generates a spreadsheet which can t be updated by participants and is kind of obnoxious when we want to get a list of mentors for a given sub org and some mentors work with many sub orgs plus there s no way for sub org admins to manage their mentor list we should see if there s a better way to track info to address these problems or ways we can tweak the existing setup to make it better
| 1
|
609,145
| 18,855,648,661
|
IssuesEvent
|
2021-11-12 05:44:18
|
wso2/product-apim
|
https://api.github.com/repos/wso2/product-apim
|
opened
|
Readonly user should be able to get Revisions and subscriptions
|
Type/Improvement Priority/Normal
|
### Describe your problem(s)
I created a read only user who has apim:api_view and apim:publisher_settings scopes. The read only user should be able to view the API but not do the modification. But I encountered an issue while getting revisions and subscriptions. I noticed that publisher-api.yaml doesn't contain particular scopes for the get subscription and get revisions resources.
### Describe your solution
<!-- Describe the feature/improvement -->
### How will you implement it
<!-- If you like to suggest an approach or a design -->
---
### Optional Fields
#### Related Issues:
<!-- Any related issues from this/other repositories-->
#### Suggested Labels:
<!--Only to be used by non-members-->
#### Suggested Assignees:
<!--Only to be used by non-members-->
|
1.0
|
Readonly user should be able to get Revisions and subscriptions - ### Describe your problem(s)
I created a read only user who has apim:api_view and apim:publisher_settings scopes. The read only user should be able to view the API but not do the modification. But I encountered an issue while getting revisions and subscriptions. I noticed that publisher-api.yaml doesn't contain particular scopes for the get subscription and get revisions resources.
### Describe your solution
<!-- Describe the feature/improvement -->
### How will you implement it
<!-- If you like to suggest an approach or a design -->
---
### Optional Fields
#### Related Issues:
<!-- Any related issues from this/other repositories-->
#### Suggested Labels:
<!--Only to be used by non-members-->
#### Suggested Assignees:
<!--Only to be used by non-members-->
|
non_infrastructure
|
readonly user should be able to get revisions and subscriptions describe your problem s i created a read only user who has apim api view and apim publisher settings scopes the read only user should be able to view the api but not do the modification but i encountered an issue while getting revisions and subscriptions i noticed that publisher api yaml doesn t contain particular scopes for the get subscription and get revisions resources describe your solution how will you implement it optional fields related issues suggested labels suggested assignees
| 0
|
23,993
| 16,746,429,142
|
IssuesEvent
|
2021-06-11 16:04:54
|
google/web-stories-wp
|
https://api.github.com/repos/google/web-stories-wp
|
closed
|
Unpin Composer version on CI
|
P2 Pod: WP & Infra Type: Infrastructure
|
<!-- NOTE: For help requests, support questions, or general feedback, please use the WordPress.org forums instead: https://wordpress.org/support/plugin/web-stories/ -->
## Task Description
<!-- A clear and concise description of what this task is about. -->
After 10b40b7ce375649f2aaf4db5ee5f9e676e28c558 / #7863, we'd want to remove this pin once the issue has been resolved on the Composer side, i.e. once there is a 2.1.3 release.
|
1.0
|
Unpin Composer version on CI - <!-- NOTE: For help requests, support questions, or general feedback, please use the WordPress.org forums instead: https://wordpress.org/support/plugin/web-stories/ -->
## Task Description
<!-- A clear and concise description of what this task is about. -->
After 10b40b7ce375649f2aaf4db5ee5f9e676e28c558 / #7863, we'd want to remove this pin once the issue has been resolved on the Composer side, i.e. once there is a 2.1.3 release.
|
infrastructure
|
unpin composer version on ci task description after we d want to remove this pin once the issue has been resolved on the composer side i e once there is a release
| 1
|
22,117
| 14,990,837,921
|
IssuesEvent
|
2021-01-29 07:14:26
|
zwave-js/node-zwave-js
|
https://api.github.com/repos/zwave-js/node-zwave-js
|
closed
|
check for duplicate config files
|
infrastructure
|
@AlCalzone I think this may need another bit of work, there is now a 46202.json and a ge_46202.json that refer to the same device IDs.
Also, should there be a test added to the config checker to block having two configs for the same IDs?
__Originally posted by @jcam in https://github.com/zwave-js/node-zwave-js/pull/1303#issuecomment-756005678__
|
1.0
|
check for duplicate config files - @AlCalzone I think this may need another bit of work, there is now a 46202.json and a ge_46202.json that refer to the same device IDs.
Also, should there be a test added to the config checker to block having two configs for the same IDs?
__Originally posted by @jcam in https://github.com/zwave-js/node-zwave-js/pull/1303#issuecomment-756005678__
|
infrastructure
|
check for duplicate config files alcalzone i think this may need another bit of work there is now a json and a ge json that refer to the same device ids also should there be a test added to the config checker to block having two configs for the same ids originally posted by jcam in
| 1
|
151,430
| 23,820,709,864
|
IssuesEvent
|
2022-09-05 10:57:38
|
microsoft/vscode
|
https://api.github.com/repos/microsoft/vscode
|
closed
|
Extension authoring: Error: Cannot activate the 'helloworld-web-sample' extension because it depends on the 'Git' extension, which is not loaded.
|
extensions *as-designed
|
<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.70.2
- OS Version: Windows 10
Steps to Reproduce:
1. Create new extension https://github.com/microsoft/vscode-extension-samples/tree/main/helloworld-web-sample
2. Add to `package.json`:
```
"extensionDependencies": [
"vscode.git"
],
```
3. Press F5 to start extension.
4. Try to activate the extension. (Execute the Hello World command)
5. Get the following error:
```
Cannot activate the 'helloworld-web-sample' extension because it depends on the 'Git' extension, which is not loaded. Would you like to reload the window to load the extension?
```
|
1.0
|
Extension authoring: Error: Cannot activate the 'helloworld-web-sample' extension because it depends on the 'Git' extension, which is not loaded. - <!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.70.2
- OS Version: Windows 10
Steps to Reproduce:
1. Create new extension https://github.com/microsoft/vscode-extension-samples/tree/main/helloworld-web-sample
2. Add to `package.json`:
```
"extensionDependencies": [
"vscode.git"
],
```
3. Press F5 to start extension.
4. Try to activate the extension. (Execute the Hello World command)
5. Get the following error:
```
Cannot activate the 'helloworld-web-sample' extension because it depends on the 'Git' extension, which is not loaded. Would you like to reload the window to load the extension?
```
|
non_infrastructure
|
extension authoring error cannot activate the helloworld web sample extension because it depends on the git extension which is not loaded does this issue occur when all extensions are disabled yes no report issue dialog can assist with this vs code version os version windows steps to reproduce create new extension add to package json extensiondependencies vscode git press to start extension try to activate the extension execute the hello world command get the following error cannot activate the helloworld web sample extension because it depends on the git extension which is not loaded would you like to reload the window to load the extension
| 0
|
12,197
| 9,635,717,474
|
IssuesEvent
|
2019-05-16 02:30:04
|
dotnet/roslyn
|
https://api.github.com/repos/dotnet/roslyn
|
closed
|
Verify safe removal of legacy testing IVTs
|
4 - In Review Area-Infrastructure
|
The following IVTs are likely unused, in which case they can be removed:
* RoslynETAHost
* RoslynTaoActions
|
1.0
|
Verify safe removal of legacy testing IVTs - The following IVTs are likely unused, in which case they can be removed:
* RoslynETAHost
* RoslynTaoActions
|
infrastructure
|
verify safe removal of legacy testing ivts the following ivts are likely unused in which case they can be removed roslynetahost roslyntaoactions
| 1
|
92,011
| 3,864,445,839
|
IssuesEvent
|
2016-04-08 13:56:46
|
Signbank/NGT-signbank
|
https://api.github.com/repos/Signbank/NGT-signbank
|
closed
|
Provide clear error message for login failure
|
ASL enhancement top priority
|
When a user tries to log in but his account expiry date has passed ( #40 ), display a message stating "Your account has expired. Please get in touch with your Signbank contact person if you want to keep using the account."
|
1.0
|
Provide clear error message for login failure - When a user tries to log in but his account expiry date has passed ( #40 ), display a message stating "Your account has expired. Please get in touch with your Signbank contact person if you want to keep using the account."
|
non_infrastructure
|
provide clear error message for login failure when a user tries to log in but his account expiry date has passed display a message stating your account has expired please get in touch with your signbank contact person if you want to keep using the account
| 0
|
44,664
| 9,621,423,491
|
IssuesEvent
|
2019-05-14 10:35:56
|
mantidproject/mantid
|
https://api.github.com/repos/mantidproject/mantid
|
closed
|
Fix MVP issues in QDataProcessorWidget
|
Component: GUI Component: Reflectometry Priority: Low Quality: Code Quality
|
The MVP pattern has been broken in a few places in the `QDataProcessorWidget`
- The model is being updated directly from the view, e.g. [here](https://github.com/mantidproject/mantid/blob/master/qt/widgets/common/src/DataProcessorUI/QDataProcessorWidget.cpp#L245). It should be updated via the presenter instead.
- Context is being passed directly from the view to the presenter, e.g. [here](https://github.com/mantidproject/mantid/blob/master/qt/widgets/common/src/DataProcessorUI/QDataProcessorWidget.cpp#L639). Instead, the view should just notify that something happened and the presenter should request the context, e.g. like [here](https://github.com/mantidproject/mantid/blob/master/qt/widgets/common/src/DataProcessorUI/QDataProcessorWidget.cpp#L176)
|
1.0
|
Fix MVP issues in QDataProcessorWidget - The MVP pattern has been broken in a few places in the `QDataProcessorWidget`
- The model is being updated directly from the view, e.g. [here](https://github.com/mantidproject/mantid/blob/master/qt/widgets/common/src/DataProcessorUI/QDataProcessorWidget.cpp#L245). It should be updated via the presenter instead.
- Context is being passed directly from the view to the presenter, e.g. [here](https://github.com/mantidproject/mantid/blob/master/qt/widgets/common/src/DataProcessorUI/QDataProcessorWidget.cpp#L639). Instead, the view should just notify that something happened and the presenter should request the context, e.g. like [here](https://github.com/mantidproject/mantid/blob/master/qt/widgets/common/src/DataProcessorUI/QDataProcessorWidget.cpp#L176)
|
non_infrastructure
|
fix mvp issues in qdataprocessorwidget the mvp pattern has been broken in a few places in the qdataprocessorwidget the model is being updated directly from the view e g it should be updated via the presenter instead context is being passed directly from the view to the presenter e g instead the view should just notify that something happened and the presenter should request the context e g like
| 0
|
15,295
| 11,453,053,300
|
IssuesEvent
|
2020-02-06 14:46:15
|
shiftkey/desktop
|
https://api.github.com/repos/shiftkey/desktop
|
closed
|
unable to build Windows app
|
infrastructure
|
https://brendanforster.visualstudio.com/desktop-linux/_build/results?buildId=422
```
$ ts-node -P script/tsconfig.json script/post-install.ts
yarn install v1.17.3
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Rebuilding all packages...
error D:\a\1\s\app\node_modules\keytar: Command failed.
Exit code: 1
Command: prebuild-install || node-gyp rebuild
Arguments:
Directory: D:\a\1\s\app\node_modules\keytar
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Output:
D:\a\1\s\app\node_modules\node-abi\index.js:30
throw new Error('Could not detect abi for version ' + target + ' and runtime ' + runtime + '. Updating "node-abi" might help solve this issue if it is a new release of ' + runtime)
^
Error: Could not detect abi for version 5.0.6 and runtime electron. Updating "node-abi" might help solve this issue if it is a new release of electron
at getAbi (D:\a\1\s\app\node_modules\node-abi\index.js:30:9)
at module.exports (D:\a\1\s\app\node_modules\prebuild-install\rc.js:71:57)
at Object.<anonymous> (D:\a\1\s\app\node_modules\prebuild-install\bin.js:9:25)
at Module._compile (internal/modules/cjs/loader.js:955:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:991:10)
at Module.load (internal/modules/cjs/loader.js:811:32)
at Function.Module._load (internal/modules/cjs/loader.js:723:14)
at Function.Module.runMain (internal/modules/cjs/loader.js:1043:10)
at internal/main/run_main_module.js:17:11
D:\a\1\s\app\node_modules\keytar>if not defined npm_config_node_gyp (node "C:\hostedtoolcache\windows\node\12.14.1\x64\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "" rebuild )
gyp info it worked if it ends with ok
gyp info using node-gyp@5.0.5
gyp info using node@12.14.1 | win32 | x64
gyp info find Python using Python version 2.7.9 found at "C:/ProgramData/Chocolatey/lib/mingw/tools/install/mingw64/opt/bin/python2.7.exe"
gyp http GET https://atom.io/download/electron/v5.0.6/node-v5.0.6-headers.tar.gz
gyp http 200 https://atom.io/download/electron/v5.0.6/node-v5.0.6-headers.tar.gz
gyp http GET https://atom.io/download/electron/v5.0.6/SHASUMS256.txt
gyp http GET https://atom.io/download/electron/v5.0.6/win-x86/node.lib
gyp http GET https://atom.io/download/electron/v5.0.6/win-x64/node.lib
gyp http GET https://atom.io/download/electron/v5.0.6/win-arm64/node.lib
gyp http 200 https://atom.io/download/electron/v5.0.6/SHASUMS256.txt
gyp http 403 https://atom.io/download/electron/v5.0.6/win-arm64/node.lib
gyp WARN install got an error, rolling back install
gyp http 200 https://atom.io/download/electron/v5.0.6/win-x86/node.lib
gyp http 200 https://atom.io/download/electron/v5.0.6/win-x64/node.lib
gyp ERR! configure error
gyp ERR! stack Error: 403 status code downloading arm64 node.lib
gyp ERR! stack at Request.<anonymous> (C:\hostedtoolcache\windows\node\12.14.1\x64\node_modules\npm\node_modules\node-gyp\lib\install.js:335:22)
gyp ERR! stack at Request.emit (events.js:228:7)
gyp ERR! stack at Request.onRequestResponse (C:\hostedtoolcache\windows\node\12.14.1\x64\node_modules\npm\node_modules\request\request.js:1066:10)
gyp ERR! stack at ClientRequest.emit (events.js:223:5)
gyp ERR! stack at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:583:27)
gyp ERR! stack at HTTPParser.parserOnHeadersComplete (_http_common.js:115:17)
gyp ERR! stack at TLSSocket.socketOnData (_http_client.js:456:22)
gyp ERR! stack at TLSSocket.emit (events.js:223:5)
gyp ERR! stack at addChunk (_stream_readable.js:309:12)
gyp ERR! stack at readableAddChunk (_stream_readable.js:290:11)
gyp ERR! System Windows_NT 10.0.14393
gyp ERR! command "C:\\hostedtoolcache\\windows\\node\\12.14.1\\x64\\node.exe" "C:\\hostedtoolcache\\windows\\node\\12.14.1\\x64\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd D:\a\1\s\app\node_modules\keytar
gyp ERR! node -v v12.14.1
gyp ERR! node-gyp -v v5.0.5
gyp ERR! not ok
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
##[error]Cmd.exe exited with code '1'.
##[section]Finishing: Install
```
-
|
1.0
|
unable to build Windows app - https://brendanforster.visualstudio.com/desktop-linux/_build/results?buildId=422
```
$ ts-node -P script/tsconfig.json script/post-install.ts
yarn install v1.17.3
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Rebuilding all packages...
error D:\a\1\s\app\node_modules\keytar: Command failed.
Exit code: 1
Command: prebuild-install || node-gyp rebuild
Arguments:
Directory: D:\a\1\s\app\node_modules\keytar
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Output:
D:\a\1\s\app\node_modules\node-abi\index.js:30
throw new Error('Could not detect abi for version ' + target + ' and runtime ' + runtime + '. Updating "node-abi" might help solve this issue if it is a new release of ' + runtime)
^
Error: Could not detect abi for version 5.0.6 and runtime electron. Updating "node-abi" might help solve this issue if it is a new release of electron
at getAbi (D:\a\1\s\app\node_modules\node-abi\index.js:30:9)
at module.exports (D:\a\1\s\app\node_modules\prebuild-install\rc.js:71:57)
at Object.<anonymous> (D:\a\1\s\app\node_modules\prebuild-install\bin.js:9:25)
at Module._compile (internal/modules/cjs/loader.js:955:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:991:10)
at Module.load (internal/modules/cjs/loader.js:811:32)
at Function.Module._load (internal/modules/cjs/loader.js:723:14)
at Function.Module.runMain (internal/modules/cjs/loader.js:1043:10)
at internal/main/run_main_module.js:17:11
D:\a\1\s\app\node_modules\keytar>if not defined npm_config_node_gyp (node "C:\hostedtoolcache\windows\node\12.14.1\x64\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "" rebuild )
gyp info it worked if it ends with ok
gyp info using node-gyp@5.0.5
gyp info using node@12.14.1 | win32 | x64
gyp info find Python using Python version 2.7.9 found at "C:/ProgramData/Chocolatey/lib/mingw/tools/install/mingw64/opt/bin/python2.7.exe"
gyp http GET https://atom.io/download/electron/v5.0.6/node-v5.0.6-headers.tar.gz
gyp http 200 https://atom.io/download/electron/v5.0.6/node-v5.0.6-headers.tar.gz
gyp http GET https://atom.io/download/electron/v5.0.6/SHASUMS256.txt
gyp http GET https://atom.io/download/electron/v5.0.6/win-x86/node.lib
gyp http GET https://atom.io/download/electron/v5.0.6/win-x64/node.lib
gyp http GET https://atom.io/download/electron/v5.0.6/win-arm64/node.lib
gyp http 200 https://atom.io/download/electron/v5.0.6/SHASUMS256.txt
gyp http 403 https://atom.io/download/electron/v5.0.6/win-arm64/node.lib
gyp WARN install got an error, rolling back install
gyp http 200 https://atom.io/download/electron/v5.0.6/win-x86/node.lib
gyp http 200 https://atom.io/download/electron/v5.0.6/win-x64/node.lib
gyp ERR! configure error
gyp ERR! stack Error: 403 status code downloading arm64 node.lib
gyp ERR! stack at Request.<anonymous> (C:\hostedtoolcache\windows\node\12.14.1\x64\node_modules\npm\node_modules\node-gyp\lib\install.js:335:22)
gyp ERR! stack at Request.emit (events.js:228:7)
gyp ERR! stack at Request.onRequestResponse (C:\hostedtoolcache\windows\node\12.14.1\x64\node_modules\npm\node_modules\request\request.js:1066:10)
gyp ERR! stack at ClientRequest.emit (events.js:223:5)
gyp ERR! stack at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:583:27)
gyp ERR! stack at HTTPParser.parserOnHeadersComplete (_http_common.js:115:17)
gyp ERR! stack at TLSSocket.socketOnData (_http_client.js:456:22)
gyp ERR! stack at TLSSocket.emit (events.js:223:5)
gyp ERR! stack at addChunk (_stream_readable.js:309:12)
gyp ERR! stack at readableAddChunk (_stream_readable.js:290:11)
gyp ERR! System Windows_NT 10.0.14393
gyp ERR! command "C:\\hostedtoolcache\\windows\\node\\12.14.1\\x64\\node.exe" "C:\\hostedtoolcache\\windows\\node\\12.14.1\\x64\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd D:\a\1\s\app\node_modules\keytar
gyp ERR! node -v v12.14.1
gyp ERR! node-gyp -v v5.0.5
gyp ERR! not ok
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
##[error]Cmd.exe exited with code '1'.
##[section]Finishing: Install
```
-
|
infrastructure
|
unable to build windows app ts node p script tsconfig json script post install ts yarn install resolving packages fetching packages linking dependencies rebuilding all packages error d a s app node modules keytar command failed exit code command prebuild install node gyp rebuild arguments directory d a s app node modules keytar info visit for documentation about this command output d a s app node modules node abi index js throw new error could not detect abi for version target and runtime runtime updating node abi might help solve this issue if it is a new release of runtime error could not detect abi for version and runtime electron updating node abi might help solve this issue if it is a new release of electron at getabi d a s app node modules node abi index js at module exports d a s app node modules prebuild install rc js at object d a s app node modules prebuild install bin js at module compile internal modules cjs loader js at object module extensions js internal modules cjs loader js at module load internal modules cjs loader js at function module load internal modules cjs loader js at function module runmain internal modules cjs loader js at internal main run main module js d a s app node modules keytar if not defined npm config node gyp node c hostedtoolcache windows node node modules npm bin node gyp bin node modules node gyp bin node gyp js rebuild else node rebuild gyp info it worked if it ends with ok gyp info using node gyp gyp info using node gyp info find python using python version found at c programdata chocolatey lib mingw tools install opt bin exe gyp http get gyp http gyp http get gyp http get gyp http get gyp http get gyp http gyp http gyp warn install got an error rolling back install gyp http gyp http gyp err configure error gyp err stack error status code downloading node lib gyp err stack at request c hostedtoolcache windows node node modules npm node modules node gyp lib install js gyp err stack at request emit events js gyp err stack at request onrequestresponse c hostedtoolcache windows node node modules npm node modules request request js gyp err stack at clientrequest emit events js gyp err stack at httpparser parseronincomingclient http client js gyp err stack at httpparser parseronheaderscomplete http common js gyp err stack at tlssocket socketondata http client js gyp err stack at tlssocket emit events js gyp err stack at addchunk stream readable js gyp err stack at readableaddchunk stream readable js gyp err system windows nt gyp err command c hostedtoolcache windows node node exe c hostedtoolcache windows node node modules npm node modules node gyp bin node gyp js rebuild gyp err cwd d a s app node modules keytar gyp err node v gyp err node gyp v gyp err not ok error command failed with exit code info visit for documentation about this command cmd exe exited with code finishing install
| 1
|
10,453
| 8,570,437,140
|
IssuesEvent
|
2018-11-11 20:10:37
|
procxx/kepka
|
https://api.github.com/repos/procxx/kepka
|
closed
|
[appveyor] manual copy ssleay32.dll to build directory
|
category:Infrastructure
|
We need to copy manually ssleay32.dll to build directory before artifact archiving. Without this library https scheme doesn't work in QNetworkAccessManager. It happens because we linking only with libeay32.dll for hash functions and vcpkg copy only this library when scanning exe dependencis.
Qt dynamically load ssleay32.dll
|
1.0
|
[appveyor] manual copy ssleay32.dll to build directory - We need to copy manually ssleay32.dll to build directory before artifact archiving. Without this library https scheme doesn't work in QNetworkAccessManager. It happens because we linking only with libeay32.dll for hash functions and vcpkg copy only this library when scanning exe dependencis.
Qt dynamically load ssleay32.dll
|
infrastructure
|
manual copy dll to build directory we need to copy manually dll to build directory before artifact archiving without this library https scheme doesn t work in qnetworkaccessmanager it happens because we linking only with dll for hash functions and vcpkg copy only this library when scanning exe dependencis qt dynamically load dll
| 1
|
4,461
| 5,100,167,329
|
IssuesEvent
|
2017-01-04 11:04:17
|
Graylog2/graylog2-server
|
https://api.github.com/repos/Graylog2/graylog2-server
|
closed
|
extractor condition timer not in metrics
|
bug infrastructure triaged
|
### Problem description
extractor conditions are not count in the internal metrics.
### code
https://github.com/Graylog2/graylog2-server/blob/c20874ec9dae79ca71794f114df4170d3ecd8292/graylog2-server/src/main/java/org/graylog2/plugin/inputs/Extractor.java#L185-L185
|
1.0
|
extractor condition timer not in metrics - ### Problem description
extractor conditions are not count in the internal metrics.
### code
https://github.com/Graylog2/graylog2-server/blob/c20874ec9dae79ca71794f114df4170d3ecd8292/graylog2-server/src/main/java/org/graylog2/plugin/inputs/Extractor.java#L185-L185
|
infrastructure
|
extractor condition timer not in metrics problem description extractor conditions are not count in the internal metrics code
| 1
|
26,691
| 20,515,894,674
|
IssuesEvent
|
2022-03-01 11:42:03
|
dotnet/aspnetcore
|
https://api.github.com/repos/dotnet/aspnetcore
|
closed
|
Automatically download the JDK as part of the build if not present
|
area-infrastructure feature-infrastructure-improvements
|
As per our discussion on DoI, if the JDK is not installed on the machine, download the appropriate binary distribution from the Microsoft distributions of the Open JDK and add it to the path.
|
2.0
|
Automatically download the JDK as part of the build if not present - As per our discussion on DoI, if the JDK is not installed on the machine, download the appropriate binary distribution from the Microsoft distributions of the Open JDK and add it to the path.
|
infrastructure
|
automatically download the jdk as part of the build if not present as per our discussion on doi if the jdk is not installed on the machine download the appropriate binary distribution from the microsoft distributions of the open jdk and add it to the path
| 1
|
30,577
| 24,938,845,913
|
IssuesEvent
|
2022-10-31 17:11:21
|
dotnet/roslyn
|
https://api.github.com/repos/dotnet/roslyn
|
opened
|
Trigger and report the VS insertion URL back to the PR upon PR creation (Productivity team only)
|
Feature Request Area-Infrastructure
|
Trigger and report the VS insertion URL back to the PR.
We've discussed it before and we think its possible (nuget team is doing it for example). It is just a little complicated because we need to ensure that non-members can't run it (or submit PRs that change our yaml files that run it)
@jmarolf may have a posssible workflow for running it.
cc: @CyrusNajmabadi
|
1.0
|
Trigger and report the VS insertion URL back to the PR upon PR creation (Productivity team only) - Trigger and report the VS insertion URL back to the PR.
We've discussed it before and we think its possible (nuget team is doing it for example). It is just a little complicated because we need to ensure that non-members can't run it (or submit PRs that change our yaml files that run it)
@jmarolf may have a posssible workflow for running it.
cc: @CyrusNajmabadi
|
infrastructure
|
trigger and report the vs insertion url back to the pr upon pr creation productivity team only trigger and report the vs insertion url back to the pr we ve discussed it before and we think its possible nuget team is doing it for example it is just a little complicated because we need to ensure that non members can t run it or submit prs that change our yaml files that run it jmarolf may have a posssible workflow for running it cc cyrusnajmabadi
| 1
|
26,734
| 20,620,387,460
|
IssuesEvent
|
2022-03-07 16:52:05
|
google/docsy
|
https://api.github.com/repos/google/docsy
|
closed
|
Netlify preview for PR is gone after renaming of default branch
|
infrastructure regression
|
After renaming default branch from `master` to `main`, the preview on netlify for pull requests (+ other checks) is gone (have a look at #915 + #916 for reference). This should be corrected.
|
1.0
|
Netlify preview for PR is gone after renaming of default branch - After renaming default branch from `master` to `main`, the preview on netlify for pull requests (+ other checks) is gone (have a look at #915 + #916 for reference). This should be corrected.
|
infrastructure
|
netlify preview for pr is gone after renaming of default branch after renaming default branch from master to main the preview on netlify for pull requests other checks is gone have a look at for reference this should be corrected
| 1
|
5,842
| 2,978,867,979
|
IssuesEvent
|
2015-07-16 09:40:10
|
edigu/zf2-boilerplate
|
https://api.github.com/repos/edigu/zf2-boilerplate
|
opened
|
Create a Search module for full-text search requirements
|
documentation improvement
|
- [ ] Create a `Search` module for various full-text search requirements.
- [ ] Search module SHOULD support both `Elasticsearch` and `Solr` selectively via different adapters.
- [ ] Consider separating `Index` and `Query` services.
- [ ] Create two example services `UserQueryService` and `UserIndexService`
- [ ] Update, modify or delete documents in `UserIndexService` and search users in `UserQueryService` classes.
- [ ] Consider creating a console route in `Search` module and add some example interfaces for deleting a user by id, indexing all users via command line.
- [ ] Write documentation & unit tests.
|
1.0
|
Create a Search module for full-text search requirements - - [ ] Create a `Search` module for various full-text search requirements.
- [ ] Search module SHOULD support both `Elasticsearch` and `Solr` selectively via different adapters.
- [ ] Consider separating `Index` and `Query` services.
- [ ] Create two example services `UserQueryService` and `UserIndexService`
- [ ] Update, modify or delete documents in `UserIndexService` and search users in `UserQueryService` classes.
- [ ] Consider creating a console route in `Search` module and add some example interfaces for deleting a user by id, indexing all users via command line.
- [ ] Write documentation & unit tests.
|
non_infrastructure
|
create a search module for full text search requirements create a search module for various full text search requirements search module should support both elasticsearch and solr selectively via different adapters consider separating index and query services create two example services userqueryservice and userindexservice update modify or delete documents in userindexservice and search users in userqueryservice classes consider creating a console route in search module and add some example interfaces for deleting a user by id indexing all users via command line write documentation unit tests
| 0
|
35,489
| 31,714,098,015
|
IssuesEvent
|
2023-09-09 16:42:27
|
ckolderup/postmarks
|
https://api.github.com/repos/ckolderup/postmarks
|
closed
|
Port cannot be changed from 3000, should use process.env.PORT
|
infrastructure
|
Port 3000 is common for local host, but once deployed, the port varies.
This should default to 3000 as it does now, but allow override using process.env.PORT
|
1.0
|
Port cannot be changed from 3000, should use process.env.PORT - Port 3000 is common for local host, but once deployed, the port varies.
This should default to 3000 as it does now, but allow override using process.env.PORT
|
infrastructure
|
port cannot be changed from should use process env port port is common for local host but once deployed the port varies this should default to as it does now but allow override using process env port
| 1
|
15,799
| 11,711,475,037
|
IssuesEvent
|
2020-03-09 05:20:28
|
dotnet/aspnetcore
|
https://api.github.com/repos/dotnet/aspnetcore
|
closed
|
Fix AssemblyTestLogTests on Helix
|
Done area-infrastructure bug
|
Some of these tests are failing since they relied on assumptions on the directory structure that breaks down on Helix.
|
1.0
|
Fix AssemblyTestLogTests on Helix - Some of these tests are failing since they relied on assumptions on the directory structure that breaks down on Helix.
|
infrastructure
|
fix assemblytestlogtests on helix some of these tests are failing since they relied on assumptions on the directory structure that breaks down on helix
| 1
|
14,190
| 10,697,051,626
|
IssuesEvent
|
2019-10-23 15:46:14
|
KhronosGroup/glTF-Project-Explorer
|
https://api.github.com/repos/KhronosGroup/glTF-Project-Explorer
|
opened
|
Deployment Strategy
|
infrastructure
|
We're to a point where we need to start getting the deployment going with GitHub Pages. This issue is for discussion of deployment strategy.
Current ideas I have:
* Deploy to GitHub Pages.
* GitHub Actions are going to be released later this month, we should be able to automate deployment on merge.
|
1.0
|
Deployment Strategy - We're to a point where we need to start getting the deployment going with GitHub Pages. This issue is for discussion of deployment strategy.
Current ideas I have:
* Deploy to GitHub Pages.
* GitHub Actions are going to be released later this month, we should be able to automate deployment on merge.
|
infrastructure
|
deployment strategy we re to a point where we need to start getting the deployment going with github pages this issue is for discussion of deployment strategy current ideas i have deploy to github pages github actions are going to be released later this month we should be able to automate deployment on merge
| 1
|
33,503
| 27,525,620,235
|
IssuesEvent
|
2023-03-06 17:50:09
|
arduino-libraries/Arduino_MKRIoTCarrier
|
https://api.github.com/repos/arduino-libraries/Arduino_MKRIoTCarrier
|
closed
|
Compilation error with latest version of "BSEC Software Library" dependency: `bsec_datatypes.h: No such file or directory`
|
type: imperfection topic: infrastructure
|
I use this board with a MKR1010 and tried to compile some examples but without luck. Both, with the official Aruino IDE and the VSC and PlatformIO it refuses to compile.
I had success compile it when I use the previous version of bsec.h (works with 1.6.1480).
With bsec.h@1.7.1492 I get this:
> In file included from c:\Users\\*USER*\Documents\Arduino\libraries\Arduino_MKRIoTCarrier\src/MKRIoTCarrierDefines.h:12:0,
> from c:\Users\\*USER*\Documents\Arduino\libraries\Arduino_MKRIoTCarrier\src/Arduino_MKRIoTCarrier.h:25,
> from C:\Users\\*USER*\AppData\Local\Temp\.arduinoIDE-unsaved202314-13184-jf53iv.t4jn\ReadPressure>\ReadPressure.ino:14:
>c:\Users\\*USER*\Documents\Arduino\libraries\BSEC_Software_Library\src/bsec.h:46:10: fatal error: bsec_datatypes.h: No such file or >directory
>#include "bsec_datatypes.h"
> ^~~~~~~~~~~~~~~~~~
>compilation terminated.
>
>exit status 1
>
>Compilation error: exit status 1
|
1.0
|
Compilation error with latest version of "BSEC Software Library" dependency: `bsec_datatypes.h: No such file or directory` - I use this board with a MKR1010 and tried to compile some examples but without luck. Both, with the official Aruino IDE and the VSC and PlatformIO it refuses to compile.
I had success compile it when I use the previous version of bsec.h (works with 1.6.1480).
With bsec.h@1.7.1492 I get this:
> In file included from c:\Users\\*USER*\Documents\Arduino\libraries\Arduino_MKRIoTCarrier\src/MKRIoTCarrierDefines.h:12:0,
> from c:\Users\\*USER*\Documents\Arduino\libraries\Arduino_MKRIoTCarrier\src/Arduino_MKRIoTCarrier.h:25,
> from C:\Users\\*USER*\AppData\Local\Temp\.arduinoIDE-unsaved202314-13184-jf53iv.t4jn\ReadPressure>\ReadPressure.ino:14:
>c:\Users\\*USER*\Documents\Arduino\libraries\BSEC_Software_Library\src/bsec.h:46:10: fatal error: bsec_datatypes.h: No such file or >directory
>#include "bsec_datatypes.h"
> ^~~~~~~~~~~~~~~~~~
>compilation terminated.
>
>exit status 1
>
>Compilation error: exit status 1
|
infrastructure
|
compilation error with latest version of bsec software library dependency bsec datatypes h no such file or directory i use this board with a and tried to compile some examples but without luck both with the official aruino ide and the vsc and platformio it refuses to compile i had success compile it when i use the previous version of bsec h works with with bsec h i get this in file included from c users user documents arduino libraries arduino mkriotcarrier src mkriotcarrierdefines h from c users user documents arduino libraries arduino mkriotcarrier src arduino mkriotcarrier h from c users user appdata local temp arduinoide readpressure readpressure ino c users user documents arduino libraries bsec software library src bsec h fatal error bsec datatypes h no such file or directory include bsec datatypes h compilation terminated exit status compilation error exit status
| 1
|
376,875
| 11,157,530,068
|
IssuesEvent
|
2019-12-25 13:23:44
|
Disfactory/Disfactory
|
https://api.github.com/repos/Disfactory/Disfactory
|
opened
|
照片新增後端花太多時間
|
Backend enhancement medium priority
|
**Describe the bug**
上傳照片有時候要花上快十秒
**To Reproduce**
上傳看看就知道了
**Expected behavior**
要再快一點
|
1.0
|
照片新增後端花太多時間 - **Describe the bug**
上傳照片有時候要花上快十秒
**To Reproduce**
上傳看看就知道了
**Expected behavior**
要再快一點
|
non_infrastructure
|
照片新增後端花太多時間 describe the bug 上傳照片有時候要花上快十秒 to reproduce 上傳看看就知道了 expected behavior 要再快一點
| 0
|
47,836
| 10,153,262,507
|
IssuesEvent
|
2019-08-06 03:39:31
|
fish-stack/AlgoMath
|
https://api.github.com/repos/fish-stack/AlgoMath
|
opened
|
414. 第三大的数
|
Java LeetCode
|
给定一个非空数组，返回此数组中第三大的数。如果不存在，则返回数组中最大的数。要求算法时间复杂度必须是O(n)。
示例 1:
```
输入: [3, 2, 1]
输出: 1
解释: 第三大的数是 1.
```
示例 2:
```
输入: [1, 2]
输出: 2
解释: 第三大的数不存在, 所以返回最大的数 2 .
```
示例 3:
```
输入: [2, 2, 3, 1]
输出: 1
解释: 注意，要求返回第三大的数，是指第三大且唯一出现的数。
存在两个值为2的数，它们都排第二。
```
|
1.0
|
414. 第三大的数 - 给定一个非空数组，返回此数组中第三大的数。如果不存在，则返回数组中最大的数。要求算法时间复杂度必须是O(n)。
示例 1:
```
输入: [3, 2, 1]
输出: 1
解释: 第三大的数是 1.
```
示例 2:
```
输入: [1, 2]
输出: 2
解释: 第三大的数不存在, 所以返回最大的数 2 .
```
示例 3:
```
输入: [2, 2, 3, 1]
输出: 1
解释: 注意，要求返回第三大的数，是指第三大且唯一出现的数。
存在两个值为2的数，它们都排第二。
```
|
non_infrastructure
|
第三大的数 给定一个非空数组，返回此数组中第三大的数。如果不存在，则返回数组中最大的数。要求算法时间复杂度必须是o n 。 示例 输入 输出 解释 第三大的数是 示例 输入 输出 解释 第三大的数不存在 所以返回最大的数 示例 输入 输出 解释 注意，要求返回第三大的数，是指第三大且唯一出现的数。 ，它们都排第二。
| 0
|
12,779
| 7,979,485,444
|
IssuesEvent
|
2018-07-17 21:58:12
|
uswds/uswds
|
https://api.github.com/repos/uswds/uswds
|
closed
|
Inline SVG assets
|
Under consideration [Skill] Front end [Status] Feature request [Topic] Web performance
|
We can cut down on load times pretty significantly by inlining our SVG assets, and _maybe_ even get away with not having to distribute the SVG files at all. (External PNGs could still be used for IE<9 fallback.) There's a good [postcss plugin](https://github.com/TrySound/postcss-inline-svg) for this.
|
True
|
Inline SVG assets - We can cut down on load times pretty significantly by inlining our SVG assets, and _maybe_ even get away with not having to distribute the SVG files at all. (External PNGs could still be used for IE<9 fallback.) There's a good [postcss plugin](https://github.com/TrySound/postcss-inline-svg) for this.
|
non_infrastructure
|
inline svg assets we can cut down on load times pretty significantly by inlining our svg assets and maybe even get away with not having to distribute the svg files at all external pngs could still be used for ie fallback there s a good for this
| 0
|
31,918
| 26,242,744,182
|
IssuesEvent
|
2023-01-05 12:56:00
|
firebase/flutterfire
|
https://api.github.com/repos/firebase/flutterfire
|
closed
|
Android emulator is failing on android firestore e2e tests
|
platform: android type: infrastructure
|
Test failure:
```bash
FirebaseFirestore Secondary app Firestore instance
W/Firestore( 3187): (24.2.1) [WriteStream]: (5b957d0) Stream closed with status: Status{code=UNAVAILABLE, description=Channel shutdownNow invoked, cause=null}.
W/GooglePlayServicesUtil( 3187): io.flutter.plugins.firebase.firestoreexample requires the Google Play Store, but it is missing.
E/GooglePlayServicesUtil( 3187): GooglePlayServices not available due to error 9
W/Firestore( 3187): (24.2.1) [GrpcCallProvider]: Failed to update ssl context: com.google.android.gms.common.GooglePlayServicesNotAvailableException
✘ Second Firestore instance should fail due to firestore.rules forbidding data writes
[E]: TimeoutException after 0:00:30.000000: Test timed out after 30 seconds. See https://pub.dev/packages/test#timeouts
------------------------------
| Test Failures |
------------------------------
1) FirebaseFirestore Secondary app Firestore instance > Second Firestore instance should fail due to firestore.rules forbidding data writes
[E]: TimeoutException after 0:00:30.000000: Test timed out after 30 seconds. See https://pub.dev/packages/test#timeouts
```
|
1.0
|
Android emulator is failing on android firestore e2e tests - Test failure:
```bash
FirebaseFirestore Secondary app Firestore instance
W/Firestore( 3187): (24.2.1) [WriteStream]: (5b957d0) Stream closed with status: Status{code=UNAVAILABLE, description=Channel shutdownNow invoked, cause=null}.
W/GooglePlayServicesUtil( 3187): io.flutter.plugins.firebase.firestoreexample requires the Google Play Store, but it is missing.
E/GooglePlayServicesUtil( 3187): GooglePlayServices not available due to error 9
W/Firestore( 3187): (24.2.1) [GrpcCallProvider]: Failed to update ssl context: com.google.android.gms.common.GooglePlayServicesNotAvailableException
✘ Second Firestore instance should fail due to firestore.rules forbidding data writes
[E]: TimeoutException after 0:00:30.000000: Test timed out after 30 seconds. See https://pub.dev/packages/test#timeouts
------------------------------
| Test Failures |
------------------------------
1) FirebaseFirestore Secondary app Firestore instance > Second Firestore instance should fail due to firestore.rules forbidding data writes
[E]: TimeoutException after 0:00:30.000000: Test timed out after 30 seconds. See https://pub.dev/packages/test#timeouts
```
|
infrastructure
|
android emulator is failing on android firestore tests test failure bash firebasefirestore secondary app firestore instance w firestore stream closed with status status code unavailable description channel shutdownnow invoked cause null w googleplayservicesutil io flutter plugins firebase firestoreexample requires the google play store but it is missing e googleplayservicesutil googleplayservices not available due to error w firestore failed to update ssl context com google android gms common googleplayservicesnotavailableexception ✘ second firestore instance should fail due to firestore rules forbidding data writes timeoutexception after test timed out after seconds see test failures firebasefirestore secondary app firestore instance second firestore instance should fail due to firestore rules forbidding data writes timeoutexception after test timed out after seconds see
| 1
|
122,435
| 10,222,888,205
|
IssuesEvent
|
2019-08-16 08:08:57
|
microsoft/AzureStorageExplorer
|
https://api.github.com/repos/microsoft/AzureStorageExplorer
|
opened
|
An error dialog pops up when creating a collection for one database
|
:beetle: regression :gear: cosmosdb 🧪 testing
|
**Storage Explorer Version:** 1.9.0
**Build:** 20190815.2
**Platform/OS:** Linux Ubuntu 19.04/Windows 10/macOS High Sierra
**Architecture:** ia32/x64
**Regression From:** Previous release(1.9.0)
**Steps to reproduce:**
1. Create a DocumentDB account in portal.
2. Open the new account in storage explorer -> Create a database.
3. Try to create a collection and check the result.
**Expect Experience:**
No error dialog pops up and show the corresponding dialog.
**Actual Experience:**
An error occurs.
**More Info:**
This issue also reproduces for CosmosDB account with table/ Graph/ MongoDB API.
|
1.0
|
An error dialog pops up when creating a collection for one database - **Storage Explorer Version:** 1.9.0
**Build:** 20190815.2
**Platform/OS:** Linux Ubuntu 19.04/Windows 10/macOS High Sierra
**Architecture:** ia32/x64
**Regression From:** Previous release(1.9.0)
**Steps to reproduce:**
1. Create a DocumentDB account in portal.
2. Open the new account in storage explorer -> Create a database.
3. Try to create a collection and check the result.
**Expect Experience:**
No error dialog pops up and show the corresponding dialog.
**Actual Experience:**
An error occurs.
**More Info:**
This issue also reproduces for CosmosDB account with table/ Graph/ MongoDB API.
|
non_infrastructure
|
an error dialog pops up when creating a collection for one database storage explorer version build platform os linux ubuntu windows macos high sierra architecture regression from previous release steps to reproduce create a documentdb account in portal open the new account in storage explorer create a database try to create a collection and check the result expect experience no error dialog pops up and show the corresponding dialog actual experience an error occurs more info this issue also reproduces for cosmosdb account with table graph mongodb api
| 0
|
52,183
| 7,751,966,009
|
IssuesEvent
|
2018-05-30 18:45:15
|
BoltEngine/Bolt-Tracker
|
https://api.github.com/repos/BoltEngine/Bolt-Tracker
|
closed
|
Vector3 BoltHitbox.hitboxCenter example is wrong
|
documentation
|
The example for hiBoxCenter is misleading as it will not get a vector to the head of the target entity as the center of a BoltHitboxBody is in local coordinates, not world coordinates.
Eample: Getting a vector that points from the player's weapon to the head of a target entity.
1 Vector3 GetHeadshotVector(BoltEntity target, IWeapon currentWeapon) {
2 BoltHitboxBody body = target.GetComponent<BoltHitboxBody%gt();
3 BoltHitbox head = body.hitboxes[0];
4
5 foreach(BoltHitbox hitbox in body.hitboxes) {
6 if(hitbox.hitboxType == BoltHitboxType.Head) {
7 head = hitbox;
8 }
9 }
10
11 return head.hitboxCenter - currentWeapon.fireOrigin;
12 }
|
1.0
|
Vector3 BoltHitbox.hitboxCenter example is wrong -
The example for hiBoxCenter is misleading as it will not get a vector to the head of the target entity as the center of a BoltHitboxBody is in local coordinates, not world coordinates.
Eample: Getting a vector that points from the player's weapon to the head of a target entity.
1 Vector3 GetHeadshotVector(BoltEntity target, IWeapon currentWeapon) {
2 BoltHitboxBody body = target.GetComponent<BoltHitboxBody%gt();
3 BoltHitbox head = body.hitboxes[0];
4
5 foreach(BoltHitbox hitbox in body.hitboxes) {
6 if(hitbox.hitboxType == BoltHitboxType.Head) {
7 head = hitbox;
8 }
9 }
10
11 return head.hitboxCenter - currentWeapon.fireOrigin;
12 }
|
non_infrastructure
|
bolthitbox hitboxcenter example is wrong the example for hiboxcenter is misleading as it will not get a vector to the head of the target entity as the center of a bolthitboxbody is in local coordinates not world coordinates eample getting a vector that points from the player s weapon to the head of a target entity getheadshotvector boltentity target iweapon currentweapon bolthitboxbody body target getcomponent bolthitboxbody gt bolthitbox head body hitboxes foreach bolthitbox hitbox in body hitboxes if hitbox hitboxtype bolthitboxtype head head hitbox return head hitboxcenter currentweapon fireorigin
| 0
|
17,797
| 12,564,870,857
|
IssuesEvent
|
2020-06-08 08:45:46
|
AdventureLookup/AdventureLookup
|
https://api.github.com/repos/AdventureLookup/AdventureLookup
|
closed
|
Upgrade to PHP 7.4
|
dependencies infrastructure
|
We still use PHP 7.0, which is no longer maintained.
I have [started to look into upgrading to PHP 7.4](https://github.com/cmfcmf/AdventureLookup/tree/php-7.4), but ran into several issues within vendor libraries.
|
1.0
|
Upgrade to PHP 7.4 - We still use PHP 7.0, which is no longer maintained.
I have [started to look into upgrading to PHP 7.4](https://github.com/cmfcmf/AdventureLookup/tree/php-7.4), but ran into several issues within vendor libraries.
|
infrastructure
|
upgrade to php we still use php which is no longer maintained i have but ran into several issues within vendor libraries
| 1
|
8,429
| 7,428,472,834
|
IssuesEvent
|
2018-03-24 01:56:29
|
DestinyItemManager/DIM
|
https://api.github.com/repos/DestinyItemManager/DIM
|
closed
|
Google Drive-stored loadouts, tags, etc. seem to have been cleared
|
Bug Help Wanted: Developer Infrastructure: Sync
|
If there's anything in particular I can look at in Drive to help diagnose, I'd be very happy to provide more information. [Would ideally love to get my tags and loadouts back, of course, but mainly offering to help debug if possible...]
Thanks!
|
1.0
|
Google Drive-stored loadouts, tags, etc. seem to have been cleared - If there's anything in particular I can look at in Drive to help diagnose, I'd be very happy to provide more information. [Would ideally love to get my tags and loadouts back, of course, but mainly offering to help debug if possible...]
Thanks!
|
infrastructure
|
google drive stored loadouts tags etc seem to have been cleared if there s anything in particular i can look at in drive to help diagnose i d be very happy to provide more information thanks
| 1
|
13,117
| 10,131,757,730
|
IssuesEvent
|
2019-08-01 20:23:35
|
HumanCellAtlas/secondary-analysis
|
https://api.github.com/repos/HumanCellAtlas/secondary-analysis
|
closed
|
Nightly clio-integration test is flaky.
|
infrastructure
|
[https://gotc-jenkins.dsp-techops.broadinstitute.org/view/greenteam-nightly/job/clio-integration/](https://gotc-jenkins.dsp-techops.broadinstitute.org/view/greenteam-nightly/job/clio-integration/)
Fails in different ways on different days.
Most look like timeouts waiting for the docker container to start.
Some look like mysterious build failures.
And occasionally it succeeds.
┆Issue is synchronized with this [Jira Story](https://broadinstitute.atlassian.net/browse/GH-339)
|
1.0
|
Nightly clio-integration test is flaky. - [https://gotc-jenkins.dsp-techops.broadinstitute.org/view/greenteam-nightly/job/clio-integration/](https://gotc-jenkins.dsp-techops.broadinstitute.org/view/greenteam-nightly/job/clio-integration/)
Fails in different ways on different days.
Most look like timeouts waiting for the docker container to start.
Some look like mysterious build failures.
And occasionally it succeeds.
┆Issue is synchronized with this [Jira Story](https://broadinstitute.atlassian.net/browse/GH-339)
|
infrastructure
|
nightly clio integration test is flaky fails in different ways on different days most look like timeouts waiting for the docker container to start some look like mysterious build failures and occasionally it succeeds ┆issue is synchronized with this
| 1
|
14,882
| 8,697,363,541
|
IssuesEvent
|
2018-12-04 20:03:11
|
dotnet/corefx
|
https://api.github.com/repos/dotnet/corefx
|
closed
|
PipeAwaitable should not hold onto CancellationTokens
|
area-System.IO.Pipelines bug tenet-performance
|
https://github.com/dotnet/corefx/blob/14072950a458eabef6eb6da2204ba0a506242b4b/src/System.IO.Pipelines/src/System/IO/Pipelines/PipeAwaitable.cs#L46-L57
Holding onto the token too long can extend the life of token even after disposal. That might include a Timer instance which won't go away until the next read (trying to figure out if that's always true, the dump is showing weirdness).
cc @pakrym
|
True
|
PipeAwaitable should not hold onto CancellationTokens - https://github.com/dotnet/corefx/blob/14072950a458eabef6eb6da2204ba0a506242b4b/src/System.IO.Pipelines/src/System/IO/Pipelines/PipeAwaitable.cs#L46-L57
Holding onto the token too long can extend the life of token even after disposal. That might include a Timer instance which won't go away until the next read (trying to figure out if that's always true, the dump is showing weirdness).
cc @pakrym
|
non_infrastructure
|
pipeawaitable should not hold onto cancellationtokens holding onto the token too long can extend the life of token even after disposal that might include a timer instance which won t go away until the next read trying to figure out if that s always true the dump is showing weirdness cc pakrym
| 0
|
7,204
| 6,820,803,460
|
IssuesEvent
|
2017-11-07 15:01:41
|
hzi-braunschweig/SORMAS-Open
|
https://api.github.com/repos/hzi-braunschweig/SORMAS-Open
|
opened
|
Allow admins to delete entities
|
Infrastructure sormas-backend sormas-ui
|
Only for admins!
## Backend
- [ ] delete task
- [ ] delete sample test
- [ ] delete sample with tests
- [ ] delete visit (symptoms)
- [ ] delete contact with all visits and tasks
- [ ] delete case (symptoms, hospitalization, epi data, etc.) with all contacts, tasks and samples
- [ ] delete event participant
- [ ] delete event with all participants and tasks
## UI
- [ ] add commit/discard delete button to all respective forms for admins
## Unclear
- [ ] How to delete the same data on the mobile devices. When the entity is changed there and is sent to the server it will be created as a new entity. Idea: Make sure that a "new" entity send from the mobile device has no creation date. Otherwise reply to the device that the entity has been delete.
|
1.0
|
Allow admins to delete entities - Only for admins!
## Backend
- [ ] delete task
- [ ] delete sample test
- [ ] delete sample with tests
- [ ] delete visit (symptoms)
- [ ] delete contact with all visits and tasks
- [ ] delete case (symptoms, hospitalization, epi data, etc.) with all contacts, tasks and samples
- [ ] delete event participant
- [ ] delete event with all participants and tasks
## UI
- [ ] add commit/discard delete button to all respective forms for admins
## Unclear
- [ ] How to delete the same data on the mobile devices. When the entity is changed there and is sent to the server it will be created as a new entity. Idea: Make sure that a "new" entity send from the mobile device has no creation date. Otherwise reply to the device that the entity has been delete.
|
infrastructure
|
allow admins to delete entities only for admins backend delete task delete sample test delete sample with tests delete visit symptoms delete contact with all visits and tasks delete case symptoms hospitalization epi data etc with all contacts tasks and samples delete event participant delete event with all participants and tasks ui add commit discard delete button to all respective forms for admins unclear how to delete the same data on the mobile devices when the entity is changed there and is sent to the server it will be created as a new entity idea make sure that a new entity send from the mobile device has no creation date otherwise reply to the device that the entity has been delete
| 1
|
10,973
| 8,850,353,966
|
IssuesEvent
|
2019-01-08 13:02:08
|
dotnet/corefx
|
https://api.github.com/repos/dotnet/corefx
|
closed
|
Add CI leg / Helix run to test net45-net463 packages on Desktop
|
area-Infrastructure test enhancement
|
We have quite a few packages (35) that ship assets on Desktop. We do not have any test coverage today:
```
135 packages support some version of desktop
98 of those include an out of band dll
35 of those contain more than just type-forwards
Breakdown by version : (numSupported) / (numSupportedOOB) / (numNotFacades)
4.5.0.0 : 70 / 20 / 1
4.5.1.0 : 73 / 22 / 1
4.6.0.0 : 133 / 86 / 28
4.6.1.0 : 134 / 88 / 29
4.6.2.0 : 134 / 94 / 33
4.6.3.0 : 135 / 98 / 35
```
See details in https://github.com/dotnet/corefx/pull/17262#issuecomment-288531194
|
1.0
|
Add CI leg / Helix run to test net45-net463 packages on Desktop - We have quite a few packages (35) that ship assets on Desktop. We do not have any test coverage today:
```
135 packages support some version of desktop
98 of those include an out of band dll
35 of those contain more than just type-forwards
Breakdown by version : (numSupported) / (numSupportedOOB) / (numNotFacades)
4.5.0.0 : 70 / 20 / 1
4.5.1.0 : 73 / 22 / 1
4.6.0.0 : 133 / 86 / 28
4.6.1.0 : 134 / 88 / 29
4.6.2.0 : 134 / 94 / 33
4.6.3.0 : 135 / 98 / 35
```
See details in https://github.com/dotnet/corefx/pull/17262#issuecomment-288531194
|
infrastructure
|
add ci leg helix run to test packages on desktop we have quite a few packages that ship assets on desktop we do not have any test coverage today packages support some version of desktop of those include an out of band dll of those contain more than just type forwards breakdown by version numsupported numsupportedoob numnotfacades see details in
| 1
|
3,778
| 4,559,863,446
|
IssuesEvent
|
2016-09-14 05:03:49
|
codingteam/loglist
|
https://api.github.com/repos/codingteam/loglist
|
closed
|
JS minification on production
|
kind:feature kind:infrastructure
|
Our production environment should include minified and optimized version of the script.
|
1.0
|
JS minification on production - Our production environment should include minified and optimized version of the script.
|
infrastructure
|
js minification on production our production environment should include minified and optimized version of the script
| 1
|
678,163
| 23,190,503,484
|
IssuesEvent
|
2022-08-01 12:14:55
|
SAP/xsk
|
https://api.github.com/repos/SAP/xsk
|
closed
|
[API] $.security.crypto should not be a function
|
wontfix API core priority-medium effort-medium incomplete
|
Currently, in order to use the `crypto` API, one should use it like:
```JS
const hashedString = $.security.crypto().md5("someString");
```
The docs, however, state it should be used like:
```JS
const hashedString = $.security.crypto.md5("someString");
```
|
1.0
|
[API] $.security.crypto should not be a function - Currently, in order to use the `crypto` API, one should use it like:
```JS
const hashedString = $.security.crypto().md5("someString");
```
The docs, however, state it should be used like:
```JS
const hashedString = $.security.crypto.md5("someString");
```
|
non_infrastructure
|
security crypto should not be a function currently in order to use the crypto api one should use it like js const hashedstring security crypto somestring the docs however state it should be used like js const hashedstring security crypto somestring
| 0
|
620,115
| 19,553,101,284
|
IssuesEvent
|
2022-01-03 02:59:20
|
cathayddt/bdk
|
https://api.github.com/repos/cathayddt/bdk
|
closed
|
network create 時的舊組織無法透過 org peer add 加入 channel
|
type:bug priority:medium status:triage
|
# ISSUE
## 說明 (Description)
command `bdk network create` 未呼叫 `peer.createPeerOrgConfigtxJSON`，沒有將 org 寫入 org-json 資料夾
## 種類 (Issue Type)
[ ] Feature Request
[x] Report Bug
[ ] Other
---
## 通報問題 (Report Bug)
**重現步驟 (Steps to Reproduce)**
1. 建立網路，有P1, P2, P3 共3個Peer Org
2. 使用 `bdk org peer create` 建立 P4 Org
3. P4 建立 channel，成員包括 P1, P2, P4
4. 使用 `bdk org peer add` 將 P3 加入 channel
**測試環境 (Environment)**:
* OS:
* NodeJS Version:
* NPM Version:
* Docker Version:
**應呈現結果 (Expected Behavior)**
讀取 P3 的 org-json 並產生信封
**實際呈現結果 (Resulted Behavior)**
P3 沒有 org-json
---
## 其他說明 (Additional Context)
|
1.0
|
network create 時的舊組織無法透過 org peer add 加入 channel - # ISSUE
## 說明 (Description)
command `bdk network create` 未呼叫 `peer.createPeerOrgConfigtxJSON`，沒有將 org 寫入 org-json 資料夾
## 種類 (Issue Type)
[ ] Feature Request
[x] Report Bug
[ ] Other
---
## 通報問題 (Report Bug)
**重現步驟 (Steps to Reproduce)**
1. 建立網路，有P1, P2, P3 共3個Peer Org
2. 使用 `bdk org peer create` 建立 P4 Org
3. P4 建立 channel，成員包括 P1, P2, P4
4. 使用 `bdk org peer add` 將 P3 加入 channel
**測試環境 (Environment)**:
* OS:
* NodeJS Version:
* NPM Version:
* Docker Version:
**應呈現結果 (Expected Behavior)**
讀取 P3 的 org-json 並產生信封
**實際呈現結果 (Resulted Behavior)**
P3 沒有 org-json
---
## 其他說明 (Additional Context)
|
non_infrastructure
|
network create 時的舊組織無法透過 org peer add 加入 channel issue 說明 description command bdk network create 未呼叫 peer createpeerorgconfigtxjson ，沒有將 org 寫入 org json 資料夾 種類 issue type feature request report bug other 通報問題 report bug 重現步驟 steps to reproduce 建立網路， org 使用 bdk org peer create 建立 org 建立 channel，成員包括 使用 bdk org peer add 將 加入 channel 測試環境 environment os nodejs version npm version docker version 應呈現結果 expected behavior 讀取 的 org json 並產生信封 實際呈現結果 resulted behavior 沒有 org json 其他說明 additional context
| 0
|
702,051
| 24,120,563,490
|
IssuesEvent
|
2022-09-20 18:18:45
|
googleapis/nodejs-dlp
|
https://api.github.com/repos/googleapis/nodejs-dlp
|
closed
|
redact: should report image redaction handling errors failed
|
type: bug priority: p1 api: dlp flakybot: issue
|
This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: 7c53b9fb61d90cbc3e592070fcf577289d54ba21
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/146260ea-01e2-4622-a770-b7111df00aa4), [Sponge](http://sponge2/146260ea-01e2-4622-a770-b7111df00aa4)
status: failed
<details><summary>Test output</summary><br><pre>expected 'Command failed: node redactImage.js l…' to include 'INVALID_ARGUMENT'
AssertionError: expected 'Command failed: node redactImage.js l…' to include 'INVALID_ARGUMENT'
at Context.<anonymous> (system-test/redact.test.js:133:12)
at processImmediate (internal/timers.js:461:21)</pre></details>
|
1.0
|
redact: should report image redaction handling errors failed - This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: 7c53b9fb61d90cbc3e592070fcf577289d54ba21
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/146260ea-01e2-4622-a770-b7111df00aa4), [Sponge](http://sponge2/146260ea-01e2-4622-a770-b7111df00aa4)
status: failed
<details><summary>Test output</summary><br><pre>expected 'Command failed: node redactImage.js l…' to include 'INVALID_ARGUMENT'
AssertionError: expected 'Command failed: node redactImage.js l…' to include 'INVALID_ARGUMENT'
at Context.<anonymous> (system-test/redact.test.js:133:12)
at processImmediate (internal/timers.js:461:21)</pre></details>
|
non_infrastructure
|
redact should report image redaction handling errors failed this test failed to configure my behavior see if i m commenting on this issue too often add the flakybot quiet label and i will stop commenting commit buildurl status failed test output expected command failed node redactimage js l… to include invalid argument assertionerror expected command failed node redactimage js l… to include invalid argument at context system test redact test js at processimmediate internal timers js
| 0
|
22,555
| 15,269,210,596
|
IssuesEvent
|
2021-02-22 12:29:00
|
conan-io/conan-center-index
|
https://api.github.com/repos/conan-io/conan-center-index
|
closed
|
[service] Build packages for Clang 10
|
infrastructure
|
Now where https://github.com/conan-io/conan-docker-tools/pull/193 is merged, the service should generate packages for Clang 10.
If added, the wiki should be updated as well: https://github.com/conan-io/conan-center-index/wiki/Supported-Platforms-And-Configurations
|
1.0
|
[service] Build packages for Clang 10 - Now where https://github.com/conan-io/conan-docker-tools/pull/193 is merged, the service should generate packages for Clang 10.
If added, the wiki should be updated as well: https://github.com/conan-io/conan-center-index/wiki/Supported-Platforms-And-Configurations
|
infrastructure
|
build packages for clang now where is merged the service should generate packages for clang if added the wiki should be updated as well
| 1
|
17,722
| 12,519,699,291
|
IssuesEvent
|
2020-06-03 14:48:37
|
dotnet/aspnetcore
|
https://api.github.com/repos/dotnet/aspnetcore
|
closed
|
Fix warning: "CS8632: The annotation for nullable reference types should only be used in code within a '#nullable' annotations context."
|
area-infrastructure
|
There are at least 28 new warnings of this type. See https://dev.azure.com/dnceng/internal/_build/results?buildId=664608&view=logs&j=1b89928a-2219-5ef9-602f-f95beb3da4dc&t=bcce746a-741e-59b7-adec-a4a82d8c5e52&l=1736 for example.
Looks like these came in with #21581.
|
1.0
|
Fix warning: "CS8632: The annotation for nullable reference types should only be used in code within a '#nullable' annotations context." - There are at least 28 new warnings of this type. See https://dev.azure.com/dnceng/internal/_build/results?buildId=664608&view=logs&j=1b89928a-2219-5ef9-602f-f95beb3da4dc&t=bcce746a-741e-59b7-adec-a4a82d8c5e52&l=1736 for example.
Looks like these came in with #21581.
|
infrastructure
|
fix warning the annotation for nullable reference types should only be used in code within a nullable annotations context there are at least new warnings of this type see for example looks like these came in with
| 1
|
718,111
| 24,704,898,727
|
IssuesEvent
|
2022-10-19 18:11:46
|
CheeseTastischProject/Java
|
https://api.github.com/repos/CheeseTastischProject/Java
|
opened
|
General architecture
|
Priority: High Type: Enchant
|
- Core
- Bootstrap
- Load ServiceProviders
- AnnotationScanner
- JsonDocument
- Logger
- Database
- SurrealDB
- Messages
- Permission
- Groups
- Subgroups
- Permissions
- Permissions
- Player
- Groups
- Permissions
- Utility
- DateUtil
- UUIDFetcher
- Item
- ItemBuilder
- InventoryBuilder
- TextComponentBuilder
- Module per logical unit
|
1.0
|
General architecture - - Core
- Bootstrap
- Load ServiceProviders
- AnnotationScanner
- JsonDocument
- Logger
- Database
- SurrealDB
- Messages
- Permission
- Groups
- Subgroups
- Permissions
- Permissions
- Player
- Groups
- Permissions
- Utility
- DateUtil
- UUIDFetcher
- Item
- ItemBuilder
- InventoryBuilder
- TextComponentBuilder
- Module per logical unit
|
non_infrastructure
|
general architecture core bootstrap load serviceproviders annotationscanner jsondocument logger database surrealdb messages permission groups subgroups permissions permissions player groups permissions utility dateutil uuidfetcher item itembuilder inventorybuilder textcomponentbuilder module per logical unit
| 0
|
600,804
| 18,357,981,902
|
IssuesEvent
|
2021-10-08 21:22:48
|
MineInAbyss/Bonfire
|
https://api.github.com/repos/MineInAbyss/Bonfire
|
closed
|
Command to kill and update all Bonfire Armorstands
|
priority:medium type:enhancement
|
Just so we can refresh all those broken bonfires around the abyss.
|
1.0
|
Command to kill and update all Bonfire Armorstands - Just so we can refresh all those broken bonfires around the abyss.
|
non_infrastructure
|
command to kill and update all bonfire armorstands just so we can refresh all those broken bonfires around the abyss
| 0
|
30,403
| 24,798,554,428
|
IssuesEvent
|
2022-10-24 19:30:45
|
GoogleForCreators/web-stories-wp
|
https://api.github.com/repos/GoogleForCreators/web-stories-wp
|
closed
|
Make it easier to run PHP unit test locally
|
Status: Blocked Type: Infrastructure Pod: WP P4
|
## Feature Description
Currently to run PHP unit tests, it requires PHP and MySQL to be setup currently on developers local machine. For many of the developers on this project, these will not be setup.
WordPress core now run's it unit tests in inside the docker containers. See this [line](https://github.com/WordPress/wordpress-develop/blob/master/package.json#L163).
Related: https://github.com/google/web-stories-wp/issues/2521
## Alternatives Considered
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
## Additional Context
<!-- Add any other context or screenshots about the feature request. -->
---
_Do not alter or remove anything below. The following sections will be managed by moderators only._
## Acceptance Criteria
<!-- One or more bullet points for acceptance criteria. -->
## Implementation Brief
<!-- One or more bullet points for how to technically implement the feature. -->
|
1.0
|
Make it easier to run PHP unit test locally - ## Feature Description
Currently to run PHP unit tests, it requires PHP and MySQL to be setup currently on developers local machine. For many of the developers on this project, these will not be setup.
WordPress core now run's it unit tests in inside the docker containers. See this [line](https://github.com/WordPress/wordpress-develop/blob/master/package.json#L163).
Related: https://github.com/google/web-stories-wp/issues/2521
## Alternatives Considered
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
## Additional Context
<!-- Add any other context or screenshots about the feature request. -->
---
_Do not alter or remove anything below. The following sections will be managed by moderators only._
## Acceptance Criteria
<!-- One or more bullet points for acceptance criteria. -->
## Implementation Brief
<!-- One or more bullet points for how to technically implement the feature. -->
|
infrastructure
|
make it easier to run php unit test locally feature description currently to run php unit tests it requires php and mysql to be setup currently on developers local machine for many of the developers on this project these will not be setup wordpress core now run s it unit tests in inside the docker containers see this related alternatives considered additional context do not alter or remove anything below the following sections will be managed by moderators only acceptance criteria implementation brief
| 1
|
13,276
| 3,321,590,736
|
IssuesEvent
|
2015-11-09 09:52:09
|
snaekobbi/sprints
|
https://api.github.com/repos/snaekobbi/sprints
|
closed
|
[4.5:78] The user shall have control over page breaking…
|
2 - Ready for test FAIL priority:1
|
### Requirement
[[4.5:78]](http://snaekobbi.github.io/requirements#4.5:78) The user shall have control over page breaking by means of
- inserting hard page breaks,
- protecting blocks from being split across multiple pages,
- avoiding page breaks within blocks leaving only the first line(s) on the first page (orphan control),
- avoiding page breaks within blocks leaving only the last line(s) on the second page (widow control), and
- keeping a block’s first line(s) on the same page as the preceding block.
## sprint#4
### Tasks
- [x] specification
- [x] OBFL: widows and orphans: http://files.pef-format.org/drafts/obfl/obfl-specification.html#L1023
- [ ] implementation
- [ ] Fix keep and keep-with-next in Dotify (https://github.com/joeha480/dotify/issues/101)
- [ ] Add support for widows and orphans in Dotify
- [x] example in braille CSS specification (@bertfrees): see http://snaekobbi.github.io/braille-css-spec/#controlling-page-breaks
- [ ] execute system tests
- [x] @mixa72 ![FAIL][]
- [x] @KariRudjord ![PASS][]
- [ ] @paivis ![Ready for test][]
- [ ] @dkager ![Ready for test][]
- [x] @stesk ![FAIL][]
- [x] @JC-MTM (MTM-script) ![FAIL][]
### Test results
- DE/DK: Widow/orphan control not working (known issue)
[priority:1]: http://snaekobbi.github.io/sprints/priority_1.svg "priority:1"
[priority:2]: http://snaekobbi.github.io/sprints/priority_2.svg "priority:2"
[Ready for test]: http://snaekobbi.github.io/sprints/Ready_for_test.svg "Ready for text"
[PASS]: http://snaekobbi.github.io/sprints/PASS.svg "PASS"
[FAIL]: http://snaekobbi.github.io/sprints/FAIL.svg "FAIL"
<!---
@huboard:{"order":25.15625,"milestone_order":58,"custom_state":""}
-->
|
1.0
|
[4.5:78] The user shall have control over page breaking… - ### Requirement
[[4.5:78]](http://snaekobbi.github.io/requirements#4.5:78) The user shall have control over page breaking by means of
- inserting hard page breaks,
- protecting blocks from being split across multiple pages,
- avoiding page breaks within blocks leaving only the first line(s) on the first page (orphan control),
- avoiding page breaks within blocks leaving only the last line(s) on the second page (widow control), and
- keeping a block’s first line(s) on the same page as the preceding block.
## sprint#4
### Tasks
- [x] specification
- [x] OBFL: widows and orphans: http://files.pef-format.org/drafts/obfl/obfl-specification.html#L1023
- [ ] implementation
- [ ] Fix keep and keep-with-next in Dotify (https://github.com/joeha480/dotify/issues/101)
- [ ] Add support for widows and orphans in Dotify
- [x] example in braille CSS specification (@bertfrees): see http://snaekobbi.github.io/braille-css-spec/#controlling-page-breaks
- [ ] execute system tests
- [x] @mixa72 ![FAIL][]
- [x] @KariRudjord ![PASS][]
- [ ] @paivis ![Ready for test][]
- [ ] @dkager ![Ready for test][]
- [x] @stesk ![FAIL][]
- [x] @JC-MTM (MTM-script) ![FAIL][]
### Test results
- DE/DK: Widow/orphan control not working (known issue)
[priority:1]: http://snaekobbi.github.io/sprints/priority_1.svg "priority:1"
[priority:2]: http://snaekobbi.github.io/sprints/priority_2.svg "priority:2"
[Ready for test]: http://snaekobbi.github.io/sprints/Ready_for_test.svg "Ready for text"
[PASS]: http://snaekobbi.github.io/sprints/PASS.svg "PASS"
[FAIL]: http://snaekobbi.github.io/sprints/FAIL.svg "FAIL"
<!---
@huboard:{"order":25.15625,"milestone_order":58,"custom_state":""}
-->
|
non_infrastructure
|
the user shall have control over page breaking… requirement the user shall have control over page breaking by means of inserting hard page breaks protecting blocks from being split across multiple pages avoiding page breaks within blocks leaving only the first line s on the first page orphan control avoiding page breaks within blocks leaving only the last line s on the second page widow control and keeping a block’s first line s on the same page as the preceding block sprint tasks specification obfl widows and orphans implementation fix keep and keep with next in dotify add support for widows and orphans in dotify example in braille css specification bertfrees see execute system tests karirudjord paivis dkager stesk jc mtm mtm script test results de dk widow orphan control not working known issue priority priority ready for text pass fail huboard order milestone order custom state
| 0
|
236,529
| 7,749,988,774
|
IssuesEvent
|
2018-05-30 13:13:40
|
Myoats/preprod
|
https://api.github.com/repos/Myoats/preprod
|
closed
|
Remove Title bar from Upsell Images
|
Highest Priority
|
Can you remove the bottom section from the instagram, fb and best of the week cards.
Can you add a class name to div class image-holder called "upsell"
|
1.0
|
Remove Title bar from Upsell Images - Can you remove the bottom section from the instagram, fb and best of the week cards.
Can you add a class name to div class image-holder called "upsell"
|
non_infrastructure
|
remove title bar from upsell images can you remove the bottom section from the instagram fb and best of the week cards can you add a class name to div class image holder called upsell
| 0
|
18,112
| 4,233,691,488
|
IssuesEvent
|
2016-07-05 08:57:10
|
nilearn/nilearn
|
https://api.github.com/repos/nilearn/nilearn
|
opened
|
nilearn.datasets.fetch_icbm152_2009 docstring isn't great
|
Datasets Documentation Easy
|
The description of the return argument in nilearn.datasets.fetch_icbm152_2009 is hard to read.
Also, we should add a seealso block to point to nilearn.datasets.load_mni152_template and fetch_icbm152_brain_gm_mask
|
1.0
|
nilearn.datasets.fetch_icbm152_2009 docstring isn't great - The description of the return argument in nilearn.datasets.fetch_icbm152_2009 is hard to read.
Also, we should add a seealso block to point to nilearn.datasets.load_mni152_template and fetch_icbm152_brain_gm_mask
|
non_infrastructure
|
nilearn datasets fetch docstring isn t great the description of the return argument in nilearn datasets fetch is hard to read also we should add a seealso block to point to nilearn datasets load template and fetch brain gm mask
| 0
|
75,777
| 3,475,618,961
|
IssuesEvent
|
2015-12-25 21:47:43
|
williamxu/MangoReader
|
https://api.github.com/repos/williamxu/MangoReader
|
closed
|
reimplementing mangaviewactivity
|
high priority in progress
|
- [x] Show next and previous directions
- [x] Horizontally scroll through pages
- [x] Show page number
- [ ] reimplement navigation gestures
|
1.0
|
reimplementing mangaviewactivity - 
- [x] Show next and previous directions
- [x] Horizontally scroll through pages
- [x] Show page number
- [ ] reimplement navigation gestures
|
non_infrastructure
|
reimplementing mangaviewactivity show next and previous directions horizontally scroll through pages show page number reimplement navigation gestures
| 0
|
9,254
| 7,883,722,031
|
IssuesEvent
|
2018-06-27 06:41:10
|
ExchangeUnion/xud
|
https://api.github.com/repos/ExchangeUnion/xud
|
opened
|
add disableMatching config
|
infrastructure order book
|
`xud` should have only 2 matching modes: do no matching, or all matching.
* represent this by adding a boolean config property, `disableMatching`, which its default value will be `false`. It should be a top-level config (not under a specific module). Should be passed, at least, to the order book module.
* remove `internalMatching` boolean value on the order book config + its usage. Not supporting this mode anymore.
|
1.0
|
add disableMatching config - `xud` should have only 2 matching modes: do no matching, or all matching.
* represent this by adding a boolean config property, `disableMatching`, which its default value will be `false`. It should be a top-level config (not under a specific module). Should be passed, at least, to the order book module.
* remove `internalMatching` boolean value on the order book config + its usage. Not supporting this mode anymore.
|
infrastructure
|
add disablematching config xud should have only matching modes do no matching or all matching represent this by adding a boolean config property disablematching which its default value will be false it should be a top level config not under a specific module should be passed at least to the order book module remove internalmatching boolean value on the order book config its usage not supporting this mode anymore
| 1
|
213,153
| 16,512,371,670
|
IssuesEvent
|
2021-05-26 06:34:50
|
GeoscienceAustralia/dea-notebooks
|
https://api.github.com/repos/GeoscienceAustralia/dea-notebooks
|
opened
|
Remove DEA Waterbodies from Scientific workflows and make DEA datasets notebook
|
documentation new feature/enhancement
|
DEA Waterbodies has outgrown its life as a folder in `scientific_workflows`. Instead it should be highlighted with a notebook in `DEA_datasets` and the old code removed.
Make sure to point to the new DEA Waterbodies repo.
|
1.0
|
Remove DEA Waterbodies from Scientific workflows and make DEA datasets notebook - DEA Waterbodies has outgrown its life as a folder in `scientific_workflows`. Instead it should be highlighted with a notebook in `DEA_datasets` and the old code removed.
Make sure to point to the new DEA Waterbodies repo.
|
non_infrastructure
|
remove dea waterbodies from scientific workflows and make dea datasets notebook dea waterbodies has outgrown its life as a folder in scientific workflows instead it should be highlighted with a notebook in dea datasets and the old code removed make sure to point to the new dea waterbodies repo
| 0
|
23,415
| 6,419,940,139
|
IssuesEvent
|
2017-08-08 22:30:23
|
xhqiao89/HydroDesktop_test
|
https://api.github.com/repos/xhqiao89/HydroDesktop_test
|
closed
|
Change units on graphs
|
CodePlex
|
<b>nmhydro[CodePlex]</b> <br />The prerequisite for this feature is implementing feature 8377 (Add support for unit conversion). This feature should be implemented as a quotChange Unitsquot ribbon button in the Graph tab. When the user clicks quotChange Unitsquot a new form
is displayed. This form shows the list of all current variables. For each variable, it shows the current unit and a quotnew unitquot drop down. The quotnew unitquot drop down is populated with all units to which the current unit can be converted. For
example if the current unit is meter then the list contains values such as millimeter, centimeter, kilometer, inch, foot, yard, mile..
When the user selects one of the options, the graphs for the selected variable are re-drawn using the new units and any future graphs of series with the selected variable will also be displayed using the selected units.
[Reported originally by Stephen]
|
1.0
|
Change units on graphs - <b>nmhydro[CodePlex]</b> <br />The prerequisite for this feature is implementing feature 8377 (Add support for unit conversion). This feature should be implemented as a quotChange Unitsquot ribbon button in the Graph tab. When the user clicks quotChange Unitsquot a new form
is displayed. This form shows the list of all current variables. For each variable, it shows the current unit and a quotnew unitquot drop down. The quotnew unitquot drop down is populated with all units to which the current unit can be converted. For
example if the current unit is meter then the list contains values such as millimeter, centimeter, kilometer, inch, foot, yard, mile..
When the user selects one of the options, the graphs for the selected variable are re-drawn using the new units and any future graphs of series with the selected variable will also be displayed using the selected units.
[Reported originally by Stephen]
|
non_infrastructure
|
change units on graphs nmhydro the prerequisite for this feature is implementing feature add support for unit conversion this feature should be implemented as a quotchange unitsquot ribbon button in the graph tab when the user clicks quotchange unitsquot a new form is displayed this form shows the list of all current variables for each variable it shows the current unit and a quotnew unitquot drop down the quotnew unitquot drop down is populated with all units to which the current unit can be converted for example if the current unit is meter then the list contains values such as millimeter centimeter kilometer inch foot yard mile when the user selects one of the options the graphs for the selected variable are re drawn using the new units and any future graphs of series with the selected variable will also be displayed using the selected units
| 0
|
280
| 2,610,367,489
|
IssuesEvent
|
2015-02-26 19:58:40
|
jdonson/first-null-commit
|
https://api.github.com/repos/jdonson/first-null-commit
|
closed
|
We ought to think about how to customize labels!!!
|
enhancement infrastructure next
|
https://help.github.com/articles/customizing-issue-labels
We ought to consider whether the default labels are useful for us....
Look at the labels that this guy created....
http://captaincodeman.com/2012/03/07/creating-labels-github-issue-system/
We should skim and discuss these:
https://help.github.com/
The following github terminology needs a glossary:
http://www.stevefenton.co.uk/Content/Blog/Date/201203/Blog/Basic-GitHub-Glossary/
Those should be turned into flashcards!
GitHub Terms...
Gists
Watch
Star
Issue
Wiki
Fork
Branch
Merge
We generally move things from chat
to skype...
and from skype to github issues...
then to github project wiki...
then to code itself, with reqs and tests well documented
|
1.0
|
We ought to think about how to customize labels!!! - https://help.github.com/articles/customizing-issue-labels
We ought to consider whether the default labels are useful for us....
Look at the labels that this guy created....
http://captaincodeman.com/2012/03/07/creating-labels-github-issue-system/
We should skim and discuss these:
https://help.github.com/
The following github terminology needs a glossary:
http://www.stevefenton.co.uk/Content/Blog/Date/201203/Blog/Basic-GitHub-Glossary/
Those should be turned into flashcards!
GitHub Terms...
Gists
Watch
Star
Issue
Wiki
Fork
Branch
Merge
We generally move things from chat
to skype...
and from skype to github issues...
then to github project wiki...
then to code itself, with reqs and tests well documented
|
infrastructure
|
we ought to think about how to customize labels we ought to consider whether the default labels are useful for us look at the labels that this guy created we should skim and discuss these the following github terminology needs a glossary those should be turned into flashcards github terms gists watch star issue wiki fork branch merge we generally move things from chat to skype and from skype to github issues then to github project wiki then to code itself with reqs and tests well documented
| 1
|
236,907
| 18,144,029,512
|
IssuesEvent
|
2021-09-25 05:00:15
|
felangel/bloc
|
https://api.github.com/repos/felangel/bloc
|
closed
|
docs: link is broken
|
documentation pkg:hydrated_bloc
|
**Description**
https://pub.dev/packages/hydrated_bloc
```
HydratedStorage is built on top of hive for a platform-agnostic, performant storage layer.
See the complete [example] for more details.
```
Link on `example` is broken
|
1.0
|
docs: link is broken - **Description**
https://pub.dev/packages/hydrated_bloc
```
HydratedStorage is built on top of hive for a platform-agnostic, performant storage layer.
See the complete [example] for more details.
```
Link on `example` is broken
|
non_infrastructure
|
docs link is broken description hydratedstorage is built on top of hive for a platform agnostic performant storage layer see the complete for more details link on example is broken
| 0
|
33,365
| 27,414,092,269
|
IssuesEvent
|
2023-03-01 12:37:40
|
vuejs/vetur
|
https://api.github.com/repos/vuejs/vetur
|
closed
|
Migration from TSLint to ESLint
|
help-wanted infrastructure integ:stylus-supremacy good first issue
|
Can you please update the `package.json` file to use `ESLint` instead of `TSLint`, as I get the following warning from `npm`:
```
npm WARN deprecated tslint@6.1.3: TSLint has been deprecated in favor of ESLint.
Please see https://github.com/palantir/tslint/issues/4534 for more information.
```
due to this [line](https://github.com/vuejs/vetur/blob/master/package.json#L629) in your `package.json`. thanks in advance.
|
1.0
|
Migration from TSLint to ESLint - Can you please update the `package.json` file to use `ESLint` instead of `TSLint`, as I get the following warning from `npm`:
```
npm WARN deprecated tslint@6.1.3: TSLint has been deprecated in favor of ESLint.
Please see https://github.com/palantir/tslint/issues/4534 for more information.
```
due to this [line](https://github.com/vuejs/vetur/blob/master/package.json#L629) in your `package.json`. thanks in advance.
|
infrastructure
|
migration from tslint to eslint can you please update the package json file to use eslint instead of tslint as i get the following warning from npm npm warn deprecated tslint tslint has been deprecated in favor of eslint please see for more information due to this in your package json thanks in advance
| 1
|
19,416
| 10,354,283,165
|
IssuesEvent
|
2019-09-05 13:27:48
|
Floz42/anniversaire
|
https://api.github.com/repos/Floz42/anniversaire
|
opened
|
CVE-2015-9251 (Medium) detected in jquery-1.12.3.js
|
security vulnerability
|
## CVE-2015-9251 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-1.12.3.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.12.3/jquery.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.12.3/jquery.js</a></p>
<p>Path to dependency file: /anniversaire/index.html</p>
<p>Path to vulnerable library: /anniversaire/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.12.3.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Floz42/anniversaire/commit/6182bd009fbac1ba1df158eb3d32cd34149e8fae">6182bd009fbac1ba1df158eb3d32cd34149e8fae</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.
<p>Publish Date: 2018-01-18
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9251>CVE-2015-9251</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-9251">https://nvd.nist.gov/vuln/detail/CVE-2015-9251</a></p>
<p>Release Date: 2018-01-18</p>
<p>Fix Resolution: jQuery - v3.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2015-9251 (Medium) detected in jquery-1.12.3.js - ## CVE-2015-9251 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-1.12.3.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.12.3/jquery.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.12.3/jquery.js</a></p>
<p>Path to dependency file: /anniversaire/index.html</p>
<p>Path to vulnerable library: /anniversaire/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.12.3.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Floz42/anniversaire/commit/6182bd009fbac1ba1df158eb3d32cd34149e8fae">6182bd009fbac1ba1df158eb3d32cd34149e8fae</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.
<p>Publish Date: 2018-01-18
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9251>CVE-2015-9251</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-9251">https://nvd.nist.gov/vuln/detail/CVE-2015-9251</a></p>
<p>Release Date: 2018-01-18</p>
<p>Fix Resolution: jQuery - v3.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_infrastructure
|
cve medium detected in jquery js cve medium severity vulnerability vulnerable library jquery js javascript library for dom operations library home page a href path to dependency file anniversaire index html path to vulnerable library anniversaire index html dependency hierarchy x jquery js vulnerable library found in head commit a href vulnerability details jquery before is vulnerable to cross site scripting xss attacks when a cross domain ajax request is performed without the datatype option causing text javascript responses to be executed publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jquery step up your open source security game with whitesource
| 0
|
37,090
| 2,814,911,962
|
IssuesEvent
|
2015-05-18 22:54:03
|
HPI-SWA-Teaching/SWT15-Project-13
|
https://api.github.com/repos/HPI-SWA-Teaching/SWT15-Project-13
|
closed
|
Auswertung vollständiger, gültiger Ausdrücke
|
priority: blocker type: feature
|
| | | |
| :---------: | :-------------------------------------------------: | :------------------: |
| _10_ | | _8_ |
| | Als **Anwender** möchte ich **vollständige, gültige Ausdrücke durch Betätigung des Zeilenschalter auswerten**, um **mit den Objekten der Entwicklungsumgebung zu interagieren**. | |
| _9_ | | _6_ |
|
1.0
|
Auswertung vollständiger, gültiger Ausdrücke - | | | |
| :---------: | :-------------------------------------------------: | :------------------: |
| _10_ | | _8_ |
| | Als **Anwender** möchte ich **vollständige, gültige Ausdrücke durch Betätigung des Zeilenschalter auswerten**, um **mit den Objekten der Entwicklungsumgebung zu interagieren**. | |
| _9_ | | _6_ |
|
non_infrastructure
|
auswertung vollständiger gültiger ausdrücke als anwender möchte ich vollständige gültige ausdrücke durch betätigung des zeilenschalter auswerten um mit den objekten der entwicklungsumgebung zu interagieren
| 0
|
341,887
| 24,718,063,161
|
IssuesEvent
|
2022-10-20 08:35:28
|
spring-projects/spring-boot
|
https://api.github.com/repos/spring-projects/spring-boot
|
opened
|
Update docs to final GraalVM 22.3
|
type: documentation
|
The `:liberica-nik-download:` in `attributes.adoc` still points to the 22-EA release, and theres
```
NOTE: If you download it manually, make sure to download the NIK 22-EA version, which is based on GraalVM 22.3.
```
in `developing-your-first-application.adoc` which should be removed after GraalVM 22.3 is released.
|
1.0
|
Update docs to final GraalVM 22.3 - The `:liberica-nik-download:` in `attributes.adoc` still points to the 22-EA release, and theres
```
NOTE: If you download it manually, make sure to download the NIK 22-EA version, which is based on GraalVM 22.3.
```
in `developing-your-first-application.adoc` which should be removed after GraalVM 22.3 is released.
|
non_infrastructure
|
update docs to final graalvm the liberica nik download in attributes adoc still points to the ea release and theres note if you download it manually make sure to download the nik ea version which is based on graalvm in developing your first application adoc which should be removed after graalvm is released
| 0
|
271,996
| 29,794,970,206
|
IssuesEvent
|
2023-06-16 01:00:50
|
billmcchesney1/hadoop
|
https://api.github.com/repos/billmcchesney1/hadoop
|
closed
|
CVE-2021-22569 (Medium) detected in protobuf-java-3.7.1.jar - autoclosed
|
Mend: dependency security vulnerability
|
## CVE-2021-22569 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>protobuf-java-3.7.1.jar</b></p></summary>
<p>Core Protocol Buffers library. Protocol Buffers are a way of encoding structured data in an
efficient yet extensible format.</p>
<p>Library home page: <a href="https://developers.google.com/protocol-buffers/">https://developers.google.com/protocol-buffers/</a></p>
<p>Path to vulnerable library: /hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase/hadoop-yarn-server-timelineservice-hbase-client/target/lib/protobuf-java-3.7.1.jar,/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase/hadoop-yarn-server-timelineservice-hbase-common/target/lib/protobuf-java-3.7.1.jar</p>
<p>
Dependency Hierarchy:
- :x: **protobuf-java-3.7.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/billmcchesney1/hadoop/commit/6dcd8400219941dcbd7fb0f6b980cc2c6a2a6b0a">6dcd8400219941dcbd7fb0f6b980cc2c6a2a6b0a</a></p>
<p>Found in base branch: <b>trunk</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>
An issue in protobuf-java allowed the interleaving of com.google.protobuf.UnknownFieldSet fields in such a way that would be processed out of order. A small malicious payload can occupy the parser for several minutes by creating large numbers of short-lived objects that cause frequent, repeated pauses. We recommend upgrading libraries beyond the vulnerable versions.
<p>Publish Date: 2022-01-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-22569>CVE-2021-22569</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-wrvw-hg22-4m67">https://github.com/advisories/GHSA-wrvw-hg22-4m67</a></p>
<p>Release Date: 2022-01-10</p>
<p>Fix Resolution: 3.16.1</p>
</p>
</details>
<p></p>
|
True
|
CVE-2021-22569 (Medium) detected in protobuf-java-3.7.1.jar - autoclosed - ## CVE-2021-22569 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>protobuf-java-3.7.1.jar</b></p></summary>
<p>Core Protocol Buffers library. Protocol Buffers are a way of encoding structured data in an
efficient yet extensible format.</p>
<p>Library home page: <a href="https://developers.google.com/protocol-buffers/">https://developers.google.com/protocol-buffers/</a></p>
<p>Path to vulnerable library: /hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase/hadoop-yarn-server-timelineservice-hbase-client/target/lib/protobuf-java-3.7.1.jar,/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase/hadoop-yarn-server-timelineservice-hbase-common/target/lib/protobuf-java-3.7.1.jar</p>
<p>
Dependency Hierarchy:
- :x: **protobuf-java-3.7.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/billmcchesney1/hadoop/commit/6dcd8400219941dcbd7fb0f6b980cc2c6a2a6b0a">6dcd8400219941dcbd7fb0f6b980cc2c6a2a6b0a</a></p>
<p>Found in base branch: <b>trunk</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>
An issue in protobuf-java allowed the interleaving of com.google.protobuf.UnknownFieldSet fields in such a way that would be processed out of order. A small malicious payload can occupy the parser for several minutes by creating large numbers of short-lived objects that cause frequent, repeated pauses. We recommend upgrading libraries beyond the vulnerable versions.
<p>Publish Date: 2022-01-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-22569>CVE-2021-22569</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-wrvw-hg22-4m67">https://github.com/advisories/GHSA-wrvw-hg22-4m67</a></p>
<p>Release Date: 2022-01-10</p>
<p>Fix Resolution: 3.16.1</p>
</p>
</details>
<p></p>
|
non_infrastructure
|
cve medium detected in protobuf java jar autoclosed cve medium severity vulnerability vulnerable library protobuf java jar core protocol buffers library protocol buffers are a way of encoding structured data in an efficient yet extensible format library home page a href path to vulnerable library hadoop yarn project hadoop yarn hadoop yarn server hadoop yarn server timelineservice hbase hadoop yarn server timelineservice hbase client target lib protobuf java jar hadoop yarn project hadoop yarn hadoop yarn server hadoop yarn server timelineservice hbase hadoop yarn server timelineservice hbase common target lib protobuf java jar dependency hierarchy x protobuf java jar vulnerable library found in head commit a href found in base branch trunk vulnerability details an issue in protobuf java allowed the interleaving of com google protobuf unknownfieldset fields in such a way that would be processed out of order a small malicious payload can occupy the parser for several minutes by creating large numbers of short lived objects that cause frequent repeated pauses we recommend upgrading libraries beyond the vulnerable versions publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution
| 0
|
12,149
| 9,603,396,217
|
IssuesEvent
|
2019-05-10 16:56:49
|
dotnet/wcf
|
https://api.github.com/repos/dotnet/wcf
|
opened
|
Fix Microsoft copyright element in nuspec.
|
Infrastructure
|
Our latest packages failed validation and had to be manually fixed before pushing to NuGet. They were throwing...
INVALID.
.\System.Private.ServiceModel.4.6.0-preview5.final.nupkg
The package System.Private.ServiceModel 4.6.0-preview5.final is not compliant.
There is 1 problem.
- The package metadata contains a non-compliant copyright element.
See https://github.com/dotnet/arcade/pull/2635 for more info.
|
1.0
|
Fix Microsoft copyright element in nuspec. - Our latest packages failed validation and had to be manually fixed before pushing to NuGet. They were throwing...
INVALID.
.\System.Private.ServiceModel.4.6.0-preview5.final.nupkg
The package System.Private.ServiceModel 4.6.0-preview5.final is not compliant.
There is 1 problem.
- The package metadata contains a non-compliant copyright element.
See https://github.com/dotnet/arcade/pull/2635 for more info.
|
infrastructure
|
fix microsoft copyright element in nuspec our latest packages failed validation and had to be manually fixed before pushing to nuget they were throwing invalid system private servicemodel final nupkg the package system private servicemodel final is not compliant there is problem the package metadata contains a non compliant copyright element see for more info
| 1
|
348,628
| 10,450,878,186
|
IssuesEvent
|
2019-09-19 11:36:24
|
OpenSRP/opensrp-client-chw
|
https://api.github.com/repos/OpenSRP/opensrp-client-chw
|
opened
|
Text underneath completed counselling task in child visit in English in Swahili version
|
Boresha Afya low priority
|
- [ ] Change 'Counselling' to 'Ushauri' in the Swahili version
|
1.0
|
Text underneath completed counselling task in child visit in English in Swahili version - - [ ] Change 'Counselling' to 'Ushauri' in the Swahili version
|
non_infrastructure
|
text underneath completed counselling task in child visit in english in swahili version change counselling to ushauri in the swahili version
| 0
|
222,252
| 17,401,568,070
|
IssuesEvent
|
2021-08-02 20:29:56
|
rstudio/rstudio
|
https://api.github.com/repos/rstudio/rstudio
|
closed
|
Code chunks within HTML comments break the document when switched to visual editor
|
bug test visual markdown editing
|
<!--
IMPORTANT: Please fill out this template fully! Failure to do so will result in the issue being closed automatically.
This issue tracker is for bugs and feature requests in the RStudio IDE. If you're having trouble with R itself or an R package, see https://www.r-project.org/help.html, and if you want to ask a question rather than report a bug, go to https://community.rstudio.com/. Finally, if you use RStudio Server Pro, get in touch with our Pro support team at support@rstudio.com.
-->
### System details
RStudio Edition : Desktop
RStudio Version : 1.4.1589
OS Version : macOS 11.2.2
R Version : 4.0.4
### Steps to reproduce the problem
- Create an R Markdown document, and place the following text using the source editor> Note that there is a space within the backticks that define the code chunk (so that text shows properly here), you'll need to remove that when reproducing.
```
---
output: html_document
---
This text is not commented out
<!--
This is commented out text
` ``{r}
# this is a code chunk within the commented out area
1+1
` ``
--->
This text is also not commented out
```
- Knit the document, and as expected you get the following output.
- Switch to the visual editor, and in the editor, things appear to be ok.
- Knit the document again, and the second line of text is no longer there.
### Describe the problem in detail
If you switch the editor back to source, the background coloring suggests the backticks that are supposed to be closing off the code chunk might now be closing the HTML block. But that still doesn't explain why the second line of text is not visible in the output.
Note that this becomes a pain point not just when switching between editor types but also when two collaborators are working on a project, one using the visual and the other using the source editor, and "Write canonical visual mode markdown in source mode" is set to true.
### Describe the behavior you expected
Since the visual editor also has a notion of "comments" I would expect this commented our block of text (including the code chunk) to be converted to such a comment.
<!--
Please keep the below portion in your issue, and check `[x]` the applicable boxes.
-->
- [x] I have read the guide for [submitting good bug reports](https://github.com/rstudio/rstudio/wiki/Writing-Good-Bug-Reports).
- [x] I have installed the latest version of RStudio, and confirmed that the issue still persists.
- [ ] If I am reporting a RStudio crash, I have included a [diagnostics report](https://support.rstudio.com/hc/en-us/articles/200321257-Running-a-Diagnostics-Report).
- [x] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
|
1.0
|
Code chunks within HTML comments break the document when switched to visual editor - <!--
IMPORTANT: Please fill out this template fully! Failure to do so will result in the issue being closed automatically.
This issue tracker is for bugs and feature requests in the RStudio IDE. If you're having trouble with R itself or an R package, see https://www.r-project.org/help.html, and if you want to ask a question rather than report a bug, go to https://community.rstudio.com/. Finally, if you use RStudio Server Pro, get in touch with our Pro support team at support@rstudio.com.
-->
### System details
RStudio Edition : Desktop
RStudio Version : 1.4.1589
OS Version : macOS 11.2.2
R Version : 4.0.4
### Steps to reproduce the problem
- Create an R Markdown document, and place the following text using the source editor> Note that there is a space within the backticks that define the code chunk (so that text shows properly here), you'll need to remove that when reproducing.
```
---
output: html_document
---
This text is not commented out
<!--
This is commented out text
` ``{r}
# this is a code chunk within the commented out area
1+1
` ``
--->
This text is also not commented out
```
- Knit the document, and as expected you get the following output.
- Switch to the visual editor, and in the editor, things appear to be ok.
- Knit the document again, and the second line of text is no longer there.
### Describe the problem in detail
If you switch the editor back to source, the background coloring suggests the backticks that are supposed to be closing off the code chunk might now be closing the HTML block. But that still doesn't explain why the second line of text is not visible in the output.
Note that this becomes a pain point not just when switching between editor types but also when two collaborators are working on a project, one using the visual and the other using the source editor, and "Write canonical visual mode markdown in source mode" is set to true.
### Describe the behavior you expected
Since the visual editor also has a notion of "comments" I would expect this commented our block of text (including the code chunk) to be converted to such a comment.
<!--
Please keep the below portion in your issue, and check `[x]` the applicable boxes.
-->
- [x] I have read the guide for [submitting good bug reports](https://github.com/rstudio/rstudio/wiki/Writing-Good-Bug-Reports).
- [x] I have installed the latest version of RStudio, and confirmed that the issue still persists.
- [ ] If I am reporting a RStudio crash, I have included a [diagnostics report](https://support.rstudio.com/hc/en-us/articles/200321257-Running-a-Diagnostics-Report).
- [x] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
|
non_infrastructure
|
code chunks within html comments break the document when switched to visual editor important please fill out this template fully failure to do so will result in the issue being closed automatically this issue tracker is for bugs and feature requests in the rstudio ide if you re having trouble with r itself or an r package see and if you want to ask a question rather than report a bug go to finally if you use rstudio server pro get in touch with our pro support team at support rstudio com system details rstudio edition desktop rstudio version os version macos r version steps to reproduce the problem create an r markdown document and place the following text using the source editor note that there is a space within the backticks that define the code chunk so that text shows properly here you ll need to remove that when reproducing output html document this text is not commented out this is commented out text r this is a code chunk within the commented out area this text is also not commented out knit the document and as expected you get the following output switch to the visual editor and in the editor things appear to be ok knit the document again and the second line of text is no longer there describe the problem in detail if you switch the editor back to source the background coloring suggests the backticks that are supposed to be closing off the code chunk might now be closing the html block but that still doesn t explain why the second line of text is not visible in the output note that this becomes a pain point not just when switching between editor types but also when two collaborators are working on a project one using the visual and the other using the source editor and write canonical visual mode markdown in source mode is set to true describe the behavior you expected since the visual editor also has a notion of comments i would expect this commented our block of text including the code chunk to be converted to such a comment please keep the below portion in your issue and check the applicable boxes i have read the guide for i have installed the latest version of rstudio and confirmed that the issue still persists if i am reporting a rstudio crash i have included a i have done my best to include a minimal self contained set of instructions for consistently reproducing the issue
| 0
|
5,685
| 5,889,463,409
|
IssuesEvent
|
2017-05-17 12:58:21
|
mozilla/parsys
|
https://api.github.com/repos/mozilla/parsys
|
opened
|
Recreate mozillians log buckets
|
[INFRASTRUCTURE]
|
These should be managed via terraform - however I don't think it's possible to import a resource into a module, so we need to spin up new buckets and migrate the content.
|
1.0
|
Recreate mozillians log buckets - These should be managed via terraform - however I don't think it's possible to import a resource into a module, so we need to spin up new buckets and migrate the content.
|
infrastructure
|
recreate mozillians log buckets these should be managed via terraform however i don t think it s possible to import a resource into a module so we need to spin up new buckets and migrate the content
| 1
|
319,216
| 9,740,362,422
|
IssuesEvent
|
2019-06-01 19:44:23
|
HevelMc/Electryon
|
https://api.github.com/repos/HevelMc/Electryon
|
closed
|
electrons et remplacement de jobs
|
Priority: Low SERVEUR SURVIE TODO
|
- [x] rename money
- [x] jobs chasseur
- [x] jobs mineur
- [x] jobs bucheron
- [ ] autres jobs ?
|
1.0
|
electrons et remplacement de jobs - - [x] rename money
- [x] jobs chasseur
- [x] jobs mineur
- [x] jobs bucheron
- [ ] autres jobs ?
|
non_infrastructure
|
electrons et remplacement de jobs rename money jobs chasseur jobs mineur jobs bucheron autres jobs
| 0
|
24,585
| 17,422,227,429
|
IssuesEvent
|
2021-08-04 03:50:00
|
deneb-viz/deneb
|
https://api.github.com/repos/deneb-viz/deneb
|
closed
|
Improve/Script the Office UI Fabric Icons Retrieval Process
|
infrastructure
|
We introduced selective packaging of the Office UI Fabric Icons in #77, but this is currently manual. It would be good if we could drive the retrieval and update of source code from a single file if possible. At the very least, we should refactor the code so we can drop it in more easily from the .zip download.
|
1.0
|
Improve/Script the Office UI Fabric Icons Retrieval Process - We introduced selective packaging of the Office UI Fabric Icons in #77, but this is currently manual. It would be good if we could drive the retrieval and update of source code from a single file if possible. At the very least, we should refactor the code so we can drop it in more easily from the .zip download.
|
infrastructure
|
improve script the office ui fabric icons retrieval process we introduced selective packaging of the office ui fabric icons in but this is currently manual it would be good if we could drive the retrieval and update of source code from a single file if possible at the very least we should refactor the code so we can drop it in more easily from the zip download
| 1
|
148,075
| 13,224,839,401
|
IssuesEvent
|
2020-08-17 19:57:20
|
sxs-collaboration/spectre
|
https://api.github.com/repos/sxs-collaboration/spectre
|
closed
|
Add some documentation about Charm++
|
documentation enhancement
|
For example define what a Charm++ node, proc, group, nodegroup, array, chare, ....
|
1.0
|
Add some documentation about Charm++ - For example define what a Charm++ node, proc, group, nodegroup, array, chare, ....
|
non_infrastructure
|
add some documentation about charm for example define what a charm node proc group nodegroup array chare
| 0
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.