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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
164,287 | 13,939,658,034 | IssuesEvent | 2020-10-22 16:47:30 | LNP-BP/rgb-node | https://api.github.com/repos/LNP-BP/rgb-node | closed | Dependency conflict when trying to use rgb-node in another project | bug documentation | rgb-node builds fine for me as its own crate, but when I try to include it in a separate project, I get this error upon cargo check or cargo build:
error: failed to select a version for `secp256k1-sys`.
... required by package `secp256k1 v0.18.0`
... which is depended on by `bitcoin v0.24.0`
... which is depended on by `miniscript v2.0.0`
... which is depended on by `lnpbp v0.1.0-rc.2 (https://github.com/LNP-BP/rust-lnpbp?tag=v0.1.0-rc.2#96832d9b)`
... which is depended on by `rgb_node v0.1.0-rc.2 (https://github.com/LNP-BP/rgb-node?tag=v0.1.0-rc.2#a46423d6)`
... which is depended on by `$MY_PROJECT`
versions that meet the requirements `^0.2.0` are: 0.2.0
the package `secp256k1-sys` links to the native library `rustsecp256k1_v0_2_0`, but it conflicts with a previous package which links to `rustsecp256k1_v0_2_0` as well:
package `secp256k1-sys v0.3.0`
... which is depended on by `secp256k1 v0.19.0`
... which is depended on by `bitcoin v0.25.0`
... which is depended on by `electrum-client v0.3.0-beta.1`
... which is depended on by `rgb_node v0.1.0-rc.2 (https://github.com/LNP-BP/rgb-node?tag=v0.1.0-rc.2#a46423d6)`
... which is depended on by `$MY_PROJECT`
failed to select a version for `secp256k1-sys` which could resolve this conflict
This error is also present for the v0.1.0-rc.1 tag, but not v0.1.0-beta.4. | 1.0 | Dependency conflict when trying to use rgb-node in another project - rgb-node builds fine for me as its own crate, but when I try to include it in a separate project, I get this error upon cargo check or cargo build:
error: failed to select a version for `secp256k1-sys`.
... required by package `secp256k1 v0.18.0`
... which is depended on by `bitcoin v0.24.0`
... which is depended on by `miniscript v2.0.0`
... which is depended on by `lnpbp v0.1.0-rc.2 (https://github.com/LNP-BP/rust-lnpbp?tag=v0.1.0-rc.2#96832d9b)`
... which is depended on by `rgb_node v0.1.0-rc.2 (https://github.com/LNP-BP/rgb-node?tag=v0.1.0-rc.2#a46423d6)`
... which is depended on by `$MY_PROJECT`
versions that meet the requirements `^0.2.0` are: 0.2.0
the package `secp256k1-sys` links to the native library `rustsecp256k1_v0_2_0`, but it conflicts with a previous package which links to `rustsecp256k1_v0_2_0` as well:
package `secp256k1-sys v0.3.0`
... which is depended on by `secp256k1 v0.19.0`
... which is depended on by `bitcoin v0.25.0`
... which is depended on by `electrum-client v0.3.0-beta.1`
... which is depended on by `rgb_node v0.1.0-rc.2 (https://github.com/LNP-BP/rgb-node?tag=v0.1.0-rc.2#a46423d6)`
... which is depended on by `$MY_PROJECT`
failed to select a version for `secp256k1-sys` which could resolve this conflict
This error is also present for the v0.1.0-rc.1 tag, but not v0.1.0-beta.4. | non_infrastructure | dependency conflict when trying to use rgb node in another project rgb node builds fine for me as its own crate but when i try to include it in a separate project i get this error upon cargo check or cargo build error failed to select a version for sys required by package which is depended on by bitcoin which is depended on by miniscript which is depended on by lnpbp rc which is depended on by rgb node rc which is depended on by my project versions that meet the requirements are the package sys links to the native library but it conflicts with a previous package which links to as well package sys which is depended on by which is depended on by bitcoin which is depended on by electrum client beta which is depended on by rgb node rc which is depended on by my project failed to select a version for sys which could resolve this conflict this error is also present for the rc tag but not beta | 0 |
122,581 | 26,144,152,553 | IssuesEvent | 2022-12-30 00:18:05 | vectordotdev/vector | https://api.github.com/repos/vectordotdev/vector | closed | `socket` sink octet framing | sink: socket source: socket type: enhancement meta: feedback domain: codecs | We received feedback that octet encoding/decoding would be a nice feature for the `socket` source and sink:
> I would be very interested in having support for sources & sinks being able to consume/emit length-value messages, e.g. 4 bytes of network-order integer that specifies the message size, then exactly that many bytes following immediately afterward.
This is similar to [RFC 6587's octet counting requirement](https://tools.ietf.org/html/rfc6587#section-3.4.1).
Ref #3454, #3453, #257. | 1.0 | `socket` sink octet framing - We received feedback that octet encoding/decoding would be a nice feature for the `socket` source and sink:
> I would be very interested in having support for sources & sinks being able to consume/emit length-value messages, e.g. 4 bytes of network-order integer that specifies the message size, then exactly that many bytes following immediately afterward.
This is similar to [RFC 6587's octet counting requirement](https://tools.ietf.org/html/rfc6587#section-3.4.1).
Ref #3454, #3453, #257. | non_infrastructure | socket sink octet framing we received feedback that octet encoding decoding would be a nice feature for the socket source and sink i would be very interested in having support for sources sinks being able to consume emit length value messages e g bytes of network order integer that specifies the message size then exactly that many bytes following immediately afterward this is similar to ref | 0 |
8,319 | 7,341,232,397 | IssuesEvent | 2018-03-07 00:58:58 | picotorrent/picotorrent | https://api.github.com/repos/picotorrent/picotorrent | opened | Add caching to the AppVeyor build | infrastructure up for grabs | If we cache the `tools/` directory in AppVeyor we could save a few minutes per build. Quite neat. | 1.0 | Add caching to the AppVeyor build - If we cache the `tools/` directory in AppVeyor we could save a few minutes per build. Quite neat. | infrastructure | add caching to the appveyor build if we cache the tools directory in appveyor we could save a few minutes per build quite neat | 1 |
417,910 | 12,189,832,678 | IssuesEvent | 2020-04-29 08:15:03 | zoot-hq/zoot | https://api.github.com/repos/zoot-hq/zoot | closed | resources-page | good first issue high priority | - accessed via last button on navbar
- lists resources in a ScrollView container
Resources:
Maternal Mental Health
[Postpartum Support International](http://postpartum.net/)
[MGH Center for Women's Mental Health](https://womensmentalhealth.org/)
[National Institute of Mental Health](https://www.nimh.nih.gov/index.shtml)
[SAMHSA Hotline](https://www.samhsa.gov/find-help/national-helpline)
Crisis Text Line: Text “HELLO” to 741741
Wellness
[Yoga with Adriene ](https://www.youtube.com/user/yogawithadriene)
[Center for Mindfulness Guided Meditations](https://www.umassmemorialhealthcare.org/umass-memorial-center-mindfulness)
[Maria Shriver's Sunday Paper ](https://mariashriver.com/sundaypaper/)
Infant & Child Development
[La Leche League](https://www.llli.org/)
[HealthyChildren.org](http://healthychildren.org/)
[PBS Kids for Parents ](https://www.pbs.org/parents)
[The Child Mind Institute ](http://childmind.org/)
[Common Sense Media ](https://www.commonsensemedia.org/)
See: [Resources-revised.pdf](https://github.com/zoot-hq/zoot/files/4496882/Resources-revised.pdf)
| 1.0 | resources-page - - accessed via last button on navbar
- lists resources in a ScrollView container
Resources:
Maternal Mental Health
[Postpartum Support International](http://postpartum.net/)
[MGH Center for Women's Mental Health](https://womensmentalhealth.org/)
[National Institute of Mental Health](https://www.nimh.nih.gov/index.shtml)
[SAMHSA Hotline](https://www.samhsa.gov/find-help/national-helpline)
Crisis Text Line: Text “HELLO” to 741741
Wellness
[Yoga with Adriene ](https://www.youtube.com/user/yogawithadriene)
[Center for Mindfulness Guided Meditations](https://www.umassmemorialhealthcare.org/umass-memorial-center-mindfulness)
[Maria Shriver's Sunday Paper ](https://mariashriver.com/sundaypaper/)
Infant & Child Development
[La Leche League](https://www.llli.org/)
[HealthyChildren.org](http://healthychildren.org/)
[PBS Kids for Parents ](https://www.pbs.org/parents)
[The Child Mind Institute ](http://childmind.org/)
[Common Sense Media ](https://www.commonsensemedia.org/)
See: [Resources-revised.pdf](https://github.com/zoot-hq/zoot/files/4496882/Resources-revised.pdf)
| non_infrastructure | resources page accessed via last button on navbar lists resources in a scrollview container resources maternal mental health crisis text line text “hello” to wellness infant child development see | 0 |
46,146 | 18,958,132,739 | IssuesEvent | 2021-11-18 23:13:48 | Azure/azure-sdk-for-net | https://api.github.com/repos/Azure/azure-sdk-for-net | closed | For Connection String support, highlight Azure.Identity instead of older library | Storage Service Attention Client customer-reported question Docs needs-team-attention | The Connection String Support section should mention [Azure.Identity Migration](https://docs.microsoft.com/en-us/dotnet/api/overview/azure/app-auth-migration) instead of focusing solely on AzureServiceTokenProvider, which is part of the older, "no longer recommended" Microsoft.Azure.Services.AppAuthentication library.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 56851479-9543-a30c-37da-a1852def3797
* Version Independent ID: 4b2f90e7-dbfb-a811-64ff-9eea8b5b7443
* Content: [App Authentication client library for .NET - Version 1.6.0 - Azure for .NET Developers](https://docs.microsoft.com/en-us/dotnet/api/overview/azure/service-to-service-authentication#connection-string-support)
* Content Source: [api/overview/azure/service-to-service-authentication.md](https://github.com/Azure/azure-docs-sdk-dotnet/blob/master/api/overview/azure/service-to-service-authentication.md)
* Product: **azure**
* GitHub Login: @jlichwa
* Microsoft Alias: **jalichwa** | 1.0 | For Connection String support, highlight Azure.Identity instead of older library - The Connection String Support section should mention [Azure.Identity Migration](https://docs.microsoft.com/en-us/dotnet/api/overview/azure/app-auth-migration) instead of focusing solely on AzureServiceTokenProvider, which is part of the older, "no longer recommended" Microsoft.Azure.Services.AppAuthentication library.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 56851479-9543-a30c-37da-a1852def3797
* Version Independent ID: 4b2f90e7-dbfb-a811-64ff-9eea8b5b7443
* Content: [App Authentication client library for .NET - Version 1.6.0 - Azure for .NET Developers](https://docs.microsoft.com/en-us/dotnet/api/overview/azure/service-to-service-authentication#connection-string-support)
* Content Source: [api/overview/azure/service-to-service-authentication.md](https://github.com/Azure/azure-docs-sdk-dotnet/blob/master/api/overview/azure/service-to-service-authentication.md)
* Product: **azure**
* GitHub Login: @jlichwa
* Microsoft Alias: **jalichwa** | non_infrastructure | for connection string support highlight azure identity instead of older library the connection string support section should mention instead of focusing solely on azureservicetokenprovider which is part of the older no longer recommended microsoft azure services appauthentication library document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id dbfb content content source product azure github login jlichwa microsoft alias jalichwa | 0 |
132,466 | 12,508,769,431 | IssuesEvent | 2020-06-02 16:03:08 | zephyrproject-rtos/zephyr | https://api.github.com/repos/zephyrproject-rtos/zephyr | closed | Example of Thread creation in documentation does not compile | area: Documentation area: Kernel bug priority: low | **Describe the bug**
Creating a statically defined thread as mentioned in the [Thread ](https://docs.zephyrproject.org/latest/reference/kernel/threads/index.html#spawning-a-thread)documentation fails to compile.
Changing `K_NO_WAIT` to `0` fixes the problem.
**To Reproduce**
Steps to reproduce the behavior:
1. Create thread using `K_THREAD_DEFINE(my_tid, MY_STACK_SIZE,my_entry_point, NULL, NULL, NULL,MY_PRIORITY, 0, K_NO_WAIT);`
2. Compile
3. See error
**Expected behavior**
Example should compile.
**Impact**
Not much, just a bit of time.
**Screenshots or console output**
```
C:/zephyrproject/zephyr/include/kernel.h:1078:16: error: incompatible types when initializing type 'int' using type 'k_timeout_t' {aka 'struct <anonymous>'}
1078 | .init_delay = (delay), \
| ^
C:/zephyrproject/zephyr/include/kernel.h:1122:3: note: in expansion of macro 'Z_THREAD_INITIALIZER'
1122 | Z_THREAD_INITIALIZER(&_k_thread_obj_##name, \
| ^~~~~~~~~~~~~~~~~~~~
C:/zephyrproject/zephyr/samples/hello_world/src/main.c:19:1: note: in expansion of macro 'K_THREAD_DEFINE'
19 | K_THREAD_DEFINE(my_tid, MY_STACK_SIZE,
| ^~~~~~~~~~~~~~~
```
**Environment (please complete the following information):**
- OS: Windows
- Toolchain GCC
- master
| 1.0 | Example of Thread creation in documentation does not compile - **Describe the bug**
Creating a statically defined thread as mentioned in the [Thread ](https://docs.zephyrproject.org/latest/reference/kernel/threads/index.html#spawning-a-thread)documentation fails to compile.
Changing `K_NO_WAIT` to `0` fixes the problem.
**To Reproduce**
Steps to reproduce the behavior:
1. Create thread using `K_THREAD_DEFINE(my_tid, MY_STACK_SIZE,my_entry_point, NULL, NULL, NULL,MY_PRIORITY, 0, K_NO_WAIT);`
2. Compile
3. See error
**Expected behavior**
Example should compile.
**Impact**
Not much, just a bit of time.
**Screenshots or console output**
```
C:/zephyrproject/zephyr/include/kernel.h:1078:16: error: incompatible types when initializing type 'int' using type 'k_timeout_t' {aka 'struct <anonymous>'}
1078 | .init_delay = (delay), \
| ^
C:/zephyrproject/zephyr/include/kernel.h:1122:3: note: in expansion of macro 'Z_THREAD_INITIALIZER'
1122 | Z_THREAD_INITIALIZER(&_k_thread_obj_##name, \
| ^~~~~~~~~~~~~~~~~~~~
C:/zephyrproject/zephyr/samples/hello_world/src/main.c:19:1: note: in expansion of macro 'K_THREAD_DEFINE'
19 | K_THREAD_DEFINE(my_tid, MY_STACK_SIZE,
| ^~~~~~~~~~~~~~~
```
**Environment (please complete the following information):**
- OS: Windows
- Toolchain GCC
- master
| non_infrastructure | example of thread creation in documentation does not compile describe the bug creating a statically defined thread as mentioned in the fails to compile changing k no wait to fixes the problem to reproduce steps to reproduce the behavior create thread using k thread define my tid my stack size my entry point null null null my priority k no wait compile see error expected behavior example should compile impact not much just a bit of time screenshots or console output c zephyrproject zephyr include kernel h error incompatible types when initializing type int using type k timeout t aka struct init delay delay c zephyrproject zephyr include kernel h note in expansion of macro z thread initializer z thread initializer k thread obj name c zephyrproject zephyr samples hello world src main c note in expansion of macro k thread define k thread define my tid my stack size environment please complete the following information os windows toolchain gcc master | 0 |
746,906 | 26,050,385,828 | IssuesEvent | 2022-12-22 18:02:33 | nychealth/EH-dataportal | https://api.github.com/repos/nychealth/EH-dataportal | closed | Act on SEO Audit | PRIORITY | I pulled out SEO audit tasks into a [private board here](https://github.com/orgs/nychealth/projects/3/views/1?layout=board). @cgettings, I'm opening up a branch `hotfix-SEO-audit` to start to work on these changes. I'm finding a few things that confuse me, so might tag you in here for some conversation and thoughts about them. ~~strikethroughs~~ for things that are NA.
**Meta**
- [x] Pages without titles
~~Pages with multiple titles~~
~~Pages with duplicate titles~~
- [x] Duplicate meta descriptions
**High priority**
- [x] Incorrect region/language codes
- [x] Duplicate titles
~~Content exact duplicates (exclusively things on `IndicatorPublic` not `/beta`)~~
- [x] 4xx error
- [x] Broken internal links
- [x] Broken external links
~~Broken internal images~~
**medium priority**
- [x] H1 missing
**low priority**
- [x] Image missing alt
- [ ] URL multiple slashes | 1.0 | Act on SEO Audit - I pulled out SEO audit tasks into a [private board here](https://github.com/orgs/nychealth/projects/3/views/1?layout=board). @cgettings, I'm opening up a branch `hotfix-SEO-audit` to start to work on these changes. I'm finding a few things that confuse me, so might tag you in here for some conversation and thoughts about them. ~~strikethroughs~~ for things that are NA.
**Meta**
- [x] Pages without titles
~~Pages with multiple titles~~
~~Pages with duplicate titles~~
- [x] Duplicate meta descriptions
**High priority**
- [x] Incorrect region/language codes
- [x] Duplicate titles
~~Content exact duplicates (exclusively things on `IndicatorPublic` not `/beta`)~~
- [x] 4xx error
- [x] Broken internal links
- [x] Broken external links
~~Broken internal images~~
**medium priority**
- [x] H1 missing
**low priority**
- [x] Image missing alt
- [ ] URL multiple slashes | non_infrastructure | act on seo audit i pulled out seo audit tasks into a cgettings i m opening up a branch hotfix seo audit to start to work on these changes i m finding a few things that confuse me so might tag you in here for some conversation and thoughts about them strikethroughs for things that are na meta pages without titles pages with multiple titles pages with duplicate titles duplicate meta descriptions high priority incorrect region language codes duplicate titles content exact duplicates exclusively things on indicatorpublic not beta error broken internal links broken external links broken internal images medium priority missing low priority image missing alt url multiple slashes | 0 |
16,825 | 12,152,117,456 | IssuesEvent | 2020-04-24 21:26:42 | BCDevOps/developer-experience | https://api.github.com/repos/BCDevOps/developer-experience | opened | Add check to ensure heketi device free is not too out of sync with LVM | Infrastructure action-required | https://trello.com/c/lFZp1xrN/87-add-check-to-ensure-heketi-device-free-is-not-too-out-of-sync-with-lvm
In response to a recent incident where we ran out of disk space by virtue of heketi thinking we were out when LVM "pvs" in PROD OCS felt otherwise.
Create a new check so that if heketi feels disk free is a certain percentage out of sync with LVM on each of the OCS nodes, then alert (WARN only should be fine) so that pro-active management of this can take place before it gets out of hand. | 1.0 | Add check to ensure heketi device free is not too out of sync with LVM - https://trello.com/c/lFZp1xrN/87-add-check-to-ensure-heketi-device-free-is-not-too-out-of-sync-with-lvm
In response to a recent incident where we ran out of disk space by virtue of heketi thinking we were out when LVM "pvs" in PROD OCS felt otherwise.
Create a new check so that if heketi feels disk free is a certain percentage out of sync with LVM on each of the OCS nodes, then alert (WARN only should be fine) so that pro-active management of this can take place before it gets out of hand. | infrastructure | add check to ensure heketi device free is not too out of sync with lvm in response to a recent incident where we ran out of disk space by virtue of heketi thinking we were out when lvm pvs in prod ocs felt otherwise create a new check so that if heketi feels disk free is a certain percentage out of sync with lvm on each of the ocs nodes then alert warn only should be fine so that pro active management of this can take place before it gets out of hand | 1 |
13,616 | 10,348,245,918 | IssuesEvent | 2019-09-04 19:19:54 | HumanCellAtlas/secondary-analysis | https://api.github.com/repos/HumanCellAtlas/secondary-analysis | closed | Use google pub/sub queue in Lira | infrastructure | Update Lira to add DSS notifications to a google pub/sub topic to fix the timeout/duplicate notifications issue. Add a new endpoint to Lira that subscribes to the topic, does the bundle pre-processing to add a hash of the inputs and checks Cromwell for workflows before submitting a new one.
In the future, we can iterate on this so that Lira saves workflow/hash/bundle info to Redis or Firestore to allow for deduplication and faster look-up of what has been run before.
┆Issue is synchronized with this [Jira Story](https://broadinstitute.atlassian.net/browse/GH-470)
| 1.0 | Use google pub/sub queue in Lira - Update Lira to add DSS notifications to a google pub/sub topic to fix the timeout/duplicate notifications issue. Add a new endpoint to Lira that subscribes to the topic, does the bundle pre-processing to add a hash of the inputs and checks Cromwell for workflows before submitting a new one.
In the future, we can iterate on this so that Lira saves workflow/hash/bundle info to Redis or Firestore to allow for deduplication and faster look-up of what has been run before.
┆Issue is synchronized with this [Jira Story](https://broadinstitute.atlassian.net/browse/GH-470)
| infrastructure | use google pub sub queue in lira update lira to add dss notifications to a google pub sub topic to fix the timeout duplicate notifications issue add a new endpoint to lira that subscribes to the topic does the bundle pre processing to add a hash of the inputs and checks cromwell for workflows before submitting a new one in the future we can iterate on this so that lira saves workflow hash bundle info to redis or firestore to allow for deduplication and faster look up of what has been run before ┆issue is synchronized with this | 1 |
1,118 | 3,040,346,777 | IssuesEvent | 2015-08-07 14:56:59 | deconst/deconst-docs | https://api.github.com/repos/deconst/deconst-docs | closed | Script to trim out-of-date CLB nodes | infrastructure | Write a `script/` entry for deconst/deploy that locates your instance's CLB, probes workers for active services, and ensures that the CLB nodes match. This would save me a lot of manual poking around in the UI once I flip the deployment name. | 1.0 | Script to trim out-of-date CLB nodes - Write a `script/` entry for deconst/deploy that locates your instance's CLB, probes workers for active services, and ensures that the CLB nodes match. This would save me a lot of manual poking around in the UI once I flip the deployment name. | infrastructure | script to trim out of date clb nodes write a script entry for deconst deploy that locates your instance s clb probes workers for active services and ensures that the clb nodes match this would save me a lot of manual poking around in the ui once i flip the deployment name | 1 |
283,837 | 8,724,408,969 | IssuesEvent | 2018-12-10 05:01:01 | rancher/rancher | https://api.github.com/repos/rancher/rancher | opened | Change the default workload alert rule | alpha-priority/0 area/alerting area/monitoring kind/bug-qa releases/alpha1 team/cn | rancher/rancher:v2.2.0-alpha2
The rule is
```
sum(container_memory_working_set_bytes{pod_name=~"prometheus-cluster-monitoring.*"}) by (pod_name) / sum(label_join(kube_pod_container_resource_limits_memory_bytes{pod=~"prometheus-cluster-monitoring.*"},"pod_name", "", "pod")) by (pod_name)
```
The pod name is specified to prometheus-cluster-monitoring. It doesn't make sense as it is the pod for cluster monitoring. We need to change the pod to something else. | 1.0 | Change the default workload alert rule - rancher/rancher:v2.2.0-alpha2
The rule is
```
sum(container_memory_working_set_bytes{pod_name=~"prometheus-cluster-monitoring.*"}) by (pod_name) / sum(label_join(kube_pod_container_resource_limits_memory_bytes{pod=~"prometheus-cluster-monitoring.*"},"pod_name", "", "pod")) by (pod_name)
```
The pod name is specified to prometheus-cluster-monitoring. It doesn't make sense as it is the pod for cluster monitoring. We need to change the pod to something else. | non_infrastructure | change the default workload alert rule rancher rancher the rule is sum container memory working set bytes pod name prometheus cluster monitoring by pod name sum label join kube pod container resource limits memory bytes pod prometheus cluster monitoring pod name pod by pod name the pod name is specified to prometheus cluster monitoring it doesn t make sense as it is the pod for cluster monitoring we need to change the pod to something else | 0 |
315,597 | 9,629,234,092 | IssuesEvent | 2019-05-15 09:09:09 | WoWManiaUK/Blackwing-Lair | https://api.github.com/repos/WoWManiaUK/Blackwing-Lair | closed | [Spell] Weapon skills | Class Fixed Confirmed Fixed in Dev Priority-High | ID 76299 (lock) > Swords do not work
ID 76298 (mage) > Swords and daggers do not work!
ID 76301 (priest) > Daggers do not work
As stated above, some of the weapon skills that are granted by these spells are not working. This bug affects Warlocks, Mages and Priests as far as we tested, couldn't find an issue on other classes.
They simply can't equip some of the weapon types they should be able. (not visual problem) | 1.0 | [Spell] Weapon skills - ID 76299 (lock) > Swords do not work
ID 76298 (mage) > Swords and daggers do not work!
ID 76301 (priest) > Daggers do not work
As stated above, some of the weapon skills that are granted by these spells are not working. This bug affects Warlocks, Mages and Priests as far as we tested, couldn't find an issue on other classes.
They simply can't equip some of the weapon types they should be able. (not visual problem) | non_infrastructure | weapon skills id lock swords do not work id mage swords and daggers do not work id priest daggers do not work as stated above some of the weapon skills that are granted by these spells are not working this bug affects warlocks mages and priests as far as we tested couldn t find an issue on other classes they simply can t equip some of the weapon types they should be able not visual problem | 0 |
16,254 | 11,885,653,634 | IssuesEvent | 2020-03-27 20:04:16 | reapit/foundations | https://api.github.com/repos/reapit/foundations | closed | Investigate means of translating event transmissions into a semantics of the platform | infrastructure investigate platform-team | The events that will be streamed from client datasets will not be in a format that webhooks consumers can easily consume or understand. We need to understand how a 'translation' process could be injected into our datastreaming tech. A tech like kinesis firehose seems to fit the bill.
R&D and discussion. | 1.0 | Investigate means of translating event transmissions into a semantics of the platform - The events that will be streamed from client datasets will not be in a format that webhooks consumers can easily consume or understand. We need to understand how a 'translation' process could be injected into our datastreaming tech. A tech like kinesis firehose seems to fit the bill.
R&D and discussion. | infrastructure | investigate means of translating event transmissions into a semantics of the platform the events that will be streamed from client datasets will not be in a format that webhooks consumers can easily consume or understand we need to understand how a translation process could be injected into our datastreaming tech a tech like kinesis firehose seems to fit the bill r d and discussion | 1 |
547,272 | 16,040,705,256 | IssuesEvent | 2021-04-22 07:30:10 | googleapis/java-aiplatform | https://api.github.com/repos/googleapis/java-aiplatform | reopened | aiplatform.CreateTrainingPipelineTextEntityExtractionSampleTest: testCreateTrainingPipelineTextEntityExtractionSample failed | api: aiplatform flakybot: flaky flakybot: issue priority: p1 type: bug | This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/master/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: 8cfdab67f373cbd7aa3f139a82c1d63502a360fa
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/109b6dd4-4ffe-453b-8e53-5e15c4a70504), [Sponge](http://sponge2/109b6dd4-4ffe-453b-8e53-5e15c4a70504)
status: failed
<details><summary>Test output</summary><br><pre>java.lang.NullPointerException
at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:892)
at com.google.cloud.aiplatform.v1.TrainingPipelineName.<init>(TrainingPipelineName.java:50)
at com.google.cloud.aiplatform.v1.TrainingPipelineName.<init>(TrainingPipelineName.java:31)
at com.google.cloud.aiplatform.v1.TrainingPipelineName$Builder.build(TrainingPipelineName.java:224)
at com.google.cloud.aiplatform.v1.TrainingPipelineName.of(TrainingPipelineName.java:78)
at aiplatform.CancelTrainingPipelineSample.cancelTrainingPipelineSample(CancelTrainingPipelineSample.java:49)
at aiplatform.CreateTrainingPipelineTextEntityExtractionSampleTest.tearDown(CreateTrainingPipelineTextEntityExtractionSampleTest.java:72)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.junit.internal.runners.statements.RunAfters.invokeMethod(RunAfters.java:46)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
</pre></details> | 1.0 | aiplatform.CreateTrainingPipelineTextEntityExtractionSampleTest: testCreateTrainingPipelineTextEntityExtractionSample failed - This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/master/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: 8cfdab67f373cbd7aa3f139a82c1d63502a360fa
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/109b6dd4-4ffe-453b-8e53-5e15c4a70504), [Sponge](http://sponge2/109b6dd4-4ffe-453b-8e53-5e15c4a70504)
status: failed
<details><summary>Test output</summary><br><pre>java.lang.NullPointerException
at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:892)
at com.google.cloud.aiplatform.v1.TrainingPipelineName.<init>(TrainingPipelineName.java:50)
at com.google.cloud.aiplatform.v1.TrainingPipelineName.<init>(TrainingPipelineName.java:31)
at com.google.cloud.aiplatform.v1.TrainingPipelineName$Builder.build(TrainingPipelineName.java:224)
at com.google.cloud.aiplatform.v1.TrainingPipelineName.of(TrainingPipelineName.java:78)
at aiplatform.CancelTrainingPipelineSample.cancelTrainingPipelineSample(CancelTrainingPipelineSample.java:49)
at aiplatform.CreateTrainingPipelineTextEntityExtractionSampleTest.tearDown(CreateTrainingPipelineTextEntityExtractionSampleTest.java:72)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.junit.internal.runners.statements.RunAfters.invokeMethod(RunAfters.java:46)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
</pre></details> | non_infrastructure | aiplatform createtrainingpipelinetextentityextractionsampletest testcreatetrainingpipelinetextentityextractionsample 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 java lang nullpointerexception at com google common base preconditions checknotnull preconditions java at com google cloud aiplatform trainingpipelinename trainingpipelinename java at com google cloud aiplatform trainingpipelinename trainingpipelinename java at com google cloud aiplatform trainingpipelinename builder build trainingpipelinename java at com google cloud aiplatform trainingpipelinename of trainingpipelinename java at aiplatform canceltrainingpipelinesample canceltrainingpipelinesample canceltrainingpipelinesample java at aiplatform createtrainingpipelinetextentityextractionsampletest teardown createtrainingpipelinetextentityextractionsampletest java at sun reflect nativemethodaccessorimpl native method at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org junit runners model frameworkmethod runreflectivecall frameworkmethod java at org junit internal runners model reflectivecallable run reflectivecallable java at org junit runners model frameworkmethod invokeexplosively frameworkmethod java at org junit internal runners statements runafters invokemethod runafters java at org junit internal runners statements runafters evaluate runafters java at org junit runners parentrunner evaluate parentrunner java at org junit runners evaluate java at org junit runners parentrunner runleaf parentrunner java at org junit runners runchild java at org junit runners runchild java at org junit runners parentrunner run parentrunner java at org junit runners parentrunner schedule parentrunner java at org junit runners parentrunner runchildren parentrunner java at org junit runners parentrunner access parentrunner java at org junit runners parentrunner evaluate parentrunner java at org junit internal runners statements runbefores evaluate runbefores java at org junit runners parentrunner evaluate parentrunner java at org junit runners parentrunner run parentrunner java at org apache maven surefire execute java at org apache maven surefire executewithrerun java at org apache maven surefire executetestset java at org apache maven surefire invoke java at org apache maven surefire booter forkedbooter runsuitesinprocess forkedbooter java at org apache maven surefire booter forkedbooter execute forkedbooter java at org apache maven surefire booter forkedbooter run forkedbooter java at org apache maven surefire booter forkedbooter main forkedbooter java | 0 |
23,146 | 15,862,013,001 | IssuesEvent | 2021-04-08 11:03:04 | emory-libraries/blacklight-catalog | https://api.github.com/repos/emory-libraries/blacklight-catalog | closed | SPIKE: Determine what Cloudwatch Metrics are available to set benchmarks on SOLR Performance | Infrastructure | As the product owner, I would like for members of the Infrastructure Team, Collin Brittle, and Mark Bussey to determine what Cloudwatch Metrics are available to set benchmarks on SOLR performance. The outcome of this spike is to document what metrics are currently in place or should be implemented to set benchmarks on a steady state for SOLR performance so that alerts can be implemented when any degradation of performance occurs similar to the recent errors when SOLR has stopped communicating with the Test environment.
Considerations:
- [ ] Cloudwatch metrics on SOLR to determine a baseline on connections to test environment
- [ ] Review DLP Alerts slack channel to the various alerts from Cloudwatch indicating SOLR has stopped communicating with Test. These same errors are occurring for both DLP and Blacklight test environments
Acceptance Criteria:
- [x] Meeting scheduled with @mlooney, @libah, @libdgg, @AGCooper, @rotated8, @mark-dce to review information above.
- [x] Metrics (existing or new) and benchmarks should be documented within ticket.
- [x] Create a new ticket for backlog to establish Cloudwatch alarms for any degradation of performance with SOLR that would indicate a lack of communication between SOLR and any of the associated environments in Blacklight or DLP.
- [x] Create a new ticket for backlog to rename DLP Alerts slack channel that includes the review of any scripts or other documentation that will need updating if the slack channel is renamed.
| 1.0 | SPIKE: Determine what Cloudwatch Metrics are available to set benchmarks on SOLR Performance - As the product owner, I would like for members of the Infrastructure Team, Collin Brittle, and Mark Bussey to determine what Cloudwatch Metrics are available to set benchmarks on SOLR performance. The outcome of this spike is to document what metrics are currently in place or should be implemented to set benchmarks on a steady state for SOLR performance so that alerts can be implemented when any degradation of performance occurs similar to the recent errors when SOLR has stopped communicating with the Test environment.
Considerations:
- [ ] Cloudwatch metrics on SOLR to determine a baseline on connections to test environment
- [ ] Review DLP Alerts slack channel to the various alerts from Cloudwatch indicating SOLR has stopped communicating with Test. These same errors are occurring for both DLP and Blacklight test environments
Acceptance Criteria:
- [x] Meeting scheduled with @mlooney, @libah, @libdgg, @AGCooper, @rotated8, @mark-dce to review information above.
- [x] Metrics (existing or new) and benchmarks should be documented within ticket.
- [x] Create a new ticket for backlog to establish Cloudwatch alarms for any degradation of performance with SOLR that would indicate a lack of communication between SOLR and any of the associated environments in Blacklight or DLP.
- [x] Create a new ticket for backlog to rename DLP Alerts slack channel that includes the review of any scripts or other documentation that will need updating if the slack channel is renamed.
| infrastructure | spike determine what cloudwatch metrics are available to set benchmarks on solr performance as the product owner i would like for members of the infrastructure team collin brittle and mark bussey to determine what cloudwatch metrics are available to set benchmarks on solr performance the outcome of this spike is to document what metrics are currently in place or should be implemented to set benchmarks on a steady state for solr performance so that alerts can be implemented when any degradation of performance occurs similar to the recent errors when solr has stopped communicating with the test environment considerations cloudwatch metrics on solr to determine a baseline on connections to test environment review dlp alerts slack channel to the various alerts from cloudwatch indicating solr has stopped communicating with test these same errors are occurring for both dlp and blacklight test environments acceptance criteria meeting scheduled with mlooney libah libdgg agcooper mark dce to review information above metrics existing or new and benchmarks should be documented within ticket create a new ticket for backlog to establish cloudwatch alarms for any degradation of performance with solr that would indicate a lack of communication between solr and any of the associated environments in blacklight or dlp create a new ticket for backlog to rename dlp alerts slack channel that includes the review of any scripts or other documentation that will need updating if the slack channel is renamed | 1 |
135,910 | 30,446,328,389 | IssuesEvent | 2023-07-15 18:10:00 | bodynar/mas.payments | https://api.github.com/repos/bodynar/mas.payments | closed | CRUD operations | enhancement code | Use different models for CRUD operations on client.
Example: addPaymentType uses paymentType model which used in getPaymentTypes | 1.0 | CRUD operations - Use different models for CRUD operations on client.
Example: addPaymentType uses paymentType model which used in getPaymentTypes | non_infrastructure | crud operations use different models for crud operations on client example addpaymenttype uses paymenttype model which used in getpaymenttypes | 0 |
153 | 2,539,442,117 | IssuesEvent | 2015-01-27 15:24:25 | dinyar/uGMTfirmware | https://api.github.com/repos/dinyar/uGMTfirmware | closed | Use included build system for firmware build | infrastructure | As we aren't using smartxplorer anymore our custom build scripts aren't necessary any more. We should remove them from the repo and adapt the readme. | 1.0 | Use included build system for firmware build - As we aren't using smartxplorer anymore our custom build scripts aren't necessary any more. We should remove them from the repo and adapt the readme. | infrastructure | use included build system for firmware build as we aren t using smartxplorer anymore our custom build scripts aren t necessary any more we should remove them from the repo and adapt the readme | 1 |
20,423 | 4,543,567,658 | IssuesEvent | 2016-09-10 06:31:18 | marionebl/led-canvas | https://api.github.com/repos/marionebl/led-canvas | closed | Write a comprehensible README | documentation | Compose a README containing:
* Synopsis
* Badges
* Plenty of bragging about performance and overall kewlness
* Quick Start
* Links to sub projects | 1.0 | Write a comprehensible README - Compose a README containing:
* Synopsis
* Badges
* Plenty of bragging about performance and overall kewlness
* Quick Start
* Links to sub projects | non_infrastructure | write a comprehensible readme compose a readme containing synopsis badges plenty of bragging about performance and overall kewlness quick start links to sub projects | 0 |
27,095 | 21,162,275,286 | IssuesEvent | 2022-04-07 10:26:36 | UCL/hivpy | https://api.github.com/repos/UCL/hivpy | opened | Sampling - design and implement | enhancement infrastructure | When and where do we sample
How do we pass the values on to the model | 1.0 | Sampling - design and implement - When and where do we sample
How do we pass the values on to the model | infrastructure | sampling design and implement when and where do we sample how do we pass the values on to the model | 1 |
473,853 | 13,648,473,632 | IssuesEvent | 2020-09-26 09:24:36 | garden-io/garden | https://api.github.com/repos/garden-io/garden | closed | Garden ignores `.env` files if they are gitignored | bug priority:medium stale | ## Bug
### Current Behavior
[Our docs](https://docs.garden.io/guides/variables-and-templating#variable-files-varfiles) mention you can store secrets in `.gitignore`-ed env files. However, those same env files get ignored by Garden so the content is never applied.
This came up on the community Slack.
### Expected behavior
Garden should pick up those env files.
### Reproducible example
N/A
### Workaround
Encrypt the secrets and store them in version control. This may not be a good workaround for all users.
### Suggested solution(s)
N/A
### Additional context
N/A
### Your environment
Latest `master`
| 1.0 | Garden ignores `.env` files if they are gitignored - ## Bug
### Current Behavior
[Our docs](https://docs.garden.io/guides/variables-and-templating#variable-files-varfiles) mention you can store secrets in `.gitignore`-ed env files. However, those same env files get ignored by Garden so the content is never applied.
This came up on the community Slack.
### Expected behavior
Garden should pick up those env files.
### Reproducible example
N/A
### Workaround
Encrypt the secrets and store them in version control. This may not be a good workaround for all users.
### Suggested solution(s)
N/A
### Additional context
N/A
### Your environment
Latest `master`
| non_infrastructure | garden ignores env files if they are gitignored bug current behavior mention you can store secrets in gitignore ed env files however those same env files get ignored by garden so the content is never applied this came up on the community slack expected behavior garden should pick up those env files reproducible example n a workaround encrypt the secrets and store them in version control this may not be a good workaround for all users suggested solution s n a additional context n a your environment latest master | 0 |
34,540 | 30,111,947,082 | IssuesEvent | 2023-06-30 08:28:55 | dotnet/roslyn | https://api.github.com/repos/dotnet/roslyn | closed | [Automated] PRs inserted in VS build main-33829.535 | Area-Infrastructure untriaged vs-insertion | [View Complete Diff of Changes](https://github.com/dotnet/roslyn/compare/d0f4099ffa7f8ff31fd397a4a96f404e1cd7dfc7...1f2bdd683297875a0ebccf099e41289ec9cd2291?w=1)
- [Allow declaring ref fields as elements of inline arrays. (68820)](https://github.com/dotnet/roslyn/pull/68820)
- [Fix SuppressMessage attributes working on primary constructors (68706)](https://github.com/dotnet/roslyn/pull/68706)
- [Rename background analysis option name (68810)](https://github.com/dotnet/roslyn/pull/68810)
- [Include expected custom modifiers for `in` parameters of virtual operators. (68808)](https://github.com/dotnet/roslyn/pull/68808)
- ["Fix" LSP semantic token modifiers (68744)](https://github.com/dotnet/roslyn/pull/68744)
- [remove long gone owners (68755)](https://github.com/dotnet/roslyn/pull/68755)
- [Update VSTelemetry package version (68806)](https://github.com/dotnet/roslyn/pull/68806)
- [Roslyn side changes to enable full solution background analysis in LSP/VSCode (68799)](https://github.com/dotnet/roslyn/pull/68799)
- [More workarounds for VS Code project system issues (68792)](https://github.com/dotnet/roslyn/pull/68792)
- [Fixes SyntaxFactory.UsingDirective overload which always throws (68762)](https://github.com/dotnet/roslyn/pull/68762)
- [Fixed CA1854: Prefer IDictionary.TryGetValue(TKey, out TValue) occurrences (66515)](https://github.com/dotnet/roslyn/pull/66515)
- [Test GetTypeInfo on values given to missing attribute (68427)](https://github.com/dotnet/roslyn/pull/68427)
- [EnC: Implement support for editing types with primary constructors (68477)](https://github.com/dotnet/roslyn/pull/68477)
- [Add razor compiler EA project ref (68732)](https://github.com/dotnet/roslyn/pull/68732)
- [Merge 'InlineArrays' feature into 'main' (68783)](https://github.com/dotnet/roslyn/pull/68783)
- [EnC: Stop reporting CS7101 on runtime that supports generic updates (68601)](https://github.com/dotnet/roslyn/pull/68601)
- [Fix assert when using `__arglist` and `in` arguments together (68726)](https://github.com/dotnet/roslyn/pull/68726)
- [Merge 'main' into InlineArrays (68717)](https://github.com/dotnet/roslyn/pull/68717)
- [Flesh out implementation of ref-safety rules for inline array operations. (68597)](https://github.com/dotnet/roslyn/pull/68597)
- [Omit Slice call when start is 0 and 0 <= end <=length. (68660)](https://github.com/dotnet/roslyn/pull/68660)
- [Avoid `Span` creation when indexing into an inline array with a constant. (68642)](https://github.com/dotnet/roslyn/pull/68642)
- [Address a prototype comment (68613)](https://github.com/dotnet/roslyn/pull/68613)
- [Improve error reporting around inline array access. (68551)](https://github.com/dotnet/roslyn/pull/68551)
- [Ensure adequate SemanticModel coverage for inline arrays. (68509)](https://github.com/dotnet/roslyn/pull/68509)
- [Extract a common helper for adding/getting private implementation class methods. (68502)](https://github.com/dotnet/roslyn/pull/68502)
- [Implement IOperation support for `foreach` over an inline array. (68506)](https://github.com/dotnet/roslyn/pull/68506)
- [Merge 'main' into InlineArrays (68496)](https://github.com/dotnet/roslyn/pull/68496)
- [Support 'foreach' for inline arrays. (68297)](https://github.com/dotnet/roslyn/pull/68297)
- [Implement definite assignment and region analysis for inline array types (68339)](https://github.com/dotnet/roslyn/pull/68339)
- [Implement IOperation support for inline array access (68373)](https://github.com/dotnet/roslyn/pull/68373)
- [Move inline arrays tests to Emit2 project due to reaching the string heap limit (68321)](https://github.com/dotnet/roslyn/pull/68321)
- [Implement runtime capability check for inline arrays feature. (68272)](https://github.com/dotnet/roslyn/pull/68272)
- [Use net8 ref assemblies for inline array testing. (68252)](https://github.com/dotnet/roslyn/pull/68252)
- [Disallow inline array operations in expression trees. (68222)](https://github.com/dotnet/roslyn/pull/68222)
- [Ensure proper handling of generic SynthesizedGlobalMethodSymbol. (68211)](https://github.com/dotnet/roslyn/pull/68211)
- [Validate InlineArrayAttribute applications on types in source. (68195)](https://github.com/dotnet/roslyn/pull/68195)
- [Use net8.0 runtime for InlineArray tests (68190)](https://github.com/dotnet/roslyn/pull/68190)
- [Merge 'dotnet/main' into InlineArrays (68215)](https://github.com/dotnet/roslyn/pull/68215)
- [Implement compile-time boundary checks around inline arrays access. (68178)](https://github.com/dotnet/roslyn/pull/68178)
- [Implement more validation for inline array element access and conversion scenarios (68146)](https://github.com/dotnet/roslyn/pull/68146)
- [Merge 'dotnet/main' into InlineArrays (68140)](https://github.com/dotnet/roslyn/pull/68140)
- [Enable some `await` scenarios involving inline arrays (68129)](https://github.com/dotnet/roslyn/pull/68129)
- [Break cycles in attribute binding for inline arrays (68067)](https://github.com/dotnet/roslyn/pull/68067)
- [Check language version for inline arrays feature (68109)](https://github.com/dotnet/roslyn/pull/68109)
- [Finalize testing and implementation around object initializers for inline arrays. (68064)](https://github.com/dotnet/roslyn/pull/68064)
- [Merge 'main' into InlineArrays (68061)](https://github.com/dotnet/roslyn/pull/68061)
- [Implement support for Inline Array conversions (68019)](https://github.com/dotnet/roslyn/pull/68019)
- [Merge 'main' into `InlineArrays` (67915)](https://github.com/dotnet/roslyn/pull/67915)
- [Implement element access for inline array types (67830)](https://github.com/dotnet/roslyn/pull/67830)
| 1.0 | [Automated] PRs inserted in VS build main-33829.535 - [View Complete Diff of Changes](https://github.com/dotnet/roslyn/compare/d0f4099ffa7f8ff31fd397a4a96f404e1cd7dfc7...1f2bdd683297875a0ebccf099e41289ec9cd2291?w=1)
- [Allow declaring ref fields as elements of inline arrays. (68820)](https://github.com/dotnet/roslyn/pull/68820)
- [Fix SuppressMessage attributes working on primary constructors (68706)](https://github.com/dotnet/roslyn/pull/68706)
- [Rename background analysis option name (68810)](https://github.com/dotnet/roslyn/pull/68810)
- [Include expected custom modifiers for `in` parameters of virtual operators. (68808)](https://github.com/dotnet/roslyn/pull/68808)
- ["Fix" LSP semantic token modifiers (68744)](https://github.com/dotnet/roslyn/pull/68744)
- [remove long gone owners (68755)](https://github.com/dotnet/roslyn/pull/68755)
- [Update VSTelemetry package version (68806)](https://github.com/dotnet/roslyn/pull/68806)
- [Roslyn side changes to enable full solution background analysis in LSP/VSCode (68799)](https://github.com/dotnet/roslyn/pull/68799)
- [More workarounds for VS Code project system issues (68792)](https://github.com/dotnet/roslyn/pull/68792)
- [Fixes SyntaxFactory.UsingDirective overload which always throws (68762)](https://github.com/dotnet/roslyn/pull/68762)
- [Fixed CA1854: Prefer IDictionary.TryGetValue(TKey, out TValue) occurrences (66515)](https://github.com/dotnet/roslyn/pull/66515)
- [Test GetTypeInfo on values given to missing attribute (68427)](https://github.com/dotnet/roslyn/pull/68427)
- [EnC: Implement support for editing types with primary constructors (68477)](https://github.com/dotnet/roslyn/pull/68477)
- [Add razor compiler EA project ref (68732)](https://github.com/dotnet/roslyn/pull/68732)
- [Merge 'InlineArrays' feature into 'main' (68783)](https://github.com/dotnet/roslyn/pull/68783)
- [EnC: Stop reporting CS7101 on runtime that supports generic updates (68601)](https://github.com/dotnet/roslyn/pull/68601)
- [Fix assert when using `__arglist` and `in` arguments together (68726)](https://github.com/dotnet/roslyn/pull/68726)
- [Merge 'main' into InlineArrays (68717)](https://github.com/dotnet/roslyn/pull/68717)
- [Flesh out implementation of ref-safety rules for inline array operations. (68597)](https://github.com/dotnet/roslyn/pull/68597)
- [Omit Slice call when start is 0 and 0 <= end <=length. (68660)](https://github.com/dotnet/roslyn/pull/68660)
- [Avoid `Span` creation when indexing into an inline array with a constant. (68642)](https://github.com/dotnet/roslyn/pull/68642)
- [Address a prototype comment (68613)](https://github.com/dotnet/roslyn/pull/68613)
- [Improve error reporting around inline array access. (68551)](https://github.com/dotnet/roslyn/pull/68551)
- [Ensure adequate SemanticModel coverage for inline arrays. (68509)](https://github.com/dotnet/roslyn/pull/68509)
- [Extract a common helper for adding/getting private implementation class methods. (68502)](https://github.com/dotnet/roslyn/pull/68502)
- [Implement IOperation support for `foreach` over an inline array. (68506)](https://github.com/dotnet/roslyn/pull/68506)
- [Merge 'main' into InlineArrays (68496)](https://github.com/dotnet/roslyn/pull/68496)
- [Support 'foreach' for inline arrays. (68297)](https://github.com/dotnet/roslyn/pull/68297)
- [Implement definite assignment and region analysis for inline array types (68339)](https://github.com/dotnet/roslyn/pull/68339)
- [Implement IOperation support for inline array access (68373)](https://github.com/dotnet/roslyn/pull/68373)
- [Move inline arrays tests to Emit2 project due to reaching the string heap limit (68321)](https://github.com/dotnet/roslyn/pull/68321)
- [Implement runtime capability check for inline arrays feature. (68272)](https://github.com/dotnet/roslyn/pull/68272)
- [Use net8 ref assemblies for inline array testing. (68252)](https://github.com/dotnet/roslyn/pull/68252)
- [Disallow inline array operations in expression trees. (68222)](https://github.com/dotnet/roslyn/pull/68222)
- [Ensure proper handling of generic SynthesizedGlobalMethodSymbol. (68211)](https://github.com/dotnet/roslyn/pull/68211)
- [Validate InlineArrayAttribute applications on types in source. (68195)](https://github.com/dotnet/roslyn/pull/68195)
- [Use net8.0 runtime for InlineArray tests (68190)](https://github.com/dotnet/roslyn/pull/68190)
- [Merge 'dotnet/main' into InlineArrays (68215)](https://github.com/dotnet/roslyn/pull/68215)
- [Implement compile-time boundary checks around inline arrays access. (68178)](https://github.com/dotnet/roslyn/pull/68178)
- [Implement more validation for inline array element access and conversion scenarios (68146)](https://github.com/dotnet/roslyn/pull/68146)
- [Merge 'dotnet/main' into InlineArrays (68140)](https://github.com/dotnet/roslyn/pull/68140)
- [Enable some `await` scenarios involving inline arrays (68129)](https://github.com/dotnet/roslyn/pull/68129)
- [Break cycles in attribute binding for inline arrays (68067)](https://github.com/dotnet/roslyn/pull/68067)
- [Check language version for inline arrays feature (68109)](https://github.com/dotnet/roslyn/pull/68109)
- [Finalize testing and implementation around object initializers for inline arrays. (68064)](https://github.com/dotnet/roslyn/pull/68064)
- [Merge 'main' into InlineArrays (68061)](https://github.com/dotnet/roslyn/pull/68061)
- [Implement support for Inline Array conversions (68019)](https://github.com/dotnet/roslyn/pull/68019)
- [Merge 'main' into `InlineArrays` (67915)](https://github.com/dotnet/roslyn/pull/67915)
- [Implement element access for inline array types (67830)](https://github.com/dotnet/roslyn/pull/67830)
| infrastructure | prs inserted in vs build main | 1 |
17,252 | 12,262,461,139 | IssuesEvent | 2020-05-06 22:09:55 | dotnet/extensions | https://api.github.com/repos/dotnet/extensions | closed | Make it easier for the community to find packages after the move | area-infrastructure super-triage task triage: 5.0-candidate triaged | A few suggestions that came up from the [discussion thread on the package move](https://github.com/dotnet/aspnetcore/issues/19806) for ensuring people can find which packages live where more quickly. This issue is tracking doing that work. Some of it should be automatic, but we should validate it:
1. Ensure the Source Repository metadata in the packages is correct so that NuGet.org links will work
1. Add a list of all `Microsoft.Extensions.*` packages that used to exist in this repo linking to where they now live. This isn't necessarily designed to be a constantly-updated list as new packages are added, but should try to cover the ones that used to be maintained in this repo. | 1.0 | Make it easier for the community to find packages after the move - A few suggestions that came up from the [discussion thread on the package move](https://github.com/dotnet/aspnetcore/issues/19806) for ensuring people can find which packages live where more quickly. This issue is tracking doing that work. Some of it should be automatic, but we should validate it:
1. Ensure the Source Repository metadata in the packages is correct so that NuGet.org links will work
1. Add a list of all `Microsoft.Extensions.*` packages that used to exist in this repo linking to where they now live. This isn't necessarily designed to be a constantly-updated list as new packages are added, but should try to cover the ones that used to be maintained in this repo. | infrastructure | make it easier for the community to find packages after the move a few suggestions that came up from the for ensuring people can find which packages live where more quickly this issue is tracking doing that work some of it should be automatic but we should validate it ensure the source repository metadata in the packages is correct so that nuget org links will work add a list of all microsoft extensions packages that used to exist in this repo linking to where they now live this isn t necessarily designed to be a constantly updated list as new packages are added but should try to cover the ones that used to be maintained in this repo | 1 |
815,079 | 30,535,220,236 | IssuesEvent | 2023-07-19 16:50:21 | calcom/cal.com | https://api.github.com/repos/calcom/cal.com | closed | [CAL-1157] Embed Issues - Reported on Slack | 🐛 bug Medium priority 3 points embed | Hey everyone, having some issues with the [http://cal.com|cal.com](http://cal.com%7Ccal.com) embed and was directed by support to join the Slack.
Verify the issues and fix them.
I was embedding my calendar on the coming soon page for my web agency and I found three bugs with the inline embed. All 3 of them are observable in the CodeSandbox demos (and I can also throw up a link if it's helpful to see my implementation).
1. \~The first bug is that when it displays the screen for a successfully scheduled meeting, it's bigger than its container. So what happens is the bottom gets cut off and it creates an internal scrollbar to see the cut-off portion. I fixed this by implementing my own quick and simple booking success screen (which doesn't necessarily size properly at this point in time, would need to use the \__dimensionChanged action).\~
2. The timezone/time options selector on desktop gets cut off at the bottom. I fixed this by giving the container wrapping the embed extra height to account for it and then overriding the styling of the iframe to fill the height of the container.
3. The loading indicator is (very noticeably on mobile) off-centred because it's positioned at left: 50% which doesn't take into account the width of the indicator itself which is 30px. It should be left: calc (50% - 15px). Its vertical positioning has the same issue but is less noticeable\~
4. Also, not a bug but a UX problem present in the regular booking pages as well (not specific to the embed) is that on mobile the date selection should move to a new screen instead of keeping the rest visible, which is how Calendly handles it. I've actually even had a couple of my friends comment on it who I've had test some of my booking stuff. This is kinda important regardless of whether I use the embed because I imagine I'm not the only one to find this clunky, and it affects everyone.
Also, just a quick question, is there any way for me to easily just build out my own [http://cal.com|cal.com](http://cal.com%7Ccal.com) widget?
[Slack Messag](https://calendso.slack.com/archives/C01NXDSRY9W/p1677108785925729?thread_ts=1677108785.925729&cid=C01NXDSRY9W)
<sub>From [SyncLinear.com](https://synclinear.com) | [CAL-1157](https://linear.app/calcom/issue/CAL-1157/embed-issues-reported-on-slack)</sub> | 1.0 | [CAL-1157] Embed Issues - Reported on Slack - Hey everyone, having some issues with the [http://cal.com|cal.com](http://cal.com%7Ccal.com) embed and was directed by support to join the Slack.
Verify the issues and fix them.
I was embedding my calendar on the coming soon page for my web agency and I found three bugs with the inline embed. All 3 of them are observable in the CodeSandbox demos (and I can also throw up a link if it's helpful to see my implementation).
1. \~The first bug is that when it displays the screen for a successfully scheduled meeting, it's bigger than its container. So what happens is the bottom gets cut off and it creates an internal scrollbar to see the cut-off portion. I fixed this by implementing my own quick and simple booking success screen (which doesn't necessarily size properly at this point in time, would need to use the \__dimensionChanged action).\~
2. The timezone/time options selector on desktop gets cut off at the bottom. I fixed this by giving the container wrapping the embed extra height to account for it and then overriding the styling of the iframe to fill the height of the container.
3. The loading indicator is (very noticeably on mobile) off-centred because it's positioned at left: 50% which doesn't take into account the width of the indicator itself which is 30px. It should be left: calc (50% - 15px). Its vertical positioning has the same issue but is less noticeable\~
4. Also, not a bug but a UX problem present in the regular booking pages as well (not specific to the embed) is that on mobile the date selection should move to a new screen instead of keeping the rest visible, which is how Calendly handles it. I've actually even had a couple of my friends comment on it who I've had test some of my booking stuff. This is kinda important regardless of whether I use the embed because I imagine I'm not the only one to find this clunky, and it affects everyone.
Also, just a quick question, is there any way for me to easily just build out my own [http://cal.com|cal.com](http://cal.com%7Ccal.com) widget?
[Slack Messag](https://calendso.slack.com/archives/C01NXDSRY9W/p1677108785925729?thread_ts=1677108785.925729&cid=C01NXDSRY9W)
<sub>From [SyncLinear.com](https://synclinear.com) | [CAL-1157](https://linear.app/calcom/issue/CAL-1157/embed-issues-reported-on-slack)</sub> | non_infrastructure | embed issues reported on slack hey everyone having some issues with the embed and was directed by support to join the slack verify the issues and fix them i was embedding my calendar on the coming soon page for my web agency and i found three bugs with the inline embed all of them are observable in the codesandbox demos and i can also throw up a link if it s helpful to see my implementation the first bug is that when it displays the screen for a successfully scheduled meeting it s bigger than its container so what happens is the bottom gets cut off and it creates an internal scrollbar to see the cut off portion i fixed this by implementing my own quick and simple booking success screen which doesn t necessarily size properly at this point in time would need to use the dimensionchanged action the timezone time options selector on desktop gets cut off at the bottom i fixed this by giving the container wrapping the embed extra height to account for it and then overriding the styling of the iframe to fill the height of the container the loading indicator is very noticeably on mobile off centred because it s positioned at left which doesn t take into account the width of the indicator itself which is it should be left calc its vertical positioning has the same issue but is less noticeable also not a bug but a ux problem present in the regular booking pages as well not specific to the embed is that on mobile the date selection should move to a new screen instead of keeping the rest visible which is how calendly handles it i ve actually even had a couple of my friends comment on it who i ve had test some of my booking stuff this is kinda important regardless of whether i use the embed because i imagine i m not the only one to find this clunky and it affects everyone also just a quick question is there any way for me to easily just build out my own widget from | 0 |
281,630 | 8,697,715,094 | IssuesEvent | 2018-12-04 21:05:57 | googleapis/google-http-java-client | https://api.github.com/repos/googleapis/google-http-java-client | closed | Tailing equals is striped out in query string and params values | :rotating_light: priority: p2 type: bug | I'm hitting an ASP.Net server with a POST method and receiving a HTTP 302 response. The Location header is like the following:
http://server/page.aspx?id=IjLo+6Fft+IzHGYC4FzjQw==
The thing is that the library is stripping out the final = character, sending an incorrect request when handling the redirect to:
http://server/page.aspx?id=IjLo+6Fft+IzHGYC4FzjQw
As a workaround I have to handle the redirect manually.
The same issue is present if I set a POST form param value with a tailing = like:
param1=someValue=¶m2=10
The library sends an incorrect request like:
param1=someValue¶m2=10
This works well on any navigator I've tested it, it sounds like a bug to me. At least it should encode the parameter instead of stripping it out.
| 1.0 | Tailing equals is striped out in query string and params values - I'm hitting an ASP.Net server with a POST method and receiving a HTTP 302 response. The Location header is like the following:
http://server/page.aspx?id=IjLo+6Fft+IzHGYC4FzjQw==
The thing is that the library is stripping out the final = character, sending an incorrect request when handling the redirect to:
http://server/page.aspx?id=IjLo+6Fft+IzHGYC4FzjQw
As a workaround I have to handle the redirect manually.
The same issue is present if I set a POST form param value with a tailing = like:
param1=someValue=¶m2=10
The library sends an incorrect request like:
param1=someValue¶m2=10
This works well on any navigator I've tested it, it sounds like a bug to me. At least it should encode the parameter instead of stripping it out.
| non_infrastructure | tailing equals is striped out in query string and params values i m hitting an asp net server with a post method and receiving a http response the location header is like the following the thing is that the library is stripping out the final character sending an incorrect request when handling the redirect to as a workaround i have to handle the redirect manually the same issue is present if i set a post form param value with a tailing like somevalue the library sends an incorrect request like somevalue this works well on any navigator i ve tested it it sounds like a bug to me at least it should encode the parameter instead of stripping it out | 0 |
20,171 | 13,735,726,167 | IssuesEvent | 2020-10-05 10:36:17 | eventespresso/event-espresso-core | https://api.github.com/repos/eventespresso/event-espresso-core | closed | Add search option to GQL schema. | EDTR v2 category:models-and-data-infrastructure | In [barista/issues/287](https://github.com/eventespresso/barista/issues/287), we need to be able to search for entities in a searchable input. Our GQL Schema does not have the search feature yet.
Looking into our PHP Model system, it looks like our model system doesn't have anything out of the box either. | 1.0 | Add search option to GQL schema. - In [barista/issues/287](https://github.com/eventespresso/barista/issues/287), we need to be able to search for entities in a searchable input. Our GQL Schema does not have the search feature yet.
Looking into our PHP Model system, it looks like our model system doesn't have anything out of the box either. | infrastructure | add search option to gql schema in we need to be able to search for entities in a searchable input our gql schema does not have the search feature yet looking into our php model system it looks like our model system doesn t have anything out of the box either | 1 |
46,333 | 19,095,668,211 | IssuesEvent | 2021-11-29 16:25:30 | cityofaustin/atd-data-tech | https://api.github.com/repos/cityofaustin/atd-data-tech | closed | AGOL Admin for ROW Accounts | Workgroup: ROW Type: IT Support Service: Geo | Asked Paloma to send me a list of ROW members so I can make sure that their AGOL accounts are configured. | 1.0 | AGOL Admin for ROW Accounts - Asked Paloma to send me a list of ROW members so I can make sure that their AGOL accounts are configured. | non_infrastructure | agol admin for row accounts asked paloma to send me a list of row members so i can make sure that their agol accounts are configured | 0 |
11,533 | 9,231,274,481 | IssuesEvent | 2019-03-13 01:37:03 | indentlabs/notebook | https://api.github.com/repos/indentlabs/notebook | closed | Zero downtime deployment | Infrastructure Needs Input | Right now we have potentially a few seconds of downtime whenever we deploy to production, and potentially longer pending any database migrations.
Since so much content can be submitted in a single form (e.g. filling out an entire character's profile), we should figure out how to either mitigate this issue (e.g. preserving the user's form content and asking them to submit again) or figure how to do zero downtime deployment (preferably without a complicated, expensive architecture).
| 1.0 | Zero downtime deployment - Right now we have potentially a few seconds of downtime whenever we deploy to production, and potentially longer pending any database migrations.
Since so much content can be submitted in a single form (e.g. filling out an entire character's profile), we should figure out how to either mitigate this issue (e.g. preserving the user's form content and asking them to submit again) or figure how to do zero downtime deployment (preferably without a complicated, expensive architecture).
| infrastructure | zero downtime deployment right now we have potentially a few seconds of downtime whenever we deploy to production and potentially longer pending any database migrations since so much content can be submitted in a single form e g filling out an entire character s profile we should figure out how to either mitigate this issue e g preserving the user s form content and asking them to submit again or figure how to do zero downtime deployment preferably without a complicated expensive architecture | 1 |
13,436 | 10,257,530,327 | IssuesEvent | 2019-08-21 20:21:34 | astropy/astropy-tutorials | https://api.github.com/repos/astropy/astropy-tutorials | opened | Remove SSL hack when STScI updates their TLS certificate | infrastructure package-expert | See the hackery in .circleci/config.yml and .circleci/openssl_hack.cnf | 1.0 | Remove SSL hack when STScI updates their TLS certificate - See the hackery in .circleci/config.yml and .circleci/openssl_hack.cnf | infrastructure | remove ssl hack when stsci updates their tls certificate see the hackery in circleci config yml and circleci openssl hack cnf | 1 |
5,592 | 5,806,124,897 | IssuesEvent | 2017-05-04 01:03:42 | dotnet/core-setup | https://api.github.com/repos/dotnet/core-setup | closed | Tests should restore a specific version of Microsoft.NETCore.DotNetAppHost, and not the highest version available on MyGet | area-Infrastructure | ## Steps to reproduce
Restore `Microsoft.NETCore.DotNetAppHost` package, which is needed for tests located at `/opt/code/TestAssets/TestProjects`
This can be by running `build.sh` or `build.cmd`.
## Expected behavior
Version matching should not be `*`. Rather should match a specific version. For example, `2.0.0-preview1-002042-00`
## Actual behavior
Restores the highest version matching `2.0.0-preview1-*`
Refer to https://github.com/dotnet/core-setup/blob/master/TestAssets/TestProjects/LightupClient/project.json
## Environment data | 1.0 | Tests should restore a specific version of Microsoft.NETCore.DotNetAppHost, and not the highest version available on MyGet - ## Steps to reproduce
Restore `Microsoft.NETCore.DotNetAppHost` package, which is needed for tests located at `/opt/code/TestAssets/TestProjects`
This can be by running `build.sh` or `build.cmd`.
## Expected behavior
Version matching should not be `*`. Rather should match a specific version. For example, `2.0.0-preview1-002042-00`
## Actual behavior
Restores the highest version matching `2.0.0-preview1-*`
Refer to https://github.com/dotnet/core-setup/blob/master/TestAssets/TestProjects/LightupClient/project.json
## Environment data | infrastructure | tests should restore a specific version of microsoft netcore dotnetapphost and not the highest version available on myget steps to reproduce restore microsoft netcore dotnetapphost package which is needed for tests located at opt code testassets testprojects this can be by running build sh or build cmd expected behavior version matching should not be rather should match a specific version for example actual behavior restores the highest version matching refer to environment data | 1 |
127,250 | 18,010,359,474 | IssuesEvent | 2021-09-16 07:53:28 | maddyCode23/linux-4.1.15 | https://api.github.com/repos/maddyCode23/linux-4.1.15 | opened | CVE-2018-13093 (Medium) detected in linux-stable-rtv4.1.33 | security vulnerability | ## CVE-2018-13093 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/maddyCode23/linux-4.1.15/commit/f1f3d2b150be669390b32dfea28e773471bdd6e7">f1f3d2b150be669390b32dfea28e773471bdd6e7</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/xfs/xfs_icache.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/xfs/xfs_icache.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in fs/xfs/xfs_icache.c in the Linux kernel through 4.17.3. There is a NULL pointer dereference and panic in lookup_slow() on a NULL inode->i_ops pointer when doing pathwalks on a corrupted xfs image. This occurs because of a lack of proper validation that cached inodes are free during allocation.
<p>Publish Date: 2018-07-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-13093>CVE-2018-13093</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="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-13093">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-13093</a></p>
<p>Release Date: 2018-07-03</p>
<p>Fix Resolution: v4.18-rc1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-13093 (Medium) detected in linux-stable-rtv4.1.33 - ## CVE-2018-13093 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/maddyCode23/linux-4.1.15/commit/f1f3d2b150be669390b32dfea28e773471bdd6e7">f1f3d2b150be669390b32dfea28e773471bdd6e7</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/xfs/xfs_icache.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/xfs/xfs_icache.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in fs/xfs/xfs_icache.c in the Linux kernel through 4.17.3. There is a NULL pointer dereference and panic in lookup_slow() on a NULL inode->i_ops pointer when doing pathwalks on a corrupted xfs image. This occurs because of a lack of proper validation that cached inodes are free during allocation.
<p>Publish Date: 2018-07-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-13093>CVE-2018-13093</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="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-13093">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-13093</a></p>
<p>Release Date: 2018-07-03</p>
<p>Fix Resolution: v4.18-rc1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_infrastructure | cve medium detected in linux stable cve medium severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href vulnerable source files fs xfs xfs icache c fs xfs xfs icache c vulnerability details an issue was discovered in fs xfs xfs icache c in the linux kernel through there is a null pointer dereference and panic in lookup slow on a null inode i ops pointer when doing pathwalks on a corrupted xfs image this occurs because of a lack of proper validation that cached inodes are free during allocation 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 step up your open source security game with whitesource | 0 |
791,769 | 27,876,171,435 | IssuesEvent | 2023-03-21 16:09:13 | Warcraft-GoA-Development-Team/Warcraft-Guardians-of-Azeroth-2 | https://api.github.com/repos/Warcraft-GoA-Development-Team/Warcraft-Guardians-of-Azeroth-2 | opened | Negative County Opinion from Fervor bugged | priority low :grey_exclamation: bug :bug: | <!--
**DO NOT REMOVE PRE-EXISTING LINES**
------------------------------------------------------------------------------------------------------------
-->
**Your mod version is:**
0.1
**What expansions do you have installed?**
none
**Are you using any submods/mods? If so, which?**
none
**Please explain your issue in as much detail as possible:**
The popular opinion penalty from fervor, which is supposed to max out at -75, can go much higher. (Here it is at -129). This leads to situations where even killing a peasant revolt will immediately allow them to start another one, since the "locals pacified" modifier only gives +50 opinion
**Steps to reproduce the issue:**
conquer a faith considered evil
**Upload an attachment below: .zip of your save, or screenshots:**
 | 1.0 | Negative County Opinion from Fervor bugged - <!--
**DO NOT REMOVE PRE-EXISTING LINES**
------------------------------------------------------------------------------------------------------------
-->
**Your mod version is:**
0.1
**What expansions do you have installed?**
none
**Are you using any submods/mods? If so, which?**
none
**Please explain your issue in as much detail as possible:**
The popular opinion penalty from fervor, which is supposed to max out at -75, can go much higher. (Here it is at -129). This leads to situations where even killing a peasant revolt will immediately allow them to start another one, since the "locals pacified" modifier only gives +50 opinion
**Steps to reproduce the issue:**
conquer a faith considered evil
**Upload an attachment below: .zip of your save, or screenshots:**
 | non_infrastructure | negative county opinion from fervor bugged do not remove pre existing lines your mod version is what expansions do you have installed none are you using any submods mods if so which none please explain your issue in as much detail as possible the popular opinion penalty from fervor which is supposed to max out at can go much higher here it is at this leads to situations where even killing a peasant revolt will immediately allow them to start another one since the locals pacified modifier only gives opinion steps to reproduce the issue conquer a faith considered evil upload an attachment below zip of your save or screenshots | 0 |
29,979 | 24,447,507,841 | IssuesEvent | 2022-10-06 19:21:01 | google/site-kit-wp | https://api.github.com/repos/google/site-kit-wp | closed | Fix E2E unexpected "You are probably offline" errors | P1 Type: Infrastructure | ## Bug Description
There are a few instances of a common error resulting in E2E instability from an unexpected console error "You are probably offline". This happens when an API request is cancelled unexpectedly (usually due to a navigation) while it is in progress. This unexpected console error causes the test to fail.
## Examples
```
FAIL specs/dashboard/search.test.js (10.806s)
● Site Kit dashboard post search › displays results when searching with a post title, and loads the details page when clicking View Data
expect(jest.fn()).not.toHaveErrored(expected)
Expected mock function not to be called but it was called with:
["Google Site Kit API Error method:GET datapoint:entity-search type:core identifier:search error:\"You are probably offline.\""]
```
```
FAIL specs/modules/tagmanager/setup.test.js (44.838s)
● Tag Manager module setup › Setup with AMP active › with Secondary AMP › when validating › validates homepage AMP for logged-in users
expect(jest.fn()).not.toHaveErrored(expected)
Expected mock function not to be called but it was called with:
["Google Site Kit API Error method:POST datapoint:survey-trigger type:core identifier:user error:\"You are probably offline.\""]
```
---------------
_Do not alter or remove anything below. The following sections will be managed by moderators only._
## Acceptance criteria
* E2E tests should not fail due to "You are probably offline" console errors
## Implementation Brief
* These errors originate from `@wordpress/api-fetch` when a fetch request throws an error. This only happens when the request truly fails (like when you're offline) or is cancelled (e.g. by a navigation) – never from a particular response's status code. As such, the simplest solution here is to add this string `You are probably offline.` to the logic we have for ignoring specific `console` messages in `bootstrap.js`.
* If we don't want to ignore it entirely, we could simply override the console method to be `debug` which aren't monitored by `jest-console` and would be visible in the log without failing the test.
### Test Coverage
* No change in coverage
## QA Brief
* E2E tests should pass—no further QA needed.
## Changelog entry
* N/A
| 1.0 | Fix E2E unexpected "You are probably offline" errors - ## Bug Description
There are a few instances of a common error resulting in E2E instability from an unexpected console error "You are probably offline". This happens when an API request is cancelled unexpectedly (usually due to a navigation) while it is in progress. This unexpected console error causes the test to fail.
## Examples
```
FAIL specs/dashboard/search.test.js (10.806s)
● Site Kit dashboard post search › displays results when searching with a post title, and loads the details page when clicking View Data
expect(jest.fn()).not.toHaveErrored(expected)
Expected mock function not to be called but it was called with:
["Google Site Kit API Error method:GET datapoint:entity-search type:core identifier:search error:\"You are probably offline.\""]
```
```
FAIL specs/modules/tagmanager/setup.test.js (44.838s)
● Tag Manager module setup › Setup with AMP active › with Secondary AMP › when validating › validates homepage AMP for logged-in users
expect(jest.fn()).not.toHaveErrored(expected)
Expected mock function not to be called but it was called with:
["Google Site Kit API Error method:POST datapoint:survey-trigger type:core identifier:user error:\"You are probably offline.\""]
```
---------------
_Do not alter or remove anything below. The following sections will be managed by moderators only._
## Acceptance criteria
* E2E tests should not fail due to "You are probably offline" console errors
## Implementation Brief
* These errors originate from `@wordpress/api-fetch` when a fetch request throws an error. This only happens when the request truly fails (like when you're offline) or is cancelled (e.g. by a navigation) – never from a particular response's status code. As such, the simplest solution here is to add this string `You are probably offline.` to the logic we have for ignoring specific `console` messages in `bootstrap.js`.
* If we don't want to ignore it entirely, we could simply override the console method to be `debug` which aren't monitored by `jest-console` and would be visible in the log without failing the test.
### Test Coverage
* No change in coverage
## QA Brief
* E2E tests should pass—no further QA needed.
## Changelog entry
* N/A
| infrastructure | fix unexpected you are probably offline errors bug description there are a few instances of a common error resulting in instability from an unexpected console error you are probably offline this happens when an api request is cancelled unexpectedly usually due to a navigation while it is in progress this unexpected console error causes the test to fail examples fail specs dashboard search test js ● site kit dashboard post search › displays results when searching with a post title and loads the details page when clicking view data expect jest fn not tohaveerrored expected expected mock function not to be called but it was called with fail specs modules tagmanager setup test js ● tag manager module setup › setup with amp active › with secondary amp › when validating › validates homepage amp for logged in users expect jest fn not tohaveerrored expected expected mock function not to be called but it was called with do not alter or remove anything below the following sections will be managed by moderators only acceptance criteria tests should not fail due to you are probably offline console errors implementation brief these errors originate from wordpress api fetch when a fetch request throws an error this only happens when the request truly fails like when you re offline or is cancelled e g by a navigation – never from a particular response s status code as such the simplest solution here is to add this string you are probably offline to the logic we have for ignoring specific console messages in bootstrap js if we don t want to ignore it entirely we could simply override the console method to be debug which aren t monitored by jest console and would be visible in the log without failing the test test coverage no change in coverage qa brief tests should pass—no further qa needed changelog entry n a | 1 |
16,030 | 11,802,571,546 | IssuesEvent | 2020-03-18 21:51:18 | magento/magento2-phpstorm-plugin | https://api.github.com/repos/magento/magento2-phpstorm-plugin | closed | Infrastructure. Configure Gradle for the project | infrastructure | Add Gradle https://gradle.org/ - automated build tool to the project.
It going to be used for decreasing the effort needed for rolling up the project on a local machine, launching it, debugging and deployment.
Update CONTRIBUTING.md with the instruction. | 1.0 | Infrastructure. Configure Gradle for the project - Add Gradle https://gradle.org/ - automated build tool to the project.
It going to be used for decreasing the effort needed for rolling up the project on a local machine, launching it, debugging and deployment.
Update CONTRIBUTING.md with the instruction. | infrastructure | infrastructure configure gradle for the project add gradle automated build tool to the project it going to be used for decreasing the effort needed for rolling up the project on a local machine launching it debugging and deployment update contributing md with the instruction | 1 |
33,010 | 27,143,879,580 | IssuesEvent | 2023-02-16 18:19:40 | cds-snc/url-shortener | https://api.github.com/repos/cds-snc/url-shortener | closed | Terraform: create checkov static analysis workflow | Security | Sécurité Infrastructure | ## Description
Create a GitHub workflow that runs for all PRs and merges to `main` that scans the Terraform code for potential issues using `checkov`.
You will likely have to adjust the [.checkov.yml](https://github.com/cds-snc/url-shortener/blob/main/terragrunt/.checkov.yml `skip-checks` block) to remove the failures we don't care about. Happy to help with this if you're not sure about any of them.
An example of this can be seen in the Scan Files workflow:
https://github.com/cds-snc/scan-files/blob/main/.github/workflows/terraform-security-scan.yml | 1.0 | Terraform: create checkov static analysis workflow - ## Description
Create a GitHub workflow that runs for all PRs and merges to `main` that scans the Terraform code for potential issues using `checkov`.
You will likely have to adjust the [.checkov.yml](https://github.com/cds-snc/url-shortener/blob/main/terragrunt/.checkov.yml `skip-checks` block) to remove the failures we don't care about. Happy to help with this if you're not sure about any of them.
An example of this can be seen in the Scan Files workflow:
https://github.com/cds-snc/scan-files/blob/main/.github/workflows/terraform-security-scan.yml | infrastructure | terraform create checkov static analysis workflow description create a github workflow that runs for all prs and merges to main that scans the terraform code for potential issues using checkov you will likely have to adjust the skip checks block to remove the failures we don t care about happy to help with this if you re not sure about any of them an example of this can be seen in the scan files workflow | 1 |
24,498 | 17,354,520,822 | IssuesEvent | 2021-07-29 12:58:22 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | [Android][libraries] Test suites failing with A JSON parsing exception | area-Infrastructure-mono os-android | The following test suites are failing on Android arm64 on CI
System.IO.Pipes.Tests
System.Numerics.Vectors.Tests
System.Reflection.Emit.Tests
System.Xml.Misc.Tests
System.Xml.XmlNodeReader.Tests
System.Xml.XmlSerializer.Tests
System.Security.Claims.Tests
System.Security.Cryptography.Primitives.Tests
System.Text.RegularExpressions.Tests
```
A JSON parsing exception occurred in [C:\h\w\AA5F0978\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.21268.1\tools\net6.0\any\Microsoft.DotNet.XHarness.CLI.runtimeconfig.json], offset 0 (line 1, column 1): The document is empty.
Invalid runtimeconfig.json [C:\h\w\AA5F0978\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.21268.1\tools\net6.0\any\Microsoft.DotNet.XHarness.CLI.runtimeconfig.json] [C:\h\w\AA5F0978\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.21268.1\tools\net6.0\any\Microsoft.DotNet.XHarness.CLI.runtimeconfig.dev.json] | 1.0 | [Android][libraries] Test suites failing with A JSON parsing exception - The following test suites are failing on Android arm64 on CI
System.IO.Pipes.Tests
System.Numerics.Vectors.Tests
System.Reflection.Emit.Tests
System.Xml.Misc.Tests
System.Xml.XmlNodeReader.Tests
System.Xml.XmlSerializer.Tests
System.Security.Claims.Tests
System.Security.Cryptography.Primitives.Tests
System.Text.RegularExpressions.Tests
```
A JSON parsing exception occurred in [C:\h\w\AA5F0978\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.21268.1\tools\net6.0\any\Microsoft.DotNet.XHarness.CLI.runtimeconfig.json], offset 0 (line 1, column 1): The document is empty.
Invalid runtimeconfig.json [C:\h\w\AA5F0978\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.21268.1\tools\net6.0\any\Microsoft.DotNet.XHarness.CLI.runtimeconfig.json] [C:\h\w\AA5F0978\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.21268.1\tools\net6.0\any\Microsoft.DotNet.XHarness.CLI.runtimeconfig.dev.json] | infrastructure | test suites failing with a json parsing exception the following test suites are failing on android on ci system io pipes tests system numerics vectors tests system reflection emit tests system xml misc tests system xml xmlnodereader tests system xml xmlserializer tests system security claims tests system security cryptography primitives tests system text regularexpressions tests a json parsing exception occurred in offset line column the document is empty invalid runtimeconfig json | 1 |
17,103 | 12,223,506,647 | IssuesEvent | 2020-05-02 17:55:06 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | build.cmd -vs System.Private.CoreLib fails to find the sln file | area-Infrastructure untriaged | The `System.Private.CoreLib` project files are located inside `src\libraries\System.Private.CoreLib` just like the code of all the other Libraries projects, but the *.sln file is located in:
`src\coreclr\src\System.Private.CoreLib\System.Private.CoreLib.sln`
Please consider adding a special case to handle this solution whe executing this command, which currently fails to find the *.sln file:
```
D:\runtime> .\build.cmd -vs System.Private.CoreLib
D:\runtime\eng\build.ps1 : The term 'D:\runtime\eng\..\src\libraries\System.Private.CoreLib\System.Private.CoreLib.sln' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included,
verify that the path is correct and try again.
At line:1 char:1
+ & 'D:\runtime\eng\build.ps1' -vs System.Private.CoreLib
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (D:\runtime\eng\...ate.CoreLib.sln:String) [build.ps1], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException,build.ps1
```
Low priority, since there is a workaround, but it would be nice not to have such a long command:
```
D:\runtime> .\build.cmd -vs src\coreclr\src\System.Private.CoreLib\System.Private.CoreLib.sln
``` | 1.0 | build.cmd -vs System.Private.CoreLib fails to find the sln file - The `System.Private.CoreLib` project files are located inside `src\libraries\System.Private.CoreLib` just like the code of all the other Libraries projects, but the *.sln file is located in:
`src\coreclr\src\System.Private.CoreLib\System.Private.CoreLib.sln`
Please consider adding a special case to handle this solution whe executing this command, which currently fails to find the *.sln file:
```
D:\runtime> .\build.cmd -vs System.Private.CoreLib
D:\runtime\eng\build.ps1 : The term 'D:\runtime\eng\..\src\libraries\System.Private.CoreLib\System.Private.CoreLib.sln' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included,
verify that the path is correct and try again.
At line:1 char:1
+ & 'D:\runtime\eng\build.ps1' -vs System.Private.CoreLib
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (D:\runtime\eng\...ate.CoreLib.sln:String) [build.ps1], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException,build.ps1
```
Low priority, since there is a workaround, but it would be nice not to have such a long command:
```
D:\runtime> .\build.cmd -vs src\coreclr\src\System.Private.CoreLib\System.Private.CoreLib.sln
``` | infrastructure | build cmd vs system private corelib fails to find the sln file the system private corelib project files are located inside src libraries system private corelib just like the code of all the other libraries projects but the sln file is located in src coreclr src system private corelib system private corelib sln please consider adding a special case to handle this solution whe executing this command which currently fails to find the sln file d runtime build cmd vs system private corelib d runtime eng build the term d runtime eng src libraries system private corelib system private corelib sln is not recognized as the name of a cmdlet function script file or operable program check the spelling of the name or if a path was included verify that the path is correct and try again at line char d runtime eng build vs system private corelib categoryinfo objectnotfound d runtime eng ate corelib sln string commandnotfoundexception fullyqualifiederrorid commandnotfoundexception build low priority since there is a workaround but it would be nice not to have such a long command d runtime build cmd vs src coreclr src system private corelib system private corelib sln | 1 |
13,215 | 10,151,550,076 | IssuesEvent | 2019-08-05 20:38:08 | dotnet/coreclr | https://api.github.com/repos/dotnet/coreclr | opened | [OSX] Failure to initialize build tools. | area-Infrastructure | build-test.sh still unfortunately uses build tools. On OSX strangely we are intermitedenly seeing:
```
Using RID osx-x64 for BuildTools native tools
Initializing BuildTools...
ERROR: An error occurred when trying to initialize the tools.
Please check the detailed log that follows.
Running: /Users/vsts/agent/2.155.1/work/1/s/init-tools.sh
Running: /Users/vsts/agent/2.155.1/work/1/s/.dotnet/dotnet restore "/Users/vsts/agent/2.155.1/work/1/s/init-tools.msbuild" --no-cache --packages /Users/vsts/agent/2.155.1/work/1/s/.packages --source https://dotnet.myget.org/F/dotnet-buildtools/api/v3/index.json /p:BuildToolsPackageVersion=3.0.0-preview4-04022-01 /p:ToolsDir=/Users/vsts/agent/2.155.1/work/1/s/Tools
```
See: https://dev.azure.com/dnceng/public/_build/results?buildId=295344 | 1.0 | [OSX] Failure to initialize build tools. - build-test.sh still unfortunately uses build tools. On OSX strangely we are intermitedenly seeing:
```
Using RID osx-x64 for BuildTools native tools
Initializing BuildTools...
ERROR: An error occurred when trying to initialize the tools.
Please check the detailed log that follows.
Running: /Users/vsts/agent/2.155.1/work/1/s/init-tools.sh
Running: /Users/vsts/agent/2.155.1/work/1/s/.dotnet/dotnet restore "/Users/vsts/agent/2.155.1/work/1/s/init-tools.msbuild" --no-cache --packages /Users/vsts/agent/2.155.1/work/1/s/.packages --source https://dotnet.myget.org/F/dotnet-buildtools/api/v3/index.json /p:BuildToolsPackageVersion=3.0.0-preview4-04022-01 /p:ToolsDir=/Users/vsts/agent/2.155.1/work/1/s/Tools
```
See: https://dev.azure.com/dnceng/public/_build/results?buildId=295344 | infrastructure | failure to initialize build tools build test sh still unfortunately uses build tools on osx strangely we are intermitedenly seeing using rid osx for buildtools native tools initializing buildtools error an error occurred when trying to initialize the tools please check the detailed log that follows running users vsts agent work s init tools sh running users vsts agent work s dotnet dotnet restore users vsts agent work s init tools msbuild no cache packages users vsts agent work s packages source p buildtoolspackageversion p toolsdir users vsts agent work s tools see | 1 |
266,761 | 28,435,099,931 | IssuesEvent | 2023-04-15 07:50:41 | emqx/nanomq | https://api.github.com/repos/emqx/nanomq | closed | potential memleak | security | **Describe the bug**
您好，我们在NanoMQ当前版本中还发现了一项内存泄露，以下为详细漏洞信息以供开发人员参考。
School of Cyber Science and Technology, Shandong University
**Expected behavior**
如果在编译时启用 ASAN，NanoMQ 会崩溃并显示 ASAN 信息。
**To Reproduce**
1. start nanomq with ./nanomq start
2. Send the packet：nc 127.0.0.1 1883 < ./leak.raw
3. NanoMQ crashes
[leak1.zip](https://github.com/emqx/nanomq/files/11234045/leak1.zip)
** Environment Details **
- NanoMQ version：master branch version commit #8c54cd7
- Operating system and version：Ubuntu 20.04
- Compiler and language used：gcc 9.4.0 clang 10.0.0
- testing scenario
| True | potential memleak - **Describe the bug**
您好，我们在NanoMQ当前版本中还发现了一项内存泄露，以下为详细漏洞信息以供开发人员参考。
School of Cyber Science and Technology, Shandong University
**Expected behavior**
如果在编译时启用 ASAN，NanoMQ 会崩溃并显示 ASAN 信息。
**To Reproduce**
1. start nanomq with ./nanomq start
2. Send the packet：nc 127.0.0.1 1883 < ./leak.raw
3. NanoMQ crashes
[leak1.zip](https://github.com/emqx/nanomq/files/11234045/leak1.zip)
** Environment Details **
- NanoMQ version：master branch version commit #8c54cd7
- Operating system and version：Ubuntu 20.04
- Compiler and language used：gcc 9.4.0 clang 10.0.0
- testing scenario
| non_infrastructure | potential memleak describe the bug 您好，我们在nanomq当前版本中还发现了一项内存泄露，以下为详细漏洞信息以供开发人员参考。 school of cyber science and technology shandong university expected behavior 如果在编译时启用 asan，nanomq 会崩溃并显示 asan 信息。 to reproduce start nanomq with nanomq start send the packet：nc leak raw nanomq crashes environment details nanomq version：master branch version commit operating system and version：ubuntu compiler and language used：gcc clang testing scenario | 0 |
743,697 | 25,910,948,914 | IssuesEvent | 2022-12-15 13:57:05 | yugabyte/yugabyte-db | https://api.github.com/repos/yugabyte/yugabyte-db | closed | [CDCSDK] Dataloss when streaming transaction intents for large tables | priority/high area/cdcsdk | Jira Link: [DB-4255](https://yugabyte.atlassian.net/browse/DB-4255)
The data corresponding to a transaction is picked and streamed from IntentDB, through the method: GetIntentsBatch.
In cases where the number of columns of a table was greater than 'FLAGS_cdc_max_stream_intent_records', it is possible that even if we get 'cdc_max_stream_intent_records' keyValue intent pairs we do not pick the pair corresponding to the key column, in which case we were having a data loss.
After this change, we will look for at-least max(number of columns in table, FLAGS_cdc_max_stream_intent_records) key value pairs.
Another issue was in cases of transactions begun before a tablet split but applied after a tablet split was successful , the intents will be streamed from the SST file of the parent tablet, in which case the keyValue intent pairs of the children tablet need not be contiguous. In such cases we will look for getting a total of max(number of columns in table, FLAGS_cdc_max_stream_intent_records) keyValue intent pairs , rather than just the next max(number of columns in table, FLAGS_cdc_max_stream_intent_records) contiguous keyValue pairs.
| 1.0 | [CDCSDK] Dataloss when streaming transaction intents for large tables - Jira Link: [DB-4255](https://yugabyte.atlassian.net/browse/DB-4255)
The data corresponding to a transaction is picked and streamed from IntentDB, through the method: GetIntentsBatch.
In cases where the number of columns of a table was greater than 'FLAGS_cdc_max_stream_intent_records', it is possible that even if we get 'cdc_max_stream_intent_records' keyValue intent pairs we do not pick the pair corresponding to the key column, in which case we were having a data loss.
After this change, we will look for at-least max(number of columns in table, FLAGS_cdc_max_stream_intent_records) key value pairs.
Another issue was in cases of transactions begun before a tablet split but applied after a tablet split was successful , the intents will be streamed from the SST file of the parent tablet, in which case the keyValue intent pairs of the children tablet need not be contiguous. In such cases we will look for getting a total of max(number of columns in table, FLAGS_cdc_max_stream_intent_records) keyValue intent pairs , rather than just the next max(number of columns in table, FLAGS_cdc_max_stream_intent_records) contiguous keyValue pairs.
| non_infrastructure | dataloss when streaming transaction intents for large tables jira link the data corresponding to a transaction is picked and streamed from intentdb through the method getintentsbatch in cases where the number of columns of a table was greater than flags cdc max stream intent records it is possible that even if we get cdc max stream intent records keyvalue intent pairs we do not pick the pair corresponding to the key column in which case we were having a data loss after this change we will look for at least max number of columns in table flags cdc max stream intent records key value pairs another issue was in cases of transactions begun before a tablet split but applied after a tablet split was successful the intents will be streamed from the sst file of the parent tablet in which case the keyvalue intent pairs of the children tablet need not be contiguous in such cases we will look for getting a total of max number of columns in table flags cdc max stream intent records keyvalue intent pairs rather than just the next max number of columns in table flags cdc max stream intent records contiguous keyvalue pairs | 0 |
14,374 | 10,773,331,601 | IssuesEvent | 2019-11-02 19:59:04 | fahimtran/upgraded-robot | https://api.github.com/repos/fahimtran/upgraded-robot | opened | Learn How to Use Spring/Java/Python for this Project | infrastructure | - [ ] Relearn Basics of Spring/Java/Python
- [ ] Apply RESTful Concepts to build a Microservice | 1.0 | Learn How to Use Spring/Java/Python for this Project - - [ ] Relearn Basics of Spring/Java/Python
- [ ] Apply RESTful Concepts to build a Microservice | infrastructure | learn how to use spring java python for this project relearn basics of spring java python apply restful concepts to build a microservice | 1 |
32,657 | 26,875,781,709 | IssuesEvent | 2023-02-05 01:47:30 | deathandmayhem/jolly-roger | https://api.github.com/repos/deathandmayhem/jolly-roger | closed | Serve a better 502 page from nginx in prod | infrastructure | When the jolly-roger Docker container is restarting in production, nginx serves a 502 page. We can make the experience for users better if we serve a custom 502 page with some "Jolly Roger is being updated" text and potentially an auto-refresher to detect and refresh when it's back online. | 1.0 | Serve a better 502 page from nginx in prod - When the jolly-roger Docker container is restarting in production, nginx serves a 502 page. We can make the experience for users better if we serve a custom 502 page with some "Jolly Roger is being updated" text and potentially an auto-refresher to detect and refresh when it's back online. | infrastructure | serve a better page from nginx in prod when the jolly roger docker container is restarting in production nginx serves a page we can make the experience for users better if we serve a custom page with some jolly roger is being updated text and potentially an auto refresher to detect and refresh when it s back online | 1 |
8,693 | 7,570,340,574 | IssuesEvent | 2018-04-23 08:42:19 | camunda/camunda-modeler | https://api.github.com/repos/camunda/camunda-modeler | opened | Spike: Produce signed modeler builds for Windows and MacOS | infrastructure ready release | __Task__
* [ ] Signed MacOS binaries
* [ ] Signed Windows binaries | 1.0 | Spike: Produce signed modeler builds for Windows and MacOS - __Task__
* [ ] Signed MacOS binaries
* [ ] Signed Windows binaries | infrastructure | spike produce signed modeler builds for windows and macos task signed macos binaries signed windows binaries | 1 |
7,273 | 6,883,107,943 | IssuesEvent | 2017-11-21 08:06:02 | qutebrowser/qutebrowser | https://api.github.com/repos/qutebrowser/qutebrowser | opened | Update to an up-to-date flake8 | component: infrastructure priority: 1 - middle | We're still using an old flake8 2.6.2 in qutebrowser because of [flake8-putty](https://pypi.python.org/pypi/flake8-putty) never being ported.
However, there's a flake8 3.x compatible [flake8-per-file-ignores](https://github.com/snoack/flake8-per-file-ignores) now, and with https://github.com/snoack/flake8-per-file-ignores/commit/d157db39aab7686d81dc9f8e1ad2e03576598463 it should be powerful enough for us to migrate.
There's probably a lot of new ignores to set though. | 1.0 | Update to an up-to-date flake8 - We're still using an old flake8 2.6.2 in qutebrowser because of [flake8-putty](https://pypi.python.org/pypi/flake8-putty) never being ported.
However, there's a flake8 3.x compatible [flake8-per-file-ignores](https://github.com/snoack/flake8-per-file-ignores) now, and with https://github.com/snoack/flake8-per-file-ignores/commit/d157db39aab7686d81dc9f8e1ad2e03576598463 it should be powerful enough for us to migrate.
There's probably a lot of new ignores to set though. | infrastructure | update to an up to date we re still using an old in qutebrowser because of never being ported however there s a x compatible now and with it should be powerful enough for us to migrate there s probably a lot of new ignores to set though | 1 |
2,161 | 3,535,715,082 | IssuesEvent | 2016-01-16 18:43:04 | MinetestForFun/server-minetestforfun-skyblock | https://api.github.com/repos/MinetestForFun/server-minetestforfun-skyblock | opened | Give time privilege to repo owners | Infrastructure Priority: High | We, workers on the repositories of Xorhub, need the `time` privilege for the skyblock server. We also need tokens to login on IRC. I think that if we are abled to push here, it's that we are trustworthy, and that we will not abuse of it, or annoy other players before using it.
It's a top priority because many players are annoyed by night, but not every player. So we need to have people to moderate time on the server. It also is annoying because of some players with a limited bandwitch (like @cessna151 ) are not abled to play too much and can't really build at night.
So those players need `time` privilege :
- @cessna151 ( cessna151 )
- @Cyberpangolin ( Cyberpangolin )
- @gravgun ( gravgun )
- @LeMagnesium ( Mg )
- @crabman77 ( crabman)
- @fabienwang ( fabienwang )
- @rredesigns ( R_R_E_Designs )
- @Ataron ( Ataron )
- @ObaniGemini ( Obani )
Maybe also :
- JAPP ?
- Uraza ?
- LizzardBeth ?
| 1.0 | Give time privilege to repo owners - We, workers on the repositories of Xorhub, need the `time` privilege for the skyblock server. We also need tokens to login on IRC. I think that if we are abled to push here, it's that we are trustworthy, and that we will not abuse of it, or annoy other players before using it.
It's a top priority because many players are annoyed by night, but not every player. So we need to have people to moderate time on the server. It also is annoying because of some players with a limited bandwitch (like @cessna151 ) are not abled to play too much and can't really build at night.
So those players need `time` privilege :
- @cessna151 ( cessna151 )
- @Cyberpangolin ( Cyberpangolin )
- @gravgun ( gravgun )
- @LeMagnesium ( Mg )
- @crabman77 ( crabman)
- @fabienwang ( fabienwang )
- @rredesigns ( R_R_E_Designs )
- @Ataron ( Ataron )
- @ObaniGemini ( Obani )
Maybe also :
- JAPP ?
- Uraza ?
- LizzardBeth ?
| infrastructure | give time privilege to repo owners we workers on the repositories of xorhub need the time privilege for the skyblock server we also need tokens to login on irc i think that if we are abled to push here it s that we are trustworthy and that we will not abuse of it or annoy other players before using it it s a top priority because many players are annoyed by night but not every player so we need to have people to moderate time on the server it also is annoying because of some players with a limited bandwitch like are not abled to play too much and can t really build at night so those players need time privilege cyberpangolin cyberpangolin gravgun gravgun lemagnesium mg crabman fabienwang fabienwang rredesigns r r e designs ataron ataron obanigemini obani maybe also japp uraza lizzardbeth | 1 |
40,371 | 12,792,301,543 | IssuesEvent | 2020-07-02 01:01:21 | yaeljacobs67/cncjs | https://api.github.com/repos/yaeljacobs67/cncjs | opened | CVE-2020-15084 (High) detected in express-jwt-5.3.1.tgz | security vulnerability | ## CVE-2020-15084 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>express-jwt-5.3.1.tgz</b></p></summary>
<p>JWT authentication middleware.</p>
<p>Library home page: <a href="https://registry.npmjs.org/express-jwt/-/express-jwt-5.3.1.tgz">https://registry.npmjs.org/express-jwt/-/express-jwt-5.3.1.tgz</a></p>
<p>Path to dependency file: /cncjs/package.json</p>
<p>Path to vulnerable library: /cncjs/src/node_modules/express-jwt/package.json</p>
<p>
Dependency Hierarchy:
- :x: **express-jwt-5.3.1.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In express-jwt (NPM package) up and including version 5.3.3, the algorithms entry to be specified in the configuration is not being enforced. When algorithms is not specified in the configuration, with the combination of jwks-rsa, it may lead to authorization bypass. You are affected by this vulnerability if all of the following conditions apply: - You are using express-jwt - You do not have **algorithms** configured in your express-jwt configuration. - You are using libraries such as jwks-rsa as the **secret**. You can fix this by specifying **algorithms** in the express-jwt configuration. See linked GHSA for example. This is also fixed in version 6.0.0.
<p>Publish Date: 2020-06-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15084>CVE-2020-15084</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: N/A
- Attack Complexity: N/A
- Privileges Required: N/A
- User Interaction: N/A
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/auth0/express-jwt/security/advisories/GHSA-6g6m-m6h5-w9gf">https://github.com/auth0/express-jwt/security/advisories/GHSA-6g6m-m6h5-w9gf</a></p>
<p>Release Date: 2020-06-30</p>
<p>Fix Resolution: 6.0.0</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"express-jwt","packageVersion":"5.3.1","isTransitiveDependency":false,"dependencyTree":"express-jwt:5.3.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"6.0.0"}],"vulnerabilityIdentifier":"CVE-2020-15084","vulnerabilityDetails":"In express-jwt (NPM package) up and including version 5.3.3, the algorithms entry to be specified in the configuration is not being enforced. When algorithms is not specified in the configuration, with the combination of jwks-rsa, it may lead to authorization bypass. You are affected by this vulnerability if all of the following conditions apply: - You are using express-jwt - You do not have **algorithms** configured in your express-jwt configuration. - You are using libraries such as jwks-rsa as the **secret**. You can fix this by specifying **algorithms** in the express-jwt configuration. See linked GHSA for example. This is also fixed in version 6.0.0.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15084","cvss3Severity":"high","cvss3Score":"7.7","cvss3Metrics":{"A":"N/A","AC":"N/A","PR":"N/A","S":"N/A","C":"N/A","UI":"N/A","AV":"N/A","I":"N/A"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-15084 (High) detected in express-jwt-5.3.1.tgz - ## CVE-2020-15084 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>express-jwt-5.3.1.tgz</b></p></summary>
<p>JWT authentication middleware.</p>
<p>Library home page: <a href="https://registry.npmjs.org/express-jwt/-/express-jwt-5.3.1.tgz">https://registry.npmjs.org/express-jwt/-/express-jwt-5.3.1.tgz</a></p>
<p>Path to dependency file: /cncjs/package.json</p>
<p>Path to vulnerable library: /cncjs/src/node_modules/express-jwt/package.json</p>
<p>
Dependency Hierarchy:
- :x: **express-jwt-5.3.1.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In express-jwt (NPM package) up and including version 5.3.3, the algorithms entry to be specified in the configuration is not being enforced. When algorithms is not specified in the configuration, with the combination of jwks-rsa, it may lead to authorization bypass. You are affected by this vulnerability if all of the following conditions apply: - You are using express-jwt - You do not have **algorithms** configured in your express-jwt configuration. - You are using libraries such as jwks-rsa as the **secret**. You can fix this by specifying **algorithms** in the express-jwt configuration. See linked GHSA for example. This is also fixed in version 6.0.0.
<p>Publish Date: 2020-06-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15084>CVE-2020-15084</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: N/A
- Attack Complexity: N/A
- Privileges Required: N/A
- User Interaction: N/A
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/auth0/express-jwt/security/advisories/GHSA-6g6m-m6h5-w9gf">https://github.com/auth0/express-jwt/security/advisories/GHSA-6g6m-m6h5-w9gf</a></p>
<p>Release Date: 2020-06-30</p>
<p>Fix Resolution: 6.0.0</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"express-jwt","packageVersion":"5.3.1","isTransitiveDependency":false,"dependencyTree":"express-jwt:5.3.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"6.0.0"}],"vulnerabilityIdentifier":"CVE-2020-15084","vulnerabilityDetails":"In express-jwt (NPM package) up and including version 5.3.3, the algorithms entry to be specified in the configuration is not being enforced. When algorithms is not specified in the configuration, with the combination of jwks-rsa, it may lead to authorization bypass. You are affected by this vulnerability if all of the following conditions apply: - You are using express-jwt - You do not have **algorithms** configured in your express-jwt configuration. - You are using libraries such as jwks-rsa as the **secret**. You can fix this by specifying **algorithms** in the express-jwt configuration. See linked GHSA for example. This is also fixed in version 6.0.0.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15084","cvss3Severity":"high","cvss3Score":"7.7","cvss3Metrics":{"A":"N/A","AC":"N/A","PR":"N/A","S":"N/A","C":"N/A","UI":"N/A","AV":"N/A","I":"N/A"},"extraData":{}}</REMEDIATE> --> | non_infrastructure | cve high detected in express jwt tgz cve high severity vulnerability vulnerable library express jwt tgz jwt authentication middleware library home page a href path to dependency file cncjs package json path to vulnerable library cncjs src node modules express jwt package json dependency hierarchy x express jwt tgz vulnerable library vulnerability details in express jwt npm package up and including version the algorithms entry to be specified in the configuration is not being enforced when algorithms is not specified in the configuration with the combination of jwks rsa it may lead to authorization bypass you are affected by this vulnerability if all of the following conditions apply you are using express jwt you do not have algorithms configured in your express jwt configuration you are using libraries such as jwks rsa as the secret you can fix this by specifying algorithms in the express jwt configuration see linked ghsa for example this is also fixed in version publish date url a href cvss score details base score metrics exploitability metrics attack vector n a attack complexity n a privileges required n a user interaction n a scope n a impact metrics confidentiality impact n a integrity impact n a availability impact n a for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution check this box to open an automated fix pr isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails in express jwt npm package up and including version the algorithms entry to be specified in the configuration is not being enforced when algorithms is not specified in the configuration with the combination of jwks rsa it may lead to authorization bypass you are affected by this vulnerability if all of the following conditions apply you are using express jwt you do not have algorithms configured in your express jwt configuration you are using libraries such as jwks rsa as the secret you can fix this by specifying algorithms in the express jwt configuration see linked ghsa for example this is also fixed in version vulnerabilityurl | 0 |
32,382 | 26,660,487,016 | IssuesEvent | 2023-01-25 20:37:31 | PavlidisLab/Gemma | https://api.github.com/repos/PavlidisLab/Gemma | closed | Review the possibility of using systemd's configuration reloading mechanism | infrastructure low priority | This is mainly for reloading Log4j configuration and maybe Tomcat configuration as well. I'm not sure if it would be wise nor feasible to reload Gemma-specific settings. | 1.0 | Review the possibility of using systemd's configuration reloading mechanism - This is mainly for reloading Log4j configuration and maybe Tomcat configuration as well. I'm not sure if it would be wise nor feasible to reload Gemma-specific settings. | infrastructure | review the possibility of using systemd s configuration reloading mechanism this is mainly for reloading configuration and maybe tomcat configuration as well i m not sure if it would be wise nor feasible to reload gemma specific settings | 1 |
32,826 | 27,017,113,661 | IssuesEvent | 2023-02-10 20:32:15 | helpwave/services | https://api.github.com/repos/helpwave/services | opened | Adopt the Custom Resources of APISX | enhancement infrastructure | ### Is your feature request related to a problem? Please describe:
> Please provide a clear and concise description of what the problem is.
Right now, when APISIX gets deployed via our IaC. The first manual step is to setup the upstream, services and routes via the dashboard of APISIX.
### Describe the solution you'd like
> Please provide a clear and concise description of what you want to happen.
The problem mentioned above can be solved by using the Custom Resources in our IaC which are already installed with APISIX.
### Additional Comments
> Add any other context about the feature request here.
- [ ] Define upstream, service and route to the apisix-dapr sidecar
- [ ] Use random secret for the APISIX dashboard | 1.0 | Adopt the Custom Resources of APISX - ### Is your feature request related to a problem? Please describe:
> Please provide a clear and concise description of what the problem is.
Right now, when APISIX gets deployed via our IaC. The first manual step is to setup the upstream, services and routes via the dashboard of APISIX.
### Describe the solution you'd like
> Please provide a clear and concise description of what you want to happen.
The problem mentioned above can be solved by using the Custom Resources in our IaC which are already installed with APISIX.
### Additional Comments
> Add any other context about the feature request here.
- [ ] Define upstream, service and route to the apisix-dapr sidecar
- [ ] Use random secret for the APISIX dashboard | infrastructure | adopt the custom resources of apisx is your feature request related to a problem please describe please provide a clear and concise description of what the problem is right now when apisix gets deployed via our iac the first manual step is to setup the upstream services and routes via the dashboard of apisix describe the solution you d like please provide a clear and concise description of what you want to happen the problem mentioned above can be solved by using the custom resources in our iac which are already installed with apisix additional comments add any other context about the feature request here define upstream service and route to the apisix dapr sidecar use random secret for the apisix dashboard | 1 |
43,298 | 7,036,909,721 | IssuesEvent | 2017-12-28 11:37:27 | bpampuch/pdfmake | https://api.github.com/repos/bpampuch/pdfmake | closed | Cannot read property 'Roboto-Regular.ttf' of undefined using Require js | documentation | Hi i am facing an error while managing pdfmake dependency with require js.
Error facing is "Cannot read property 'Roboto-Regular.ttf".
Any help would be appreciated. One thing more it works fine without using require js.
require.config({
paths: {
```
pdfmake:'../vendor/build/pdfmake.min',
vfs_fonts:'../vendor/build/vfs_fonts'
```
},
shim: {
pdfmake:{
deps:['vfs_fonts']
}
}
| 1.0 | Cannot read property 'Roboto-Regular.ttf' of undefined using Require js - Hi i am facing an error while managing pdfmake dependency with require js.
Error facing is "Cannot read property 'Roboto-Regular.ttf".
Any help would be appreciated. One thing more it works fine without using require js.
require.config({
paths: {
```
pdfmake:'../vendor/build/pdfmake.min',
vfs_fonts:'../vendor/build/vfs_fonts'
```
},
shim: {
pdfmake:{
deps:['vfs_fonts']
}
}
| non_infrastructure | cannot read property roboto regular ttf of undefined using require js hi i am facing an error while managing pdfmake dependency with require js error facing is cannot read property roboto regular ttf any help would be appreciated one thing more it works fine without using require js require config paths pdfmake vendor build pdfmake min vfs fonts vendor build vfs fonts shim pdfmake deps | 0 |
33,675 | 27,709,932,669 | IssuesEvent | 2023-03-14 13:40:54 | CDCgov/data-exchange-hl7 | https://api.github.com/repos/CDCgov/data-exchange-hl7 | opened | Need to install the Fortify software | infrastructure | Before deploying code into dev server need to Run Security Scan and remediate bugs in code using Fortify Static Code Analysis tool. | 1.0 | Need to install the Fortify software - Before deploying code into dev server need to Run Security Scan and remediate bugs in code using Fortify Static Code Analysis tool. | infrastructure | need to install the fortify software before deploying code into dev server need to run security scan and remediate bugs in code using fortify static code analysis tool | 1 |
4,933 | 5,343,984,200 | IssuesEvent | 2017-02-17 13:12:50 | elmsln/elmsln | https://api.github.com/repos/elmsln/elmsln | closed | Session Expiration for Bakery Master Site | community infrastructure question | Issue linked to #920
We currently use the elmsln bakery setup to handle authentication between systems but have the CIS as the master site.
Each of the slave sites will log the user out after a certain amount of time, however this is never the case for the master site/CIS. The user will stay logged in until someone is logged out. Is it possible to set the session expiration time to be the same as the other systems? | 1.0 | Session Expiration for Bakery Master Site - Issue linked to #920
We currently use the elmsln bakery setup to handle authentication between systems but have the CIS as the master site.
Each of the slave sites will log the user out after a certain amount of time, however this is never the case for the master site/CIS. The user will stay logged in until someone is logged out. Is it possible to set the session expiration time to be the same as the other systems? | infrastructure | session expiration for bakery master site issue linked to we currently use the elmsln bakery setup to handle authentication between systems but have the cis as the master site each of the slave sites will log the user out after a certain amount of time however this is never the case for the master site cis the user will stay logged in until someone is logged out is it possible to set the session expiration time to be the same as the other systems | 1 |
99,048 | 30,262,970,393 | IssuesEvent | 2023-07-07 09:36:06 | invertase/react-native-firebase | https://api.github.com/repos/invertase/react-native-firebase | closed | [🐛] XCode 14.3 iOS Build Error - Undefined _swift_stdlib_isStackAllocationSafe | Impact: Bug Platform: iOS Impact: Build Error Resolution: Needs Repro Type: Stale | <!---
**Note <= v5 is deprecated, v5 issues are unlikely to get attention. Feel free to ask in discussions instead.**
Hello there you awesome person;
Please note that the issue list of this repo is exclusively for bug reports;
1) For feature requests, questions and general support please use [GitHub Discussions](https://github.com/invertase/react-native-firebase/discussions).
2) If this is a setup issue then please make sure you've correctly followed the setup guides, most setup issues such as 'duplicate dex files', 'default app has not been initialized' etc are all down to an incorrect setup as the guides haven't been correctly followed.
-->
<!-- NOTE: You can change any of the `[ ]` to `[x]` to mark an option(s) as selected -->
<!-- PLEASE DO NOT REMOVE ANY SECTIONS FROM THIS ISSUE TEMPLATE -->
<!-- Leave them as they are even if they're irrelevant to your issue -->
## Issue
<!-- Please describe your issue here --^ and provide as much detail as you can. -->
<!-- Include code snippets that show your usages of the library in the context of your project. -->
<!-- Snippets that also show how and where the library is imported in JS are useful to debug issues relating to importing or methods not found issues -->
I have just updated my Mac to Ventura 13.3 and XCode got updated to 14.3. And now my app is not archived (but works in debug on simulator) anymore and outputs build error when building Firebase pods:
```
Undefined symbols for architecture arm64:
"_swift_stdlib_isStackAllocationSafe", referenced from:
_$ss17_NativeDictionaryV6filteryAByxq_GSbx3key_q_5valuet_tKXEKF20FirebaseCoreInternal10TimePeriodO_10Foundation4DateVTg504$s20fg10Internal10ij14O10Foundation4L41VSbs5Error_pIgyndzo_AcFSbsAG_pIegnndzo_TRAiLSbs0R0_pIgyndzo_Tf1cn_n in libFirebaseCoreInternal.a(HeartbeatController.o
```
---
## Environment
<details><summary>Click To Expand</summary>
<p>
**`react-native info` output:**
<!-- Please run `react-native info` on your terminal and paste the contents into the code block below -->
```
System:
OS: macOS 13.3
CPU: (8) arm64 Apple M1
Memory: 125.84 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 19.7.0 - /opt/homebrew/bin/node
Yarn: 1.22.18 - /opt/homebrew/bin/yarn
npm: 9.5.0 - /opt/homebrew/bin/npm
Watchman: 2023.03.06.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.12.0 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
Android SDK:
Android NDK: 22.1.7171670
IDEs:
Android Studio: 2022.1 AI-221.6008.13.2211.9619390
Xcode: 14.3/14E222b - /usr/bin/xcodebuild
Languages:
Java: 11.0.16 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: ^18.2.0 => 18.2.0
react-native: ^0.71.6 => 0.71.6
react-native-macos: Not Found
npmGlobalPackages:
*react-native*: Not Found
```
<!-- change `[ ]` to `[x]` to select an option(s) -->
- **Platform that you're experiencing the issue on**:
- [x] iOS
- [ ] Android
- [ ] **iOS** but have not tested behavior on Android
- [ ] **Android** but have not tested behavior on iOS
- [ ] Both
- **`react-native-firebase` version you're using that has this issue:**
- `e.g. 17.4.1`
- **`Firebase` module(s) you're using that has the issue:**
- `app`, `Analytics`, `Crashlytics`, `Messaging`, `remote-config`, `installations`
- **Are you using `TypeScript`?**
- `Y` & `5.0.3`
</p>
</details>
<!-- Thanks for reading this far down ❤️ -->
<!-- High quality, detailed issues are much easier to triage for maintainers -->
<!-- For bonus points, if you put a 🔥 (:fire:) emojii at the start of the issue title we'll know -->
<!-- that you took the time to fill this out correctly, or, at least read this far -->
---
- 👉 Check out [`React Native Firebase`](https://twitter.com/rnfirebase) and [`Invertase`](https://twitter.com/invertaseio) on Twitter for updates on the library.
| 1.0 | [🐛] XCode 14.3 iOS Build Error - Undefined _swift_stdlib_isStackAllocationSafe - <!---
**Note <= v5 is deprecated, v5 issues are unlikely to get attention. Feel free to ask in discussions instead.**
Hello there you awesome person;
Please note that the issue list of this repo is exclusively for bug reports;
1) For feature requests, questions and general support please use [GitHub Discussions](https://github.com/invertase/react-native-firebase/discussions).
2) If this is a setup issue then please make sure you've correctly followed the setup guides, most setup issues such as 'duplicate dex files', 'default app has not been initialized' etc are all down to an incorrect setup as the guides haven't been correctly followed.
-->
<!-- NOTE: You can change any of the `[ ]` to `[x]` to mark an option(s) as selected -->
<!-- PLEASE DO NOT REMOVE ANY SECTIONS FROM THIS ISSUE TEMPLATE -->
<!-- Leave them as they are even if they're irrelevant to your issue -->
## Issue
<!-- Please describe your issue here --^ and provide as much detail as you can. -->
<!-- Include code snippets that show your usages of the library in the context of your project. -->
<!-- Snippets that also show how and where the library is imported in JS are useful to debug issues relating to importing or methods not found issues -->
I have just updated my Mac to Ventura 13.3 and XCode got updated to 14.3. And now my app is not archived (but works in debug on simulator) anymore and outputs build error when building Firebase pods:
```
Undefined symbols for architecture arm64:
"_swift_stdlib_isStackAllocationSafe", referenced from:
_$ss17_NativeDictionaryV6filteryAByxq_GSbx3key_q_5valuet_tKXEKF20FirebaseCoreInternal10TimePeriodO_10Foundation4DateVTg504$s20fg10Internal10ij14O10Foundation4L41VSbs5Error_pIgyndzo_AcFSbsAG_pIegnndzo_TRAiLSbs0R0_pIgyndzo_Tf1cn_n in libFirebaseCoreInternal.a(HeartbeatController.o
```
---
## Environment
<details><summary>Click To Expand</summary>
<p>
**`react-native info` output:**
<!-- Please run `react-native info` on your terminal and paste the contents into the code block below -->
```
System:
OS: macOS 13.3
CPU: (8) arm64 Apple M1
Memory: 125.84 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 19.7.0 - /opt/homebrew/bin/node
Yarn: 1.22.18 - /opt/homebrew/bin/yarn
npm: 9.5.0 - /opt/homebrew/bin/npm
Watchman: 2023.03.06.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.12.0 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
Android SDK:
Android NDK: 22.1.7171670
IDEs:
Android Studio: 2022.1 AI-221.6008.13.2211.9619390
Xcode: 14.3/14E222b - /usr/bin/xcodebuild
Languages:
Java: 11.0.16 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: ^18.2.0 => 18.2.0
react-native: ^0.71.6 => 0.71.6
react-native-macos: Not Found
npmGlobalPackages:
*react-native*: Not Found
```
<!-- change `[ ]` to `[x]` to select an option(s) -->
- **Platform that you're experiencing the issue on**:
- [x] iOS
- [ ] Android
- [ ] **iOS** but have not tested behavior on Android
- [ ] **Android** but have not tested behavior on iOS
- [ ] Both
- **`react-native-firebase` version you're using that has this issue:**
- `e.g. 17.4.1`
- **`Firebase` module(s) you're using that has the issue:**
- `app`, `Analytics`, `Crashlytics`, `Messaging`, `remote-config`, `installations`
- **Are you using `TypeScript`?**
- `Y` & `5.0.3`
</p>
</details>
<!-- Thanks for reading this far down ❤️ -->
<!-- High quality, detailed issues are much easier to triage for maintainers -->
<!-- For bonus points, if you put a 🔥 (:fire:) emojii at the start of the issue title we'll know -->
<!-- that you took the time to fill this out correctly, or, at least read this far -->
---
- 👉 Check out [`React Native Firebase`](https://twitter.com/rnfirebase) and [`Invertase`](https://twitter.com/invertaseio) on Twitter for updates on the library.
| non_infrastructure | xcode ios build error undefined swift stdlib isstackallocationsafe note is deprecated issues are unlikely to get attention feel free to ask in discussions instead hello there you awesome person please note that the issue list of this repo is exclusively for bug reports for feature requests questions and general support please use if this is a setup issue then please make sure you ve correctly followed the setup guides most setup issues such as duplicate dex files default app has not been initialized etc are all down to an incorrect setup as the guides haven t been correctly followed issue i have just updated my mac to ventura and xcode got updated to and now my app is not archived but works in debug on simulator anymore and outputs build error when building firebase pods undefined symbols for architecture swift stdlib isstackallocationsafe referenced from q pigyndzo acfsbsag piegnndzo pigyndzo n in libfirebasecoreinternal a heartbeatcontroller o environment click to expand react native info output system os macos cpu apple memory mb gb shell bin bash binaries node opt homebrew bin node yarn opt homebrew bin yarn npm opt homebrew bin npm watchman opt homebrew bin watchman managers cocoapods opt homebrew bin pod sdks ios sdk platforms driverkit ios macos tvos watchos android sdk android ndk ides android studio ai xcode usr bin xcodebuild languages java usr bin javac npmpackages react native community cli not found react react native react native macos not found npmglobalpackages react native not found platform that you re experiencing the issue on ios android ios but have not tested behavior on android android but have not tested behavior on ios both react native firebase version you re using that has this issue e g firebase module s you re using that has the issue app analytics crashlytics messaging remote config installations are you using typescript y 👉 check out and on twitter for updates on the library | 0 |
21,205 | 14,441,447,304 | IssuesEvent | 2020-12-07 16:48:24 | pulibrary/dspace-development | https://api.github.com/repos/pulibrary/dspace-development | closed | Update the X.509 certificates for the Symplectic Elements servers | infrastructure symplectic elements | These were provided by the Operations Team, and must be directly applied on the server. | 1.0 | Update the X.509 certificates for the Symplectic Elements servers - These were provided by the Operations Team, and must be directly applied on the server. | infrastructure | update the x certificates for the symplectic elements servers these were provided by the operations team and must be directly applied on the server | 1 |
13,174 | 10,133,855,754 | IssuesEvent | 2019-08-02 05:24:17 | oppia/oppia-android | https://api.github.com/repos/oppia/oppia-android | opened | Per-profile data storage system | Priority: Essential Status: Blocked Type: Improvement Where: Infrastructure | Individual profiles will need to have data associated with them directly. Such data requires a system to organize other file I/O systems based on the current profile that's selected. This system should interop directly with the other I/O systems described above rather than reimplement them. One possible manifestation of this might be a series of providers for the other I/O systems based on profile ID.
Note that this system is not responsible for managing the current profile logged in, though it should be designed with per-profile Takeout/Wipeout in mind. | 1.0 | Per-profile data storage system - Individual profiles will need to have data associated with them directly. Such data requires a system to organize other file I/O systems based on the current profile that's selected. This system should interop directly with the other I/O systems described above rather than reimplement them. One possible manifestation of this might be a series of providers for the other I/O systems based on profile ID.
Note that this system is not responsible for managing the current profile logged in, though it should be designed with per-profile Takeout/Wipeout in mind. | infrastructure | per profile data storage system individual profiles will need to have data associated with them directly such data requires a system to organize other file i o systems based on the current profile that s selected this system should interop directly with the other i o systems described above rather than reimplement them one possible manifestation of this might be a series of providers for the other i o systems based on profile id note that this system is not responsible for managing the current profile logged in though it should be designed with per profile takeout wipeout in mind | 1 |
12,740 | 9,936,025,948 | IssuesEvent | 2019-07-02 18:02:57 | dart-lang/sdk | https://api.github.com/repos/dart-lang/sdk | closed | use relative paths on repro instructions of test failures | area-infrastructure closed-cannot-reproduce | Now that we use --packages instead of package-root, the repro instructions contain absolute paths from the bots. For example:
```
Short reproduction command (experimental):
python tools/test.py -mrelease --use-sdk --checked --write-debug-log --write-test-outcome-log --copy-coredumps -t60 --packages /mnt/data/b/build/slave/analyzer-linux-release-be/build/sdk/.packages pkg/analysis_server/test/integration/analysis/update_content_test
```
It would be good to make the path to `.packages` relative so you can easily copy/paste the repro instructions.
Even better: we could remove flags that are unlikely a cause of the failure or that have the default value, for example, in the code we can remove `--packages`, and also `--write-debug-log --write-test-outcome-log --copy-coredumps -t60`
/cc @whesse
| 1.0 | use relative paths on repro instructions of test failures - Now that we use --packages instead of package-root, the repro instructions contain absolute paths from the bots. For example:
```
Short reproduction command (experimental):
python tools/test.py -mrelease --use-sdk --checked --write-debug-log --write-test-outcome-log --copy-coredumps -t60 --packages /mnt/data/b/build/slave/analyzer-linux-release-be/build/sdk/.packages pkg/analysis_server/test/integration/analysis/update_content_test
```
It would be good to make the path to `.packages` relative so you can easily copy/paste the repro instructions.
Even better: we could remove flags that are unlikely a cause of the failure or that have the default value, for example, in the code we can remove `--packages`, and also `--write-debug-log --write-test-outcome-log --copy-coredumps -t60`
/cc @whesse
| infrastructure | use relative paths on repro instructions of test failures now that we use packages instead of package root the repro instructions contain absolute paths from the bots for example short reproduction command experimental python tools test py mrelease use sdk checked write debug log write test outcome log copy coredumps packages mnt data b build slave analyzer linux release be build sdk packages pkg analysis server test integration analysis update content test it would be good to make the path to packages relative so you can easily copy paste the repro instructions even better we could remove flags that are unlikely a cause of the failure or that have the default value for example in the code we can remove packages and also write debug log write test outcome log copy coredumps cc whesse | 1 |
665,589 | 22,322,479,523 | IssuesEvent | 2022-06-14 07:47:30 | UseCrowdWise/crowdwise | https://api.github.com/repos/UseCrowdWise/crowdwise | closed | Scraping the comments from provider results (HN/Reddit). | enhancement PRIORITY-HIGH | Backend:
- Crawl the top result for each provider for comments
- Don't crawl if there 0 comments
UI: show top comments before all provider post results
| 1.0 | Scraping the comments from provider results (HN/Reddit). - Backend:
- Crawl the top result for each provider for comments
- Don't crawl if there 0 comments
UI: show top comments before all provider post results
| non_infrastructure | scraping the comments from provider results hn reddit backend crawl the top result for each provider for comments don t crawl if there comments ui show top comments before all provider post results | 0 |
176,341 | 6,558,444,498 | IssuesEvent | 2017-09-06 21:25:52 | FreeAndFair/ColoradoRLA | https://api.github.com/repos/FreeAndFair/ColoradoRLA | opened | Alert user if public seed date invalid | CDOS Priority client feature ui/ux | The date of the public meeting to establish the random seed must be strictly _after_ the election date. | 1.0 | Alert user if public seed date invalid - The date of the public meeting to establish the random seed must be strictly _after_ the election date. | non_infrastructure | alert user if public seed date invalid the date of the public meeting to establish the random seed must be strictly after the election date | 0 |
142,573 | 5,476,493,150 | IssuesEvent | 2017-03-11 21:08:56 | pmeas/pmeas-frontend | https://api.github.com/repos/pmeas/pmeas-frontend | closed | Only show the remove button during mouse over. | Difficulty: Easy Priority: Medium Type: Bug | In the enabled effects list the remove button, which looks something like "x", should only show when the user's mouse hovers over the button. | 1.0 | Only show the remove button during mouse over. - In the enabled effects list the remove button, which looks something like "x", should only show when the user's mouse hovers over the button. | non_infrastructure | only show the remove button during mouse over in the enabled effects list the remove button which looks something like x should only show when the user s mouse hovers over the button | 0 |
23,362 | 16,091,678,066 | IssuesEvent | 2021-04-26 17:29:57 | google/site-kit-wp | https://api.github.com/repos/google/site-kit-wp | closed | All traffic widget styles inconsistent in Storybook | Good First Issue P2 Type: Infrastructure | ## Bug Description
The styling of the all traffic widget in Storybook is inconsistent with the styles in WordPress which show correctly.
This is due to its styles being coupled to its `widgetSlug` which is not consistent in Storybook (see `generateReportBasedWidgetStories`). This may only affect the tab bar which is the most obvious, but it may affect other parts as well.
See the current component in Storybook here:
https://google.github.io/site-kit-wp/storybook/main/?path=/story/analytics-module-components-dashboard-all-traffic-widget--loaded
## Screenshots
**Storybook**
**On Dashboard**
---------------
_Do not alter or remove anything below. The following sections will be managed by moderators only._
## Acceptance criteria
* All styles on the new All Traffic widget should be independent of the widget slug (or CSS classes derived from it)
* The All Traffic Widget stories should be visually consistent with the widget rendered in WordPress
## Implementation Brief
* Using `assets/js/modules/analytics/components/dashboard/DashboardAllTrafficWidget/index.js`,
* Add the `googlesitekit-widget__analytics--all-traffic` class name in addition to the existing `googlesitekit-widget--footer-v2` class name to the `Widget` component.
* Using `assets/sass/widgets/_googlesitekit-widget-analyticsAllTraffic.scss`,
* Replace the `.googlesitekit-widget.googlesitekit-widget--analyticsAllTraffic` selector by `.googlesitekit-widget__analytics--all-traffic`.
### Test Coverage
* N/A
### Visual Regression Changes
* N/A
## QA Brief
* Check the story above (https://google.github.io/site-kit-wp/storybook/develop/?path=/story/analytics-module-components-dashboard-all-traffic-widget--loaded) and ensure the spacing is not off as reported in the issue.
* Check that the All Traffic Widget on the dashboard of the site remains the same and hasn't changed based on this change.
## Changelog entry
* N/A
| 1.0 | All traffic widget styles inconsistent in Storybook - ## Bug Description
The styling of the all traffic widget in Storybook is inconsistent with the styles in WordPress which show correctly.
This is due to its styles being coupled to its `widgetSlug` which is not consistent in Storybook (see `generateReportBasedWidgetStories`). This may only affect the tab bar which is the most obvious, but it may affect other parts as well.
See the current component in Storybook here:
https://google.github.io/site-kit-wp/storybook/main/?path=/story/analytics-module-components-dashboard-all-traffic-widget--loaded
## Screenshots
**Storybook**
**On Dashboard**
---------------
_Do not alter or remove anything below. The following sections will be managed by moderators only._
## Acceptance criteria
* All styles on the new All Traffic widget should be independent of the widget slug (or CSS classes derived from it)
* The All Traffic Widget stories should be visually consistent with the widget rendered in WordPress
## Implementation Brief
* Using `assets/js/modules/analytics/components/dashboard/DashboardAllTrafficWidget/index.js`,
* Add the `googlesitekit-widget__analytics--all-traffic` class name in addition to the existing `googlesitekit-widget--footer-v2` class name to the `Widget` component.
* Using `assets/sass/widgets/_googlesitekit-widget-analyticsAllTraffic.scss`,
* Replace the `.googlesitekit-widget.googlesitekit-widget--analyticsAllTraffic` selector by `.googlesitekit-widget__analytics--all-traffic`.
### Test Coverage
* N/A
### Visual Regression Changes
* N/A
## QA Brief
* Check the story above (https://google.github.io/site-kit-wp/storybook/develop/?path=/story/analytics-module-components-dashboard-all-traffic-widget--loaded) and ensure the spacing is not off as reported in the issue.
* Check that the All Traffic Widget on the dashboard of the site remains the same and hasn't changed based on this change.
## Changelog entry
* N/A
| infrastructure | all traffic widget styles inconsistent in storybook bug description the styling of the all traffic widget in storybook is inconsistent with the styles in wordpress which show correctly this is due to its styles being coupled to its widgetslug which is not consistent in storybook see generatereportbasedwidgetstories this may only affect the tab bar which is the most obvious but it may affect other parts as well see the current component in storybook here screenshots storybook on dashboard do not alter or remove anything below the following sections will be managed by moderators only acceptance criteria all styles on the new all traffic widget should be independent of the widget slug or css classes derived from it the all traffic widget stories should be visually consistent with the widget rendered in wordpress implementation brief using assets js modules analytics components dashboard dashboardalltrafficwidget index js add the googlesitekit widget analytics all traffic class name in addition to the existing googlesitekit widget footer class name to the widget component using assets sass widgets googlesitekit widget analyticsalltraffic scss replace the googlesitekit widget googlesitekit widget analyticsalltraffic selector by googlesitekit widget analytics all traffic test coverage n a visual regression changes n a qa brief check the story above and ensure the spacing is not off as reported in the issue check that the all traffic widget on the dashboard of the site remains the same and hasn t changed based on this change changelog entry n a | 1 |
336,693 | 30,216,059,920 | IssuesEvent | 2023-07-05 15:39:15 | RamenDR/ramen | https://api.github.com/repos/RamenDR/ramen | closed | VolSync integration in test environment | test | According to @ShyamsundarR, volsync will be installed by ramen automatically using cluster manager add-on mechanism.
But even if ramen installs volsync, we have the issue that volsync crds are missing.
This causes ramen to fail on the managed cluster after few minutes. Can be fixed by
disabling volsync in ramen config manually, but this does not make sense if we want
to test volsync in the e2e tests.
Tasks:
- [x] Install volsync crds as part of starting the environment so we don't have to disable volsync in ramen configmap
- [ ] If we install volsync crds, should install also the operator?
- [ ] Is volsync installed automatically as expected?
- [ ] Does it work without submariner?
- The minikube clusters are using host network, so all of them are in libvirt default network (192.168.122.0/24)
Needs to discuss the right way to solve this.
Maybe start with disabling volsync in ramen config, since we don't need for metro dr
e2e tests, which is more urgent than regional dr e2e tests.
@BenamarMk what do yo think?
| 1.0 | VolSync integration in test environment - According to @ShyamsundarR, volsync will be installed by ramen automatically using cluster manager add-on mechanism.
But even if ramen installs volsync, we have the issue that volsync crds are missing.
This causes ramen to fail on the managed cluster after few minutes. Can be fixed by
disabling volsync in ramen config manually, but this does not make sense if we want
to test volsync in the e2e tests.
Tasks:
- [x] Install volsync crds as part of starting the environment so we don't have to disable volsync in ramen configmap
- [ ] If we install volsync crds, should install also the operator?
- [ ] Is volsync installed automatically as expected?
- [ ] Does it work without submariner?
- The minikube clusters are using host network, so all of them are in libvirt default network (192.168.122.0/24)
Needs to discuss the right way to solve this.
Maybe start with disabling volsync in ramen config, since we don't need for metro dr
e2e tests, which is more urgent than regional dr e2e tests.
@BenamarMk what do yo think?
| non_infrastructure | volsync integration in test environment according to shyamsundarr volsync will be installed by ramen automatically using cluster manager add on mechanism but even if ramen installs volsync we have the issue that volsync crds are missing this causes ramen to fail on the managed cluster after few minutes can be fixed by disabling volsync in ramen config manually but this does not make sense if we want to test volsync in the tests tasks install volsync crds as part of starting the environment so we don t have to disable volsync in ramen configmap if we install volsync crds should install also the operator is volsync installed automatically as expected does it work without submariner the minikube clusters are using host network so all of them are in libvirt default network needs to discuss the right way to solve this maybe start with disabling volsync in ramen config since we don t need for metro dr tests which is more urgent than regional dr tests benamarmk what do yo think | 0 |
19,595 | 13,303,627,290 | IssuesEvent | 2020-08-25 15:46:00 | GoogleChrome/workbox | https://api.github.com/repos/GoogleChrome/workbox | closed | Automate npm dependency updates | Discuss Good First Issue Infrastructure | As mentioned at https://github.com/GoogleChrome/workbox/issues/1656#issuecomment-428693893, a tool like @renovatebot could help keep things up to date. | 1.0 | Automate npm dependency updates - As mentioned at https://github.com/GoogleChrome/workbox/issues/1656#issuecomment-428693893, a tool like @renovatebot could help keep things up to date. | infrastructure | automate npm dependency updates as mentioned at a tool like renovatebot could help keep things up to date | 1 |
8,655 | 7,545,926,927 | IssuesEvent | 2018-04-17 23:56:16 | dotnet/corefx | https://api.github.com/repos/dotnet/corefx | closed | NuGet build failures in 'prodcon/corefx/master/' - '20180416.01' | area-Infrastructure bug | @dotnet-mc-bot commented on [Sun Apr 15 2018](https://github.com/dotnet/core-eng/issues/3292)
There were a set of failures during this build. Here is a summary of these:
* https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_build?_a=summary&buildId=1594896
- **Agent:** DDVSOLINUXAGE007
- **Error log:** /root/corefx-1594896/external/runtime/runtime.depproj : error NU1102: - Found 414 version(s) in https://dotnetfeed.blob.core.windows.net/dotnet-core/index.json [ Nearest version: 2.1.0-preview3-26416-01 ]...
@mmitche
| 1.0 | NuGet build failures in 'prodcon/corefx/master/' - '20180416.01' - @dotnet-mc-bot commented on [Sun Apr 15 2018](https://github.com/dotnet/core-eng/issues/3292)
There were a set of failures during this build. Here is a summary of these:
* https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_build?_a=summary&buildId=1594896
- **Agent:** DDVSOLINUXAGE007
- **Error log:** /root/corefx-1594896/external/runtime/runtime.depproj : error NU1102: - Found 414 version(s) in https://dotnetfeed.blob.core.windows.net/dotnet-core/index.json [ Nearest version: 2.1.0-preview3-26416-01 ]...
@mmitche
| infrastructure | nuget build failures in prodcon corefx master dotnet mc bot commented on there were a set of failures during this build here is a summary of these agent error log root corefx external runtime runtime depproj error found version s in mmitche | 1 |
28,160 | 23,067,273,705 | IssuesEvent | 2022-07-25 14:52:40 | Quantco/datajudge | https://api.github.com/repos/Quantco/datajudge | closed | Extend CI. | infrastructure | - [x] Test whether package is building correctly, e.g. whether `flit install` finishes successfully.
- [ ] Evaluate test coverage. | 1.0 | Extend CI. - - [x] Test whether package is building correctly, e.g. whether `flit install` finishes successfully.
- [ ] Evaluate test coverage. | infrastructure | extend ci test whether package is building correctly e g whether flit install finishes successfully evaluate test coverage | 1 |
19,343 | 13,220,253,608 | IssuesEvent | 2020-08-17 12:04:11 | libero/reviewer | https://api.github.com/repos/libero/reviewer | closed | Add reviewer-report to helm chart | Infrastructure | Makes no sense to have separate builder deploy just for reviewer-reporter if we can run it as a k8s cron-job.
Tasks:
- [x] make container send report on execution (remove cron)
- [x] add cronjob to helm chart with interval settings
- [x] add dependabot to repo
- [x] add secret to cluster
- [x] test
| 1.0 | Add reviewer-report to helm chart - Makes no sense to have separate builder deploy just for reviewer-reporter if we can run it as a k8s cron-job.
Tasks:
- [x] make container send report on execution (remove cron)
- [x] add cronjob to helm chart with interval settings
- [x] add dependabot to repo
- [x] add secret to cluster
- [x] test
| infrastructure | add reviewer report to helm chart makes no sense to have separate builder deploy just for reviewer reporter if we can run it as a cron job tasks make container send report on execution remove cron add cronjob to helm chart with interval settings add dependabot to repo add secret to cluster test | 1 |
15,053 | 11,309,489,751 | IssuesEvent | 2020-01-19 13:34:48 | kaitai-io/kaitai_struct | https://api.github.com/repos/kaitai-io/kaitai_struct | opened | sbt: cross project | infrastructure | Since recent updates of sbt, it started to give this warning:
```
/home/travis/build/kaitai-io/kaitai_struct/compiler/build.sbt:22: warning: method crossProjectFromBuilder in trait CrossProjectExtra is deprecated (since 0.6.23): The built-in cross-project feature of sbt-scalajs is deprecated. Use the separate sbt plugin sbt-crossproject instead: https://github.com/portable-scala/sbt-crossproject
lazy val compiler = crossProject.in(file(".")).
^
```
It looks like we need to migrate to https://github.com/portable-scala/sbt-crossproject | 1.0 | sbt: cross project - Since recent updates of sbt, it started to give this warning:
```
/home/travis/build/kaitai-io/kaitai_struct/compiler/build.sbt:22: warning: method crossProjectFromBuilder in trait CrossProjectExtra is deprecated (since 0.6.23): The built-in cross-project feature of sbt-scalajs is deprecated. Use the separate sbt plugin sbt-crossproject instead: https://github.com/portable-scala/sbt-crossproject
lazy val compiler = crossProject.in(file(".")).
^
```
It looks like we need to migrate to https://github.com/portable-scala/sbt-crossproject | infrastructure | sbt cross project since recent updates of sbt it started to give this warning home travis build kaitai io kaitai struct compiler build sbt warning method crossprojectfrombuilder in trait crossprojectextra is deprecated since the built in cross project feature of sbt scalajs is deprecated use the separate sbt plugin sbt crossproject instead lazy val compiler crossproject in file it looks like we need to migrate to | 1 |
10,134 | 8,381,078,395 | IssuesEvent | 2018-10-07 21:05:25 | RITlug/tasks | https://api.github.com/repos/RITlug/tasks | closed | Regain control of RITlug IFTTT account | infrastructure internal organization needs info priority:med | Currently no one on eboard knows the credentials or email (for password reset) being used for IFTTT, which has hooks for production RITlug things, such as the mailing list. | 1.0 | Regain control of RITlug IFTTT account - Currently no one on eboard knows the credentials or email (for password reset) being used for IFTTT, which has hooks for production RITlug things, such as the mailing list. | infrastructure | regain control of ritlug ifttt account currently no one on eboard knows the credentials or email for password reset being used for ifttt which has hooks for production ritlug things such as the mailing list | 1 |
15,872 | 11,737,559,434 | IssuesEvent | 2020-03-11 14:48:22 | deptofdefense/solo | https://api.github.com/repos/deptofdefense/solo | closed | Terraform container working directory needs updaet | LOE 1 bug infrastructure | Thanks for submitting an issue! Below are a few things you can do to help us more quickly address the issue.
## Checklist
I have…
- [x] described in detail below both the behavior I expected and the behavior I observed.
- [x] thoroughly outlined below the steps to reproduce this issue, including relevant technical details (e.g. device, operating system, browser, browser version).
~~[ ] attached screenshots illustrating relevant behavior.~~
## Expected Behavior
Terraform supplies appropriate working directory to Django based containers (celery, worker, and api)
## Observed Behavior
Terraform overrides working directory defined in dockerfile.
## Steps to Reproduce
To reproduce this issue…
1. Merge PR and view terraform logs in circleci.
## Screenshots
N/A | 1.0 | Terraform container working directory needs updaet - Thanks for submitting an issue! Below are a few things you can do to help us more quickly address the issue.
## Checklist
I have…
- [x] described in detail below both the behavior I expected and the behavior I observed.
- [x] thoroughly outlined below the steps to reproduce this issue, including relevant technical details (e.g. device, operating system, browser, browser version).
~~[ ] attached screenshots illustrating relevant behavior.~~
## Expected Behavior
Terraform supplies appropriate working directory to Django based containers (celery, worker, and api)
## Observed Behavior
Terraform overrides working directory defined in dockerfile.
## Steps to Reproduce
To reproduce this issue…
1. Merge PR and view terraform logs in circleci.
## Screenshots
N/A | infrastructure | terraform container working directory needs updaet thanks for submitting an issue below are a few things you can do to help us more quickly address the issue checklist i have… described in detail below both the behavior i expected and the behavior i observed thoroughly outlined below the steps to reproduce this issue including relevant technical details e g device operating system browser browser version attached screenshots illustrating relevant behavior expected behavior terraform supplies appropriate working directory to django based containers celery worker and api observed behavior terraform overrides working directory defined in dockerfile steps to reproduce to reproduce this issue… merge pr and view terraform logs in circleci screenshots n a | 1 |
17,631 | 12,486,960,414 | IssuesEvent | 2020-05-31 06:04:39 | ForNeVeR/praefectus | https://api.github.com/repos/ForNeVeR/praefectus | closed | Publish framework-dependent packages | kind:infrastructure | Currently we're only publishing the framework-independent packages for supported operating systems, which mean that the only external requirements for our packages are that of .NET Core itself.
It could be good for most cases, but is problematic in terms of package size: even if we apply recommendations from #18, the compressed package is still about 14 MiB, which is very significant for an application that only prints its version to the logs and does nothing else. Compressed framework-dependent package may only take 1.8 MiB.
Thus, I suggest we also publish framework-dependent package for people who have an external runtime already installed.
To do that, it's enough to pass `--self-contained false` to our publish command.
We'll still publish separate packages for all the supported platforms, because the set of native libraries is different, which could create some troubles e.g. if Windows binaries are in macOS app package and require special signing procedure. | 1.0 | Publish framework-dependent packages - Currently we're only publishing the framework-independent packages for supported operating systems, which mean that the only external requirements for our packages are that of .NET Core itself.
It could be good for most cases, but is problematic in terms of package size: even if we apply recommendations from #18, the compressed package is still about 14 MiB, which is very significant for an application that only prints its version to the logs and does nothing else. Compressed framework-dependent package may only take 1.8 MiB.
Thus, I suggest we also publish framework-dependent package for people who have an external runtime already installed.
To do that, it's enough to pass `--self-contained false` to our publish command.
We'll still publish separate packages for all the supported platforms, because the set of native libraries is different, which could create some troubles e.g. if Windows binaries are in macOS app package and require special signing procedure. | infrastructure | publish framework dependent packages currently we re only publishing the framework independent packages for supported operating systems which mean that the only external requirements for our packages are that of net core itself it could be good for most cases but is problematic in terms of package size even if we apply recommendations from the compressed package is still about mib which is very significant for an application that only prints its version to the logs and does nothing else compressed framework dependent package may only take mib thus i suggest we also publish framework dependent package for people who have an external runtime already installed to do that it s enough to pass self contained false to our publish command we ll still publish separate packages for all the supported platforms because the set of native libraries is different which could create some troubles e g if windows binaries are in macos app package and require special signing procedure | 1 |
31,428 | 25,748,178,835 | IssuesEvent | 2022-12-08 11:15:55 | reapit/foundations | https://api.github.com/repos/reapit/foundations | opened | Spike: Use Vite for Foundations Storybook Elements build | feature elements front-end infrastructure | **Background context or User story:**
_Vite is quite mature now, much better dev ex and much quicker than Webpack. It also now supports Linaria and Storybook with a plugin. Experiment to see if we can replace webpack for Elements Storybook_ | 1.0 | Spike: Use Vite for Foundations Storybook Elements build - **Background context or User story:**
_Vite is quite mature now, much better dev ex and much quicker than Webpack. It also now supports Linaria and Storybook with a plugin. Experiment to see if we can replace webpack for Elements Storybook_ | infrastructure | spike use vite for foundations storybook elements build background context or user story vite is quite mature now much better dev ex and much quicker than webpack it also now supports linaria and storybook with a plugin experiment to see if we can replace webpack for elements storybook | 1 |
73,206 | 14,009,221,696 | IssuesEvent | 2020-10-29 01:47:52 | GTNewHorizons/GT-New-Horizons-Modpack | https://api.github.com/repos/GTNewHorizons/GT-New-Horizons-Modpack | closed | Nano circuit requieres weird soldering alloy amount | Type: Need Code changes Type: recipe change | #### Which modpack version are you using?
GTNH 2.0.9.0QF4
#
It requiers 3670L of soldering alloy wich is 26,1111 ingots, that's weird. Make it 26 or 27 or 32 ingots, an integer amount of ingots please.
| 1.0 | Nano circuit requieres weird soldering alloy amount - #### Which modpack version are you using?
GTNH 2.0.9.0QF4
#
It requiers 3670L of soldering alloy wich is 26,1111 ingots, that's weird. Make it 26 or 27 or 32 ingots, an integer amount of ingots please.
| non_infrastructure | nano circuit requieres weird soldering alloy amount which modpack version are you using gtnh it requiers of soldering alloy wich is ingots that s weird make it or or ingots an integer amount of ingots please | 0 |
8,203 | 7,290,635,568 | IssuesEvent | 2018-02-24 04:05:21 | RITlug/tasks | https://api.github.com/repos/RITlug/tasks | opened | Install basic NextCloud server onto Titan VM | EBoard blocked infrastructure priority:low | Once the VM on Titan is ready, @ct-martin will do a base install of NextCloud onto the virtual machine. After this, we are blocked on policy discussions to decide how we want to offer this service to RITlug.
* **Blocked by**: #29
* **DUE**: 2018-03-02 | 1.0 | Install basic NextCloud server onto Titan VM - Once the VM on Titan is ready, @ct-martin will do a base install of NextCloud onto the virtual machine. After this, we are blocked on policy discussions to decide how we want to offer this service to RITlug.
* **Blocked by**: #29
* **DUE**: 2018-03-02 | infrastructure | install basic nextcloud server onto titan vm once the vm on titan is ready ct martin will do a base install of nextcloud onto the virtual machine after this we are blocked on policy discussions to decide how we want to offer this service to ritlug blocked by due | 1 |
32,192 | 26,523,456,590 | IssuesEvent | 2023-01-19 06:14:32 | OpenHistoricalMap/issues | https://api.github.com/repos/OpenHistoricalMap/issues | closed | Tiler 500 errors at zooms >z15 Leaflet / z14 Tegola Preview | vtiles infrastructure | **Bug description**
When I go to a link like this https://www.openhistoricalmap.org/node/2094461996#map=20/54.59851/-5.65506&layers=O&date=1923-01-01&daterange=1923-01-01,2023-12-31, I'm getting no map tiles and the console is full of errors:
This is happening on vtiles endpoint as well, anything over z14 on Tegola preview or z15 in Leaflet (which is the same as z14 Tegola):
https://vtiles.openhistoricalmap.org/#14.82/54.35068/-5.60811
| 1.0 | Tiler 500 errors at zooms >z15 Leaflet / z14 Tegola Preview - **Bug description**
When I go to a link like this https://www.openhistoricalmap.org/node/2094461996#map=20/54.59851/-5.65506&layers=O&date=1923-01-01&daterange=1923-01-01,2023-12-31, I'm getting no map tiles and the console is full of errors:
This is happening on vtiles endpoint as well, anything over z14 on Tegola preview or z15 in Leaflet (which is the same as z14 Tegola):
https://vtiles.openhistoricalmap.org/#14.82/54.35068/-5.60811
| infrastructure | tiler errors at zooms leaflet tegola preview bug description when i go to a link like this i m getting no map tiles and the console is full of errors this is happening on vtiles endpoint as well anything over on tegola preview or in leaflet which is the same as tegola | 1 |
20,447 | 13,925,621,776 | IssuesEvent | 2020-10-21 17:05:53 | OpenXRay/xray-16 | https://api.github.com/repos/OpenXRay/xray-16 | closed | Please don't overwrite trees of external dependencies | Critical Developer Experience Infrastructure | Hi.
We have 730-july-preview packed in NixOS.
The problem is 730-july-preview points to BugTrap at 28c7928927ba05661ecdb2e4ff870dfaed0ac763 but there is no more such commit in BugTrap repository
So we have a hard fail trying to fetch xray-16 730-july-preview with submodules
How this could be fixed? We need to have deterministic hashes, so its a no way for us to always checkout a latest commit of submodule
```
source> Initialized empty Git repository in /nix/store/w6hzm7z8i5k25vmi77clc70zakxbmdj5-source/Externals/BugTrap/.git/
source> remote: Enumerating objects: 42, done.
source> remote: Counting objects: 100% (42/42), done.
source> remote: Compressing objects: 100% (33/33), done.
source> remote: Total 1099 (delta 15), reused 16 (delta 9), pack-reused 1057
source> Receiving objects: 100% (1099/1099), 7.49 MiB | 8.01 MiB/s, done.
source> Resolving deltas: 100% (543/543), done.
source> From https://github.com/OpenXRay/BugTrap
source> * [new branch] master -> origin/master
source> * [new tag] v1.4.2 -> v1.4.2
source> * [new tag] v1.4.3 -> v1.4.3
source> * [new tag] v1.4.4 -> v1.4.4
source> * [new tag] v1.4.5 -> v1.4.5
source> * [new tag] v1.4.6 -> v1.4.6
source> * [new tag] v1.4.7 -> v1.4.7
source> * [new tag] v1.4.8 -> v1.4.8
source> fatal: reference is not a tree: 28c7928927ba05661ecdb2e4ff870dfaed0ac763
source> Unable to checkout 28c7928927ba05661ecdb2e4ff870dfaed0ac763 from https://github.com/OpenXRay/BugTrap.git.
error: --- Error --- nix-daemon
builder for '/nix/store/k6q2c29g3313wj5zszb96kc85c15cgw8-source.drv' failed with exit code 1
error: --- Error ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- nix
error: --- Error --- nix-daemon
1 dependencies of derivation '/nix/store/v72c6sikb3qghz773sna8bxsa7408q9r-OpenXRay-730-july-preview.drv' failed to build
```
https://github.com/NixOS/nixpkgs/pull/101240 | 1.0 | Please don't overwrite trees of external dependencies - Hi.
We have 730-july-preview packed in NixOS.
The problem is 730-july-preview points to BugTrap at 28c7928927ba05661ecdb2e4ff870dfaed0ac763 but there is no more such commit in BugTrap repository
So we have a hard fail trying to fetch xray-16 730-july-preview with submodules
How this could be fixed? We need to have deterministic hashes, so its a no way for us to always checkout a latest commit of submodule
```
source> Initialized empty Git repository in /nix/store/w6hzm7z8i5k25vmi77clc70zakxbmdj5-source/Externals/BugTrap/.git/
source> remote: Enumerating objects: 42, done.
source> remote: Counting objects: 100% (42/42), done.
source> remote: Compressing objects: 100% (33/33), done.
source> remote: Total 1099 (delta 15), reused 16 (delta 9), pack-reused 1057
source> Receiving objects: 100% (1099/1099), 7.49 MiB | 8.01 MiB/s, done.
source> Resolving deltas: 100% (543/543), done.
source> From https://github.com/OpenXRay/BugTrap
source> * [new branch] master -> origin/master
source> * [new tag] v1.4.2 -> v1.4.2
source> * [new tag] v1.4.3 -> v1.4.3
source> * [new tag] v1.4.4 -> v1.4.4
source> * [new tag] v1.4.5 -> v1.4.5
source> * [new tag] v1.4.6 -> v1.4.6
source> * [new tag] v1.4.7 -> v1.4.7
source> * [new tag] v1.4.8 -> v1.4.8
source> fatal: reference is not a tree: 28c7928927ba05661ecdb2e4ff870dfaed0ac763
source> Unable to checkout 28c7928927ba05661ecdb2e4ff870dfaed0ac763 from https://github.com/OpenXRay/BugTrap.git.
error: --- Error --- nix-daemon
builder for '/nix/store/k6q2c29g3313wj5zszb96kc85c15cgw8-source.drv' failed with exit code 1
error: --- Error ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- nix
error: --- Error --- nix-daemon
1 dependencies of derivation '/nix/store/v72c6sikb3qghz773sna8bxsa7408q9r-OpenXRay-730-july-preview.drv' failed to build
```
https://github.com/NixOS/nixpkgs/pull/101240 | infrastructure | please don t overwrite trees of external dependencies hi we have july preview packed in nixos the problem is july preview points to bugtrap at but there is no more such commit in bugtrap repository so we have a hard fail trying to fetch xray july preview with submodules how this could be fixed we need to have deterministic hashes so its a no way for us to always checkout a latest commit of submodule source initialized empty git repository in nix store source externals bugtrap git source remote enumerating objects done source remote counting objects done source remote compressing objects done source remote total delta reused delta pack reused source receiving objects mib mib s done source resolving deltas done source from source master origin master source source source source source source source source fatal reference is not a tree source unable to checkout from error error nix daemon builder for nix store source drv failed with exit code error error nix error error nix daemon dependencies of derivation nix store openxray july preview drv failed to build | 1 |
10,526 | 8,614,975,151 | IssuesEvent | 2018-11-19 19:07:17 | dotnet/roslyn | https://api.github.com/repos/dotnet/roslyn | closed | Can't install Roslyn on dev15.9 | Area-Compilers Area-Infrastructure Contributor Pain | I tried `msbuild /v:m /m Roslyn.sln` and `devenv /rootSuffix RoslynDev` with latest bits from `master` today and VS crashed as soon as I opened a project.
The exception in the crash dump mentioned `System.Memory`.
This means that contributors will not be able to test IDE changes until dev16 preview2 becomes public.
One option would be to temporarily remove this dependency and add it back when we are closer to shipping preview2.
@agocke @jasonmalinowski @jaredpar to advise. | 1.0 | Can't install Roslyn on dev15.9 - I tried `msbuild /v:m /m Roslyn.sln` and `devenv /rootSuffix RoslynDev` with latest bits from `master` today and VS crashed as soon as I opened a project.
The exception in the crash dump mentioned `System.Memory`.
This means that contributors will not be able to test IDE changes until dev16 preview2 becomes public.
One option would be to temporarily remove this dependency and add it back when we are closer to shipping preview2.
@agocke @jasonmalinowski @jaredpar to advise. | infrastructure | can t install roslyn on i tried msbuild v m m roslyn sln and devenv rootsuffix roslyndev with latest bits from master today and vs crashed as soon as i opened a project the exception in the crash dump mentioned system memory this means that contributors will not be able to test ide changes until becomes public one option would be to temporarily remove this dependency and add it back when we are closer to shipping agocke jasonmalinowski jaredpar to advise | 1 |
9,670 | 8,072,296,297 | IssuesEvent | 2018-08-06 15:32:51 | Microsoft/visualfsharp | https://api.github.com/repos/Microsoft/visualfsharp | opened | CI change from Jenkins to public VSTS | Announcements Area-Infrastructure | TL;DR - we've moved from Jenkins to a public VSTS.
What is looks like in GitHub:
<img width="483" alt="screen shot 2018-08-06 at 08 30 09" src="https://user-images.githubusercontent.com/6309070/43726048-f3727d6e-9952-11e8-8fd9-c0310fbd4436.png">
What it looks like when you click Details:
<img width="771" alt="screen shot 2018-08-06 at 08 30 31" src="https://user-images.githubusercontent.com/6309070/43726070-00ca1f76-9953-11e8-9578-a07f95260321.png">
There are no additional modifications; this is our same CI process just being hosted elsewhere. | 1.0 | CI change from Jenkins to public VSTS - TL;DR - we've moved from Jenkins to a public VSTS.
What is looks like in GitHub:
<img width="483" alt="screen shot 2018-08-06 at 08 30 09" src="https://user-images.githubusercontent.com/6309070/43726048-f3727d6e-9952-11e8-8fd9-c0310fbd4436.png">
What it looks like when you click Details:
<img width="771" alt="screen shot 2018-08-06 at 08 30 31" src="https://user-images.githubusercontent.com/6309070/43726070-00ca1f76-9953-11e8-9578-a07f95260321.png">
There are no additional modifications; this is our same CI process just being hosted elsewhere. | infrastructure | ci change from jenkins to public vsts tl dr we ve moved from jenkins to a public vsts what is looks like in github img width alt screen shot at src what it looks like when you click details img width alt screen shot at src there are no additional modifications this is our same ci process just being hosted elsewhere | 1 |
195,079 | 6,902,532,274 | IssuesEvent | 2017-11-25 21:51:54 | CruCentralCoast/CruAndroid | https://api.github.com/repos/CruCentralCoast/CruAndroid | opened | Push Notifications: update info sent to server | Priority: Major Type: Improvement | There have been some changes recently on how the server deals with Push Notifications most notably everywhere that a Firebase token is stored there is now a device type field. In order to guarantee that the notification is in the correct format, the device type needs to be set in the model. The value for Android in the deviceType field is 2. | 1.0 | Push Notifications: update info sent to server - There have been some changes recently on how the server deals with Push Notifications most notably everywhere that a Firebase token is stored there is now a device type field. In order to guarantee that the notification is in the correct format, the device type needs to be set in the model. The value for Android in the deviceType field is 2. | non_infrastructure | push notifications update info sent to server there have been some changes recently on how the server deals with push notifications most notably everywhere that a firebase token is stored there is now a device type field in order to guarantee that the notification is in the correct format the device type needs to be set in the model the value for android in the devicetype field is | 0 |
7,943 | 7,157,119,401 | IssuesEvent | 2018-01-26 18:44:16 | coe-google-apps-support/oct-portal | https://api.github.com/repos/coe-google-apps-support/oct-portal | closed | Enable Continuous Integration on github commits | infrastructure | Right now the build server doesn't automatically start when we check into guthub.
We should have another build definition that just updates the content from the plugins and themes subdirectory defined in github. | 1.0 | Enable Continuous Integration on github commits - Right now the build server doesn't automatically start when we check into guthub.
We should have another build definition that just updates the content from the plugins and themes subdirectory defined in github. | infrastructure | enable continuous integration on github commits right now the build server doesn t automatically start when we check into guthub we should have another build definition that just updates the content from the plugins and themes subdirectory defined in github | 1 |
245,024 | 7,880,737,419 | IssuesEvent | 2018-06-26 16:47:25 | aowen87/FOO | https://api.github.com/repos/aowen87/FOO | closed | add layer nameschemes | Expected Use: 3 - Occasional Impact: 3 - Medium OS: All Priority: Urgent Support Group: Any Target Version: 2.12.0 feature | Need to support Ale3d user's layers namescheme
<pre>
FYI...below is the original proposal for layer nameschems...
And, that appears to be *exactly* what you have defined here..
if (DBPutMultimesh(file, meshName3D, numFileDomains, nullptr,
nullptr, optlist) == -1) {
Warn("WriteRestartMultiMesh", "DBPutMultimesh failed") ;
}
else {
char layerName[256] ;
SNPRINTF(layerName, 256, "%s_layer_namescheme", meshName3D) ;
int len = strlen(problem->parwriteRestart->GetLayerNamescheme())+1 ;
DBWrite(file, layerName, problem->parwriteRestart->GetLayerNamescheme(), &len, 1, DB_CHAR) ;
}
</pre> | 1.0 | add layer nameschemes - Need to support Ale3d user's layers namescheme
<pre>
FYI...below is the original proposal for layer nameschems...
And, that appears to be *exactly* what you have defined here..
if (DBPutMultimesh(file, meshName3D, numFileDomains, nullptr,
nullptr, optlist) == -1) {
Warn("WriteRestartMultiMesh", "DBPutMultimesh failed") ;
}
else {
char layerName[256] ;
SNPRINTF(layerName, 256, "%s_layer_namescheme", meshName3D) ;
int len = strlen(problem->parwriteRestart->GetLayerNamescheme())+1 ;
DBWrite(file, layerName, problem->parwriteRestart->GetLayerNamescheme(), &len, 1, DB_CHAR) ;
}
</pre> | non_infrastructure | add layer nameschemes need to support user s layers namescheme fyi below is the original proposal for layer nameschems and that appears to be exactly what you have defined here if dbputmultimesh file numfiledomains nullptr nullptr optlist warn writerestartmultimesh dbputmultimesh failed else char layername snprintf layername s layer namescheme int len strlen problem parwriterestart getlayernamescheme dbwrite file layername problem parwriterestart getlayernamescheme len db char | 0 |
4,654 | 5,216,841,966 | IssuesEvent | 2017-01-26 11:47:22 | catapult-project/catapult | https://api.github.com/repos/catapult-project/catapult | closed | Catapult roll failing | Infrastructure P1 Telemetry | It's been failing since this roll: https://codereview.chromium.org/2649013003/
Which has this CL:
678cfd33a `nednguyen [Telemetry] Remove labels field from story.Story constructor & labels related flags`
From the [logs](https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/218106/steps/telemetry_perf_unittests%20%28with%20patch%29%20on%20Android/logs/stdio):
```
[302/318] page_sets.story_set_unittest.StorySetUnitTest.testSmoke failed unexpectedly 0.0153s:
Skipping /b/swarm_slave/w/irRCEpcS/tools/perf/page_sets/partial_invalidation_cases.py: no archive data file
Traceback (most recent call last):
File "/b/swarm_slave/w/irRCEpcS/tools/perf/page_sets/story_set_unittest.py", line 23, in testSmoke
self.RunSmokeTest(self.story_sets_dir, self.top_level_dir)
File "/b/swarm_slave/w/irRCEpcS/third_party/catapult/telemetry/telemetry/testing/story_set_smoke_test.py", line 153, in RunSmokeTest
self.CheckAttributes(story_set)
File "/b/swarm_slave/w/irRCEpcS/third_party/catapult/telemetry/telemetry/testing/story_set_smoke_test.py", line 77, in CheckAttributes
self.CheckAttributesOfStoryBasicAttributes(story)
File "/b/swarm_slave/w/irRCEpcS/third_party/catapult/telemetry/telemetry/testing/story_set_smoke_test.py", line 95, in CheckAttributesOfStoryBasicAttributes
isinstance(story.labels, set),
AttributeError: 'PartialInvalidationCasesPage' object has no attribute 'labels'
```
@nedn can you take a look? | 1.0 | Catapult roll failing - It's been failing since this roll: https://codereview.chromium.org/2649013003/
Which has this CL:
678cfd33a `nednguyen [Telemetry] Remove labels field from story.Story constructor & labels related flags`
From the [logs](https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/218106/steps/telemetry_perf_unittests%20%28with%20patch%29%20on%20Android/logs/stdio):
```
[302/318] page_sets.story_set_unittest.StorySetUnitTest.testSmoke failed unexpectedly 0.0153s:
Skipping /b/swarm_slave/w/irRCEpcS/tools/perf/page_sets/partial_invalidation_cases.py: no archive data file
Traceback (most recent call last):
File "/b/swarm_slave/w/irRCEpcS/tools/perf/page_sets/story_set_unittest.py", line 23, in testSmoke
self.RunSmokeTest(self.story_sets_dir, self.top_level_dir)
File "/b/swarm_slave/w/irRCEpcS/third_party/catapult/telemetry/telemetry/testing/story_set_smoke_test.py", line 153, in RunSmokeTest
self.CheckAttributes(story_set)
File "/b/swarm_slave/w/irRCEpcS/third_party/catapult/telemetry/telemetry/testing/story_set_smoke_test.py", line 77, in CheckAttributes
self.CheckAttributesOfStoryBasicAttributes(story)
File "/b/swarm_slave/w/irRCEpcS/third_party/catapult/telemetry/telemetry/testing/story_set_smoke_test.py", line 95, in CheckAttributesOfStoryBasicAttributes
isinstance(story.labels, set),
AttributeError: 'PartialInvalidationCasesPage' object has no attribute 'labels'
```
@nedn can you take a look? | infrastructure | catapult roll failing it s been failing since this roll which has this cl nednguyen remove labels field from story story constructor labels related flags from the page sets story set unittest storysetunittest testsmoke failed unexpectedly skipping b swarm slave w irrcepcs tools perf page sets partial invalidation cases py no archive data file traceback most recent call last file b swarm slave w irrcepcs tools perf page sets story set unittest py line in testsmoke self runsmoketest self story sets dir self top level dir file b swarm slave w irrcepcs third party catapult telemetry telemetry testing story set smoke test py line in runsmoketest self checkattributes story set file b swarm slave w irrcepcs third party catapult telemetry telemetry testing story set smoke test py line in checkattributes self checkattributesofstorybasicattributes story file b swarm slave w irrcepcs third party catapult telemetry telemetry testing story set smoke test py line in checkattributesofstorybasicattributes isinstance story labels set attributeerror partialinvalidationcasespage object has no attribute labels nedn can you take a look | 1 |
92,187 | 15,856,889,822 | IssuesEvent | 2021-04-08 03:25:46 | sandrinesuire/project_10_10 | https://api.github.com/repos/sandrinesuire/project_10_10 | opened | CVE-2020-9402 (High) detected in Django-3.0.tar.gz, Django-2.2.4.tar.gz | security vulnerability | ## CVE-2020-9402 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>Django-3.0.tar.gz</b>, <b>Django-2.2.4.tar.gz</b></p></summary>
<p>
<details><summary><b>Django-3.0.tar.gz</b></p></summary>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/f8/46/b3b8c61f867827fff2305db40659495dcd64fb35c399e75c53f23c113871/Django-3.0.tar.gz">https://files.pythonhosted.org/packages/f8/46/b3b8c61f867827fff2305db40659495dcd64fb35c399e75c53f23c113871/Django-3.0.tar.gz</a></p>
<p>Path to dependency file: /tmp/ws-scm/project_11/requirements.txt</p>
<p>Path to vulnerable library: /project_11/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.0.tar.gz** (Vulnerable Library)
</details>
<details><summary><b>Django-2.2.4.tar.gz</b></p></summary>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/19/11/3449a2071df9427e7a5c4dddee2462e88840dd968a9b0c161097154fcb0c/Django-2.2.4.tar.gz">https://files.pythonhosted.org/packages/19/11/3449a2071df9427e7a5c4dddee2462e88840dd968a9b0c161097154fcb0c/Django-2.2.4.tar.gz</a></p>
<p>Path to dependency file: /tmp/ws-scm/project_11/requirements.txt</p>
<p>Path to vulnerable library: /project_11/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-2.2.4.tar.gz** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Django 1.11 before 1.11.29, 2.2 before 2.2.11, and 3.0 before 3.0.4 allows SQL Injection if untrusted data is used as a tolerance parameter in GIS functions and aggregates on Oracle. By passing a suitably crafted tolerance to GIS functions and aggregates on Oracle, it was possible to break escaping and inject malicious SQL.
<p>Publish Date: 2020-03-05
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9402>CVE-2020-9402</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: 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-2020-9402">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9402</a></p>
<p>Release Date: 2020-03-05</p>
<p>Fix Resolution: 1.11.29,2.2.11,3.0.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-9402 (High) detected in Django-3.0.tar.gz, Django-2.2.4.tar.gz - ## CVE-2020-9402 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>Django-3.0.tar.gz</b>, <b>Django-2.2.4.tar.gz</b></p></summary>
<p>
<details><summary><b>Django-3.0.tar.gz</b></p></summary>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/f8/46/b3b8c61f867827fff2305db40659495dcd64fb35c399e75c53f23c113871/Django-3.0.tar.gz">https://files.pythonhosted.org/packages/f8/46/b3b8c61f867827fff2305db40659495dcd64fb35c399e75c53f23c113871/Django-3.0.tar.gz</a></p>
<p>Path to dependency file: /tmp/ws-scm/project_11/requirements.txt</p>
<p>Path to vulnerable library: /project_11/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-3.0.tar.gz** (Vulnerable Library)
</details>
<details><summary><b>Django-2.2.4.tar.gz</b></p></summary>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/19/11/3449a2071df9427e7a5c4dddee2462e88840dd968a9b0c161097154fcb0c/Django-2.2.4.tar.gz">https://files.pythonhosted.org/packages/19/11/3449a2071df9427e7a5c4dddee2462e88840dd968a9b0c161097154fcb0c/Django-2.2.4.tar.gz</a></p>
<p>Path to dependency file: /tmp/ws-scm/project_11/requirements.txt</p>
<p>Path to vulnerable library: /project_11/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-2.2.4.tar.gz** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Django 1.11 before 1.11.29, 2.2 before 2.2.11, and 3.0 before 3.0.4 allows SQL Injection if untrusted data is used as a tolerance parameter in GIS functions and aggregates on Oracle. By passing a suitably crafted tolerance to GIS functions and aggregates on Oracle, it was possible to break escaping and inject malicious SQL.
<p>Publish Date: 2020-03-05
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9402>CVE-2020-9402</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: 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-2020-9402">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9402</a></p>
<p>Release Date: 2020-03-05</p>
<p>Fix Resolution: 1.11.29,2.2.11,3.0.4</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 django tar gz django tar gz cve high severity vulnerability vulnerable libraries django tar gz django tar gz django tar gz a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file tmp ws scm project requirements txt path to vulnerable library project requirements txt dependency hierarchy x django tar gz vulnerable library django tar gz a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file tmp ws scm project requirements txt path to vulnerable library project requirements txt dependency hierarchy x django tar gz vulnerable library vulnerability details django before before and before allows sql injection if untrusted data is used as a tolerance parameter in gis functions and aggregates on oracle by passing a suitably crafted tolerance to gis functions and aggregates on oracle it was possible to break escaping and inject malicious sql publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
5,983 | 6,087,378,374 | IssuesEvent | 2017-06-18 12:26:58 | Nivenly/genderidentity.io | https://api.github.com/repos/Nivenly/genderidentity.io | opened | Build Pipeline | Infrastructure | We need to construct a build pipeline! (Hooray!)
This is merely a set of automation scripts that do the following things. Ideally the scripts will be ran from a tool like Jenkins, so we as administrators have convenient buttons to use to run them. But in theory they can be ran anywhere.
### Stories
- As an administrator for genderidentity.io I can automatically build our application.
- As an administrator for genderidentity.io I can automatically deploy our application to Kubernetes.
### Success Criteria
##### Process
- Propose tooling for the pipeline (and get it accepted/agreed upon)
- Build on infrastructure for the tooling (Ask @kris-nova for infra here)
##### Tooling
- The application hosted in this repository is built, and containerized.
- The container is ONLY built after the tests are ran for the application.
- The tested container image is pushed up to a docker registry.
- The image can be pulled from the registry and deployed in Kubernetes.
| 1.0 | Build Pipeline - We need to construct a build pipeline! (Hooray!)
This is merely a set of automation scripts that do the following things. Ideally the scripts will be ran from a tool like Jenkins, so we as administrators have convenient buttons to use to run them. But in theory they can be ran anywhere.
### Stories
- As an administrator for genderidentity.io I can automatically build our application.
- As an administrator for genderidentity.io I can automatically deploy our application to Kubernetes.
### Success Criteria
##### Process
- Propose tooling for the pipeline (and get it accepted/agreed upon)
- Build on infrastructure for the tooling (Ask @kris-nova for infra here)
##### Tooling
- The application hosted in this repository is built, and containerized.
- The container is ONLY built after the tests are ran for the application.
- The tested container image is pushed up to a docker registry.
- The image can be pulled from the registry and deployed in Kubernetes.
| infrastructure | build pipeline we need to construct a build pipeline hooray this is merely a set of automation scripts that do the following things ideally the scripts will be ran from a tool like jenkins so we as administrators have convenient buttons to use to run them but in theory they can be ran anywhere stories as an administrator for genderidentity io i can automatically build our application as an administrator for genderidentity io i can automatically deploy our application to kubernetes success criteria process propose tooling for the pipeline and get it accepted agreed upon build on infrastructure for the tooling ask kris nova for infra here tooling the application hosted in this repository is built and containerized the container is only built after the tests are ran for the application the tested container image is pushed up to a docker registry the image can be pulled from the registry and deployed in kubernetes | 1 |
38,274 | 10,164,361,485 | IssuesEvent | 2019-08-07 11:29:20 | syndesisio/syndesis | https://api.github.com/repos/syndesisio/syndesis | closed | syndesis command line tool ignores --project parameter | cat/bug cat/build prio/p2 | ## This is a...
<pre><code>
[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[X] Bug report <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Documentation issue or request
</code></pre>
## Description
`syndesis` command line tool ignores `--project` parameter and always installs Syndesis in the `myproject` project.
## Output
```
$ syndesis minishift --install -p syndesis
Creating project syndesis
Now using project "myproject" from context named "syndesis" on server "https://192.168.42.58:8443".
Switching to project "syndesis"
Already on project "myproject" on server "https://192.168.42.58:8443".
Installing Syndesis CRD
cluster role "syndesis-extra-permissions" added: "developer"
Deploying Syndesis operator
Switching to project "syndesis"
Login successful.
You have access to the following projects and can switch between them with 'oc project <projectname>':
application-monitoring
default
kube-dns
kube-proxy
kube-public
kube-system
* myproject
openshift
openshift-apiserver
openshift-controller-manager
openshift-core-operators
openshift-infra
openshift-node
openshift-service-cert-signer
openshift-web-console
syndesis
Using project "myproject".
Waiting for syndesis-operator to be scaled to 1
Sleeping 10s ...
NAME READY STATUS RESTARTS AGE
syndesis-operator-1-deploy 0/1 Pending 0 0s
syndesis-operator-1-deploy 0/1 Pending 0 0s
syndesis-operator-1-deploy 0/1 ContainerCreating 0 1s
syndesis-operator-1-c9z4r 0/1 Pending 0 0s
syndesis-operator-1-c9z4r 0/1 Pending 0 0s
syndesis-operator-1-c9z4r 0/1 ContainerCreating 0 0s
syndesis-operator-1-deploy 1/1 Running 0 4s
Sleeping 10s ...
Sleeping 10s ...
Sleeping 10s ...
Sleeping 10s ...
``` | 1.0 | syndesis command line tool ignores --project parameter - ## This is a...
<pre><code>
[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[X] Bug report <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Documentation issue or request
</code></pre>
## Description
`syndesis` command line tool ignores `--project` parameter and always installs Syndesis in the `myproject` project.
## Output
```
$ syndesis minishift --install -p syndesis
Creating project syndesis
Now using project "myproject" from context named "syndesis" on server "https://192.168.42.58:8443".
Switching to project "syndesis"
Already on project "myproject" on server "https://192.168.42.58:8443".
Installing Syndesis CRD
cluster role "syndesis-extra-permissions" added: "developer"
Deploying Syndesis operator
Switching to project "syndesis"
Login successful.
You have access to the following projects and can switch between them with 'oc project <projectname>':
application-monitoring
default
kube-dns
kube-proxy
kube-public
kube-system
* myproject
openshift
openshift-apiserver
openshift-controller-manager
openshift-core-operators
openshift-infra
openshift-node
openshift-service-cert-signer
openshift-web-console
syndesis
Using project "myproject".
Waiting for syndesis-operator to be scaled to 1
Sleeping 10s ...
NAME READY STATUS RESTARTS AGE
syndesis-operator-1-deploy 0/1 Pending 0 0s
syndesis-operator-1-deploy 0/1 Pending 0 0s
syndesis-operator-1-deploy 0/1 ContainerCreating 0 1s
syndesis-operator-1-c9z4r 0/1 Pending 0 0s
syndesis-operator-1-c9z4r 0/1 Pending 0 0s
syndesis-operator-1-c9z4r 0/1 ContainerCreating 0 0s
syndesis-operator-1-deploy 1/1 Running 0 4s
Sleeping 10s ...
Sleeping 10s ...
Sleeping 10s ...
Sleeping 10s ...
``` | non_infrastructure | syndesis command line tool ignores project parameter this is a feature request regression a behavior that used to work and stopped working in a new release bug report documentation issue or request description syndesis command line tool ignores project parameter and always installs syndesis in the myproject project output syndesis minishift install p syndesis creating project syndesis now using project myproject from context named syndesis on server switching to project syndesis already on project myproject on server installing syndesis crd cluster role syndesis extra permissions added developer deploying syndesis operator switching to project syndesis login successful you have access to the following projects and can switch between them with oc project application monitoring default kube dns kube proxy kube public kube system myproject openshift openshift apiserver openshift controller manager openshift core operators openshift infra openshift node openshift service cert signer openshift web console syndesis using project myproject waiting for syndesis operator to be scaled to sleeping name ready status restarts age syndesis operator deploy pending syndesis operator deploy pending syndesis operator deploy containercreating syndesis operator pending syndesis operator pending syndesis operator containercreating syndesis operator deploy running sleeping sleeping sleeping sleeping | 0 |
263,550 | 8,292,399,455 | IssuesEvent | 2018-09-20 00:35:50 | minetest/minetest | https://api.github.com/repos/minetest/minetest | closed | Pick up 10 items at a time with middle click. | Feature request Low priority Possible close | I would like to add a feature in (not creative menu) the inventory: giving for example bread by middle-click mouse button to get 10 per middle-click, quicker than 1 item per left-click/right-click. | 1.0 | Pick up 10 items at a time with middle click. - I would like to add a feature in (not creative menu) the inventory: giving for example bread by middle-click mouse button to get 10 per middle-click, quicker than 1 item per left-click/right-click. | non_infrastructure | pick up items at a time with middle click i would like to add a feature in not creative menu the inventory giving for example bread by middle click mouse button to get per middle click quicker than item per left click right click | 0 |
121,495 | 12,127,507,324 | IssuesEvent | 2020-04-22 18:50:54 | vmware-tanzu/velero | https://api.github.com/repos/vmware-tanzu/velero | closed | Velero site missing vSphere installation and configuration instructions | Documentation | **Describe the problem/challenge you have**
The Velero website site doesn't include installation and configuration instructions for the vShpere provider
**Describe the solution you'd like**
A link in the provider page to install and configuration instructions for vSphere
**Anything else you would like to add:**
Referencing the latest Velero page here
https://velero.io/docs/v1.3.1/supported-providers/
**Environment:**
N/A
- Velero version (use `velero version`):
- Kubernetes version (use `kubectl version`):
- Kubernetes installer & version:
- Cloud provider or hardware configuration:
- OS (e.g. from `/etc/os-release`):
| 1.0 | Velero site missing vSphere installation and configuration instructions - **Describe the problem/challenge you have**
The Velero website site doesn't include installation and configuration instructions for the vShpere provider
**Describe the solution you'd like**
A link in the provider page to install and configuration instructions for vSphere
**Anything else you would like to add:**
Referencing the latest Velero page here
https://velero.io/docs/v1.3.1/supported-providers/
**Environment:**
N/A
- Velero version (use `velero version`):
- Kubernetes version (use `kubectl version`):
- Kubernetes installer & version:
- Cloud provider or hardware configuration:
- OS (e.g. from `/etc/os-release`):
| non_infrastructure | velero site missing vsphere installation and configuration instructions describe the problem challenge you have the velero website site doesn t include installation and configuration instructions for the vshpere provider describe the solution you d like a link in the provider page to install and configuration instructions for vsphere anything else you would like to add referencing the latest velero page here environment n a velero version use velero version kubernetes version use kubectl version kubernetes installer version cloud provider or hardware configuration os e g from etc os release | 0 |
8,020 | 7,189,554,285 | IssuesEvent | 2018-02-02 14:26:38 | twosigma/beakerx | https://api.github.com/repos/twosigma/beakerx | opened | uninstall should not fail on missing kernel | Bug Infrastructure | if a user has uninstalled a kernel, then they uninstall all over beakerx, the uninstall process fails and is left incomplete.
during "beakerx uninstall" it should ignore errors. | 1.0 | uninstall should not fail on missing kernel - if a user has uninstalled a kernel, then they uninstall all over beakerx, the uninstall process fails and is left incomplete.
during "beakerx uninstall" it should ignore errors. | infrastructure | uninstall should not fail on missing kernel if a user has uninstalled a kernel then they uninstall all over beakerx the uninstall process fails and is left incomplete during beakerx uninstall it should ignore errors | 1 |
6,384 | 9,449,377,661 | IssuesEvent | 2019-04-16 01:37:56 | googleapis/google-auth-library-nodejs | https://api.github.com/repos/googleapis/google-auth-library-nodejs | closed | Add a test to cover #605 | type: process | There's a PR over in #605 to fix a bug with not throwing on refreshAccessToken when no refresh_token is set. We... should have a test to cover that. | 1.0 | Add a test to cover #605 - There's a PR over in #605 to fix a bug with not throwing on refreshAccessToken when no refresh_token is set. We... should have a test to cover that. | non_infrastructure | add a test to cover there s a pr over in to fix a bug with not throwing on refreshaccesstoken when no refresh token is set we should have a test to cover that | 0 |
93,682 | 10,773,165,313 | IssuesEvent | 2019-11-02 18:59:52 | sinonjs/sinon | https://api.github.com/repos/sinonjs/sinon | closed | Incomplete and incorrect sandbox documentation | Difficulty: Easy Documentation Help wanted good first issue pinned | When researching sinonjs/sinon-test#57 I found that the [documentation for sandboxes](http://sinonjs.org/releases/v2.3.1/sandbox/) was incomplete and somewhat misleading.
## Issues found
### Incorrect default config
It says the sandbox is configured with the following config per default, which is incorrect:
```javascript
sinon.defaultConfig = {
// ...
injectInto: null,
properties: ["spy", "stub", "mock", "clock", "server", "requests"],
useFakeTimers: true,
useFakeServer: true
}
```
I do not think there is something called `sinon.defaultConfig` and a quick test will show that there is no server configured per default:
```javascript
var sandbox = sinonSandbox.create();
console.log(sandbox.server) // => undefined
```
### References removed fields
`sinon.defaultConfig` was removed in Sinon 2. Is still used in the docs.
### Incomplete list of properties
There is no list of properties one can expose on the sandbox, but a list is given:
```javascript
properties: ["spy", "stub", "mock", "clock", "server", "requests"]
```
One important field that is missing is `sandbox` which will expose the actual sandbox object, along with all of its methods. This is for instance useful when using `sinon-test` and you want to invoke `sandbox.reset()`.
### No example of how to use `inject()` or the config `injectInto`
The code and [set of tests](https://github.com/sinonjs/sinon/blob/c89fb21b00cd4f3d99fdeb48d2c5193f96d5e9fb/test/sandbox-test.js#L258) were pretty useful. No other examples exist in the docs. Not even mention of `inject()`
### Incomplete API description
`inject()` is missing from the docs
* Sinon version : 2.3.1 | 1.0 | Incomplete and incorrect sandbox documentation - When researching sinonjs/sinon-test#57 I found that the [documentation for sandboxes](http://sinonjs.org/releases/v2.3.1/sandbox/) was incomplete and somewhat misleading.
## Issues found
### Incorrect default config
It says the sandbox is configured with the following config per default, which is incorrect:
```javascript
sinon.defaultConfig = {
// ...
injectInto: null,
properties: ["spy", "stub", "mock", "clock", "server", "requests"],
useFakeTimers: true,
useFakeServer: true
}
```
I do not think there is something called `sinon.defaultConfig` and a quick test will show that there is no server configured per default:
```javascript
var sandbox = sinonSandbox.create();
console.log(sandbox.server) // => undefined
```
### References removed fields
`sinon.defaultConfig` was removed in Sinon 2. Is still used in the docs.
### Incomplete list of properties
There is no list of properties one can expose on the sandbox, but a list is given:
```javascript
properties: ["spy", "stub", "mock", "clock", "server", "requests"]
```
One important field that is missing is `sandbox` which will expose the actual sandbox object, along with all of its methods. This is for instance useful when using `sinon-test` and you want to invoke `sandbox.reset()`.
### No example of how to use `inject()` or the config `injectInto`
The code and [set of tests](https://github.com/sinonjs/sinon/blob/c89fb21b00cd4f3d99fdeb48d2c5193f96d5e9fb/test/sandbox-test.js#L258) were pretty useful. No other examples exist in the docs. Not even mention of `inject()`
### Incomplete API description
`inject()` is missing from the docs
* Sinon version : 2.3.1 | non_infrastructure | incomplete and incorrect sandbox documentation when researching sinonjs sinon test i found that the was incomplete and somewhat misleading issues found incorrect default config it says the sandbox is configured with the following config per default which is incorrect javascript sinon defaultconfig injectinto null properties usefaketimers true usefakeserver true i do not think there is something called sinon defaultconfig and a quick test will show that there is no server configured per default javascript var sandbox sinonsandbox create console log sandbox server undefined references removed fields sinon defaultconfig was removed in sinon is still used in the docs incomplete list of properties there is no list of properties one can expose on the sandbox but a list is given javascript properties one important field that is missing is sandbox which will expose the actual sandbox object along with all of its methods this is for instance useful when using sinon test and you want to invoke sandbox reset no example of how to use inject or the config injectinto the code and were pretty useful no other examples exist in the docs not even mention of inject incomplete api description inject is missing from the docs sinon version | 0 |
24,870 | 7,574,754,717 | IssuesEvent | 2018-04-23 22:06:34 | envoyproxy/envoy | https://api.github.com/repos/envoyproxy/envoy | closed | `envoy --version` reports old git SHA | bug build | *Title*: `envoy --version` reports old git SHA
*Description*:
Re-linking envoy binary no longer updates the git SHA linkstamp shown by `envoy --version`. This may be due to a change in bazel 0.10.0, from the release notes, under *Important changes*:
"- Linkstamping is now a separate and full-blown CppCompileAction,
it's no longer a part of linking command."
*Repro steps*:
```
$ bazel build //source/exe:envoy-static
$ bazel-bin/source/exe/envoy-static --version
bazel-bin/source/exe/envoy-static version: 97b69ce6a507471180c0585b6742c627962b433b/1.6.0-dev/Clean/DEBUG
$ touch empty-file
$ git add empty-file
$ git commit -a -m "testing."
$ git log --pretty=oneline
35931e6a89f38fe8ad3334e1d13bf056e2464f4d testing.
97b69ce6a507471180c0585b6742c627962b433b test: automatically registering integration ports from listener names (#2536)
...
$ rm bazel-bin/source/exe/envoy-static
$ bazel build //source/exe:envoy-static
$ bazel-bin/source/exe/envoy-static --version
bazel-bin/source/exe/envoy-static version: 97b69ce6a507471180c0585b6742c627962b433b/1.6.0-dev/Clean/DEBUG
```
Note that the version was not updated even though the binary was relinked.
| 1.0 | `envoy --version` reports old git SHA - *Title*: `envoy --version` reports old git SHA
*Description*:
Re-linking envoy binary no longer updates the git SHA linkstamp shown by `envoy --version`. This may be due to a change in bazel 0.10.0, from the release notes, under *Important changes*:
"- Linkstamping is now a separate and full-blown CppCompileAction,
it's no longer a part of linking command."
*Repro steps*:
```
$ bazel build //source/exe:envoy-static
$ bazel-bin/source/exe/envoy-static --version
bazel-bin/source/exe/envoy-static version: 97b69ce6a507471180c0585b6742c627962b433b/1.6.0-dev/Clean/DEBUG
$ touch empty-file
$ git add empty-file
$ git commit -a -m "testing."
$ git log --pretty=oneline
35931e6a89f38fe8ad3334e1d13bf056e2464f4d testing.
97b69ce6a507471180c0585b6742c627962b433b test: automatically registering integration ports from listener names (#2536)
...
$ rm bazel-bin/source/exe/envoy-static
$ bazel build //source/exe:envoy-static
$ bazel-bin/source/exe/envoy-static --version
bazel-bin/source/exe/envoy-static version: 97b69ce6a507471180c0585b6742c627962b433b/1.6.0-dev/Clean/DEBUG
```
Note that the version was not updated even though the binary was relinked.
| non_infrastructure | envoy version reports old git sha title envoy version reports old git sha description re linking envoy binary no longer updates the git sha linkstamp shown by envoy version this may be due to a change in bazel from the release notes under important changes linkstamping is now a separate and full blown cppcompileaction it s no longer a part of linking command repro steps bazel build source exe envoy static bazel bin source exe envoy static version bazel bin source exe envoy static version dev clean debug touch empty file git add empty file git commit a m testing git log pretty oneline testing test automatically registering integration ports from listener names rm bazel bin source exe envoy static bazel build source exe envoy static bazel bin source exe envoy static version bazel bin source exe envoy static version dev clean debug note that the version was not updated even though the binary was relinked | 0 |
439,736 | 30,711,736,804 | IssuesEvent | 2023-07-27 10:15:20 | risingwavelabs/risingwave-docs | https://api.github.com/repos/risingwavelabs/risingwave-docs | closed | Document `pg_shadow` | documentation | ### Related code PR
https://github.com/risingwavelabs/risingwave/pull/10860
### Which part(s) of the docs might be affected or should be updated? And how?
Add `pg_shadow` to PostgreSQL catalogs.
### Reference
https://www.postgresql.org/docs/current/view-pg-shadow.html | 1.0 | Document `pg_shadow` - ### Related code PR
https://github.com/risingwavelabs/risingwave/pull/10860
### Which part(s) of the docs might be affected or should be updated? And how?
Add `pg_shadow` to PostgreSQL catalogs.
### Reference
https://www.postgresql.org/docs/current/view-pg-shadow.html | non_infrastructure | document pg shadow related code pr which part s of the docs might be affected or should be updated and how add pg shadow to postgresql catalogs reference | 0 |
29,703 | 4,534,115,284 | IssuesEvent | 2016-09-08 13:48:39 | networkcube/networkcube | https://api.github.com/repos/networkcube/networkcube | closed | [VIST] Add Sample Data to Vistorian Site | enhancement test | <a href="https://github.com/RickGMSR"><img src="https://avatars.githubusercontent.com/u/15837908?v=3" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [RickGMSR](https://github.com/RickGMSR)**
_Tuesday Feb 02, 2016 at 16:56 GMT_
_Originally opened as https://github.com/nathalieriche/networkcube-dev/issues/52_
----
Currently Vistorian Site does not have a sample data. Would be nice to have something like the ConnectToScope Site where sample data is already provided.
| 1.0 | [VIST] Add Sample Data to Vistorian Site - <a href="https://github.com/RickGMSR"><img src="https://avatars.githubusercontent.com/u/15837908?v=3" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [RickGMSR](https://github.com/RickGMSR)**
_Tuesday Feb 02, 2016 at 16:56 GMT_
_Originally opened as https://github.com/nathalieriche/networkcube-dev/issues/52_
----
Currently Vistorian Site does not have a sample data. Would be nice to have something like the ConnectToScope Site where sample data is already provided.
| non_infrastructure | add sample data to vistorian site issue by tuesday feb at gmt originally opened as currently vistorian site does not have a sample data would be nice to have something like the connecttoscope site where sample data is already provided | 0 |
12,855 | 9,982,005,900 | IssuesEvent | 2019-07-10 08:52:52 | ReliSA/CRCE | https://api.github.com/repos/ReliSA/CRCE | closed | merge "rpesek" into "dev" | infrastructure | Review the new module, the whole CRCE functionality on "ghessova" branch, cleanup, merge into "dev".
### See also: #22 | 1.0 | merge "rpesek" into "dev" - Review the new module, the whole CRCE functionality on "ghessova" branch, cleanup, merge into "dev".
### See also: #22 | infrastructure | merge rpesek into dev review the new module the whole crce functionality on ghessova branch cleanup merge into dev see also | 1 |
116,000 | 17,355,563,971 | IssuesEvent | 2021-07-29 14:03:01 | KaterinaOrg/notary | https://api.github.com/repos/KaterinaOrg/notary | opened | CVE-2018-1098 (High) detected in multiple libraries | security vulnerability | ## CVE-2018-1098 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>github.com/etcd-io/etcd-v3.1.20</b>, <b>github.com/etcd-io/etcd/pkg/httputil-v3.1.20</b>, <b>github.com/etcd-io/etcd-v3.3.25</b></p></summary>
<p>
<details><summary><b>github.com/etcd-io/etcd-v3.1.20</b></p></summary>
<p>Distributed reliable key-value store for the most critical data of a distributed system</p>
<p>
Dependency Hierarchy:
- github.com/google/certificate-transparency-go-v1.1.1 (Root Library)
- github.com/etcd-io/etcd-v3.3.25
- :x: **github.com/etcd-io/etcd-v3.1.20** (Vulnerable Library)
</details>
<details><summary><b>github.com/etcd-io/etcd/pkg/httputil-v3.1.20</b></p></summary>
<p>Distributed reliable key-value store for the most critical data of a distributed system</p>
<p>
Dependency Hierarchy:
- github.com/google/certificate-transparency-go-v1.1.1 (Root Library)
- github.com/etcd-io/etcd-v3.3.25
- github.com/etcd-io/etcd-v3.1.20
- github.com/etcd-io/etcd/etcdserver-v3.1.20
- github.com/etcd-io/etcd/lease/leasehttp-v3.1.20
- github.com/etcd-io/etcd/lease-v3.1.20
- :x: **github.com/etcd-io/etcd/pkg/httputil-v3.1.20** (Vulnerable Library)
</details>
<details><summary><b>github.com/etcd-io/etcd-v3.3.25</b></p></summary>
<p>Distributed reliable key-value store for the most critical data of a distributed system</p>
<p>
Dependency Hierarchy:
- github.com/google/certificate-transparency-go-v1.1.1 (Root Library)
- :x: **github.com/etcd-io/etcd-v3.3.25** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/KaterinaOrg/notary/commit/549c2321b216d811654d8e364e811dbca812a5a6">549c2321b216d811654d8e364e811dbca812a5a6</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>
A cross-site request forgery flaw was found in etcd 3.3.1 and earlier. An attacker can set up a website that tries to send a POST request to the etcd server and modify a key. Adding a key is done with PUT so it is theoretically safe (can't PUT from an HTML form or such) but POST allows creating in-order keys that an attacker can send.
<p>Publish Date: 2018-04-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1098>CVE-2018-1098</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: 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="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1098">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1098</a></p>
<p>Release Date: 2018-04-03</p>
<p>Fix Resolution: v3.4.0-rc.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"GO","packageName":"github.com/etcd-io/etcd","packageVersion":"v3.1.20","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"github.com/google/certificate-transparency-go:v1.1.1;github.com/etcd-io/etcd:v3.3.25;github.com/etcd-io/etcd:v3.1.20","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v3.4.0-rc.0"},{"packageType":"GO","packageName":"github.com/etcd-io/etcd/pkg/httputil","packageVersion":"v3.1.20","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"github.com/google/certificate-transparency-go:v1.1.1;github.com/etcd-io/etcd:v3.3.25;github.com/etcd-io/etcd:v3.1.20;github.com/etcd-io/etcd/etcdserver:v3.1.20;github.com/etcd-io/etcd/lease/leasehttp:v3.1.20;github.com/etcd-io/etcd/lease:v3.1.20;github.com/etcd-io/etcd/pkg/httputil:v3.1.20","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v3.4.0-rc.0"},{"packageType":"GO","packageName":"github.com/etcd-io/etcd","packageVersion":"v3.3.25","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"github.com/google/certificate-transparency-go:v1.1.1;github.com/etcd-io/etcd:v3.3.25","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v3.4.0-rc.0"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-1098","vulnerabilityDetails":"A cross-site request forgery flaw was found in etcd 3.3.1 and earlier. An attacker can set up a website that tries to send a POST request to the etcd server and modify a key. Adding a key is done with PUT so it is theoretically safe (can\u0027t PUT from an HTML form or such) but POST allows creating in-order keys that an attacker can send.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1098","cvss3Severity":"high","cvss3Score":"8.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2018-1098 (High) detected in multiple libraries - ## CVE-2018-1098 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>github.com/etcd-io/etcd-v3.1.20</b>, <b>github.com/etcd-io/etcd/pkg/httputil-v3.1.20</b>, <b>github.com/etcd-io/etcd-v3.3.25</b></p></summary>
<p>
<details><summary><b>github.com/etcd-io/etcd-v3.1.20</b></p></summary>
<p>Distributed reliable key-value store for the most critical data of a distributed system</p>
<p>
Dependency Hierarchy:
- github.com/google/certificate-transparency-go-v1.1.1 (Root Library)
- github.com/etcd-io/etcd-v3.3.25
- :x: **github.com/etcd-io/etcd-v3.1.20** (Vulnerable Library)
</details>
<details><summary><b>github.com/etcd-io/etcd/pkg/httputil-v3.1.20</b></p></summary>
<p>Distributed reliable key-value store for the most critical data of a distributed system</p>
<p>
Dependency Hierarchy:
- github.com/google/certificate-transparency-go-v1.1.1 (Root Library)
- github.com/etcd-io/etcd-v3.3.25
- github.com/etcd-io/etcd-v3.1.20
- github.com/etcd-io/etcd/etcdserver-v3.1.20
- github.com/etcd-io/etcd/lease/leasehttp-v3.1.20
- github.com/etcd-io/etcd/lease-v3.1.20
- :x: **github.com/etcd-io/etcd/pkg/httputil-v3.1.20** (Vulnerable Library)
</details>
<details><summary><b>github.com/etcd-io/etcd-v3.3.25</b></p></summary>
<p>Distributed reliable key-value store for the most critical data of a distributed system</p>
<p>
Dependency Hierarchy:
- github.com/google/certificate-transparency-go-v1.1.1 (Root Library)
- :x: **github.com/etcd-io/etcd-v3.3.25** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/KaterinaOrg/notary/commit/549c2321b216d811654d8e364e811dbca812a5a6">549c2321b216d811654d8e364e811dbca812a5a6</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>
A cross-site request forgery flaw was found in etcd 3.3.1 and earlier. An attacker can set up a website that tries to send a POST request to the etcd server and modify a key. Adding a key is done with PUT so it is theoretically safe (can't PUT from an HTML form or such) but POST allows creating in-order keys that an attacker can send.
<p>Publish Date: 2018-04-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1098>CVE-2018-1098</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: 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="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1098">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1098</a></p>
<p>Release Date: 2018-04-03</p>
<p>Fix Resolution: v3.4.0-rc.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"GO","packageName":"github.com/etcd-io/etcd","packageVersion":"v3.1.20","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"github.com/google/certificate-transparency-go:v1.1.1;github.com/etcd-io/etcd:v3.3.25;github.com/etcd-io/etcd:v3.1.20","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v3.4.0-rc.0"},{"packageType":"GO","packageName":"github.com/etcd-io/etcd/pkg/httputil","packageVersion":"v3.1.20","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"github.com/google/certificate-transparency-go:v1.1.1;github.com/etcd-io/etcd:v3.3.25;github.com/etcd-io/etcd:v3.1.20;github.com/etcd-io/etcd/etcdserver:v3.1.20;github.com/etcd-io/etcd/lease/leasehttp:v3.1.20;github.com/etcd-io/etcd/lease:v3.1.20;github.com/etcd-io/etcd/pkg/httputil:v3.1.20","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v3.4.0-rc.0"},{"packageType":"GO","packageName":"github.com/etcd-io/etcd","packageVersion":"v3.3.25","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"github.com/google/certificate-transparency-go:v1.1.1;github.com/etcd-io/etcd:v3.3.25","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v3.4.0-rc.0"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-1098","vulnerabilityDetails":"A cross-site request forgery flaw was found in etcd 3.3.1 and earlier. An attacker can set up a website that tries to send a POST request to the etcd server and modify a key. Adding a key is done with PUT so it is theoretically safe (can\u0027t PUT from an HTML form or such) but POST allows creating in-order keys that an attacker can send.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1098","cvss3Severity":"high","cvss3Score":"8.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_infrastructure | cve high detected in multiple libraries cve high severity vulnerability vulnerable libraries github com etcd io etcd github com etcd io etcd pkg httputil github com etcd io etcd github com etcd io etcd distributed reliable key value store for the most critical data of a distributed system dependency hierarchy github com google certificate transparency go root library github com etcd io etcd x github com etcd io etcd vulnerable library github com etcd io etcd pkg httputil distributed reliable key value store for the most critical data of a distributed system dependency hierarchy github com google certificate transparency go root library github com etcd io etcd github com etcd io etcd github com etcd io etcd etcdserver github com etcd io etcd lease leasehttp github com etcd io etcd lease x github com etcd io etcd pkg httputil vulnerable library github com etcd io etcd distributed reliable key value store for the most critical data of a distributed system dependency hierarchy github com google certificate transparency go root library x github com etcd io etcd vulnerable library found in head commit a href found in base branch master vulnerability details a cross site request forgery flaw was found in etcd and earlier an attacker can set up a website that tries to send a post request to the etcd server and modify a key adding a key is done with put so it is theoretically safe can t put from an html form or such but post allows creating in order keys that an attacker can send publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rc isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree github com google certificate transparency go github com etcd io etcd github com etcd io etcd isminimumfixversionavailable true minimumfixversion rc packagetype go packagename github com etcd io etcd pkg httputil packageversion packagefilepaths istransitivedependency true dependencytree github com google certificate transparency go github com etcd io etcd github com etcd io etcd github com etcd io etcd etcdserver github com etcd io etcd lease leasehttp github com etcd io etcd lease github com etcd io etcd pkg httputil isminimumfixversionavailable true minimumfixversion rc packagetype go packagename github com etcd io etcd packageversion packagefilepaths istransitivedependency true dependencytree github com google certificate transparency go github com etcd io etcd isminimumfixversionavailable true minimumfixversion rc basebranches vulnerabilityidentifier cve vulnerabilitydetails a cross site request forgery flaw was found in etcd and earlier an attacker can set up a website that tries to send a post request to the etcd server and modify a key adding a key is done with put so it is theoretically safe can put from an html form or such but post allows creating in order keys that an attacker can send vulnerabilityurl | 0 |
36,029 | 7,850,667,897 | IssuesEvent | 2018-06-20 09:15:42 | primefaces/primeng | https://api.github.com/repos/primefaces/primeng | closed | FileUpload styleClass not working in basic mode | defect | The styleClass attribute is not working in 'basic' mode. Nor with component binded variable nor with a simple string. | 1.0 | FileUpload styleClass not working in basic mode - The styleClass attribute is not working in 'basic' mode. Nor with component binded variable nor with a simple string. | non_infrastructure | fileupload styleclass not working in basic mode the styleclass attribute is not working in basic mode nor with component binded variable nor with a simple string | 0 |
10,398 | 8,551,644,672 | IssuesEvent | 2018-11-07 18:39:47 | Azure/azure-cli | https://api.github.com/repos/Azure/azure-cli | closed | Consider adding a mechanism to filter the iteratable result without writing a custom command. | Feature Infrastructure | Example: https://github.com/Azure/azure-cli/blob/132b472a380c2701f1ea4caa87045d5be5240982/src/command_modules/azure-cli-storage/azure/cli/command_modules/storage/custom.py#L113 | 1.0 | Consider adding a mechanism to filter the iteratable result without writing a custom command. - Example: https://github.com/Azure/azure-cli/blob/132b472a380c2701f1ea4caa87045d5be5240982/src/command_modules/azure-cli-storage/azure/cli/command_modules/storage/custom.py#L113 | infrastructure | consider adding a mechanism to filter the iteratable result without writing a custom command example | 1 |
5,435 | 3,926,936,352 | IssuesEvent | 2016-04-23 07:17:41 | betterangels/buoy | https://api.github.com/repos/betterangels/buoy | closed | Add Facebook's Open Graph markup and other social media enhancements to project websites | enhancement good first issue meta:project website usability | Let's make it so that when someone shares a link to one of our static, public-facing websites, on a social network, it looks good there.
* For Facebook, these are ["Open Graph" markup tags](https://developers.facebook.com/docs/sharing/webmasters)
* Twitter calls these ["Twitter Cards"](https://dev.twitter.com/cards/getting-started)
* I'm not sure if there are any special such things for other networks.
Here's [a blog post about the above](https://moz.com/blog/meta-data-templates-123). | True | Add Facebook's Open Graph markup and other social media enhancements to project websites - Let's make it so that when someone shares a link to one of our static, public-facing websites, on a social network, it looks good there.
* For Facebook, these are ["Open Graph" markup tags](https://developers.facebook.com/docs/sharing/webmasters)
* Twitter calls these ["Twitter Cards"](https://dev.twitter.com/cards/getting-started)
* I'm not sure if there are any special such things for other networks.
Here's [a blog post about the above](https://moz.com/blog/meta-data-templates-123). | non_infrastructure | add facebook s open graph markup and other social media enhancements to project websites let s make it so that when someone shares a link to one of our static public facing websites on a social network it looks good there for facebook these are twitter calls these i m not sure if there are any special such things for other networks here s | 0 |
86,055 | 8,017,813,220 | IssuesEvent | 2018-07-25 17:04:30 | quipucords/camayoc | https://api.github.com/repos/quipucords/camayoc | closed | UI test cases for adding credentials in QPC | test case | # Issue type
- Test Case
# Description of issue
UI tests for adding new credentials to qpc.
# Completion checklist
To close this issue, the following items must be satisfied with the UI:
- [x] Add credentials of a network, satellite, and vcenter type, with a username and password.
- [ ] Add credentials of a network type, with a username, password, and the optional become password provided
- [ ] Add credentials of a network type, using an SSH key file.
- [ ] Add credentials of a network type, using an SSH key file and the optional become password provided.
| 1.0 | UI test cases for adding credentials in QPC - # Issue type
- Test Case
# Description of issue
UI tests for adding new credentials to qpc.
# Completion checklist
To close this issue, the following items must be satisfied with the UI:
- [x] Add credentials of a network, satellite, and vcenter type, with a username and password.
- [ ] Add credentials of a network type, with a username, password, and the optional become password provided
- [ ] Add credentials of a network type, using an SSH key file.
- [ ] Add credentials of a network type, using an SSH key file and the optional become password provided.
| non_infrastructure | ui test cases for adding credentials in qpc issue type test case description of issue ui tests for adding new credentials to qpc completion checklist to close this issue the following items must be satisfied with the ui add credentials of a network satellite and vcenter type with a username and password add credentials of a network type with a username password and the optional become password provided add credentials of a network type using an ssh key file add credentials of a network type using an ssh key file and the optional become password provided | 0 |
509,274 | 14,727,241,933 | IssuesEvent | 2021-01-06 08:13:23 | rism-ch/verovio | https://api.github.com/repos/rism-ch/verovio | closed | cross-staff slur placement | enhancement low priority | Slurs attached to notes that are not on their home staff have placement problems:
<img width="511" alt="Screen Shot 2019-06-29 at 12 10 56 PM" src="https://user-images.githubusercontent.com/3487289/60382703-71056a00-9a67-11e9-8a2e-cbf9a0c99b87.png">
Particularly when the slur is on the head side of the notes (odd measures). However, the tail-side slur in measure 4 is also not placed properly (too far from the note stems). Other even measures are OK, although I would be useful to move beams off of the home staff if all notes in the beam are off of the home staff as well in measures 1 and 2 (is that currently possible to do?).
MEI test data:
```xml
<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="http://music-encoding.org/schema/4.0.0/mei-all.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="http://music-encoding.org/schema/4.0.0/mei-all.rng" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?>
<mei xmlns="http://www.music-encoding.org/ns/mei" meiversion="4.0.0">
<meiHead>
<fileDesc>
<titleStmt>
<title />
</titleStmt>
<pubStmt />
</fileDesc>
<encodingDesc>
<appInfo>
<application isodate="2019-06-29T12:11:18" version="2.2.0-dev-64789a0-dirty">
<name>Verovio</name>
<p>Transcoded from Humdrum</p>
</application>
</appInfo>
</encodingDesc>
<workList>
<work>
<title />
</work>
</workList>
</meiHead>
<music>
<body>
<mdiv xml:id="mdiv-0000001771814920">
<score xml:id="score-0000000420745698">
<scoreDef xml:id="scoredef-0000001003762518">
<staffGrp xml:id="staffgrp-0000000994073757" symbol="brace" bar.thru="true">
<staffDef xml:id="staffdef-0000001485785563" clef.shape="G" clef.line="2" meter.count="4" meter.unit="4" n="1" lines="5" />
<staffDef xml:id="staffdef-0000001445209371" clef.shape="F" clef.line="4" meter.count="4" meter.unit="4" n="2" lines="5" />
</staffGrp>
</scoreDef>
<section xml:id="section-L1F1">
<measure xml:id="measure-L1" n="0">
<staff xml:id="staff-0000001174874088" n="1">
<layer xml:id="layer-L1F2N1" n="1">
<note xml:id="note-L5F2" dur="2" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-0000001066044845" n="2">
<layer xml:id="layer-L1F1N1" n="1">
<beam xml:id="beam-L5F1-L8F1">
<note xml:id="note-L5F1" dur="8" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L6F1" dur="8" staff="1" oct="5" pname="g" stem.dir="down" accid.ges="n" />
<note xml:id="note-L7F1" dur="8" staff="1" oct="5" pname="e" stem.dir="down" accid.ges="n" />
<note xml:id="note-L8F1" dur="8" staff="1" oct="5" pname="f" stem.dir="down" accid.ges="n" />
</beam>
</layer>
</staff>
<slur xml:id="slur-L5F1-L8F1" staff="2" startid="#note-L5F1" endid="#note-L8F1" />
</measure>
<measure xml:id="measure-L9" right="dbl" n="2">
<staff xml:id="staff-L9F2N1" n="1">
<layer xml:id="layer-L9F2N1" n="1">
<note xml:id="note-L10F2" dur="2" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L9F1N1" n="2">
<layer xml:id="layer-L9F1N1" n="1">
<beam xml:id="beam-L10F1-L13F1">
<note xml:id="note-L10F1" dur="8" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L11F1" dur="8" staff="1" oct="5" pname="g" stem.dir="down" accid.ges="n" />
<note xml:id="note-L12F1" dur="8" staff="1" oct="5" pname="e" stem.dir="down" accid.ges="n" />
<note xml:id="note-L13F1" dur="8" staff="1" oct="5" pname="f" stem.dir="down" accid.ges="n" />
</beam>
</layer>
</staff>
<slur xml:id="slur-L10F1-L13F1" staff="2" startid="#note-L10F1" endid="#note-L13F1" curvedir="below" />
</measure>
<measure xml:id="measure-L14" n="3">
<staff xml:id="staff-L14F2N1" n="1">
<layer xml:id="layer-L14F2N1" n="1">
<note xml:id="note-L15F2" dur="2" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L14F1N1" n="2">
<layer xml:id="layer-L14F1N1" n="1">
<note xml:id="note-L15F1" dur="8" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L16F1" dur="8" staff="1" oct="5" pname="g" stem.dir="down" accid.ges="n" />
<note xml:id="note-L17F1" dur="8" staff="1" oct="5" pname="e" stem.dir="down" accid.ges="n" />
<note xml:id="note-L18F1" dur="8" staff="1" oct="5" pname="f" stem.dir="down" accid.ges="n" />
</layer>
</staff>
<slur xml:id="slur-L15F1-L18F1" staff="2" startid="#note-L15F1" endid="#note-L18F1" />
</measure>
<measure xml:id="measure-L19" right="dbl" n="4">
<staff xml:id="staff-L19F2N1" n="1">
<layer xml:id="layer-L19F2N1" n="1">
<note xml:id="note-L20F2" dur="2" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L19F1N1" n="2">
<layer xml:id="layer-L19F1N1" n="1">
<note xml:id="note-L20F1" dur="8" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L21F1" dur="8" staff="1" oct="5" pname="g" stem.dir="down" accid.ges="n" />
<note xml:id="note-L22F1" dur="8" staff="1" oct="5" pname="e" stem.dir="down" accid.ges="n" />
<note xml:id="note-L23F1" dur="8" staff="1" oct="5" pname="f" stem.dir="down" accid.ges="n" />
</layer>
</staff>
<slur xml:id="slur-L20F1-L23F1" staff="2" startid="#note-L20F1" endid="#note-L23F1" curvedir="below" />
</measure>
<measure xml:id="measure-L24" n="5">
<staff xml:id="staff-L24F2N1" n="1">
<layer xml:id="layer-L24F2N1" n="1">
<note xml:id="note-L25F2" dur="2" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L24F1N1" n="2">
<layer xml:id="layer-L24F1N1" n="1">
<beam xml:id="beam-L25F1-L28F1">
<note xml:id="note-L25F1" dur="8" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L26F1" dur="8" oct="5" pname="g" accid.ges="n" />
<note xml:id="note-L27F1" dur="8" oct="5" pname="e" accid.ges="n" />
<note xml:id="note-L28F1" dur="8" oct="5" pname="f" accid.ges="n" />
</beam>
</layer>
</staff>
<slur xml:id="slur-L25F1-L28F1" staff="2" startid="#note-L25F1" endid="#note-L28F1" />
</measure>
<measure xml:id="measure-L29" right="dbl" n="6">
<staff xml:id="staff-L29F2N1" n="1">
<layer xml:id="layer-L29F2N1" n="1">
<note xml:id="note-L30F2" dur="2" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L29F1N1" n="2">
<layer xml:id="layer-L29F1N1" n="1">
<beam xml:id="beam-L30F1-L33F1">
<note xml:id="note-L30F1" dur="8" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L31F1" dur="8" oct="5" pname="g" accid.ges="n" />
<note xml:id="note-L32F1" dur="8" oct="5" pname="e" accid.ges="n" />
<note xml:id="note-L33F1" dur="8" oct="5" pname="f" accid.ges="n" />
</beam>
</layer>
</staff>
<slur xml:id="slur-L30F1-L33F1" staff="2" startid="#note-L30F1" endid="#note-L33F1" curvedir="below" />
</measure>
<measure xml:id="measure-L34" n="7">
<staff xml:id="staff-L34F2N1" n="1">
<layer xml:id="layer-L34F2N1" n="1">
<note xml:id="note-L35F2" dur="2" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L34F1N1" n="2">
<layer xml:id="layer-L34F1N1" n="1">
<note xml:id="note-L35F1" dur="8" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L36F1" dur="8" oct="5" pname="g" accid.ges="n" />
<note xml:id="note-L37F1" dur="8" oct="5" pname="e" accid.ges="n" />
<note xml:id="note-L38F1" dur="8" oct="5" pname="f" accid.ges="n" />
</layer>
</staff>
<slur xml:id="slur-L35F1-L38F1" staff="2" startid="#note-L35F1" endid="#note-L38F1" />
</measure>
<measure xml:id="measure-L39" right="dbl" n="8">
<staff xml:id="staff-L39F2N1" n="1">
<layer xml:id="layer-L39F2N1" n="1">
<note xml:id="note-L40F2" dur="2" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L39F1N1" n="2">
<layer xml:id="layer-L39F1N1" n="1">
<note xml:id="note-L40F1" dur="8" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L41F1" dur="8" oct="5" pname="g" accid.ges="n" />
<note xml:id="note-L42F1" dur="8" oct="5" pname="e" accid.ges="n" />
<note xml:id="note-L43F1" dur="8" oct="5" pname="f" accid.ges="n" />
</layer>
</staff>
<slur xml:id="slur-L40F1-L43F1" staff="2" startid="#note-L40F1" endid="#note-L43F1" curvedir="below" />
</measure>
<measure xml:id="measure-L44" n="9">
<staff xml:id="staff-L44F2N1" n="1">
<layer xml:id="layer-L44F2N1" n="1">
<note xml:id="note-L45F2" dur="1" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L44F1N1" n="2">
<layer xml:id="layer-L44F1N1" n="1">
<note xml:id="note-L45F1" dur="4" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L46F1" dur="4" oct="5" pname="g" accid.ges="n" />
<note xml:id="note-L47F1" dur="4" oct="5" pname="e" accid.ges="n" />
<note xml:id="note-L48F1" dur="4" oct="5" pname="f" accid.ges="n" />
</layer>
</staff>
<slur xml:id="slur-L45F1-L48F1" staff="2" startid="#note-L45F1" endid="#note-L48F1" />
</measure>
<measure xml:id="measure-L49" right="end" n="10">
<staff xml:id="staff-L49F2N1" n="1">
<layer xml:id="layer-L49F2N1" n="1">
<note xml:id="note-L50F2" dur="1" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L49F1N1" n="2">
<layer xml:id="layer-L49F1N1" n="1">
<note xml:id="note-L50F1" dur="4" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L51F1" dur="4" oct="5" pname="g" accid.ges="n" />
<note xml:id="note-L52F1" dur="4" oct="5" pname="e" accid.ges="n" />
<note xml:id="note-L53F1" dur="4" oct="5" pname="f" accid.ges="n" />
</layer>
</staff>
<slur xml:id="slur-L50F1-L53F1" staff="2" startid="#note-L50F1" endid="#note-L53F1" curvedir="below" />
</measure>
</section>
</score>
</mdiv>
</body>
</music>
</mei>
``` | 1.0 | cross-staff slur placement - Slurs attached to notes that are not on their home staff have placement problems:
<img width="511" alt="Screen Shot 2019-06-29 at 12 10 56 PM" src="https://user-images.githubusercontent.com/3487289/60382703-71056a00-9a67-11e9-8a2e-cbf9a0c99b87.png">
Particularly when the slur is on the head side of the notes (odd measures). However, the tail-side slur in measure 4 is also not placed properly (too far from the note stems). Other even measures are OK, although I would be useful to move beams off of the home staff if all notes in the beam are off of the home staff as well in measures 1 and 2 (is that currently possible to do?).
MEI test data:
```xml
<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="http://music-encoding.org/schema/4.0.0/mei-all.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="http://music-encoding.org/schema/4.0.0/mei-all.rng" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?>
<mei xmlns="http://www.music-encoding.org/ns/mei" meiversion="4.0.0">
<meiHead>
<fileDesc>
<titleStmt>
<title />
</titleStmt>
<pubStmt />
</fileDesc>
<encodingDesc>
<appInfo>
<application isodate="2019-06-29T12:11:18" version="2.2.0-dev-64789a0-dirty">
<name>Verovio</name>
<p>Transcoded from Humdrum</p>
</application>
</appInfo>
</encodingDesc>
<workList>
<work>
<title />
</work>
</workList>
</meiHead>
<music>
<body>
<mdiv xml:id="mdiv-0000001771814920">
<score xml:id="score-0000000420745698">
<scoreDef xml:id="scoredef-0000001003762518">
<staffGrp xml:id="staffgrp-0000000994073757" symbol="brace" bar.thru="true">
<staffDef xml:id="staffdef-0000001485785563" clef.shape="G" clef.line="2" meter.count="4" meter.unit="4" n="1" lines="5" />
<staffDef xml:id="staffdef-0000001445209371" clef.shape="F" clef.line="4" meter.count="4" meter.unit="4" n="2" lines="5" />
</staffGrp>
</scoreDef>
<section xml:id="section-L1F1">
<measure xml:id="measure-L1" n="0">
<staff xml:id="staff-0000001174874088" n="1">
<layer xml:id="layer-L1F2N1" n="1">
<note xml:id="note-L5F2" dur="2" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-0000001066044845" n="2">
<layer xml:id="layer-L1F1N1" n="1">
<beam xml:id="beam-L5F1-L8F1">
<note xml:id="note-L5F1" dur="8" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L6F1" dur="8" staff="1" oct="5" pname="g" stem.dir="down" accid.ges="n" />
<note xml:id="note-L7F1" dur="8" staff="1" oct="5" pname="e" stem.dir="down" accid.ges="n" />
<note xml:id="note-L8F1" dur="8" staff="1" oct="5" pname="f" stem.dir="down" accid.ges="n" />
</beam>
</layer>
</staff>
<slur xml:id="slur-L5F1-L8F1" staff="2" startid="#note-L5F1" endid="#note-L8F1" />
</measure>
<measure xml:id="measure-L9" right="dbl" n="2">
<staff xml:id="staff-L9F2N1" n="1">
<layer xml:id="layer-L9F2N1" n="1">
<note xml:id="note-L10F2" dur="2" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L9F1N1" n="2">
<layer xml:id="layer-L9F1N1" n="1">
<beam xml:id="beam-L10F1-L13F1">
<note xml:id="note-L10F1" dur="8" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L11F1" dur="8" staff="1" oct="5" pname="g" stem.dir="down" accid.ges="n" />
<note xml:id="note-L12F1" dur="8" staff="1" oct="5" pname="e" stem.dir="down" accid.ges="n" />
<note xml:id="note-L13F1" dur="8" staff="1" oct="5" pname="f" stem.dir="down" accid.ges="n" />
</beam>
</layer>
</staff>
<slur xml:id="slur-L10F1-L13F1" staff="2" startid="#note-L10F1" endid="#note-L13F1" curvedir="below" />
</measure>
<measure xml:id="measure-L14" n="3">
<staff xml:id="staff-L14F2N1" n="1">
<layer xml:id="layer-L14F2N1" n="1">
<note xml:id="note-L15F2" dur="2" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L14F1N1" n="2">
<layer xml:id="layer-L14F1N1" n="1">
<note xml:id="note-L15F1" dur="8" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L16F1" dur="8" staff="1" oct="5" pname="g" stem.dir="down" accid.ges="n" />
<note xml:id="note-L17F1" dur="8" staff="1" oct="5" pname="e" stem.dir="down" accid.ges="n" />
<note xml:id="note-L18F1" dur="8" staff="1" oct="5" pname="f" stem.dir="down" accid.ges="n" />
</layer>
</staff>
<slur xml:id="slur-L15F1-L18F1" staff="2" startid="#note-L15F1" endid="#note-L18F1" />
</measure>
<measure xml:id="measure-L19" right="dbl" n="4">
<staff xml:id="staff-L19F2N1" n="1">
<layer xml:id="layer-L19F2N1" n="1">
<note xml:id="note-L20F2" dur="2" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L19F1N1" n="2">
<layer xml:id="layer-L19F1N1" n="1">
<note xml:id="note-L20F1" dur="8" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L21F1" dur="8" staff="1" oct="5" pname="g" stem.dir="down" accid.ges="n" />
<note xml:id="note-L22F1" dur="8" staff="1" oct="5" pname="e" stem.dir="down" accid.ges="n" />
<note xml:id="note-L23F1" dur="8" staff="1" oct="5" pname="f" stem.dir="down" accid.ges="n" />
</layer>
</staff>
<slur xml:id="slur-L20F1-L23F1" staff="2" startid="#note-L20F1" endid="#note-L23F1" curvedir="below" />
</measure>
<measure xml:id="measure-L24" n="5">
<staff xml:id="staff-L24F2N1" n="1">
<layer xml:id="layer-L24F2N1" n="1">
<note xml:id="note-L25F2" dur="2" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L24F1N1" n="2">
<layer xml:id="layer-L24F1N1" n="1">
<beam xml:id="beam-L25F1-L28F1">
<note xml:id="note-L25F1" dur="8" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L26F1" dur="8" oct="5" pname="g" accid.ges="n" />
<note xml:id="note-L27F1" dur="8" oct="5" pname="e" accid.ges="n" />
<note xml:id="note-L28F1" dur="8" oct="5" pname="f" accid.ges="n" />
</beam>
</layer>
</staff>
<slur xml:id="slur-L25F1-L28F1" staff="2" startid="#note-L25F1" endid="#note-L28F1" />
</measure>
<measure xml:id="measure-L29" right="dbl" n="6">
<staff xml:id="staff-L29F2N1" n="1">
<layer xml:id="layer-L29F2N1" n="1">
<note xml:id="note-L30F2" dur="2" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L29F1N1" n="2">
<layer xml:id="layer-L29F1N1" n="1">
<beam xml:id="beam-L30F1-L33F1">
<note xml:id="note-L30F1" dur="8" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L31F1" dur="8" oct="5" pname="g" accid.ges="n" />
<note xml:id="note-L32F1" dur="8" oct="5" pname="e" accid.ges="n" />
<note xml:id="note-L33F1" dur="8" oct="5" pname="f" accid.ges="n" />
</beam>
</layer>
</staff>
<slur xml:id="slur-L30F1-L33F1" staff="2" startid="#note-L30F1" endid="#note-L33F1" curvedir="below" />
</measure>
<measure xml:id="measure-L34" n="7">
<staff xml:id="staff-L34F2N1" n="1">
<layer xml:id="layer-L34F2N1" n="1">
<note xml:id="note-L35F2" dur="2" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L34F1N1" n="2">
<layer xml:id="layer-L34F1N1" n="1">
<note xml:id="note-L35F1" dur="8" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L36F1" dur="8" oct="5" pname="g" accid.ges="n" />
<note xml:id="note-L37F1" dur="8" oct="5" pname="e" accid.ges="n" />
<note xml:id="note-L38F1" dur="8" oct="5" pname="f" accid.ges="n" />
</layer>
</staff>
<slur xml:id="slur-L35F1-L38F1" staff="2" startid="#note-L35F1" endid="#note-L38F1" />
</measure>
<measure xml:id="measure-L39" right="dbl" n="8">
<staff xml:id="staff-L39F2N1" n="1">
<layer xml:id="layer-L39F2N1" n="1">
<note xml:id="note-L40F2" dur="2" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L39F1N1" n="2">
<layer xml:id="layer-L39F1N1" n="1">
<note xml:id="note-L40F1" dur="8" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L41F1" dur="8" oct="5" pname="g" accid.ges="n" />
<note xml:id="note-L42F1" dur="8" oct="5" pname="e" accid.ges="n" />
<note xml:id="note-L43F1" dur="8" oct="5" pname="f" accid.ges="n" />
</layer>
</staff>
<slur xml:id="slur-L40F1-L43F1" staff="2" startid="#note-L40F1" endid="#note-L43F1" curvedir="below" />
</measure>
<measure xml:id="measure-L44" n="9">
<staff xml:id="staff-L44F2N1" n="1">
<layer xml:id="layer-L44F2N1" n="1">
<note xml:id="note-L45F2" dur="1" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L44F1N1" n="2">
<layer xml:id="layer-L44F1N1" n="1">
<note xml:id="note-L45F1" dur="4" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L46F1" dur="4" oct="5" pname="g" accid.ges="n" />
<note xml:id="note-L47F1" dur="4" oct="5" pname="e" accid.ges="n" />
<note xml:id="note-L48F1" dur="4" oct="5" pname="f" accid.ges="n" />
</layer>
</staff>
<slur xml:id="slur-L45F1-L48F1" staff="2" startid="#note-L45F1" endid="#note-L48F1" />
</measure>
<measure xml:id="measure-L49" right="end" n="10">
<staff xml:id="staff-L49F2N1" n="1">
<layer xml:id="layer-L49F2N1" n="1">
<note xml:id="note-L50F2" dur="1" oct="6" pname="c" stem.dir="up" accid.ges="n" />
</layer>
</staff>
<staff xml:id="staff-L49F1N1" n="2">
<layer xml:id="layer-L49F1N1" n="1">
<note xml:id="note-L50F1" dur="4" staff="1" oct="5" pname="c" stem.dir="down" accid.ges="n" />
<note xml:id="note-L51F1" dur="4" oct="5" pname="g" accid.ges="n" />
<note xml:id="note-L52F1" dur="4" oct="5" pname="e" accid.ges="n" />
<note xml:id="note-L53F1" dur="4" oct="5" pname="f" accid.ges="n" />
</layer>
</staff>
<slur xml:id="slur-L50F1-L53F1" staff="2" startid="#note-L50F1" endid="#note-L53F1" curvedir="below" />
</measure>
</section>
</score>
</mdiv>
</body>
</music>
</mei>
``` | non_infrastructure | cross staff slur placement slurs attached to notes that are not on their home staff have placement problems img width alt screen shot at pm src particularly when the slur is on the head side of the notes odd measures however the tail side slur in measure is also not placed properly too far from the note stems other even measures are ok although i would be useful to move beams off of the home staff if all notes in the beam are off of the home staff as well in measures and is that currently possible to do mei test data xml xml model href type application xml schematypens xml model href type application xml schematypens verovio transcoded from humdrum | 0 |
352,778 | 10,545,948,603 | IssuesEvent | 2019-10-02 20:18:49 | DXHeroes/dx-scanner | https://api.github.com/repos/DXHeroes/dx-scanner | closed | Create a language detector for C# (~100 new lines of code) | Difficulty: Easy Hacktoberfest Priority: Low Status: Available Type: Enhancement good first issue | We'd like to measure the quality of apps written in C#.
There are "language detectors" to determine what language is on which path.
It's necessary to implement **CSharpLanguageDetector** the same way as is [JavaScriptLanguageDetector](https://github.com/DXHeroes/dx-scanner/blob/master/src/detectors/JavaScript/JavaScriptLanguageDetector.ts) implemented. It's around 100 new lines of code including tests.
More info in [our Contribution guide](https://github.com/DXHeroes/dx-scanner/blob/master/CONTRIBUTING.md). | 1.0 | Create a language detector for C# (~100 new lines of code) - We'd like to measure the quality of apps written in C#.
There are "language detectors" to determine what language is on which path.
It's necessary to implement **CSharpLanguageDetector** the same way as is [JavaScriptLanguageDetector](https://github.com/DXHeroes/dx-scanner/blob/master/src/detectors/JavaScript/JavaScriptLanguageDetector.ts) implemented. It's around 100 new lines of code including tests.
More info in [our Contribution guide](https://github.com/DXHeroes/dx-scanner/blob/master/CONTRIBUTING.md). | non_infrastructure | create a language detector for c new lines of code we d like to measure the quality of apps written in c there are language detectors to determine what language is on which path it s necessary to implement csharplanguagedetector the same way as is implemented it s around new lines of code including tests more info in | 0 |
28,223 | 23,095,467,850 | IssuesEvent | 2022-07-26 19:04:50 | cal-itp/benefits | https://api.github.com/repos/cal-itp/benefits | opened | make downtime alerts louder | bug infrastructure | As [described in the 7/21 downtime report](https://docs.google.com/document/d/14XFpJonXmrNKDt98g8vML3RimbZha0UJiIeUVclXYGs/edit#heading=h.tbfsxvwjhk7u),
> We should get “loud” alerts about downtime, but right now there’s just [a message posted to a high-volume channel](https://cal-itp.slack.com/archives/C022HHSEE3F/p1658439759753709).
## To Reproduce
1. Make one of the environments unavailable: disable traffic, delete the hostname binding, etc.
2. Wait for alert
## Expected behavior
For production downtime, engineer(s) should get a ping, ideally something that needs to be acknowledged.
## Additional context
none
| 1.0 | make downtime alerts louder - As [described in the 7/21 downtime report](https://docs.google.com/document/d/14XFpJonXmrNKDt98g8vML3RimbZha0UJiIeUVclXYGs/edit#heading=h.tbfsxvwjhk7u),
> We should get “loud” alerts about downtime, but right now there’s just [a message posted to a high-volume channel](https://cal-itp.slack.com/archives/C022HHSEE3F/p1658439759753709).
## To Reproduce
1. Make one of the environments unavailable: disable traffic, delete the hostname binding, etc.
2. Wait for alert
## Expected behavior
For production downtime, engineer(s) should get a ping, ideally something that needs to be acknowledged.
## Additional context
none
| infrastructure | make downtime alerts louder as we should get “loud” alerts about downtime but right now there’s just to reproduce make one of the environments unavailable disable traffic delete the hostname binding etc wait for alert expected behavior for production downtime engineer s should get a ping ideally something that needs to be acknowledged additional context none | 1 |
740,835 | 25,770,309,854 | IssuesEvent | 2022-12-09 07:17:49 | OrderN/CONQUEST-release | https://api.github.com/repos/OrderN/CONQUEST-release | closed | Problem in setting spin-dependent atomic charge density | area: main-source needs: confirmation priority: minor time: days type: bug | For multi-element systems, even when we set different electron numbers for spin up and down electrons of some elements, CONQUEST does not set the initial density is not set properly.
It is because the flag `flag_InitialAtomicSpin` in `initial_read_module.f90` is not set properly for multi-element systems, I think. It is now set in the do-loop of species for every species, thus can be overwritten.
We will correct it soon, but for now, the problem may be solved if we set the element which needs to be spin polarized as the last element. | 1.0 | Problem in setting spin-dependent atomic charge density - For multi-element systems, even when we set different electron numbers for spin up and down electrons of some elements, CONQUEST does not set the initial density is not set properly.
It is because the flag `flag_InitialAtomicSpin` in `initial_read_module.f90` is not set properly for multi-element systems, I think. It is now set in the do-loop of species for every species, thus can be overwritten.
We will correct it soon, but for now, the problem may be solved if we set the element which needs to be spin polarized as the last element. | non_infrastructure | problem in setting spin dependent atomic charge density for multi element systems even when we set different electron numbers for spin up and down electrons of some elements conquest does not set the initial density is not set properly it is because the flag flag initialatomicspin in initial read module is not set properly for multi element systems i think it is now set in the do loop of species for every species thus can be overwritten we will correct it soon but for now the problem may be solved if we set the element which needs to be spin polarized as the last element | 0 |
88,229 | 8,135,777,384 | IssuesEvent | 2018-08-20 05:26:07 | systers/mentorship-backend | https://api.github.com/repos/systers/mentorship-backend | closed | Revoke an admin role Quality Assurance | Category: Quality Assurance Priority: MEDIUM Status: Available Type: Testing | ## Description
This issue is to test all the test cases in the Revoke an admin rolein the Quality Assurance document below. This issue can be worked by many contributors. Refer this issue when you find a bug in the following test cases.
## Test cases
You can check the below document for test cases.
https://docs.google.com/document/d/1kStdMWK9K93zlsjIFbU2fODE98NK3a4nJGtYtBEyrlo/
**Service:** POST /admin/remove
## Definition of Done
- [ ] At least one test case tested.
## Estimation
30 minutes for test case (approximation)
| 1.0 | Revoke an admin role Quality Assurance - ## Description
This issue is to test all the test cases in the Revoke an admin rolein the Quality Assurance document below. This issue can be worked by many contributors. Refer this issue when you find a bug in the following test cases.
## Test cases
You can check the below document for test cases.
https://docs.google.com/document/d/1kStdMWK9K93zlsjIFbU2fODE98NK3a4nJGtYtBEyrlo/
**Service:** POST /admin/remove
## Definition of Done
- [ ] At least one test case tested.
## Estimation
30 minutes for test case (approximation)
| non_infrastructure | revoke an admin role quality assurance description this issue is to test all the test cases in the revoke an admin rolein the quality assurance document below this issue can be worked by many contributors refer this issue when you find a bug in the following test cases test cases you can check the below document for test cases service post admin remove definition of done at least one test case tested estimation minutes for test case approximation | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.