Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1
value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3
values | title stringlengths 1 1k | labels stringlengths 4 1.38k | body stringlengths 1 262k | index stringclasses 16
values | text_combine stringlengths 96 262k | label stringclasses 2
values | text stringlengths 96 252k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
707,102 | 24,295,170,501 | IssuesEvent | 2022-09-29 09:28:42 | wso2/api-manager | https://api.github.com/repos/wso2/api-manager | opened | Integration Studio 8.1.0 issue when running the embeded micro integrator in debug mode | Type/Bug Priority/Normal | ### Description
Integration Studio 8.1.0 is returning the below warn and error logs while running the integrations studio in debug mode as follows.
**WARNING:** An illegal reflective access operation has occurred
**WARNING:** Illegal reflective access by org.eclipse.osgi.storage.FrameworkExtensionInstaller (file:/home/eshani/Documents/products/chek/WSO2-Integration-Studio-8.1.0-linux-gtk-x86_64/IntegrationStudio/runtime/microesb/wso2/components/plugins/org.eclipse.osgi_3.14.0.v20190517-1309.jar) to method java.net.URLClassLoader.addURL(java.net.URL)
**WARNING:** Please consider reporting this to the maintainers of org.eclipse.osgi.storage.FrameworkExtensionInstaller
**WARNING:** Use --illegal-access=warn to enable warnings of further illegal reflective access operations
**WARNING:** All illegal access operations will be denied in a future release
[2022-09-29 14:11:24,753] INFO {EventAdminConfigurationNotifier} - Logging configuration changed. (Event Admin service unavailable - no notification sent).
[2022-09-29 14:11:25,452] **ERROR** {Framework} - FrameworkEvent ERROR org.osgi.framework.BundleException: Could not resolve module: org.wso2.carbon.capp.monitor [171]
Unresolved requirement: Import-Package: org.wso2.carbon.application.deployer
at org.eclipse.osgi.container.Module.start(Module.java:457)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$1.run(ModuleContainer.java:1820)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$2$1.execute(EquinoxContainerAdaptor.java:150)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1813)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1770)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1735)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1661)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)
After running the integration studio in debug mode once and then just running the embedded micro integrator, the mentioned warn logs are not getting printed, but the following error can be observed.
[2022-09-29 14:12:45,997] INFO {EventAdminConfigurationNotifier} - Logging configuration changed. (Event Admin service unavailable - no notification sent).
[2022-09-29 14:12:46,667] ERROR {Framework} - FrameworkEvent ERROR org.osgi.framework.BundleException: Could not resolve module: org.wso2.carbon.capp.monitor [171]
Unresolved requirement: Import-Package: org.wso2.carbon.application.deployer
at org.eclipse.osgi.container.Module.start(Module.java:457)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$1.run(ModuleContainer.java:1820)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$2$1.execute(EquinoxContainerAdaptor.java:150)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1813)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1770)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1735)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1661)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)
When further checking, we were able to find that the org.wso2.carbon.capp.monitor-3.0.0.jar jar file is getting stored into the droppings folder in embedded integration studio in micro integrator.
### Steps to Reproduce
1. Create an integration project.
2. Go to Run-->Debug configurations-->Debug on Emdeded micro integration server-->debug
3. You will see the errors and it will indicate that the server is MI-1.2.0
4. Then stop and just run the project in the embedded micro integrator.
5. The jar file issue will be observed
### Affected Component
IntegrationStudio
### Version
8.1.0
### Environment Details (with versions)
_No response_
### Relevant Log Output
_No response_
### Related Issues
_No response_
### Suggested Labels
_No response_ | 1.0 | Integration Studio 8.1.0 issue when running the embeded micro integrator in debug mode - ### Description
Integration Studio 8.1.0 is returning the below warn and error logs while running the integrations studio in debug mode as follows.
**WARNING:** An illegal reflective access operation has occurred
**WARNING:** Illegal reflective access by org.eclipse.osgi.storage.FrameworkExtensionInstaller (file:/home/eshani/Documents/products/chek/WSO2-Integration-Studio-8.1.0-linux-gtk-x86_64/IntegrationStudio/runtime/microesb/wso2/components/plugins/org.eclipse.osgi_3.14.0.v20190517-1309.jar) to method java.net.URLClassLoader.addURL(java.net.URL)
**WARNING:** Please consider reporting this to the maintainers of org.eclipse.osgi.storage.FrameworkExtensionInstaller
**WARNING:** Use --illegal-access=warn to enable warnings of further illegal reflective access operations
**WARNING:** All illegal access operations will be denied in a future release
[2022-09-29 14:11:24,753] INFO {EventAdminConfigurationNotifier} - Logging configuration changed. (Event Admin service unavailable - no notification sent).
[2022-09-29 14:11:25,452] **ERROR** {Framework} - FrameworkEvent ERROR org.osgi.framework.BundleException: Could not resolve module: org.wso2.carbon.capp.monitor [171]
Unresolved requirement: Import-Package: org.wso2.carbon.application.deployer
at org.eclipse.osgi.container.Module.start(Module.java:457)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$1.run(ModuleContainer.java:1820)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$2$1.execute(EquinoxContainerAdaptor.java:150)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1813)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1770)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1735)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1661)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)
After running the integration studio in debug mode once and then just running the embedded micro integrator, the mentioned warn logs are not getting printed, but the following error can be observed.
[2022-09-29 14:12:45,997] INFO {EventAdminConfigurationNotifier} - Logging configuration changed. (Event Admin service unavailable - no notification sent).
[2022-09-29 14:12:46,667] ERROR {Framework} - FrameworkEvent ERROR org.osgi.framework.BundleException: Could not resolve module: org.wso2.carbon.capp.monitor [171]
Unresolved requirement: Import-Package: org.wso2.carbon.application.deployer
at org.eclipse.osgi.container.Module.start(Module.java:457)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$1.run(ModuleContainer.java:1820)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$2$1.execute(EquinoxContainerAdaptor.java:150)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1813)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1770)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1735)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1661)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)
When further checking, we were able to find that the org.wso2.carbon.capp.monitor-3.0.0.jar jar file is getting stored into the droppings folder in embedded integration studio in micro integrator.
### Steps to Reproduce
1. Create an integration project.
2. Go to Run-->Debug configurations-->Debug on Emdeded micro integration server-->debug
3. You will see the errors and it will indicate that the server is MI-1.2.0
4. Then stop and just run the project in the embedded micro integrator.
5. The jar file issue will be observed
### Affected Component
IntegrationStudio
### Version
8.1.0
### Environment Details (with versions)
_No response_
### Relevant Log Output
_No response_
### Related Issues
_No response_
### Suggested Labels
_No response_ | priority | integration studio issue when running the embeded micro integrator in debug mode description integration studio is returning the below warn and error logs while running the integrations studio in debug mode as follows warning an illegal reflective access operation has occurred warning illegal reflective access by org eclipse osgi storage frameworkextensioninstaller file home eshani documents products chek integration studio linux gtk integrationstudio runtime microesb components plugins org eclipse osgi jar to method java net urlclassloader addurl java net url warning please consider reporting this to the maintainers of org eclipse osgi storage frameworkextensioninstaller warning use illegal access warn to enable warnings of further illegal reflective access operations warning all illegal access operations will be denied in a future release info eventadminconfigurationnotifier logging configuration changed event admin service unavailable no notification sent error framework frameworkevent error org osgi framework bundleexception could not resolve module org carbon capp monitor unresolved requirement import package org carbon application deployer at org eclipse osgi container module start module java at org eclipse osgi container modulecontainer containerstartlevel run modulecontainer java at org eclipse osgi internal framework equinoxcontaineradaptor execute equinoxcontaineradaptor java at org eclipse osgi container modulecontainer containerstartlevel incstartlevel modulecontainer java at org eclipse osgi container modulecontainer containerstartlevel incstartlevel modulecontainer java at org eclipse osgi container modulecontainer containerstartlevel docontainerstartlevel modulecontainer java at org eclipse osgi container modulecontainer containerstartlevel dispatchevent modulecontainer java at org eclipse osgi container modulecontainer containerstartlevel dispatchevent modulecontainer java at org eclipse osgi framework eventmgr eventmanager dispatchevent eventmanager java at org eclipse osgi framework eventmgr eventmanager eventthread run eventmanager java after running the integration studio in debug mode once and then just running the embedded micro integrator the mentioned warn logs are not getting printed but the following error can be observed info eventadminconfigurationnotifier logging configuration changed event admin service unavailable no notification sent error framework frameworkevent error org osgi framework bundleexception could not resolve module org carbon capp monitor unresolved requirement import package org carbon application deployer at org eclipse osgi container module start module java at org eclipse osgi container modulecontainer containerstartlevel run modulecontainer java at org eclipse osgi internal framework equinoxcontaineradaptor execute equinoxcontaineradaptor java at org eclipse osgi container modulecontainer containerstartlevel incstartlevel modulecontainer java at org eclipse osgi container modulecontainer containerstartlevel incstartlevel modulecontainer java at org eclipse osgi container modulecontainer containerstartlevel docontainerstartlevel modulecontainer java at org eclipse osgi container modulecontainer containerstartlevel dispatchevent modulecontainer java at org eclipse osgi container modulecontainer containerstartlevel dispatchevent modulecontainer java at org eclipse osgi framework eventmgr eventmanager dispatchevent eventmanager java at org eclipse osgi framework eventmgr eventmanager eventthread run eventmanager java when further checking we were able to find that the org carbon capp monitor jar jar file is getting stored into the droppings folder in embedded integration studio in micro integrator steps to reproduce create an integration project go to run debug configurations debug on emdeded micro integration server debug you will see the errors and it will indicate that the server is mi then stop and just run the project in the embedded micro integrator the jar file issue will be observed affected component integrationstudio version environment details with versions no response relevant log output no response related issues no response suggested labels no response | 1 |
611,193 | 18,947,814,362 | IssuesEvent | 2021-11-18 12:09:09 | metabase/metabase | https://api.github.com/repos/metabase/metabase | opened | When filtering by Entity Key, then most options are hidden in Simple GUI | Type:UX Priority:P3 .Frontend Querying/GUI | **Describe the bug**
When filtering by Entity Key, then it hides all filters and the Filtering/Summarize buttons in Simple GUI.
This can be specially confusing, when accidentally inputting a wrong value, so there's "No results".
**To Reproduce**
1. Simple question > Sample Dataset > Products - Filtering: "Category"=`Gizmo`
2. Now add another filter (of the Entity Key), "ID"=`2022` (non-existing value) - it quickly flashes the filters before hiding them:
**Expected behavior**
Do not try to go into ObjectDetail view, when there's no results.
I would prefer to always have the filters shown, but that's a Product call: https://github.com/metabase/metabase/pull/16614#pullrequestreview-685369588
**Information about your Metabase Installation:**
Tested 0.37.8 thru 0.41.2 | 1.0 | When filtering by Entity Key, then most options are hidden in Simple GUI - **Describe the bug**
When filtering by Entity Key, then it hides all filters and the Filtering/Summarize buttons in Simple GUI.
This can be specially confusing, when accidentally inputting a wrong value, so there's "No results".
**To Reproduce**
1. Simple question > Sample Dataset > Products - Filtering: "Category"=`Gizmo`
2. Now add another filter (of the Entity Key), "ID"=`2022` (non-existing value) - it quickly flashes the filters before hiding them:
**Expected behavior**
Do not try to go into ObjectDetail view, when there's no results.
I would prefer to always have the filters shown, but that's a Product call: https://github.com/metabase/metabase/pull/16614#pullrequestreview-685369588
**Information about your Metabase Installation:**
Tested 0.37.8 thru 0.41.2 | priority | when filtering by entity key then most options are hidden in simple gui describe the bug when filtering by entity key then it hides all filters and the filtering summarize buttons in simple gui this can be specially confusing when accidentally inputting a wrong value so there s no results to reproduce simple question sample dataset products filtering category gizmo now add another filter of the entity key id non existing value it quickly flashes the filters before hiding them expected behavior do not try to go into objectdetail view when there s no results i would prefer to always have the filters shown but that s a product call information about your metabase installation tested thru | 1 |
457,915 | 13,165,061,399 | IssuesEvent | 2020-08-11 05:38:45 | wso2/product-apim | https://api.github.com/repos/wso2/product-apim | closed | Portals Publisher and Admin cannot view in Microsoft Edge 44.18362.449.0 | Priority/Normal Type/Accessibility Type/Bug Type/React-UI | ### Description:
Publisher and Admin portals are not working in Microsoft Edge 44.18362.449.0, Devportal is working.
All working when remote viewing a server hosted on mac.
### Steps to reproduce:
### Affected Product Version:
<!-- Members can use Affected/*** labels -->
RC3
### Environment details (with versions):
- OS: Windows 10
- Client:
- Env (Docker/K8s):
- Microsoft Edge 44.18362.449.0
---
### Optional Fields
#### Related Issues:
<!-- Any related issues from this/other repositories-->
#### Suggested Labels:
<!--Only to be used by non-members-->
#### Suggested Assignees:
<!--Only to be used by non-members--> | 1.0 | Portals Publisher and Admin cannot view in Microsoft Edge 44.18362.449.0 - ### Description:
Publisher and Admin portals are not working in Microsoft Edge 44.18362.449.0, Devportal is working.
All working when remote viewing a server hosted on mac.
### Steps to reproduce:
### Affected Product Version:
<!-- Members can use Affected/*** labels -->
RC3
### Environment details (with versions):
- OS: Windows 10
- Client:
- Env (Docker/K8s):
- Microsoft Edge 44.18362.449.0
---
### Optional Fields
#### Related Issues:
<!-- Any related issues from this/other repositories-->
#### Suggested Labels:
<!--Only to be used by non-members-->
#### Suggested Assignees:
<!--Only to be used by non-members--> | priority | portals publisher and admin cannot view in microsoft edge description publisher and admin portals are not working in microsoft edge devportal is working all working when remote viewing a server hosted on mac steps to reproduce affected product version environment details with versions os windows client env docker microsoft edge optional fields related issues suggested labels suggested assignees | 1 |
178,905 | 14,684,406,333 | IssuesEvent | 2021-01-01 02:23:19 | apache/buildstream | https://api.github.com/repos/apache/buildstream | opened | Plugin documentation is lacking | documentation | [See original issue on GitLab](https://gitlab.com/BuildStream/buildstream/-/issues/1192)
In GitLab by [[Gitlab user @cs-shadow]](https://gitlab.com/cs-shadow) on Nov 6, 2019, 19:30
## Background
Plugins are at the heart of BuildStream when it comes to end-users, as that is what allows users to write their element configuration. However BuildStream documentation appears to be lacking in this department. We do have some documentation for each plugin where we talk a bit about default variables. But, just describing what those variables mean in one sentence is hardly sufficient for a new user.
Take `stack` element for example, [it's documentation](https://docs.buildstream.build/master/elements/stack.html) says just one sentence:
> Stack elements are simply a symbolic element used for representing a logical group of elements.
Just by reading that one sentence, it's not clear at all how should an user go about writing a `stack` element.
## Task description
I think we first need to think more seriously about _what_ to document. Next, maybe start with a couple of common plugins and have a more detailed documentation for them. Once we are happy with the general strucutre, we can follow similar format in other plugins as well.
## Acceptance Criteria
[//]: # (Acceptance criteria should follow the S.M.A.R.T. principle https://en.wikipedia.org/wiki/SMART_criteria )
A resonably new BuildStream user should be able to understand how to use a given plugin by reading its documentation.
----
[//]: # (To review information about possible relevant labels for this issue please view the list of labels: https://gitlab.com/BuildStream/buildstream/labels) | 1.0 | Plugin documentation is lacking - [See original issue on GitLab](https://gitlab.com/BuildStream/buildstream/-/issues/1192)
In GitLab by [[Gitlab user @cs-shadow]](https://gitlab.com/cs-shadow) on Nov 6, 2019, 19:30
## Background
Plugins are at the heart of BuildStream when it comes to end-users, as that is what allows users to write their element configuration. However BuildStream documentation appears to be lacking in this department. We do have some documentation for each plugin where we talk a bit about default variables. But, just describing what those variables mean in one sentence is hardly sufficient for a new user.
Take `stack` element for example, [it's documentation](https://docs.buildstream.build/master/elements/stack.html) says just one sentence:
> Stack elements are simply a symbolic element used for representing a logical group of elements.
Just by reading that one sentence, it's not clear at all how should an user go about writing a `stack` element.
## Task description
I think we first need to think more seriously about _what_ to document. Next, maybe start with a couple of common plugins and have a more detailed documentation for them. Once we are happy with the general strucutre, we can follow similar format in other plugins as well.
## Acceptance Criteria
[//]: # (Acceptance criteria should follow the S.M.A.R.T. principle https://en.wikipedia.org/wiki/SMART_criteria )
A resonably new BuildStream user should be able to understand how to use a given plugin by reading its documentation.
----
[//]: # (To review information about possible relevant labels for this issue please view the list of labels: https://gitlab.com/BuildStream/buildstream/labels) | non_priority | plugin documentation is lacking in gitlab by on nov background plugins are at the heart of buildstream when it comes to end users as that is what allows users to write their element configuration however buildstream documentation appears to be lacking in this department we do have some documentation for each plugin where we talk a bit about default variables but just describing what those variables mean in one sentence is hardly sufficient for a new user take stack element for example says just one sentence stack elements are simply a symbolic element used for representing a logical group of elements just by reading that one sentence it s not clear at all how should an user go about writing a stack element task description i think we first need to think more seriously about what to document next maybe start with a couple of common plugins and have a more detailed documentation for them once we are happy with the general strucutre we can follow similar format in other plugins as well acceptance criteria acceptance criteria should follow the s m a r t principle a resonably new buildstream user should be able to understand how to use a given plugin by reading its documentation to review information about possible relevant labels for this issue please view the list of labels | 0 |
813,765 | 30,471,181,889 | IssuesEvent | 2023-07-17 13:44:34 | magento/magento2 | https://api.github.com/repos/magento/magento2 | closed | Customer data in localstorage not reset when session file lost | Issue: Confirmed Reproduced on 2.4.x Component: Session Priority: P2 Progress: done Reported on 2.4.x Area: Account | ### Preconditions and environment
- Magento version 2.4-develop
### Steps to reproduce
1. Login customer in frontend
2. Add product to cart
3. Remove magento session files with command: rm -rf var/session/*
4. Flush cache
### Expected result
- Header not show customer name
- Mini cart not show any item
### Actual result
- Header still show old customer name
- Mini cart still show old item
### Additional information
_No response_
### Release note
_No response_
### Triage and priority
- [ ] Severity: **S0** _- Affects critical data or functionality and leaves users without workaround._
- [ ] Severity: **S1** _- Affects critical data or functionality and forces users to employ a workaround._
- [ ] Severity: **S2** _- Affects non-critical data or functionality and forces users to employ a workaround._
- [ ] Severity: **S3** _- Affects non-critical data or functionality and does not force users to employ a workaround._
- [ ] Severity: **S4** _- Affects aesthetics, professional look and feel, “quality” or “usability”._ | 1.0 | Customer data in localstorage not reset when session file lost - ### Preconditions and environment
- Magento version 2.4-develop
### Steps to reproduce
1. Login customer in frontend
2. Add product to cart
3. Remove magento session files with command: rm -rf var/session/*
4. Flush cache
### Expected result
- Header not show customer name
- Mini cart not show any item
### Actual result
- Header still show old customer name
- Mini cart still show old item
### Additional information
_No response_
### Release note
_No response_
### Triage and priority
- [ ] Severity: **S0** _- Affects critical data or functionality and leaves users without workaround._
- [ ] Severity: **S1** _- Affects critical data or functionality and forces users to employ a workaround._
- [ ] Severity: **S2** _- Affects non-critical data or functionality and forces users to employ a workaround._
- [ ] Severity: **S3** _- Affects non-critical data or functionality and does not force users to employ a workaround._
- [ ] Severity: **S4** _- Affects aesthetics, professional look and feel, “quality” or “usability”._ | priority | customer data in localstorage not reset when session file lost preconditions and environment magento version develop steps to reproduce login customer in frontend add product to cart remove magento session files with command rm rf var session flush cache expected result header not show customer name mini cart not show any item actual result header still show old customer name mini cart still show old item additional information no response release note no response triage and priority severity affects critical data or functionality and leaves users without workaround severity affects critical data or functionality and forces users to employ a workaround severity affects non critical data or functionality and forces users to employ a workaround severity affects non critical data or functionality and does not force users to employ a workaround severity affects aesthetics professional look and feel “quality” or “usability” | 1 |
120,437 | 25,794,356,467 | IssuesEvent | 2022-12-10 11:44:32 | reactplay/react-play | https://api.github.com/repos/reactplay/react-play | closed | ✨ [Feature request]: Code cleanup `Common` folder | code-cleanup | ### Is your feature request related to a problem? Please describe.
Fix the eslint and formatting issue for common folder file formatting.
### Describe the solution you'd like.
Fix the eslint and formatting issue for common folder file formatting.
### Describe alternatives you've considered.
.
### Screenshot / Screenshare
_No response_
### Additional context
_No response_
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct | 1.0 | ✨ [Feature request]: Code cleanup `Common` folder - ### Is your feature request related to a problem? Please describe.
Fix the eslint and formatting issue for common folder file formatting.
### Describe the solution you'd like.
Fix the eslint and formatting issue for common folder file formatting.
### Describe alternatives you've considered.
.
### Screenshot / Screenshare
_No response_
### Additional context
_No response_
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct | non_priority | ✨ code cleanup common folder is your feature request related to a problem please describe fix the eslint and formatting issue for common folder file formatting describe the solution you d like fix the eslint and formatting issue for common folder file formatting describe alternatives you ve considered screenshot screenshare no response additional context no response code of conduct i agree to follow this project s code of conduct | 0 |
278,900 | 30,702,421,715 | IssuesEvent | 2023-07-27 01:28:48 | panasalap/linux-4.1.15 | https://api.github.com/repos/panasalap/linux-4.1.15 | closed | CVE-2022-25258 (Medium) detected in linux179e72b561d3d331c850e1a5779688d7a7de5246 - autoclosed | Mend: dependency security vulnerability | ## CVE-2022-25258 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux179e72b561d3d331c850e1a5779688d7a7de5246</b></p></summary>
<p>
<p>Linux kernel stable tree mirror</p>
<p>Library home page: <a href=https://github.com/gregkh/linux.git>https://github.com/gregkh/linux.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/panasalap/linux-4.1.15/commit/aae4c2fa46027fd4c477372871df090c6b94f3f1">aae4c2fa46027fd4c477372871df090c6b94f3f1</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in drivers/usb/gadget/composite.c in the Linux kernel before 5.16.10. The USB Gadget subsystem lacks certain validation of interface OS descriptor requests (ones with a large array index and ones associated with NULL function pointer retrieval). Memory corruption might occur.
<p>Publish Date: 2022-02-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-25258>CVE-2022-25258</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Physical
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25258">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25258</a></p>
<p>Release Date: 2022-02-16</p>
<p>Fix Resolution: v5.17-rc4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-25258 (Medium) detected in linux179e72b561d3d331c850e1a5779688d7a7de5246 - autoclosed - ## CVE-2022-25258 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux179e72b561d3d331c850e1a5779688d7a7de5246</b></p></summary>
<p>
<p>Linux kernel stable tree mirror</p>
<p>Library home page: <a href=https://github.com/gregkh/linux.git>https://github.com/gregkh/linux.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/panasalap/linux-4.1.15/commit/aae4c2fa46027fd4c477372871df090c6b94f3f1">aae4c2fa46027fd4c477372871df090c6b94f3f1</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in drivers/usb/gadget/composite.c in the Linux kernel before 5.16.10. The USB Gadget subsystem lacks certain validation of interface OS descriptor requests (ones with a large array index and ones associated with NULL function pointer retrieval). Memory corruption might occur.
<p>Publish Date: 2022-02-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-25258>CVE-2022-25258</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Physical
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25258">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25258</a></p>
<p>Release Date: 2022-02-16</p>
<p>Fix Resolution: v5.17-rc4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in autoclosed cve medium severity vulnerability vulnerable library linux kernel stable tree mirror library home page a href found in head commit a href found in base branch master vulnerable source files vulnerability details an issue was discovered in drivers usb gadget composite c in the linux kernel before the usb gadget subsystem lacks certain validation of interface os descriptor requests ones with a large array index and ones associated with null function pointer retrieval memory corruption might occur publish date url a href cvss score details base score metrics exploitability metrics attack vector physical attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
318,510 | 9,693,636,613 | IssuesEvent | 2019-05-24 16:36:54 | mono/monodevelop | https://api.github.com/repos/mono/monodevelop | closed | Crash on trying to open solution from start window | Area: IDE Platform\Start Window high-priority regression vs-sync | Build Information
Release ID: 801002578
Git revision: a79542bdc4aba2fe7ea8589b8bff6ea239853078
Build date: 2019-05-24 08:54:27+00
Build branch: release-8.1
Xamarin extensions: b894e02a8f68200720b84feb210215a3c1c2dc66
Clicking a solution on the start window terminates VS Mac.
```
FATAL ERROR [2019-05-24 11:37:54Z]: Visual Studio failed to start. Some of the assemblies required to run Visual Studio (for example gtk-sharp)may not be properly installed in the GAC.
System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'GetToCodeMainPageView'.
at Foundation.NSObject.get_SuperHandle () [0x0005b] in /Library/Frameworks/Xamarin.Mac.framework/Versions/5.6.0.25/src/Xamarin.Mac/Foundation/NSObject2.cs:458
at AppKit.NSView.RegisterForDraggedTypes (System.String[] newTypes) [0x00047] in /Library/Frameworks/Xamarin.Mac.framework/Versions/5.6.0.25/src/Xamarin.Mac/AppKit/NSView.g.cs:4148
at Xamarin.Ide.GetToCode.GetToCodeMainPageView.ViewDidMoveToSuperview () [0x00000] in /Users/vsts/agent/2.150.3/work/1/s/md-addins/Xamarin.Ide/Xamarin.Ide/Xamarin.Ide.GetToCode/GetToCodeMainPageView.cs:195
at (wrapper managed-to-native) Gtk.Application.gtk_main()
at Gtk.Application.Run () [0x00001] in /Users/builder/jenkins/workspace/build-package-osx-mono/2018-08/external/bockbuild/builds/gtk-sharp-None/gtk/Application.cs:145
at MonoDevelop.Ide.IdeStartup.Run (MonoDevelop.Ide.MonoDevelopOptions options) [0x00455] in /Users/vsts/agent/2.150.3/work/1/s/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide/IdeStartup.cs:221
at MonoDevelop.Ide.IdeStartup.Main (System.String[] args, MonoDevelop.Ide.Extensions.IdeCustomizer customizer) [0x0009e] in /Users/vsts/agent/2.150.3/work/1/s/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide/IdeStartup.cs:729
```
> VS bug [#899164](https://devdiv.visualstudio.com/DevDiv/_workitems/edit/899164) | 1.0 | Crash on trying to open solution from start window - Build Information
Release ID: 801002578
Git revision: a79542bdc4aba2fe7ea8589b8bff6ea239853078
Build date: 2019-05-24 08:54:27+00
Build branch: release-8.1
Xamarin extensions: b894e02a8f68200720b84feb210215a3c1c2dc66
Clicking a solution on the start window terminates VS Mac.
```
FATAL ERROR [2019-05-24 11:37:54Z]: Visual Studio failed to start. Some of the assemblies required to run Visual Studio (for example gtk-sharp)may not be properly installed in the GAC.
System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'GetToCodeMainPageView'.
at Foundation.NSObject.get_SuperHandle () [0x0005b] in /Library/Frameworks/Xamarin.Mac.framework/Versions/5.6.0.25/src/Xamarin.Mac/Foundation/NSObject2.cs:458
at AppKit.NSView.RegisterForDraggedTypes (System.String[] newTypes) [0x00047] in /Library/Frameworks/Xamarin.Mac.framework/Versions/5.6.0.25/src/Xamarin.Mac/AppKit/NSView.g.cs:4148
at Xamarin.Ide.GetToCode.GetToCodeMainPageView.ViewDidMoveToSuperview () [0x00000] in /Users/vsts/agent/2.150.3/work/1/s/md-addins/Xamarin.Ide/Xamarin.Ide/Xamarin.Ide.GetToCode/GetToCodeMainPageView.cs:195
at (wrapper managed-to-native) Gtk.Application.gtk_main()
at Gtk.Application.Run () [0x00001] in /Users/builder/jenkins/workspace/build-package-osx-mono/2018-08/external/bockbuild/builds/gtk-sharp-None/gtk/Application.cs:145
at MonoDevelop.Ide.IdeStartup.Run (MonoDevelop.Ide.MonoDevelopOptions options) [0x00455] in /Users/vsts/agent/2.150.3/work/1/s/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide/IdeStartup.cs:221
at MonoDevelop.Ide.IdeStartup.Main (System.String[] args, MonoDevelop.Ide.Extensions.IdeCustomizer customizer) [0x0009e] in /Users/vsts/agent/2.150.3/work/1/s/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide/IdeStartup.cs:729
```
> VS bug [#899164](https://devdiv.visualstudio.com/DevDiv/_workitems/edit/899164) | priority | crash on trying to open solution from start window build information release id git revision build date build branch release xamarin extensions clicking a solution on the start window terminates vs mac fatal error visual studio failed to start some of the assemblies required to run visual studio for example gtk sharp may not be properly installed in the gac system objectdisposedexception cannot access a disposed object object name gettocodemainpageview at foundation nsobject get superhandle in library frameworks xamarin mac framework versions src xamarin mac foundation cs at appkit nsview registerfordraggedtypes system string newtypes in library frameworks xamarin mac framework versions src xamarin mac appkit nsview g cs at xamarin ide gettocode gettocodemainpageview viewdidmovetosuperview in users vsts agent work s md addins xamarin ide xamarin ide xamarin ide gettocode gettocodemainpageview cs at wrapper managed to native gtk application gtk main at gtk application run in users builder jenkins workspace build package osx mono external bockbuild builds gtk sharp none gtk application cs at monodevelop ide idestartup run monodevelop ide monodevelopoptions options in users vsts agent work s monodevelop main src core monodevelop ide monodevelop ide idestartup cs at monodevelop ide idestartup main system string args monodevelop ide extensions idecustomizer customizer in users vsts agent work s monodevelop main src core monodevelop ide monodevelop ide idestartup cs vs bug | 1 |
84,032 | 7,888,072,015 | IssuesEvent | 2018-06-27 20:42:48 | rancher/rancher | https://api.github.com/repos/rancher/rancher | closed | 2.0.0: kubectl version in Launch kubectl does not match cluster | area/agent kind/enhancement status/resolved status/to-test version/2.0 | kubectl version when launched from UI does not match the version of the cluster.
Expected output:
> kubectl version --short
Client Version: v1.9.7
Server Version: v1.9.7
Actual:
# Run kubectl commands inside here
# e.g. kubectl get all
> kubectl version --short
Client Version: v1.8.9-rancher1
Server Version: v1.9.7
**Rancher versions:**
rancher/server or rancher/rancher: v2.0.0
rancher/agent or rancher/rancher-agent: v2.0.0
**Infrastructure Stack versions:**
healthcheck:
ipsec:
network-services:
scheduler:
kubernetes (if applicable):
Client Version: version.Info{Major:"1", Minor:"8+", GitVersion:"v1.8.9-rancher1", GitCommit:"68595e18f25e24125244e9966b1e5468a98c1cd4", GitTreeState:"clean", BuildDate:"2018-03-13T04:51:52Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.7", GitCommit:"dd5e1a2978fd0b97d9b78e1564398aeea7e7fe92", GitTreeState:"clean", BuildDate:"2018-04-18T23:58:35Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
**Docker version: (`docker version`,`docker info` preferred)**
docker version
Client:
Version: 1.13.1
API version: 1.26
Package version: <unknown>
Go version: go1.8.3
Git commit: 774336d/1.13.1
Built: Wed Mar 7 17:06:16 2018
OS/Arch: linux/amd64
Server:
Version: 1.13.1
API version: 1.26 (minimum version 1.12)
Package version: <unknown>
Go version: go1.8.3
Git commit: 774336d/1.13.1
Built: Wed Mar 7 17:06:16 2018
OS/Arch: linux/amd64
Experimental: true
docker info
Containers: 40
Running: 26
Paused: 0
Stopped: 14
Images: 26
Server Version: 1.13.1
Storage Driver: overlay2
Backing Filesystem: xfs
Supports d_type: false
Native Overlay Diff: true
Logging Driver: journald
Cgroup Driver: systemd
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Swarm: inactive
Runtimes: docker-runc runc
Default Runtime: docker-runc
Init Binary: docker-init
containerd version: (expected: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1)
runc version: N/A (expected: 9df8b306d01f59d3a8029be411de015b7304dd8f)
init version: N/A (expected: 949e6facb77383876aeff8a6944dde66b3089574)
Security Options:
seccomp
WARNING: You're not using the default seccomp profile
Profile: /etc/docker/seccomp.json
Kernel Version: 3.10.0-693.21.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 3
CPUs: 4
Total Memory: 7.639 GiB
Name: se-centos-bjma-k8s
ID: BFUC:COHW:AKSO:ODQT:A63I:NH75:HJKA:UQWA:JRG4:N47F:HNMO:HBL3
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 151
Goroutines: 151
System Time: 2018-05-17T12:33:10.308006117+02:00
EventsListeners: 0
**Operating system and kernel: (`cat /etc/os-release`, `uname -r` preferred)**
cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"
uname -r
3.10.0-693.21.1.el7.x86_64
**Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)**
Bare metal / VM. Custom cluster used
**Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)**
Single node Rancher
**Environment Template: (Cattle/Kubernetes/Swarm/Mesos)**
**Steps to Reproduce:**
**Results:**
| 1.0 | 2.0.0: kubectl version in Launch kubectl does not match cluster - kubectl version when launched from UI does not match the version of the cluster.
Expected output:
> kubectl version --short
Client Version: v1.9.7
Server Version: v1.9.7
Actual:
# Run kubectl commands inside here
# e.g. kubectl get all
> kubectl version --short
Client Version: v1.8.9-rancher1
Server Version: v1.9.7
**Rancher versions:**
rancher/server or rancher/rancher: v2.0.0
rancher/agent or rancher/rancher-agent: v2.0.0
**Infrastructure Stack versions:**
healthcheck:
ipsec:
network-services:
scheduler:
kubernetes (if applicable):
Client Version: version.Info{Major:"1", Minor:"8+", GitVersion:"v1.8.9-rancher1", GitCommit:"68595e18f25e24125244e9966b1e5468a98c1cd4", GitTreeState:"clean", BuildDate:"2018-03-13T04:51:52Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.7", GitCommit:"dd5e1a2978fd0b97d9b78e1564398aeea7e7fe92", GitTreeState:"clean", BuildDate:"2018-04-18T23:58:35Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
**Docker version: (`docker version`,`docker info` preferred)**
docker version
Client:
Version: 1.13.1
API version: 1.26
Package version: <unknown>
Go version: go1.8.3
Git commit: 774336d/1.13.1
Built: Wed Mar 7 17:06:16 2018
OS/Arch: linux/amd64
Server:
Version: 1.13.1
API version: 1.26 (minimum version 1.12)
Package version: <unknown>
Go version: go1.8.3
Git commit: 774336d/1.13.1
Built: Wed Mar 7 17:06:16 2018
OS/Arch: linux/amd64
Experimental: true
docker info
Containers: 40
Running: 26
Paused: 0
Stopped: 14
Images: 26
Server Version: 1.13.1
Storage Driver: overlay2
Backing Filesystem: xfs
Supports d_type: false
Native Overlay Diff: true
Logging Driver: journald
Cgroup Driver: systemd
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Swarm: inactive
Runtimes: docker-runc runc
Default Runtime: docker-runc
Init Binary: docker-init
containerd version: (expected: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1)
runc version: N/A (expected: 9df8b306d01f59d3a8029be411de015b7304dd8f)
init version: N/A (expected: 949e6facb77383876aeff8a6944dde66b3089574)
Security Options:
seccomp
WARNING: You're not using the default seccomp profile
Profile: /etc/docker/seccomp.json
Kernel Version: 3.10.0-693.21.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 3
CPUs: 4
Total Memory: 7.639 GiB
Name: se-centos-bjma-k8s
ID: BFUC:COHW:AKSO:ODQT:A63I:NH75:HJKA:UQWA:JRG4:N47F:HNMO:HBL3
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 151
Goroutines: 151
System Time: 2018-05-17T12:33:10.308006117+02:00
EventsListeners: 0
**Operating system and kernel: (`cat /etc/os-release`, `uname -r` preferred)**
cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"
uname -r
3.10.0-693.21.1.el7.x86_64
**Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)**
Bare metal / VM. Custom cluster used
**Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)**
Single node Rancher
**Environment Template: (Cattle/Kubernetes/Swarm/Mesos)**
**Steps to Reproduce:**
**Results:**
| non_priority | kubectl version in launch kubectl does not match cluster kubectl version when launched from ui does not match the version of the cluster expected output kubectl version short client version server version actual run kubectl commands inside here e g kubectl get all kubectl version short client version server version rancher versions rancher server or rancher rancher rancher agent or rancher rancher agent infrastructure stack versions healthcheck ipsec network services scheduler kubernetes if applicable client version version info major minor gitversion gitcommit gittreestate clean builddate goversion compiler gc platform linux server version version info major minor gitversion gitcommit gittreestate clean builddate goversion compiler gc platform linux docker version docker version docker info preferred docker version client version api version package version go version git commit built wed mar os arch linux server version api version minimum version package version go version git commit built wed mar os arch linux experimental true docker info containers running paused stopped images server version storage driver backing filesystem xfs supports d type false native overlay diff true logging driver journald cgroup driver systemd plugins volume local network bridge host ipvlan macvlan null overlay swarm inactive runtimes docker runc runc default runtime docker runc init binary docker init containerd version expected runc version n a expected init version n a expected security options seccomp warning you re not using the default seccomp profile profile etc docker seccomp json kernel version operating system centos linux core ostype linux architecture number of docker hooks cpus total memory gib name se centos bjma id bfuc cohw akso odqt hjka uqwa hnmo docker root dir var lib docker debug mode client false debug mode server true file descriptors goroutines system time eventslisteners operating system and kernel cat etc os release uname r preferred cat etc os release name centos linux version core id centos id like rhel fedora version id pretty name centos linux core ansi color cpe name cpe o centos centos home url bug report url centos mantisbt project centos centos mantisbt project version redhat support product centos redhat support product version uname r type provider of hosts virtualbox bare metal aws gce do bare metal vm custom cluster used setup details single node rancher vs ha rancher internal db vs external db single node rancher environment template cattle kubernetes swarm mesos steps to reproduce results | 0 |
48,699 | 2,999,471,771 | IssuesEvent | 2015-07-23 19:12:11 | jayway/powermock | https://api.github.com/repos/jayway/powermock | closed | OSGi-ify PowerMock | enhancement imported Milestone-Release1.6 Priority-Low | _From [lukewpat...@gmail.com](https://code.google.com/u/115628002144849920714/) on November 13, 2009 20:06:39_
Please add OSGi metadata to manifest files. This will allow in-container
testing with PowerMock.
_Original issue: http://code.google.com/p/powermock/issues/detail?id=204_ | 1.0 | OSGi-ify PowerMock - _From [lukewpat...@gmail.com](https://code.google.com/u/115628002144849920714/) on November 13, 2009 20:06:39_
Please add OSGi metadata to manifest files. This will allow in-container
testing with PowerMock.
_Original issue: http://code.google.com/p/powermock/issues/detail?id=204_ | priority | osgi ify powermock from on november please add osgi metadata to manifest files this will allow in container testing with powermock original issue | 1 |
220,932 | 7,372,306,900 | IssuesEvent | 2018-03-13 14:26:32 | TMats/survey | https://api.github.com/repos/TMats/survey | closed | Learning by Playing - Solving Sparse Reward Tasks from Scratch | Priority: High RL | https://arxiv.org/abs/1802.10567
- Martin Riedmiller, Roland Hafner, Thomas Lampe, Michael Neunert, Jonas Degrave, Tom Van de Wiele, Volodymyr Mnih, Nicolas Heess, Jost Tobias Springenberg
- Submitted on 28 Feb 2018 | 1.0 | Learning by Playing - Solving Sparse Reward Tasks from Scratch - https://arxiv.org/abs/1802.10567
- Martin Riedmiller, Roland Hafner, Thomas Lampe, Michael Neunert, Jonas Degrave, Tom Van de Wiele, Volodymyr Mnih, Nicolas Heess, Jost Tobias Springenberg
- Submitted on 28 Feb 2018 | priority | learning by playing solving sparse reward tasks from scratch martin riedmiller roland hafner thomas lampe michael neunert jonas degrave tom van de wiele volodymyr mnih nicolas heess jost tobias springenberg submitted on feb | 1 |
7,656 | 2,919,649,850 | IssuesEvent | 2015-06-24 15:09:39 | php-coder/mystamps | https://api.github.com/repos/php-coder/mystamps | opened | Test that Togglz is working | integration tests | In commit 69214f44d9b47e106803c0c826bc1a509d3d3508 I've fixed Togglz that didn't work. To avoid such breakage we need a test for this case.
I suggest to add special feature that is always disabled. On any page we will show special message if this feature is active. Our test will just check that this message doesn't exist. | 1.0 | Test that Togglz is working - In commit 69214f44d9b47e106803c0c826bc1a509d3d3508 I've fixed Togglz that didn't work. To avoid such breakage we need a test for this case.
I suggest to add special feature that is always disabled. On any page we will show special message if this feature is active. Our test will just check that this message doesn't exist. | non_priority | test that togglz is working in commit i ve fixed togglz that didn t work to avoid such breakage we need a test for this case i suggest to add special feature that is always disabled on any page we will show special message if this feature is active our test will just check that this message doesn t exist | 0 |
289,623 | 31,991,433,732 | IssuesEvent | 2023-09-21 06:13:08 | pazhanivel07/frameworks_av_AOSP_10_r33_CVE-2023-35687_CVE-2023-35679 | https://api.github.com/repos/pazhanivel07/frameworks_av_AOSP_10_r33_CVE-2023-35687_CVE-2023-35679 | opened | CVE-2022-20393 (Medium) detected in avandroid-9.0.0_r56 | Mend: dependency security vulnerability | ## CVE-2022-20393 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>avandroid-9.0.0_r56</b></p></summary>
<p>
<p>Library home page: <a href=https://android.googlesource.com/platform/frameworks/av>https://android.googlesource.com/platform/frameworks/av</a></p>
<p>Found in HEAD commit: <a href="https://github.com/pazhanivel07/frameworks_av_AOSP_10_r33_CVE-2023-35687_CVE-2023-35679/commit/f6c68d1f56234bf68c91ea85f355b0612cd36a2b">f6c68d1f56234bf68c91ea85f355b0612cd36a2b</a></p>
<p>Found in base branch: <b>main</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/media/libstagefright/timedtext/TextDescriptions.cpp</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>
In extract3GPPGlobalDescriptions of TextDescriptions.cpp, there is a possible out of bounds read due to an integer overflow. This could lead to local information disclosure from the media server with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-12 Android-12LAndroid ID: A-233735886
<p>Publish Date: 2022-09-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-20393>CVE-2022-20393</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: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://source.android.com/docs/security/bulletin/2022-09-01">https://source.android.com/docs/security/bulletin/2022-09-01</a></p>
<p>Release Date: 2022-09-13</p>
<p>Fix Resolution: android-13.0.0_r1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-20393 (Medium) detected in avandroid-9.0.0_r56 - ## CVE-2022-20393 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>avandroid-9.0.0_r56</b></p></summary>
<p>
<p>Library home page: <a href=https://android.googlesource.com/platform/frameworks/av>https://android.googlesource.com/platform/frameworks/av</a></p>
<p>Found in HEAD commit: <a href="https://github.com/pazhanivel07/frameworks_av_AOSP_10_r33_CVE-2023-35687_CVE-2023-35679/commit/f6c68d1f56234bf68c91ea85f355b0612cd36a2b">f6c68d1f56234bf68c91ea85f355b0612cd36a2b</a></p>
<p>Found in base branch: <b>main</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/media/libstagefright/timedtext/TextDescriptions.cpp</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>
In extract3GPPGlobalDescriptions of TextDescriptions.cpp, there is a possible out of bounds read due to an integer overflow. This could lead to local information disclosure from the media server with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-12 Android-12LAndroid ID: A-233735886
<p>Publish Date: 2022-09-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-20393>CVE-2022-20393</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: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://source.android.com/docs/security/bulletin/2022-09-01">https://source.android.com/docs/security/bulletin/2022-09-01</a></p>
<p>Release Date: 2022-09-13</p>
<p>Fix Resolution: android-13.0.0_r1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in avandroid cve medium severity vulnerability vulnerable library avandroid library home page a href found in head commit a href found in base branch main vulnerable source files media libstagefright timedtext textdescriptions cpp vulnerability details in of textdescriptions cpp there is a possible out of bounds read due to an integer overflow this could lead to local information disclosure from the media server with no additional execution privileges needed user interaction is not needed for exploitation product androidversions android android android id a publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution android step up your open source security game with mend | 0 |
44,655 | 2,910,342,665 | IssuesEvent | 2015-06-21 17:17:08 | Metaswitch/sprout | https://api.github.com/repos/Metaswitch/sprout | closed | Sprout loops ACKs to itself after responding with 503 to an INVITE | high-priority | After Sprout returns a 503 for an INVITE due to overload controls, it begins looping ACKs to itself until Max-Forwards has "expired". This additional processing triggers a LIR over the Cx for each ACK which adds to system latency, thereby "reinforcing" the overload condition (the overload was initially caused by Cx interface latency). A SAS trace has been collected. | 1.0 | Sprout loops ACKs to itself after responding with 503 to an INVITE - After Sprout returns a 503 for an INVITE due to overload controls, it begins looping ACKs to itself until Max-Forwards has "expired". This additional processing triggers a LIR over the Cx for each ACK which adds to system latency, thereby "reinforcing" the overload condition (the overload was initially caused by Cx interface latency). A SAS trace has been collected. | priority | sprout loops acks to itself after responding with to an invite after sprout returns a for an invite due to overload controls it begins looping acks to itself until max forwards has expired this additional processing triggers a lir over the cx for each ack which adds to system latency thereby reinforcing the overload condition the overload was initially caused by cx interface latency a sas trace has been collected | 1 |
103,854 | 12,976,734,811 | IssuesEvent | 2020-07-21 19:19:42 | elastic/kibana | https://api.github.com/repos/elastic/kibana | opened | Custom CAs and SSL options | Team:Ingest Management design | **Summary of the problem**
Having secure communication between Elastic-Agent and elasticsearch or tier services requires to deal with SSL (TLS):
- **Certificate authorities (common):** when authenticating the server.
- **Certificate:** required when doing mutual authentication.
- **Certificate private key:** required when doing mutual authentication.
- **key_passphrase:** used to decode the private key.
- **verification_mode (advanced)**: Control how the client verifies the server.
- **supported protocol (advanced):** define which version of TLS to use.
- **cipher_suites (advanced):** Define which cipher is supported, required in some lock down environment.
- **curve_types (advanced):** Define which ECDH curve to use.
- **renegotiation (advanced):** Configure TLS renegotiation
- **client_authentication (advanced):** Configure client authentication.
For a complete list of types see [Filebeat](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-ssl.html#_client_authentication) documentation.
The Certificate authorities, Certificate and certificate private key are more often files or blob of text.
It's also common to be able to reuse the artifacts on multiples integrations or outputs, and its convenient to
only have to update a single file on disk.
User stories:
* As a Fleet administrator I should be able to define the Certificate Authorities, Certificate and the private key on outputs.
* As a fleet administrator I should be able to define the Certificate Authorities, Certificate and the private key on integrations that require it.
* As fleet administrator I should be able to define SSL options.
| 1.0 | Custom CAs and SSL options - **Summary of the problem**
Having secure communication between Elastic-Agent and elasticsearch or tier services requires to deal with SSL (TLS):
- **Certificate authorities (common):** when authenticating the server.
- **Certificate:** required when doing mutual authentication.
- **Certificate private key:** required when doing mutual authentication.
- **key_passphrase:** used to decode the private key.
- **verification_mode (advanced)**: Control how the client verifies the server.
- **supported protocol (advanced):** define which version of TLS to use.
- **cipher_suites (advanced):** Define which cipher is supported, required in some lock down environment.
- **curve_types (advanced):** Define which ECDH curve to use.
- **renegotiation (advanced):** Configure TLS renegotiation
- **client_authentication (advanced):** Configure client authentication.
For a complete list of types see [Filebeat](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-ssl.html#_client_authentication) documentation.
The Certificate authorities, Certificate and certificate private key are more often files or blob of text.
It's also common to be able to reuse the artifacts on multiples integrations or outputs, and its convenient to
only have to update a single file on disk.
User stories:
* As a Fleet administrator I should be able to define the Certificate Authorities, Certificate and the private key on outputs.
* As a fleet administrator I should be able to define the Certificate Authorities, Certificate and the private key on integrations that require it.
* As fleet administrator I should be able to define SSL options.
| non_priority | custom cas and ssl options summary of the problem having secure communication between elastic agent and elasticsearch or tier services requires to deal with ssl tls certificate authorities common when authenticating the server certificate required when doing mutual authentication certificate private key required when doing mutual authentication key passphrase used to decode the private key verification mode advanced control how the client verifies the server supported protocol advanced define which version of tls to use cipher suites advanced define which cipher is supported required in some lock down environment curve types advanced define which ecdh curve to use renegotiation advanced configure tls renegotiation client authentication advanced configure client authentication for a complete list of types see documentation the certificate authorities certificate and certificate private key are more often files or blob of text it s also common to be able to reuse the artifacts on multiples integrations or outputs and its convenient to only have to update a single file on disk user stories as a fleet administrator i should be able to define the certificate authorities certificate and the private key on outputs as a fleet administrator i should be able to define the certificate authorities certificate and the private key on integrations that require it as fleet administrator i should be able to define ssl options | 0 |
104,606 | 4,215,501,064 | IssuesEvent | 2016-06-30 04:34:49 | diamm/diamm | https://api.github.com/repos/diamm/diamm | closed | Figure out how to migrate old users to new site | Component: User Interface Component: Web Application Priority: High Status: In Progress Type: Enhancement | Conversation with Arielle:
The login form will only display the username / e-mail to log in at first. It will then use the information in there to tell what the rest of the form should look like:
1. If the user has logged in to the new site before, show a password prompt.
2. If the username was in the old database but they have never logged in, it should show a 'request new password' link to send an e-mail to them to reset their password.
3. If the username or e-mail does not exist in the new site, show a 'create new account' link, or offer them the chance to correct their username or e-mail and try again. | 1.0 | Figure out how to migrate old users to new site - Conversation with Arielle:
The login form will only display the username / e-mail to log in at first. It will then use the information in there to tell what the rest of the form should look like:
1. If the user has logged in to the new site before, show a password prompt.
2. If the username was in the old database but they have never logged in, it should show a 'request new password' link to send an e-mail to them to reset their password.
3. If the username or e-mail does not exist in the new site, show a 'create new account' link, or offer them the chance to correct their username or e-mail and try again. | priority | figure out how to migrate old users to new site conversation with arielle the login form will only display the username e mail to log in at first it will then use the information in there to tell what the rest of the form should look like if the user has logged in to the new site before show a password prompt if the username was in the old database but they have never logged in it should show a request new password link to send an e mail to them to reset their password if the username or e mail does not exist in the new site show a create new account link or offer them the chance to correct their username or e mail and try again | 1 |
163,885 | 25,892,510,990 | IssuesEvent | 2022-12-14 19:12:51 | GCTC-NTGC/gc-digital-talent | https://api.github.com/repos/GCTC-NTGC/gc-digital-talent | closed | Display referral path on /not-found page | design | <sup>ℹ️ [Figma (root)][figma] | [Sitemap][sitemap]</sup>
<sup>_This initial comment is collaborative and open to modification by all._</sup>
Spin-off from: https://github.com/GCTC-NTGC/gc-digital-talent/issues/1904
On 404/not-found page, we should show the referral page we redirected from when it's available. This will help with support requests when ppl arrive on this page.
## Description
## Screenshot: Prototype
(needs to be updated with updated design)
<img width="934" alt="Screen Shot 2022-10-06 at 4 05 29 PM" src="https://user-images.githubusercontent.com/305339/194354368-f0882ad1-45b2-47d4-aef3-9e0fb0cbc42a.png">
<sup>[Click screenshot to visit Figma.][image-link]</sup>
## Acceptance Criteria
- [ ] show referral url when referred from within app
- [ ] hide referral url when not available (apache redirect?)
- [ ] make URL monospaced and with copy helper
<!-- Links -->
[image]: https://user-images.githubusercontent.com/305339/166570935-6425a615-82c7-4b2f-9840-5c7d698fa2ab.png
[image-link]: https://example.com
[figma]: https://go.talent.c4nada.ca/figma
[sitemap]: https://go.talent.c4nada.ca/sitemap
<!-- Find your prototype via https://go.talent.c4nada.ca/figma and click "play button" ▷ in top-right. -->
| 1.0 | Display referral path on /not-found page - <sup>ℹ️ [Figma (root)][figma] | [Sitemap][sitemap]</sup>
<sup>_This initial comment is collaborative and open to modification by all._</sup>
Spin-off from: https://github.com/GCTC-NTGC/gc-digital-talent/issues/1904
On 404/not-found page, we should show the referral page we redirected from when it's available. This will help with support requests when ppl arrive on this page.
## Description
## Screenshot: Prototype
(needs to be updated with updated design)
<img width="934" alt="Screen Shot 2022-10-06 at 4 05 29 PM" src="https://user-images.githubusercontent.com/305339/194354368-f0882ad1-45b2-47d4-aef3-9e0fb0cbc42a.png">
<sup>[Click screenshot to visit Figma.][image-link]</sup>
## Acceptance Criteria
- [ ] show referral url when referred from within app
- [ ] hide referral url when not available (apache redirect?)
- [ ] make URL monospaced and with copy helper
<!-- Links -->
[image]: https://user-images.githubusercontent.com/305339/166570935-6425a615-82c7-4b2f-9840-5c7d698fa2ab.png
[image-link]: https://example.com
[figma]: https://go.talent.c4nada.ca/figma
[sitemap]: https://go.talent.c4nada.ca/sitemap
<!-- Find your prototype via https://go.talent.c4nada.ca/figma and click "play button" ▷ in top-right. -->
| non_priority | display referral path on not found page ℹ️ this initial comment is collaborative and open to modification by all spin off from on not found page we should show the referral page we redirected from when it s available this will help with support requests when ppl arrive on this page description screenshot prototype needs to be updated with updated design img width alt screen shot at pm src acceptance criteria show referral url when referred from within app hide referral url when not available apache redirect make url monospaced and with copy helper | 0 |
255,595 | 19,309,377,323 | IssuesEvent | 2021-12-13 14:49:20 | moonD4rk/HackBrowserData | https://api.github.com/repos/moonD4rk/HackBrowserData | closed | [Improvement] CHANGELOG | documentation | Hi,
would be awesome if you could also establish a file for the CHANGELOG with all the (great) frequent changes of each version.
I think it would be helpful for everyone to track what is and has happened. | 1.0 | [Improvement] CHANGELOG - Hi,
would be awesome if you could also establish a file for the CHANGELOG with all the (great) frequent changes of each version.
I think it would be helpful for everyone to track what is and has happened. | non_priority | changelog hi would be awesome if you could also establish a file for the changelog with all the great frequent changes of each version i think it would be helpful for everyone to track what is and has happened | 0 |
494,566 | 14,260,592,201 | IssuesEvent | 2020-11-20 10:02:55 | openmsupply/mobile | https://api.github.com/repos/openmsupply/mobile | closed | Odd modal spacing when opening while keyboard is open | Bug: production Docs: not needed Effort: small Good first issue Priority: normal | ## Describe the bug
When opening a modal (i.e. clicking finalize, or any other action which opens a modal whether it is in requisitions or stocktakes), if the keyboard is opening when the modal is mounted, the spacing is odd forcing the vertical height downward
### To reproduce
Steps to reproduce the behavior:
1. Go to requisition / stocktakes
2. Click on a cell to open the keyboard
3. Press Finalize
4. See error
### Expected behaviour
The modal should always be consistent
### Version and device info
- App version: 2.3.4
- Tablet model: Lenovo Tab4 10
### Additional context
N/A
| 1.0 | Odd modal spacing when opening while keyboard is open - ## Describe the bug
When opening a modal (i.e. clicking finalize, or any other action which opens a modal whether it is in requisitions or stocktakes), if the keyboard is opening when the modal is mounted, the spacing is odd forcing the vertical height downward
### To reproduce
Steps to reproduce the behavior:
1. Go to requisition / stocktakes
2. Click on a cell to open the keyboard
3. Press Finalize
4. See error
### Expected behaviour
The modal should always be consistent
### Version and device info
- App version: 2.3.4
- Tablet model: Lenovo Tab4 10
### Additional context
N/A
| priority | odd modal spacing when opening while keyboard is open describe the bug when opening a modal i e clicking finalize or any other action which opens a modal whether it is in requisitions or stocktakes if the keyboard is opening when the modal is mounted the spacing is odd forcing the vertical height downward to reproduce steps to reproduce the behavior go to requisition stocktakes click on a cell to open the keyboard press finalize see error expected behaviour the modal should always be consistent version and device info app version tablet model lenovo additional context n a | 1 |
155,713 | 12,267,916,623 | IssuesEvent | 2020-05-07 11:35:01 | wopian/kitsu | https://api.github.com/repos/wopian/kitsu | closed | serialise depends on binded this (missing pluralize dependency) | bug kitsu-core test | Unable to serialise data using `kitsu-core` as a standalone - tests did not pick this up as they're pre-bound in the specs for each bind combination.
Should fallback to requiring `pluralize` if `this.plural` is not a function
Ref: https://codepen.io/wopian/pen/KQZwzq (console) | 1.0 | serialise depends on binded this (missing pluralize dependency) - Unable to serialise data using `kitsu-core` as a standalone - tests did not pick this up as they're pre-bound in the specs for each bind combination.
Should fallback to requiring `pluralize` if `this.plural` is not a function
Ref: https://codepen.io/wopian/pen/KQZwzq (console) | non_priority | serialise depends on binded this missing pluralize dependency unable to serialise data using kitsu core as a standalone tests did not pick this up as they re pre bound in the specs for each bind combination should fallback to requiring pluralize if this plural is not a function ref console | 0 |
298,471 | 22,500,774,530 | IssuesEvent | 2022-06-23 11:37:54 | BrainsOnBoard/python-gm-plotting | https://api.github.com/repos/BrainsOnBoard/python-gm-plotting | opened | Add a readme file and other documentation | documentation | It would also be useful to have instructions on how to get set up with a proper Google account so that the user can obtain satellite images. | 1.0 | Add a readme file and other documentation - It would also be useful to have instructions on how to get set up with a proper Google account so that the user can obtain satellite images. | non_priority | add a readme file and other documentation it would also be useful to have instructions on how to get set up with a proper google account so that the user can obtain satellite images | 0 |
753,373 | 26,345,513,442 | IssuesEvent | 2023-01-10 21:40:00 | yugabyte/yugabyte-db | https://api.github.com/repos/yugabyte/yugabyte-db | closed | [Platform] [docdb] Validate gflags and raise error if any are invalid | kind/enhancement area/docdb priority/high status/awaiting-triage | Jira Link: [DB-4733](https://yugabyte.atlassian.net/browse/DB-4733)
If the admin is setting gflags, an error should be raised if any of the entered gflags are invalid (like a typo in the gflag name). I guess the validation needs to be done by docdb and the error propagated to YW | 1.0 | [Platform] [docdb] Validate gflags and raise error if any are invalid - Jira Link: [DB-4733](https://yugabyte.atlassian.net/browse/DB-4733)
If the admin is setting gflags, an error should be raised if any of the entered gflags are invalid (like a typo in the gflag name). I guess the validation needs to be done by docdb and the error propagated to YW | priority | validate gflags and raise error if any are invalid jira link if the admin is setting gflags an error should be raised if any of the entered gflags are invalid like a typo in the gflag name i guess the validation needs to be done by docdb and the error propagated to yw | 1 |
751,631 | 26,251,584,088 | IssuesEvent | 2023-01-05 19:50:19 | googleapis/google-api-go-client | https://api.github.com/repos/googleapis/google-api-go-client | closed | bigquery: How to mock for unit testing | type: question api: bigquery priority: p3 | Hey, I'm trying to mock bigquery Client, but I didn't find a good solution for that.
- https://github.com/googleapis/google-cloud-go-testing it sounds interesting the way but it's outdated and lots of methods have not been updated and the project has been archived recently
- [sample 1 ](https://github.com/GoogleCloudPlatform/golang-samples/blob/main/bigquery/simpleapp/simpleapp_test.go) it's using the real client with just a sample project that is not what I wanted
is there any sample or way to mock bigquery client for unittesting?
| 1.0 | bigquery: How to mock for unit testing - Hey, I'm trying to mock bigquery Client, but I didn't find a good solution for that.
- https://github.com/googleapis/google-cloud-go-testing it sounds interesting the way but it's outdated and lots of methods have not been updated and the project has been archived recently
- [sample 1 ](https://github.com/GoogleCloudPlatform/golang-samples/blob/main/bigquery/simpleapp/simpleapp_test.go) it's using the real client with just a sample project that is not what I wanted
is there any sample or way to mock bigquery client for unittesting?
| priority | bigquery how to mock for unit testing hey i m trying to mock bigquery client but i didn t find a good solution for that it sounds interesting the way but it s outdated and lots of methods have not been updated and the project has been archived recently it s using the real client with just a sample project that is not what i wanted is there any sample or way to mock bigquery client for unittesting | 1 |
463,235 | 13,262,068,062 | IssuesEvent | 2020-08-20 21:02:40 | OregonDigital/OD2 | https://api.github.com/repos/OregonDigital/OD2 | reopened | FetchGraphWorker overrides metadata labels as it indexes | Bug Features Priority - High | ### Descriptive summary
As FetchGraphWorker works through the metadata values for a single field, it's clobbering the values it JUST sent to Solr.
https://github.com/OregonDigital/OD2/blob/master/app/workers/fetch_graph_worker.rb#L42-L46
These values need to be initialized to an empty array, then appended to each iteration.
This is also true of the FetchFailedGraphWorker.
### Expected behavior
Works reindexed through the Fetch(Failed)GraphWorker has all labels associated with all metadata values for each metadata field indexed into Solr, not just the last one.
### Related work
#1224 Caused issue
### Accessibility Concerns
| 1.0 | FetchGraphWorker overrides metadata labels as it indexes - ### Descriptive summary
As FetchGraphWorker works through the metadata values for a single field, it's clobbering the values it JUST sent to Solr.
https://github.com/OregonDigital/OD2/blob/master/app/workers/fetch_graph_worker.rb#L42-L46
These values need to be initialized to an empty array, then appended to each iteration.
This is also true of the FetchFailedGraphWorker.
### Expected behavior
Works reindexed through the Fetch(Failed)GraphWorker has all labels associated with all metadata values for each metadata field indexed into Solr, not just the last one.
### Related work
#1224 Caused issue
### Accessibility Concerns
| priority | fetchgraphworker overrides metadata labels as it indexes descriptive summary as fetchgraphworker works through the metadata values for a single field it s clobbering the values it just sent to solr these values need to be initialized to an empty array then appended to each iteration this is also true of the fetchfailedgraphworker expected behavior works reindexed through the fetch failed graphworker has all labels associated with all metadata values for each metadata field indexed into solr not just the last one related work caused issue accessibility concerns | 1 |
27,052 | 21,055,851,157 | IssuesEvent | 2022-04-01 03:06:17 | google/pytype | https://api.github.com/repos/google/pytype | closed | Add `--platform` option | enhancement cat: infrastructure | As [per PEP 484](https://www.python.org/dev/peps/pep-0484/#version-and-platform-checking) type checkers are expected to understand simple version and platform checks, e.g.:
```python
if sys.version_info[0] >= 3:
# Python 3 specific definitions
if sys.platform == 'win32':
# Windows specific definitions
```
While the `pytype` CLI currently supports the flags `-V`, `--python-version` to change for which Python version the types are checked, there apparently is no such option to change for which OS platform the code is checked, instead `pytype` apparently always defaults to `linux`, with no option to change that:
https://github.com/google/pytype/blob/9a0f492875f8440627fef7de42ee9244e89e8a06/pytype/pyi/parser.py#L31
https://github.com/google/pytype/blob/9a0f492875f8440627fef7de42ee9244e89e8a06/pytype/pyi/parser.py#L704-L722
So I think it would make sense to introduce a `--platform` option to allow the checking for other platforms.
Both mypy and pyright provide such an option:
```
$ mypy -h | grep platform
--platform PLATFORM Type check special-cased code for the given OS
platform (defaults to sys.platform)
$ pyright -h | grep platform
--pythonplatform <PLATFORM> Analyze for a specific platform (Darwin, Linux, Windows)
``` | 1.0 | Add `--platform` option - As [per PEP 484](https://www.python.org/dev/peps/pep-0484/#version-and-platform-checking) type checkers are expected to understand simple version and platform checks, e.g.:
```python
if sys.version_info[0] >= 3:
# Python 3 specific definitions
if sys.platform == 'win32':
# Windows specific definitions
```
While the `pytype` CLI currently supports the flags `-V`, `--python-version` to change for which Python version the types are checked, there apparently is no such option to change for which OS platform the code is checked, instead `pytype` apparently always defaults to `linux`, with no option to change that:
https://github.com/google/pytype/blob/9a0f492875f8440627fef7de42ee9244e89e8a06/pytype/pyi/parser.py#L31
https://github.com/google/pytype/blob/9a0f492875f8440627fef7de42ee9244e89e8a06/pytype/pyi/parser.py#L704-L722
So I think it would make sense to introduce a `--platform` option to allow the checking for other platforms.
Both mypy and pyright provide such an option:
```
$ mypy -h | grep platform
--platform PLATFORM Type check special-cased code for the given OS
platform (defaults to sys.platform)
$ pyright -h | grep platform
--pythonplatform <PLATFORM> Analyze for a specific platform (Darwin, Linux, Windows)
``` | non_priority | add platform option as type checkers are expected to understand simple version and platform checks e g python if sys version info python specific definitions if sys platform windows specific definitions while the pytype cli currently supports the flags v python version to change for which python version the types are checked there apparently is no such option to change for which os platform the code is checked instead pytype apparently always defaults to linux with no option to change that so i think it would make sense to introduce a platform option to allow the checking for other platforms both mypy and pyright provide such an option mypy h grep platform platform platform type check special cased code for the given os platform defaults to sys platform pyright h grep platform pythonplatform analyze for a specific platform darwin linux windows | 0 |
583,846 | 17,399,767,336 | IssuesEvent | 2021-08-02 17:53:28 | ita-social-projects/TeachUA | https://api.github.com/repos/ita-social-projects/TeachUA | closed | [Редагування профілю] Wrong alignment of 'Змінити пароль' label | Priority: High UI bug | **Environment:** Windows 10, Google Chrome Version 92.0.4515.107 (Official Build) (64-bit
**Reproducible:** always
**Build found:** last commit
**Preconditions**
1. Go to https://speak-ukrainian.org.ua/dev/
2. Log in
**Steps to reproduce**
1. Go to 'Мій Профіль' page
2. Click on 'Редагувати профіль'
**Actual result**
Wrong alignment of 'Змінити пароль' label.
**Expected result**
**User story link**
User story #164 | 1.0 | [Редагування профілю] Wrong alignment of 'Змінити пароль' label - **Environment:** Windows 10, Google Chrome Version 92.0.4515.107 (Official Build) (64-bit
**Reproducible:** always
**Build found:** last commit
**Preconditions**
1. Go to https://speak-ukrainian.org.ua/dev/
2. Log in
**Steps to reproduce**
1. Go to 'Мій Профіль' page
2. Click on 'Редагувати профіль'
**Actual result**
Wrong alignment of 'Змінити пароль' label.
**Expected result**
**User story link**
User story #164 | priority | wrong alignment of змінити пароль label environment windows google chrome version official build bit reproducible always build found last commit preconditions go to log in steps to reproduce go to мій профіль page click on редагувати профіль actual result wrong alignment of змінити пароль label expected result user story link user story | 1 |
570,730 | 17,023,170,512 | IssuesEvent | 2021-07-03 00:41:28 | tomhughes/trac-tickets | https://api.github.com/repos/tomhughes/trac-tickets | closed | Allow better reuse of GeoRSS class in lib/osm.rb | Component: rails_port Priority: minor Resolution: fixed Type: enhancement | **[Submitted to the original trac issue database at 10.13pm, Saturday, 9th June 2007]**
There are some hardcoded strings in there that should probably all be passed in through as parameters (with defaults) so the code can better be reused for other purposes as well as traces. | 1.0 | Allow better reuse of GeoRSS class in lib/osm.rb - **[Submitted to the original trac issue database at 10.13pm, Saturday, 9th June 2007]**
There are some hardcoded strings in there that should probably all be passed in through as parameters (with defaults) so the code can better be reused for other purposes as well as traces. | priority | allow better reuse of georss class in lib osm rb there are some hardcoded strings in there that should probably all be passed in through as parameters with defaults so the code can better be reused for other purposes as well as traces | 1 |
200,179 | 7,001,143,613 | IssuesEvent | 2017-12-18 09:07:29 | cilium/cilium | https://api.github.com/repos/cilium/cilium | closed | Ginkgo CI: Gather logs that are dumped to file as artifacts in Jenkins build | area/CI priority/high | Parent: #1839
We currently `archiveArtifacts` as part of the Jenkins build for Cilium as a "post-build action"
```
post {
always {
sh './test/post_build_agent.sh || true'
sh './tests/copy_files || true'
archiveArtifacts artifacts: "cilium-files-runtime-${JOB_BASE_NAME}-${BUILD_NUMBER}.tar.gz", allowEmptyArchive: true
sh './tests/k8s/copy_files || true'
archiveArtifacts artifacts: "cilium-files-k8s-${JOB_BASE_NAME}-${BUILD_NUMBER}.tar.gz", allowEmptyArchive: true
sh 'rm -rf ${WORKSPACE}/cilium-files*${JOB_BASE_NAME}-${BUILD_NUMBER}* ${WORKSPACE}/tests/cilium-files ${WORKSPACE}/tests/k8s/tests/cilium-files'
sh 'ls'
sh 'vagrant destroy -f'
sh 'cd ./tests/k8s && vagrant destroy -f'
}
}
```
Make sure that the logs which are gathered as part of #2026 are packaged up and archived to be picked up by Jenkins for further inspection by those who run PRs. | 1.0 | Ginkgo CI: Gather logs that are dumped to file as artifacts in Jenkins build - Parent: #1839
We currently `archiveArtifacts` as part of the Jenkins build for Cilium as a "post-build action"
```
post {
always {
sh './test/post_build_agent.sh || true'
sh './tests/copy_files || true'
archiveArtifacts artifacts: "cilium-files-runtime-${JOB_BASE_NAME}-${BUILD_NUMBER}.tar.gz", allowEmptyArchive: true
sh './tests/k8s/copy_files || true'
archiveArtifacts artifacts: "cilium-files-k8s-${JOB_BASE_NAME}-${BUILD_NUMBER}.tar.gz", allowEmptyArchive: true
sh 'rm -rf ${WORKSPACE}/cilium-files*${JOB_BASE_NAME}-${BUILD_NUMBER}* ${WORKSPACE}/tests/cilium-files ${WORKSPACE}/tests/k8s/tests/cilium-files'
sh 'ls'
sh 'vagrant destroy -f'
sh 'cd ./tests/k8s && vagrant destroy -f'
}
}
```
Make sure that the logs which are gathered as part of #2026 are packaged up and archived to be picked up by Jenkins for further inspection by those who run PRs. | priority | ginkgo ci gather logs that are dumped to file as artifacts in jenkins build parent we currently archiveartifacts as part of the jenkins build for cilium as a post build action post always sh test post build agent sh true sh tests copy files true archiveartifacts artifacts cilium files runtime job base name build number tar gz allowemptyarchive true sh tests copy files true archiveartifacts artifacts cilium files job base name build number tar gz allowemptyarchive true sh rm rf workspace cilium files job base name build number workspace tests cilium files workspace tests tests cilium files sh ls sh vagrant destroy f sh cd tests vagrant destroy f make sure that the logs which are gathered as part of are packaged up and archived to be picked up by jenkins for further inspection by those who run prs | 1 |
106,737 | 16,717,902,407 | IssuesEvent | 2021-06-10 01:04:59 | ilan-WS/m3 | https://api.github.com/repos/ilan-WS/m3 | opened | WS-2020-0345 (High) detected in jsonpointer-4.0.1.tgz | security vulnerability | ## WS-2020-0345 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jsonpointer-4.0.1.tgz</b></p></summary>
<p>Simple JSON Addressing.</p>
<p>Library home page: <a href="https://registry.npmjs.org/jsonpointer/-/jsonpointer-4.0.1.tgz">https://registry.npmjs.org/jsonpointer/-/jsonpointer-4.0.1.tgz</a></p>
<p>Path to dependency file: m3/src/ctl/ui/package.json</p>
<p>Path to vulnerable library: m3/src/ctl/ui/node_modules/jsonpointer</p>
<p>
Dependency Hierarchy:
- react-scripts-1.0.10.tgz (Root Library)
- eslint-3.19.0.tgz
- is-my-json-valid-2.20.0.tgz
- :x: **jsonpointer-4.0.1.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prototype Pollution vulnerability was found in jsonpointer before 4.1.0 via the set function.
<p>Publish Date: 2020-07-03
<p>URL: <a href=https://github.com/janl/node-jsonpointer/commit/234e3437019c6c07537ed2ad1e03b3e132b85e34>WS-2020-0345</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/janl/node-jsonpointer/releases/tag/v4.1.0">https://github.com/janl/node-jsonpointer/releases/tag/v4.1.0</a></p>
<p>Release Date: 2020-07-03</p>
<p>Fix Resolution: jsonpointer - 4.1.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"jsonpointer","packageVersion":"4.0.1","packageFilePaths":["/src/ctl/ui/package.json"],"isTransitiveDependency":true,"dependencyTree":"react-scripts:1.0.10;eslint:3.19.0;is-my-json-valid:2.20.0;jsonpointer:4.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jsonpointer - 4.1.0"}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2020-0345","vulnerabilityDetails":"Prototype Pollution vulnerability was found in jsonpointer before 4.1.0 via the set function.","vulnerabilityUrl":"https://github.com/janl/node-jsonpointer/commit/234e3437019c6c07537ed2ad1e03b3e132b85e34","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | WS-2020-0345 (High) detected in jsonpointer-4.0.1.tgz - ## WS-2020-0345 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jsonpointer-4.0.1.tgz</b></p></summary>
<p>Simple JSON Addressing.</p>
<p>Library home page: <a href="https://registry.npmjs.org/jsonpointer/-/jsonpointer-4.0.1.tgz">https://registry.npmjs.org/jsonpointer/-/jsonpointer-4.0.1.tgz</a></p>
<p>Path to dependency file: m3/src/ctl/ui/package.json</p>
<p>Path to vulnerable library: m3/src/ctl/ui/node_modules/jsonpointer</p>
<p>
Dependency Hierarchy:
- react-scripts-1.0.10.tgz (Root Library)
- eslint-3.19.0.tgz
- is-my-json-valid-2.20.0.tgz
- :x: **jsonpointer-4.0.1.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prototype Pollution vulnerability was found in jsonpointer before 4.1.0 via the set function.
<p>Publish Date: 2020-07-03
<p>URL: <a href=https://github.com/janl/node-jsonpointer/commit/234e3437019c6c07537ed2ad1e03b3e132b85e34>WS-2020-0345</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/janl/node-jsonpointer/releases/tag/v4.1.0">https://github.com/janl/node-jsonpointer/releases/tag/v4.1.0</a></p>
<p>Release Date: 2020-07-03</p>
<p>Fix Resolution: jsonpointer - 4.1.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"jsonpointer","packageVersion":"4.0.1","packageFilePaths":["/src/ctl/ui/package.json"],"isTransitiveDependency":true,"dependencyTree":"react-scripts:1.0.10;eslint:3.19.0;is-my-json-valid:2.20.0;jsonpointer:4.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jsonpointer - 4.1.0"}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2020-0345","vulnerabilityDetails":"Prototype Pollution vulnerability was found in jsonpointer before 4.1.0 via the set function.","vulnerabilityUrl":"https://github.com/janl/node-jsonpointer/commit/234e3437019c6c07537ed2ad1e03b3e132b85e34","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | ws high detected in jsonpointer tgz ws high severity vulnerability vulnerable library jsonpointer tgz simple json addressing library home page a href path to dependency file src ctl ui package json path to vulnerable library src ctl ui node modules jsonpointer dependency hierarchy react scripts tgz root library eslint tgz is my json valid tgz x jsonpointer tgz vulnerable library found in base branch master vulnerability details prototype pollution vulnerability was found in jsonpointer before via the set function publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jsonpointer isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree react scripts eslint is my json valid jsonpointer isminimumfixversionavailable true minimumfixversion jsonpointer basebranches vulnerabilityidentifier ws vulnerabilitydetails prototype pollution vulnerability was found in jsonpointer before via the set function vulnerabilityurl | 0 |
253,477 | 8,056,626,751 | IssuesEvent | 2018-08-02 13:17:37 | tavorperry/MTA-Coffee | https://api.github.com/repos/tavorperry/MTA-Coffee | closed | Change URL in code | High Priority | replace
**http://vmedu151.mtacloud.co.il**
or
**http://whispering-scrubland-84389.herokuapp.com/**
with
**http://mtacoffee.mta.ac.il**
in every place that mentions in the code | 1.0 | Change URL in code - replace
**http://vmedu151.mtacloud.co.il**
or
**http://whispering-scrubland-84389.herokuapp.com/**
with
**http://mtacoffee.mta.ac.il**
in every place that mentions in the code | priority | change url in code replace or with in every place that mentions in the code | 1 |
671,494 | 22,763,477,170 | IssuesEvent | 2022-07-08 00:14:13 | kubernetes/ingress-nginx | https://api.github.com/repos/kubernetes/ingress-nginx | closed | Helm template with custom values does not create deployment | kind/bug needs-triage needs-priority | When using the helm chart version:
```
$ helm show chart nginx-stable/nginx-ingress 7:34PM
apiVersion: v1
appVersion: 2.2.2
description: NGINX Ingress Controller
home: https://github.com/nginxinc/kubernetes-ingress
icon: https://raw.githubusercontent.com/nginxinc/kubernetes-ingress/v2.2.2/deployments/helm-chart/chart-icon.png
keywords:
- ingress
- nginx
kubeVersion: '>= 1.19.0-0'
maintainers:
- email: kubernetes@nginx.com
name: nginxinc
name: nginx-ingress
sources:
- https://github.com/nginxinc/kubernetes-ingress/tree/v2.2.2/deployments/helm-chart
version: 0.13.2
```
Running `helm template nginx nginx-stable/nginx-ingress -f values.yml` where `values.yml` is the default values found https://github.com/kubernetes/ingress-nginx/blob/main/charts/ingress-nginx/values.yaml, does not generate a deployment manifest.
If run without the `-f values.yml` the deployment manifest is created.
What is wrong with the values that causes the manifest to not be created? | 1.0 | Helm template with custom values does not create deployment - When using the helm chart version:
```
$ helm show chart nginx-stable/nginx-ingress 7:34PM
apiVersion: v1
appVersion: 2.2.2
description: NGINX Ingress Controller
home: https://github.com/nginxinc/kubernetes-ingress
icon: https://raw.githubusercontent.com/nginxinc/kubernetes-ingress/v2.2.2/deployments/helm-chart/chart-icon.png
keywords:
- ingress
- nginx
kubeVersion: '>= 1.19.0-0'
maintainers:
- email: kubernetes@nginx.com
name: nginxinc
name: nginx-ingress
sources:
- https://github.com/nginxinc/kubernetes-ingress/tree/v2.2.2/deployments/helm-chart
version: 0.13.2
```
Running `helm template nginx nginx-stable/nginx-ingress -f values.yml` where `values.yml` is the default values found https://github.com/kubernetes/ingress-nginx/blob/main/charts/ingress-nginx/values.yaml, does not generate a deployment manifest.
If run without the `-f values.yml` the deployment manifest is created.
What is wrong with the values that causes the manifest to not be created? | priority | helm template with custom values does not create deployment when using the helm chart version helm show chart nginx stable nginx ingress apiversion appversion description nginx ingress controller home icon keywords ingress nginx kubeversion maintainers email kubernetes nginx com name nginxinc name nginx ingress sources version running helm template nginx nginx stable nginx ingress f values yml where values yml is the default values found does not generate a deployment manifest if run without the f values yml the deployment manifest is created what is wrong with the values that causes the manifest to not be created | 1 |
632,282 | 20,189,609,362 | IssuesEvent | 2022-02-11 03:21:11 | WeAreNewt/NonFungibleTime | https://api.github.com/repos/WeAreNewt/NonFungibleTime | closed | No error prompt when I try to mint absurdly low duration | bug good first issue frontend mid priority | 
I can't mint an absurdly low numberOfHours (Metamask doesn't pop up), but I also get no error messaging from the modal | 1.0 | No error prompt when I try to mint absurdly low duration - 
I can't mint an absurdly low numberOfHours (Metamask doesn't pop up), but I also get no error messaging from the modal | priority | no error prompt when i try to mint absurdly low duration i can t mint an absurdly low numberofhours metamask doesn t pop up but i also get no error messaging from the modal | 1 |
54,651 | 13,401,012,209 | IssuesEvent | 2020-09-03 16:38:29 | stitchEm/stitchEm | https://api.github.com/repos/stitchEm/stitchEm | opened | Print CMake version for easier troubleshooting | Build enhancement good first issue | Just print out the CMake version at the beginning of the configuration, so that when issues are filed with CMake printouts, we already have that information (see #121). | 1.0 | Print CMake version for easier troubleshooting - Just print out the CMake version at the beginning of the configuration, so that when issues are filed with CMake printouts, we already have that information (see #121). | non_priority | print cmake version for easier troubleshooting just print out the cmake version at the beginning of the configuration so that when issues are filed with cmake printouts we already have that information see | 0 |
648,521 | 21,188,190,635 | IssuesEvent | 2022-04-08 14:42:25 | ConsistencyPlus/ConsistencyPlus | https://api.github.com/repos/ConsistencyPlus/ConsistencyPlus | closed | Crash at creating a new world | Help Wanted Invalid Question/Information Needed Low Priority | **Describe the bug**
Crash at creating a new world after updating C+ from 0.3 to 0.4.2
**Versions**
Minecraft version: 1.16.5
C+ version: 0.4.2
Fabric API version: 0.43.0+1.16 (Edited by Siuol the reflect the actual version of Fabric API used.)
**Other mods**
[crash-2021-12-04_13.23.09-server.txt](https://github.com/ConsistencyPlus/ConsistencyPlus/files/7653380/crash-2021-12-04_13.23.09-server.txt)
**Logs**
[latest.log](https://github.com/ConsistencyPlus/ConsistencyPlus/files/7653378/latest.log)
**To Reproduce**
1. Updating C+ from 0.3 to 0.4.2
2. Start Minecraft
3. Create new world
| 1.0 | Crash at creating a new world - **Describe the bug**
Crash at creating a new world after updating C+ from 0.3 to 0.4.2
**Versions**
Minecraft version: 1.16.5
C+ version: 0.4.2
Fabric API version: 0.43.0+1.16 (Edited by Siuol the reflect the actual version of Fabric API used.)
**Other mods**
[crash-2021-12-04_13.23.09-server.txt](https://github.com/ConsistencyPlus/ConsistencyPlus/files/7653380/crash-2021-12-04_13.23.09-server.txt)
**Logs**
[latest.log](https://github.com/ConsistencyPlus/ConsistencyPlus/files/7653378/latest.log)
**To Reproduce**
1. Updating C+ from 0.3 to 0.4.2
2. Start Minecraft
3. Create new world
| priority | crash at creating a new world describe the bug crash at creating a new world after updating c from to versions minecraft version c version fabric api version edited by siuol the reflect the actual version of fabric api used other mods logs to reproduce updating c from to start minecraft create new world | 1 |
89,885 | 3,801,503,779 | IssuesEvent | 2016-03-23 23:15:42 | kubernetes/kubernetes | https://api.github.com/repos/kubernetes/kubernetes | opened | Add a munger (bot) to require release-note-* on all PRs and release-note-(!NONE) on cherrypicks (to branches) | help-wanted priority/P1 | Following a revelation in https://github.com/kubernetes/kubernetes/pull/23315#issuecomment-200573266, it became clear we could solve the release note issue (at least the simple case) with labels and a bot.
We need a new munger/bot to do the following:
1. Initiate a `needs-release-note` label on all new PRs
1. Disallow/Remove the `lgtm` label on all PRs labeled as `needs-release-note`
1. Create new labels: `release-note-NONE`, maybe others for new release note categories
1. Auto-remove `needs-release-note` when one of the release-note-* labels is added
1. Special case for cherry-picked/branch PRs, release-note-NONE is not allowed | 1.0 | Add a munger (bot) to require release-note-* on all PRs and release-note-(!NONE) on cherrypicks (to branches) - Following a revelation in https://github.com/kubernetes/kubernetes/pull/23315#issuecomment-200573266, it became clear we could solve the release note issue (at least the simple case) with labels and a bot.
We need a new munger/bot to do the following:
1. Initiate a `needs-release-note` label on all new PRs
1. Disallow/Remove the `lgtm` label on all PRs labeled as `needs-release-note`
1. Create new labels: `release-note-NONE`, maybe others for new release note categories
1. Auto-remove `needs-release-note` when one of the release-note-* labels is added
1. Special case for cherry-picked/branch PRs, release-note-NONE is not allowed | priority | add a munger bot to require release note on all prs and release note none on cherrypicks to branches following a revelation in it became clear we could solve the release note issue at least the simple case with labels and a bot we need a new munger bot to do the following initiate a needs release note label on all new prs disallow remove the lgtm label on all prs labeled as needs release note create new labels release note none maybe others for new release note categories auto remove needs release note when one of the release note labels is added special case for cherry picked branch prs release note none is not allowed | 1 |
279,506 | 8,666,763,987 | IssuesEvent | 2018-11-29 05:57:14 | dmwm/WMCore | https://api.github.com/repos/dmwm/WMCore | closed | Push worker threads execution time to MONIT IT | Medium Priority Monitoring | Since we now collect this data and persist it in the relational database, it should be pretty straight forward to publish how long each component and their threads take per cycle.
This is going to be more like a developers metric/view, but I think it's quite useful. | 1.0 | Push worker threads execution time to MONIT IT - Since we now collect this data and persist it in the relational database, it should be pretty straight forward to publish how long each component and their threads take per cycle.
This is going to be more like a developers metric/view, but I think it's quite useful. | priority | push worker threads execution time to monit it since we now collect this data and persist it in the relational database it should be pretty straight forward to publish how long each component and their threads take per cycle this is going to be more like a developers metric view but i think it s quite useful | 1 |
807,771 | 30,018,740,082 | IssuesEvent | 2023-06-26 20:59:38 | vrchatapi/specification | https://api.github.com/repos/vrchatapi/specification | closed | Presence in auth/user | Type: Enhancement Priority: Medium Status: Help Wanted Good First Task | Noticed this in auth/user:
```json
"presence": {
"id": "...",
"platform": "",
"status": "offline",
"world": "offline",
"instance": "offline",
"instanceType": "",
"travelingToWorld": "offline",
"travelingToInstance": "offline",
"groups": []
}
```
No idea how long it's been there. Some fields were previously in the root of the returned object. | 1.0 | Presence in auth/user - Noticed this in auth/user:
```json
"presence": {
"id": "...",
"platform": "",
"status": "offline",
"world": "offline",
"instance": "offline",
"instanceType": "",
"travelingToWorld": "offline",
"travelingToInstance": "offline",
"groups": []
}
```
No idea how long it's been there. Some fields were previously in the root of the returned object. | priority | presence in auth user noticed this in auth user json presence id platform status offline world offline instance offline instancetype travelingtoworld offline travelingtoinstance offline groups no idea how long it s been there some fields were previously in the root of the returned object | 1 |
369,950 | 10,920,406,156 | IssuesEvent | 2019-11-21 21:11:38 | bounswe/bounswe2019group6 | https://api.github.com/repos/bounswe/bounswe2019group6 | closed | Implement Portfolio Page | priority:high related:frontend type:new-feature | A user can create a portfolio using his/her profile page. When the user clicks to the created portfolio. We need to redirect him/her to a new page containing the information of the portfolio. User should be able to:
* see all trading equipments
* add new trading equipment
* remove already added trading equipment | 1.0 | Implement Portfolio Page - A user can create a portfolio using his/her profile page. When the user clicks to the created portfolio. We need to redirect him/her to a new page containing the information of the portfolio. User should be able to:
* see all trading equipments
* add new trading equipment
* remove already added trading equipment | priority | implement portfolio page a user can create a portfolio using his her profile page when the user clicks to the created portfolio we need to redirect him her to a new page containing the information of the portfolio user should be able to see all trading equipments add new trading equipment remove already added trading equipment | 1 |
314,264 | 26,988,282,802 | IssuesEvent | 2023-02-09 17:43:46 | Azure/azure-sdk-tools | https://api.github.com/repos/Azure/azure-sdk-tools | closed | Test issue - disregard | Test-Proxy | Test of the change I made to Fabric Bot to assign issues labeled as 'Test-Proxy' to me. | 1.0 | Test issue - disregard - Test of the change I made to Fabric Bot to assign issues labeled as 'Test-Proxy' to me. | non_priority | test issue disregard test of the change i made to fabric bot to assign issues labeled as test proxy to me | 0 |
289,724 | 31,996,938,126 | IssuesEvent | 2023-09-21 09:46:36 | Mend-developer-platform-load/3184155_33 | https://api.github.com/repos/Mend-developer-platform-load/3184155_33 | opened | ansible-2.9.9.tar.gz: 8 vulnerabilities (highest severity is: 7.1) | Mend: dependency security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p></summary>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (ansible version) | Remediation Possible** |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2020-14365](https://www.mend.io/vulnerability-database/CVE-2020-14365) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.1 | ansible-2.9.9.tar.gz | Direct | 2.9.12 | ✅ |
| [CVE-2020-14332](https://www.mend.io/vulnerability-database/CVE-2020-14332) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.5 | ansible-2.9.9.tar.gz | Direct | 2.9.12 | ✅ |
| [CVE-2020-1753](https://www.mend.io/vulnerability-database/CVE-2020-1753) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.5 | ansible-2.9.9.tar.gz | Direct | 2.9.10 | ✅ |
| [CVE-2021-20180](https://www.mend.io/vulnerability-database/CVE-2021-20180) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.5 | ansible-2.9.9.tar.gz | Direct | 2.9.18 | ✅ |
| [CVE-2020-14330](https://www.mend.io/vulnerability-database/CVE-2020-14330) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.5 | ansible-2.9.9.tar.gz | Direct | 2.9.14 | ✅ |
| [CVE-2020-10744](https://www.mend.io/vulnerability-database/CVE-2020-10744) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.0 | ansible-2.9.9.tar.gz | Direct | 2.9.10 | ✅ |
| [CVE-2020-1738](https://www.mend.io/vulnerability-database/CVE-2020-1738) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> Low | 3.9 | ansible-2.9.9.tar.gz | Direct | 2.9.10 | ✅ |
| [CVE-2021-3533](https://www.mend.io/vulnerability-database/CVE-2021-3533) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> Low | 2.5 | ansible-2.9.9.tar.gz | Direct | 2.9.23 | ✅ |
<p>**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-14365</summary>
### Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p>
<p>Found in base branch: <b>feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A flaw was found in the Ansible Engine, in ansible-engine 2.8.x before 2.8.15 and ansible-engine 2.9.x before 2.9.13, when installing packages using the dnf module. GPG signatures are ignored during installation even when disable_gpg_check is set to False, which is the default behavior. This flaw leads to malicious packages being installed on the system and arbitrary code executed via package installation scripts. The highest threat from this vulnerability is to integrity and system availability.
<p>Publish Date: 2020-09-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-14365>CVE-2020-14365</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1869154">https://bugzilla.redhat.com/show_bug.cgi?id=1869154</a></p>
<p>Release Date: 2020-09-23</p>
<p>Fix Resolution: 2.9.12</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-14332</summary>
### Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p>
<p>Found in base branch: <b>feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A flaw was found in the Ansible Engine when using module_args. Tasks executed with check mode (--check-mode) do not properly neutralize sensitive data exposed in the event data. This flaw allows unauthorized users to read this data. The highest threat from this vulnerability is to confidentiality.
<p>Publish Date: 2020-09-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-14332>CVE-2020-14332</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-14332">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-14332</a></p>
<p>Release Date: 2020-09-11</p>
<p>Fix Resolution: 2.9.12</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-1753</summary>
### Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p>
<p>Found in base branch: <b>feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A security flaw was found in Ansible Engine, all Ansible 2.7.x versions prior to 2.7.17, all Ansible 2.8.x versions prior to 2.8.11 and all Ansible 2.9.x versions prior to 2.9.7, when managing kubernetes using the k8s module. Sensitive parameters such as passwords and tokens are passed to kubectl from the command line, not using an environment variable or an input configuration file. This will disclose passwords and tokens from process list and no_log directive from debug module would not have any effect making these secrets being disclosed on stdout and log files.
<p>Publish Date: 2020-03-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-1753>CVE-2020-1753</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2020-1753">https://nvd.nist.gov/vuln/detail/CVE-2020-1753</a></p>
<p>Release Date: 2020-03-16</p>
<p>Fix Resolution: 2.9.10</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2021-20180</summary>
### Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p>
<p>Found in base branch: <b>feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A flaw was found in ansible module where credentials are disclosed in the console log by default and not protected by the security feature when using the bitbucket_pipeline_variable module. This flaw allows an attacker to steal bitbucket_pipeline credentials. The highest threat from this vulnerability is to confidentiality.
<p>Publish Date: 2022-03-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-20180>CVE-2021-20180</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-fh5v-5f35-2rv2">https://github.com/advisories/GHSA-fh5v-5f35-2rv2</a></p>
<p>Release Date: 2022-03-16</p>
<p>Fix Resolution: 2.9.18</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-14330</summary>
### Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p>
<p>Found in base branch: <b>feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An Improper Output Neutralization for Logs flaw was found in Ansible when using the uri module, where sensitive data is exposed to content and json output. This flaw allows an attacker to access the logs or outputs of performed tasks to read keys used in playbooks from other users within the uri module. The highest threat from this vulnerability is to data confidentiality.
<p>Publish Date: 2020-09-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-14330>CVE-2020-14330</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-14330">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-14330</a></p>
<p>Release Date: 2020-09-11</p>
<p>Fix Resolution: 2.9.14</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-10744</summary>
### Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p>
<p>Found in base branch: <b>feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An incomplete fix was found for the fix of the flaw CVE-2020-1733 ansible: insecure temporary directory when running become_user from become directive. The provided fix is insufficient to prevent the race condition on systems using ACLs and FUSE filesystems. Ansible Engine 2.7.18, 2.8.12, and 2.9.9 as well as previous versions are affected and Ansible Tower 3.4.5, 3.5.6 and 3.6.4 as well as previous versions are affected.
<p>Publish Date: 2020-05-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-10744>CVE-2020-10744</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2020-10744">https://nvd.nist.gov/vuln/detail/CVE-2020-10744</a></p>
<p>Release Date: 2020-05-15</p>
<p>Fix Resolution: 2.9.10</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> CVE-2020-1738</summary>
### Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p>
<p>Found in base branch: <b>feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A flaw was found in Ansible Engine when the module package or service is used and the parameter 'use' is not specified. If a previous task is executed with a malicious user, the module sent can be selected by the attacker using the ansible facts file. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.
<p>Publish Date: 2020-03-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-1738>CVE-2020-1738</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>3.9</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1738">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1738</a></p>
<p>Release Date: 2020-03-16</p>
<p>Fix Resolution: 2.9.10</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> CVE-2021-3533</summary>
### Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p>
<p>Found in base branch: <b>feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A flaw was found in Ansible if an ansible user sets ANSIBLE_ASYNC_DIR to a subdirectory of a world writable directory. When this occurs, there is a race condition on the managed machine. A malicious, non-privileged account on the remote machine can exploit the race condition to access the async result data. This flaw affects Ansible Tower 3.7 and Ansible Automation Platform 1.2.
<p>Publish Date: 2021-06-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-3533>CVE-2021-3533</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>2.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-3533">https://nvd.nist.gov/vuln/detail/CVE-2021-3533</a></p>
<p>Release Date: 2021-06-09</p>
<p>Fix Resolution: 2.9.23</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details>
***
<p>:rescue_worker_helmet:Automatic Remediation will be attempted for this issue.</p> | True | ansible-2.9.9.tar.gz: 8 vulnerabilities (highest severity is: 7.1) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p></summary>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (ansible version) | Remediation Possible** |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2020-14365](https://www.mend.io/vulnerability-database/CVE-2020-14365) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.1 | ansible-2.9.9.tar.gz | Direct | 2.9.12 | ✅ |
| [CVE-2020-14332](https://www.mend.io/vulnerability-database/CVE-2020-14332) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.5 | ansible-2.9.9.tar.gz | Direct | 2.9.12 | ✅ |
| [CVE-2020-1753](https://www.mend.io/vulnerability-database/CVE-2020-1753) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.5 | ansible-2.9.9.tar.gz | Direct | 2.9.10 | ✅ |
| [CVE-2021-20180](https://www.mend.io/vulnerability-database/CVE-2021-20180) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.5 | ansible-2.9.9.tar.gz | Direct | 2.9.18 | ✅ |
| [CVE-2020-14330](https://www.mend.io/vulnerability-database/CVE-2020-14330) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.5 | ansible-2.9.9.tar.gz | Direct | 2.9.14 | ✅ |
| [CVE-2020-10744](https://www.mend.io/vulnerability-database/CVE-2020-10744) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.0 | ansible-2.9.9.tar.gz | Direct | 2.9.10 | ✅ |
| [CVE-2020-1738](https://www.mend.io/vulnerability-database/CVE-2020-1738) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> Low | 3.9 | ansible-2.9.9.tar.gz | Direct | 2.9.10 | ✅ |
| [CVE-2021-3533](https://www.mend.io/vulnerability-database/CVE-2021-3533) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> Low | 2.5 | ansible-2.9.9.tar.gz | Direct | 2.9.23 | ✅ |
<p>**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-14365</summary>
### Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p>
<p>Found in base branch: <b>feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A flaw was found in the Ansible Engine, in ansible-engine 2.8.x before 2.8.15 and ansible-engine 2.9.x before 2.9.13, when installing packages using the dnf module. GPG signatures are ignored during installation even when disable_gpg_check is set to False, which is the default behavior. This flaw leads to malicious packages being installed on the system and arbitrary code executed via package installation scripts. The highest threat from this vulnerability is to integrity and system availability.
<p>Publish Date: 2020-09-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-14365>CVE-2020-14365</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1869154">https://bugzilla.redhat.com/show_bug.cgi?id=1869154</a></p>
<p>Release Date: 2020-09-23</p>
<p>Fix Resolution: 2.9.12</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-14332</summary>
### Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p>
<p>Found in base branch: <b>feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A flaw was found in the Ansible Engine when using module_args. Tasks executed with check mode (--check-mode) do not properly neutralize sensitive data exposed in the event data. This flaw allows unauthorized users to read this data. The highest threat from this vulnerability is to confidentiality.
<p>Publish Date: 2020-09-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-14332>CVE-2020-14332</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-14332">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-14332</a></p>
<p>Release Date: 2020-09-11</p>
<p>Fix Resolution: 2.9.12</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-1753</summary>
### Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p>
<p>Found in base branch: <b>feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A security flaw was found in Ansible Engine, all Ansible 2.7.x versions prior to 2.7.17, all Ansible 2.8.x versions prior to 2.8.11 and all Ansible 2.9.x versions prior to 2.9.7, when managing kubernetes using the k8s module. Sensitive parameters such as passwords and tokens are passed to kubectl from the command line, not using an environment variable or an input configuration file. This will disclose passwords and tokens from process list and no_log directive from debug module would not have any effect making these secrets being disclosed on stdout and log files.
<p>Publish Date: 2020-03-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-1753>CVE-2020-1753</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2020-1753">https://nvd.nist.gov/vuln/detail/CVE-2020-1753</a></p>
<p>Release Date: 2020-03-16</p>
<p>Fix Resolution: 2.9.10</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2021-20180</summary>
### Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p>
<p>Found in base branch: <b>feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A flaw was found in ansible module where credentials are disclosed in the console log by default and not protected by the security feature when using the bitbucket_pipeline_variable module. This flaw allows an attacker to steal bitbucket_pipeline credentials. The highest threat from this vulnerability is to confidentiality.
<p>Publish Date: 2022-03-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-20180>CVE-2021-20180</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-fh5v-5f35-2rv2">https://github.com/advisories/GHSA-fh5v-5f35-2rv2</a></p>
<p>Release Date: 2022-03-16</p>
<p>Fix Resolution: 2.9.18</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-14330</summary>
### Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p>
<p>Found in base branch: <b>feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An Improper Output Neutralization for Logs flaw was found in Ansible when using the uri module, where sensitive data is exposed to content and json output. This flaw allows an attacker to access the logs or outputs of performed tasks to read keys used in playbooks from other users within the uri module. The highest threat from this vulnerability is to data confidentiality.
<p>Publish Date: 2020-09-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-14330>CVE-2020-14330</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-14330">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-14330</a></p>
<p>Release Date: 2020-09-11</p>
<p>Fix Resolution: 2.9.14</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-10744</summary>
### Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p>
<p>Found in base branch: <b>feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An incomplete fix was found for the fix of the flaw CVE-2020-1733 ansible: insecure temporary directory when running become_user from become directive. The provided fix is insufficient to prevent the race condition on systems using ACLs and FUSE filesystems. Ansible Engine 2.7.18, 2.8.12, and 2.9.9 as well as previous versions are affected and Ansible Tower 3.4.5, 3.5.6 and 3.6.4 as well as previous versions are affected.
<p>Publish Date: 2020-05-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-10744>CVE-2020-10744</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2020-10744">https://nvd.nist.gov/vuln/detail/CVE-2020-10744</a></p>
<p>Release Date: 2020-05-15</p>
<p>Fix Resolution: 2.9.10</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> CVE-2020-1738</summary>
### Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p>
<p>Found in base branch: <b>feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A flaw was found in Ansible Engine when the module package or service is used and the parameter 'use' is not specified. If a previous task is executed with a malicious user, the module sent can be selected by the attacker using the ansible facts file. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.
<p>Publish Date: 2020-03-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-1738>CVE-2020-1738</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>3.9</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1738">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1738</a></p>
<p>Release Date: 2020-03-16</p>
<p>Fix Resolution: 2.9.10</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> CVE-2021-3533</summary>
### Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/3184155_33/commit/7da6eb4ea8282c74045d0ef7c7c93c00c9df886d">7da6eb4ea8282c74045d0ef7c7c93c00c9df886d</a></p>
<p>Found in base branch: <b>feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A flaw was found in Ansible if an ansible user sets ANSIBLE_ASYNC_DIR to a subdirectory of a world writable directory. When this occurs, there is a race condition on the managed machine. A malicious, non-privileged account on the remote machine can exploit the race condition to access the async result data. This flaw affects Ansible Tower 3.7 and Ansible Automation Platform 1.2.
<p>Publish Date: 2021-06-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-3533>CVE-2021-3533</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>2.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-3533">https://nvd.nist.gov/vuln/detail/CVE-2021-3533</a></p>
<p>Release Date: 2021-06-09</p>
<p>Fix Resolution: 2.9.23</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details>
***
<p>:rescue_worker_helmet:Automatic Remediation will be attempted for this issue.</p> | non_priority | ansible tar gz vulnerabilities highest severity is vulnerable library ansible tar gz radically simple it automation library home page a href path to dependency file requirements txt path to vulnerable library requirements txt found in head commit a href vulnerabilities cve severity cvss dependency type fixed in ansible version remediation possible high ansible tar gz direct medium ansible tar gz direct medium ansible tar gz direct medium ansible tar gz direct medium ansible tar gz direct medium ansible tar gz direct low ansible tar gz direct low ansible tar gz direct in some cases remediation pr cannot be created automatically for a vulnerability despite the availability of remediation details cve vulnerable library ansible tar gz radically simple it automation library home page a href path to dependency file requirements txt path to vulnerable library requirements txt dependency hierarchy x ansible tar gz vulnerable library found in head commit a href found in base branch feature branch vulnerability details a flaw was found in the ansible engine in ansible engine x before and ansible engine x before when installing packages using the dnf module gpg signatures are ignored during installation even when disable gpg check is set to false which is the default behavior this flaw leads to malicious packages being installed on the system and arbitrary code executed via package installation scripts the highest threat from this vulnerability is to integrity and system availability publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation will be attempted for this issue cve vulnerable library ansible tar gz radically simple it automation library home page a href path to dependency file requirements txt path to vulnerable library requirements txt dependency hierarchy x ansible tar gz vulnerable library found in head commit a href found in base branch feature branch vulnerability details a flaw was found in the ansible engine when using module args tasks executed with check mode check mode do not properly neutralize sensitive data exposed in the event data this flaw allows unauthorized users to read this data the highest threat from this vulnerability is to confidentiality publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation will be attempted for this issue cve vulnerable library ansible tar gz radically simple it automation library home page a href path to dependency file requirements txt path to vulnerable library requirements txt dependency hierarchy x ansible tar gz vulnerable library found in head commit a href found in base branch feature branch vulnerability details a security flaw was found in ansible engine all ansible x versions prior to all ansible x versions prior to and all ansible x versions prior to when managing kubernetes using the module sensitive parameters such as passwords and tokens are passed to kubectl from the command line not using an environment variable or an input configuration file this will disclose passwords and tokens from process list and no log directive from debug module would not have any effect making these secrets being disclosed on stdout and log files publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation will be attempted for this issue cve vulnerable library ansible tar gz radically simple it automation library home page a href path to dependency file requirements txt path to vulnerable library requirements txt dependency hierarchy x ansible tar gz vulnerable library found in head commit a href found in base branch feature branch vulnerability details a flaw was found in ansible module where credentials are disclosed in the console log by default and not protected by the security feature when using the bitbucket pipeline variable module this flaw allows an attacker to steal bitbucket pipeline credentials the highest threat from this vulnerability is to confidentiality publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation will be attempted for this issue cve vulnerable library ansible tar gz radically simple it automation library home page a href path to dependency file requirements txt path to vulnerable library requirements txt dependency hierarchy x ansible tar gz vulnerable library found in head commit a href found in base branch feature branch vulnerability details an improper output neutralization for logs flaw was found in ansible when using the uri module where sensitive data is exposed to content and json output this flaw allows an attacker to access the logs or outputs of performed tasks to read keys used in playbooks from other users within the uri module the highest threat from this vulnerability is to data confidentiality publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation will be attempted for this issue cve vulnerable library ansible tar gz radically simple it automation library home page a href path to dependency file requirements txt path to vulnerable library requirements txt dependency hierarchy x ansible tar gz vulnerable library found in head commit a href found in base branch feature branch vulnerability details an incomplete fix was found for the fix of the flaw cve ansible insecure temporary directory when running become user from become directive the provided fix is insufficient to prevent the race condition on systems using acls and fuse filesystems ansible engine and as well as previous versions are affected and ansible tower and as well as previous versions are affected publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation will be attempted for this issue cve vulnerable library ansible tar gz radically simple it automation library home page a href path to dependency file requirements txt path to vulnerable library requirements txt dependency hierarchy x ansible tar gz vulnerable library found in head commit a href found in base branch feature branch vulnerability details a flaw was found in ansible engine when the module package or service is used and the parameter use is not specified if a previous task is executed with a malicious user the module sent can be selected by the attacker using the ansible facts file all versions in x x and x branches are believed to be vulnerable publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low user interaction required scope changed impact metrics confidentiality impact none integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation will be attempted for this issue cve vulnerable library ansible tar gz radically simple it automation library home page a href path to dependency file requirements txt path to vulnerable library requirements txt dependency hierarchy x ansible tar gz vulnerable library found in head commit a href found in base branch feature branch vulnerability details a flaw was found in ansible if an ansible user sets ansible async dir to a subdirectory of a world writable directory when this occurs there is a race condition on the managed machine a malicious non privileged account on the remote machine can exploit the race condition to access the async result data this flaw affects ansible tower and ansible automation platform publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation will be attempted for this issue rescue worker helmet automatic remediation will be attempted for this issue | 0 |
76,912 | 9,968,870,168 | IssuesEvent | 2019-07-08 16:34:15 | microsoft/MixedRealityToolkit-Unity | https://api.github.com/repos/microsoft/MixedRealityToolkit-Unity | closed | How to connect HoloLens to server via TCP/IP? | Documentation | Hi guys,
I am a beginner in this field. I want to know there is a tutorial that explains to me, how can I connect HoloLens to a server on the network using TCP/IP to exchange data between them.
Thnx | 1.0 | How to connect HoloLens to server via TCP/IP? - Hi guys,
I am a beginner in this field. I want to know there is a tutorial that explains to me, how can I connect HoloLens to a server on the network using TCP/IP to exchange data between them.
Thnx | non_priority | how to connect hololens to server via tcp ip hi guys i am a beginner in this field i want to know there is a tutorial that explains to me how can i connect hololens to a server on the network using tcp ip to exchange data between them thnx | 0 |
171,016 | 27,048,976,838 | IssuesEvent | 2023-02-13 11:53:23 | effektio/effektio | https://api.github.com/repos/effektio/effektio | closed | internet connectivity state in app | bug flutter infrastructure design needed | We should add network aware handlers/widgets in the application which would inform the internet connectivity state of the application. These packages seems to be helpful:
https://pub.dev/packages/connectivity_plus
https://pub.dev/packages/connectivity_wrapper | 1.0 | internet connectivity state in app - We should add network aware handlers/widgets in the application which would inform the internet connectivity state of the application. These packages seems to be helpful:
https://pub.dev/packages/connectivity_plus
https://pub.dev/packages/connectivity_wrapper | non_priority | internet connectivity state in app we should add network aware handlers widgets in the application which would inform the internet connectivity state of the application these packages seems to be helpful | 0 |
593,039 | 17,936,666,245 | IssuesEvent | 2021-09-10 16:10:37 | assurance-maladie-digital/design-system | https://api.github.com/repos/assurance-maladie-digital/design-system | closed | Documentation de la règle de validation exactLength | low-priority | ## Description
En tant que développeur utilisant le Design System, je veux savoir comment utiliser la règle de validation [`exactLength`](https://github.com/assurance-maladie-digital/design-system/blob/dev/packages/vue-dot/src/rules/exactLength/index.ts).
| 1.0 | Documentation de la règle de validation exactLength - ## Description
En tant que développeur utilisant le Design System, je veux savoir comment utiliser la règle de validation [`exactLength`](https://github.com/assurance-maladie-digital/design-system/blob/dev/packages/vue-dot/src/rules/exactLength/index.ts).
| priority | documentation de la règle de validation exactlength description en tant que développeur utilisant le design system je veux savoir comment utiliser la règle de validation | 1 |
820,143 | 30,761,206,490 | IssuesEvent | 2023-07-29 18:22:32 | prakhartiwari0/Arito | https://api.github.com/repos/prakhartiwari0/Arito | closed | [FEATURE] Add a challenge mode | enhancement priority: Low gssoc23 | **Is your feature request related to a problem? Please describe.**
Yes, the feature request is related to improving the user experience on the mathematical quiz website. Currently, the website lacks a time-based challenge mode and an option to skip questions, which can limit user engagement and frustrate players who encounter difficult or unfamiliar questions.
**Describe the solution you'd like**
I would like the addition of a challenge mode on the mathematical quiz website. This mode would require players to complete tasks within a specific time limit, adding an element of excitement and urgency to the gameplay. Users would be motivated to solve questions quickly and accurately, enhancing their mathematical skills under pressure.
Furthermore, I suggest implementing an option to skip questions. This feature would allow users to bypass questions they find challenging or don't know the answer to, providing a smoother and less frustrating experience. It would enable players to continue progressing through the quiz without getting stuck on a particular question.
**Additional context**
These features can attract a wider audience and encourage users to continue using the website to improve their mathematical abilities.
| 1.0 | [FEATURE] Add a challenge mode - **Is your feature request related to a problem? Please describe.**
Yes, the feature request is related to improving the user experience on the mathematical quiz website. Currently, the website lacks a time-based challenge mode and an option to skip questions, which can limit user engagement and frustrate players who encounter difficult or unfamiliar questions.
**Describe the solution you'd like**
I would like the addition of a challenge mode on the mathematical quiz website. This mode would require players to complete tasks within a specific time limit, adding an element of excitement and urgency to the gameplay. Users would be motivated to solve questions quickly and accurately, enhancing their mathematical skills under pressure.
Furthermore, I suggest implementing an option to skip questions. This feature would allow users to bypass questions they find challenging or don't know the answer to, providing a smoother and less frustrating experience. It would enable players to continue progressing through the quiz without getting stuck on a particular question.
**Additional context**
These features can attract a wider audience and encourage users to continue using the website to improve their mathematical abilities.
| priority | add a challenge mode is your feature request related to a problem please describe yes the feature request is related to improving the user experience on the mathematical quiz website currently the website lacks a time based challenge mode and an option to skip questions which can limit user engagement and frustrate players who encounter difficult or unfamiliar questions describe the solution you d like i would like the addition of a challenge mode on the mathematical quiz website this mode would require players to complete tasks within a specific time limit adding an element of excitement and urgency to the gameplay users would be motivated to solve questions quickly and accurately enhancing their mathematical skills under pressure furthermore i suggest implementing an option to skip questions this feature would allow users to bypass questions they find challenging or don t know the answer to providing a smoother and less frustrating experience it would enable players to continue progressing through the quiz without getting stuck on a particular question additional context these features can attract a wider audience and encourage users to continue using the website to improve their mathematical abilities | 1 |
378,939 | 11,211,008,299 | IssuesEvent | 2020-01-06 14:33:19 | AugurProject/augur | https://api.github.com/repos/AugurProject/augur | closed | Onboarding: modals have strange spacing all of a sudden | Priority: Medium | See comparison shots below for strange spacing in the build.
**note** the heading/description copy is now jumping around as well:
Comparisons shots (design left, build right):
Similar for mobile (build on left):
Figma link for mobile:
https://www.figma.com/file/RMXc7jUWiC6amxz9Q2JK5L/Onboarding-and-Wallet-UX?node-id=1756%3A121
| 1.0 | Onboarding: modals have strange spacing all of a sudden - See comparison shots below for strange spacing in the build.
**note** the heading/description copy is now jumping around as well:
Comparisons shots (design left, build right):
Similar for mobile (build on left):
Figma link for mobile:
https://www.figma.com/file/RMXc7jUWiC6amxz9Q2JK5L/Onboarding-and-Wallet-UX?node-id=1756%3A121
| priority | onboarding modals have strange spacing all of a sudden see comparison shots below for strange spacing in the build note the heading description copy is now jumping around as well comparisons shots design left build right similar for mobile build on left figma link for mobile | 1 |
82,394 | 7,840,481,458 | IssuesEvent | 2018-06-18 16:29:01 | w3c/csswg-drafts | https://api.github.com/repos/w3c/csswg-drafts | closed | [css-cascade] Change the precedence order of cascading origins to match reality better? | Closed Rejected as Invalid Needs Testcase (WPT) css-cascade-3 | Currently, the CSS Cascade spec states that animation declarations [shouldn't override](https://drafts.csswg.org/css-cascade/#cascade-origin) important author declarations. In fact, they do in all browsers except Firefox. There are some articles that appear to describe this overriding as a standard behavior ([1](https://escss.blogspot.com/2015/04/animaciones-transiciones-contra-important.html), [2](https://paulbakaus.com/2017/07/27/more-important-than-important/)), so devs may start to believe that this is how it should be (e.g. [3](https://twitter.com/iamvdo/status/890862651324104704)). The [Chrome bug](https://bugs.chromium.org/p/chromium/issues/detail?id=552085) about this has been reported in 2015, but still there seems to be no visible intent to fix it. Unfortunately I have no data if the corresponding bugs were reported to Safari and Edge.
Wouldn't it be easier to change the behavior of Firefox than to persuade all other browser vendors to change their behavior according to the current spec? Wouldn't it make sense to change the spec to match the reality of the majority of the browsers? | 1.0 | [css-cascade] Change the precedence order of cascading origins to match reality better? - Currently, the CSS Cascade spec states that animation declarations [shouldn't override](https://drafts.csswg.org/css-cascade/#cascade-origin) important author declarations. In fact, they do in all browsers except Firefox. There are some articles that appear to describe this overriding as a standard behavior ([1](https://escss.blogspot.com/2015/04/animaciones-transiciones-contra-important.html), [2](https://paulbakaus.com/2017/07/27/more-important-than-important/)), so devs may start to believe that this is how it should be (e.g. [3](https://twitter.com/iamvdo/status/890862651324104704)). The [Chrome bug](https://bugs.chromium.org/p/chromium/issues/detail?id=552085) about this has been reported in 2015, but still there seems to be no visible intent to fix it. Unfortunately I have no data if the corresponding bugs were reported to Safari and Edge.
Wouldn't it be easier to change the behavior of Firefox than to persuade all other browser vendors to change their behavior according to the current spec? Wouldn't it make sense to change the spec to match the reality of the majority of the browsers? | non_priority | change the precedence order of cascading origins to match reality better currently the css cascade spec states that animation declarations important author declarations in fact they do in all browsers except firefox there are some articles that appear to describe this overriding as a standard behavior so devs may start to believe that this is how it should be e g the about this has been reported in but still there seems to be no visible intent to fix it unfortunately i have no data if the corresponding bugs were reported to safari and edge wouldn t it be easier to change the behavior of firefox than to persuade all other browser vendors to change their behavior according to the current spec wouldn t it make sense to change the spec to match the reality of the majority of the browsers | 0 |
690,481 | 23,661,546,322 | IssuesEvent | 2022-08-26 16:03:21 | PrefectHQ/prefect | https://api.github.com/repos/PrefectHQ/prefect | closed | Add `EXTRA_PIP_PACKAGES` to the `KubernetesJob` block | bug status:backlog v2 priority:medium | ### First check
- [X] I added a descriptive title to this issue.
- [X] I used the GitHub search to find a similar request and didn't find it.
- [X] I searched the Prefect documentation for this feature.
### Prefect Version
2.x
### Describe the proposed behavior
Add it to K8s block
### Describe the current behavior
Atm it only works with the `DockerContainer` block
### Example Use
_No response_
### Additional context
_No response_ | 1.0 | Add `EXTRA_PIP_PACKAGES` to the `KubernetesJob` block - ### First check
- [X] I added a descriptive title to this issue.
- [X] I used the GitHub search to find a similar request and didn't find it.
- [X] I searched the Prefect documentation for this feature.
### Prefect Version
2.x
### Describe the proposed behavior
Add it to K8s block
### Describe the current behavior
Atm it only works with the `DockerContainer` block
### Example Use
_No response_
### Additional context
_No response_ | priority | add extra pip packages to the kubernetesjob block first check i added a descriptive title to this issue i used the github search to find a similar request and didn t find it i searched the prefect documentation for this feature prefect version x describe the proposed behavior add it to block describe the current behavior atm it only works with the dockercontainer block example use no response additional context no response | 1 |
247,341 | 7,917,386,644 | IssuesEvent | 2018-07-04 09:40:58 | georchestra/georchestra | https://api.github.com/repos/georchestra/georchestra | closed | console - navigation by organisation don't lead to users of organisations | 2018 priority-top | When you navigate by organisation /ldapadmin/console/#/orgs/all you have the organisation list and, for each organisation the count of users attached to the organisation.
But at any time you have the list of the users of an organisation. | 1.0 | console - navigation by organisation don't lead to users of organisations - When you navigate by organisation /ldapadmin/console/#/orgs/all you have the organisation list and, for each organisation the count of users attached to the organisation.
But at any time you have the list of the users of an organisation. | priority | console navigation by organisation don t lead to users of organisations when you navigate by organisation ldapadmin console orgs all you have the organisation list and for each organisation the count of users attached to the organisation but at any time you have the list of the users of an organisation | 1 |
56,285 | 13,784,652,596 | IssuesEvent | 2020-10-08 21:14:56 | microsoft/vscode-cpptools | https://api.github.com/repos/microsoft/vscode-cpptools | closed | Unable to compile program in Win 10 with MinGW | build/tasks question | I had met a bug like what https://github.com/microsoft/vscode-cpptools/issues/1329 mentioned, and I fixed it through change the code in task.json to:
```json
"label": "build",
"type": "shell",
"command": "C:/mingw-w64/i686-8.1.0-posix-dwarf-rt_v6-rev0/mingw32/bin/g++.exe",
"args": [
"-g",
"-o",
"FAIL",
"FAIL.c",
],
```
(fix bugs is like torture, so I used FAIL as file name)
now,
1.how to make the filename in "args" is defined automatically?
2.after that, the powershell cmd returns it to me:
```
> Executing task: C:/mingw-w64/i686-8.1.0-posix-dwarf-rt_v6-rev0/mingw32/bin/g++.exe -g -o FAIL FAIL.c <
The terminal process terminated with exit code: 1
Terminal will be reused by tasks, press any key to close it.
```
but I press F5, it sends me that the exe program has not been set up.How to fix it?
Sorry for my improper English and program level, but I am new in VSCode and not familiar with many basic operations, so maybe I will seek help to bugs in preparation of cpp here. | 1.0 | Unable to compile program in Win 10 with MinGW - I had met a bug like what https://github.com/microsoft/vscode-cpptools/issues/1329 mentioned, and I fixed it through change the code in task.json to:
```json
"label": "build",
"type": "shell",
"command": "C:/mingw-w64/i686-8.1.0-posix-dwarf-rt_v6-rev0/mingw32/bin/g++.exe",
"args": [
"-g",
"-o",
"FAIL",
"FAIL.c",
],
```
(fix bugs is like torture, so I used FAIL as file name)
now,
1.how to make the filename in "args" is defined automatically?
2.after that, the powershell cmd returns it to me:
```
> Executing task: C:/mingw-w64/i686-8.1.0-posix-dwarf-rt_v6-rev0/mingw32/bin/g++.exe -g -o FAIL FAIL.c <
The terminal process terminated with exit code: 1
Terminal will be reused by tasks, press any key to close it.
```
but I press F5, it sends me that the exe program has not been set up.How to fix it?
Sorry for my improper English and program level, but I am new in VSCode and not familiar with many basic operations, so maybe I will seek help to bugs in preparation of cpp here. | non_priority | unable to compile program in win with mingw i had met a bug like what mentioned and i fixed it through change the code in task json to json label build type shell command c mingw posix dwarf rt bin g exe args g o fail fail c fix bugs is like torture so i used fail as file name now how to make the filename in args is defined automatically after that the powershell cmd returns it to me executing task c mingw posix dwarf rt bin g exe g o fail fail c the terminal process terminated with exit code terminal will be reused by tasks press any key to close it but i press it sends me that the exe program has not been set up how to fix it sorry for my improper english and program level but i am new in vscode and not familiar with many basic operations so maybe i will seek help to bugs in preparation of cpp here | 0 |
442,976 | 30,868,790,053 | IssuesEvent | 2023-08-03 09:51:36 | HishamWattar/cooks-kingdom | https://api.github.com/repos/HishamWattar/cooks-kingdom | closed | Add admin endpoint api/admin/user/approve-chef/:id | documentation API tests | This endpoint will approve a chef request in case a user wanted to become a chef | 1.0 | Add admin endpoint api/admin/user/approve-chef/:id - This endpoint will approve a chef request in case a user wanted to become a chef | non_priority | add admin endpoint api admin user approve chef id this endpoint will approve a chef request in case a user wanted to become a chef | 0 |
742,146 | 25,840,250,753 | IssuesEvent | 2022-12-12 23:26:38 | rancher/dashboard | https://api.github.com/repos/rancher/dashboard | closed | [Bug] [Monitoring V2] Cannot add Email receivers | kind/bug internal area/monitoring [zube]: QA Working priority/1 team/area3 area/ui JIRA | **What kind of request is this (question/bug/enhancement/feature request):**
Bug
**Steps to reproduce (least amount of steps as possible):**
In this case, the steps we followed were to:
1. Deploy a fresh Rancher v2.5.1 cluster
2. Enable monitoring v2
3. Upgrade Rancher to v2.5.3
4. Attempt to add an email receiver for notifications
**Result:**
Creation fails with `Cannot read property 'data' of undefined`
Workaround is to manually add the receiver to the `alertmanager-rancher-monitoring-alertmanager` secret.
Alerts will work but the receiver and routes will not show in the UI.
We have a HAR capture and a copy of the manually created secret (please DM me internally in Slack)
**Other details that may be helpful:**
We have seen this in another cluster where they were able to workaround by:
1. Filling in the fields to create a Reciever
2. Clicking on Edit as YAML
3. Copying the YAML and manually applying
For them the fix was to disable and re-enable monitoring. It may be worth noting they had upgraded from v2.4.x
gz#14160
gz#15969 | 1.0 | [Bug] [Monitoring V2] Cannot add Email receivers - **What kind of request is this (question/bug/enhancement/feature request):**
Bug
**Steps to reproduce (least amount of steps as possible):**
In this case, the steps we followed were to:
1. Deploy a fresh Rancher v2.5.1 cluster
2. Enable monitoring v2
3. Upgrade Rancher to v2.5.3
4. Attempt to add an email receiver for notifications
**Result:**
Creation fails with `Cannot read property 'data' of undefined`
Workaround is to manually add the receiver to the `alertmanager-rancher-monitoring-alertmanager` secret.
Alerts will work but the receiver and routes will not show in the UI.
We have a HAR capture and a copy of the manually created secret (please DM me internally in Slack)
**Other details that may be helpful:**
We have seen this in another cluster where they were able to workaround by:
1. Filling in the fields to create a Reciever
2. Clicking on Edit as YAML
3. Copying the YAML and manually applying
For them the fix was to disable and re-enable monitoring. It may be worth noting they had upgraded from v2.4.x
gz#14160
gz#15969 | priority | cannot add email receivers what kind of request is this question bug enhancement feature request bug steps to reproduce least amount of steps as possible in this case the steps we followed were to deploy a fresh rancher cluster enable monitoring upgrade rancher to attempt to add an email receiver for notifications result creation fails with cannot read property data of undefined workaround is to manually add the receiver to the alertmanager rancher monitoring alertmanager secret alerts will work but the receiver and routes will not show in the ui we have a har capture and a copy of the manually created secret please dm me internally in slack other details that may be helpful we have seen this in another cluster where they were able to workaround by filling in the fields to create a reciever clicking on edit as yaml copying the yaml and manually applying for them the fix was to disable and re enable monitoring it may be worth noting they had upgraded from x gz gz | 1 |
554,241 | 16,415,260,020 | IssuesEvent | 2021-05-19 05:31:26 | Nelson-Gon/pycite | https://api.github.com/repos/Nelson-Gon/pycite | closed | Automated documentation and release | enhancement good first issue help wanted priority:medium | **Description**
I would like to automate the doc generation and release process.
**Similar Features**
This is similar to `scripts/mkdocs.sh` and `scripts/release.sh`.
**Feature Details**
Sufficiently described.
**Proposed Implementation**
Use an Actions run to automate these e.g. "on release" to run "release.sh". Should also set environmental variables i.e. PyPI username and password.
| 1.0 | Automated documentation and release - **Description**
I would like to automate the doc generation and release process.
**Similar Features**
This is similar to `scripts/mkdocs.sh` and `scripts/release.sh`.
**Feature Details**
Sufficiently described.
**Proposed Implementation**
Use an Actions run to automate these e.g. "on release" to run "release.sh". Should also set environmental variables i.e. PyPI username and password.
| priority | automated documentation and release description i would like to automate the doc generation and release process similar features this is similar to scripts mkdocs sh and scripts release sh feature details sufficiently described proposed implementation use an actions run to automate these e g on release to run release sh should also set environmental variables i e pypi username and password | 1 |
53,429 | 22,783,767,299 | IssuesEvent | 2022-07-09 00:42:45 | operate-first/operations | https://api.github.com/repos/operate-first/operations | closed | Let's make Grafana landing page more friendly | lifecycle/rotten area/service/grafana area/monitoring | The landing page at https://grafana.operate-first.cloud/ is just the Grafana default. Let's replace that with something that highlights interesting dashboards, or maybe provides information about how to contribute new dashboards (or links to appropriate docs), etc.
| 1.0 | Let's make Grafana landing page more friendly - The landing page at https://grafana.operate-first.cloud/ is just the Grafana default. Let's replace that with something that highlights interesting dashboards, or maybe provides information about how to contribute new dashboards (or links to appropriate docs), etc.
| non_priority | let s make grafana landing page more friendly the landing page at is just the grafana default let s replace that with something that highlights interesting dashboards or maybe provides information about how to contribute new dashboards or links to appropriate docs etc | 0 |
43,286 | 2,887,367,329 | IssuesEvent | 2015-06-12 14:35:58 | FLEXIcontent/flexicontent-cck | https://api.github.com/repos/FLEXIcontent/flexicontent-cck | opened | Add to content types selection for menu item when editing, thus to allow custom Joomla template | Priority Normal | The Joomla template used in item views, may not be appropriate or desirable for FLEXIcontent item form
The FLEXIcontent edit links should include a different menu item that the item viewing links
- this should be a parameter per content type | 1.0 | Add to content types selection for menu item when editing, thus to allow custom Joomla template - The Joomla template used in item views, may not be appropriate or desirable for FLEXIcontent item form
The FLEXIcontent edit links should include a different menu item that the item viewing links
- this should be a parameter per content type | priority | add to content types selection for menu item when editing thus to allow custom joomla template the joomla template used in item views may not be appropriate or desirable for flexicontent item form the flexicontent edit links should include a different menu item that the item viewing links this should be a parameter per content type | 1 |
134,727 | 19,318,145,502 | IssuesEvent | 2021-12-14 00:19:28 | timberline-secondary/hackerspace-todo | https://api.github.com/repos/timberline-secondary/hackerspace-todo | closed | Web Dev HTMl & CSS FInal Project? | Campaigns: New Course: Web Design | This might make a good final project for HTML and CSS (pre-JavaScript)
https://www.youtube.com/watch?v=-8LTPIJBGwQ | 1.0 | Web Dev HTMl & CSS FInal Project? - This might make a good final project for HTML and CSS (pre-JavaScript)
https://www.youtube.com/watch?v=-8LTPIJBGwQ | non_priority | web dev html css final project this might make a good final project for html and css pre javascript | 0 |
218,066 | 7,330,368,590 | IssuesEvent | 2018-03-05 09:42:03 | NCEAS/metacat | https://api.github.com/repos/NCEAS/metacat | closed | Dependence of NCEAS registry on Admin database | Category: registry Component: Bugzilla-Id Priority: Normal Status: Resolved Tracker: Bug | ---
Author Name: **Saurabh Garg** (Saurabh Garg)
Original Redmine Issue: 1552, https://projects.ecoinformatics.org/ecoinfo/issues/1552
Original Date: 2004-05-04
Original Assignee: Shaun Walbridge
---
This is reported by Sandy:
She had problems accessing the registry when she was in Washington DC and
giving demos of the registry to NSF.
Everything was working fine except for the register dataset page for NCEAS. So
other functions like search etc were working properly - but
http://knb.ecoinformatics.org/cgi-bin/register-dataset.cgi?cfg=nceas was
showing up as blank page.
I think (and I told her the same thing) that it was the admin database that was
causing the problem. The project list is generated from the admin database and
if admin database is down - we get a blank page for the url
http://knb.ecoinformatics.org/cgi-bin/register-dataset.cgi?cfg=nceas.
Solution: We should probably make the project list independent of the admin
database... (and/or) we should put some kind of error recovery in case admin
database is down.
| 1.0 | Dependence of NCEAS registry on Admin database - ---
Author Name: **Saurabh Garg** (Saurabh Garg)
Original Redmine Issue: 1552, https://projects.ecoinformatics.org/ecoinfo/issues/1552
Original Date: 2004-05-04
Original Assignee: Shaun Walbridge
---
This is reported by Sandy:
She had problems accessing the registry when she was in Washington DC and
giving demos of the registry to NSF.
Everything was working fine except for the register dataset page for NCEAS. So
other functions like search etc were working properly - but
http://knb.ecoinformatics.org/cgi-bin/register-dataset.cgi?cfg=nceas was
showing up as blank page.
I think (and I told her the same thing) that it was the admin database that was
causing the problem. The project list is generated from the admin database and
if admin database is down - we get a blank page for the url
http://knb.ecoinformatics.org/cgi-bin/register-dataset.cgi?cfg=nceas.
Solution: We should probably make the project list independent of the admin
database... (and/or) we should put some kind of error recovery in case admin
database is down.
| priority | dependence of nceas registry on admin database author name saurabh garg saurabh garg original redmine issue original date original assignee shaun walbridge this is reported by sandy she had problems accessing the registry when she was in washington dc and giving demos of the registry to nsf everything was working fine except for the register dataset page for nceas so other functions like search etc were working properly but was showing up as blank page i think and i told her the same thing that it was the admin database that was causing the problem the project list is generated from the admin database and if admin database is down we get a blank page for the url solution we should probably make the project list independent of the admin database and or we should put some kind of error recovery in case admin database is down | 1 |
627,612 | 19,910,180,150 | IssuesEvent | 2022-01-25 16:25:39 | mozilla/addons-server | https://api.github.com/repos/mozilla/addons-server | closed | Stop exposing reviewer names to developers | component: reviewer tools priority: p3 | This is a spin-off from https://github.com/mozilla/addons-server/issues/17318 and is just about removing the names of reviewers from any screens that developers can see, which should be exclusively devhub pages. | 1.0 | Stop exposing reviewer names to developers - This is a spin-off from https://github.com/mozilla/addons-server/issues/17318 and is just about removing the names of reviewers from any screens that developers can see, which should be exclusively devhub pages. | priority | stop exposing reviewer names to developers this is a spin off from and is just about removing the names of reviewers from any screens that developers can see which should be exclusively devhub pages | 1 |
396,457 | 27,119,381,517 | IssuesEvent | 2023-02-15 21:22:56 | MatteoCazzaniga/IngegneriaSoftware_22-23 | https://api.github.com/repos/MatteoCazzaniga/IngegneriaSoftware_22-23 | closed | Creazione Immagini Diagrammi UML mancanti | documentation | Creazione file jpg dei diagrammi UML mancanti (diagramma dei casi d'uso e diagramma delle attività) | 1.0 | Creazione Immagini Diagrammi UML mancanti - Creazione file jpg dei diagrammi UML mancanti (diagramma dei casi d'uso e diagramma delle attività) | non_priority | creazione immagini diagrammi uml mancanti creazione file jpg dei diagrammi uml mancanti diagramma dei casi d uso e diagramma delle attività | 0 |
360,317 | 25,285,501,064 | IssuesEvent | 2022-11-16 18:56:39 | WordPress/Documentation-Issue-Tracker | https://api.github.com/repos/WordPress/Documentation-Issue-Tracker | closed | [HelpHub] File block | user documentation block editor medium priority 6.1 | Article: https://wordpress.org/support/article/file-block/
## Updating for 6.1
- [x] Display upload error notices using snackbars. [43893](https://github.com/WordPress/gutenberg/pull/43893)
- [x] Remove redundant block name from "settings" panels [40275](https://github.com/WordPress/gutenberg/pull/40275)
## General
- [x] Make sure all screenshots are relevant to the latest version
- [x] Make sure videos are up to date
- [x] Add ALT tags for the images
- [x] Make sure the headings are in sentence case
- [x] Convert all reusable blocks to a ‘regular block’.
- [x] Update the changelog at the end of the article
| 1.0 | [HelpHub] File block - Article: https://wordpress.org/support/article/file-block/
## Updating for 6.1
- [x] Display upload error notices using snackbars. [43893](https://github.com/WordPress/gutenberg/pull/43893)
- [x] Remove redundant block name from "settings" panels [40275](https://github.com/WordPress/gutenberg/pull/40275)
## General
- [x] Make sure all screenshots are relevant to the latest version
- [x] Make sure videos are up to date
- [x] Add ALT tags for the images
- [x] Make sure the headings are in sentence case
- [x] Convert all reusable blocks to a ‘regular block’.
- [x] Update the changelog at the end of the article
| non_priority | file block article updating for display upload error notices using snackbars remove redundant block name from settings panels general make sure all screenshots are relevant to the latest version make sure videos are up to date add alt tags for the images make sure the headings are in sentence case convert all reusable blocks to a ‘regular block’ update the changelog at the end of the article | 0 |
214,870 | 24,120,884,260 | IssuesEvent | 2022-09-20 18:35:46 | bcgov/cloud-pathfinder | https://api.github.com/repos/bcgov/cloud-pathfinder | opened | Compile a list with the guardrails rules that limit/enable the workload accounts | Security Quality Assurance | **Describe the issue**
There is not a guardrails list. The closest thing is a bunch of Service Control Policies that can be found at https://github.com/aws-samples/aws-secure-environment-accelerator/tree/main/reference-artifacts/SCPs
**Additional context**
The guardrails are a crucial characteristic of the ECF. They are tested and poked in several aspects (CSPM, scripts that detect any change in the rules/policies). The approach for which this ticket is required is to impersonate a user, and then poke the guardrails, to see which actions are allowed and which ones are not permitted. However, before doing this "poke" we need to have the list of actions.
**Definition of done**
A list (text document) of the actions that are allowed/denied, probably sorted by role
| True | Compile a list with the guardrails rules that limit/enable the workload accounts - **Describe the issue**
There is not a guardrails list. The closest thing is a bunch of Service Control Policies that can be found at https://github.com/aws-samples/aws-secure-environment-accelerator/tree/main/reference-artifacts/SCPs
**Additional context**
The guardrails are a crucial characteristic of the ECF. They are tested and poked in several aspects (CSPM, scripts that detect any change in the rules/policies). The approach for which this ticket is required is to impersonate a user, and then poke the guardrails, to see which actions are allowed and which ones are not permitted. However, before doing this "poke" we need to have the list of actions.
**Definition of done**
A list (text document) of the actions that are allowed/denied, probably sorted by role
| non_priority | compile a list with the guardrails rules that limit enable the workload accounts describe the issue there is not a guardrails list the closest thing is a bunch of service control policies that can be found at additional context the guardrails are a crucial characteristic of the ecf they are tested and poked in several aspects cspm scripts that detect any change in the rules policies the approach for which this ticket is required is to impersonate a user and then poke the guardrails to see which actions are allowed and which ones are not permitted however before doing this poke we need to have the list of actions definition of done a list text document of the actions that are allowed denied probably sorted by role | 0 |
304,994 | 23,093,672,158 | IssuesEvent | 2022-07-26 17:21:06 | hashicorp/terraform-provider-aws | https://api.github.com/repos/hashicorp/terraform-provider-aws | closed | aws_appstream_stack.access_endpoints argument documentation missing | documentation service/appstream | <!---
Please note the following potential times when an issue might be in Terraform core:
* [Configuration Language](https://www.terraform.io/docs/configuration/index.html) or resource ordering issues
* [State](https://www.terraform.io/docs/state/index.html) and [State Backend](https://www.terraform.io/docs/backends/index.html) issues
* [Provisioner](https://www.terraform.io/docs/provisioners/index.html) issues
* [Registry](https://registry.terraform.io/) issues
* Spans resources across multiple providers
If you are running into one of these scenarios, we recommend opening an issue in the [Terraform core repository](https://github.com/hashicorp/terraform/) instead.
--->
<!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Affected Resource(s)
<!--- Please list the affected resources and data sources. --->
* aws_appstream_stack
`aws_appstream_stack` [documentation page](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/appstream_stack) is missing documentation for the `access_endpoints` argument.
https://github.com/hashicorp/terraform-provider-aws/blob/main/internal/service/appstream/stack.go#L38
https://github.com/hashicorp/terraform-provider-aws/blob/main/website/docs/r/appstream_stack.html.markdown
| 1.0 | aws_appstream_stack.access_endpoints argument documentation missing - <!---
Please note the following potential times when an issue might be in Terraform core:
* [Configuration Language](https://www.terraform.io/docs/configuration/index.html) or resource ordering issues
* [State](https://www.terraform.io/docs/state/index.html) and [State Backend](https://www.terraform.io/docs/backends/index.html) issues
* [Provisioner](https://www.terraform.io/docs/provisioners/index.html) issues
* [Registry](https://registry.terraform.io/) issues
* Spans resources across multiple providers
If you are running into one of these scenarios, we recommend opening an issue in the [Terraform core repository](https://github.com/hashicorp/terraform/) instead.
--->
<!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Affected Resource(s)
<!--- Please list the affected resources and data sources. --->
* aws_appstream_stack
`aws_appstream_stack` [documentation page](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/appstream_stack) is missing documentation for the `access_endpoints` argument.
https://github.com/hashicorp/terraform-provider-aws/blob/main/internal/service/appstream/stack.go#L38
https://github.com/hashicorp/terraform-provider-aws/blob/main/website/docs/r/appstream_stack.html.markdown
| non_priority | aws appstream stack access endpoints argument documentation missing please note the following potential times when an issue might be in terraform core or resource ordering issues and issues issues issues spans resources across multiple providers if you are running into one of these scenarios we recommend opening an issue in the instead community note please vote on this issue by adding a 👍 to the original issue to help the community and maintainers prioritize this request please do not leave or other comments that do not add relevant new information or questions they generate extra noise for issue followers and do not help prioritize the request if you are interested in working on this issue or have submitted a pull request please leave a comment affected resource s aws appstream stack aws appstream stack is missing documentation for the access endpoints argument | 0 |
296,507 | 9,116,750,599 | IssuesEvent | 2019-02-22 09:52:11 | Xceptance/neodymium-library | https://api.github.com/repos/Xceptance/neodymium-library | closed | Update Cucumber to 4.x | Medium Priority doneInDevelop recheckedInDevelop update-dependency | Update Cucumber version to 3.x once the allure support >= version 2.8 is available.
See the link for latest release: https://github.com/allure-framework/allure2/releases
Remove "io.qameta.allure.cucumber2jvm.AllureCucumber2Jvm" if the update above is successful.
| 1.0 | Update Cucumber to 4.x - Update Cucumber version to 3.x once the allure support >= version 2.8 is available.
See the link for latest release: https://github.com/allure-framework/allure2/releases
Remove "io.qameta.allure.cucumber2jvm.AllureCucumber2Jvm" if the update above is successful.
| priority | update cucumber to x update cucumber version to x once the allure support version is available see the link for latest release remove io qameta allure if the update above is successful | 1 |
97,504 | 11,015,028,284 | IssuesEvent | 2019-12-05 00:19:24 | openenclave/openenclave | https://api.github.com/repos/openenclave/openenclave | closed | API docs are too hard to find | documentation triaged | Currently they're hidden in the obscure "Versions" link at openenclave.io
There's nothing about docs, or APIs, or anything else that one would be looking for to find API docs. And the main GitHub/openenclave readme docs just point to openenclave.io. | 1.0 | API docs are too hard to find - Currently they're hidden in the obscure "Versions" link at openenclave.io
There's nothing about docs, or APIs, or anything else that one would be looking for to find API docs. And the main GitHub/openenclave readme docs just point to openenclave.io. | non_priority | api docs are too hard to find currently they re hidden in the obscure versions link at openenclave io there s nothing about docs or apis or anything else that one would be looking for to find api docs and the main github openenclave readme docs just point to openenclave io | 0 |
10,840 | 12,824,604,168 | IssuesEvent | 2020-07-06 13:44:33 | pingcap/tidb | https://api.github.com/repos/pingcap/tidb | closed | ORM and application Support | status/TODO status/WIP type/compatibility | Python:
- [ ] SQLAlchemy
- [ ] Peewee
- [ ] django
- [ ] ponyorm
Go:
Orm:
- [x] xorm: https://github.com/go-xorm/xorm
- [x] beego: https://github.com/astaxie/beego/tree/master/orm
- [x] go-sql-test: https://github.com/bradfitz/go-sql-test
- [ ] upper.io: https://upper.io/db.v1/mysql
Application:
- [x] Gogs: https://github.com/gogits/gogs
- [ ] Dalga: https://github.com/cenkalti/dalga
Java：
- [x] Mybatis
- [ ] Jdbctemplate
- [ ] Hibernate
- [ ] Play
PHP:
- [ ] phabricator: http://phabricator.org/
- [x] phpmyadmin
- [x] wordpress
- [ ] yii: http://www.yiiframework.com/doc/guide/1.1/en/database.ar
- [ ] discuz!: http://www.discuz.net/
- [ ] drupal: https://www.drupal.org/
- [ ] [Eloquent](https://laravel.com/docs/5.5/eloquent)
Dotnet:
- [ ] [Entity Framework Core](https://github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql)
| True | ORM and application Support - Python:
- [ ] SQLAlchemy
- [ ] Peewee
- [ ] django
- [ ] ponyorm
Go:
Orm:
- [x] xorm: https://github.com/go-xorm/xorm
- [x] beego: https://github.com/astaxie/beego/tree/master/orm
- [x] go-sql-test: https://github.com/bradfitz/go-sql-test
- [ ] upper.io: https://upper.io/db.v1/mysql
Application:
- [x] Gogs: https://github.com/gogits/gogs
- [ ] Dalga: https://github.com/cenkalti/dalga
Java：
- [x] Mybatis
- [ ] Jdbctemplate
- [ ] Hibernate
- [ ] Play
PHP:
- [ ] phabricator: http://phabricator.org/
- [x] phpmyadmin
- [x] wordpress
- [ ] yii: http://www.yiiframework.com/doc/guide/1.1/en/database.ar
- [ ] discuz!: http://www.discuz.net/
- [ ] drupal: https://www.drupal.org/
- [ ] [Eloquent](https://laravel.com/docs/5.5/eloquent)
Dotnet:
- [ ] [Entity Framework Core](https://github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql)
| non_priority | orm and application support python sqlalchemy peewee django ponyorm go orm xorm beego go sql test upper io application gogs dalga java： mybatis jdbctemplate hibernate play php phabricator phpmyadmin wordpress yii discuz drupal dotnet | 0 |
31,792 | 2,736,876,077 | IssuesEvent | 2015-04-19 21:03:51 | x360ce/x360ce | https://api.github.com/repos/x360ce/x360ce | closed | llll | bug imported invalid Priority-Medium | _From [Crack.bi...@gmail.com](https://code.google.com/u/110974868023865476405/) on May 12, 2010 09:28:38_
What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? What version of the product are you using? On what operating system? What gamepad are you using? On what version of drivers? Please set third label to Core if issue affect emulator (dll file) or App if issue affect x360ce.App application (exe file). Also if you want you can provide any additional information below.
_Original issue: http://code.google.com/p/x360ce/issues/detail?id=16_ | 1.0 | llll - _From [Crack.bi...@gmail.com](https://code.google.com/u/110974868023865476405/) on May 12, 2010 09:28:38_
What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? What version of the product are you using? On what operating system? What gamepad are you using? On what version of drivers? Please set third label to Core if issue affect emulator (dll file) or App if issue affect x360ce.App application (exe file). Also if you want you can provide any additional information below.
_Original issue: http://code.google.com/p/x360ce/issues/detail?id=16_ | priority | llll from on may what steps will reproduce the problem what is the expected output what do you see instead what version of the product are you using on what operating system what gamepad are you using on what version of drivers please set third label to core if issue affect emulator dll file or app if issue affect app application exe file also if you want you can provide any additional information below original issue | 1 |
670,977 | 22,716,469,887 | IssuesEvent | 2022-07-06 02:51:37 | ansible-collections/azure | https://api.github.com/repos/ansible-collections/azure | closed | Couldn't find api version for Microsoft.DataFactory/factories?api-version=2018-06-01 | medium_priority not a bug | - name: Check if Data Factory ({{ az_datafactory_name }}) already exists
azure.azcollection.azure_rm_resource_info:
auth_source: auto
client_id: "{{ az_client_id }}"
secret: "{{ az_secret }}"
tenant: "{{ az_tenant_id }}"
subscription_id: "{{ az_subscription_id }}"
url: "https://management.azure.com/subscriptions/{{ az_subscription_id }}/resourceGroups/{{ az_resource_group_name }}/providers/Microsoft.DataFactory/factories?api-version=2018-06-01"
register: az_datafactory
Output:
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Couldn't find api version for Microsoft.DataFactory/factories?api-version=2018-06-01"} | 1.0 | Couldn't find api version for Microsoft.DataFactory/factories?api-version=2018-06-01 - - name: Check if Data Factory ({{ az_datafactory_name }}) already exists
azure.azcollection.azure_rm_resource_info:
auth_source: auto
client_id: "{{ az_client_id }}"
secret: "{{ az_secret }}"
tenant: "{{ az_tenant_id }}"
subscription_id: "{{ az_subscription_id }}"
url: "https://management.azure.com/subscriptions/{{ az_subscription_id }}/resourceGroups/{{ az_resource_group_name }}/providers/Microsoft.DataFactory/factories?api-version=2018-06-01"
register: az_datafactory
Output:
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Couldn't find api version for Microsoft.DataFactory/factories?api-version=2018-06-01"} | priority | couldn t find api version for microsoft datafactory factories api version name check if data factory az datafactory name already exists azure azcollection azure rm resource info auth source auto client id az client id secret az secret tenant az tenant id subscription id az subscription id url az subscription id resourcegroups az resource group name providers microsoft datafactory factories api version register az datafactory output fatal failed changed false msg couldn t find api version for microsoft datafactory factories api version | 1 |
1,935 | 4,763,886,581 | IssuesEvent | 2016-10-25 15:32:42 | openvstorage/alba | https://api.github.com/repos/openvstorage/alba | closed | Claim osd looping and high cpu usage | process_wontfix SRP type_bug | ## Problem description
When I logged into my setup, I found that my root partition was completely full. The culprit was found in /var/log/upstart/alba-asd *.
One of the asd logging was full of:
```
2016-10-19 21:53:42 16108 +0200 - ovs-node1 - 9453/0 - alba/asd - 5366 - info - returning error (Asd_protocol.Protocol.Error.Assert_failed; "p\000\000\000\000n\000\000\000\000g\000\000\000\000\000\000\000\000 \000\000\000\022v\0119\127\220C\168\166\216\005 \228\210\175\242\021\217\143aG\232A\158\184.\146\164\240g=a\142\159\003\000\002\000\000\000\000\000\000\000")
2016-10-19 21:53:42 17439 +0200 - ovs-node1 - 9453/0 - alba/asd - 5367 - warning - Assertion failed, expected some but got None instead
2016-10-19 21:53:42 17473 +0200 - ovs-node1 - 9453/0 - alba/asd - 5368 - info - returning error (Asd_protocol.Protocol.Error.Assert_failed; "p\000\000\000\000n\000\000\000\000g\000\000\000\000\000\000\000\000 \000\000\000\022v\0119\127\220C\168\166\216\005 \228\210\175\242\021\217\143aG\232A\158\184.\146\164\240g=a\142\159\004\000\002\000\000\000\000\000\000\000")
2016-10-19 21:53:42 22216 +0200 - ovs-node1 - 9453/0 - alba/asd - 5369 - warning - Assertion failed, expected some but got None instead
2016-10-19 21:53:42 22241 +0200 - ovs-node1 - 9453/0 - alba/asd - 5370 - info - returning error (Asd_protocol.Protocol.Error.Assert_failed;
```
Every node within my cluster had an identical issue but the asd-id was different each time.
After closer inspection I spotted the following:
```
alba 9333 39.7 0.3 459100 52200 ? Rsl Oct19 380:40 /usr/bin/alba asd-start --config arakoon://config/ovs/alba/asds/0Z1uxwBY2djSHiAdG5xG855bwCHhZKfO/config?ini=%2Fopt%2Fasd-manager%2Fconfig%2Farakoon_cacc.ini --log-sink console:
```
The asd process is taking up alot of cpu.
The reason why is the claim-osd that is looping:
```
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 14619 ovs 20 0 7718872 6.096g 2652 S 47.5 38.9 325:26.80
/usr/bin/alba claim-osd --config=arakoon://config/ovs/arakoon/mybackend-global-abm/config?ini=%2Fopt%2FOpenvStorage%2Fconfig%2Farakoon_cacc.ini --long-id=0ff56d57-930c-4a38-96a8-71da45cd7c3c --to-json 9333 alba 20 0 455944 50164 4876 R 43.2 0.3 384:15.83 /usr/bin/alba asd-start --config arakoon://config/ovs/alba/asds/0Z1uxwBY2djSHiAdG5xG855bwCHhZKfO/config?ini=%2Fopt%2Fasd-manager%2Fconfig%2Farakoon_cacc.ini --log-sink console:
```
When the claim-osd was killed, my cpu usage was back to normal. | 1.0 | Claim osd looping and high cpu usage - ## Problem description
When I logged into my setup, I found that my root partition was completely full. The culprit was found in /var/log/upstart/alba-asd *.
One of the asd logging was full of:
```
2016-10-19 21:53:42 16108 +0200 - ovs-node1 - 9453/0 - alba/asd - 5366 - info - returning error (Asd_protocol.Protocol.Error.Assert_failed; "p\000\000\000\000n\000\000\000\000g\000\000\000\000\000\000\000\000 \000\000\000\022v\0119\127\220C\168\166\216\005 \228\210\175\242\021\217\143aG\232A\158\184.\146\164\240g=a\142\159\003\000\002\000\000\000\000\000\000\000")
2016-10-19 21:53:42 17439 +0200 - ovs-node1 - 9453/0 - alba/asd - 5367 - warning - Assertion failed, expected some but got None instead
2016-10-19 21:53:42 17473 +0200 - ovs-node1 - 9453/0 - alba/asd - 5368 - info - returning error (Asd_protocol.Protocol.Error.Assert_failed; "p\000\000\000\000n\000\000\000\000g\000\000\000\000\000\000\000\000 \000\000\000\022v\0119\127\220C\168\166\216\005 \228\210\175\242\021\217\143aG\232A\158\184.\146\164\240g=a\142\159\004\000\002\000\000\000\000\000\000\000")
2016-10-19 21:53:42 22216 +0200 - ovs-node1 - 9453/0 - alba/asd - 5369 - warning - Assertion failed, expected some but got None instead
2016-10-19 21:53:42 22241 +0200 - ovs-node1 - 9453/0 - alba/asd - 5370 - info - returning error (Asd_protocol.Protocol.Error.Assert_failed;
```
Every node within my cluster had an identical issue but the asd-id was different each time.
After closer inspection I spotted the following:
```
alba 9333 39.7 0.3 459100 52200 ? Rsl Oct19 380:40 /usr/bin/alba asd-start --config arakoon://config/ovs/alba/asds/0Z1uxwBY2djSHiAdG5xG855bwCHhZKfO/config?ini=%2Fopt%2Fasd-manager%2Fconfig%2Farakoon_cacc.ini --log-sink console:
```
The asd process is taking up alot of cpu.
The reason why is the claim-osd that is looping:
```
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 14619 ovs 20 0 7718872 6.096g 2652 S 47.5 38.9 325:26.80
/usr/bin/alba claim-osd --config=arakoon://config/ovs/arakoon/mybackend-global-abm/config?ini=%2Fopt%2FOpenvStorage%2Fconfig%2Farakoon_cacc.ini --long-id=0ff56d57-930c-4a38-96a8-71da45cd7c3c --to-json 9333 alba 20 0 455944 50164 4876 R 43.2 0.3 384:15.83 /usr/bin/alba asd-start --config arakoon://config/ovs/alba/asds/0Z1uxwBY2djSHiAdG5xG855bwCHhZKfO/config?ini=%2Fopt%2Fasd-manager%2Fconfig%2Farakoon_cacc.ini --log-sink console:
```
When the claim-osd was killed, my cpu usage was back to normal. | non_priority | claim osd looping and high cpu usage problem description when i logged into my setup i found that my root partition was completely full the culprit was found in var log upstart alba asd one of the asd logging was full of ovs alba asd info returning error asd protocol protocol error assert failed p a ovs alba asd warning assertion failed expected some but got none instead ovs alba asd info returning error asd protocol protocol error assert failed p a ovs alba asd warning assertion failed expected some but got none instead ovs alba asd info returning error asd protocol protocol error assert failed every node within my cluster had an identical issue but the asd id was different each time after closer inspection i spotted the following alba rsl usr bin alba asd start config arakoon config ovs alba asds config ini manager cacc ini log sink console the asd process is taking up alot of cpu the reason why is the claim osd that is looping pid user pr ni virt res shr s cpu mem time command ovs s usr bin alba claim osd config arakoon config ovs arakoon mybackend global abm config ini cacc ini long id to json alba r usr bin alba asd start config arakoon config ovs alba asds config ini manager cacc ini log sink console when the claim osd was killed my cpu usage was back to normal | 0 |
570,212 | 17,021,263,351 | IssuesEvent | 2021-07-02 19:32:49 | phetsims/balloons-and-static-electricity | https://api.github.com/repos/phetsims/balloons-and-static-electricity | closed | The "Remove Wall" button is no longer visible on the wall | priority:2-high status:blocks-publication status:ready-for-review | While testing today, I noticed that the "Remove Wall" button seemed to be gone, but then I found I could navigate to it using the tab keys. Turns out that it is now behind the wall instead of in from of it. After a little detective work, I believe I've traced it to this commit: https://github.com/phetsims/joist/commit/17645a7ad98b2177524b9cc9e61b5d0a9660a82c.
This was done by @jessegreenberg, so I'm going to assign it to him.
In general, this change seems like it could have similar impacts on other sims, so I'd recommend having QA regression test all sims that are using `pdomControlAreaNode` and `pdomPlayAreaNode` if we decide to keep this change. | 1.0 | The "Remove Wall" button is no longer visible on the wall - While testing today, I noticed that the "Remove Wall" button seemed to be gone, but then I found I could navigate to it using the tab keys. Turns out that it is now behind the wall instead of in from of it. After a little detective work, I believe I've traced it to this commit: https://github.com/phetsims/joist/commit/17645a7ad98b2177524b9cc9e61b5d0a9660a82c.
This was done by @jessegreenberg, so I'm going to assign it to him.
In general, this change seems like it could have similar impacts on other sims, so I'd recommend having QA regression test all sims that are using `pdomControlAreaNode` and `pdomPlayAreaNode` if we decide to keep this change. | priority | the remove wall button is no longer visible on the wall while testing today i noticed that the remove wall button seemed to be gone but then i found i could navigate to it using the tab keys turns out that it is now behind the wall instead of in from of it after a little detective work i believe i ve traced it to this commit this was done by jessegreenberg so i m going to assign it to him in general this change seems like it could have similar impacts on other sims so i d recommend having qa regression test all sims that are using pdomcontrolareanode and pdomplayareanode if we decide to keep this change | 1 |
676,349 | 23,123,448,944 | IssuesEvent | 2022-07-28 01:25:22 | FEeasy404/GameUs | https://api.github.com/repos/FEeasy404/GameUs | closed | 하단탭 화면 좁아질 경우 height가 높아짐 | 🐛bug 🌿Priority: Low ⚔Fix | ## 버그 발생 설명
- 화면이 좁아질 경우 하단탭의 height가 높아져 페이지 하단 내용을 가립니다!
- 게시물수정' 텍스트가 화면이 좁아져도 한줄로 유지되도록 하면 좋을것 같습니다!
## 할 일
- [ ] 하단탭 height 수정
## ETC
| 1.0 | 하단탭 화면 좁아질 경우 height가 높아짐 - ## 버그 발생 설명
- 화면이 좁아질 경우 하단탭의 height가 높아져 페이지 하단 내용을 가립니다!
- 게시물수정' 텍스트가 화면이 좁아져도 한줄로 유지되도록 하면 좋을것 같습니다!
## 할 일
- [ ] 하단탭 height 수정
## ETC
| priority | 하단탭 화면 좁아질 경우 height가 높아짐 버그 발생 설명 화면이 좁아질 경우 하단탭의 height가 높아져 페이지 하단 내용을 가립니다 게시물수정 텍스트가 화면이 좁아져도 한줄로 유지되도록 하면 좋을것 같습니다 할 일 하단탭 height 수정 etc | 1 |
177,122 | 13,684,353,727 | IssuesEvent | 2020-09-30 04:38:30 | dotnet/roslyn | https://api.github.com/repos/dotnet/roslyn | closed | LiveShare tests are crashing and causing build flakiness | Area-IDE Flaky Resolution-Not Applicable Test | Failing builds:
- https://dev.azure.com/dnceng/public/_build/results/buildId=564945&view=artifacts&type=publishedArtifacts
- https://dev.azure.com/dnceng/public/_build/results?buildId=563985&view=artifacts&type=publishedArtifacts
The crash appears to occur on xunit shutdown. The actual log file for the tests indicates that everything succeeded. But xunit is exiting with a failure code and no output.
| 1.0 | LiveShare tests are crashing and causing build flakiness - Failing builds:
- https://dev.azure.com/dnceng/public/_build/results/buildId=564945&view=artifacts&type=publishedArtifacts
- https://dev.azure.com/dnceng/public/_build/results?buildId=563985&view=artifacts&type=publishedArtifacts
The crash appears to occur on xunit shutdown. The actual log file for the tests indicates that everything succeeded. But xunit is exiting with a failure code and no output.
| non_priority | liveshare tests are crashing and causing build flakiness failing builds the crash appears to occur on xunit shutdown the actual log file for the tests indicates that everything succeeded but xunit is exiting with a failure code and no output | 0 |
590,482 | 17,778,740,706 | IssuesEvent | 2021-08-30 23:31:53 | dtcenter/MET | https://api.github.com/repos/dtcenter/MET | closed | Enhance MET to compute the CBS score. | type: new feature priority: blocker requestor: DTC/AF V&V required: FOR DEVELOPMENT RELEASE | ## Describe the New Feature ##
The AF project needs to generate the CBS score on its GPP verification. This requires adding another method of interpolation (areal). Michelle Harrold has provided some code (from Bob Craig) and helpful references (see attachments).
From Bob:
"All, the attached document describes the CBS verification process , I.7-36 Table F. The verification is done over a 1.5 degree remap of the model using an area averaging technique. The ground truth is the model analysis. I have attached the program we use to average the data. The index based on the CBS score is from UKMO. I attached the program that calculates it along with the configuration files."
I have attached the WMO document with I.7-36 Table F as well as the the areal weighting IDL script (around line 251 is the weighting code) and the CBS score python program. Also, the areal weighting script references a paper, which might have some helpful background:
https://www.wmo.int/pages/prog/www/BAS/documents/AnnexDoc3-3.pdf
The work for this issue may include supporting a new interpolation method, computing the CBS score, and writing its output somewhere. Recommend coordinating with @michelleharrold since she's likely familiar with the details.
### Acceptance Testing ###
*List input data types and sources.*
*Describe tests required for new functionality.*
### Time Estimate ###
*Estimate the amount of work required here.*
*Issues should represent approximately 1 to 3 days of work.*
### Sub-Issues ###
Consider breaking the new feature down into sub-issues.
- [ ] *Add a checkbox for each sub-issue here.*
### Relevant Deadlines ###
*List relevant project deadlines here or state NONE.*
### Funding Source ###
*Define the source of funding and account keys here or state NONE.*
## Define the Metadata ##
### Assignee ###
- [x] Select **engineer(s)** or **no engineer** required: John HG
- [ ] Select **scientist(s)** or **no scientist** required: unknown
### Labels ###
- [x] Select **component(s)**
- [x] Select **priority**
- [x] Select **requestor(s)**
### Projects and Milestone ###
- [x] Review **projects** and select relevant **Repository** and **Organization** ones or add "alert:NEED PROJECT ASSIGNMENT" label
- [x] Select **milestone** to next major version milestone or "Future Versions"
## Define Related Issue(s) ##
Consider the impact to the other METplus components.
- [ ] [METplus](https://github.com/dtcenter/METplus/issues/new/choose), [MET](https://github.com/dtcenter/MET/issues/new/choose), [METdatadb](https://github.com/dtcenter/METdatadb/issues/new/choose), [METviewer](https://github.com/dtcenter/METviewer/issues/new/choose), [METexpress](https://github.com/dtcenter/METexpress/issues/new/choose), [METcalcpy](https://github.com/dtcenter/METcalcpy/issues/new/choose), [METplotpy](https://github.com/dtcenter/METplotpy/issues/new/choose)
Depending on the changes to the output, may need an issue for METviewer to handle new output. May also need a METplus issue if new configuration file options are added.
## New Feature Checklist ##
See the [METplus Workflow](https://dtcenter.github.io/METplus/Contributors_Guide/github_workflow.html) for details.
- [x] Complete the issue definition above, including the **Time Estimate** and **Funding source**.
- [x] Fork this repository or create a branch of **develop**.
Branch name: `feature_<Issue Number>_<Description>`
- [ ] Complete the development and test your changes.
- [x] Add/update log messages for easier debugging.
- [x] Add/update unit tests.
- [x] Add/update documentation.
- [x] Push local changes to GitHub.
- [x] Submit a pull request to merge into **develop**.
Pull request: `feature <Issue Number> <Description>`
- [x] Define the pull request metadata, as permissions allow.
Select: **Reviewer(s)**, **Project(s)**, **Milestone**, and **Linked issues**
- [x] Iterate until the reviewer(s) accept and merge your changes.
- [x] Delete your fork or branch.
- [x] Close this issue. | 1.0 | Enhance MET to compute the CBS score. - ## Describe the New Feature ##
The AF project needs to generate the CBS score on its GPP verification. This requires adding another method of interpolation (areal). Michelle Harrold has provided some code (from Bob Craig) and helpful references (see attachments).
From Bob:
"All, the attached document describes the CBS verification process , I.7-36 Table F. The verification is done over a 1.5 degree remap of the model using an area averaging technique. The ground truth is the model analysis. I have attached the program we use to average the data. The index based on the CBS score is from UKMO. I attached the program that calculates it along with the configuration files."
I have attached the WMO document with I.7-36 Table F as well as the the areal weighting IDL script (around line 251 is the weighting code) and the CBS score python program. Also, the areal weighting script references a paper, which might have some helpful background:
https://www.wmo.int/pages/prog/www/BAS/documents/AnnexDoc3-3.pdf
The work for this issue may include supporting a new interpolation method, computing the CBS score, and writing its output somewhere. Recommend coordinating with @michelleharrold since she's likely familiar with the details.
### Acceptance Testing ###
*List input data types and sources.*
*Describe tests required for new functionality.*
### Time Estimate ###
*Estimate the amount of work required here.*
*Issues should represent approximately 1 to 3 days of work.*
### Sub-Issues ###
Consider breaking the new feature down into sub-issues.
- [ ] *Add a checkbox for each sub-issue here.*
### Relevant Deadlines ###
*List relevant project deadlines here or state NONE.*
### Funding Source ###
*Define the source of funding and account keys here or state NONE.*
## Define the Metadata ##
### Assignee ###
- [x] Select **engineer(s)** or **no engineer** required: John HG
- [ ] Select **scientist(s)** or **no scientist** required: unknown
### Labels ###
- [x] Select **component(s)**
- [x] Select **priority**
- [x] Select **requestor(s)**
### Projects and Milestone ###
- [x] Review **projects** and select relevant **Repository** and **Organization** ones or add "alert:NEED PROJECT ASSIGNMENT" label
- [x] Select **milestone** to next major version milestone or "Future Versions"
## Define Related Issue(s) ##
Consider the impact to the other METplus components.
- [ ] [METplus](https://github.com/dtcenter/METplus/issues/new/choose), [MET](https://github.com/dtcenter/MET/issues/new/choose), [METdatadb](https://github.com/dtcenter/METdatadb/issues/new/choose), [METviewer](https://github.com/dtcenter/METviewer/issues/new/choose), [METexpress](https://github.com/dtcenter/METexpress/issues/new/choose), [METcalcpy](https://github.com/dtcenter/METcalcpy/issues/new/choose), [METplotpy](https://github.com/dtcenter/METplotpy/issues/new/choose)
Depending on the changes to the output, may need an issue for METviewer to handle new output. May also need a METplus issue if new configuration file options are added.
## New Feature Checklist ##
See the [METplus Workflow](https://dtcenter.github.io/METplus/Contributors_Guide/github_workflow.html) for details.
- [x] Complete the issue definition above, including the **Time Estimate** and **Funding source**.
- [x] Fork this repository or create a branch of **develop**.
Branch name: `feature_<Issue Number>_<Description>`
- [ ] Complete the development and test your changes.
- [x] Add/update log messages for easier debugging.
- [x] Add/update unit tests.
- [x] Add/update documentation.
- [x] Push local changes to GitHub.
- [x] Submit a pull request to merge into **develop**.
Pull request: `feature <Issue Number> <Description>`
- [x] Define the pull request metadata, as permissions allow.
Select: **Reviewer(s)**, **Project(s)**, **Milestone**, and **Linked issues**
- [x] Iterate until the reviewer(s) accept and merge your changes.
- [x] Delete your fork or branch.
- [x] Close this issue. | priority | enhance met to compute the cbs score describe the new feature the af project needs to generate the cbs score on its gpp verification this requires adding another method of interpolation areal michelle harrold has provided some code from bob craig and helpful references see attachments from bob all the attached document describes the cbs verification process i table f the verification is done over a degree remap of the model using an area averaging technique the ground truth is the model analysis i have attached the program we use to average the data the index based on the cbs score is from ukmo i attached the program that calculates it along with the configuration files i have attached the wmo document with i table f as well as the the areal weighting idl script around line is the weighting code and the cbs score python program also the areal weighting script references a paper which might have some helpful background the work for this issue may include supporting a new interpolation method computing the cbs score and writing its output somewhere recommend coordinating with michelleharrold since she s likely familiar with the details acceptance testing list input data types and sources describe tests required for new functionality time estimate estimate the amount of work required here issues should represent approximately to days of work sub issues consider breaking the new feature down into sub issues add a checkbox for each sub issue here relevant deadlines list relevant project deadlines here or state none funding source define the source of funding and account keys here or state none define the metadata assignee select engineer s or no engineer required john hg select scientist s or no scientist required unknown labels select component s select priority select requestor s projects and milestone review projects and select relevant repository and organization ones or add alert need project assignment label select milestone to next major version milestone or future versions define related issue s consider the impact to the other metplus components depending on the changes to the output may need an issue for metviewer to handle new output may also need a metplus issue if new configuration file options are added new feature checklist see the for details complete the issue definition above including the time estimate and funding source fork this repository or create a branch of develop branch name feature complete the development and test your changes add update log messages for easier debugging add update unit tests add update documentation push local changes to github submit a pull request to merge into develop pull request feature define the pull request metadata as permissions allow select reviewer s project s milestone and linked issues iterate until the reviewer s accept and merge your changes delete your fork or branch close this issue | 1 |
215,104 | 7,290,309,613 | IssuesEvent | 2018-02-24 00:54:30 | PikyCZ/NovaMobsX | https://api.github.com/repos/PikyCZ/NovaMobsX | closed | Know Issues | [Priority] High [Status] Work in Progress help wanted | **Autospawn**
- [ ] Fix autospawn
- [x] disable worlds
**Entities**
- [ ] spider attacking
- [x] target option for passive entities | 1.0 | Know Issues - **Autospawn**
- [ ] Fix autospawn
- [x] disable worlds
**Entities**
- [ ] spider attacking
- [x] target option for passive entities | priority | know issues autospawn fix autospawn disable worlds entities spider attacking target option for passive entities | 1 |
248,047 | 18,858,025,709 | IssuesEvent | 2021-11-12 09:18:05 | IshaaanVyas/pe | https://api.github.com/repos/IshaaanVyas/pe | opened | Very complicated class diagram | type.DocumentationBug severity.Medium | 
Could have made it much simpler and easier to understand by removing methods/attributes that were not necessary to the understanding of the class diagram. (Pretty sure all the print methods are not necessary to understand the relationship between the classes).
<!--session: 1636703251302-c5bade30-d168-4126-8d73-77e1ed078f98-->
<!--Version: Web v3.4.1--> | 1.0 | Very complicated class diagram - 
Could have made it much simpler and easier to understand by removing methods/attributes that were not necessary to the understanding of the class diagram. (Pretty sure all the print methods are not necessary to understand the relationship between the classes).
<!--session: 1636703251302-c5bade30-d168-4126-8d73-77e1ed078f98-->
<!--Version: Web v3.4.1--> | non_priority | very complicated class diagram could have made it much simpler and easier to understand by removing methods attributes that were not necessary to the understanding of the class diagram pretty sure all the print methods are not necessary to understand the relationship between the classes | 0 |
391,337 | 11,572,219,084 | IssuesEvent | 2020-02-20 23:24:54 | googleapis/python-monitoring | https://api.github.com/repos/googleapis/python-monitoring | closed | Synthesis failed for python-monitoring | api: monitoring autosynth failure priority: p1 type: bug | Hello! Autosynth couldn't regenerate python-monitoring. :broken_heart:
Here's the output from running `synth.py`:
```
Cloning into 'working_repo'...
Switched to branch 'autosynth'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', 'synth.py', '--']
synthtool > Executing /tmpfs/src/git/autosynth/working_repo/synth.py.
On branch autosynth
nothing to commit, working tree clean
HEAD detached at FETCH_HEAD
nothing to commit, working tree clean
synthtool > Ensuring dependencies.
synthtool > Pulling artman image.
latest: Pulling from googleapis/artman
Digest: sha256:6aec9c34db0e4be221cdaf6faba27bdc07cfea846808b3d3b964dfce3a9a0f9b
Status: Image is up to date for googleapis/artman:latest
synthtool > Cloning googleapis.
synthtool > Running generator for google/monitoring/artman_monitoring.yaml.
synthtool > Generated code into /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3.
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/group_service.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/group_service.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/metric.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/metric.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/alert_service.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/alert_service.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/dropped_labels.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/dropped_labels.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/group.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/group.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/common.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/common.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/notification.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/notification.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/metric_service.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/metric_service.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/service.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/service.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/service_service.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/service_service.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/alert.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/alert.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/uptime_service.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/uptime_service.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/mutation_record.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/mutation_record.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/uptime.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/uptime.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/span_context.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/span_context.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/notification_service.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/notification_service.proto
synthtool > Placed proto files into /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto.
synthtool > Replaced 'def .*\\(([^\\)]+)\n.*metadata=None\\):\n\\s+"""(.*\n)*?\\s+"""\n' in google/cloud/monitoring_v3/gapic/metric_service_client.py.
synthtool > Replaced 'def .*\\(([^\\)]+)\n.*metadata=None\\):\n\\s+"""(.*\n)*?\\s+"""\n' in google/cloud/monitoring_v3/gapic/group_service_client.py.
synthtool > Replaced 'def .*\\(([^\\)]+)\n.*metadata=None\\):\n\\s+"""(.*\n)*?\\s+"""\n' in google/cloud/monitoring_v3/gapic/alert_policy_service_client.py.
synthtool > Replaced 'def .*\\(([^\\)]+)\n.*metadata=None\\):\n\\s+"""(.*\n)*?\\s+"""\n' in google/cloud/monitoring_v3/gapic/service_monitoring_service_client.py.
synthtool > Replaced 'def .*\\(([^\\)]+)\n.*metadata=None\\):\n\\s+"""(.*\n)*?\\s+"""\n' in google/cloud/monitoring_v3/gapic/notification_channel_service_client.py.
synthtool > Replaced 'def .*\\(([^\\)]+)\n.*metadata=None\\):\n\\s+"""(.*\n)*?\\s+"""\n' in google/cloud/monitoring_v3/gapic/uptime_check_service_client.py.
synthtool > Replaced '(^.*$\\n)*' in google/cloud/monitoring_v3/proto/common_pb2.py.
synthtool > No replacements made in google/cloud/monitoring_v3/gapic/alert_policy_service_client.py for pattern then a new `\[CONDITION_ID\]` is created.
, maybe replacement is not longer needed?
synthtool > Replaced ' ::\n\n' in google/cloud/monitoring_v3/gapic/alert_policy_service_client.py.
synthtool > No replacements made in google/cloud/monitoring_v3/proto/metric_service_pb2.py for pattern ^(\s+)have an ``id`` label: :: resource.type =
.*, maybe replacement is not longer needed?
synthtool > Replaced 'from google.cloud.monitoring_v3.gapic import notification_channel_service_client\n' in google/cloud/monitoring_v3/__init__.py.
synthtool > Replaced 'notification_channel_service_client.NotificationChannelServiceClient' in google/cloud/monitoring_v3/__init__.py.
.coveragerc
.flake8
.github/CONTRIBUTING.md
.github/ISSUE_TEMPLATE/bug_report.md
.github/ISSUE_TEMPLATE/feature_request.md
.github/ISSUE_TEMPLATE/support_request.md
.github/PULL_REQUEST_TEMPLATE.md
.github/release-please.yml
.gitignore
.kokoro/build.sh
.kokoro/continuous/common.cfg
.kokoro/continuous/continuous.cfg
.kokoro/docs/common.cfg
.kokoro/docs/docs.cfg
.kokoro/presubmit/common.cfg
.kokoro/presubmit/presubmit.cfg
.kokoro/publish-docs.sh
.kokoro/release.sh
.kokoro/release/common.cfg
.kokoro/release/release.cfg
.kokoro/trampoline.sh
CODE_OF_CONDUCT.md
CONTRIBUTING.rst
LICENSE
MANIFEST.in
docs/_static/custom.css
docs/_templates/layout.html
docs/conf.py.j2
noxfile.py.j2
renovate.json
setup.cfg
Running session blacken
Creating virtual environment (virtualenv) using python3.6 in .nox/blacken
pip install black==19.3b0
Error: pip is not installed into the virtualenv, it is located at /tmpfs/src/git/autosynth/env/bin/pip. Pass external=True into run() to explicitly allow this.
Session blacken failed.
synthtool > Failed executing nox -s blacken:
None
synthtool > Wrote metadata to synth.metadata.
Traceback (most recent call last):
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py", line 102, in <module>
main()
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 764, in __call__
return self.main(*args, **kwargs)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py", line 94, in main
spec.loader.exec_module(synth_module) # type: ignore
File "<frozen importlib._bootstrap_external>", line 678, in exec_module
File "<frozen importlib._bootstrap>", line 205, in _call_with_frames_removed
File "/tmpfs/src/git/autosynth/working_repo/synth.py", line 99, in <module>
s.shell.run(["nox", "-s", "blacken"], hide_output=False)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/shell.py", line 39, in run
raise exc
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/shell.py", line 33, in run
encoding="utf-8",
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 418, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['nox', '-s', 'blacken']' returned non-zero exit status 1.
Synthesis failed
```
Google internal developers can see the full log [here](https://sponge/bc296324-7867-4eae-a113-8090e6bcc834).
| 1.0 | Synthesis failed for python-monitoring - Hello! Autosynth couldn't regenerate python-monitoring. :broken_heart:
Here's the output from running `synth.py`:
```
Cloning into 'working_repo'...
Switched to branch 'autosynth'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', 'synth.py', '--']
synthtool > Executing /tmpfs/src/git/autosynth/working_repo/synth.py.
On branch autosynth
nothing to commit, working tree clean
HEAD detached at FETCH_HEAD
nothing to commit, working tree clean
synthtool > Ensuring dependencies.
synthtool > Pulling artman image.
latest: Pulling from googleapis/artman
Digest: sha256:6aec9c34db0e4be221cdaf6faba27bdc07cfea846808b3d3b964dfce3a9a0f9b
Status: Image is up to date for googleapis/artman:latest
synthtool > Cloning googleapis.
synthtool > Running generator for google/monitoring/artman_monitoring.yaml.
synthtool > Generated code into /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3.
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/group_service.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/group_service.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/metric.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/metric.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/alert_service.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/alert_service.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/dropped_labels.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/dropped_labels.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/group.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/group.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/common.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/common.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/notification.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/notification.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/metric_service.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/metric_service.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/service.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/service.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/service_service.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/service_service.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/alert.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/alert.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/uptime_service.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/uptime_service.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/mutation_record.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/mutation_record.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/uptime.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/uptime.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/span_context.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/span_context.proto
synthtool > Copy: /home/kbuilder/.cache/synthtool/googleapis/google/monitoring/v3/notification_service.proto to /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto/notification_service.proto
synthtool > Placed proto files into /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/python/monitoring-v3/google/cloud/monitoring_v3/proto.
synthtool > Replaced 'def .*\\(([^\\)]+)\n.*metadata=None\\):\n\\s+"""(.*\n)*?\\s+"""\n' in google/cloud/monitoring_v3/gapic/metric_service_client.py.
synthtool > Replaced 'def .*\\(([^\\)]+)\n.*metadata=None\\):\n\\s+"""(.*\n)*?\\s+"""\n' in google/cloud/monitoring_v3/gapic/group_service_client.py.
synthtool > Replaced 'def .*\\(([^\\)]+)\n.*metadata=None\\):\n\\s+"""(.*\n)*?\\s+"""\n' in google/cloud/monitoring_v3/gapic/alert_policy_service_client.py.
synthtool > Replaced 'def .*\\(([^\\)]+)\n.*metadata=None\\):\n\\s+"""(.*\n)*?\\s+"""\n' in google/cloud/monitoring_v3/gapic/service_monitoring_service_client.py.
synthtool > Replaced 'def .*\\(([^\\)]+)\n.*metadata=None\\):\n\\s+"""(.*\n)*?\\s+"""\n' in google/cloud/monitoring_v3/gapic/notification_channel_service_client.py.
synthtool > Replaced 'def .*\\(([^\\)]+)\n.*metadata=None\\):\n\\s+"""(.*\n)*?\\s+"""\n' in google/cloud/monitoring_v3/gapic/uptime_check_service_client.py.
synthtool > Replaced '(^.*$\\n)*' in google/cloud/monitoring_v3/proto/common_pb2.py.
synthtool > No replacements made in google/cloud/monitoring_v3/gapic/alert_policy_service_client.py for pattern then a new `\[CONDITION_ID\]` is created.
, maybe replacement is not longer needed?
synthtool > Replaced ' ::\n\n' in google/cloud/monitoring_v3/gapic/alert_policy_service_client.py.
synthtool > No replacements made in google/cloud/monitoring_v3/proto/metric_service_pb2.py for pattern ^(\s+)have an ``id`` label: :: resource.type =
.*, maybe replacement is not longer needed?
synthtool > Replaced 'from google.cloud.monitoring_v3.gapic import notification_channel_service_client\n' in google/cloud/monitoring_v3/__init__.py.
synthtool > Replaced 'notification_channel_service_client.NotificationChannelServiceClient' in google/cloud/monitoring_v3/__init__.py.
.coveragerc
.flake8
.github/CONTRIBUTING.md
.github/ISSUE_TEMPLATE/bug_report.md
.github/ISSUE_TEMPLATE/feature_request.md
.github/ISSUE_TEMPLATE/support_request.md
.github/PULL_REQUEST_TEMPLATE.md
.github/release-please.yml
.gitignore
.kokoro/build.sh
.kokoro/continuous/common.cfg
.kokoro/continuous/continuous.cfg
.kokoro/docs/common.cfg
.kokoro/docs/docs.cfg
.kokoro/presubmit/common.cfg
.kokoro/presubmit/presubmit.cfg
.kokoro/publish-docs.sh
.kokoro/release.sh
.kokoro/release/common.cfg
.kokoro/release/release.cfg
.kokoro/trampoline.sh
CODE_OF_CONDUCT.md
CONTRIBUTING.rst
LICENSE
MANIFEST.in
docs/_static/custom.css
docs/_templates/layout.html
docs/conf.py.j2
noxfile.py.j2
renovate.json
setup.cfg
Running session blacken
Creating virtual environment (virtualenv) using python3.6 in .nox/blacken
pip install black==19.3b0
Error: pip is not installed into the virtualenv, it is located at /tmpfs/src/git/autosynth/env/bin/pip. Pass external=True into run() to explicitly allow this.
Session blacken failed.
synthtool > Failed executing nox -s blacken:
None
synthtool > Wrote metadata to synth.metadata.
Traceback (most recent call last):
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py", line 102, in <module>
main()
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 764, in __call__
return self.main(*args, **kwargs)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py", line 94, in main
spec.loader.exec_module(synth_module) # type: ignore
File "<frozen importlib._bootstrap_external>", line 678, in exec_module
File "<frozen importlib._bootstrap>", line 205, in _call_with_frames_removed
File "/tmpfs/src/git/autosynth/working_repo/synth.py", line 99, in <module>
s.shell.run(["nox", "-s", "blacken"], hide_output=False)
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/shell.py", line 39, in run
raise exc
File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/shell.py", line 33, in run
encoding="utf-8",
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 418, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['nox', '-s', 'blacken']' returned non-zero exit status 1.
Synthesis failed
```
Google internal developers can see the full log [here](https://sponge/bc296324-7867-4eae-a113-8090e6bcc834).
| priority | synthesis failed for python monitoring hello autosynth couldn t regenerate python monitoring broken heart here s the output from running synth py cloning into working repo switched to branch autosynth running synthtool synthtool executing tmpfs src git autosynth working repo synth py on branch autosynth nothing to commit working tree clean head detached at fetch head nothing to commit working tree clean synthtool ensuring dependencies synthtool pulling artman image latest pulling from googleapis artman digest status image is up to date for googleapis artman latest synthtool cloning googleapis synthtool running generator for google monitoring artman monitoring yaml synthtool generated code into home kbuilder cache synthtool googleapis artman genfiles python monitoring synthtool copy home kbuilder cache synthtool googleapis google monitoring group service proto to home kbuilder cache synthtool googleapis artman genfiles python monitoring google cloud monitoring proto group service proto synthtool copy home kbuilder cache synthtool googleapis google monitoring metric proto to home kbuilder cache synthtool googleapis artman genfiles python monitoring google cloud monitoring proto metric proto synthtool copy home kbuilder cache synthtool googleapis google monitoring alert service proto to home kbuilder cache synthtool googleapis artman genfiles python monitoring google cloud monitoring proto alert service proto synthtool copy home kbuilder cache synthtool googleapis google monitoring dropped labels proto to home kbuilder cache synthtool googleapis artman genfiles python monitoring google cloud monitoring proto dropped labels proto synthtool copy home kbuilder cache synthtool googleapis google monitoring group proto to home kbuilder cache synthtool googleapis artman genfiles python monitoring google cloud monitoring proto group proto synthtool copy home kbuilder cache synthtool googleapis google monitoring common proto to home kbuilder cache synthtool googleapis artman genfiles python monitoring google cloud monitoring proto common proto synthtool copy home kbuilder cache synthtool googleapis google monitoring notification proto to home kbuilder cache synthtool googleapis artman genfiles python monitoring google cloud monitoring proto notification proto synthtool copy home kbuilder cache synthtool googleapis google monitoring metric service proto to home kbuilder cache synthtool googleapis artman genfiles python monitoring google cloud monitoring proto metric service proto synthtool copy home kbuilder cache synthtool googleapis google monitoring service proto to home kbuilder cache synthtool googleapis artman genfiles python monitoring google cloud monitoring proto service proto synthtool copy home kbuilder cache synthtool googleapis google monitoring service service proto to home kbuilder cache synthtool googleapis artman genfiles python monitoring google cloud monitoring proto service service proto synthtool copy home kbuilder cache synthtool googleapis google monitoring alert proto to home kbuilder cache synthtool googleapis artman genfiles python monitoring google cloud monitoring proto alert proto synthtool copy home kbuilder cache synthtool googleapis google monitoring uptime service proto to home kbuilder cache synthtool googleapis artman genfiles python monitoring google cloud monitoring proto uptime service proto synthtool copy home kbuilder cache synthtool googleapis google monitoring mutation record proto to home kbuilder cache synthtool googleapis artman genfiles python monitoring google cloud monitoring proto mutation record proto synthtool copy home kbuilder cache synthtool googleapis google monitoring uptime proto to home kbuilder cache synthtool googleapis artman genfiles python monitoring google cloud monitoring proto uptime proto synthtool copy home kbuilder cache synthtool googleapis google monitoring span context proto to home kbuilder cache synthtool googleapis artman genfiles python monitoring google cloud monitoring proto span context proto synthtool copy home kbuilder cache synthtool googleapis google monitoring notification service proto to home kbuilder cache synthtool googleapis artman genfiles python monitoring google cloud monitoring proto notification service proto synthtool placed proto files into home kbuilder cache synthtool googleapis artman genfiles python monitoring google cloud monitoring proto synthtool replaced def n metadata none n s n s n in google cloud monitoring gapic metric service client py synthtool replaced def n metadata none n s n s n in google cloud monitoring gapic group service client py synthtool replaced def n metadata none n s n s n in google cloud monitoring gapic alert policy service client py synthtool replaced def n metadata none n s n s n in google cloud monitoring gapic service monitoring service client py synthtool replaced def n metadata none n s n s n in google cloud monitoring gapic notification channel service client py synthtool replaced def n metadata none n s n s n in google cloud monitoring gapic uptime check service client py synthtool replaced n in google cloud monitoring proto common py synthtool no replacements made in google cloud monitoring gapic alert policy service client py for pattern then a new is created maybe replacement is not longer needed synthtool replaced n n in google cloud monitoring gapic alert policy service client py synthtool no replacements made in google cloud monitoring proto metric service py for pattern s have an id label resource type maybe replacement is not longer needed synthtool replaced from google cloud monitoring gapic import notification channel service client n in google cloud monitoring init py synthtool replaced notification channel service client notificationchannelserviceclient in google cloud monitoring init py coveragerc github contributing md github issue template bug report md github issue template feature request md github issue template support request md github pull request template md github release please yml gitignore kokoro build sh kokoro continuous common cfg kokoro continuous continuous cfg kokoro docs common cfg kokoro docs docs cfg kokoro presubmit common cfg kokoro presubmit presubmit cfg kokoro publish docs sh kokoro release sh kokoro release common cfg kokoro release release cfg kokoro trampoline sh code of conduct md contributing rst license manifest in docs static custom css docs templates layout html docs conf py noxfile py renovate json setup cfg running session blacken creating virtual environment virtualenv using in nox blacken pip install black error pip is not installed into the virtualenv it is located at tmpfs src git autosynth env bin pip pass external true into run to explicitly allow this session blacken failed synthtool failed executing nox s blacken none synthtool wrote metadata to synth metadata traceback most recent call last file home kbuilder pyenv versions lib runpy py line in run module as main main mod spec file home kbuilder pyenv versions lib runpy py line in run code exec code run globals file tmpfs src git autosynth env lib site packages synthtool main py line in main file tmpfs src git autosynth env lib site packages click core py line in call return self main args kwargs file tmpfs src git autosynth env lib site packages click core py line in main rv self invoke ctx file tmpfs src git autosynth env lib site packages click core py line in invoke return ctx invoke self callback ctx params file tmpfs src git autosynth env lib site packages click core py line in invoke return callback args kwargs file tmpfs src git autosynth env lib site packages synthtool main py line in main spec loader exec module synth module type ignore file line in exec module file line in call with frames removed file tmpfs src git autosynth working repo synth py line in s shell run hide output false file tmpfs src git autosynth env lib site packages synthtool shell py line in run raise exc file tmpfs src git autosynth env lib site packages synthtool shell py line in run encoding utf file home kbuilder pyenv versions lib subprocess py line in run output stdout stderr stderr subprocess calledprocesserror command returned non zero exit status synthesis failed google internal developers can see the full log | 1 |
236,532 | 7,750,081,821 | IssuesEvent | 2018-05-30 13:28:37 | ld4l-labs/vitrolib | https://api.github.com/repos/ld4l-labs/vitrolib | opened | Add accession number to custodial event | ARM custom forms priority: medium | Currently linked only to Item. Complexities in adding to custodial event: select list should display all accession numbers linked to the item and not linked to another custodial event; otherwise create new. For now we are linking the accession number only to the item using bf:identifies. | 1.0 | Add accession number to custodial event - Currently linked only to Item. Complexities in adding to custodial event: select list should display all accession numbers linked to the item and not linked to another custodial event; otherwise create new. For now we are linking the accession number only to the item using bf:identifies. | priority | add accession number to custodial event currently linked only to item complexities in adding to custodial event select list should display all accession numbers linked to the item and not linked to another custodial event otherwise create new for now we are linking the accession number only to the item using bf identifies | 1 |
25,938 | 19,476,131,918 | IssuesEvent | 2021-12-24 12:44:06 | IBM-Cloud/terraform-provider-ibm | https://api.github.com/repos/IBM-Cloud/terraform-provider-ibm | closed | Destroy of ibm_is_instance_group.instance_group fails with provisioning_status must be active to delete instance group | service/VPC Infrastructure | ### Terraform Version
- IBM Cloud Provider version 1.16.1
- Terraform v0.12.29
### Affected Resource(s)
- ibm_is_instance_group.instance_group
### Terraform Configuration Files
See https://github.com/IBM-Cloud/vpc-tutorials/tree/master/vpc-autoscale
### Expected Behavior
Destroy completes succesfully
### Actual Behavior
Destroy fails with
```
Error: Error Deleting the InstanceGroup: Load Balancer r006-c66bd695-f88b-4c7d-a4a5-ed69637d021b provisioning_status must be active to delete instance group
{
"StatusCode": 409,
"Headers": {
...,
"X-Request-Id": [
"9bc944a6-9297-448c-97e1-742c0d1856da"
],
"X-Xss-Protection": [
"1; mode=block"
]
},
"Result": {
"errors": [
{
"code": "conflict_field",
"message": "Load Balancer r006-c66bd695-f88b-4c7d-a4a5-ed69637d021b provisioning_status must be active to delete instance group",
"target": {
"name": "load_balancer",
"type": "load_balancer"
}
}
],
"trace": "9bc944a6-9297-448c-97e1-742c0d1856da"
},
"RawResult": null
}
```
### Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
1. `terraform apply`
1. `terraform destroy`
### Important Factoids
The same template used to work with IBM Cloud Provider version 1.13.1. Maybe the provider code has changed, or the backend API did.
| 1.0 | Destroy of ibm_is_instance_group.instance_group fails with provisioning_status must be active to delete instance group - ### Terraform Version
- IBM Cloud Provider version 1.16.1
- Terraform v0.12.29
### Affected Resource(s)
- ibm_is_instance_group.instance_group
### Terraform Configuration Files
See https://github.com/IBM-Cloud/vpc-tutorials/tree/master/vpc-autoscale
### Expected Behavior
Destroy completes succesfully
### Actual Behavior
Destroy fails with
```
Error: Error Deleting the InstanceGroup: Load Balancer r006-c66bd695-f88b-4c7d-a4a5-ed69637d021b provisioning_status must be active to delete instance group
{
"StatusCode": 409,
"Headers": {
...,
"X-Request-Id": [
"9bc944a6-9297-448c-97e1-742c0d1856da"
],
"X-Xss-Protection": [
"1; mode=block"
]
},
"Result": {
"errors": [
{
"code": "conflict_field",
"message": "Load Balancer r006-c66bd695-f88b-4c7d-a4a5-ed69637d021b provisioning_status must be active to delete instance group",
"target": {
"name": "load_balancer",
"type": "load_balancer"
}
}
],
"trace": "9bc944a6-9297-448c-97e1-742c0d1856da"
},
"RawResult": null
}
```
### Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
1. `terraform apply`
1. `terraform destroy`
### Important Factoids
The same template used to work with IBM Cloud Provider version 1.13.1. Maybe the provider code has changed, or the backend API did.
| non_priority | destroy of ibm is instance group instance group fails with provisioning status must be active to delete instance group terraform version ibm cloud provider version terraform affected resource s ibm is instance group instance group terraform configuration files see expected behavior destroy completes succesfully actual behavior destroy fails with error error deleting the instancegroup load balancer provisioning status must be active to delete instance group statuscode headers x request id x xss protection mode block result errors code conflict field message load balancer provisioning status must be active to delete instance group target name load balancer type load balancer trace rawresult null steps to reproduce please list the steps required to reproduce the issue for example terraform apply terraform destroy important factoids the same template used to work with ibm cloud provider version maybe the provider code has changed or the backend api did | 0 |
53,300 | 13,151,780,904 | IssuesEvent | 2020-08-09 18:31:51 | xamarin/xamarin-android | https://api.github.com/repos/xamarin/xamarin-android | closed | Unable to build Xamarin Android application after upgrading to VS 16.7 Release - getting error CS8370 | Area: App+Library Build | ### Steps to Reproduce
1. Open a project containing some C# 8.0 code & which was compiling fine with 16.6, then build it in "Debug" mode
2. Note that updating the tag langversion to "latest" in .csproj does not solve the issue
### Expected Behavior
Build should complete without errors.
### Actual Behavior
Getting messages CS8370 on C# 8.0 constructs saying that C# language version should be 8.0. Compiler is using C# 7.3.
### Version Information
Microsoft Visual Studio Community 2019
Version 16.7.0
VisualStudio.16.Release/16.7.0+30330.147
Microsoft .NET Framework
Version 4.8.04084
Version installée : Community
ASP.NET and Web Tools 2019 16.7.532.28833
ASP.NET and Web Tools 2019
ASP.NET Core Razor Language Services 16.1.0.2035807+72d099b977d3a85e65fa3b0614ca8cfc803fef02
Provides languages services for ASP.NET Core Razor.
ASP.NET Web Frameworks and Tools 2019 16.7.532.28833
Pour plus d'informations, visitez https://www.asp.net/
Azure Functions and Web Jobs Tools 16.7.532.28833
Azure Functions and Web Jobs Tools
Common Azure Tools 1.10
Fournit des services courants utilisables par Microsoft Azure Mobile Services et Microsoft Azure Tools.
Extensibility Message Bus 1.2.6 (master@34d6af2)
Provides common messaging-based MEF services for loosely coupled Visual Studio extension components communication and integration.
Extension IntelliCode 1.0
Informations détaillées sur l'extension Visual Studio IntelliCode
Extensions des outils de conteneur Visual Studio (préversion) 1.0
Affichez, gérez et diagnostiquez les conteneurs dans Visual Studio.
Gestionnaire de package NuGet 5.7.0
Gestionnaire de package NuGet dans Visual Studio. Pour plus d'informations sur NuGet, visitez https://docs.nuget.org/
Microsoft Azure Tools 2.9
Microsoft Azure Tools pour Microsoft Visual Studio 2019 - v2.9.30701.1
Microsoft Continuous Delivery Tools pour Visual Studio 0.4
Simplification de la configuration des pipelines Azure DevOps à partir de l'IDE Visual Studio.
Microsoft JVM Debugger 1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines
Microsoft MI-Based Debugger 1.0
Provides support for connecting Visual Studio to MI compatible debuggers
Mono Debugging for Visual Studio 16.7.5 (112c7bc)
Support for debugging Mono processes with Visual Studio.
Outils Azure App Service v3.0.0 16.7.532.28833
Outils Azure App Service v3.0.0
Outils C# 3.7.0-6.20375.2+34202cc2f3e869fd70a26d8237f4552cf9e192cf
Composants C# utilisés dans l'IDE. Selon votre type de projet et vos paramètres, une version différente du compilateur peut être utilisée.
Outils TypeScript 16.0.20702.2001
Outils TypeScript pour Microsoft Visual Studio
Outils Visual Basic 3.7.0-6.20375.2+34202cc2f3e869fd70a26d8237f4552cf9e192cf
Composants Visual Basic utilisés dans l'IDE. Selon votre type de projet et vos paramètres, une version différente du compilateur peut être utilisée.
Package hôte de l'adaptateur de débogage de Visual Studio Code 1.0
Couche d'interopérabilité pour l'hébergement d'adaptateurs de débogage Visual Studio Code dans Visual Studio
ProjectServicesPackage Extension 1.0
ProjectServicesPackage Visual Studio Extension Detailed Info
SQL Server Data Tools 16.0.62007.09200
Microsoft SQL Server Data Tools
Visual Studio Tools pour Conteneurs 1.0
Visual Studio Tools pour Conteneurs
Visual Studio Tools pour Docker 1.1
Développez, exécutez et validez vos applications ASP.NET Core dans l'environnement cible. Appuyez sur F5 pour exécuter votre application directement dans un conteneur avec débogage ou sur CTRL+F5 pour modifier et actualiser votre application sans avoir à recréer le conteneur.
Visual Studio Tools pour Kubernetes 1.0
Visual Studio Tools pour Kubernetes
Visual F# Tools 10.10.0.0 pour F# 4.7 16.7.0-beta.20361.3+3ef6f0b514198c0bfa6c2c09fefe41a740b024d5
Microsoft Visual F# Tools 10.10.0.0 pour F# 4.7
VisualStudio.DeviceLog 1.0
Informations sur mon paquet
VisualStudio.Foo 1.0
Information about my package
VisualStudio.Mac 1.0
Mac Extension for Visual Studio
Xamarin 16.7.000.440 (d16-7@358f3c6)
Extension Visual Studio permettant de développer pour Xamarin.iOS et Xamarin.Android.
Xamarin Designer 16.7.0.495 (remotes/origin/d16-7@79c0c522c)
Extension Visual Studio pour activer les outils Xamarin Designer dans Visual Studio.
Xamarin Templates 16.7.85 (1bcbbdf)
Templates for building iOS, Android, and Windows apps with Xamarin and Xamarin.Forms.
Xamarin.Android SDK 11.0.0.3 (d16-7/aca845b)
Xamarin.Android Reference Assemblies and MSBuild support.
Mono: 83105ba
Java.Interop: xamarin/java.interop/d16-7@1f3388a
ProGuard: Guardsquare/proguard/proguard6.2.2@ebe9000
SQLite: xamarin/sqlite/3.32.1@1a3276b
Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-7@017078f
Xamarin.iOS and Xamarin.Mac SDK 13.20.2.2 (817b6f72a)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.
> dotnet --list-sdks
1.1.0-preview1-005077 [C:\Program Files\dotnet\sdk]
2.0.2 [C:\Program Files\dotnet\sdk]
2.1.202 [C:\Program Files\dotnet\sdk]
2.1.504 [C:\Program Files\dotnet\sdk]
2.1.801 [C:\Program Files\dotnet\sdk]
2.2.101 [C:\Program Files\dotnet\sdk]
2.2.207 [C:\Program Files\dotnet\sdk]
3.1.400 [C:\Program Files\dotnet\sdk]
### Log File
Application.cs(424,28,424,31): error CS8370: La fonctionnalité 'assignation de fusion' n'est pas disponible en C# 7.3. Utilisez la version de langage 8.0 ou une version ultérieure.
| 1.0 | Unable to build Xamarin Android application after upgrading to VS 16.7 Release - getting error CS8370 - ### Steps to Reproduce
1. Open a project containing some C# 8.0 code & which was compiling fine with 16.6, then build it in "Debug" mode
2. Note that updating the tag langversion to "latest" in .csproj does not solve the issue
### Expected Behavior
Build should complete without errors.
### Actual Behavior
Getting messages CS8370 on C# 8.0 constructs saying that C# language version should be 8.0. Compiler is using C# 7.3.
### Version Information
Microsoft Visual Studio Community 2019
Version 16.7.0
VisualStudio.16.Release/16.7.0+30330.147
Microsoft .NET Framework
Version 4.8.04084
Version installée : Community
ASP.NET and Web Tools 2019 16.7.532.28833
ASP.NET and Web Tools 2019
ASP.NET Core Razor Language Services 16.1.0.2035807+72d099b977d3a85e65fa3b0614ca8cfc803fef02
Provides languages services for ASP.NET Core Razor.
ASP.NET Web Frameworks and Tools 2019 16.7.532.28833
Pour plus d'informations, visitez https://www.asp.net/
Azure Functions and Web Jobs Tools 16.7.532.28833
Azure Functions and Web Jobs Tools
Common Azure Tools 1.10
Fournit des services courants utilisables par Microsoft Azure Mobile Services et Microsoft Azure Tools.
Extensibility Message Bus 1.2.6 (master@34d6af2)
Provides common messaging-based MEF services for loosely coupled Visual Studio extension components communication and integration.
Extension IntelliCode 1.0
Informations détaillées sur l'extension Visual Studio IntelliCode
Extensions des outils de conteneur Visual Studio (préversion) 1.0
Affichez, gérez et diagnostiquez les conteneurs dans Visual Studio.
Gestionnaire de package NuGet 5.7.0
Gestionnaire de package NuGet dans Visual Studio. Pour plus d'informations sur NuGet, visitez https://docs.nuget.org/
Microsoft Azure Tools 2.9
Microsoft Azure Tools pour Microsoft Visual Studio 2019 - v2.9.30701.1
Microsoft Continuous Delivery Tools pour Visual Studio 0.4
Simplification de la configuration des pipelines Azure DevOps à partir de l'IDE Visual Studio.
Microsoft JVM Debugger 1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines
Microsoft MI-Based Debugger 1.0
Provides support for connecting Visual Studio to MI compatible debuggers
Mono Debugging for Visual Studio 16.7.5 (112c7bc)
Support for debugging Mono processes with Visual Studio.
Outils Azure App Service v3.0.0 16.7.532.28833
Outils Azure App Service v3.0.0
Outils C# 3.7.0-6.20375.2+34202cc2f3e869fd70a26d8237f4552cf9e192cf
Composants C# utilisés dans l'IDE. Selon votre type de projet et vos paramètres, une version différente du compilateur peut être utilisée.
Outils TypeScript 16.0.20702.2001
Outils TypeScript pour Microsoft Visual Studio
Outils Visual Basic 3.7.0-6.20375.2+34202cc2f3e869fd70a26d8237f4552cf9e192cf
Composants Visual Basic utilisés dans l'IDE. Selon votre type de projet et vos paramètres, une version différente du compilateur peut être utilisée.
Package hôte de l'adaptateur de débogage de Visual Studio Code 1.0
Couche d'interopérabilité pour l'hébergement d'adaptateurs de débogage Visual Studio Code dans Visual Studio
ProjectServicesPackage Extension 1.0
ProjectServicesPackage Visual Studio Extension Detailed Info
SQL Server Data Tools 16.0.62007.09200
Microsoft SQL Server Data Tools
Visual Studio Tools pour Conteneurs 1.0
Visual Studio Tools pour Conteneurs
Visual Studio Tools pour Docker 1.1
Développez, exécutez et validez vos applications ASP.NET Core dans l'environnement cible. Appuyez sur F5 pour exécuter votre application directement dans un conteneur avec débogage ou sur CTRL+F5 pour modifier et actualiser votre application sans avoir à recréer le conteneur.
Visual Studio Tools pour Kubernetes 1.0
Visual Studio Tools pour Kubernetes
Visual F# Tools 10.10.0.0 pour F# 4.7 16.7.0-beta.20361.3+3ef6f0b514198c0bfa6c2c09fefe41a740b024d5
Microsoft Visual F# Tools 10.10.0.0 pour F# 4.7
VisualStudio.DeviceLog 1.0
Informations sur mon paquet
VisualStudio.Foo 1.0
Information about my package
VisualStudio.Mac 1.0
Mac Extension for Visual Studio
Xamarin 16.7.000.440 (d16-7@358f3c6)
Extension Visual Studio permettant de développer pour Xamarin.iOS et Xamarin.Android.
Xamarin Designer 16.7.0.495 (remotes/origin/d16-7@79c0c522c)
Extension Visual Studio pour activer les outils Xamarin Designer dans Visual Studio.
Xamarin Templates 16.7.85 (1bcbbdf)
Templates for building iOS, Android, and Windows apps with Xamarin and Xamarin.Forms.
Xamarin.Android SDK 11.0.0.3 (d16-7/aca845b)
Xamarin.Android Reference Assemblies and MSBuild support.
Mono: 83105ba
Java.Interop: xamarin/java.interop/d16-7@1f3388a
ProGuard: Guardsquare/proguard/proguard6.2.2@ebe9000
SQLite: xamarin/sqlite/3.32.1@1a3276b
Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-7@017078f
Xamarin.iOS and Xamarin.Mac SDK 13.20.2.2 (817b6f72a)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.
> dotnet --list-sdks
1.1.0-preview1-005077 [C:\Program Files\dotnet\sdk]
2.0.2 [C:\Program Files\dotnet\sdk]
2.1.202 [C:\Program Files\dotnet\sdk]
2.1.504 [C:\Program Files\dotnet\sdk]
2.1.801 [C:\Program Files\dotnet\sdk]
2.2.101 [C:\Program Files\dotnet\sdk]
2.2.207 [C:\Program Files\dotnet\sdk]
3.1.400 [C:\Program Files\dotnet\sdk]
### Log File
Application.cs(424,28,424,31): error CS8370: La fonctionnalité 'assignation de fusion' n'est pas disponible en C# 7.3. Utilisez la version de langage 8.0 ou une version ultérieure.
| non_priority | unable to build xamarin android application after upgrading to vs release getting error steps to reproduce open a project containing some c code which was compiling fine with then build it in debug mode note that updating the tag langversion to latest in csproj does not solve the issue expected behavior build should complete without errors actual behavior getting messages on c constructs saying that c language version should be compiler is using c version information microsoft visual studio community version visualstudio release microsoft net framework version version installée community asp net and web tools asp net and web tools asp net core razor language services provides languages services for asp net core razor asp net web frameworks and tools pour plus d informations visitez azure functions and web jobs tools azure functions and web jobs tools common azure tools fournit des services courants utilisables par microsoft azure mobile services et microsoft azure tools extensibility message bus master provides common messaging based mef services for loosely coupled visual studio extension components communication and integration extension intellicode informations détaillées sur l extension visual studio intellicode extensions des outils de conteneur visual studio préversion affichez gérez et diagnostiquez les conteneurs dans visual studio gestionnaire de package nuget gestionnaire de package nuget dans visual studio pour plus d informations sur nuget visitez microsoft azure tools microsoft azure tools pour microsoft visual studio microsoft continuous delivery tools pour visual studio simplification de la configuration des pipelines azure devops à partir de l ide visual studio microsoft jvm debugger provides support for connecting the visual studio debugger to jdwp compatible java virtual machines microsoft mi based debugger provides support for connecting visual studio to mi compatible debuggers mono debugging for visual studio support for debugging mono processes with visual studio outils azure app service outils azure app service outils c composants c utilisés dans l ide selon votre type de projet et vos paramètres une version différente du compilateur peut être utilisée outils typescript outils typescript pour microsoft visual studio outils visual basic composants visual basic utilisés dans l ide selon votre type de projet et vos paramètres une version différente du compilateur peut être utilisée package hôte de l adaptateur de débogage de visual studio code couche d interopérabilité pour l hébergement d adaptateurs de débogage visual studio code dans visual studio projectservicespackage extension projectservicespackage visual studio extension detailed info sql server data tools microsoft sql server data tools visual studio tools pour conteneurs visual studio tools pour conteneurs visual studio tools pour docker développez exécutez et validez vos applications asp net core dans l environnement cible appuyez sur pour exécuter votre application directement dans un conteneur avec débogage ou sur ctrl pour modifier et actualiser votre application sans avoir à recréer le conteneur visual studio tools pour kubernetes visual studio tools pour kubernetes visual f tools pour f beta microsoft visual f tools pour f visualstudio devicelog informations sur mon paquet visualstudio foo information about my package visualstudio mac mac extension for visual studio xamarin extension visual studio permettant de développer pour xamarin ios et xamarin android xamarin designer remotes origin extension visual studio pour activer les outils xamarin designer dans visual studio xamarin templates templates for building ios android and windows apps with xamarin and xamarin forms xamarin android sdk xamarin android reference assemblies and msbuild support mono java interop xamarin java interop proguard guardsquare proguard sqlite xamarin sqlite xamarin android tools xamarin xamarin android tools xamarin ios and xamarin mac sdk xamarin ios and xamarin mac reference assemblies and msbuild support dotnet list sdks log file application cs error la fonctionnalité assignation de fusion n est pas disponible en c utilisez la version de langage ou une version ultérieure | 0 |
179,823 | 30,308,713,515 | IssuesEvent | 2023-07-10 11:19:33 | GSA-TTS/FAC | https://api.github.com/repos/GSA-TTS/FAC | closed | Mock up new FAC Resources page | ux/design content | Breakout issue of #377
### Background
We're designing a new FAC Resources page (#458) based on research with auditors and auditees. Once we complete the research and content design work in #458, we can mock up the new FAC Resources page in Figma.
### Tasks
- [x] Mock up new page
- [ ] Peer review
- [ ] Write implementation notes
### Definition of Done
- [ ] Screens in Figma are ready to be handed off to front end
- [x] All text has a contrast ratio of 4.5:1 with the background
- [x] Interaction are documented if they deviate from USWDS components
- [x] The needs of someone navigating the site with the use of a screenreader or keyboard has been considered and documented
- [x] There is an option for multilingual support
- [x] There is supporting documentation for alt text, labels for links (anchor + target), error text in forms, and what assistive technologies should announce (if applicable)
| 1.0 | Mock up new FAC Resources page - Breakout issue of #377
### Background
We're designing a new FAC Resources page (#458) based on research with auditors and auditees. Once we complete the research and content design work in #458, we can mock up the new FAC Resources page in Figma.
### Tasks
- [x] Mock up new page
- [ ] Peer review
- [ ] Write implementation notes
### Definition of Done
- [ ] Screens in Figma are ready to be handed off to front end
- [x] All text has a contrast ratio of 4.5:1 with the background
- [x] Interaction are documented if they deviate from USWDS components
- [x] The needs of someone navigating the site with the use of a screenreader or keyboard has been considered and documented
- [x] There is an option for multilingual support
- [x] There is supporting documentation for alt text, labels for links (anchor + target), error text in forms, and what assistive technologies should announce (if applicable)
| non_priority | mock up new fac resources page breakout issue of background we re designing a new fac resources page based on research with auditors and auditees once we complete the research and content design work in we can mock up the new fac resources page in figma tasks mock up new page peer review write implementation notes definition of done screens in figma are ready to be handed off to front end all text has a contrast ratio of with the background interaction are documented if they deviate from uswds components the needs of someone navigating the site with the use of a screenreader or keyboard has been considered and documented there is an option for multilingual support there is supporting documentation for alt text labels for links anchor target error text in forms and what assistive technologies should announce if applicable | 0 |
13,066 | 5,291,675,441 | IssuesEvent | 2017-02-08 23:12:42 | grpc/grpc | https://api.github.com/repos/grpc/grpc | closed | Python unit.beta._not_found_test.NotFoundTest.test_future_stream_unary_not_found test is flaky | BUILDPONY P1 python | https://grpc-testing.appspot.com/job/gRPC_pull_requests_linux/1799/testReport/junit/(root)/python_linux_opt/py27_test_unit_beta__not_found_test_NotFoundTest/
```
[0mRunning unit.beta._not_found_test.NotFoundTest.test_future_stream_unary_not_found
[91mERROR unit.beta._not_found_test.NotFoundTest.test_future_stream_unary_not_found
[0m2 tests finished:
1 successful
1 unsuccessful
0 skipped
0 expected failures
0 unexpected successes
Interrupted Tests:
[]
Errors/Failures:
[91munit.beta._not_found_test.NotFoundTest.test_future_stream_unary_not_found[0m
[1mtraceback:[0m
Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/case.py", line 329, in run
testMethod()
File "/var/local/git/grpc/src/python/grpcio_tests/tests/unit/beta/_not_found_test.py", line 66, in test_future_stream_unary_not_found
rpc_future.result()
File "/var/local/git/grpc/py27/local/lib/python2.7/site-packages/grpc/beta/_client_adaptations.py", line 111, in result
raise _abortion_error(rpc_error_call)
RemoteError: RemoteError(code=StatusCode.UNKNOWN, details="Exception iterating requests!")
[1mstdout:[0m
[1mstderr:[0m
ERROR:root:Exception iterating requests!
Traceback (most recent call last):
File "/var/local/git/grpc/py27/local/lib/python2.7/site-packages/grpc/_channel.py", line 203, in consume_request_iterator
request = next(request_iterator)
TypeError: list object is not an iterator
Unexpected successes: []
Test failure
```
| 1.0 | Python unit.beta._not_found_test.NotFoundTest.test_future_stream_unary_not_found test is flaky - https://grpc-testing.appspot.com/job/gRPC_pull_requests_linux/1799/testReport/junit/(root)/python_linux_opt/py27_test_unit_beta__not_found_test_NotFoundTest/
```
[0mRunning unit.beta._not_found_test.NotFoundTest.test_future_stream_unary_not_found
[91mERROR unit.beta._not_found_test.NotFoundTest.test_future_stream_unary_not_found
[0m2 tests finished:
1 successful
1 unsuccessful
0 skipped
0 expected failures
0 unexpected successes
Interrupted Tests:
[]
Errors/Failures:
[91munit.beta._not_found_test.NotFoundTest.test_future_stream_unary_not_found[0m
[1mtraceback:[0m
Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/case.py", line 329, in run
testMethod()
File "/var/local/git/grpc/src/python/grpcio_tests/tests/unit/beta/_not_found_test.py", line 66, in test_future_stream_unary_not_found
rpc_future.result()
File "/var/local/git/grpc/py27/local/lib/python2.7/site-packages/grpc/beta/_client_adaptations.py", line 111, in result
raise _abortion_error(rpc_error_call)
RemoteError: RemoteError(code=StatusCode.UNKNOWN, details="Exception iterating requests!")
[1mstdout:[0m
[1mstderr:[0m
ERROR:root:Exception iterating requests!
Traceback (most recent call last):
File "/var/local/git/grpc/py27/local/lib/python2.7/site-packages/grpc/_channel.py", line 203, in consume_request_iterator
request = next(request_iterator)
TypeError: list object is not an iterator
Unexpected successes: []
Test failure
```
| non_priority | python unit beta not found test notfoundtest test future stream unary not found test is flaky unit beta not found test notfoundtest test future stream unary not found unit beta not found test notfoundtest test future stream unary not found tests finished successful unsuccessful skipped expected failures unexpected successes interrupted tests errors failures beta not found test notfoundtest test future stream unary not found traceback most recent call last file usr lib unittest case py line in run testmethod file var local git grpc src python grpcio tests tests unit beta not found test py line in test future stream unary not found rpc future result file var local git grpc local lib site packages grpc beta client adaptations py line in result raise abortion error rpc error call remoteerror remoteerror code statuscode unknown details exception iterating requests error root exception iterating requests traceback most recent call last file var local git grpc local lib site packages grpc channel py line in consume request iterator request next request iterator typeerror list object is not an iterator unexpected successes test failure | 0 |
195,415 | 14,728,707,621 | IssuesEvent | 2021-01-06 10:19:42 | WoWManiaUK/Redemption | https://api.github.com/repos/WoWManiaUK/Redemption | closed | [Raid] Eredar Twins intro voicelines | Fixed on PTR - Tester Confirmed Priority - Low | **Links:** https://wowwiki.fandom.com/wiki/Eredar_Twins#:~:text=The%20Eredar%20Twins%2C%20Lady%20Sacrolash,of%20Rohendor%2C%20the%20Second%20Gate.
**What is Happening:** Lady Sarcolash and Grand Warlock Alythess currently play their intro dialogue exchange as soon as the first player enters the Sunwell Plateau instance. At this point, the bosses are way far from the players, and definitely out of sight, and them talking is quite strange and out of place.
**What Should happen:** Their intro dialogue should probably play as soon as the first player enters their room. (Change trigger)
| 1.0 | [Raid] Eredar Twins intro voicelines - **Links:** https://wowwiki.fandom.com/wiki/Eredar_Twins#:~:text=The%20Eredar%20Twins%2C%20Lady%20Sacrolash,of%20Rohendor%2C%20the%20Second%20Gate.
**What is Happening:** Lady Sarcolash and Grand Warlock Alythess currently play their intro dialogue exchange as soon as the first player enters the Sunwell Plateau instance. At this point, the bosses are way far from the players, and definitely out of sight, and them talking is quite strange and out of place.
**What Should happen:** Their intro dialogue should probably play as soon as the first player enters their room. (Change trigger)
| non_priority | eredar twins intro voicelines links what is happening lady sarcolash and grand warlock alythess currently play their intro dialogue exchange as soon as the first player enters the sunwell plateau instance at this point the bosses are way far from the players and definitely out of sight and them talking is quite strange and out of place what should happen their intro dialogue should probably play as soon as the first player enters their room change trigger | 0 |
25,587 | 4,414,499,103 | IssuesEvent | 2016-08-13 13:31:33 | ironjan/klausurtool-ror | https://api.github.com/repos/ironjan/klausurtool-ror | closed | Sorted TOC | defect | ## How does this problem happen?
1. First I go to http://ausleihe.fachschafts.website/internal/admin/old_folders/175/toc
## What does happen?
TOC is unsorted.
## What do you expect to happen instead?
TOC should be sorted. | 1.0 | Sorted TOC - ## How does this problem happen?
1. First I go to http://ausleihe.fachschafts.website/internal/admin/old_folders/175/toc
## What does happen?
TOC is unsorted.
## What do you expect to happen instead?
TOC should be sorted. | non_priority | sorted toc how does this problem happen first i go to what does happen toc is unsorted what do you expect to happen instead toc should be sorted | 0 |
94,539 | 3,928,105,214 | IssuesEvent | 2016-04-24 01:21:42 | Baystation12/Baystation12 | https://api.github.com/repos/Baystation12/Baystation12 | closed | Ghosts can attach and detach IV drips | feature oversight priority: trivial | [Spooky ghost] attaches the IV drip to [Non-spooky human].
Very spooky! But probably not something they should be able to do. | 1.0 | Ghosts can attach and detach IV drips - [Spooky ghost] attaches the IV drip to [Non-spooky human].
Very spooky! But probably not something they should be able to do. | priority | ghosts can attach and detach iv drips attaches the iv drip to very spooky but probably not something they should be able to do | 1 |
255,915 | 8,126,577,039 | IssuesEvent | 2018-08-17 03:07:41 | aowen87/BAR | https://api.github.com/repos/aowen87/BAR | closed | ITAPS shared libraries not included when doing a make package. | Bug Likelihood: 3 - Occasional Priority: Normal Severity: 2 - Minor Irritation | make package doesn't package up the ITAPS shared libraries, so when VisIt is run there are error message at startup about missing shared libraries and of course the ITAPS plugins won't work. This can be fixed by either installing only static libraries or fixing the make package script so that it packages up the shared libraries. I guess either way works. It seems like doing the static libraries would be easier. I ran into this problem both on yana and hoth and I moved the shared libriares into a directory named shared and the problem went away.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 390
Status: Resolved
Project: VisIt
Tracker: Bug
Priority: Normal
Subject: ITAPS shared libraries not included when doing a make package.
Assigned to: Mark Miller
Category:
Target version: 2.1.1
Author: Eric Brugger
Start: 09/14/2010
Due date:
% Done: 0
Estimated time:
Created: 09/14/2010 05:28 pm
Updated: 10/26/2010 07:19 pm
Likelihood: 3 - Occasional
Severity: 2 - Minor Irritation
Found in version: trunk
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
make package doesn't package up the ITAPS shared libraries, so when VisIt is run there are error message at startup about missing shared libraries and of course the ITAPS plugins won't work. This can be fixed by either installing only static libraries or fixing the make package script so that it packages up the shared libraries. I guess either way works. It seems like doing the static libraries would be easier. I ran into this problem both on yana and hoth and I moved the shared libriares into a directory named shared and the problem went away.
Comments:
Ensure build_visit removes any .sos for ITAPS installs.Ensure any existing ITAPS installations have .sos removed.The above 2 actions will ensure ITAPS plugins get statically linked to their respective libs and will then 'ride along for free' when those plugins are packaged in an installation.
I installed some new ITAPS libs on July 27th. But, when I did, I left the .so's there as well and this caused problems. It turns out build_visit does indeed remove the .so's after installing ITAPS libs. So, I think this is now resolved.
| 1.0 | ITAPS shared libraries not included when doing a make package. - make package doesn't package up the ITAPS shared libraries, so when VisIt is run there are error message at startup about missing shared libraries and of course the ITAPS plugins won't work. This can be fixed by either installing only static libraries or fixing the make package script so that it packages up the shared libraries. I guess either way works. It seems like doing the static libraries would be easier. I ran into this problem both on yana and hoth and I moved the shared libriares into a directory named shared and the problem went away.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 390
Status: Resolved
Project: VisIt
Tracker: Bug
Priority: Normal
Subject: ITAPS shared libraries not included when doing a make package.
Assigned to: Mark Miller
Category:
Target version: 2.1.1
Author: Eric Brugger
Start: 09/14/2010
Due date:
% Done: 0
Estimated time:
Created: 09/14/2010 05:28 pm
Updated: 10/26/2010 07:19 pm
Likelihood: 3 - Occasional
Severity: 2 - Minor Irritation
Found in version: trunk
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
make package doesn't package up the ITAPS shared libraries, so when VisIt is run there are error message at startup about missing shared libraries and of course the ITAPS plugins won't work. This can be fixed by either installing only static libraries or fixing the make package script so that it packages up the shared libraries. I guess either way works. It seems like doing the static libraries would be easier. I ran into this problem both on yana and hoth and I moved the shared libriares into a directory named shared and the problem went away.
Comments:
Ensure build_visit removes any .sos for ITAPS installs.Ensure any existing ITAPS installations have .sos removed.The above 2 actions will ensure ITAPS plugins get statically linked to their respective libs and will then 'ride along for free' when those plugins are packaged in an installation.
I installed some new ITAPS libs on July 27th. But, when I did, I left the .so's there as well and this caused problems. It turns out build_visit does indeed remove the .so's after installing ITAPS libs. So, I think this is now resolved.
| priority | itaps shared libraries not included when doing a make package make package doesn t package up the itaps shared libraries so when visit is run there are error message at startup about missing shared libraries and of course the itaps plugins won t work this can be fixed by either installing only static libraries or fixing the make package script so that it packages up the shared libraries i guess either way works it seems like doing the static libraries would be easier i ran into this problem both on yana and hoth and i moved the shared libriares into a directory named shared and the problem went away redmine migration this ticket was migrated from redmine as such not all information was able to be captured in the transition below is a complete record of the original redmine ticket ticket number status resolved project visit tracker bug priority normal subject itaps shared libraries not included when doing a make package assigned to mark miller category target version author eric brugger start due date done estimated time created pm updated pm likelihood occasional severity minor irritation found in version trunk impact expected use os all support group any description make package doesn t package up the itaps shared libraries so when visit is run there are error message at startup about missing shared libraries and of course the itaps plugins won t work this can be fixed by either installing only static libraries or fixing the make package script so that it packages up the shared libraries i guess either way works it seems like doing the static libraries would be easier i ran into this problem both on yana and hoth and i moved the shared libriares into a directory named shared and the problem went away comments ensure build visit removes any sos for itaps installs ensure any existing itaps installations have sos removed the above actions will ensure itaps plugins get statically linked to their respective libs and will then ride along for free when those plugins are packaged in an installation i installed some new itaps libs on july but when i did i left the so s there as well and this caused problems it turns out build visit does indeed remove the so s after installing itaps libs so i think this is now resolved | 1 |
561,480 | 16,617,888,173 | IssuesEvent | 2021-06-02 19:16:56 | department-of-veterans-affairs/caseflow | https://api.github.com/repos/department-of-veterans-affairs/caseflow | closed | [Dogfooding Bug] Offset is displayed instead of Timezone for some cases | Priority: Low Product: caseflow-hearings Stakeholder: BVA Team: Tango 💃 Type: Bug | ## Description
An offset is displayed instead of a timezone for some timezones (e.g. "Vladivostok", which shows "+10").
## Acceptance criteria
- [ ] Ensure something friendlier than the timezone offset displays
## Background/context/resources
## Technical notes
Possibly because there is no timezone abbreviation associated with "Vladivostok"; this is an issue in both the front end (moment.js) and back end (Rails timezones). | 1.0 | [Dogfooding Bug] Offset is displayed instead of Timezone for some cases - ## Description
An offset is displayed instead of a timezone for some timezones (e.g. "Vladivostok", which shows "+10").
## Acceptance criteria
- [ ] Ensure something friendlier than the timezone offset displays
## Background/context/resources
## Technical notes
Possibly because there is no timezone abbreviation associated with "Vladivostok"; this is an issue in both the front end (moment.js) and back end (Rails timezones). | priority | offset is displayed instead of timezone for some cases description an offset is displayed instead of a timezone for some timezones e g vladivostok which shows acceptance criteria ensure something friendlier than the timezone offset displays background context resources technical notes possibly because there is no timezone abbreviation associated with vladivostok this is an issue in both the front end moment js and back end rails timezones | 1 |
499,578 | 14,450,616,608 | IssuesEvent | 2020-12-08 09:50:05 | StrangeLoopGames/EcoIssues | https://api.github.com/repos/StrangeLoopGames/EcoIssues | closed | Contract Nested Clause "Any" only checks first clause | Category: Gameplay Priority: Medium Status: Fixed | 
In the contract only the first entry is counted for the Nested Clause "Any". For example, I gave 20 corn but in the chat it was reported that 20 fiddleheads are missing. When I want to sign the contract as done he tells me that everything is still missing.
If I hand in the 20 fiddleheads I can close the contract without everything else.
[Player-prev.log](https://github.com/StrangeLoopGames/EcoIssues/files/5214744/Player-prev.log)
| 1.0 | Contract Nested Clause "Any" only checks first clause - 
In the contract only the first entry is counted for the Nested Clause "Any". For example, I gave 20 corn but in the chat it was reported that 20 fiddleheads are missing. When I want to sign the contract as done he tells me that everything is still missing.
If I hand in the 20 fiddleheads I can close the contract without everything else.
[Player-prev.log](https://github.com/StrangeLoopGames/EcoIssues/files/5214744/Player-prev.log)
| priority | contract nested clause any only checks first clause in the contract only the first entry is counted for the nested clause any for example i gave corn but in the chat it was reported that fiddleheads are missing when i want to sign the contract as done he tells me that everything is still missing if i hand in the fiddleheads i can close the contract without everything else | 1 |
259,207 | 19,590,650,744 | IssuesEvent | 2022-01-05 12:35:19 | brumik/react-json-chart-builder | https://api.github.com/repos/brumik/react-json-chart-builder | closed | Demo app improvements | documentation | - [x] Use react router for different chart types, so you can send link to an exact chart.
- [x] Make the link menu better, probably horizontal instead of vertical so it can grow better.
- [ ] Add a few more examples.
- [ ] Describe the examples so the user can decide which example is probably the closes to the feature they want.
- [ ] The description could be on an index page in "tiles" or just a list of charts. | 1.0 | Demo app improvements - - [x] Use react router for different chart types, so you can send link to an exact chart.
- [x] Make the link menu better, probably horizontal instead of vertical so it can grow better.
- [ ] Add a few more examples.
- [ ] Describe the examples so the user can decide which example is probably the closes to the feature they want.
- [ ] The description could be on an index page in "tiles" or just a list of charts. | non_priority | demo app improvements use react router for different chart types so you can send link to an exact chart make the link menu better probably horizontal instead of vertical so it can grow better add a few more examples describe the examples so the user can decide which example is probably the closes to the feature they want the description could be on an index page in tiles or just a list of charts | 0 |
568,119 | 16,959,804,363 | IssuesEvent | 2021-06-29 00:59:29 | TerriaJS/de-australia-map | https://api.github.com/repos/TerriaJS/de-australia-map | closed | DE Australia - option for DEA team to update catalogue & test data services | high priority | DEA Team:
- we do need somewhere to test our web services and catalog
- now with the v8 release we don't really have a convenient/persistent spot
- until earlier this week, we updated the terria cube catalog with the services/features we want to test to share with stakeholders
Some options:
1) update terriacube to v8 and keep that as DEA testing site (public)
2) give access to dev/test DE AU to DEA team (not public) | 1.0 | DE Australia - option for DEA team to update catalogue & test data services - DEA Team:
- we do need somewhere to test our web services and catalog
- now with the v8 release we don't really have a convenient/persistent spot
- until earlier this week, we updated the terria cube catalog with the services/features we want to test to share with stakeholders
Some options:
1) update terriacube to v8 and keep that as DEA testing site (public)
2) give access to dev/test DE AU to DEA team (not public) | priority | de australia option for dea team to update catalogue test data services dea team we do need somewhere to test our web services and catalog now with the release we don t really have a convenient persistent spot until earlier this week we updated the terria cube catalog with the services features we want to test to share with stakeholders some options update terriacube to and keep that as dea testing site public give access to dev test de au to dea team not public | 1 |
461,183 | 13,224,780,467 | IssuesEvent | 2020-08-17 19:50:03 | google/ground-platform | https://api.github.com/repos/google/ground-platform | closed | [Add/edit observation] Set audit info (creation/edit user and timestamp) on save | priority: p2 type: feature request web | @gyarill fyi, adding here for future work. | 1.0 | [Add/edit observation] Set audit info (creation/edit user and timestamp) on save - @gyarill fyi, adding here for future work. | priority | set audit info creation edit user and timestamp on save gyarill fyi adding here for future work | 1 |
372,099 | 11,009,170,163 | IssuesEvent | 2019-12-04 12:04:39 | StrangeLoopGames/EcoIssues | https://api.github.com/repos/StrangeLoopGames/EcoIssues | closed | Audio errors spam console on various tool use | Fixed Medium Priority | When trying to use various tools on the environment:
Can not play a disabled audio source
UnityEngine.AudioSource:Play()
PlayRandomAudioClip:OnEnable() (at Assets/PlayRandomAudioClip.cs:34)
UnityEngine.Object:Instantiate(GameObject, Vector3, Quaternion)
CharacterAudioController:Update() (at Assets/CharacterController/CharacterAudioController.cs:31) | 1.0 | Audio errors spam console on various tool use - When trying to use various tools on the environment:
Can not play a disabled audio source
UnityEngine.AudioSource:Play()
PlayRandomAudioClip:OnEnable() (at Assets/PlayRandomAudioClip.cs:34)
UnityEngine.Object:Instantiate(GameObject, Vector3, Quaternion)
CharacterAudioController:Update() (at Assets/CharacterController/CharacterAudioController.cs:31) | priority | audio errors spam console on various tool use when trying to use various tools on the environment can not play a disabled audio source unityengine audiosource play playrandomaudioclip onenable at assets playrandomaudioclip cs unityengine object instantiate gameobject quaternion characteraudiocontroller update at assets charactercontroller characteraudiocontroller cs | 1 |
66,936 | 8,058,895,097 | IssuesEvent | 2018-08-02 20:01:52 | apache/incubator-openwhisk-website | https://api.github.com/repos/apache/incubator-openwhisk-website | opened | Create README Templates for Deployment methods | design priority: low | We would like to link every deployment README to openwhisk website documentation page. And to provide a uniform experience throughout all deployment methods, create a common template so that every deployment repos can change its README.md based on that template.
| 1.0 | Create README Templates for Deployment methods - We would like to link every deployment README to openwhisk website documentation page. And to provide a uniform experience throughout all deployment methods, create a common template so that every deployment repos can change its README.md based on that template.
| non_priority | create readme templates for deployment methods we would like to link every deployment readme to openwhisk website documentation page and to provide a uniform experience throughout all deployment methods create a common template so that every deployment repos can change its readme md based on that template | 0 |
44,325 | 11,427,307,501 | IssuesEvent | 2020-02-04 00:21:35 | lyft/envoy-mobile | https://api.github.com/repos/lyft/envoy-mobile | closed | build: publish envoy artifact | build community no stalebot | During master CI we should publish a compiled library for envoy that people can use to avoid compiling on their own. | 1.0 | build: publish envoy artifact - During master CI we should publish a compiled library for envoy that people can use to avoid compiling on their own. | non_priority | build publish envoy artifact during master ci we should publish a compiled library for envoy that people can use to avoid compiling on their own | 0 |
436,875 | 30,573,162,425 | IssuesEvent | 2023-07-21 01:21:27 | SSWConsulting/SSW.Website | https://api.github.com/repos/SSWConsulting/SSW.Website | closed | 📄Docs - Wiki Page for Components | Type: Documentation | At the moment, when you press the "embed" button on Tina, it won't give you a preview or description of what each component is. It would be good if there was a piece of documentation describing some/all of the components available to users.
**Figure: The "Embed" button in the Tina rich text edtior**
```[tasklist]
### Tasks
- [x] Write a wiki page listing components that can be used in the Tina rich text editor
```
| 1.0 | 📄Docs - Wiki Page for Components - At the moment, when you press the "embed" button on Tina, it won't give you a preview or description of what each component is. It would be good if there was a piece of documentation describing some/all of the components available to users.
**Figure: The "Embed" button in the Tina rich text edtior**
```[tasklist]
### Tasks
- [x] Write a wiki page listing components that can be used in the Tina rich text editor
```
| non_priority | 📄docs wiki page for components at the moment when you press the embed button on tina it won t give you a preview or description of what each component is it would be good if there was a piece of documentation describing some all of the components available to users figure the embed button in the tina rich text edtior tasks write a wiki page listing components that can be used in the tina rich text editor | 0 |
216,016 | 7,300,036,894 | IssuesEvent | 2018-02-26 22:08:16 | peaceiris/we-are-smarter-than-me | https://api.github.com/repos/peaceiris/we-are-smarter-than-me | opened | Post: Affiliate | Priority: High Status: Pending Target: Post Type: Addition | # Affiliate
## Task
- bitFlyer
- bitbank
- Softbank Air
- App
- クレジットカード
- デビットカード
- Taiwan JTB
- ポータブルスキャナー AOLECA
- 吉野の鶏めし
## References
| 1.0 | Post: Affiliate - # Affiliate
## Task
- bitFlyer
- bitbank
- Softbank Air
- App
- クレジットカード
- デビットカード
- Taiwan JTB
- ポータブルスキャナー AOLECA
- 吉野の鶏めし
## References
| priority | post affiliate affiliate task bitflyer bitbank softbank air app クレジットカード デビットカード taiwan jtb ポータブルスキャナー aoleca 吉野の鶏めし references | 1 |
82,039 | 15,838,629,851 | IssuesEvent | 2021-04-06 22:54:03 | flutter/flutter | https://api.github.com/repos/flutter/flutter | closed | "pod install" is running on every iOS build with plugins, even if nothing changed | passed first triage t: xcode tool | ```
$ cd dev/integration_tests/flutter_gallery
$ flutter build ios
...
Running pod install... 1,605ms
```
Run the same command again, and it will run `pod install` again even though it doesn't need to. This adds an extra 1.6 seconds to every build. | 1.0 | "pod install" is running on every iOS build with plugins, even if nothing changed - ```
$ cd dev/integration_tests/flutter_gallery
$ flutter build ios
...
Running pod install... 1,605ms
```
Run the same command again, and it will run `pod install` again even though it doesn't need to. This adds an extra 1.6 seconds to every build. | non_priority | pod install is running on every ios build with plugins even if nothing changed cd dev integration tests flutter gallery flutter build ios running pod install run the same command again and it will run pod install again even though it doesn t need to this adds an extra seconds to every build | 0 |
134,350 | 18,457,954,240 | IssuesEvent | 2021-10-15 19:15:07 | bgoonz/bass-station | https://api.github.com/repos/bgoonz/bass-station | opened | CVE-2021-33502 (High) detected in normalize-url-1.9.1.tgz, normalize-url-3.3.0.tgz | security vulnerability | ## CVE-2021-33502 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>normalize-url-1.9.1.tgz</b>, <b>normalize-url-3.3.0.tgz</b></p></summary>
<p>
<details><summary><b>normalize-url-1.9.1.tgz</b></p></summary>
<p>Normalize a URL</p>
<p>Library home page: <a href="https://registry.npmjs.org/normalize-url/-/normalize-url-1.9.1.tgz">https://registry.npmjs.org/normalize-url/-/normalize-url-1.9.1.tgz</a></p>
<p>Path to dependency file: bass-station/package.json</p>
<p>Path to vulnerable library: bass-station/node_modules/normalize-url/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-4.0.3.tgz (Root Library)
- mini-css-extract-plugin-0.11.3.tgz
- :x: **normalize-url-1.9.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>normalize-url-3.3.0.tgz</b></p></summary>
<p>Normalize a URL</p>
<p>Library home page: <a href="https://registry.npmjs.org/normalize-url/-/normalize-url-3.3.0.tgz">https://registry.npmjs.org/normalize-url/-/normalize-url-3.3.0.tgz</a></p>
<p>Path to dependency file: bass-station/package.json</p>
<p>Path to vulnerable library: bass-station/node_modules/postcss-normalize-url/node_modules/normalize-url/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-4.0.3.tgz (Root Library)
- optimize-css-assets-webpack-plugin-5.0.4.tgz
- cssnano-4.1.11.tgz
- cssnano-preset-default-4.0.8.tgz
- postcss-normalize-url-4.0.1.tgz
- :x: **normalize-url-3.3.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/bgoonz/bass-station/commit/09780fa1a8249ca85be224bc1399bc232d23b2e2">09780fa1a8249ca85be224bc1399bc232d23b2e2</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.
<p>Publish Date: 2021-05-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33502>CVE-2021-33502</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502</a></p>
<p>Release Date: 2021-05-24</p>
<p>Fix Resolution: normalize-url - 4.5.1, 5.3.1, 6.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-33502 (High) detected in normalize-url-1.9.1.tgz, normalize-url-3.3.0.tgz - ## CVE-2021-33502 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>normalize-url-1.9.1.tgz</b>, <b>normalize-url-3.3.0.tgz</b></p></summary>
<p>
<details><summary><b>normalize-url-1.9.1.tgz</b></p></summary>
<p>Normalize a URL</p>
<p>Library home page: <a href="https://registry.npmjs.org/normalize-url/-/normalize-url-1.9.1.tgz">https://registry.npmjs.org/normalize-url/-/normalize-url-1.9.1.tgz</a></p>
<p>Path to dependency file: bass-station/package.json</p>
<p>Path to vulnerable library: bass-station/node_modules/normalize-url/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-4.0.3.tgz (Root Library)
- mini-css-extract-plugin-0.11.3.tgz
- :x: **normalize-url-1.9.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>normalize-url-3.3.0.tgz</b></p></summary>
<p>Normalize a URL</p>
<p>Library home page: <a href="https://registry.npmjs.org/normalize-url/-/normalize-url-3.3.0.tgz">https://registry.npmjs.org/normalize-url/-/normalize-url-3.3.0.tgz</a></p>
<p>Path to dependency file: bass-station/package.json</p>
<p>Path to vulnerable library: bass-station/node_modules/postcss-normalize-url/node_modules/normalize-url/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-4.0.3.tgz (Root Library)
- optimize-css-assets-webpack-plugin-5.0.4.tgz
- cssnano-4.1.11.tgz
- cssnano-preset-default-4.0.8.tgz
- postcss-normalize-url-4.0.1.tgz
- :x: **normalize-url-3.3.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/bgoonz/bass-station/commit/09780fa1a8249ca85be224bc1399bc232d23b2e2">09780fa1a8249ca85be224bc1399bc232d23b2e2</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.
<p>Publish Date: 2021-05-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33502>CVE-2021-33502</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502</a></p>
<p>Release Date: 2021-05-24</p>
<p>Fix Resolution: normalize-url - 4.5.1, 5.3.1, 6.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in normalize url tgz normalize url tgz cve high severity vulnerability vulnerable libraries normalize url tgz normalize url tgz normalize url tgz normalize a url library home page a href path to dependency file bass station package json path to vulnerable library bass station node modules normalize url package json dependency hierarchy react scripts tgz root library mini css extract plugin tgz x normalize url tgz vulnerable library normalize url tgz normalize a url library home page a href path to dependency file bass station package json path to vulnerable library bass station node modules postcss normalize url node modules normalize url package json dependency hierarchy react scripts tgz root library optimize css assets webpack plugin tgz cssnano tgz cssnano preset default tgz postcss normalize url tgz x normalize url tgz vulnerable library found in head commit a href found in base branch master vulnerability details the normalize url package before x before and x before for node js has a redos regular expression denial of service issue because it has exponential performance for data urls publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution normalize url step up your open source security game with whitesource | 0 |
359,275 | 10,667,517,954 | IssuesEvent | 2019-10-19 13:04:16 | eJourn-al/eJournal | https://api.github.com/repos/eJourn-al/eJournal | closed | LTI course not ready screen | Priority: High Status: In Progress Type: Enhancement Workload: Medium | **Describe the solution you'd like**
- A dedicated screen to this scenario, explaining the situation in a lighthearted way.
- Notification with sufficient context so the eJournal team can take action as well.
- Notification to the staff member if known (preferably in a non spammy fashion).
**User story**
As a student start LTI launch without the corresponding course having been set up on eJournal by the teacher yet. Currently, a 404 with a hint in subtext is displayed, I want to be reassured I did nothing wrong. Tell me to contact my teacher to get things in order. | 1.0 | LTI course not ready screen - **Describe the solution you'd like**
- A dedicated screen to this scenario, explaining the situation in a lighthearted way.
- Notification with sufficient context so the eJournal team can take action as well.
- Notification to the staff member if known (preferably in a non spammy fashion).
**User story**
As a student start LTI launch without the corresponding course having been set up on eJournal by the teacher yet. Currently, a 404 with a hint in subtext is displayed, I want to be reassured I did nothing wrong. Tell me to contact my teacher to get things in order. | priority | lti course not ready screen describe the solution you d like a dedicated screen to this scenario explaining the situation in a lighthearted way notification with sufficient context so the ejournal team can take action as well notification to the staff member if known preferably in a non spammy fashion user story as a student start lti launch without the corresponding course having been set up on ejournal by the teacher yet currently a with a hint in subtext is displayed i want to be reassured i did nothing wrong tell me to contact my teacher to get things in order | 1 |
794,246 | 28,027,616,134 | IssuesEvent | 2023-03-28 10:10:09 | ipfs-force-community/venus-cluster | https://api.github.com/repos/ipfs-force-community/venus-cluster | closed | [venus-sector-manager] 手动发送recover消息 | enhancement good first issue priority:mid C-cli v0.6 | ### 模块 / Components
- [x] venus-sector-manager
- [ ] venus-worker
- [ ] 工具链 / toolchains
- [ ] 文档 / docs
### 描述 / Description
是否可以考虑增加，允许用户手动发送recover请求，不用等到下一个windowPost，的相关功能？
关联：
- [ ] https://github.com/filecoin-project/lotus/pull/9144 | 1.0 | [venus-sector-manager] 手动发送recover消息 - ### 模块 / Components
- [x] venus-sector-manager
- [ ] venus-worker
- [ ] 工具链 / toolchains
- [ ] 文档 / docs
### 描述 / Description
是否可以考虑增加，允许用户手动发送recover请求，不用等到下一个windowPost，的相关功能？
关联：
- [ ] https://github.com/filecoin-project/lotus/pull/9144 | priority | 手动发送recover消息 模块 components venus sector manager venus worker 工具链 toolchains 文档 docs 描述 description 是否可以考虑增加，允许用户手动发送recover请求，不用等到下一个windowpost，的相关功能？ 关联： | 1 |
246,403 | 20,862,779,275 | IssuesEvent | 2022-03-22 01:45:56 | khalidsaadat/soen341 | https://api.github.com/repos/khalidsaadat/soen341 | closed | [TESTING] Create working CI for the project | Testing | **Acceptance Test**
1. Build has to be detected by Github actions
2. For our project, empty tests are available through Github actions | 1.0 | [TESTING] Create working CI for the project - **Acceptance Test**
1. Build has to be detected by Github actions
2. For our project, empty tests are available through Github actions | non_priority | create working ci for the project acceptance test build has to be detected by github actions for our project empty tests are available through github actions | 0 |
64,038 | 26,591,988,442 | IssuesEvent | 2023-01-23 09:28:08 | gradido/gradido | https://api.github.com/repos/gradido/gradido | closed | 🐛 [Bug] [Design] Fix Mobile Design | bug service: wallet frontend | <!-- You can find the latest issue templates here https://github.com/ulfgebhardt/issue-templates -->
## 🐛 Bugreport
<!-- Describe your issue in detail. Include screenshots if needed. Give us as much information as possible. Use a clear and concise description of what the bug is.-->
### Mobile
- [x] Startseite zu großer Abstand zwischen box & Konto infos
- [x] Startseite button zweizeilig
- [x] Kein Avatar im Menü
- [x] Beim senden sind die Radioboxen nicht gleichgroß
- [x] GDD&GDT Avatare oval
- [x] GDD&GDT Aufklapp pfeil außerhalb der box
- [ ] GDD&GDT Pagination zu groß für minimalen Mobile view(zeige nicht Seite 2 an, sondern nur Pfeile und aktuelle Seite) >>> @mahula please
- [ ] Informations -> keinen außenabstand der boxen
- [x] Mobile has horizontal scrollbar
- [x] No round corners on mobile
- [x] Mobile-Menu no avatar
- [x] Whats this for in the menu?
- [x] Mobile header should have avatar(can be skipped if we put it in the menu) but the Menu button has no border
- [x] Mobile-Menu should not be in a box
 | 1.0 | 🐛 [Bug] [Design] Fix Mobile Design - <!-- You can find the latest issue templates here https://github.com/ulfgebhardt/issue-templates -->
## 🐛 Bugreport
<!-- Describe your issue in detail. Include screenshots if needed. Give us as much information as possible. Use a clear and concise description of what the bug is.-->
### Mobile
- [x] Startseite zu großer Abstand zwischen box & Konto infos
- [x] Startseite button zweizeilig
- [x] Kein Avatar im Menü
- [x] Beim senden sind die Radioboxen nicht gleichgroß
- [x] GDD&GDT Avatare oval
- [x] GDD&GDT Aufklapp pfeil außerhalb der box
- [ ] GDD&GDT Pagination zu groß für minimalen Mobile view(zeige nicht Seite 2 an, sondern nur Pfeile und aktuelle Seite) >>> @mahula please
- [ ] Informations -> keinen außenabstand der boxen
- [x] Mobile has horizontal scrollbar
- [x] No round corners on mobile
- [x] Mobile-Menu no avatar
- [x] Whats this for in the menu?
- [x] Mobile header should have avatar(can be skipped if we put it in the menu) but the Menu button has no border
- [x] Mobile-Menu should not be in a box
 | non_priority | 🐛 fix mobile design 🐛 bugreport mobile startseite zu großer abstand zwischen box konto infos startseite button zweizeilig kein avatar im menü beim senden sind die radioboxen nicht gleichgroß gdd gdt avatare oval gdd gdt aufklapp pfeil außerhalb der box gdd gdt pagination zu groß für minimalen mobile view zeige nicht seite an sondern nur pfeile und aktuelle seite mahula please informations keinen außenabstand der boxen mobile has horizontal scrollbar no round corners on mobile mobile menu no avatar whats this for in the menu mobile header should have avatar can be skipped if we put it in the menu but the menu button has no border mobile menu should not be in a box | 0 |
14,158 | 3,806,745,434 | IssuesEvent | 2016-03-25 01:45:40 | rosmod/webgme-rosmod | https://api.github.com/repos/rosmod/webgme-rosmod | opened | User guide for deployment and experiment models and infrastructure. | documentation | Should explain how the models work (containment hierarchy, etc.) as well as how they map to hosts on networks for execution. The end of this guide should be the execution of the `RunExperiment` plugin on a sample model and some explanation of how to get access the output of the experiments. | 1.0 | User guide for deployment and experiment models and infrastructure. - Should explain how the models work (containment hierarchy, etc.) as well as how they map to hosts on networks for execution. The end of this guide should be the execution of the `RunExperiment` plugin on a sample model and some explanation of how to get access the output of the experiments. | non_priority | user guide for deployment and experiment models and infrastructure should explain how the models work containment hierarchy etc as well as how they map to hosts on networks for execution the end of this guide should be the execution of the runexperiment plugin on a sample model and some explanation of how to get access the output of the experiments | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.