Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 4 112 | repo_url stringlengths 33 141 | action stringclasses 3 values | title stringlengths 1 957 | labels stringlengths 4 1.11k | body stringlengths 1 261k | index stringclasses 11 values | text_combine stringlengths 95 261k | label stringclasses 2 values | text stringlengths 96 250k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
157,720 | 24,712,943,308 | IssuesEvent | 2022-10-20 03:23:58 | npocccties/chiloportal | https://api.github.com/repos/npocccties/chiloportal | closed | バッジ画像の作成ガイドライン | design | 現在検討中のバッジの見た目は
能力バッジ... 丸くリボンが付いている
知識バッジ... 角丸四角形
であるが、そもそもこのデザインについて議論があまりされていないのでどこかでやる。
さらに運用において禁止ルールを設けたほうが作成しやすい場合もあるかもしれないので、ガイドラインを作成するほうがいいかも。 | 1.0 | バッジ画像の作成ガイドライン - 現在検討中のバッジの見た目は
能力バッジ... 丸くリボンが付いている
知識バッジ... 角丸四角形
であるが、そもそもこのデザインについて議論があまりされていないのでどこかでやる。
さらに運用において禁止ルールを設けたほうが作成しやすい場合もあるかもしれないので、ガイドラインを作成するほうがいいかも。 | design | バッジ画像の作成ガイドライン 現在検討中のバッジの見た目は 能力バッジ 丸くリボンが付いている 知識バッジ 角丸四角形 であるが、そもそもこのデザインについて議論があまりされていないのでどこかでやる。 さらに運用において禁止ルールを設けたほうが作成しやすい場合もあるかもしれないので、ガイドラインを作成するほうがいいかも。 | 1 |
160,266 | 20,099,752,946 | IssuesEvent | 2022-02-07 01:31:08 | kapseliboi/mimic | https://api.github.com/repos/kapseliboi/mimic | opened | CVE-2018-14732 (High) detected in webpack-dev-server-2.5.0.tgz | security vulnerability | ## CVE-2018-14732 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>webpack-dev-server-2.5.0.tgz</b></p></summary>
<p>Serves a webpack app. Updates the browser on changes.</p>
<p>Library home page: <a href="https://registry.npmjs.org/webpack-dev-server/-/webpack-dev-server-2.5.0.tgz">https://registry.npmjs.org/webpack-dev-server/-/webpack-dev-server-2.5.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/webpack-dev-server/package.json</p>
<p>
Dependency Hierarchy:
- :x: **webpack-dev-server-2.5.0.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>
An issue was discovered in lib/Server.js in webpack-dev-server before 3.1.6. Attackers are able to steal developer's code because the origin of requests is not checked by the WebSocket server, which is used for HMR (Hot Module Replacement). Anyone can receive the HMR message sent by the WebSocket server via a ws://127.0.0.1:8080/ connection from any origin.
<p>Publish Date: 2018-09-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14732>CVE-2018-14732</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: 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://nvd.nist.gov/vuln/detail/CVE-2018-14732">https://nvd.nist.gov/vuln/detail/CVE-2018-14732</a></p>
<p>Release Date: 2018-09-21</p>
<p>Fix Resolution: 3.1.6</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-14732 (High) detected in webpack-dev-server-2.5.0.tgz - ## CVE-2018-14732 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>webpack-dev-server-2.5.0.tgz</b></p></summary>
<p>Serves a webpack app. Updates the browser on changes.</p>
<p>Library home page: <a href="https://registry.npmjs.org/webpack-dev-server/-/webpack-dev-server-2.5.0.tgz">https://registry.npmjs.org/webpack-dev-server/-/webpack-dev-server-2.5.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/webpack-dev-server/package.json</p>
<p>
Dependency Hierarchy:
- :x: **webpack-dev-server-2.5.0.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>
An issue was discovered in lib/Server.js in webpack-dev-server before 3.1.6. Attackers are able to steal developer's code because the origin of requests is not checked by the WebSocket server, which is used for HMR (Hot Module Replacement). Anyone can receive the HMR message sent by the WebSocket server via a ws://127.0.0.1:8080/ connection from any origin.
<p>Publish Date: 2018-09-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14732>CVE-2018-14732</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: 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://nvd.nist.gov/vuln/detail/CVE-2018-14732">https://nvd.nist.gov/vuln/detail/CVE-2018-14732</a></p>
<p>Release Date: 2018-09-21</p>
<p>Fix Resolution: 3.1.6</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve high detected in webpack dev server tgz cve high severity vulnerability vulnerable library webpack dev server tgz serves a webpack app updates the browser on changes library home page a href path to dependency file package json path to vulnerable library node modules webpack dev server package json dependency hierarchy x webpack dev server tgz vulnerable library found in base branch master vulnerability details an issue was discovered in lib server js in webpack dev server before attackers are able to steal developer s code because the origin of requests is not checked by the websocket server which is used for hmr hot module replacement anyone can receive the hmr message sent by the websocket server via a ws connection from any origin 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 none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
178,771 | 30,008,392,212 | IssuesEvent | 2023-06-26 13:51:38 | NCIOCPL/ncids | https://api.github.com/repos/NCIOCPL/ncids | closed | [R2.1 Content] Home Page Spanish - Tagline Wraps | Track: Design | **Description:** Presently, the tagline wraps [[ACSF-test](https://www-test-acsf.cancer.gov/espanol)] using the Spanish translation provided to match English. Need to determine if we leave as-is or generate new text (that may deviate from the English translation) to bring the tagline to one line.
**Sub-tasks:**
- [x] Consult Anna/federal team
- [ ] Determine next steps, as needed | 1.0 | [R2.1 Content] Home Page Spanish - Tagline Wraps - **Description:** Presently, the tagline wraps [[ACSF-test](https://www-test-acsf.cancer.gov/espanol)] using the Spanish translation provided to match English. Need to determine if we leave as-is or generate new text (that may deviate from the English translation) to bring the tagline to one line.
**Sub-tasks:**
- [x] Consult Anna/federal team
- [ ] Determine next steps, as needed | design | home page spanish tagline wraps description presently the tagline wraps using the spanish translation provided to match english need to determine if we leave as is or generate new text that may deviate from the english translation to bring the tagline to one line sub tasks consult anna federal team determine next steps as needed | 1 |
68,333 | 8,250,929,114 | IssuesEvent | 2018-09-12 05:45:52 | otavanopisto/muikku | https://api.github.com/repos/otavanopisto/muikku | closed | Big issue with styles in IE11 | REDESIGN2017 bug | IE11 barely supports the styles (specially flex) we have assigned and hence it requires that we prefix and polyfill a lot of the styles, I have installed the sass-autoprefixer, you can see the available functions here
https://github.com/JumpLinkNetwork/sass-prefix-mixins/blob/master/scss/_flexbox.scss
We need to change every single line of the css that uses a non autoprefixed method to a prefixed one, just to get rid of the headache. | 1.0 | Big issue with styles in IE11 - IE11 barely supports the styles (specially flex) we have assigned and hence it requires that we prefix and polyfill a lot of the styles, I have installed the sass-autoprefixer, you can see the available functions here
https://github.com/JumpLinkNetwork/sass-prefix-mixins/blob/master/scss/_flexbox.scss
We need to change every single line of the css that uses a non autoprefixed method to a prefixed one, just to get rid of the headache. | design | big issue with styles in barely supports the styles specially flex we have assigned and hence it requires that we prefix and polyfill a lot of the styles i have installed the sass autoprefixer you can see the available functions here we need to change every single line of the css that uses a non autoprefixed method to a prefixed one just to get rid of the headache | 1 |
195,072 | 22,286,772,239 | IssuesEvent | 2022-06-11 19:03:49 | argoproj-labs/argocd-extensions | https://api.github.com/repos/argoproj-labs/argocd-extensions | opened | Check downloaded resources integrity | bug security | When you pull a resource down, you should check the resources hash against a known good value, in case the third-party is compromised and an attacker replaces the resource (Javascript) with something bad.
Basically this:
https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity
```html
<script src="https://example.com/example-framework.js"
integrity="sha384-oqVuAfXRKap7fdgcCY5uykM6+R9GqQ8K/uxy9rx7HNQlGYl1kPzQho1wx4JwY8wC"
crossorigin="anonymous"></script>
```
Could be done like this:
```yaml
apiVersion: argoproj.io/v1alpha1
kind: ArgoCDExtension
metadata:
name: hello-world
finalizers:
- extensions-finalizer.argocd.argoproj.io
spec:
sources:
- git:
url: https://github.com/argoproj-labs/argocd-example-extension.git
- web:
url: https://github.com/argoproj-labs/argocd-example-extension/releases/download/v0.1.0/extension.tar
integrity: sha384-oqVuAfXRKap7fdgcCY5uykM6+R9GqQ8K/uxy9rx7HNQlGYl1kPzQho1wx4JwY8wC
```
| True | Check downloaded resources integrity - When you pull a resource down, you should check the resources hash against a known good value, in case the third-party is compromised and an attacker replaces the resource (Javascript) with something bad.
Basically this:
https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity
```html
<script src="https://example.com/example-framework.js"
integrity="sha384-oqVuAfXRKap7fdgcCY5uykM6+R9GqQ8K/uxy9rx7HNQlGYl1kPzQho1wx4JwY8wC"
crossorigin="anonymous"></script>
```
Could be done like this:
```yaml
apiVersion: argoproj.io/v1alpha1
kind: ArgoCDExtension
metadata:
name: hello-world
finalizers:
- extensions-finalizer.argocd.argoproj.io
spec:
sources:
- git:
url: https://github.com/argoproj-labs/argocd-example-extension.git
- web:
url: https://github.com/argoproj-labs/argocd-example-extension/releases/download/v0.1.0/extension.tar
integrity: sha384-oqVuAfXRKap7fdgcCY5uykM6+R9GqQ8K/uxy9rx7HNQlGYl1kPzQho1wx4JwY8wC
```
| non_design | check downloaded resources integrity when you pull a resource down you should check the resources hash against a known good value in case the third party is compromised and an attacker replaces the resource javascript with something bad basically this html script src integrity crossorigin anonymous could be done like this yaml apiversion argoproj io kind argocdextension metadata name hello world finalizers extensions finalizer argocd argoproj io spec sources git url web url integrity | 0 |
181,107 | 30,624,482,497 | IssuesEvent | 2023-07-24 10:28:47 | vector-im/compound | https://api.github.com/repos/vector-im/compound | closed | iOS tokens output | P-iOS P-Android A-Design-Tokens T-Enhancement | Only declare colorset in one common color Swift class rather than in all theme variant as it is done today
| 1.0 | iOS tokens output - Only declare colorset in one common color Swift class rather than in all theme variant as it is done today
| design | ios tokens output only declare colorset in one common color swift class rather than in all theme variant as it is done today | 1 |
102,442 | 12,798,743,495 | IssuesEvent | 2020-07-02 14:22:45 | Blazored/Modal | https://api.github.com/repos/Blazored/Modal | closed | Focus trap | Feature Request Help Wanted Needs: Design Up For Grabs | Do you have any plans to implement a focus trap to prevent users from using the keyboard to tab to elements outside of a dialog? | 1.0 | Focus trap - Do you have any plans to implement a focus trap to prevent users from using the keyboard to tab to elements outside of a dialog? | design | focus trap do you have any plans to implement a focus trap to prevent users from using the keyboard to tab to elements outside of a dialog | 1 |
118,546 | 25,332,789,847 | IssuesEvent | 2022-11-18 14:32:05 | arduino/arduino-serial-plotter-webapp | https://api.github.com/repos/arduino/arduino-serial-plotter-webapp | closed | Do a display range adjustable X-axis, Add repeatable options when displaying the same contents | type: enhancement topic: code | When I use the Serial Plotter, I want to extend the display range of the horizontal axis time so that the latest data acquisition and the previous data acquisition can be displayed on the same graph.
Second, when the x-coordinate data is a cyclic change in a range, I want the x-coordinate data to be displayed within the range instead of forward. | 1.0 | Do a display range adjustable X-axis, Add repeatable options when displaying the same contents - When I use the Serial Plotter, I want to extend the display range of the horizontal axis time so that the latest data acquisition and the previous data acquisition can be displayed on the same graph.
Second, when the x-coordinate data is a cyclic change in a range, I want the x-coordinate data to be displayed within the range instead of forward. | non_design | do a display range adjustable x axis add repeatable options when displaying the same contents when i use the serial plotter i want to extend the display range of the horizontal axis time so that the latest data acquisition and the previous data acquisition can be displayed on the same graph second when the x coordinate data is a cyclic change in a range i want the x coordinate data to be displayed within the range instead of forward | 0 |
559,247 | 16,553,642,844 | IssuesEvent | 2021-05-28 11:30:30 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | duckduckgo.com - see bug description | browser-firefox-mobile engine-gecko ml-needsdiagnosis-false priority-important | <!-- @browser: Firefox Mobile 90.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.1.0; Mobile; rv:90.0) Gecko/90.0 Firefox/90.0 -->
<!-- @reported_with: unknown -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/75257 -->
**URL**: https://duckduckgo.com/
**Browser / Version**: Firefox Mobile 90.0
**Operating System**: Android 8.1.0
**Tested Another Browser**: Yes Other
**Problem type**: Something else
**Description**: under search there is no option to search for images, videos, news
**Steps to Reproduce**:
under search there is no option to search for images, videos, news.
out of all the mobile browsers I chose mozilla and the search engine preferably duckduckgo or bing but duckduckgo no longer has the options to search for images. All you have as option is any time and all region .
(the other applications are commercial and I don't prefer)
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2021/5/87d54a93-b481-46b5-bc77-128e82203c0a.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | duckduckgo.com - see bug description - <!-- @browser: Firefox Mobile 90.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.1.0; Mobile; rv:90.0) Gecko/90.0 Firefox/90.0 -->
<!-- @reported_with: unknown -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/75257 -->
**URL**: https://duckduckgo.com/
**Browser / Version**: Firefox Mobile 90.0
**Operating System**: Android 8.1.0
**Tested Another Browser**: Yes Other
**Problem type**: Something else
**Description**: under search there is no option to search for images, videos, news
**Steps to Reproduce**:
under search there is no option to search for images, videos, news.
out of all the mobile browsers I chose mozilla and the search engine preferably duckduckgo or bing but duckduckgo no longer has the options to search for images. All you have as option is any time and all region .
(the other applications are commercial and I don't prefer)
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2021/5/87d54a93-b481-46b5-bc77-128e82203c0a.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_design | duckduckgo com see bug description url browser version firefox mobile operating system android tested another browser yes other problem type something else description under search there is no option to search for images videos news steps to reproduce under search there is no option to search for images videos news out of all the mobile browsers i chose mozilla and the search engine preferably duckduckgo or bing but duckduckgo no longer has the options to search for images all you have as option is any time and all region the other applications are commercial and i don t prefer view the screenshot img alt screenshot src browser configuration none from with ❤️ | 0 |
88,005 | 25,274,897,053 | IssuesEvent | 2022-11-16 11:56:28 | appsmithorg/appsmith | https://api.github.com/repos/appsmithorg/appsmith | opened | [Bug]: Issue with evaluation after we do undo actions | Bug Needs Triaging UI Builders Pod All Widgets | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Description
https://www.loom.com/share/ed6059a2d9c943b896644abca6d9326a
### Steps To Reproduce
1. Dnd a button widget
2. add some text in the tooltip
3. move the focus out of the property pane
4. click cmd+Z(for undo)--> you will notice the tooltip string which we added was removed after undo action but evalution didn't update
https://www.loom.com/share/ed6059a2d9c943b896644abca6d9326a
### Public Sample App
_No response_
### Issue video log
_No response_
### Version
Production | 1.0 | [Bug]: Issue with evaluation after we do undo actions - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Description
https://www.loom.com/share/ed6059a2d9c943b896644abca6d9326a
### Steps To Reproduce
1. Dnd a button widget
2. add some text in the tooltip
3. move the focus out of the property pane
4. click cmd+Z(for undo)--> you will notice the tooltip string which we added was removed after undo action but evalution didn't update
https://www.loom.com/share/ed6059a2d9c943b896644abca6d9326a
### Public Sample App
_No response_
### Issue video log
_No response_
### Version
Production | non_design | issue with evaluation after we do undo actions is there an existing issue for this i have searched the existing issues description steps to reproduce dnd a button widget add some text in the tooltip move the focus out of the property pane click cmd z for undo you will notice the tooltip string which we added was removed after undo action but evalution didn t update public sample app no response issue video log no response version production | 0 |
155,473 | 24,469,929,761 | IssuesEvent | 2022-10-07 18:44:25 | department-of-veterans-affairs/vets-design-system-documentation | https://api.github.com/repos/department-of-veterans-affairs/vets-design-system-documentation | opened | Conversion to USWDS v3 - Text Input - Development | vsp-design-system-team va-text-input | ## Description
Adapt the va-text-input component to match the [USWDS Text input](https://designsystem.digital.gov/components/text-input/) component and import and use the USWDS CSS for this component.
## Details
- Design documents: [add links to any design documents]
- See the [Textarea discovery](https://github.com/department-of-veterans-affairs/component-library/pull/493) for an example
- According to the [plan](https://vfs.atlassian.net/wiki/spaces/DST/pages/2366275704/Plan+-+Aligning+VA+Design+System+components+with+their+USWDS+v3+equivalents), we will be using a prop if necessary to differentiate between our version of this component and the USWDS version. It may not be necessary for this component, this can be decided on a case-by-case basis
## Tasks
- [ ] Create a version of this component that imports and uses the USWDS CSS
- [ ] Make any structural changes necessary and add a prop that determines which version of the component will be used
- [ ] Check with Natalie to make sure the component and the design match
- [ ] Add a USWDS story to Storybook
- [ ] Merge component
- [ ] Create a new release of component-library
- [ ] Update component-library dependency in vets-design-system-documentation to get the updated component-docs.json
## Acceptance Criteria
- [ ] USWDS version has been created and added to Storybook
- [ ] Design.va.gov has the latest version of component-library | 1.0 | Conversion to USWDS v3 - Text Input - Development - ## Description
Adapt the va-text-input component to match the [USWDS Text input](https://designsystem.digital.gov/components/text-input/) component and import and use the USWDS CSS for this component.
## Details
- Design documents: [add links to any design documents]
- See the [Textarea discovery](https://github.com/department-of-veterans-affairs/component-library/pull/493) for an example
- According to the [plan](https://vfs.atlassian.net/wiki/spaces/DST/pages/2366275704/Plan+-+Aligning+VA+Design+System+components+with+their+USWDS+v3+equivalents), we will be using a prop if necessary to differentiate between our version of this component and the USWDS version. It may not be necessary for this component, this can be decided on a case-by-case basis
## Tasks
- [ ] Create a version of this component that imports and uses the USWDS CSS
- [ ] Make any structural changes necessary and add a prop that determines which version of the component will be used
- [ ] Check with Natalie to make sure the component and the design match
- [ ] Add a USWDS story to Storybook
- [ ] Merge component
- [ ] Create a new release of component-library
- [ ] Update component-library dependency in vets-design-system-documentation to get the updated component-docs.json
## Acceptance Criteria
- [ ] USWDS version has been created and added to Storybook
- [ ] Design.va.gov has the latest version of component-library | design | conversion to uswds text input development description adapt the va text input component to match the component and import and use the uswds css for this component details design documents see the for an example according to the we will be using a prop if necessary to differentiate between our version of this component and the uswds version it may not be necessary for this component this can be decided on a case by case basis tasks create a version of this component that imports and uses the uswds css make any structural changes necessary and add a prop that determines which version of the component will be used check with natalie to make sure the component and the design match add a uswds story to storybook merge component create a new release of component library update component library dependency in vets design system documentation to get the updated component docs json acceptance criteria uswds version has been created and added to storybook design va gov has the latest version of component library | 1 |
233,362 | 25,765,341,799 | IssuesEvent | 2022-12-09 01:04:46 | nexmo-community/python-voicemail-dead-drop | https://api.github.com/repos/nexmo-community/python-voicemail-dead-drop | opened | certifi-2019.3.9-py2.py3-none-any.whl: 1 vulnerabilities (highest severity is: 6.8) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>certifi-2019.3.9-py2.py3-none-any.whl</b></p></summary>
<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/60/75/f692a584e85b7eaba0e03827b3d51f45f571c2e793dd731e598828d380aa/certifi-2019.3.9-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/60/75/f692a584e85b7eaba0e03827b3d51f45f571c2e793dd731e598828d380aa/certifi-2019.3.9-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (certifi version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-23491](https://www.mend.io/vulnerability-database/CVE-2022-23491) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.8 | certifi-2019.3.9-py2.py3-none-any.whl | Direct | certifi - 2022.12.07 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-23491</summary>
### Vulnerable Library - <b>certifi-2019.3.9-py2.py3-none-any.whl</b></p>
<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/60/75/f692a584e85b7eaba0e03827b3d51f45f571c2e793dd731e598828d380aa/certifi-2019.3.9-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/60/75/f692a584e85b7eaba0e03827b3d51f45f571c2e793dd731e598828d380aa/certifi-2019.3.9-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **certifi-2019.3.9-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi 2022.12.07 removes root certificates from "TrustCor" from the root store. These are in the process of being removed from Mozilla's trust store. TrustCor's root certificates are being removed pursuant to an investigation prompted by media reporting that TrustCor's ownership also operated a business that produced spyware. Conclusions of Mozilla's investigation can be found in the linked google group discussion.
<p>Publish Date: 2022-12-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23491>CVE-2022-23491</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-23491">https://www.cve.org/CVERecord?id=CVE-2022-23491</a></p>
<p>Release Date: 2022-12-07</p>
<p>Fix Resolution: certifi - 2022.12.07</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | True | certifi-2019.3.9-py2.py3-none-any.whl: 1 vulnerabilities (highest severity is: 6.8) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>certifi-2019.3.9-py2.py3-none-any.whl</b></p></summary>
<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/60/75/f692a584e85b7eaba0e03827b3d51f45f571c2e793dd731e598828d380aa/certifi-2019.3.9-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/60/75/f692a584e85b7eaba0e03827b3d51f45f571c2e793dd731e598828d380aa/certifi-2019.3.9-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (certifi version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-23491](https://www.mend.io/vulnerability-database/CVE-2022-23491) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.8 | certifi-2019.3.9-py2.py3-none-any.whl | Direct | certifi - 2022.12.07 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-23491</summary>
### Vulnerable Library - <b>certifi-2019.3.9-py2.py3-none-any.whl</b></p>
<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/60/75/f692a584e85b7eaba0e03827b3d51f45f571c2e793dd731e598828d380aa/certifi-2019.3.9-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/60/75/f692a584e85b7eaba0e03827b3d51f45f571c2e793dd731e598828d380aa/certifi-2019.3.9-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **certifi-2019.3.9-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi 2022.12.07 removes root certificates from "TrustCor" from the root store. These are in the process of being removed from Mozilla's trust store. TrustCor's root certificates are being removed pursuant to an investigation prompted by media reporting that TrustCor's ownership also operated a business that produced spyware. Conclusions of Mozilla's investigation can be found in the linked google group discussion.
<p>Publish Date: 2022-12-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23491>CVE-2022-23491</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-23491">https://www.cve.org/CVERecord?id=CVE-2022-23491</a></p>
<p>Release Date: 2022-12-07</p>
<p>Fix Resolution: certifi - 2022.12.07</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | non_design | certifi none any whl vulnerabilities highest severity is vulnerable library certifi none any whl python package for providing mozilla s ca bundle library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt vulnerabilities cve severity cvss dependency type fixed in certifi version remediation available medium certifi none any whl direct certifi details cve vulnerable library certifi none any whl python package for providing mozilla s ca bundle library home page a href path to dependency file requirements txt path to vulnerable library requirements txt requirements txt dependency hierarchy x certifi none any whl vulnerable library found in base branch main vulnerability details certifi is a curated collection of root certificates for validating the trustworthiness of ssl certificates while verifying the identity of tls hosts certifi removes root certificates from trustcor from the root store these are in the process of being removed from mozilla s trust store trustcor s root certificates are being removed pursuant to an investigation prompted by media reporting that trustcor s ownership also operated a business that produced spyware conclusions of mozilla s investigation can be found in the linked google group discussion publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required high user interaction none scope changed impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution certifi rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue | 0 |
147,184 | 23,177,501,931 | IssuesEvent | 2022-07-31 16:35:13 | JupiterBroadcasting/jupiterbroadcasting.com | https://api.github.com/repos/JupiterBroadcasting/jupiterbroadcasting.com | closed | "Support Show" button design on Episode pages - needs change | design feedback requested | The bright green colour of the "Support $SHOW" button on Episode pages does not match any of the rest of the site's colour scheme, and frankly I find a little hard to read the white-on-green text (could be my need for new glasses...)
Open to exploration of different options.
Also opening a conversation about the placement of said button:
Would placing the button in the hosts/sponsors section, i.e. below the embedded player, be a more natural fit?
#
| 1.0 | "Support Show" button design on Episode pages - needs change - The bright green colour of the "Support $SHOW" button on Episode pages does not match any of the rest of the site's colour scheme, and frankly I find a little hard to read the white-on-green text (could be my need for new glasses...)
Open to exploration of different options.
Also opening a conversation about the placement of said button:
Would placing the button in the hosts/sponsors section, i.e. below the embedded player, be a more natural fit?
#
| design | support show button design on episode pages needs change the bright green colour of the support show button on episode pages does not match any of the rest of the site s colour scheme and frankly i find a little hard to read the white on green text could be my need for new glasses open to exploration of different options also opening a conversation about the placement of said button would placing the button in the hosts sponsors section i e below the embedded player be a more natural fit | 1 |
6,887 | 2,823,458,117 | IssuesEvent | 2015-05-21 08:57:49 | geetsisbac/WCVVENIXYFVIRBXH3BYTI6TE | https://api.github.com/repos/geetsisbac/WCVVENIXYFVIRBXH3BYTI6TE | closed | ELkOX+N4o8+iY94UQJgL47xXiuomNC5qfmfREzd/RgVXg/tF6d/8F/nHECzWj74tsHdMZSxwZ4uBOEsZqlIGsjaXk/CKfat2kqm7JFiKPI3T2SwYDMmkY7eNp4zn8WyWMm50WZp9SiKSZr2xorwGb47tfxVr2MbxdotDLQ+wNNk= | design | JXrJyDYGobeT8+paaaY7iDNLmBUNF7MUGylXd1Wmu9RuLDzKj8DHdLGSv/bAdLMyF4OV1pwKuvokltWQpILB2Sg5AoZjPJ0QyrDzXLXlwLZVAalXLxylV2FWj4U0/MEyLJuAEklEeBK5ideL5XtAStQs0xLYP5p5kY0hBV9ehFwiatZjyWSzAF4rkGgd8/Tpg9DdTFPnda2hZ/+6cFa/P+k59wkJ4Bolww0KpCYSFnHJJbbXWDMLB4ItrihIYt2nrrca58zXWL6yGihuDGaDSJXCngZpvYwomyWG9dazYmkKIxOR9DgECOJhqLQJw3fzxLairIX3Lg2gxo/EWRs3ol/vkF7G6kofV35TPwu4YAJcBMZSBE4Q+FNfU31gk7ieZ//F0PXqkyHwwqrTD8Is98NhoP4XW0xU5LtqRCWq1TsWpfv2qbY7ViEMiBMiVc9V/qyy7m8Ostpg8Ygbb1Ht1fin8JM6h4p4wdjkTzKmoWkUVH86XeGNO/SzIgNGvYDWf8coK4lVUNmWhIUI0A53nrD+eSncspNLhgZKJJkiXx8YI/aJkLFxwhJK/gnUpNDkH9q1d0SD8K9nyu0uA6EHHlERmCFE9tPFEX1EfEF7NbU1u3u2+YpWFUvemSO20nU3H9q1d0SD8K9nyu0uA6EHHhPYDMl2stqzTOBC5tamYiwf2rV3RIPwr2fK7S4DoQcebFXzbL/+rXUnVGbyVyOgDuDQN9UyiNe5Do7PNVBEf30f2rV3RIPwr2fK7S4DoQcelLxf3p3Mzfmpc6PDLOujQR/atXdEg/CvZ8rtLgOhBx7g7mqAtEShhRtLnseiNmhWVj4mewnHnpYwLjNZBIMsFR/atXdEg/CvZ8rtLgOhBx63QNSrHKz4lt/oULPHUaDRH9q1d0SD8K9nyu0uA6EHHnvffn4XKzq/VZrEgEb2ZyRWPiZ7CceeljAuM1kEgywVH9q1d0SD8K9nyu0uA6EHHt0uO6HeEsyAPj9BSReVxmsf2rV3RIPwr2fK7S4DoQce53+yZP3gMJliWFwVTlwlbUwiatCMFLiCGD2RuFwjpukf2rV3RIPwr2fK7S4DoQceX3U3i2QDw8OnLx+HKFLQ6x/atXdEg/CvZ8rtLgOhBx7CO8m3BbW5Y7H61nC5XqCLYt+S31XHjwwwsAmh4O9PMv7dndlPdNUpDSlTa2eb9Xa0oLZR9AA4os5dC9xu5TE0H9q1d0SD8K9nyu0uA6EHHl8Hy1m6KbJgHlDtWRquHTbKYygM2/47i+7bU/QuuRxQ/t2d2U901SkNKVNrZ5v1dtofmdEcLcTFuZ5a/np6+YAf2rV3RIPwr2fK7S4DoQceUU0ZblgspNGXrKPSD7eM+Vgdr2d9VxERjkMUTkMPTs4f2rV3RIPwr2fK7S4DoQcemvVv1WIKf6mAsFONXGWYdR/atXdEg/CvZ8rtLgOhBx7BpWD13x41M+ImbGIH+AhXM0a2KKV4dzh0uRx6gMpN+R/atXdEg/CvZ8rtLgOhBx6ltAu+eu7Nfj4VjKo9oAcFH9q1d0SD8K9nyu0uA6EHHoO4sxkNcYYuBQbwhhEi36ZV4FRThT4Xvhr4L2QdYZJzH9q1d0SD8K9nyu0uA6EHHnM3RV1aziRP7LMnHZK7DLUf2rV3RIPwr2fK7S4DoQcelZ+/+5W/XrLEsZV3LRmfDM8LMs58B/CEIB+6MKcdqW8f2rV3RIPwr2fK7S4DoQceZ6htTxIGnjlC6MUdT2aWcx/atXdEg/CvZ8rtLgOhBx6fB2BjQGqfdTJrrNs1leeqXfM5LzRteUgM4oCLSHAblDUUoahLWz+7J54cDJs89rz7pccmqyO7GV0ZcCx6JuUJH9q1d0SD8K9nyu0uA6EHHpZ9qVbonzOIE+oP1xp3ojNV4FRThT4Xvhr4L2QdYZJzH9q1d0SD8K9nyu0uA6EHHsMHUNRE3AyLvjNjoeuDSDMf2rV3RIPwr2fK7S4DoQceEKKuMwA7gST38e3ChKMwDFXgVFOFPhe+GvgvZB1hknMf2rV3RIPwr2fK7S4DoQce1GISw0U/0sULM4CAWGhvLR/atXdEg/CvZ8rtLgOhBx6H91fP6Mt1Qj6ai2u6o1sOVeBUU4U+F74a+C9kHWGScx/atXdEg/CvZ8rtLgOhBx5hp5zKPAEW9EsU8bY/jOQKH9q1d0SD8K9nyu0uA6EHHion4XrF2iXYfPLlwSzbeFZV4FRThT4Xvhr4L2QdYZJzH9q1d0SD8K9nyu0uA6EHHuwkAj3HLKPgJmE4yf02IqMf2rV3RIPwr2fK7S4DoQceicYFVBvdDQUwsn7FMIT2tVXgVFOFPhe+GvgvZB1hknMf2rV3RIPwr2fK7S4DoQceg7Y4pUCs1xRdH5okBzw/Nx/atXdEg/CvZ8rtLgOhBx5rkBzJBDUIjz8tquWIxFDRVeBUU4U+F74a+C9kHWGScx/atXdEg/CvZ8rtLgOhBx5QLEnuc9bOF9Dy87NGpVbCH9q1d0SD8K9nyu0uA6EHHtFPDm0Kjb5qjugGqbgow1pV4FRThT4Xvhr4L2QdYZJzH9q1d0SD8K9nyu0uA6EHHprioB7Yw7v/FE7lPhG0p2Yf2rV3RIPwr2fK7S4DoQceYfU+mQVr8sHSpHshvDEHZ8nC4Hy5JkcWU+l/GhUS598f2rV3RIPwr2fK7S4DoQcegWIPHZZg3EDDrmPV46XNTx/atXdEg/CvZ8rtLgOhBx6A2OI0X2psNqZL7FAYk6/OVeBUU4U+F74a+C9kHWGScx/atXdEg/CvZ8rtLgOhBx59CLmefx1MtyWbv5to4a0rH9q1d0SD8K9nyu0uA6EHHkkeTE+eBrnRIy2Z9ERxcydV4FRThT4Xvhr4L2QdYZJzH9q1d0SD8K9nyu0uA6EHHjO034W56cwK+WYN4V1Edvgf2rV3RIPwr2fK7S4DoQceznBf8DIhFNHOA0VqU6V7kVXgVFOFPhe+GvgvZB1hknMf2rV3RIPwr2fK7S4DoQceAORTHS78fUGnq4KCAGajHR/atXdEg/CvZ8rtLgOhBx5oOIYUwdIkT0QHYDuwwAKWIecDg+7ZVVRWDyD3zxUA6v7dndlPdNUpDSlTa2eb9Xbr7GCMDpfAZ3X93VAaVpqQH9q1d0SD8K9nyu0uA6EHHqxi4kcko2XrnMyJcST7arm7m31Fwz/DmfpKiMmIfpmYH9q1d0SD8K9nyu0uA6EHHl/5Zdi807s6XnUkIFGftU8f2rV3RIPwr2fK7S4DoQceaG0Jy9Uqwe5kR+nIXYgYgFXgVFOFPhe+GvgvZB1hknMf2rV3RIPwr2fK7S4DoQcevRsCE7aut4LN+BMqu8Dqfh/atXdEg/CvZ8rtLgOhBx54SKajzkkDqpQer3qZiiM96+RYtQxG2wpPWpHliY25yf7dndlPdNUpDSlTa2eb9XYVpmvTSxHfQOSR1LT7wLGMH9q1d0SD8K9nyu0uA6EHHlTWpyf8tfOsB4vyzPxNLSxV4FRThT4Xvhr4L2QdYZJzH9q1d0SD8K9nyu0uA6EHHkaXlSjsRUUdZ7fpAzinonMf2rV3RIPwr2fK7S4DoQce7Im6Idtvl4ju759OkexfyVXgVFOFPhe+GvgvZB1hknMf2rV3RIPwr2fK7S4DoQceIC5XxuYwcowsm+M128Fp2x/atXdEg/CvZ8rtLgOhBx5rKjiuR2aa+vCvD53jVYYvQXVDo8lcFTkXK6wRCPzA/h/atXdEg/CvZ8rtLgOhBx7K6AEOSGmgYWDGJwpSUKFOH9q1d0SD8K9nyu0uA6EHHr1N4R55zkmtyrnLZHi32hNjztBQKIi/oqdc7wshzLgSQ5IIBIkrsGoFLBeq0s3y6WuRlzJyKovEHFB/ldS3UFcf2rV3RIPwr2fK7S4DoQceTkePDh4uY5ZTFD4VNh4QaUF1Q6PJXBU5FyusEQj8wP4f2rV3RIPwr2fK7S4DoQceVWmv7vLECA8thfboxA0TsR/atXdEg/CvZ8rtLgOhBx5IloOE8TJzD5JDPVcTSl4A2HBhO47lb0STLYK56R7Tqv7dndlPdNUpDSlTa2eb9XYRE1Z2nIdNpxYCo0fELNWKH9q1d0SD8K9nyu0uA6EHHrSe5scEyhbJ2TEHTpkWkD3QWOQKaqWGgs3mkmr28JvD/t2d2U901SkNKVNrZ5v1duES9Tlr2iH8QOGtLSe1IOQf2rV3RIPwr2fK7S4DoQceFyCur+g1p9MFRO4yJy/p5FXgVFOFPhe+GvgvZB1hknMf2rV3RIPwr2fK7S4DoQceJkc/TUKpeJArdxJdtjYnwR/atXdEg/CvZ8rtLgOhBx4SoO4481LgxXMyuyA0WAjNfC3cSifDA2EO/gdPBCO9VN+hQjJoGZ2YJHHx7qJY3O50DG9nOQI/3W41cYZ0yZA2H9q1d0SD8K9nyu0uA6EHHg+BAADdiGFdDmnMyNITbO0h5Fvb/giUevogvwloapSQH9q1d0SD8K9nyu0uA6EHHiw4f5sO2+74pjdvcxkiTOMf2rV3RIPwr2fK7S4DoQce67IGn/3f04H4Hb0l5SVjfZoUsWQYDXU2bXLiyT9YrgW7+rvoJ8J+RgS8RSrsZW6yI25witCEVTPnS69p19qIxx/atXdEg/CvZ8rtLgOhBx79ua6VV6hYu4bHN1v2iFaW7rLpBcfzbBIqeU7ZuUDkox/atXdEg/CvZ8rtLgOhBx77H5KHzfVt6XWDpFE9BBwMH9q1d0SD8K9nyu0uA6EHHvuYnOC2hxfXAFgu0K6aTG5Eoif/6P2LgVFgb5M59areH9q1d0SD8K9nyu0uA6EHHm2S2Wsa8fFQMpHSLX5AfEkf2rV3RIPwr2fK7S4DoQce/nleDaUM1e7rJ5DhQge2gQGIv1w8+/XJ3AAD4Imt3HIf2rV3RIPwr2fK7S4DoQcex7LsRpiFnN5om8paMCzFSx/atXdEg/CvZ8rtLgOhBx6U/XxU2sNCM+BPAlks2pjlVeBUU4U+F74a+C9kHWGScx/atXdEg/CvZ8rtLgOhBx7NiVSX9ecjYICUh/6TMIBDH9q1d0SD8K9nyu0uA6EHHl6xGZNExA83ctCJpl2jkbMPZXy7w1H9NuCS+lZyHbV8/t2d2U901SkNKVNrZ5v1dnHXmF9NOSive4dlTIQtWikf2rV3RIPwr2fK7S4DoQceYACBpQykiWWguBVZGpTmDs8LMs58B/CEIB+6MKcdqW8f2rV3RIPwr2fK7S4DoQcehAJtA+KmM0CM36wPqWLhaB/atXdEg/CvZ8rtLgOhBx5Fs9c49WpSGcJauXlHaIE/qf2h2ikRvN7h5tobDKb8qx/atXdEg/CvZ8rtLgOhBx6d6vgwPmGj5d0dkxXGKYCtH9q1d0SD8K9nyu0uA6EHHmeGt5ZQo7pIrKJFyGU9hHk5j0xBzaum5MS8pvmq4QZ+/t2d2U901SkNKVNrZ5v1dnM7On+4xPLZlf7iW7OesbUf2rV3RIPwr2fK7S4DoQceTjZxKL4k5nMP107qINrkvSaFqUzpF2C5alGfg1Qmv8sf2rV3RIPwr2fK7S4DoQceCo1k6qi7lcpDBj22K7hx1h/atXdEg/CvZ8rtLgOhBx7Lw5BPPGcQU80fbPfiy+05ugTz65cwEh9gNpByzo10X/7dndlPdNUpDSlTa2eb9XaSse6gYhjbw9yppkE8GxJWH9q1d0SD8K9nyu0uA6EHHkvyg1RiJIaTyPuBbVtn8xch72Mw7P87W3HjucCllDI0/t2d2U901SkNKVNrZ5v1dmTUMVKCW5+hkT/LFaryycMf2rV3RIPwr2fK7S4DoQceZV6mciXYY8K23nhnHuyzg6GZIyISs0BKbuii0+tt4EjJnhw4G0abVQH7IUhq4l9B+YKKPJfk7iXEMHbuaB3iyR/atXdEg/CvZ8rtLgOhBx4xNWIgnUzPd3N4qYoZ8qapPyMiUf7ok9B62zOL3pdTAB/atXdEg/CvZ8rtLgOhBx4vM/3D4skLF9A4EftyYdcUH9q1d0SD8K9nyu0uA6EHHvG2tFYkzZUREZfGXhULxaEBAb71CWfqTxhX2VWg+2WaH9q1d0SD8K9nyu0uA6EHHrRWxnCTHKPeLEE0AxjzPxwf2rV3RIPwr2fK7S4DoQceZRnC6CUr4pF3zc3ZFfaHFE4Vm/442LBdsdoz4IAtaflDkggEiSuwagUsF6rSzfLpqhNBC0+pBE40WjyyW14six/atXdEg/CvZ8rtLgOhBx7j+eYosTw1XUze05fEBFB+i06QmW/m4dzq22kPSkvoh/7dndlPdNUpDSlTa2eb9XZcH19RZhjBu3NXzHcPlEFnH9q1d0SD8K9nyu0uA6EHHnoU1D3ZPYECIC0w1Ft7JhsMgePaxKIQbymuDwiiPlWwu/q76CfCfkYEvEUq7GVusghLE1LQ3b684d3vnF//brIf2rV3RIPwr2fK7S4DoQceLMk5glRSBkD3Sm2S8xrAdK22uvOu8TL2GTW9+6j0iET+3Z3ZT3TVKQ0pU2tnm/V2f3gSNv8inH8k7BraCDIVlx/atXdEg/CvZ8rtLgOhBx5V2m32aaD3aWESTPSf6QapTrIYXrJ7FJ2iSJms6sFv5f7dndlPdNUpDSlTa2eb9XZ1X2YUYyJvRnspVwD+RhzwH9q1d0SD8K9nyu0uA6EHHo9/Fs8JUl5T/iOaMRvyV9K5GJ9e+Db715OC9B8qa6X2H9q1d0SD8K9nyu0uA6EHHp+Bh2E2SGfjRnNbts6KG0Uf2rV3RIPwr2fK7S4DoQcemnGZy4/udAsSVRgeyhslJMN3oNN9IJ/iSNzU4qm9tgq7+rvoJ8J+RgS8RSrsZW6yOFwemMfrYYurdPy27fOLVB/atXdEg/CvZ8rtLgOhBx7dceBunCAyU0ttJrcrISoHuqzUk6k08XyH45vISEjWBbv6u+gnwn5GBLxFKuxlbrIptmhe6EWVVSxmFLTA4ocVH9q1d0SD8K9nyu0uA6EHHpiDyuWtJtksbZMJzkJg9Cl/jENMVvwgct8QcqgZIt3uH9q1d0SD8K9nyu0uA6EHHiB4UeZqAkPDiqmDNAEsbT8f2rV3RIPwr2fK7S4DoQceI5I3vKEWtR5GL7sUnHFY3AEBvvUJZ+pPGFfZVaD7ZZof2rV3RIPwr2fK7S4DoQcennxpp/tavr8kvJTwfDO6xh/atXdEg/CvZ8rtLgOhBx4KsuVqHWYHRc8ogr3DOHDEAQG+9Qln6k8YV9lVoPtlmh/atXdEg/CvZ8rtLgOhBx7TiAP+4Ms1voGSbXUwSmKdH9q1d0SD8K9nyu0uA6EHHou5gYNdjWHIsf18clpFoLwBAb71CWfqTxhX2VWg+2WaH9q1d0SD8K9nyu0uA6EHHpbWNIMI/K8Gu/WYt39G5b4f2rV3RIPwr2fK7S4DoQcez+RMrCan1nh74BuilzkDwfhYORKjAusi1soBRiXmBYT+3Z3ZT3TVKQ0pU2tnm/V2GG35aeJF8NMEeEqRza0NQh/atXdEg/CvZ8rtLgOhBx7r5HtxSk0X3ckHBctWQjReAlcBAKqSoG8jkkGAkdMz0x/atXdEg/CvZ8rtLgOhBx7Qpa7neoMvlqLoy23122TTH9q1d0SD8K9nyu0uA6EHHlhysldgOLfg+AQi/vqNigcBAb71CWfqTxhX2VWg+2WaH9q1d0SD8K9nyu0uA6EHHpomBKys6tFUEfCFFNElk/Mf2rV3RIPwr2fK7S4DoQceEC9F4Rat2S+EpCDpaaWroAEBvvUJZ+pPGFfZVaD7ZZof2rV3RIPwr2fK7S4DoQceR1JpBMbtceGLaBLIcam/ux/atXdEg/CvZ8rtLgOhBx5PI84Q0ggL1f1bKoggdmazdTzJOXqhQoHh8wEreQIisx/atXdEg/CvZ8rtLgOhBx6FdvA8q0JGBBfIB7bzkCgNH9q1d0SD8K9nyu0uA6EHHro6QJMcV9dtKPXTP6cjVmPW6F6/v36xZZW6v+byUVDK/t2d2U901SkNKVNrZ5v1dr8b7DmdqmqJNudV8qvkp14f2rV3RIPwr2fK7S4DoQceXfNIkF7UHb+e98Kl30UOY9boXr+/frFllbq/5vJRUMr+3Z3ZT3TVKQ0pU2tnm/V2XTI2s+r4eGGaIfaNopwPth/atXdEg/CvZ8rtLgOhBx5QAmIP20+q08I1huBKmGOj1uhev79+sWWVur/m8lFQyv7dndlPdNUpDSlTa2eb9XZjpFT8YjSvDLT4MSe0O3gYH9q1d0SD8K9nyu0uA6EHHlIGeTfIRLuv/gyAvacG+fjxWiX7RJbJ3QtzRrzKslICrtECKTL5bn8PY5DK3hUuartS/k07D4b6aCS3a2cSrEEf2rV3RIPwr2fK7S4DoQceVTek2Ks7jy54CCNloPPCXki6DwrqFQ/MdjrRabLohcAf2rV3RIPwr2fK7S4DoQceSUePzRY6lU+nBQg63D9z+B/atXdEg/CvZ8rtLgOhBx4U0JXRESJpIvQjouuJAedV7rLpBcfzbBIqeU7ZuUDkox/atXdEg/CvZ8rtLgOhBx7NASsfqueGN0Nd1VZCQ6zoH9q1d0SD8K9nyu0uA6EHHkuiBdjWgLjGCcOjrpTBqpVdEZ4oPSPbw08EBLOs1ISP/t2d2U901SkNKVNrZ5v1dnGQnUW/9gK+deFoSP3na1Af2rV3RIPwr2fK7S4DoQcef+2TyDoMT7osPCORST2LvNBY5ApqpYaCzeaSavbwm8P+3Z3ZT3TVKQ0pU2tnm/V20PwoHlkKUv1TTFYzJymqbx/atXdEg/CvZ8rtLgOhBx5Da0ki/vsXmvtyLzvOwqPgCwqcDRURZ0+I8lV0Vn4Zx3lOVAJCU5sAlLz00b1u161gsyURQl+DkNLyKgtOnN4+ovVQHIxQ0VQo+aO2u8l1KA== | 1.0 | ELkOX+N4o8+iY94UQJgL47xXiuomNC5qfmfREzd/RgVXg/tF6d/8F/nHECzWj74tsHdMZSxwZ4uBOEsZqlIGsjaXk/CKfat2kqm7JFiKPI3T2SwYDMmkY7eNp4zn8WyWMm50WZp9SiKSZr2xorwGb47tfxVr2MbxdotDLQ+wNNk= - JXrJyDYGobeT8+paaaY7iDNLmBUNF7MUGylXd1Wmu9RuLDzKj8DHdLGSv/bAdLMyF4OV1pwKuvokltWQpILB2Sg5AoZjPJ0QyrDzXLXlwLZVAalXLxylV2FWj4U0/MEyLJuAEklEeBK5ideL5XtAStQs0xLYP5p5kY0hBV9ehFwiatZjyWSzAF4rkGgd8/Tpg9DdTFPnda2hZ/+6cFa/P+k59wkJ4Bolww0KpCYSFnHJJbbXWDMLB4ItrihIYt2nrrca58zXWL6yGihuDGaDSJXCngZpvYwomyWG9dazYmkKIxOR9DgECOJhqLQJw3fzxLairIX3Lg2gxo/EWRs3ol/vkF7G6kofV35TPwu4YAJcBMZSBE4Q+FNfU31gk7ieZ//F0PXqkyHwwqrTD8Is98NhoP4XW0xU5LtqRCWq1TsWpfv2qbY7ViEMiBMiVc9V/qyy7m8Ostpg8Ygbb1Ht1fin8JM6h4p4wdjkTzKmoWkUVH86XeGNO/SzIgNGvYDWf8coK4lVUNmWhIUI0A53nrD+eSncspNLhgZKJJkiXx8YI/aJkLFxwhJK/gnUpNDkH9q1d0SD8K9nyu0uA6EHHlERmCFE9tPFEX1EfEF7NbU1u3u2+YpWFUvemSO20nU3H9q1d0SD8K9nyu0uA6EHHhPYDMl2stqzTOBC5tamYiwf2rV3RIPwr2fK7S4DoQcebFXzbL/+rXUnVGbyVyOgDuDQN9UyiNe5Do7PNVBEf30f2rV3RIPwr2fK7S4DoQcelLxf3p3Mzfmpc6PDLOujQR/atXdEg/CvZ8rtLgOhBx7g7mqAtEShhRtLnseiNmhWVj4mewnHnpYwLjNZBIMsFR/atXdEg/CvZ8rtLgOhBx63QNSrHKz4lt/oULPHUaDRH9q1d0SD8K9nyu0uA6EHHnvffn4XKzq/VZrEgEb2ZyRWPiZ7CceeljAuM1kEgywVH9q1d0SD8K9nyu0uA6EHHt0uO6HeEsyAPj9BSReVxmsf2rV3RIPwr2fK7S4DoQce53+yZP3gMJliWFwVTlwlbUwiatCMFLiCGD2RuFwjpukf2rV3RIPwr2fK7S4DoQceX3U3i2QDw8OnLx+HKFLQ6x/atXdEg/CvZ8rtLgOhBx7CO8m3BbW5Y7H61nC5XqCLYt+S31XHjwwwsAmh4O9PMv7dndlPdNUpDSlTa2eb9Xa0oLZR9AA4os5dC9xu5TE0H9q1d0SD8K9nyu0uA6EHHl8Hy1m6KbJgHlDtWRquHTbKYygM2/47i+7bU/QuuRxQ/t2d2U901SkNKVNrZ5v1dtofmdEcLcTFuZ5a/np6+YAf2rV3RIPwr2fK7S4DoQceUU0ZblgspNGXrKPSD7eM+Vgdr2d9VxERjkMUTkMPTs4f2rV3RIPwr2fK7S4DoQcemvVv1WIKf6mAsFONXGWYdR/atXdEg/CvZ8rtLgOhBx7BpWD13x41M+ImbGIH+AhXM0a2KKV4dzh0uRx6gMpN+R/atXdEg/CvZ8rtLgOhBx6ltAu+eu7Nfj4VjKo9oAcFH9q1d0SD8K9nyu0uA6EHHoO4sxkNcYYuBQbwhhEi36ZV4FRThT4Xvhr4L2QdYZJzH9q1d0SD8K9nyu0uA6EHHnM3RV1aziRP7LMnHZK7DLUf2rV3RIPwr2fK7S4DoQcelZ+/+5W/XrLEsZV3LRmfDM8LMs58B/CEIB+6MKcdqW8f2rV3RIPwr2fK7S4DoQceZ6htTxIGnjlC6MUdT2aWcx/atXdEg/CvZ8rtLgOhBx6fB2BjQGqfdTJrrNs1leeqXfM5LzRteUgM4oCLSHAblDUUoahLWz+7J54cDJs89rz7pccmqyO7GV0ZcCx6JuUJH9q1d0SD8K9nyu0uA6EHHpZ9qVbonzOIE+oP1xp3ojNV4FRThT4Xvhr4L2QdYZJzH9q1d0SD8K9nyu0uA6EHHsMHUNRE3AyLvjNjoeuDSDMf2rV3RIPwr2fK7S4DoQceEKKuMwA7gST38e3ChKMwDFXgVFOFPhe+GvgvZB1hknMf2rV3RIPwr2fK7S4DoQce1GISw0U/0sULM4CAWGhvLR/atXdEg/CvZ8rtLgOhBx6H91fP6Mt1Qj6ai2u6o1sOVeBUU4U+F74a+C9kHWGScx/atXdEg/CvZ8rtLgOhBx5hp5zKPAEW9EsU8bY/jOQKH9q1d0SD8K9nyu0uA6EHHion4XrF2iXYfPLlwSzbeFZV4FRThT4Xvhr4L2QdYZJzH9q1d0SD8K9nyu0uA6EHHuwkAj3HLKPgJmE4yf02IqMf2rV3RIPwr2fK7S4DoQceicYFVBvdDQUwsn7FMIT2tVXgVFOFPhe+GvgvZB1hknMf2rV3RIPwr2fK7S4DoQceg7Y4pUCs1xRdH5okBzw/Nx/atXdEg/CvZ8rtLgOhBx5rkBzJBDUIjz8tquWIxFDRVeBUU4U+F74a+C9kHWGScx/atXdEg/CvZ8rtLgOhBx5QLEnuc9bOF9Dy87NGpVbCH9q1d0SD8K9nyu0uA6EHHtFPDm0Kjb5qjugGqbgow1pV4FRThT4Xvhr4L2QdYZJzH9q1d0SD8K9nyu0uA6EHHprioB7Yw7v/FE7lPhG0p2Yf2rV3RIPwr2fK7S4DoQceYfU+mQVr8sHSpHshvDEHZ8nC4Hy5JkcWU+l/GhUS598f2rV3RIPwr2fK7S4DoQcegWIPHZZg3EDDrmPV46XNTx/atXdEg/CvZ8rtLgOhBx6A2OI0X2psNqZL7FAYk6/OVeBUU4U+F74a+C9kHWGScx/atXdEg/CvZ8rtLgOhBx59CLmefx1MtyWbv5to4a0rH9q1d0SD8K9nyu0uA6EHHkkeTE+eBrnRIy2Z9ERxcydV4FRThT4Xvhr4L2QdYZJzH9q1d0SD8K9nyu0uA6EHHjO034W56cwK+WYN4V1Edvgf2rV3RIPwr2fK7S4DoQceznBf8DIhFNHOA0VqU6V7kVXgVFOFPhe+GvgvZB1hknMf2rV3RIPwr2fK7S4DoQceAORTHS78fUGnq4KCAGajHR/atXdEg/CvZ8rtLgOhBx5oOIYUwdIkT0QHYDuwwAKWIecDg+7ZVVRWDyD3zxUA6v7dndlPdNUpDSlTa2eb9Xbr7GCMDpfAZ3X93VAaVpqQH9q1d0SD8K9nyu0uA6EHHqxi4kcko2XrnMyJcST7arm7m31Fwz/DmfpKiMmIfpmYH9q1d0SD8K9nyu0uA6EHHl/5Zdi807s6XnUkIFGftU8f2rV3RIPwr2fK7S4DoQceaG0Jy9Uqwe5kR+nIXYgYgFXgVFOFPhe+GvgvZB1hknMf2rV3RIPwr2fK7S4DoQcevRsCE7aut4LN+BMqu8Dqfh/atXdEg/CvZ8rtLgOhBx54SKajzkkDqpQer3qZiiM96+RYtQxG2wpPWpHliY25yf7dndlPdNUpDSlTa2eb9XYVpmvTSxHfQOSR1LT7wLGMH9q1d0SD8K9nyu0uA6EHHlTWpyf8tfOsB4vyzPxNLSxV4FRThT4Xvhr4L2QdYZJzH9q1d0SD8K9nyu0uA6EHHkaXlSjsRUUdZ7fpAzinonMf2rV3RIPwr2fK7S4DoQce7Im6Idtvl4ju759OkexfyVXgVFOFPhe+GvgvZB1hknMf2rV3RIPwr2fK7S4DoQceIC5XxuYwcowsm+M128Fp2x/atXdEg/CvZ8rtLgOhBx5rKjiuR2aa+vCvD53jVYYvQXVDo8lcFTkXK6wRCPzA/h/atXdEg/CvZ8rtLgOhBx7K6AEOSGmgYWDGJwpSUKFOH9q1d0SD8K9nyu0uA6EHHr1N4R55zkmtyrnLZHi32hNjztBQKIi/oqdc7wshzLgSQ5IIBIkrsGoFLBeq0s3y6WuRlzJyKovEHFB/ldS3UFcf2rV3RIPwr2fK7S4DoQceTkePDh4uY5ZTFD4VNh4QaUF1Q6PJXBU5FyusEQj8wP4f2rV3RIPwr2fK7S4DoQceVWmv7vLECA8thfboxA0TsR/atXdEg/CvZ8rtLgOhBx5IloOE8TJzD5JDPVcTSl4A2HBhO47lb0STLYK56R7Tqv7dndlPdNUpDSlTa2eb9XYRE1Z2nIdNpxYCo0fELNWKH9q1d0SD8K9nyu0uA6EHHrSe5scEyhbJ2TEHTpkWkD3QWOQKaqWGgs3mkmr28JvD/t2d2U901SkNKVNrZ5v1duES9Tlr2iH8QOGtLSe1IOQf2rV3RIPwr2fK7S4DoQceFyCur+g1p9MFRO4yJy/p5FXgVFOFPhe+GvgvZB1hknMf2rV3RIPwr2fK7S4DoQceJkc/TUKpeJArdxJdtjYnwR/atXdEg/CvZ8rtLgOhBx4SoO4481LgxXMyuyA0WAjNfC3cSifDA2EO/gdPBCO9VN+hQjJoGZ2YJHHx7qJY3O50DG9nOQI/3W41cYZ0yZA2H9q1d0SD8K9nyu0uA6EHHg+BAADdiGFdDmnMyNITbO0h5Fvb/giUevogvwloapSQH9q1d0SD8K9nyu0uA6EHHiw4f5sO2+74pjdvcxkiTOMf2rV3RIPwr2fK7S4DoQce67IGn/3f04H4Hb0l5SVjfZoUsWQYDXU2bXLiyT9YrgW7+rvoJ8J+RgS8RSrsZW6yI25witCEVTPnS69p19qIxx/atXdEg/CvZ8rtLgOhBx79ua6VV6hYu4bHN1v2iFaW7rLpBcfzbBIqeU7ZuUDkox/atXdEg/CvZ8rtLgOhBx77H5KHzfVt6XWDpFE9BBwMH9q1d0SD8K9nyu0uA6EHHvuYnOC2hxfXAFgu0K6aTG5Eoif/6P2LgVFgb5M59areH9q1d0SD8K9nyu0uA6EHHm2S2Wsa8fFQMpHSLX5AfEkf2rV3RIPwr2fK7S4DoQce/nleDaUM1e7rJ5DhQge2gQGIv1w8+/XJ3AAD4Imt3HIf2rV3RIPwr2fK7S4DoQcex7LsRpiFnN5om8paMCzFSx/atXdEg/CvZ8rtLgOhBx6U/XxU2sNCM+BPAlks2pjlVeBUU4U+F74a+C9kHWGScx/atXdEg/CvZ8rtLgOhBx7NiVSX9ecjYICUh/6TMIBDH9q1d0SD8K9nyu0uA6EHHl6xGZNExA83ctCJpl2jkbMPZXy7w1H9NuCS+lZyHbV8/t2d2U901SkNKVNrZ5v1dnHXmF9NOSive4dlTIQtWikf2rV3RIPwr2fK7S4DoQceYACBpQykiWWguBVZGpTmDs8LMs58B/CEIB+6MKcdqW8f2rV3RIPwr2fK7S4DoQcehAJtA+KmM0CM36wPqWLhaB/atXdEg/CvZ8rtLgOhBx5Fs9c49WpSGcJauXlHaIE/qf2h2ikRvN7h5tobDKb8qx/atXdEg/CvZ8rtLgOhBx6d6vgwPmGj5d0dkxXGKYCtH9q1d0SD8K9nyu0uA6EHHmeGt5ZQo7pIrKJFyGU9hHk5j0xBzaum5MS8pvmq4QZ+/t2d2U901SkNKVNrZ5v1dnM7On+4xPLZlf7iW7OesbUf2rV3RIPwr2fK7S4DoQceTjZxKL4k5nMP107qINrkvSaFqUzpF2C5alGfg1Qmv8sf2rV3RIPwr2fK7S4DoQceCo1k6qi7lcpDBj22K7hx1h/atXdEg/CvZ8rtLgOhBx7Lw5BPPGcQU80fbPfiy+05ugTz65cwEh9gNpByzo10X/7dndlPdNUpDSlTa2eb9XaSse6gYhjbw9yppkE8GxJWH9q1d0SD8K9nyu0uA6EHHkvyg1RiJIaTyPuBbVtn8xch72Mw7P87W3HjucCllDI0/t2d2U901SkNKVNrZ5v1dmTUMVKCW5+hkT/LFaryycMf2rV3RIPwr2fK7S4DoQceZV6mciXYY8K23nhnHuyzg6GZIyISs0BKbuii0+tt4EjJnhw4G0abVQH7IUhq4l9B+YKKPJfk7iXEMHbuaB3iyR/atXdEg/CvZ8rtLgOhBx4xNWIgnUzPd3N4qYoZ8qapPyMiUf7ok9B62zOL3pdTAB/atXdEg/CvZ8rtLgOhBx4vM/3D4skLF9A4EftyYdcUH9q1d0SD8K9nyu0uA6EHHvG2tFYkzZUREZfGXhULxaEBAb71CWfqTxhX2VWg+2WaH9q1d0SD8K9nyu0uA6EHHrRWxnCTHKPeLEE0AxjzPxwf2rV3RIPwr2fK7S4DoQceZRnC6CUr4pF3zc3ZFfaHFE4Vm/442LBdsdoz4IAtaflDkggEiSuwagUsF6rSzfLpqhNBC0+pBE40WjyyW14six/atXdEg/CvZ8rtLgOhBx7j+eYosTw1XUze05fEBFB+i06QmW/m4dzq22kPSkvoh/7dndlPdNUpDSlTa2eb9XZcH19RZhjBu3NXzHcPlEFnH9q1d0SD8K9nyu0uA6EHHnoU1D3ZPYECIC0w1Ft7JhsMgePaxKIQbymuDwiiPlWwu/q76CfCfkYEvEUq7GVusghLE1LQ3b684d3vnF//brIf2rV3RIPwr2fK7S4DoQceLMk5glRSBkD3Sm2S8xrAdK22uvOu8TL2GTW9+6j0iET+3Z3ZT3TVKQ0pU2tnm/V2f3gSNv8inH8k7BraCDIVlx/atXdEg/CvZ8rtLgOhBx5V2m32aaD3aWESTPSf6QapTrIYXrJ7FJ2iSJms6sFv5f7dndlPdNUpDSlTa2eb9XZ1X2YUYyJvRnspVwD+RhzwH9q1d0SD8K9nyu0uA6EHHo9/Fs8JUl5T/iOaMRvyV9K5GJ9e+Db715OC9B8qa6X2H9q1d0SD8K9nyu0uA6EHHp+Bh2E2SGfjRnNbts6KG0Uf2rV3RIPwr2fK7S4DoQcemnGZy4/udAsSVRgeyhslJMN3oNN9IJ/iSNzU4qm9tgq7+rvoJ8J+RgS8RSrsZW6yOFwemMfrYYurdPy27fOLVB/atXdEg/CvZ8rtLgOhBx7dceBunCAyU0ttJrcrISoHuqzUk6k08XyH45vISEjWBbv6u+gnwn5GBLxFKuxlbrIptmhe6EWVVSxmFLTA4ocVH9q1d0SD8K9nyu0uA6EHHpiDyuWtJtksbZMJzkJg9Cl/jENMVvwgct8QcqgZIt3uH9q1d0SD8K9nyu0uA6EHHiB4UeZqAkPDiqmDNAEsbT8f2rV3RIPwr2fK7S4DoQceI5I3vKEWtR5GL7sUnHFY3AEBvvUJZ+pPGFfZVaD7ZZof2rV3RIPwr2fK7S4DoQcennxpp/tavr8kvJTwfDO6xh/atXdEg/CvZ8rtLgOhBx4KsuVqHWYHRc8ogr3DOHDEAQG+9Qln6k8YV9lVoPtlmh/atXdEg/CvZ8rtLgOhBx7TiAP+4Ms1voGSbXUwSmKdH9q1d0SD8K9nyu0uA6EHHou5gYNdjWHIsf18clpFoLwBAb71CWfqTxhX2VWg+2WaH9q1d0SD8K9nyu0uA6EHHpbWNIMI/K8Gu/WYt39G5b4f2rV3RIPwr2fK7S4DoQcez+RMrCan1nh74BuilzkDwfhYORKjAusi1soBRiXmBYT+3Z3ZT3TVKQ0pU2tnm/V2GG35aeJF8NMEeEqRza0NQh/atXdEg/CvZ8rtLgOhBx7r5HtxSk0X3ckHBctWQjReAlcBAKqSoG8jkkGAkdMz0x/atXdEg/CvZ8rtLgOhBx7Qpa7neoMvlqLoy23122TTH9q1d0SD8K9nyu0uA6EHHlhysldgOLfg+AQi/vqNigcBAb71CWfqTxhX2VWg+2WaH9q1d0SD8K9nyu0uA6EHHpomBKys6tFUEfCFFNElk/Mf2rV3RIPwr2fK7S4DoQceEC9F4Rat2S+EpCDpaaWroAEBvvUJZ+pPGFfZVaD7ZZof2rV3RIPwr2fK7S4DoQceR1JpBMbtceGLaBLIcam/ux/atXdEg/CvZ8rtLgOhBx5PI84Q0ggL1f1bKoggdmazdTzJOXqhQoHh8wEreQIisx/atXdEg/CvZ8rtLgOhBx6FdvA8q0JGBBfIB7bzkCgNH9q1d0SD8K9nyu0uA6EHHro6QJMcV9dtKPXTP6cjVmPW6F6/v36xZZW6v+byUVDK/t2d2U901SkNKVNrZ5v1dr8b7DmdqmqJNudV8qvkp14f2rV3RIPwr2fK7S4DoQceXfNIkF7UHb+e98Kl30UOY9boXr+/frFllbq/5vJRUMr+3Z3ZT3TVKQ0pU2tnm/V2XTI2s+r4eGGaIfaNopwPth/atXdEg/CvZ8rtLgOhBx5QAmIP20+q08I1huBKmGOj1uhev79+sWWVur/m8lFQyv7dndlPdNUpDSlTa2eb9XZjpFT8YjSvDLT4MSe0O3gYH9q1d0SD8K9nyu0uA6EHHlIGeTfIRLuv/gyAvacG+fjxWiX7RJbJ3QtzRrzKslICrtECKTL5bn8PY5DK3hUuartS/k07D4b6aCS3a2cSrEEf2rV3RIPwr2fK7S4DoQceVTek2Ks7jy54CCNloPPCXki6DwrqFQ/MdjrRabLohcAf2rV3RIPwr2fK7S4DoQceSUePzRY6lU+nBQg63D9z+B/atXdEg/CvZ8rtLgOhBx4U0JXRESJpIvQjouuJAedV7rLpBcfzbBIqeU7ZuUDkox/atXdEg/CvZ8rtLgOhBx7NASsfqueGN0Nd1VZCQ6zoH9q1d0SD8K9nyu0uA6EHHkuiBdjWgLjGCcOjrpTBqpVdEZ4oPSPbw08EBLOs1ISP/t2d2U901SkNKVNrZ5v1dnGQnUW/9gK+deFoSP3na1Af2rV3RIPwr2fK7S4DoQcef+2TyDoMT7osPCORST2LvNBY5ApqpYaCzeaSavbwm8P+3Z3ZT3TVKQ0pU2tnm/V20PwoHlkKUv1TTFYzJymqbx/atXdEg/CvZ8rtLgOhBx5Da0ki/vsXmvtyLzvOwqPgCwqcDRURZ0+I8lV0Vn4Zx3lOVAJCU5sAlLz00b1u161gsyURQl+DkNLyKgtOnN4+ovVQHIxQ0VQo+aO2u8l1KA== | design | elkox rgvxg wnnk p ajklfxwhjk atxdeg atxdeg atxdeg quurxq atxdeg imbgih r atxdeg ceib atxdeg atxdeg atxdeg nx atxdeg atxdeg l atxdeg atxdeg atxdeg nixygygfxgvfofphe atxdeg atxdeg h atxdeg atxdeg tukpejardxjdtjynwr atxdeg atxdeg atxdeg atxdeg atxdeg ceib atxdeg atxdeg atxdeg hkt atxdeg atxdeg atxdeg atxdeg atxdeg atxdeg atxdeg atxdeg atxdeg aqi epcdpaawroaebvvujz ux atxdeg atxdeg byuvdk frfllbq atxdeg swwvur gyavacg b atxdeg atxdeg atxdeg | 1 |
125,656 | 16,823,888,861 | IssuesEvent | 2021-06-17 15:59:06 | zulip/zulip | https://api.github.com/repos/zulip/zulip | opened | Customize notification sounds per-stream | area: notifications (other) area: stream settings design | Since we now offer a reasonably wide choice of notification sounds, we could support customizing the sound for each stream. That'd allow users to be able to distinguish which stream a notification came from just from the audio cue, which seems like a nice thing to have.
CC @alya | 1.0 | Customize notification sounds per-stream - Since we now offer a reasonably wide choice of notification sounds, we could support customizing the sound for each stream. That'd allow users to be able to distinguish which stream a notification came from just from the audio cue, which seems like a nice thing to have.
CC @alya | design | customize notification sounds per stream since we now offer a reasonably wide choice of notification sounds we could support customizing the sound for each stream that d allow users to be able to distinguish which stream a notification came from just from the audio cue which seems like a nice thing to have cc alya | 1 |
378,687 | 26,332,914,413 | IssuesEvent | 2023-01-10 12:14:46 | Kotlin/dokka | https://api.github.com/repos/Kotlin/dokka | closed | Example: Dokka + MPP + MavenPublish | enhancement question documentation | **Question**
Thank you for adding MPP support. I was wondering if there is an example of how we can now make uploading documentation via the maven-publish plugin?
(Or if it's possible to make it detect the maven-publish plugin to auto attach artifacts)
**Installation**
- Operating system: macOS
- Build tool: Gradle v6.1.1 / Kotlin 1.3.70-eap / MPP
- Dokka version: 0.10.1
**Additional context**
Example for how to attach javadoc artifacts - or support adding them automatically when the maven-publish plugin is added.
| 1.0 | Example: Dokka + MPP + MavenPublish - **Question**
Thank you for adding MPP support. I was wondering if there is an example of how we can now make uploading documentation via the maven-publish plugin?
(Or if it's possible to make it detect the maven-publish plugin to auto attach artifacts)
**Installation**
- Operating system: macOS
- Build tool: Gradle v6.1.1 / Kotlin 1.3.70-eap / MPP
- Dokka version: 0.10.1
**Additional context**
Example for how to attach javadoc artifacts - or support adding them automatically when the maven-publish plugin is added.
| non_design | example dokka mpp mavenpublish question thank you for adding mpp support i was wondering if there is an example of how we can now make uploading documentation via the maven publish plugin or if it s possible to make it detect the maven publish plugin to auto attach artifacts installation operating system macos build tool gradle kotlin eap mpp dokka version additional context example for how to attach javadoc artifacts or support adding them automatically when the maven publish plugin is added | 0 |
4,060 | 2,963,565,974 | IssuesEvent | 2015-07-10 11:21:10 | epimorphics/elda | https://api.github.com/repos/epimorphics/elda | closed | Elda does not forward 500 problems from the SPARQL endpoint
| from_gcode | <pre>If the SPARQL endpoint reports a problem, Elda has nothing that can
handle it (not at the top level nor in the Source query handlers).
This makes generating good error reports challenging.
</pre>
| 1.0 | Elda does not forward 500 problems from the SPARQL endpoint
- <pre>If the SPARQL endpoint reports a problem, Elda has nothing that can
handle it (not at the top level nor in the Source query handlers).
This makes generating good error reports challenging.
</pre>
| non_design | elda does not forward problems from the sparql endpoint if the sparql endpoint reports a problem elda has nothing that can handle it not at the top level nor in the source query handlers this makes generating good error reports challenging | 0 |
48,529 | 20,169,004,392 | IssuesEvent | 2022-02-10 08:40:07 | kubeshop/testkube | https://api.github.com/repos/kubeshop/testkube | opened | Pass file content by Volume | enhancement service:api 🎡 | **Describe the enhancement you'd like to see**
Currently, the information about tests are passed as a data structure (part of execution), as it complicates creating
We could try to create volume in the API server and then mount it in the job container (if possible).
https://kubernetes.io/docs/concepts/storage/volumes/#emptydir-configuration-example
**Additional context**
It'll simplify a lot writing a new executor - currently, we have only libs for Go which help getting files, we can move this logic to api - and simply pass everything fetched to volume. | 1.0 | Pass file content by Volume - **Describe the enhancement you'd like to see**
Currently, the information about tests are passed as a data structure (part of execution), as it complicates creating
We could try to create volume in the API server and then mount it in the job container (if possible).
https://kubernetes.io/docs/concepts/storage/volumes/#emptydir-configuration-example
**Additional context**
It'll simplify a lot writing a new executor - currently, we have only libs for Go which help getting files, we can move this logic to api - and simply pass everything fetched to volume. | non_design | pass file content by volume describe the enhancement you d like to see currently the information about tests are passed as a data structure part of execution as it complicates creating we could try to create volume in the api server and then mount it in the job container if possible additional context it ll simplify a lot writing a new executor currently we have only libs for go which help getting files we can move this logic to api and simply pass everything fetched to volume | 0 |
278,765 | 24,174,329,399 | IssuesEvent | 2022-09-22 22:48:00 | redpanda-data/redpanda | https://api.github.com/repos/redpanda-data/redpanda | closed | CI Failure in partition_balancer_scale_test | kind/bug area/redpanda area/tests ci-failure | ### Version & Environment
Redpanda version: dev
https://buildkite.com/redpanda/vtools/builds/3183#01828adc-074b-45e5-b224-1245d61997dc
```
Module: rptest.scale_tests.partition_balancer_scale_test
Class: PartitionBalancerScaleTest
Method: test_partition_balancer_with_many_partitions
Arguments:
{
"type": "big_partitions"
}
```
```
Module: rptest.scale_tests.partition_balancer_scale_test
Class: PartitionBalancerScaleTest
Method: test_partition_balancer_with_many_partitions
Arguments:
{
"type": "many_partitions"
}
```
### What went wrong?
<!--
Describe the unexpected behavior
-->
### What should have happened instead?
<!--
Describe what you wanted to happen.
-->
### How to reproduce the issue?
???
### Additional information
This looks a lot like the other `TimeoutError` failures, but I didn't see `partition_balancer_scale_test` in any of the call stacks.
```
[INFO - 2022-08-11 06:14:39,884 - runner_client - log - lineno:278]: RunnerClient: rptest.scale_tests.partition_balancer_scale_test.PartitionBalancerScaleTest.test_partition_balancer_with_many_partitions.type=big_partitions: Summary: TimeoutError('')
Traceback (most recent call last):
File "/home/ubuntu/.local/lib/python3.10/site-packages/ducktape/tests/runner_client.py", line 135, in run
data = self.run_test()
File "/home/ubuntu/.local/lib/python3.10/site-packages/ducktape/tests/runner_client.py", line 227, in run_test
return self.test_context.function(self.test)
File "/home/ubuntu/.local/lib/python3.10/site-packages/ducktape/mark/_mark.py", line 476, in wrapper
return functools.partial(f, *args, **kwargs)(*w_args, **w_kwargs)
File "/home/ubuntu/redpanda/tests/rptest/services/cluster.py", line 35, in wrapped
r = f(self, *args, **kwargs)
File "/home/ubuntu/redpanda/tests/rptest/scale_tests/partition_balancer_scale_test.py", line 147, in test_partition_balancer_with_many_partitions
self.verify()
File "/home/ubuntu/redpanda/tests/rptest/scale_tests/partition_balancer_scale_test.py", line 70, in verify
wait_until(
File "/home/ubuntu/.local/lib/python3.10/site-packages/ducktape/utils/util.py", line 58, in wait_until
raise TimeoutError(err_msg() if callable(err_msg) else err_msg) from last_exception
ducktape.errors.TimeoutError
```
| 1.0 | CI Failure in partition_balancer_scale_test - ### Version & Environment
Redpanda version: dev
https://buildkite.com/redpanda/vtools/builds/3183#01828adc-074b-45e5-b224-1245d61997dc
```
Module: rptest.scale_tests.partition_balancer_scale_test
Class: PartitionBalancerScaleTest
Method: test_partition_balancer_with_many_partitions
Arguments:
{
"type": "big_partitions"
}
```
```
Module: rptest.scale_tests.partition_balancer_scale_test
Class: PartitionBalancerScaleTest
Method: test_partition_balancer_with_many_partitions
Arguments:
{
"type": "many_partitions"
}
```
### What went wrong?
<!--
Describe the unexpected behavior
-->
### What should have happened instead?
<!--
Describe what you wanted to happen.
-->
### How to reproduce the issue?
???
### Additional information
This looks a lot like the other `TimeoutError` failures, but I didn't see `partition_balancer_scale_test` in any of the call stacks.
```
[INFO - 2022-08-11 06:14:39,884 - runner_client - log - lineno:278]: RunnerClient: rptest.scale_tests.partition_balancer_scale_test.PartitionBalancerScaleTest.test_partition_balancer_with_many_partitions.type=big_partitions: Summary: TimeoutError('')
Traceback (most recent call last):
File "/home/ubuntu/.local/lib/python3.10/site-packages/ducktape/tests/runner_client.py", line 135, in run
data = self.run_test()
File "/home/ubuntu/.local/lib/python3.10/site-packages/ducktape/tests/runner_client.py", line 227, in run_test
return self.test_context.function(self.test)
File "/home/ubuntu/.local/lib/python3.10/site-packages/ducktape/mark/_mark.py", line 476, in wrapper
return functools.partial(f, *args, **kwargs)(*w_args, **w_kwargs)
File "/home/ubuntu/redpanda/tests/rptest/services/cluster.py", line 35, in wrapped
r = f(self, *args, **kwargs)
File "/home/ubuntu/redpanda/tests/rptest/scale_tests/partition_balancer_scale_test.py", line 147, in test_partition_balancer_with_many_partitions
self.verify()
File "/home/ubuntu/redpanda/tests/rptest/scale_tests/partition_balancer_scale_test.py", line 70, in verify
wait_until(
File "/home/ubuntu/.local/lib/python3.10/site-packages/ducktape/utils/util.py", line 58, in wait_until
raise TimeoutError(err_msg() if callable(err_msg) else err_msg) from last_exception
ducktape.errors.TimeoutError
```
| non_design | ci failure in partition balancer scale test version environment redpanda version dev module rptest scale tests partition balancer scale test class partitionbalancerscaletest method test partition balancer with many partitions arguments type big partitions module rptest scale tests partition balancer scale test class partitionbalancerscaletest method test partition balancer with many partitions arguments type many partitions what went wrong describe the unexpected behavior what should have happened instead describe what you wanted to happen how to reproduce the issue additional information this looks a lot like the other timeouterror failures but i didn t see partition balancer scale test in any of the call stacks runnerclient rptest scale tests partition balancer scale test partitionbalancerscaletest test partition balancer with many partitions type big partitions summary timeouterror traceback most recent call last file home ubuntu local lib site packages ducktape tests runner client py line in run data self run test file home ubuntu local lib site packages ducktape tests runner client py line in run test return self test context function self test file home ubuntu local lib site packages ducktape mark mark py line in wrapper return functools partial f args kwargs w args w kwargs file home ubuntu redpanda tests rptest services cluster py line in wrapped r f self args kwargs file home ubuntu redpanda tests rptest scale tests partition balancer scale test py line in test partition balancer with many partitions self verify file home ubuntu redpanda tests rptest scale tests partition balancer scale test py line in verify wait until file home ubuntu local lib site packages ducktape utils util py line in wait until raise timeouterror err msg if callable err msg else err msg from last exception ducktape errors timeouterror | 0 |
62,508 | 7,606,511,517 | IssuesEvent | 2018-04-30 13:38:10 | opendatakit/docs | https://api.github.com/repos/opendatakit/docs | closed | Pull in (and edit/rewrite) XLSForm gotchas | Form design doc needed | Currently:
https://opendatakit.org/help/form-design/workarounds/
The original has a lot of organizational issues, so it really needs to be cleaned up before it is merged in here. | 1.0 | Pull in (and edit/rewrite) XLSForm gotchas - Currently:
https://opendatakit.org/help/form-design/workarounds/
The original has a lot of organizational issues, so it really needs to be cleaned up before it is merged in here. | design | pull in and edit rewrite xlsform gotchas currently the original has a lot of organizational issues so it really needs to be cleaned up before it is merged in here | 1 |
92,962 | 11,728,712,890 | IssuesEvent | 2020-03-10 18:01:53 | department-of-veterans-affairs/va.gov-team | https://api.github.com/repos/department-of-veterans-affairs/va.gov-team | opened | [Design] Connected accounts updates | design personalization-2.0 profile vsa-authenticated-exp | ## User Story
As a user who has allowed a 3rd-party application to access my VA.gov account, I need to be able to access and manage these permissions quickly and easily from VA.gov
## Additional background
Carey works with the VA API team and will be managing connected accounts going forward. She would like to make some updates for profile 2.0. We'll use this ticket to track the proposed design updates.
[Carey's Figma prototype](https://www.figma.com/proto/Za0usVKp8l80mlrsx7FaB0/Account?node-id=13%3A1690&scaling=min-zoom)
## Tasks
- [ ] Carey to share design proposals
- [ ] Iterate with team
- [ ] Settle on a final proposal
**We can create a separate ticket to get copy help from Peggy or someone else on the team*.
## Acceptance Criteria
- [ ] Carey, Tressa, and Samara are in agreement about the connected accounts direction | 1.0 | [Design] Connected accounts updates - ## User Story
As a user who has allowed a 3rd-party application to access my VA.gov account, I need to be able to access and manage these permissions quickly and easily from VA.gov
## Additional background
Carey works with the VA API team and will be managing connected accounts going forward. She would like to make some updates for profile 2.0. We'll use this ticket to track the proposed design updates.
[Carey's Figma prototype](https://www.figma.com/proto/Za0usVKp8l80mlrsx7FaB0/Account?node-id=13%3A1690&scaling=min-zoom)
## Tasks
- [ ] Carey to share design proposals
- [ ] Iterate with team
- [ ] Settle on a final proposal
**We can create a separate ticket to get copy help from Peggy or someone else on the team*.
## Acceptance Criteria
- [ ] Carey, Tressa, and Samara are in agreement about the connected accounts direction | design | connected accounts updates user story as a user who has allowed a party application to access my va gov account i need to be able to access and manage these permissions quickly and easily from va gov additional background carey works with the va api team and will be managing connected accounts going forward she would like to make some updates for profile we ll use this ticket to track the proposed design updates tasks carey to share design proposals iterate with team settle on a final proposal we can create a separate ticket to get copy help from peggy or someone else on the team acceptance criteria carey tressa and samara are in agreement about the connected accounts direction | 1 |
62,811 | 7,645,006,296 | IssuesEvent | 2018-05-08 17:11:55 | statsmodels/statsmodels | https://api.github.com/repos/statsmodels/statsmodels | opened | ENH/Design: support for unpenalized exog in fit_penalized, fit_regularized | comp-genmod design topic-penalization type-enh | related to #4608 better start_params for fit_regularized in GLM.
A common (non-machine learning) usecase for penalization/variable selection is to regularize or penalize extra variables that are not the main variables of interest.
In these cases we have a some exog that are not penalized.
The unpenalized exog can be used to get good starting values using the standard non-penalized model, E,g, in GLM we need the IRLS weights that depend on a good initial estimate on mu.
For ultra-high screening I used the resid_pearson of previous estimates to get a measure of the **additional** contribution of candidate variables to add to the model. (related would be score/LM test base on an initial model.) (IIRC I have one version of ultra-high screening (somewhere?) where users can explicitly specify a set of unpenalized, always to keep exog)
specifically:
GLM.fit_regularized alpha can be a vector with zeros for unpenalized exog. We can use the zero mask to create an intial unpenalized model for the start_params and set the start_params of the remaining variables to zero.
Similarly, my penalized/SCAD PR #4576 could use the same approach (not implemented yet) | 1.0 | ENH/Design: support for unpenalized exog in fit_penalized, fit_regularized - related to #4608 better start_params for fit_regularized in GLM.
A common (non-machine learning) usecase for penalization/variable selection is to regularize or penalize extra variables that are not the main variables of interest.
In these cases we have a some exog that are not penalized.
The unpenalized exog can be used to get good starting values using the standard non-penalized model, E,g, in GLM we need the IRLS weights that depend on a good initial estimate on mu.
For ultra-high screening I used the resid_pearson of previous estimates to get a measure of the **additional** contribution of candidate variables to add to the model. (related would be score/LM test base on an initial model.) (IIRC I have one version of ultra-high screening (somewhere?) where users can explicitly specify a set of unpenalized, always to keep exog)
specifically:
GLM.fit_regularized alpha can be a vector with zeros for unpenalized exog. We can use the zero mask to create an intial unpenalized model for the start_params and set the start_params of the remaining variables to zero.
Similarly, my penalized/SCAD PR #4576 could use the same approach (not implemented yet) | design | enh design support for unpenalized exog in fit penalized fit regularized related to better start params for fit regularized in glm a common non machine learning usecase for penalization variable selection is to regularize or penalize extra variables that are not the main variables of interest in these cases we have a some exog that are not penalized the unpenalized exog can be used to get good starting values using the standard non penalized model e g in glm we need the irls weights that depend on a good initial estimate on mu for ultra high screening i used the resid pearson of previous estimates to get a measure of the additional contribution of candidate variables to add to the model related would be score lm test base on an initial model iirc i have one version of ultra high screening somewhere where users can explicitly specify a set of unpenalized always to keep exog specifically glm fit regularized alpha can be a vector with zeros for unpenalized exog we can use the zero mask to create an intial unpenalized model for the start params and set the start params of the remaining variables to zero similarly my penalized scad pr could use the same approach not implemented yet | 1 |
58,955 | 3,098,020,944 | IssuesEvent | 2015-08-28 08:12:56 | tconsts/pefladdons | https://api.github.com/repos/tconsts/pefladdons | closed | Team strength | auto-migrated Priority-Medium Type-Improvment | ```
Поменять "сст" в Состав+ на силу игрока
относительно идеальной позиции именно на
рассматриваемой позиции.
Вывести силу выбранного состава и по
линиям в отдельности тоже.
В принципе можно сделать чтоб это попадало
и в "состав для форума"
Будет типа видно слабые стороны команды, а
так же можно будет помериться пиписьками
на форуме :)
```
Original issue reported on code.google.com by `tconsts` on 11 Nov 2010 at 12:18 | 1.0 | Team strength - ```
Поменять "сст" в Состав+ на силу игрока
относительно идеальной позиции именно на
рассматриваемой позиции.
Вывести силу выбранного состава и по
линиям в отдельности тоже.
В принципе можно сделать чтоб это попадало
и в "состав для форума"
Будет типа видно слабые стороны команды, а
так же можно будет помериться пиписьками
на форуме :)
```
Original issue reported on code.google.com by `tconsts` on 11 Nov 2010 at 12:18 | non_design | team strength поменять сст в состав на силу игрока относительно идеальной позиции именно на рассматриваемой позиции вывести силу выбранного состава и по линиям в отдельности тоже в принципе можно сделать чтоб это попадало и в состав для форума будет типа видно слабые стороны команды а так же можно будет помериться пиписьками на форуме original issue reported on code google com by tconsts on nov at | 0 |
28,683 | 7,017,156,542 | IssuesEvent | 2017-12-21 08:28:34 | jOOQ/jOOQ | https://api.github.com/repos/jOOQ/jOOQ | closed | Add integration test for <forcedType/> applied to table valued function result | C: Code Generation P: Medium R: Fixed T: Task | We don't have a test for this yet, only for `<forcedType/>` applied to function parameters. If there's a problem, this issue will turn into a defect. | 1.0 | Add integration test for <forcedType/> applied to table valued function result - We don't have a test for this yet, only for `<forcedType/>` applied to function parameters. If there's a problem, this issue will turn into a defect. | non_design | add integration test for applied to table valued function result we don t have a test for this yet only for applied to function parameters if there s a problem this issue will turn into a defect | 0 |
318,985 | 27,336,951,462 | IssuesEvent | 2023-02-26 10:33:31 | spring-projects-experimental/spring-modulith | https://api.github.com/repos/spring-projects-experimental/spring-modulith | closed | Default to await termination of task executors unless configured | in: events in: test support type: enhancement | Especially in integration tests of long-running application module listener invocations, we can run into the situation that the context already initiates the shutdown, while a listener is still running. A successful execution of a listener will result in trying to mark the event publication completed, and effectively access database resources already shut down.
This can be worked around by configuring the task executor to await termination and setting an await termination period. It makes sense to enable this by default. We should provide an explicit flag to disable this and defensively back off if any of the Spring Boot properties for the executor shutdown is configured explicitly by the user. | 1.0 | Default to await termination of task executors unless configured - Especially in integration tests of long-running application module listener invocations, we can run into the situation that the context already initiates the shutdown, while a listener is still running. A successful execution of a listener will result in trying to mark the event publication completed, and effectively access database resources already shut down.
This can be worked around by configuring the task executor to await termination and setting an await termination period. It makes sense to enable this by default. We should provide an explicit flag to disable this and defensively back off if any of the Spring Boot properties for the executor shutdown is configured explicitly by the user. | non_design | default to await termination of task executors unless configured especially in integration tests of long running application module listener invocations we can run into the situation that the context already initiates the shutdown while a listener is still running a successful execution of a listener will result in trying to mark the event publication completed and effectively access database resources already shut down this can be worked around by configuring the task executor to await termination and setting an await termination period it makes sense to enable this by default we should provide an explicit flag to disable this and defensively back off if any of the spring boot properties for the executor shutdown is configured explicitly by the user | 0 |
8,629 | 10,578,839,981 | IssuesEvent | 2019-10-08 00:12:44 | thedarkcolour/Future-MC | https://api.github.com/repos/thedarkcolour/Future-MC | closed | 1.15 addon crash with Cubic Chunks mod? | bug compatibility upcoming fix | 0.1.11 seems to crash with cubic chunks instaled?
As the 0.1.10 had no problems I tried disabling the 1.15 stuff in the config file, and this removed the crash problem. so it seems the problem is related to 1.15 addons.
[crash-2019-09-25_00.01.06-client.txt](https://github.com/thedarkcolour/Future-MC/files/3649743/crash-2019-09-25_00.01.06-client.txt)
| True | 1.15 addon crash with Cubic Chunks mod? - 0.1.11 seems to crash with cubic chunks instaled?
As the 0.1.10 had no problems I tried disabling the 1.15 stuff in the config file, and this removed the crash problem. so it seems the problem is related to 1.15 addons.
[crash-2019-09-25_00.01.06-client.txt](https://github.com/thedarkcolour/Future-MC/files/3649743/crash-2019-09-25_00.01.06-client.txt)
| non_design | addon crash with cubic chunks mod seems to crash with cubic chunks instaled as the had no problems i tried disabling the stuff in the config file and this removed the crash problem so it seems the problem is related to addons | 0 |
432,992 | 12,501,044,453 | IssuesEvent | 2020-06-02 00:02:47 | tiwaz1994/DynamicBulwarks | https://api.github.com/repos/tiwaz1994/DynamicBulwarks | closed | Prettify the lobby, remove ability to equip yourself | Feature Request High Priority | The current lobby platform and initial bulwark was just a convenience for testing/setup, but it should be formalized:
1. Make it pretty - more like a proper staging area.
2. Remove the ability to equip yourself from the bulwark itself. | 1.0 | Prettify the lobby, remove ability to equip yourself - The current lobby platform and initial bulwark was just a convenience for testing/setup, but it should be formalized:
1. Make it pretty - more like a proper staging area.
2. Remove the ability to equip yourself from the bulwark itself. | non_design | prettify the lobby remove ability to equip yourself the current lobby platform and initial bulwark was just a convenience for testing setup but it should be formalized make it pretty more like a proper staging area remove the ability to equip yourself from the bulwark itself | 0 |
804,724 | 29,498,499,539 | IssuesEvent | 2023-06-02 19:13:49 | zephyrproject-rtos/zephyr | https://api.github.com/repos/zephyrproject-rtos/zephyr | closed | [Coverity CID: 316518] Out-of-bounds access in subsys/net/lib/coap/coap.c | bug priority: medium area: Networking Coverity |
Static code scan issues found in file:
https://github.com/zephyrproject-rtos/zephyr/tree/dae79cefaabf63086946a48ccca4094f26f146c8/subsys/net/lib/coap/coap.c
Category: Memory - corruptions
Function: `coap_reply_init`
Component: Networking
CID: [316518](https://scan9.scan.coverity.com/reports.htm#v29726/p12996/mergedDefectId=316518)
Details:
https://github.com/zephyrproject-rtos/zephyr/blob/dae79cefaabf63086946a48ccca4094f26f146c8/subsys/net/lib/coap/coap.c#L1506
Please fix or provide comments in coverity using the link:
https://scan9.scan.coverity.com/reports.htm#v29271/p12996.
For more information about the violation, check the [Coverity Reference](https://scan9.scan.coverity.com/doc/en/cov_checker_ref.html#static_checker_OVERRUN). ([CWE-119](http://cwe.mitre.org/data/definitions/119.html))
Note: This issue was created automatically. Priority was set based on classification
of the file affected and the impact field in coverity. Assignees were set using the CODEOWNERS file.
| 1.0 | [Coverity CID: 316518] Out-of-bounds access in subsys/net/lib/coap/coap.c -
Static code scan issues found in file:
https://github.com/zephyrproject-rtos/zephyr/tree/dae79cefaabf63086946a48ccca4094f26f146c8/subsys/net/lib/coap/coap.c
Category: Memory - corruptions
Function: `coap_reply_init`
Component: Networking
CID: [316518](https://scan9.scan.coverity.com/reports.htm#v29726/p12996/mergedDefectId=316518)
Details:
https://github.com/zephyrproject-rtos/zephyr/blob/dae79cefaabf63086946a48ccca4094f26f146c8/subsys/net/lib/coap/coap.c#L1506
Please fix or provide comments in coverity using the link:
https://scan9.scan.coverity.com/reports.htm#v29271/p12996.
For more information about the violation, check the [Coverity Reference](https://scan9.scan.coverity.com/doc/en/cov_checker_ref.html#static_checker_OVERRUN). ([CWE-119](http://cwe.mitre.org/data/definitions/119.html))
Note: This issue was created automatically. Priority was set based on classification
of the file affected and the impact field in coverity. Assignees were set using the CODEOWNERS file.
| non_design | out of bounds access in subsys net lib coap coap c static code scan issues found in file category memory corruptions function coap reply init component networking cid details please fix or provide comments in coverity using the link for more information about the violation check the note this issue was created automatically priority was set based on classification of the file affected and the impact field in coverity assignees were set using the codeowners file | 0 |
500,847 | 14,516,157,770 | IssuesEvent | 2020-12-13 15:00:20 | amplication/amplication | https://api.github.com/repos/amplication/amplication | closed | Data Service Generator: Improve structure of generated app code | priority: low type: feature request | **Is your feature request related to a problem? Please describe.**
Currently, all files are saved to the root directory
**Describe the solution you'd like**
The application code should be saved to the src directory.
Built code should not be included.
| 1.0 | Data Service Generator: Improve structure of generated app code - **Is your feature request related to a problem? Please describe.**
Currently, all files are saved to the root directory
**Describe the solution you'd like**
The application code should be saved to the src directory.
Built code should not be included.
| non_design | data service generator improve structure of generated app code is your feature request related to a problem please describe currently all files are saved to the root directory describe the solution you d like the application code should be saved to the src directory built code should not be included | 0 |
231,426 | 25,499,189,403 | IssuesEvent | 2022-11-28 01:16:27 | samq-wsdemo/NodeGoat | https://api.github.com/repos/samq-wsdemo/NodeGoat | opened | CVE-2022-24999 (Medium) detected in multiple libraries | security vulnerability | ## CVE-2022-24999 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>qs-6.10.1.tgz</b>, <b>qs-6.3.2.tgz</b>, <b>qs-6.5.2.tgz</b>, <b>qs-6.7.0.tgz</b>, <b>qs-5.2.1.tgz</b>, <b>qs-6.2.1.tgz</b></p></summary>
<p>
<details><summary><b>qs-6.10.1.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.10.1.tgz">https://registry.npmjs.org/qs/-/qs-6.10.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- grunt-contrib-watch-1.1.0.tgz (Root Library)
- tiny-lr-1.1.1.tgz
- :x: **qs-6.10.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-6.3.2.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.3.2.tgz">https://registry.npmjs.org/qs/-/qs-6.3.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/coveralls/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- foreground-child-1.5.3.tgz (Root Library)
- grunt-contrib-nodeunit-1.0.0.tgz
- nodeunit-0.9.5.tgz
- tap-7.1.2.tgz
- coveralls-2.13.3.tgz
- request-2.79.0.tgz
- :x: **qs-6.3.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-6.5.2.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.5.2.tgz">https://registry.npmjs.org/qs/-/qs-6.5.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/request/node_modules/qs/package.json,/node_modules/cypress/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- cypress-3.8.3.tgz (Root Library)
- request-2.88.0.tgz
- :x: **qs-6.5.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-6.7.0.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.7.0.tgz">https://registry.npmjs.org/qs/-/qs-6.7.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/body-parser/node_modules/qs/package.json,/node_modules/express/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- body-parser-1.19.0.tgz (Root Library)
- :x: **qs-6.7.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-5.2.1.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-5.2.1.tgz">https://registry.npmjs.org/qs/-/qs-5.2.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/grunt-retire/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- grunt-retire-0.3.12.tgz (Root Library)
- request-2.67.0.tgz
- :x: **qs-5.2.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-6.2.1.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.2.1.tgz">https://registry.npmjs.org/qs/-/qs-6.2.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/request/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- :x: **qs-6.2.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/samq-wsdemo/NodeGoat/commit/4cddc2d15630da8f1806b8b98b45b987fbb3a397">4cddc2d15630da8f1806b8b98b45b987fbb3a397</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
<p>Publish Date: 2022-11-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-24999>CVE-2022-24999</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-24999">https://www.cve.org/CVERecord?id=CVE-2022-24999</a></p>
<p>Release Date: 2022-11-26</p>
<p>Fix Resolution: qs - 6.2.4,6.3.3,6.4.1,6.5.3,6.6.1,6.7.3,6.8.3,6.9.7,6.10.3</p>
</p>
</details>
<p></p>
| True | CVE-2022-24999 (Medium) detected in multiple libraries - ## CVE-2022-24999 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>qs-6.10.1.tgz</b>, <b>qs-6.3.2.tgz</b>, <b>qs-6.5.2.tgz</b>, <b>qs-6.7.0.tgz</b>, <b>qs-5.2.1.tgz</b>, <b>qs-6.2.1.tgz</b></p></summary>
<p>
<details><summary><b>qs-6.10.1.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.10.1.tgz">https://registry.npmjs.org/qs/-/qs-6.10.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- grunt-contrib-watch-1.1.0.tgz (Root Library)
- tiny-lr-1.1.1.tgz
- :x: **qs-6.10.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-6.3.2.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.3.2.tgz">https://registry.npmjs.org/qs/-/qs-6.3.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/coveralls/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- foreground-child-1.5.3.tgz (Root Library)
- grunt-contrib-nodeunit-1.0.0.tgz
- nodeunit-0.9.5.tgz
- tap-7.1.2.tgz
- coveralls-2.13.3.tgz
- request-2.79.0.tgz
- :x: **qs-6.3.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-6.5.2.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.5.2.tgz">https://registry.npmjs.org/qs/-/qs-6.5.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/request/node_modules/qs/package.json,/node_modules/cypress/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- cypress-3.8.3.tgz (Root Library)
- request-2.88.0.tgz
- :x: **qs-6.5.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-6.7.0.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.7.0.tgz">https://registry.npmjs.org/qs/-/qs-6.7.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/body-parser/node_modules/qs/package.json,/node_modules/express/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- body-parser-1.19.0.tgz (Root Library)
- :x: **qs-6.7.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-5.2.1.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-5.2.1.tgz">https://registry.npmjs.org/qs/-/qs-5.2.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/grunt-retire/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- grunt-retire-0.3.12.tgz (Root Library)
- request-2.67.0.tgz
- :x: **qs-5.2.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-6.2.1.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.2.1.tgz">https://registry.npmjs.org/qs/-/qs-6.2.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/request/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- :x: **qs-6.2.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/samq-wsdemo/NodeGoat/commit/4cddc2d15630da8f1806b8b98b45b987fbb3a397">4cddc2d15630da8f1806b8b98b45b987fbb3a397</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
<p>Publish Date: 2022-11-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-24999>CVE-2022-24999</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-24999">https://www.cve.org/CVERecord?id=CVE-2022-24999</a></p>
<p>Release Date: 2022-11-26</p>
<p>Fix Resolution: qs - 6.2.4,6.3.3,6.4.1,6.5.3,6.6.1,6.7.3,6.8.3,6.9.7,6.10.3</p>
</p>
</details>
<p></p>
| non_design | cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries qs tgz qs tgz qs tgz qs tgz qs tgz qs tgz qs tgz a querystring parser that supports nesting and arrays with a depth limit library home page a href path to dependency file package json path to vulnerable library node modules qs package json dependency hierarchy grunt contrib watch tgz root library tiny lr tgz x qs tgz vulnerable library qs tgz a querystring parser that supports nesting and arrays with a depth limit library home page a href path to dependency file package json path to vulnerable library node modules coveralls node modules qs package json dependency hierarchy foreground child tgz root library grunt contrib nodeunit tgz nodeunit tgz tap tgz coveralls tgz request tgz x qs tgz vulnerable library qs tgz a querystring parser that supports nesting and arrays with a depth limit library home page a href path to dependency file package json path to vulnerable library node modules request node modules qs package json node modules cypress node modules qs package json dependency hierarchy cypress tgz root library request tgz x qs tgz vulnerable library qs tgz a querystring parser that supports nesting and arrays with a depth limit library home page a href path to dependency file package json path to vulnerable library node modules body parser node modules qs package json node modules express node modules qs package json dependency hierarchy body parser tgz root library x qs tgz vulnerable library qs tgz a querystring parser that supports nesting and arrays with a depth limit library home page a href path to dependency file package json path to vulnerable library node modules grunt retire node modules qs package json dependency hierarchy grunt retire tgz root library request tgz x qs tgz vulnerable library qs tgz a querystring parser that supports nesting and arrays with a depth limit library home page a href path to dependency file package json path to vulnerable library node modules npm node modules request node modules qs package json dependency hierarchy grunt npm install tgz root library npm tgz request tgz x qs tgz vulnerable library found in head commit a href found in base branch master vulnerability details qs before as used in express before and other products allows attackers to cause a node process hang for an express application because an proto key can be used in many typical express use cases an unauthenticated remote attacker can place the attack payload in the query string of the url that is used to visit the application such as a b a a the fix was backported to qs and and therefore express which has deps qs in its release description is not vulnerable publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution qs | 0 |
714,261 | 24,555,977,404 | IssuesEvent | 2022-10-12 15:53:59 | eBay/skin | https://api.github.com/repos/eBay/skin | closed | Tourtip: add optional index and "next" button | type: feature priority: 3 module: tourtip | We've updated the tour tip component with more properties, flexibility, and guidelines. An idea is being added, the title is being increased in size, and actions are added along with a smaller close icon.
DOD: Tourtip component matches [Playbook](https://playbook.corp.ebay.com/PlaybookApp#/executional-guidelines/product-design-system/patterns/tourtips) and [Figma](https://www.figma.com/file/zEBdEhbonrBOGzZ0fXzWvM/?node-id=54797%3A88595)
| 1.0 | Tourtip: add optional index and "next" button - We've updated the tour tip component with more properties, flexibility, and guidelines. An idea is being added, the title is being increased in size, and actions are added along with a smaller close icon.
DOD: Tourtip component matches [Playbook](https://playbook.corp.ebay.com/PlaybookApp#/executional-guidelines/product-design-system/patterns/tourtips) and [Figma](https://www.figma.com/file/zEBdEhbonrBOGzZ0fXzWvM/?node-id=54797%3A88595)
| non_design | tourtip add optional index and next button we ve updated the tour tip component with more properties flexibility and guidelines an idea is being added the title is being increased in size and actions are added along with a smaller close icon dod tourtip component matches and | 0 |
176,798 | 28,209,117,922 | IssuesEvent | 2023-04-05 01:31:47 | Zhuinden/simple-stack-compose-integration | https://api.github.com/repos/Zhuinden/simple-stack-compose-integration | closed | Question: Multiple compose backstacks supported | question design required user support | I don't see any examples regarding this. Is simple-stack-compose-integration designed with multiple compose backstack support? For example, I'd like an outer backstack closer to the activity level and I'd also like a backstack contained within a BottomSheetScaffold. Before I spend time on a sizeable prototype I was hoping you could either say yes, no, or maybe yes with caveats. This will be greenfield development, no fragments, views, etc. | 1.0 | Question: Multiple compose backstacks supported - I don't see any examples regarding this. Is simple-stack-compose-integration designed with multiple compose backstack support? For example, I'd like an outer backstack closer to the activity level and I'd also like a backstack contained within a BottomSheetScaffold. Before I spend time on a sizeable prototype I was hoping you could either say yes, no, or maybe yes with caveats. This will be greenfield development, no fragments, views, etc. | design | question multiple compose backstacks supported i don t see any examples regarding this is simple stack compose integration designed with multiple compose backstack support for example i d like an outer backstack closer to the activity level and i d also like a backstack contained within a bottomsheetscaffold before i spend time on a sizeable prototype i was hoping you could either say yes no or maybe yes with caveats this will be greenfield development no fragments views etc | 1 |
17,713 | 3,362,620,657 | IssuesEvent | 2015-11-20 07:26:10 | pypa/warehouse | https://api.github.com/repos/pypa/warehouse | closed | Recruit users for usability testing | design usability | I'd like to conduct some basic remote usability testing on the new design prior to relaunch.
For this, we will need to recruit a number of community members to participate in usability testing sessions. Ideally, the users would come from a variety of backgrounds and be at different levels of expertise, e.g:
* Absolute beginners who are new to the Python ecosystem and have never used PyPI
* Users who have never created a package for PyPI
* Intermediate users who are familiar with PyPI but only use it occasionally
* Power users who are intimate with PyPI
Volunteers will need to be:
* Available for up to one hour in late November (date TBC)
* Fluent in English
* Using a fast enough internet connection to run Google Hangouts with screen sharing enabled
* Happy to have their user session recorded
* Located in a timezone compatible with GMT
The goal of the sessions will be to identify any major usability problems with the new design.
Participants will be formally credited on the credits page when the new version of PyPI is launched.
If you would like to participate in the user testing, please **do not comment here** - instead, please submit your details at http://bit.ly/1MpAHRm
If you have any experience in conducting or facilitating usability sessions, I would appreciate your input, comments or suggestions below. | 1.0 | Recruit users for usability testing - I'd like to conduct some basic remote usability testing on the new design prior to relaunch.
For this, we will need to recruit a number of community members to participate in usability testing sessions. Ideally, the users would come from a variety of backgrounds and be at different levels of expertise, e.g:
* Absolute beginners who are new to the Python ecosystem and have never used PyPI
* Users who have never created a package for PyPI
* Intermediate users who are familiar with PyPI but only use it occasionally
* Power users who are intimate with PyPI
Volunteers will need to be:
* Available for up to one hour in late November (date TBC)
* Fluent in English
* Using a fast enough internet connection to run Google Hangouts with screen sharing enabled
* Happy to have their user session recorded
* Located in a timezone compatible with GMT
The goal of the sessions will be to identify any major usability problems with the new design.
Participants will be formally credited on the credits page when the new version of PyPI is launched.
If you would like to participate in the user testing, please **do not comment here** - instead, please submit your details at http://bit.ly/1MpAHRm
If you have any experience in conducting or facilitating usability sessions, I would appreciate your input, comments or suggestions below. | design | recruit users for usability testing i d like to conduct some basic remote usability testing on the new design prior to relaunch for this we will need to recruit a number of community members to participate in usability testing sessions ideally the users would come from a variety of backgrounds and be at different levels of expertise e g absolute beginners who are new to the python ecosystem and have never used pypi users who have never created a package for pypi intermediate users who are familiar with pypi but only use it occasionally power users who are intimate with pypi volunteers will need to be available for up to one hour in late november date tbc fluent in english using a fast enough internet connection to run google hangouts with screen sharing enabled happy to have their user session recorded located in a timezone compatible with gmt the goal of the sessions will be to identify any major usability problems with the new design participants will be formally credited on the credits page when the new version of pypi is launched if you would like to participate in the user testing please do not comment here instead please submit your details at if you have any experience in conducting or facilitating usability sessions i would appreciate your input comments or suggestions below | 1 |
183,757 | 31,761,245,016 | IssuesEvent | 2023-09-12 05:24:31 | appsmithorg/appsmith | https://api.github.com/repos/appsmithorg/appsmith | closed | [Epic]: Category token developement | Design System Pod Epic ADS Category Token | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### SubTasks
_No response_
```[tasklist]
### Tasks
- [ ] https://github.com/appsmithorg/appsmith/issues/24525
- [ ] https://github.com/appsmithorg/appsmith/issues/24526
- [ ] https://github.com/appsmithorg/appsmith/issues/24527
- [ ] https://github.com/appsmithorg/appsmith/issues/24528
- [ ] https://github.com/appsmithorg/appsmith/issues/24529
- [ ] https://github.com/appsmithorg/appsmith/issues/24530
- [ ] https://github.com/appsmithorg/appsmith/issues/24531
- [ ] https://github.com/appsmithorg/appsmith/issues/24532
- [ ] https://github.com/appsmithorg/appsmith/issues/24533
- [ ] https://github.com/appsmithorg/appsmith/issues/24534
- [ ] https://github.com/appsmithorg/appsmith/issues/24535
- [ ] https://github.com/appsmithorg/appsmith/issues/24536
- [ ] https://github.com/appsmithorg/appsmith/issues/24537
- [ ] https://github.com/appsmithorg/appsmith/issues/24538
- [ ] https://github.com/appsmithorg/appsmith/issues/24539
- [ ] https://github.com/appsmithorg/appsmith/issues/24540
- [ ] https://github.com/appsmithorg/appsmith/issues/24541
- [ ] https://github.com/appsmithorg/appsmith/issues/24542
- [ ] https://github.com/appsmithorg/appsmith/issues/24543
- [ ] https://github.com/appsmithorg/appsmith/issues/24544
- [ ] https://github.com/appsmithorg/appsmith/issues/24545
- [ ] https://github.com/appsmithorg/appsmith/issues/24546
- [ ] https://github.com/appsmithorg/appsmith/issues/24547
- [ ] https://github.com/appsmithorg/appsmith/issues/24548
- [ ] https://github.com/appsmithorg/appsmith/issues/24549
- [ ] https://github.com/appsmithorg/appsmith/issues/24550
- [ ] https://github.com/appsmithorg/appsmith/issues/24551
- [ ] https://github.com/appsmithorg/appsmith/issues/24552
- [ ] https://github.com/appsmithorg/appsmith/issues/24553
- [ ] https://github.com/appsmithorg/appsmith/issues/24554
```
| 1.0 | [Epic]: Category token developement - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### SubTasks
_No response_
```[tasklist]
### Tasks
- [ ] https://github.com/appsmithorg/appsmith/issues/24525
- [ ] https://github.com/appsmithorg/appsmith/issues/24526
- [ ] https://github.com/appsmithorg/appsmith/issues/24527
- [ ] https://github.com/appsmithorg/appsmith/issues/24528
- [ ] https://github.com/appsmithorg/appsmith/issues/24529
- [ ] https://github.com/appsmithorg/appsmith/issues/24530
- [ ] https://github.com/appsmithorg/appsmith/issues/24531
- [ ] https://github.com/appsmithorg/appsmith/issues/24532
- [ ] https://github.com/appsmithorg/appsmith/issues/24533
- [ ] https://github.com/appsmithorg/appsmith/issues/24534
- [ ] https://github.com/appsmithorg/appsmith/issues/24535
- [ ] https://github.com/appsmithorg/appsmith/issues/24536
- [ ] https://github.com/appsmithorg/appsmith/issues/24537
- [ ] https://github.com/appsmithorg/appsmith/issues/24538
- [ ] https://github.com/appsmithorg/appsmith/issues/24539
- [ ] https://github.com/appsmithorg/appsmith/issues/24540
- [ ] https://github.com/appsmithorg/appsmith/issues/24541
- [ ] https://github.com/appsmithorg/appsmith/issues/24542
- [ ] https://github.com/appsmithorg/appsmith/issues/24543
- [ ] https://github.com/appsmithorg/appsmith/issues/24544
- [ ] https://github.com/appsmithorg/appsmith/issues/24545
- [ ] https://github.com/appsmithorg/appsmith/issues/24546
- [ ] https://github.com/appsmithorg/appsmith/issues/24547
- [ ] https://github.com/appsmithorg/appsmith/issues/24548
- [ ] https://github.com/appsmithorg/appsmith/issues/24549
- [ ] https://github.com/appsmithorg/appsmith/issues/24550
- [ ] https://github.com/appsmithorg/appsmith/issues/24551
- [ ] https://github.com/appsmithorg/appsmith/issues/24552
- [ ] https://github.com/appsmithorg/appsmith/issues/24553
- [ ] https://github.com/appsmithorg/appsmith/issues/24554
```
| design | category token developement is there an existing issue for this i have searched the existing issues subtasks no response tasks | 1 |
81,151 | 10,110,072,559 | IssuesEvent | 2019-07-30 09:27:02 | Automattic/wp-calypso | https://api.github.com/repos/Automattic/wp-calypso | closed | Android Post Image Editor: usability bugs | Design Mobile | Issue lives here https://github.com/wordpress-mobile/WordPress-Android/issues/8416
#### Steps to reproduce
1. Edit a post
2. Add an image
3. tap on the image
#### What I expected
Clear actions to confirm or reject the changes
#### What happened instead
- The top right contains a negative action (remove image)
- The top left has an 'x' which closes the view, and is actually the positive action
#### Browser / OS version
#### Screenshot / Video
#### Context / Source
Found on our mobile groundskeeping board
This definitely has some usability issues. The behaviours are also completely different on iOS and Android
Seems like something I can design in a day, and get on a team's backlog to build.
<!--
PLEASE NOTE
- These comments won't show up when you submit the issue.
- Everything is optional, but try to add as many details as possible.
Docs & troubleshooting:
https://github.com/Automattic/wp-calypso/blob/master/.github/CONTRIBUTING.md
https://github.com/Automattic/wp-calypso/blob/master/docs/troubleshooting.md
Helpful tips for screenshots:
https://en.support.wordpress.com/make-a-screenshot/
-->
| 1.0 | Android Post Image Editor: usability bugs - Issue lives here https://github.com/wordpress-mobile/WordPress-Android/issues/8416
#### Steps to reproduce
1. Edit a post
2. Add an image
3. tap on the image
#### What I expected
Clear actions to confirm or reject the changes
#### What happened instead
- The top right contains a negative action (remove image)
- The top left has an 'x' which closes the view, and is actually the positive action
#### Browser / OS version
#### Screenshot / Video
#### Context / Source
Found on our mobile groundskeeping board
This definitely has some usability issues. The behaviours are also completely different on iOS and Android
Seems like something I can design in a day, and get on a team's backlog to build.
<!--
PLEASE NOTE
- These comments won't show up when you submit the issue.
- Everything is optional, but try to add as many details as possible.
Docs & troubleshooting:
https://github.com/Automattic/wp-calypso/blob/master/.github/CONTRIBUTING.md
https://github.com/Automattic/wp-calypso/blob/master/docs/troubleshooting.md
Helpful tips for screenshots:
https://en.support.wordpress.com/make-a-screenshot/
-->
| design | android post image editor usability bugs issue lives here steps to reproduce edit a post add an image tap on the image what i expected clear actions to confirm or reject the changes what happened instead the top right contains a negative action remove image the top left has an x which closes the view and is actually the positive action browser os version screenshot video context source found on our mobile groundskeeping board this definitely has some usability issues the behaviours are also completely different on ios and android seems like something i can design in a day and get on a team s backlog to build please note these comments won t show up when you submit the issue everything is optional but try to add as many details as possible docs troubleshooting helpful tips for screenshots | 1 |
309,841 | 23,307,461,493 | IssuesEvent | 2022-08-08 03:45:30 | stoneatom/stonedb | https://api.github.com/repos/stoneatom/stonedb | closed | bug: Pictures width exceeds content area in docs site. | A-bug A-documentation | ### Describe the problem
for example:
https://stonedb.io/docs/O&M-Guide/monitoring-and-alerting/prometheus+grafana-monitor/
For all the contents in the document that contain pictures, the width of the pictures exceeds the content area.
### Expected behavior
The width of the picture can be automatically adapted.
### How To Reproduce
See this page：https://stonedb.io/docs/O&M-Guide/monitoring-and-alerting/prometheus+grafana-monitor/
### Environment
_No response_
### Are you interested in submitting a PR to solve the problem?
- [X] Yes, I will! | 1.0 | bug: Pictures width exceeds content area in docs site. - ### Describe the problem
for example:
https://stonedb.io/docs/O&M-Guide/monitoring-and-alerting/prometheus+grafana-monitor/
For all the contents in the document that contain pictures, the width of the pictures exceeds the content area.
### Expected behavior
The width of the picture can be automatically adapted.
### How To Reproduce
See this page：https://stonedb.io/docs/O&M-Guide/monitoring-and-alerting/prometheus+grafana-monitor/
### Environment
_No response_
### Are you interested in submitting a PR to solve the problem?
- [X] Yes, I will! | non_design | bug pictures width exceeds content area in docs site describe the problem for example for all the contents in the document that contain pictures the width of the pictures exceeds the content area expected behavior the width of the picture can be automatically adapted how to reproduce see this page： environment no response are you interested in submitting a pr to solve the problem yes i will | 0 |
161,759 | 20,155,331,967 | IssuesEvent | 2022-02-09 15:58:28 | kapseliboi/Node-Data | https://api.github.com/repos/kapseliboi/Node-Data | opened | CVE-2018-3721 (Medium) detected in multiple libraries | security vulnerability | ## CVE-2018-3721 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>lodash-1.0.2.tgz</b>, <b>lodash-4.12.0.tgz</b>, <b>lodash-3.10.1.tgz</b></p></summary>
<p>
<details><summary><b>lodash-1.0.2.tgz</b></p></summary>
<p>A utility library delivering consistency, customization, performance, and extras.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-1.0.2.tgz">https://registry.npmjs.org/lodash/-/lodash-1.0.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/globule/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- gulp-3.9.0.tgz (Root Library)
- vinyl-fs-0.3.14.tgz
- glob-watcher-0.0.6.tgz
- gaze-0.5.2.tgz
- globule-0.1.0.tgz
- :x: **lodash-1.0.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-4.12.0.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.12.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.12.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/sequelize/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- sequelize-3.23.2.tgz (Root Library)
- :x: **lodash-4.12.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-3.10.1.tgz</b></p></summary>
<p>The modern build of lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz">https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- elasticsearch-10.1.3.tgz (Root Library)
- :x: **lodash-3.10.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/kapseliboi/Node-Data/commit/289c77565fc637d4c0e4bf4a9a1e81df96cd190a">289c77565fc637d4c0e4bf4a9a1e81df96cd190a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3721>CVE-2018-3721</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-3721">https://nvd.nist.gov/vuln/detail/CVE-2018-3721</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution (lodash): 4.17.5</p>
<p>Direct dependency fix Resolution (gulp): 4.0.0</p><p>Fix Resolution (lodash): 4.17.5</p>
<p>Direct dependency fix Resolution (sequelize): 3.33.0</p><p>Fix Resolution (lodash): 4.17.5</p>
<p>Direct dependency fix Resolution (elasticsearch): 12.0.0-rc1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-3721 (Medium) detected in multiple libraries - ## CVE-2018-3721 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>lodash-1.0.2.tgz</b>, <b>lodash-4.12.0.tgz</b>, <b>lodash-3.10.1.tgz</b></p></summary>
<p>
<details><summary><b>lodash-1.0.2.tgz</b></p></summary>
<p>A utility library delivering consistency, customization, performance, and extras.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-1.0.2.tgz">https://registry.npmjs.org/lodash/-/lodash-1.0.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/globule/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- gulp-3.9.0.tgz (Root Library)
- vinyl-fs-0.3.14.tgz
- glob-watcher-0.0.6.tgz
- gaze-0.5.2.tgz
- globule-0.1.0.tgz
- :x: **lodash-1.0.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-4.12.0.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.12.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.12.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/sequelize/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- sequelize-3.23.2.tgz (Root Library)
- :x: **lodash-4.12.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-3.10.1.tgz</b></p></summary>
<p>The modern build of lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz">https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- elasticsearch-10.1.3.tgz (Root Library)
- :x: **lodash-3.10.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/kapseliboi/Node-Data/commit/289c77565fc637d4c0e4bf4a9a1e81df96cd190a">289c77565fc637d4c0e4bf4a9a1e81df96cd190a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3721>CVE-2018-3721</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-3721">https://nvd.nist.gov/vuln/detail/CVE-2018-3721</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution (lodash): 4.17.5</p>
<p>Direct dependency fix Resolution (gulp): 4.0.0</p><p>Fix Resolution (lodash): 4.17.5</p>
<p>Direct dependency fix Resolution (sequelize): 3.33.0</p><p>Fix Resolution (lodash): 4.17.5</p>
<p>Direct dependency fix Resolution (elasticsearch): 12.0.0-rc1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries lodash tgz lodash tgz lodash tgz lodash tgz a utility library delivering consistency customization performance and extras library home page a href path to dependency file package json path to vulnerable library node modules globule node modules lodash package json dependency hierarchy gulp tgz root library vinyl fs tgz glob watcher tgz gaze tgz globule tgz x lodash tgz vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file package json path to vulnerable library node modules sequelize node modules lodash package json dependency hierarchy sequelize tgz root library x lodash tgz vulnerable library lodash tgz the modern build of lodash modular utilities library home page a href path to dependency file package json path to vulnerable library node modules lodash package json dependency hierarchy elasticsearch tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details lodash node module before suffers from a modification of assumed immutable data maid vulnerability via defaultsdeep merge and mergewith functions which allows a malicious user to modify the prototype of object via proto causing the addition or modification of an existing property that will exist on all objects publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash direct dependency fix resolution gulp fix resolution lodash direct dependency fix resolution sequelize fix resolution lodash direct dependency fix resolution elasticsearch step up your open source security game with whitesource | 0 |
80,591 | 10,025,869,813 | IssuesEvent | 2019-07-17 04:14:07 | gitcoinco/web | https://api.github.com/repos/gitcoinco/web | closed | Metamask requests fee payment when funds aren't available | bug design to bounty | **Describe the bug**
If a user doesn't have enough funds in their account to pay for the bounty, the user is still prompted to pay the fee associated with posting.
https://gyazo.com/80f9acc058a4348aca9eea296664a597
**Expected behavior**
If a user does not have enough funds in their account Metamask should not prompt the user and they should instead be asked only to refill their account, to avoid users paying fees for failed bounties.
| 1.0 | Metamask requests fee payment when funds aren't available - **Describe the bug**
If a user doesn't have enough funds in their account to pay for the bounty, the user is still prompted to pay the fee associated with posting.
https://gyazo.com/80f9acc058a4348aca9eea296664a597
**Expected behavior**
If a user does not have enough funds in their account Metamask should not prompt the user and they should instead be asked only to refill their account, to avoid users paying fees for failed bounties.
| design | metamask requests fee payment when funds aren t available describe the bug if a user doesn t have enough funds in their account to pay for the bounty the user is still prompted to pay the fee associated with posting expected behavior if a user does not have enough funds in their account metamask should not prompt the user and they should instead be asked only to refill their account to avoid users paying fees for failed bounties | 1 |
52,610 | 13,018,269,627 | IssuesEvent | 2020-07-26 16:30:33 | apache/incubator-mxnet | https://api.github.com/repos/apache/incubator-mxnet | closed | Outdated mxnet nightly build wheel instructions | Bug Build Installation | The mxnet nightly pip wheel instructions are outdated. The latest wheels are available at https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/index.html
Shall we update the website with this link? Or maybe at least the static links to latest builds | 1.0 | Outdated mxnet nightly build wheel instructions - The mxnet nightly pip wheel instructions are outdated. The latest wheels are available at https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/index.html
Shall we update the website with this link? Or maybe at least the static links to latest builds | non_design | outdated mxnet nightly build wheel instructions the mxnet nightly pip wheel instructions are outdated the latest wheels are available at shall we update the website with this link or maybe at least the static links to latest builds | 0 |
115,425 | 24,762,865,739 | IssuesEvent | 2022-10-22 05:51:13 | log2timeline/plaso | https://api.github.com/repos/log2timeline/plaso | closed | refactor usbstor winreg plugin | enhancement parsers analysis code health | **Description of problem:**
https://github.com/log2timeline/plaso/blob/master/plaso/parsers/winreg_plugins/usbstor.py#L45
The usbstor winreg plugin current assumes connection times based on the key last written time:
- [x] change parser to produce event objects with last written time
- [x] ~~add setup api information~~ - setupapi parser has been added
- [x] ~~move the determination of the connection times to an analysis plugin~~ - out of scope
| 1.0 | refactor usbstor winreg plugin - **Description of problem:**
https://github.com/log2timeline/plaso/blob/master/plaso/parsers/winreg_plugins/usbstor.py#L45
The usbstor winreg plugin current assumes connection times based on the key last written time:
- [x] change parser to produce event objects with last written time
- [x] ~~add setup api information~~ - setupapi parser has been added
- [x] ~~move the determination of the connection times to an analysis plugin~~ - out of scope
| non_design | refactor usbstor winreg plugin description of problem the usbstor winreg plugin current assumes connection times based on the key last written time change parser to produce event objects with last written time add setup api information setupapi parser has been added move the determination of the connection times to an analysis plugin out of scope | 0 |
140,368 | 21,089,365,494 | IssuesEvent | 2022-04-04 01:50:19 | spaceone-dev/spaceone-design-system | https://api.github.com/repos/spaceone-dev/spaceone-design-system | closed | [auto-complete-input] New | Design Update Priority: Low | **Problem** Need input component with auto-complete
**Solution** Create it
**Figma / Jira Link** https://www.figma.com/file/IS6P8y1Wn2nfBC4jGlSiya/Components?node-id=1154%3A124605
| 1.0 | [auto-complete-input] New - **Problem** Need input component with auto-complete
**Solution** Create it
**Figma / Jira Link** https://www.figma.com/file/IS6P8y1Wn2nfBC4jGlSiya/Components?node-id=1154%3A124605
| design | new problem need input component with auto complete solution create it figma jira link | 1 |
73,389 | 8,870,690,593 | IssuesEvent | 2019-01-11 10:14:48 | ppy/osu-web | https://api.github.com/repos/ppy/osu-web | closed | Add a notice to pages stating there is additional functionality if you're logged in. | design overdue overdue x2 | This supersedes/fixes #2376 and #2217.
Assigned to @arflyte for design. | 1.0 | Add a notice to pages stating there is additional functionality if you're logged in. - This supersedes/fixes #2376 and #2217.
Assigned to @arflyte for design. | design | add a notice to pages stating there is additional functionality if you re logged in this supersedes fixes and assigned to arflyte for design | 1 |
28,881 | 4,142,020,331 | IssuesEvent | 2016-06-14 08:32:52 | owncloud/core | https://api.github.com/repos/owncloud/core | closed | conflicts dialog not usable on phones (mobile) | app:files bug design old-inactive | ### Steps to reproduce
1. Go to an owncloud folder on an iPhone
2. Select 2 photos from the Camera Roll to upload together
3. Upload
### Expected behaviour
Conflict dialog should appear and be usable
### Actual behaviour
Conflict dialog appears, but it isn't usable. Much of the dialog is off the screen. Zooming does not work. Scrolling does not work. Turning the viewport to landscape or portrait shows a little bit more of the dialog in some ways, but never exposes the 'Cancel' and 'Continue' buttons.
### Server configuration
Witnessed on v7.0.1 (stable) and 8.0.2 (stable), the latter on [demo.owncloud.org](https://demo.owncloud.org).
### Client configuration
iOS v 7.1 Native Safari
(I think I also saw it on a Galaxy S3 on FireFox v 34.0.1)
### Additional information
This is particularly irritating when trying to upload multiple photos from iOS's Camera Roll. All of the photos have the same name (image) and are all detected as conflicts. There's no way to actually resolve the conflicts from the phone, though.
I did my best to look through past issues (searching for things like conflicts, dialogs, mobile, iPhone, and android), but I didn't find anything about this. #4766 is possibly the introduction of the current dialog. The lack of zooming on mobile (#15024) also inhibits function here.
### Screenshots
| 1.0 | conflicts dialog not usable on phones (mobile) - ### Steps to reproduce
1. Go to an owncloud folder on an iPhone
2. Select 2 photos from the Camera Roll to upload together
3. Upload
### Expected behaviour
Conflict dialog should appear and be usable
### Actual behaviour
Conflict dialog appears, but it isn't usable. Much of the dialog is off the screen. Zooming does not work. Scrolling does not work. Turning the viewport to landscape or portrait shows a little bit more of the dialog in some ways, but never exposes the 'Cancel' and 'Continue' buttons.
### Server configuration
Witnessed on v7.0.1 (stable) and 8.0.2 (stable), the latter on [demo.owncloud.org](https://demo.owncloud.org).
### Client configuration
iOS v 7.1 Native Safari
(I think I also saw it on a Galaxy S3 on FireFox v 34.0.1)
### Additional information
This is particularly irritating when trying to upload multiple photos from iOS's Camera Roll. All of the photos have the same name (image) and are all detected as conflicts. There's no way to actually resolve the conflicts from the phone, though.
I did my best to look through past issues (searching for things like conflicts, dialogs, mobile, iPhone, and android), but I didn't find anything about this. #4766 is possibly the introduction of the current dialog. The lack of zooming on mobile (#15024) also inhibits function here.
### Screenshots
| design | conflicts dialog not usable on phones mobile steps to reproduce go to an owncloud folder on an iphone select photos from the camera roll to upload together upload expected behaviour conflict dialog should appear and be usable actual behaviour conflict dialog appears but it isn t usable much of the dialog is off the screen zooming does not work scrolling does not work turning the viewport to landscape or portrait shows a little bit more of the dialog in some ways but never exposes the cancel and continue buttons server configuration witnessed on stable and stable the latter on client configuration ios v native safari i think i also saw it on a galaxy on firefox v additional information this is particularly irritating when trying to upload multiple photos from ios s camera roll all of the photos have the same name image and are all detected as conflicts there s no way to actually resolve the conflicts from the phone though i did my best to look through past issues searching for things like conflicts dialogs mobile iphone and android but i didn t find anything about this is possibly the introduction of the current dialog the lack of zooming on mobile also inhibits function here screenshots | 1 |
71,956 | 8,692,366,656 | IssuesEvent | 2018-12-04 06:00:21 | Microsoft/vscode | https://api.github.com/repos/Microsoft/vscode | closed | "Source" line in a notification can get truncated down to "Sour..." | *as-designed | <!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->
The "Source:" section of a notification is can get heavily truncated, to the point that it says "Sour.." which at that point is obstructing what the text is representing.
Not sure if there is much to do here, but it is a slight usability issue as I was demoing this feature to a PM and they asked "what's sour?"
<!-- Use Help > Report Issue to prefill these. -->
Version: 1.29.0-insider (user setup)
Commit: 4d9f1d23a556dccd2c0fd5203923a24b21e41209
Date: 2018-10-22T05:18:34.128Z
Electron: 2.0.11
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
- OS Version: Windows 10
Steps to Reproduce:
1. Have PowerShell set as your terminal
1. Create a conda environment
1. Launch the Python extension for VS Code
1. Open a fresh terminal which will trigger the notification
<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
| 1.0 | "Source" line in a notification can get truncated down to "Sour..." - <!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->
The "Source:" section of a notification is can get heavily truncated, to the point that it says "Sour.." which at that point is obstructing what the text is representing.
Not sure if there is much to do here, but it is a slight usability issue as I was demoing this feature to a PM and they asked "what's sour?"
<!-- Use Help > Report Issue to prefill these. -->
Version: 1.29.0-insider (user setup)
Commit: 4d9f1d23a556dccd2c0fd5203923a24b21e41209
Date: 2018-10-22T05:18:34.128Z
Electron: 2.0.11
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
- OS Version: Windows 10
Steps to Reproduce:
1. Have PowerShell set as your terminal
1. Create a conda environment
1. Launch the Python extension for VS Code
1. Open a fresh terminal which will trigger the notification
<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
| design | source line in a notification can get truncated down to sour the source section of a notification is can get heavily truncated to the point that it says sour which at that point is obstructing what the text is representing not sure if there is much to do here but it is a slight usability issue as i was demoing this feature to a pm and they asked what s sour report issue to prefill these version insider user setup commit date electron chrome node js architecture os version windows steps to reproduce have powershell set as your terminal create a conda environment launch the python extension for vs code open a fresh terminal which will trigger the notification does this issue occur when all extensions are disabled yes | 1 |
32,179 | 4,330,034,891 | IssuesEvent | 2016-07-26 18:41:37 | inaturalist/inaturalist | https://api.github.com/repos/inaturalist/inaturalist | opened | Possible Interim Dashboard Enhancement | design improvements | I realize we will be revisiting the dashboard down the road. No probby. Just wondering how complicated it would be to add a tab here....
...entitled "Following" and it would only show taxa and people you are following. I ask because when I make mass uploads of obs and get mass amounts of IDs, I find myself missing out on content of the folks I follow. This can be a bit of a bummer especially when I'm following new users and want to give them feedback as quickly as possible. | 1.0 | Possible Interim Dashboard Enhancement - I realize we will be revisiting the dashboard down the road. No probby. Just wondering how complicated it would be to add a tab here....
...entitled "Following" and it would only show taxa and people you are following. I ask because when I make mass uploads of obs and get mass amounts of IDs, I find myself missing out on content of the folks I follow. This can be a bit of a bummer especially when I'm following new users and want to give them feedback as quickly as possible. | design | possible interim dashboard enhancement i realize we will be revisiting the dashboard down the road no probby just wondering how complicated it would be to add a tab here entitled following and it would only show taxa and people you are following i ask because when i make mass uploads of obs and get mass amounts of ids i find myself missing out on content of the folks i follow this can be a bit of a bummer especially when i m following new users and want to give them feedback as quickly as possible | 1 |
317,457 | 9,665,687,349 | IssuesEvent | 2019-05-21 09:05:06 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | pontoon.mozilla.org - desktop site instead of mobile site | browser-fenix engine-gecko priority-important | <!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 7.0; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://pontoon.mozilla.org/
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android 7.0
**Tested Another Browser**: No
**Problem type**: Desktop site instead of mobile site
**Description**: pontoon desktop site opens instead of mobile site (Firefox Fenix)
**Steps to Reproduce**:
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | pontoon.mozilla.org - desktop site instead of mobile site - <!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 7.0; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://pontoon.mozilla.org/
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android 7.0
**Tested Another Browser**: No
**Problem type**: Desktop site instead of mobile site
**Description**: pontoon desktop site opens instead of mobile site (Firefox Fenix)
**Steps to Reproduce**:
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_design | pontoon mozilla org desktop site instead of mobile site url browser version firefox mobile operating system android tested another browser no problem type desktop site instead of mobile site description pontoon desktop site opens instead of mobile site firefox fenix steps to reproduce browser configuration none from with ❤️ | 0 |
307,345 | 23,195,603,341 | IssuesEvent | 2022-08-01 16:05:29 | Icinga/icinga2 | https://api.github.com/repos/Icinga/icinga2 | closed | Docs - Installation - Debian Bullseye - apt gpg key -> lack of docu | area/documentation good first issue | Hey,
while doing manually the installation for checking all stuff as preparation for my saltstack automation, i just noticed that the docs for the installation on Debian has a lack for installing the repo key.
The docs here doesn't work for debian bullseye: https://icinga.com/docs/icinga-2/latest/doc/02-installation/#debianubunturaspbian-repositories
You have to save the GPG key in the new folder of apt:
`wget -O - https://packages.icinga.com/icinga.key | gpg --dearmor -o /etc/apt/trusted.gpg.d/icinga-archive-keyring.gpg`
With help of the https://packages.icinga.com/debian/ i found the solution here:
`Archive Key
wget -O - https://packages.icinga.com/icinga.key | gpg --dearmor -o /usr/share/keyrings/icinga-archive-keyring.gpg
# or
curl https://packages.icinga.com/icinga.key | gpg --dearmor -o /usr/share/keyrings/icinga-archive-keyring.gpg
`
So can please someone update the docs with that very important commands for Debian Bullseye?!
Thanks! | 1.0 | Docs - Installation - Debian Bullseye - apt gpg key -> lack of docu - Hey,
while doing manually the installation for checking all stuff as preparation for my saltstack automation, i just noticed that the docs for the installation on Debian has a lack for installing the repo key.
The docs here doesn't work for debian bullseye: https://icinga.com/docs/icinga-2/latest/doc/02-installation/#debianubunturaspbian-repositories
You have to save the GPG key in the new folder of apt:
`wget -O - https://packages.icinga.com/icinga.key | gpg --dearmor -o /etc/apt/trusted.gpg.d/icinga-archive-keyring.gpg`
With help of the https://packages.icinga.com/debian/ i found the solution here:
`Archive Key
wget -O - https://packages.icinga.com/icinga.key | gpg --dearmor -o /usr/share/keyrings/icinga-archive-keyring.gpg
# or
curl https://packages.icinga.com/icinga.key | gpg --dearmor -o /usr/share/keyrings/icinga-archive-keyring.gpg
`
So can please someone update the docs with that very important commands for Debian Bullseye?!
Thanks! | non_design | docs installation debian bullseye apt gpg key lack of docu hey while doing manually the installation for checking all stuff as preparation for my saltstack automation i just noticed that the docs for the installation on debian has a lack for installing the repo key the docs here doesn t work for debian bullseye you have to save the gpg key in the new folder of apt wget o gpg dearmor o etc apt trusted gpg d icinga archive keyring gpg with help of the i found the solution here archive key wget o gpg dearmor o usr share keyrings icinga archive keyring gpg or curl gpg dearmor o usr share keyrings icinga archive keyring gpg so can please someone update the docs with that very important commands for debian bullseye thanks | 0 |
5,807 | 5,968,586,645 | IssuesEvent | 2017-05-30 18:25:32 | mcoffin/purescript-rdkafka | https://api.github.com/repos/mcoffin/purescript-rdkafka | closed | Bower metadata should be complete | infrastructure ready | Before publishing, bower metadata needs to contain:
* Repository link
* Author metadata
* License information
* Documentation link? | 1.0 | Bower metadata should be complete - Before publishing, bower metadata needs to contain:
* Repository link
* Author metadata
* License information
* Documentation link? | non_design | bower metadata should be complete before publishing bower metadata needs to contain repository link author metadata license information documentation link | 0 |
336,332 | 30,188,984,084 | IssuesEvent | 2023-07-04 14:01:48 | thedworak/dfg_3dviewer | https://api.github.com/repos/thedworak/dfg_3dviewer | closed | Bug: Integration with DFG-Viewer breaks because of absolute paths | bug help wanted Testing Possible to do | In `main/main.js` all but one includes are handled as relative paths and work fine when integrating with the DFG-Viewer. But this include uses an absolute path which is only valid in Drupal/WissKI and therefore breaks integration:
https://github.com/thedworak/dfg_3dviewer/blob/72368981a5b6ca4f10e54db1d5678acb82aa141a/main/main.js#L27
Is there a reason for this being an absolute path or could it be a relative path as well?
I suggest changing it like:
`import { GUI } from './node_modules/lil-gui/dist/lil-gui.esm.min.js';`
Furthermore, when I change this locally, there are multiple additional absolute include paths in the library files (e. g. `three.module.js` and `GLTFLoader.js`) which also break integration. | 1.0 | Bug: Integration with DFG-Viewer breaks because of absolute paths - In `main/main.js` all but one includes are handled as relative paths and work fine when integrating with the DFG-Viewer. But this include uses an absolute path which is only valid in Drupal/WissKI and therefore breaks integration:
https://github.com/thedworak/dfg_3dviewer/blob/72368981a5b6ca4f10e54db1d5678acb82aa141a/main/main.js#L27
Is there a reason for this being an absolute path or could it be a relative path as well?
I suggest changing it like:
`import { GUI } from './node_modules/lil-gui/dist/lil-gui.esm.min.js';`
Furthermore, when I change this locally, there are multiple additional absolute include paths in the library files (e. g. `three.module.js` and `GLTFLoader.js`) which also break integration. | non_design | bug integration with dfg viewer breaks because of absolute paths in main main js all but one includes are handled as relative paths and work fine when integrating with the dfg viewer but this include uses an absolute path which is only valid in drupal wisski and therefore breaks integration is there a reason for this being an absolute path or could it be a relative path as well i suggest changing it like import gui from node modules lil gui dist lil gui esm min js furthermore when i change this locally there are multiple additional absolute include paths in the library files e g three module js and gltfloader js which also break integration | 0 |
20,427 | 6,886,983,893 | IssuesEvent | 2017-11-21 21:31:21 | habitat-sh/habitat | https://api.github.com/repos/habitat-sh/habitat | closed | API docs and tests | A-builder A-documentation C-feature | As the first step towards the goals laid out in https://github.com/habitat-sh/habitat/issues/4013, documentation for 3 API endpoints will be written in both API Blueprint and Swagger:
- [x] Origin creation
- [x] Origin update
- [x] Origin retrieval
Dredd will be added and used to run tests against the API docs. This will serve as a test of Dredd to generate tests and also to compare the experience of writing API docs in the two libraries. | 1.0 | API docs and tests - As the first step towards the goals laid out in https://github.com/habitat-sh/habitat/issues/4013, documentation for 3 API endpoints will be written in both API Blueprint and Swagger:
- [x] Origin creation
- [x] Origin update
- [x] Origin retrieval
Dredd will be added and used to run tests against the API docs. This will serve as a test of Dredd to generate tests and also to compare the experience of writing API docs in the two libraries. | non_design | api docs and tests as the first step towards the goals laid out in documentation for api endpoints will be written in both api blueprint and swagger origin creation origin update origin retrieval dredd will be added and used to run tests against the api docs this will serve as a test of dredd to generate tests and also to compare the experience of writing api docs in the two libraries | 0 |
165,562 | 26,191,950,433 | IssuesEvent | 2023-01-03 09:53:53 | nextcloud/deck | https://api.github.com/repos/nextcloud/deck | closed | When the board has "children" the icon-expand is moved to the right | bug design | <!--
Thanks for reporting issues back!
Guidelines for submitting issues:
* Please search the existing issues first, it's likely that your issue was already reported or even fixed.
* SECURITY: Report any potential security bug to us via our HackerOne page (https://hackerone.com/nextcloud) following our security policy (https://nextcloud.com/security/) instead of filing an issue in our bug tracker.
* The issues in other components should be reported in their respective repositories: You will find them in our GitHub Organization (https://github.com/nextcloud/)
* You can also use the Issue Template app to prefill most of the required information: https://apps.nextcloud.com/apps/issuetemplate
-->
<!--- Please keep this note for other contributors -->
### How to use GitHub
* Please use the 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to show that you are affected by the same issue.
* Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
* Subscribe to receive notifications on status change and new comments.
**Describe the bug**
The icon collapse/expand, is moved to the right
**To Reproduce**
Steps to reproduce the behavior:
1. Go to Deck app
2. Click on or hover on All board
3. Make sure you have at least one board
4. See the icon
**Expected behavior**
A clear and concise description of what you expected to happen.
The icon is shown on the left instead of the default icon
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Client details:**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
- Device: [e.g. iPhone6, desktop]
<details>
<summary>Server details</summary>
<!--
You can use the Issue Template application to prefill most of the required information: https://apps.nextcloud.com/apps/issuetemplate
-->
**Operating system**:
**Web server:**
**Database:**
**PHP version:**
**Nextcloud version:** (see Nextcloud admin page)
**Where did you install Nextcloud from:**
**Signing status:**
```
Login as admin user into your Nextcloud and access
http://example.com/index.php/settings/integrity/failed
paste the results here.
```
**List of activated apps:**
```
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder
```
**Nextcloud configuration:**
```
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
or
Insert your config.php content here
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)
```
**Are you using an external user-backend, if yes which one:** LDAP/ActiveDirectory/Webdav/...
</details>
<details>
<summary>Logs</summary>
#### Nextcloud log (data/nextcloud.log)
```
Insert your Nextcloud log here
```
#### Browser log
```
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...
```
</details>
| 1.0 | When the board has "children" the icon-expand is moved to the right - <!--
Thanks for reporting issues back!
Guidelines for submitting issues:
* Please search the existing issues first, it's likely that your issue was already reported or even fixed.
* SECURITY: Report any potential security bug to us via our HackerOne page (https://hackerone.com/nextcloud) following our security policy (https://nextcloud.com/security/) instead of filing an issue in our bug tracker.
* The issues in other components should be reported in their respective repositories: You will find them in our GitHub Organization (https://github.com/nextcloud/)
* You can also use the Issue Template app to prefill most of the required information: https://apps.nextcloud.com/apps/issuetemplate
-->
<!--- Please keep this note for other contributors -->
### How to use GitHub
* Please use the 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to show that you are affected by the same issue.
* Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
* Subscribe to receive notifications on status change and new comments.
**Describe the bug**
The icon collapse/expand, is moved to the right
**To Reproduce**
Steps to reproduce the behavior:
1. Go to Deck app
2. Click on or hover on All board
3. Make sure you have at least one board
4. See the icon
**Expected behavior**
A clear and concise description of what you expected to happen.
The icon is shown on the left instead of the default icon
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Client details:**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
- Device: [e.g. iPhone6, desktop]
<details>
<summary>Server details</summary>
<!--
You can use the Issue Template application to prefill most of the required information: https://apps.nextcloud.com/apps/issuetemplate
-->
**Operating system**:
**Web server:**
**Database:**
**PHP version:**
**Nextcloud version:** (see Nextcloud admin page)
**Where did you install Nextcloud from:**
**Signing status:**
```
Login as admin user into your Nextcloud and access
http://example.com/index.php/settings/integrity/failed
paste the results here.
```
**List of activated apps:**
```
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder
```
**Nextcloud configuration:**
```
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
or
Insert your config.php content here
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)
```
**Are you using an external user-backend, if yes which one:** LDAP/ActiveDirectory/Webdav/...
</details>
<details>
<summary>Logs</summary>
#### Nextcloud log (data/nextcloud.log)
```
Insert your Nextcloud log here
```
#### Browser log
```
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...
```
</details>
| design | when the board has children the icon expand is moved to the right thanks for reporting issues back guidelines for submitting issues please search the existing issues first it s likely that your issue was already reported or even fixed security report any potential security bug to us via our hackerone page following our security policy instead of filing an issue in our bug tracker the issues in other components should be reported in their respective repositories you will find them in our github organization you can also use the issue template app to prefill most of the required information how to use github please use the 👍 to show that you are affected by the same issue please don t comment if you have no relevant information to add it s just extra noise for everyone subscribed to this issue subscribe to receive notifications on status change and new comments describe the bug the icon collapse expand is moved to the right to reproduce steps to reproduce the behavior go to deck app click on or hover on all board make sure you have at least one board see the icon expected behavior a clear and concise description of what you expected to happen the icon is shown on the left instead of the default icon screenshots if applicable add screenshots to help explain your problem client details os browser version device server details you can use the issue template application to prefill most of the required information operating system web server database php version nextcloud version see nextcloud admin page where did you install nextcloud from signing status login as admin user into your nextcloud and access paste the results here list of activated apps if you have access to your command line run e g sudo u www data php occ app list from within your nextcloud installation folder nextcloud configuration if you have access to your command line run e g sudo u www data php occ config list system from within your nextcloud installation folder or insert your config php content here make sure to remove all sensitive content such as passwords e g database password passwordsalt secret smtp password … are you using an external user backend if yes which one ldap activedirectory webdav logs nextcloud log data nextcloud log insert your nextcloud log here browser log insert your browser log here this could for example include a the javascript console log b the network log c | 1 |
121,997 | 12,138,803,096 | IssuesEvent | 2020-04-23 17:50:26 | certbot/certbot | https://api.github.com/repos/certbot/certbot | opened | Create EFF/Certbot snapcraft account and transfer ownership to it | area: documentation area: snaps | Related to #7865, https://snapcraft.io/certbot says the Certbot snap is owned by Robie Basak who is the Canonical employee who helped us create the Certbot snap. We should change this to say the snap is owned by EFF or the Certbot team. Perhaps we could/should make it a verified account like you see for many of the snaps advertised on https://snapcraft.io/store with the green checkmark. I'm not immediately sure if there's anything special we need to do to create an organization account instead of a personal account so this should be looked into a bit.
Once the account is created, I believe we/Robie has to make a post on Discourse asking the snap store maintainers to transfer ownership. | 1.0 | Create EFF/Certbot snapcraft account and transfer ownership to it - Related to #7865, https://snapcraft.io/certbot says the Certbot snap is owned by Robie Basak who is the Canonical employee who helped us create the Certbot snap. We should change this to say the snap is owned by EFF or the Certbot team. Perhaps we could/should make it a verified account like you see for many of the snaps advertised on https://snapcraft.io/store with the green checkmark. I'm not immediately sure if there's anything special we need to do to create an organization account instead of a personal account so this should be looked into a bit.
Once the account is created, I believe we/Robie has to make a post on Discourse asking the snap store maintainers to transfer ownership. | non_design | create eff certbot snapcraft account and transfer ownership to it related to says the certbot snap is owned by robie basak who is the canonical employee who helped us create the certbot snap we should change this to say the snap is owned by eff or the certbot team perhaps we could should make it a verified account like you see for many of the snaps advertised on with the green checkmark i m not immediately sure if there s anything special we need to do to create an organization account instead of a personal account so this should be looked into a bit once the account is created i believe we robie has to make a post on discourse asking the snap store maintainers to transfer ownership | 0 |
209,148 | 7,165,736,411 | IssuesEvent | 2018-01-29 15:17:12 | s1lentq/ReGameDLL_CS | https://api.github.com/repos/s1lentq/ReGameDLL_CS | closed | Bad bomb angles (#207) | Priority: Low Status: Accepted Type: Enhancement | Related to https://github.com/s1lentq/ReGameDLL_CS/pull/207
Since most people use right hand ingame, bomb feel reversed about the angle. The right is at the left and so on.
That could be easly fix by changing the angle value, but i have no time to test this. | 1.0 | Bad bomb angles (#207) - Related to https://github.com/s1lentq/ReGameDLL_CS/pull/207
Since most people use right hand ingame, bomb feel reversed about the angle. The right is at the left and so on.
That could be easly fix by changing the angle value, but i have no time to test this. | non_design | bad bomb angles related to since most people use right hand ingame bomb feel reversed about the angle the right is at the left and so on that could be easly fix by changing the angle value but i have no time to test this | 0 |
66,216 | 7,976,012,661 | IssuesEvent | 2018-07-17 11:14:14 | mysociety/alaveteli | https://api.github.com/repos/mysociety/alaveteli | closed | Reword blank state text on homepage | 0 - backlog f:framework improvement t:design user-experience | 
Maybe:
``` diff
- Alaveteli users have made 0 requests, including:
+ Alaveteli users have made 0 requests. Make a request –>
```
<!---
@huboard:{"order":1562.0000000000007,"custom_state":""}
-->
| 1.0 | Reword blank state text on homepage - 
Maybe:
``` diff
- Alaveteli users have made 0 requests, including:
+ Alaveteli users have made 0 requests. Make a request –>
```
<!---
@huboard:{"order":1562.0000000000007,"custom_state":""}
-->
| design | reword blank state text on homepage maybe diff alaveteli users have made requests including alaveteli users have made requests make a request – huboard order custom state | 1 |
2,700 | 2,640,501,018 | IssuesEvent | 2015-03-11 12:41:10 | mayf3/train_system | https://api.github.com/repos/mayf3/train_system | opened | models设计 | Design | base model初始化数据库链接
member model继承自base model
功能暂定为：
editMember
deleteMember
createMember
table model继承自base model
功能暂定为：
getTableNumber
getTableContent
insertTable
editTable
deleteTable
imformation model继承自base model
insertImformation
editImformation
deleteImformation
getImformation
具体参数待定 | 1.0 | models设计 - base model初始化数据库链接
member model继承自base model
功能暂定为：
editMember
deleteMember
createMember
table model继承自base model
功能暂定为：
getTableNumber
getTableContent
insertTable
editTable
deleteTable
imformation model继承自base model
insertImformation
editImformation
deleteImformation
getImformation
具体参数待定 | design | models设计 base model初始化数据库链接 member model继承自base model 功能暂定为： editmember deletemember createmember table model继承自base model 功能暂定为： gettablenumber gettablecontent inserttable edittable deletetable imformation model继承自base model insertimformation editimformation deleteimformation getimformation 具体参数待定 | 1 |
397,160 | 11,724,308,387 | IssuesEvent | 2020-03-10 10:42:49 | wso2/product-apim | https://api.github.com/repos/wso2/product-apim | opened | [Improvement] Starting server profiles when installed as a Windows service. | Docs/Has Impact Priority/Normal Type/Docs | ### Description:
Running the apim product using profiles in Windows as a service. Instructions already present to pass this parameter and enabling the profile when starting with .bat script. But I failed to locate the same when using wrapper.conf file.
Below instructions work and better to keep this added in the docs as this might not be obvious to many users.
Add the below parameter to wrapper conf. Replace x with the next digit.
wrapper.java.additional.x = -Dprofile=gateway-worker
--
| 1.0 | [Improvement] Starting server profiles when installed as a Windows service. - ### Description:
Running the apim product using profiles in Windows as a service. Instructions already present to pass this parameter and enabling the profile when starting with .bat script. But I failed to locate the same when using wrapper.conf file.
Below instructions work and better to keep this added in the docs as this might not be obvious to many users.
Add the below parameter to wrapper conf. Replace x with the next digit.
wrapper.java.additional.x = -Dprofile=gateway-worker
--
| non_design | starting server profiles when installed as a windows service description running the apim product using profiles in windows as a service instructions already present to pass this parameter and enabling the profile when starting with bat script but i failed to locate the same when using wrapper conf file below instructions work and better to keep this added in the docs as this might not be obvious to many users add the below parameter to wrapper conf replace x with the next digit wrapper java additional x dprofile gateway worker | 0 |
183,515 | 31,560,443,613 | IssuesEvent | 2023-09-03 07:21:04 | BanchanArt/banchan | https://api.github.com/repos/BanchanArt/banchan | opened | More marketing-y home page | feature design | Right now, the home page is just the marketplace.
Instead, we should have a page that highlights the important points about Banchan, with a nice design, and then acts as a jumping point into our marketplace | 1.0 | More marketing-y home page - Right now, the home page is just the marketplace.
Instead, we should have a page that highlights the important points about Banchan, with a nice design, and then acts as a jumping point into our marketplace | design | more marketing y home page right now the home page is just the marketplace instead we should have a page that highlights the important points about banchan with a nice design and then acts as a jumping point into our marketplace | 1 |
254,819 | 27,430,487,868 | IssuesEvent | 2023-03-02 00:40:53 | devssa/onde-codar-em-salvador | https://api.github.com/repos/devssa/onde-codar-em-salvador | closed | [REMOTO] [JAVA] [BACK-END] Desenvolvedor Java na [SOFTPLAN] | HOME OFFICE BACK-END JAVA JAVASCRIPT CSS3 HTML SCRUM BDD GIT REST SOAP DOCKER REACT REMOTO TDD KANBAN LEAN XP DDD METODOLOGIAS ÁGEIS HELP WANTED SPRING SECURITY SPRING BOOT Stale | <!--
==================================================
POR FAVOR, SÓ POSTE SE A VAGA FOR PARA SALVADOR E CIDADES VIZINHAS!
Use: "Desenvolvedor Front-end" ao invés de
"Front-End Developer" \o/
Exemplo: `[JAVASCRIPT] [MYSQL] [NODE.JS] Desenvolvedor Front-End na [NOME DA EMPRESA]`
==================================================
-->
## Descrição da vaga
- Desenvolvedor Java na Softplan.
**Desafio:**
- Nesta função você irá desenvolver novas soluções aplicando as melhores práticas de mercado, levando até nossos clientes o que há de melhor em experiência do usuário.
- Desenvolver e manter aplicações com foco em escalabilidade e eficiência;
- Valorizar a manutenção do código;
- Colaborar no planejamento e especificação das evoluções e manutenções das soluções;
- Participar da estimativa e validação de esforço para evolução e manutenção de software;
- Prezar pela sustentabilidade das soluções;
- Ser corresponsável pela qualidade do produto entregue;
- Documentar tecnicamente os sistemas desenvolvidos;
- Documentar análises para escolhas tecnológicas e técnicas das melhorias entregues em novas versões;
- Buscar constantemente aperfeiçoamento tecnológico, mantendo-se atualizado quanto as mais novas tecnologias e metodologias de desenvolvimentos utilizadas no mercado.
## Local
- Home Office
## Benefícios
- Plano de saúde e odontológico;
- Vale-alimentação/Vale-refeição;
- Vale-transporte;
- Auxílio home-office;
- Bônus anual por resultados;
- Programa de promoção à saúde e bem-estar (ginástica laboral 3x na semana, acolhimento psicológico, atendimento médico, nutricionista, ambulatório na sede, etc.);
- Programa Desenvolve Softplan: apoio para realizar cursos e certificações;
- Parcerias e descontos.
## Requisitos
**Obrigatórios:**
- Experiência com o desenvolvimento de back-end em Java.
- Conhecimento sólido de Javascript, HTML e CSS.
- Experiência com desenvolvimento em ReactJS.
- Conhecimento de frameworks: SpringBoot, SpringSecurity
- Experiência no desenvolvimento de serviços: REST e SOAP
- Experiência em ferramentas: Git e Docker.
- Conhecimento em metodologias: TDD, DDD e BDD
- Metodologias ágeis: SCRUM, XP, Lean, Kanban
## Contratação
- a combinar
## Nossa empresa
- Somos uma empresa especialista em traduzir conhecimento e tecnologia em soluções que simplificam e geram mais valor aos mercados da Gestão Pública, Justiça e Indústria da Construção. Como uma das maiores desenvolvedoras de software do país, atuamos diariamente para promover transformações fundamentais na vida de milhares de pessoas que são beneficiadas por nossos produtos.
## Como se candidatar
- [Clique aqui para se candidatar](https://jobs.kenoby.com/softplan/job/java-developer-cod-2015-segmento-justica/60102e61caff000ff8d8c051?utm_source=website)
| True | [REMOTO] [JAVA] [BACK-END] Desenvolvedor Java na [SOFTPLAN] - <!--
==================================================
POR FAVOR, SÓ POSTE SE A VAGA FOR PARA SALVADOR E CIDADES VIZINHAS!
Use: "Desenvolvedor Front-end" ao invés de
"Front-End Developer" \o/
Exemplo: `[JAVASCRIPT] [MYSQL] [NODE.JS] Desenvolvedor Front-End na [NOME DA EMPRESA]`
==================================================
-->
## Descrição da vaga
- Desenvolvedor Java na Softplan.
**Desafio:**
- Nesta função você irá desenvolver novas soluções aplicando as melhores práticas de mercado, levando até nossos clientes o que há de melhor em experiência do usuário.
- Desenvolver e manter aplicações com foco em escalabilidade e eficiência;
- Valorizar a manutenção do código;
- Colaborar no planejamento e especificação das evoluções e manutenções das soluções;
- Participar da estimativa e validação de esforço para evolução e manutenção de software;
- Prezar pela sustentabilidade das soluções;
- Ser corresponsável pela qualidade do produto entregue;
- Documentar tecnicamente os sistemas desenvolvidos;
- Documentar análises para escolhas tecnológicas e técnicas das melhorias entregues em novas versões;
- Buscar constantemente aperfeiçoamento tecnológico, mantendo-se atualizado quanto as mais novas tecnologias e metodologias de desenvolvimentos utilizadas no mercado.
## Local
- Home Office
## Benefícios
- Plano de saúde e odontológico;
- Vale-alimentação/Vale-refeição;
- Vale-transporte;
- Auxílio home-office;
- Bônus anual por resultados;
- Programa de promoção à saúde e bem-estar (ginástica laboral 3x na semana, acolhimento psicológico, atendimento médico, nutricionista, ambulatório na sede, etc.);
- Programa Desenvolve Softplan: apoio para realizar cursos e certificações;
- Parcerias e descontos.
## Requisitos
**Obrigatórios:**
- Experiência com o desenvolvimento de back-end em Java.
- Conhecimento sólido de Javascript, HTML e CSS.
- Experiência com desenvolvimento em ReactJS.
- Conhecimento de frameworks: SpringBoot, SpringSecurity
- Experiência no desenvolvimento de serviços: REST e SOAP
- Experiência em ferramentas: Git e Docker.
- Conhecimento em metodologias: TDD, DDD e BDD
- Metodologias ágeis: SCRUM, XP, Lean, Kanban
## Contratação
- a combinar
## Nossa empresa
- Somos uma empresa especialista em traduzir conhecimento e tecnologia em soluções que simplificam e geram mais valor aos mercados da Gestão Pública, Justiça e Indústria da Construção. Como uma das maiores desenvolvedoras de software do país, atuamos diariamente para promover transformações fundamentais na vida de milhares de pessoas que são beneficiadas por nossos produtos.
## Como se candidatar
- [Clique aqui para se candidatar](https://jobs.kenoby.com/softplan/job/java-developer-cod-2015-segmento-justica/60102e61caff000ff8d8c051?utm_source=website)
| non_design | desenvolvedor java na por favor só poste se a vaga for para salvador e cidades vizinhas use desenvolvedor front end ao invés de front end developer o exemplo desenvolvedor front end na descrição da vaga desenvolvedor java na softplan desafio nesta função você irá desenvolver novas soluções aplicando as melhores práticas de mercado levando até nossos clientes o que há de melhor em experiência do usuário desenvolver e manter aplicações com foco em escalabilidade e eficiência valorizar a manutenção do código colaborar no planejamento e especificação das evoluções e manutenções das soluções participar da estimativa e validação de esforço para evolução e manutenção de software prezar pela sustentabilidade das soluções ser corresponsável pela qualidade do produto entregue documentar tecnicamente os sistemas desenvolvidos documentar análises para escolhas tecnológicas e técnicas das melhorias entregues em novas versões buscar constantemente aperfeiçoamento tecnológico mantendo se atualizado quanto as mais novas tecnologias e metodologias de desenvolvimentos utilizadas no mercado local home office benefícios plano de saúde e odontológico vale alimentação vale refeição vale transporte auxílio home office bônus anual por resultados programa de promoção à saúde e bem estar ginástica laboral na semana acolhimento psicológico atendimento médico nutricionista ambulatório na sede etc programa desenvolve softplan apoio para realizar cursos e certificações parcerias e descontos requisitos obrigatórios experiência com o desenvolvimento de back end em java conhecimento sólido de javascript html e css experiência com desenvolvimento em reactjs conhecimento de frameworks springboot springsecurity experiência no desenvolvimento de serviços rest e soap experiência em ferramentas git e docker conhecimento em metodologias tdd ddd e bdd metodologias ágeis scrum xp lean kanban contratação a combinar nossa empresa somos uma empresa especialista em traduzir conhecimento e tecnologia em soluções que simplificam e geram mais valor aos mercados da gestão pública justiça e indústria da construção como uma das maiores desenvolvedoras de software do país atuamos diariamente para promover transformações fundamentais na vida de milhares de pessoas que são beneficiadas por nossos produtos como se candidatar | 0 |
290,802 | 25,096,677,079 | IssuesEvent | 2022-11-08 10:38:59 | wazuh/wazuh-qa | https://api.github.com/repos/wazuh/wazuh-qa | closed | Change authd.pass ownership and permissions | team/qa target/4.4.0 type/dev-testing role/qa-runtime-terror subteam/qa-rainbow | | Target version | Related issue | Related PR |
|--------------------|--------------------|-----------------|
| 4.4 | https://github.com/wazuh/wazuh-packages/issues/1787 | https://github.com/wazuh/wazuh/pull/14967 |
<!-- Important: No section may be left blank. If not, delete it directly (in principle only Steps to reproduce could be left blank in case of not proceeding, although there are always exceptions). -->
# Description
<!-- Description that puts into context and shows the QA tester the changes that have been made by the developer and need to be tested. -->
Installing the wazuh-agent using the deployment variable ```WAZUH_REGISTRATION_PASSWORD``` sets wrong ownership and permissions, now it is expected that the permissions are set to ```640``` and the ownership to ```root:wazuh```
# Checks
The following checks have been done in multiple scenarios: production, after upgrading the product with the bug(with the fix), and a fresh installation that contains the fix. Also, in Windows environment they have been tested, just verifying that it is not broken
## Proposed checks
<!-- Indicate through a list of checkboxes the suggested checks to be carried out by the QA tester -->
- [x] authd.pass ownership is root:wazuh
- [x] authd.pass permissions are set to ```640```
## Additional checks
- [x] Check that agents enroll using `WAZUH_REGISTRATION_PASSWORD`
- [x] Check that password can be empty
- [x] Check that password can has spaces
## Expected results
````
root@7c5749dadb1d:/# ll /var/ossec/etc/
total 56
drwxrwx--- 3 wazuh wazuh 4096 Sep 19 14:05 ./
drwxr-x--- 15 root wazuh 4096 Sep 19 14:04 ../
-rw-r----- 1 root wazuh 10 Sep 19 14:04 authd.pass
-rw-r----- 1 wazuh wazuh 86 Sep 19 14:05 client.keys
-rw-r----- 1 root wazuh 13408 Sep 19 11:49 internal_options.conf
-rw-r----- 1 root wazuh 320 Sep 19 11:49 local_internal_options.conf
-rw-r----- 1 root wazuh 118 Sep 19 11:49 localtime
-rw-rw---- 1 root wazuh 5459 Sep 19 14:04 ossec.conf
drwxrwx--- 2 root wazuh 4096 Sep 19 14:05 shared/
-rw-r----- 1 root wazuh 1367 Sep 19 11:49 wpk_root.pem
````
## Configuration and considerations
Generate the wazuh-agent package using the branch of the PR https://github.com/wazuh/wazuh/pull/14967
| 1.0 | Change authd.pass ownership and permissions - | Target version | Related issue | Related PR |
|--------------------|--------------------|-----------------|
| 4.4 | https://github.com/wazuh/wazuh-packages/issues/1787 | https://github.com/wazuh/wazuh/pull/14967 |
<!-- Important: No section may be left blank. If not, delete it directly (in principle only Steps to reproduce could be left blank in case of not proceeding, although there are always exceptions). -->
# Description
<!-- Description that puts into context and shows the QA tester the changes that have been made by the developer and need to be tested. -->
Installing the wazuh-agent using the deployment variable ```WAZUH_REGISTRATION_PASSWORD``` sets wrong ownership and permissions, now it is expected that the permissions are set to ```640``` and the ownership to ```root:wazuh```
# Checks
The following checks have been done in multiple scenarios: production, after upgrading the product with the bug(with the fix), and a fresh installation that contains the fix. Also, in Windows environment they have been tested, just verifying that it is not broken
## Proposed checks
<!-- Indicate through a list of checkboxes the suggested checks to be carried out by the QA tester -->
- [x] authd.pass ownership is root:wazuh
- [x] authd.pass permissions are set to ```640```
## Additional checks
- [x] Check that agents enroll using `WAZUH_REGISTRATION_PASSWORD`
- [x] Check that password can be empty
- [x] Check that password can has spaces
## Expected results
````
root@7c5749dadb1d:/# ll /var/ossec/etc/
total 56
drwxrwx--- 3 wazuh wazuh 4096 Sep 19 14:05 ./
drwxr-x--- 15 root wazuh 4096 Sep 19 14:04 ../
-rw-r----- 1 root wazuh 10 Sep 19 14:04 authd.pass
-rw-r----- 1 wazuh wazuh 86 Sep 19 14:05 client.keys
-rw-r----- 1 root wazuh 13408 Sep 19 11:49 internal_options.conf
-rw-r----- 1 root wazuh 320 Sep 19 11:49 local_internal_options.conf
-rw-r----- 1 root wazuh 118 Sep 19 11:49 localtime
-rw-rw---- 1 root wazuh 5459 Sep 19 14:04 ossec.conf
drwxrwx--- 2 root wazuh 4096 Sep 19 14:05 shared/
-rw-r----- 1 root wazuh 1367 Sep 19 11:49 wpk_root.pem
````
## Configuration and considerations
Generate the wazuh-agent package using the branch of the PR https://github.com/wazuh/wazuh/pull/14967
| non_design | change authd pass ownership and permissions target version related issue related pr description installing the wazuh agent using the deployment variable wazuh registration password sets wrong ownership and permissions now it is expected that the permissions are set to and the ownership to root wazuh checks the following checks have been done in multiple scenarios production after upgrading the product with the bug with the fix and a fresh installation that contains the fix also in windows environment they have been tested just verifying that it is not broken proposed checks authd pass ownership is root wazuh authd pass permissions are set to additional checks check that agents enroll using wazuh registration password check that password can be empty check that password can has spaces expected results root ll var ossec etc total drwxrwx wazuh wazuh sep drwxr x root wazuh sep rw r root wazuh sep authd pass rw r wazuh wazuh sep client keys rw r root wazuh sep internal options conf rw r root wazuh sep local internal options conf rw r root wazuh sep localtime rw rw root wazuh sep ossec conf drwxrwx root wazuh sep shared rw r root wazuh sep wpk root pem configuration and considerations generate the wazuh agent package using the branch of the pr | 0 |
334,530 | 29,872,468,729 | IssuesEvent | 2023-06-20 09:22:44 | JsDaddy/ngx-mask | https://api.github.com/repos/JsDaddy/ngx-mask | closed | Not able to type latin characters | need test custom pattern | # 🐞 bug report
### Is this a regression?
I don't know.
### Description
I'm not able to type latin characters even if I specify it in a custom pattern like this:
```ts
readonly customPatterns = { N: { pattern: /[a-zÀ-ÿ\s'-]/i } };
```
```html
<input matInput mask="N*" [formControl]="formControl" [patterns]="customPatterns">
```
It doesn't let me to type "á" or "é", for example.
## 🔬 Minimal Reproduction
https://stackblitz.com/edit/angular-ivy-rmluab
## 🌍 Your Environment
**Angular Version:** 11.x | 1.0 | Not able to type latin characters - # 🐞 bug report
### Is this a regression?
I don't know.
### Description
I'm not able to type latin characters even if I specify it in a custom pattern like this:
```ts
readonly customPatterns = { N: { pattern: /[a-zÀ-ÿ\s'-]/i } };
```
```html
<input matInput mask="N*" [formControl]="formControl" [patterns]="customPatterns">
```
It doesn't let me to type "á" or "é", for example.
## 🔬 Minimal Reproduction
https://stackblitz.com/edit/angular-ivy-rmluab
## 🌍 Your Environment
**Angular Version:** 11.x | non_design | not able to type latin characters 🐞 bug report is this a regression i don t know description i m not able to type latin characters even if i specify it in a custom pattern like this ts readonly custompatterns n pattern i html it doesn t let me to type á or é for example 🔬 minimal reproduction 🌍 your environment angular version x | 0 |
94,976 | 11,943,839,134 | IssuesEvent | 2020-04-03 00:30:41 | Automattic/wp-calypso | https://api.github.com/repos/Automattic/wp-calypso | closed | Gutenboarding: make commercial domain default in header | [Goal] Gutenboarding [Status] Needs Design Review [Type] Task | In the header, we now show free _"*.wordpress.com is available"_. The domain should be the recommended paid domain.
<img width="540" alt="Screenshot 2020-03-29 at 20 15 47" src="https://user-images.githubusercontent.com/87168/77855616-2aad8900-71fa-11ea-9405-99f44546bdc2.png">
**Question:** should we somehow highlight what customer's free domain is going to be without any action?
Once they've actually selected something (e.g. free domain), show that in the header:
**Question:** what should the text then be?
@Automattic/gutenboarding-design | 1.0 | Gutenboarding: make commercial domain default in header - In the header, we now show free _"*.wordpress.com is available"_. The domain should be the recommended paid domain.
<img width="540" alt="Screenshot 2020-03-29 at 20 15 47" src="https://user-images.githubusercontent.com/87168/77855616-2aad8900-71fa-11ea-9405-99f44546bdc2.png">
**Question:** should we somehow highlight what customer's free domain is going to be without any action?
Once they've actually selected something (e.g. free domain), show that in the header:
**Question:** what should the text then be?
@Automattic/gutenboarding-design | design | gutenboarding make commercial domain default in header in the header we now show free wordpress com is available the domain should be the recommended paid domain img width alt screenshot at src question should we somehow highlight what customer s free domain is going to be without any action once they ve actually selected something e g free domain show that in the header question what should the text then be automattic gutenboarding design | 1 |
141,836 | 21,630,501,771 | IssuesEvent | 2022-05-05 09:13:10 | vector-im/element-web | https://api.github.com/repos/vector-im/element-web | closed | Highlight pills when hovering over them | X-Needs-Design T-Enhancement A-Pills Z-Papercuts Z-Visibility-2 Z-Impact-3 | This gives them a little bit more feel.
Demonstration video:
https://user-images.githubusercontent.com/22740616/114694693-1a8c1d00-9d1b-11eb-8049-8bf28fbaf7c9.mp4
| 1.0 | Highlight pills when hovering over them - This gives them a little bit more feel.
Demonstration video:
https://user-images.githubusercontent.com/22740616/114694693-1a8c1d00-9d1b-11eb-8049-8bf28fbaf7c9.mp4
| design | highlight pills when hovering over them this gives them a little bit more feel demonstration video | 1 |
358,223 | 25,183,017,157 | IssuesEvent | 2022-11-11 15:19:09 | rcgsheffield/vscoderemote_sheffield_hpc | https://api.github.com/repos/rcgsheffield/vscoderemote_sheffield_hpc | opened | Readme needs updating. | bug documentation | When the Bessemer script is available the readme will need refactoring to reflect both scripts are available as well as highlight the differences in options. | 1.0 | Readme needs updating. - When the Bessemer script is available the readme will need refactoring to reflect both scripts are available as well as highlight the differences in options. | non_design | readme needs updating when the bessemer script is available the readme will need refactoring to reflect both scripts are available as well as highlight the differences in options | 0 |
86,228 | 3,703,848,366 | IssuesEvent | 2016-02-29 21:52:14 | kubernetes/kubernetes | https://api.github.com/repos/kubernetes/kubernetes | closed | 1000 node cluster: GCE api calls have low success rate | area/cloudprovider area/platform/gce priority/P1 team/cluster team/control-plane team/gke | From https://console.developers.google.com/project I see that my project (mohr-instance-manager1, used exclusively for GKE clusters) has 66k successful API requests and 353k errors. A skim of other kubernetes and GKE projects turns up many that have 10-20% error rates, which isn't the 80% error rate my project is seeing, but it still seems unlikely that's WAI and there's a bug in something that calls GCE's api.
| 1.0 | 1000 node cluster: GCE api calls have low success rate - From https://console.developers.google.com/project I see that my project (mohr-instance-manager1, used exclusively for GKE clusters) has 66k successful API requests and 353k errors. A skim of other kubernetes and GKE projects turns up many that have 10-20% error rates, which isn't the 80% error rate my project is seeing, but it still seems unlikely that's WAI and there's a bug in something that calls GCE's api.
| non_design | node cluster gce api calls have low success rate from i see that my project mohr instance used exclusively for gke clusters has successful api requests and errors a skim of other kubernetes and gke projects turns up many that have error rates which isn t the error rate my project is seeing but it still seems unlikely that s wai and there s a bug in something that calls gce s api | 0 |
63,397 | 15,596,423,932 | IssuesEvent | 2021-03-18 15:51:07 | spack/spack | https://api.github.com/repos/spack/spack | opened | Installation issue: gsl | build-error | When building gsl there are a few problems.
1) gsl patch fails on 2.6
2) when using +external-cblas with nvhpc+blas:
==> Error: NoHeadersError: Unable to locate nvhpc headers in /opt/nvidia/hpc_sdk/include
removing CBLAS_CFLAGS= if '^nvhpc+blas' in self.spec:
one can go further:
3) when linking it fails to find aio_return and al function which are to be found with -lrt
$ spack install gsl@2.5+external-cblas %nvhpc ^nhpc+blas
==> Error: NoHeadersError: Unable to locate nvhpc headers in /opt/nvidia/hpc_sdk/include
This error occurs on Ubuntu18.04 wuth external nvhpc@21.2.
<!-- Please include the output of `spack debug report` -->
* **Spack:** 0.16.0-1079-af988fc32d
* **Python:** 3.6.9
* **Platform:** linux-ubuntu18.04-zen2
* **Concretizer:** original
<!-- If you have any relevant configuration detail (custom `packages.yaml` or `modules.yaml`, etc.) you can add that here as well. -->
packages:
nvhpc:
externals:
- spec: nvhpc@21.2+mpi+blas+lapack
prefix: /opt/nvidia/hpc_sdk
modules:
- nvhpc/21.2
- spec: nvhpc@21.2~mpi+blas+lapack
prefix: /opt/nvidia/hpc_sdk
modules:
- nvhpc-nompi/21.2
compilers:
- compiler:
spec: nvhpc@21.2
paths:
cc: /opt/nvidia/hpc_sdk/Linux_x86_64/21.2/compilers/bin/nvc
cxx: /opt/nvidia/hpc_sdk/Linux_x86_64/21.2/compilers/bin/nvc++
f77: /opt/nvidia/hpc_sdk/Linux_x86_64/21.2/compilers/bin/nvfortran
fc: /opt/nvidia/hpc_sdk/Linux_x86_64/21.2/compilers/bin/nvfortran
flags: {}
operating_system: ubuntu18.04
target: x86_64
modules: [nvhpc/21.2]
environment:
set:
MODULEPATH: ${MODULEPATH}:/opt/nvidia/hpc_sdk/modulefiles
extra_rpaths: []
### General information
<!-- These boxes can be checked by replacing [ ] with [x] or by clicking them after submitting the issue. -->
- [x] I have run `spack debug report` and reported the version of Spack/Python/Platform
- [x] I have run `spack maintainers <name-of-the-package>` and @mentioned any maintainers
- [ ] I have uploaded the build log and environment files
- [x] I have searched the issues of this repo and believe this is not a duplicate
| 1.0 | Installation issue: gsl - When building gsl there are a few problems.
1) gsl patch fails on 2.6
2) when using +external-cblas with nvhpc+blas:
==> Error: NoHeadersError: Unable to locate nvhpc headers in /opt/nvidia/hpc_sdk/include
removing CBLAS_CFLAGS= if '^nvhpc+blas' in self.spec:
one can go further:
3) when linking it fails to find aio_return and al function which are to be found with -lrt
$ spack install gsl@2.5+external-cblas %nvhpc ^nhpc+blas
==> Error: NoHeadersError: Unable to locate nvhpc headers in /opt/nvidia/hpc_sdk/include
This error occurs on Ubuntu18.04 wuth external nvhpc@21.2.
<!-- Please include the output of `spack debug report` -->
* **Spack:** 0.16.0-1079-af988fc32d
* **Python:** 3.6.9
* **Platform:** linux-ubuntu18.04-zen2
* **Concretizer:** original
<!-- If you have any relevant configuration detail (custom `packages.yaml` or `modules.yaml`, etc.) you can add that here as well. -->
packages:
nvhpc:
externals:
- spec: nvhpc@21.2+mpi+blas+lapack
prefix: /opt/nvidia/hpc_sdk
modules:
- nvhpc/21.2
- spec: nvhpc@21.2~mpi+blas+lapack
prefix: /opt/nvidia/hpc_sdk
modules:
- nvhpc-nompi/21.2
compilers:
- compiler:
spec: nvhpc@21.2
paths:
cc: /opt/nvidia/hpc_sdk/Linux_x86_64/21.2/compilers/bin/nvc
cxx: /opt/nvidia/hpc_sdk/Linux_x86_64/21.2/compilers/bin/nvc++
f77: /opt/nvidia/hpc_sdk/Linux_x86_64/21.2/compilers/bin/nvfortran
fc: /opt/nvidia/hpc_sdk/Linux_x86_64/21.2/compilers/bin/nvfortran
flags: {}
operating_system: ubuntu18.04
target: x86_64
modules: [nvhpc/21.2]
environment:
set:
MODULEPATH: ${MODULEPATH}:/opt/nvidia/hpc_sdk/modulefiles
extra_rpaths: []
### General information
<!-- These boxes can be checked by replacing [ ] with [x] or by clicking them after submitting the issue. -->
- [x] I have run `spack debug report` and reported the version of Spack/Python/Platform
- [x] I have run `spack maintainers <name-of-the-package>` and @mentioned any maintainers
- [ ] I have uploaded the build log and environment files
- [x] I have searched the issues of this repo and believe this is not a duplicate
| non_design | installation issue gsl when building gsl there are a few problems gsl patch fails on when using external cblas with nvhpc blas error noheaderserror unable to locate nvhpc headers in opt nvidia hpc sdk include removing cblas cflags if nvhpc blas in self spec one can go further when linking it fails to find aio return and al function which are to be found with lrt spack install gsl external cblas nvhpc nhpc blas error noheaderserror unable to locate nvhpc headers in opt nvidia hpc sdk include this error occurs on wuth external nvhpc spack python platform linux concretizer original packages nvhpc externals spec nvhpc mpi blas lapack prefix opt nvidia hpc sdk modules nvhpc spec nvhpc mpi blas lapack prefix opt nvidia hpc sdk modules nvhpc nompi compilers compiler spec nvhpc paths cc opt nvidia hpc sdk linux compilers bin nvc cxx opt nvidia hpc sdk linux compilers bin nvc opt nvidia hpc sdk linux compilers bin nvfortran fc opt nvidia hpc sdk linux compilers bin nvfortran flags operating system target modules environment set modulepath modulepath opt nvidia hpc sdk modulefiles extra rpaths general information i have run spack debug report and reported the version of spack python platform i have run spack maintainers and mentioned any maintainers i have uploaded the build log and environment files i have searched the issues of this repo and believe this is not a duplicate | 0 |
66,032 | 7,960,242,444 | IssuesEvent | 2018-07-13 06:16:08 | tarantool/tarantool | https://api.github.com/repos/tarantool/tarantool | closed | box.schema.func.reload only work with a function name | feature in design | `box.schema.func.reload()` only work with a function name but the documentation says that it should work with a module name and also without any arguments to reload everything https://tarantool.org/en/doc/1.7/book/box/box_schema.html?highlight=reload#lua-function.box.schema.func.reload
```lua
tarantool> box.schema.func.reload()
---
- error: 'bad argument #1 to ''?'' (string expected, got no value)'
...
tarantool> box.schema.func.reload("function1_module")
---
- error: Function 'function1_module' does not exist
...
```
| 1.0 | box.schema.func.reload only work with a function name - `box.schema.func.reload()` only work with a function name but the documentation says that it should work with a module name and also without any arguments to reload everything https://tarantool.org/en/doc/1.7/book/box/box_schema.html?highlight=reload#lua-function.box.schema.func.reload
```lua
tarantool> box.schema.func.reload()
---
- error: 'bad argument #1 to ''?'' (string expected, got no value)'
...
tarantool> box.schema.func.reload("function1_module")
---
- error: Function 'function1_module' does not exist
...
```
| design | box schema func reload only work with a function name box schema func reload only work with a function name but the documentation says that it should work with a module name and also without any arguments to reload everything lua tarantool box schema func reload error bad argument to string expected got no value tarantool box schema func reload module error function module does not exist | 1 |
179,702 | 30,285,617,171 | IssuesEvent | 2023-07-08 16:36:38 | hashgraph/hedera-smart-contracts | https://api.github.com/repos/hashgraph/hedera-smart-contracts | opened | [Design] Explore structured Solidity API example and test support | enhancement P2 Epic Design | ### Problem
Solidity has many reserved words (some map to opcodes) that we want to provided coverage and examples for devs
### Solution
Explore the design and necessary implementation steps to support this and update the relay.
Create sub epic tasklist to capture the necessary work
### Alternatives
_No response_ | 1.0 | [Design] Explore structured Solidity API example and test support - ### Problem
Solidity has many reserved words (some map to opcodes) that we want to provided coverage and examples for devs
### Solution
Explore the design and necessary implementation steps to support this and update the relay.
Create sub epic tasklist to capture the necessary work
### Alternatives
_No response_ | design | explore structured solidity api example and test support problem solidity has many reserved words some map to opcodes that we want to provided coverage and examples for devs solution explore the design and necessary implementation steps to support this and update the relay create sub epic tasklist to capture the necessary work alternatives no response | 1 |
124,288 | 16,603,017,632 | IssuesEvent | 2021-06-01 22:24:52 | microsoft/TypeScript | https://api.github.com/repos/microsoft/TypeScript | closed | Type Narrowing with logical OR doesn't work properly | Design Limitation | <!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨
Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!
Please help us by doing the following steps before logging an issue:
* Search: https://github.com/Microsoft/TypeScript/search?type=Issues
* Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ
Please fill in the *entire* template below.
-->
<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:** 3.1.0-dev.201xxxxx
<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
Type Narrowing
Logical OR
**Code**
```ts
// A *self-contained* demonstration of the problem follows...
let foo: { a(): string } | undefined;
let bar: { a(): string } | undefined;
if (foo || bar) {
const val = foo || bar;
val.a(); // This is a compiler error with strictNullChecks enabled
}
```
**Expected behavior:**
val is typed as { a(): string } inside the if block
**Actual behavior:**
val includes undefined type
**Playground Link:** http://www.typescriptlang.org/play/#src=let%20foo%3A%20%7B%20a()%3A%20string%20%7D%20%7C%20undefined%3B%0D%0Alet%20bar%3A%20%7B%20a()%3A%20string%20%7D%20%7C%20undefined%3B%0D%0A%0D%0Aif%20(foo%20%7C%7C%20bar)%20%7B%0D%0A%20%20%20%20const%20val%20%3D%20foo%20%7C%7C%20bar%3B%0D%0A%20%20%20%20val.a()%3B%0D%0A%7D
**Related Issues:** <!-- Did you find other bugs that looked similar? -->
| 1.0 | Type Narrowing with logical OR doesn't work properly - <!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨
Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!
Please help us by doing the following steps before logging an issue:
* Search: https://github.com/Microsoft/TypeScript/search?type=Issues
* Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ
Please fill in the *entire* template below.
-->
<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:** 3.1.0-dev.201xxxxx
<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
Type Narrowing
Logical OR
**Code**
```ts
// A *self-contained* demonstration of the problem follows...
let foo: { a(): string } | undefined;
let bar: { a(): string } | undefined;
if (foo || bar) {
const val = foo || bar;
val.a(); // This is a compiler error with strictNullChecks enabled
}
```
**Expected behavior:**
val is typed as { a(): string } inside the if block
**Actual behavior:**
val includes undefined type
**Playground Link:** http://www.typescriptlang.org/play/#src=let%20foo%3A%20%7B%20a()%3A%20string%20%7D%20%7C%20undefined%3B%0D%0Alet%20bar%3A%20%7B%20a()%3A%20string%20%7D%20%7C%20undefined%3B%0D%0A%0D%0Aif%20(foo%20%7C%7C%20bar)%20%7B%0D%0A%20%20%20%20const%20val%20%3D%20foo%20%7C%7C%20bar%3B%0D%0A%20%20%20%20val.a()%3B%0D%0A%7D
**Related Issues:** <!-- Did you find other bugs that looked similar? -->
| design | type narrowing with logical or doesn t work properly 🚨 stop 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨 half of all issues filed here are duplicates answered in the faq or not appropriate for the bug tracker even if you think you ve found a bug please read the faq first especially the common bugs that aren t bugs section please help us by doing the following steps before logging an issue search read the faq please fill in the entire template below typescript version dev search terms type narrowing logical or code ts a self contained demonstration of the problem follows let foo a string undefined let bar a string undefined if foo bar const val foo bar val a this is a compiler error with strictnullchecks enabled expected behavior val is typed as a string inside the if block actual behavior val includes undefined type playground link related issues | 1 |
61,034 | 7,433,837,780 | IssuesEvent | 2018-03-26 09:00:55 | greatnewcls/HLNLL3FFR3NVETEIL4MMB55N | https://api.github.com/repos/greatnewcls/HLNLL3FFR3NVETEIL4MMB55N | reopened | TzhhJ5mlMzwHgmDQDsWLswzHfuW53Eqz8edCDnqbDP1A3Vel6OuT965m65hnbR8UhDGeXlAUWABYho6oOea5zdL6W389XaaUjU1iG7mab2CRn/2XM69SALIFiwrtDEuATmsldWRxfFTa1j7uDZKBxP2GZJHUfumm/unSqOIcFJs= | design | jZmX6ST7qz4TQcH5HwvyN6mwatRsAIXhb+sB1kzwna4nwWr0TQWDSxF5jPiny/cfuSCZYj5CDBw8syraSbBmSltZWDEVLqN5t/hbIuikXblyaKNCC3CgWOWjI3whgn56dqp7PrBFO4X7BSO6h7gz0T1vGk5w7rQWk1yd0hlUopnUHiHVE2oRRGYAi3xu+iVEArRkh0IYpGvSTZKhHxmYdwK0ZIdCGKRr0k2SoR8ZmHcCtGSHQhika9JNkqEfGZh3ArRkh0IYpGvSTZKhHxmYdzb6FT9A0jE9AzFWbOfnftnZnRB8BEYF7eWWpn6N/BJEsam7dVS0d6F7RcG1yfPs0nnAAt7EO4bERgjE1IcDlnW8MyMsU+EN1dSa3Wws1Xfhw5/8gkaJZmseCee6euqmNz1vGk5w7rQWk1yd0hlUopk9bxpOcO60FpNcndIZVKKZwyQCIDdRU3yTuMYYMlOulbL/TzYlB49qq1Yyudn6kDmcL4SdefbYbhnkerKJbrNtgxN7lRdUds48yjfVr+DfgEGh4Wvo8UYvSC8JBD0C/mLPQPwOy9ZIVrON/r18H6xN+h+G2eX62fuQcx/5j5vQPD1vGk5w7rQWk1yd0hlUopk9bxpOcO60FpNcndIZVKKZsy+b8W0BU54pkhDXatBS7c0+2DG59Df9RIeu8jCIOLpsSjNgcXPg9afP2zBIeYa8q9G305p+E3ggrN4Frjw4CExHeEkHaLHplySAzl9WytI/JCbsugltNjK9ft6ah1qUBTyEJOtTQPHcWXpBjr+FbT1vGk5w7rQWk1yd0hlUopk9bxpOcO60FpNcndIZVKKZg79zK6kk90Rg8T0ePjC16neCKi85G41CGvASl54339lHOY6MiXpSTYh6eayrzDaf2MxIHJEt7jv2yXVncrCnoHZ2wz8yVyAJ4nF9TMNSEd5gcGQDJLBqLGkbYmrNcAl8f6Ys1VVp+Ospl+qqRstcGz1vGk5w7rQWk1yd0hlUopk9bxpOcO60FpNcndIZVKKZkvGG5NT1PsT0c230EQQ1hSzkXcDVtqsLP63FwKpy2FqQbWD0VLvy8ZvOtX8aO2k2sam7dVS0d6F7RcG1yfPs0uKF6PGi5W9UFljvGNiTD6AF0sHkFSOBMAmnvH96JObJPW8aTnDutBaTXJ3SGVSimT1vGk5w7rQWk1yd0hlUopnbiUeGhKFRJsa0ZSqHVfmBxZcuHeZFgHMfNNi0HspsE0LQBxLpD5fICFI3vhblwtzT4V3tOeVD11Y4Nx68hvjIwDPKXIFOO1r0QSDsBQCgFTJ0NeV7Vw6QP7UVJwmOAieFZa1Do7p6kX06rAHkJWiuPW8aTnDutBaTXJ3SGVSimT1vGk5w7rQWk1yd0hlUopmzL5vxbQFTnimSENdq0FLtzT7YMbn0N/1Eh67yMIg4umxKM2Bxc+D1p8/bMEh5hrzv2Nn4Lh0kHLy/dzhV6PuJTEd4SQdosemXJIDOX1bK0v5oCH60lUA+bRfp2cNXuyZ/pizVVWn46ymX6qpGy1wbPW8aTnDutBaTXJ3SGVSimT1vGk5w7rQWk1yd0hlUopmS8Ybk1PU+xPRzbfQRBDWFLORdwNW2qws/rcXAqnLYWkXdQXX8Fom1mbCzEtKZ99exqbt1VLR3oXtFwbXJ8+zSOIWhV87/T96MtKL9gSoycK10kTqsRF659leGG0aAM0M9bxpOcO60FpNcndIZVKKZPW8aTnDutBaTXJ3SGVSimcMkAiA3UVN8k7jGGDJTrpWy/082JQePaqtWMrnZ+pA5nC+EnXn22G4Z5HqyiW6zbT1vGk5w7rQWk1yd0hlUopnC3tpzXGlV2LMplSs2Y0s+URoBaHWkmGdjs/zQzwjo0m3MFTDvrAnYgaFhe/yGI6yMYclmQfYclpp+FsEqpqpjPW8aTnDutBaTXJ3SGVSimToSsCpdGn8dQjEL96I9e2TICNp7M/rr1L2HYsx0xAhsBmo34QDz68dd9T1xw2NB1DHrDUDI8Qpr3pCao8/6GlkoSitD8Fxf4UTAW4Mvrpq8GPiXWn+4WCfBxeEVojkHqqO4diLVm8bgEVbHQdV02n+JqdLm/h0OGgpDUMQuN9iwxJPfXYSXadzN8lu+q4E1FRBCxt74f0dlJy5Kx2Pwiz4= | 1.0 | TzhhJ5mlMzwHgmDQDsWLswzHfuW53Eqz8edCDnqbDP1A3Vel6OuT965m65hnbR8UhDGeXlAUWABYho6oOea5zdL6W389XaaUjU1iG7mab2CRn/2XM69SALIFiwrtDEuATmsldWRxfFTa1j7uDZKBxP2GZJHUfumm/unSqOIcFJs= - jZmX6ST7qz4TQcH5HwvyN6mwatRsAIXhb+sB1kzwna4nwWr0TQWDSxF5jPiny/cfuSCZYj5CDBw8syraSbBmSltZWDEVLqN5t/hbIuikXblyaKNCC3CgWOWjI3whgn56dqp7PrBFO4X7BSO6h7gz0T1vGk5w7rQWk1yd0hlUopnUHiHVE2oRRGYAi3xu+iVEArRkh0IYpGvSTZKhHxmYdwK0ZIdCGKRr0k2SoR8ZmHcCtGSHQhika9JNkqEfGZh3ArRkh0IYpGvSTZKhHxmYdzb6FT9A0jE9AzFWbOfnftnZnRB8BEYF7eWWpn6N/BJEsam7dVS0d6F7RcG1yfPs0nnAAt7EO4bERgjE1IcDlnW8MyMsU+EN1dSa3Wws1Xfhw5/8gkaJZmseCee6euqmNz1vGk5w7rQWk1yd0hlUopk9bxpOcO60FpNcndIZVKKZwyQCIDdRU3yTuMYYMlOulbL/TzYlB49qq1Yyudn6kDmcL4SdefbYbhnkerKJbrNtgxN7lRdUds48yjfVr+DfgEGh4Wvo8UYvSC8JBD0C/mLPQPwOy9ZIVrON/r18H6xN+h+G2eX62fuQcx/5j5vQPD1vGk5w7rQWk1yd0hlUopk9bxpOcO60FpNcndIZVKKZsy+b8W0BU54pkhDXatBS7c0+2DG59Df9RIeu8jCIOLpsSjNgcXPg9afP2zBIeYa8q9G305p+E3ggrN4Frjw4CExHeEkHaLHplySAzl9WytI/JCbsugltNjK9ft6ah1qUBTyEJOtTQPHcWXpBjr+FbT1vGk5w7rQWk1yd0hlUopk9bxpOcO60FpNcndIZVKKZg79zK6kk90Rg8T0ePjC16neCKi85G41CGvASl54339lHOY6MiXpSTYh6eayrzDaf2MxIHJEt7jv2yXVncrCnoHZ2wz8yVyAJ4nF9TMNSEd5gcGQDJLBqLGkbYmrNcAl8f6Ys1VVp+Ospl+qqRstcGz1vGk5w7rQWk1yd0hlUopk9bxpOcO60FpNcndIZVKKZkvGG5NT1PsT0c230EQQ1hSzkXcDVtqsLP63FwKpy2FqQbWD0VLvy8ZvOtX8aO2k2sam7dVS0d6F7RcG1yfPs0uKF6PGi5W9UFljvGNiTD6AF0sHkFSOBMAmnvH96JObJPW8aTnDutBaTXJ3SGVSimT1vGk5w7rQWk1yd0hlUopnbiUeGhKFRJsa0ZSqHVfmBxZcuHeZFgHMfNNi0HspsE0LQBxLpD5fICFI3vhblwtzT4V3tOeVD11Y4Nx68hvjIwDPKXIFOO1r0QSDsBQCgFTJ0NeV7Vw6QP7UVJwmOAieFZa1Do7p6kX06rAHkJWiuPW8aTnDutBaTXJ3SGVSimT1vGk5w7rQWk1yd0hlUopmzL5vxbQFTnimSENdq0FLtzT7YMbn0N/1Eh67yMIg4umxKM2Bxc+D1p8/bMEh5hrzv2Nn4Lh0kHLy/dzhV6PuJTEd4SQdosemXJIDOX1bK0v5oCH60lUA+bRfp2cNXuyZ/pizVVWn46ymX6qpGy1wbPW8aTnDutBaTXJ3SGVSimT1vGk5w7rQWk1yd0hlUopmS8Ybk1PU+xPRzbfQRBDWFLORdwNW2qws/rcXAqnLYWkXdQXX8Fom1mbCzEtKZ99exqbt1VLR3oXtFwbXJ8+zSOIWhV87/T96MtKL9gSoycK10kTqsRF659leGG0aAM0M9bxpOcO60FpNcndIZVKKZPW8aTnDutBaTXJ3SGVSimcMkAiA3UVN8k7jGGDJTrpWy/082JQePaqtWMrnZ+pA5nC+EnXn22G4Z5HqyiW6zbT1vGk5w7rQWk1yd0hlUopnC3tpzXGlV2LMplSs2Y0s+URoBaHWkmGdjs/zQzwjo0m3MFTDvrAnYgaFhe/yGI6yMYclmQfYclpp+FsEqpqpjPW8aTnDutBaTXJ3SGVSimToSsCpdGn8dQjEL96I9e2TICNp7M/rr1L2HYsx0xAhsBmo34QDz68dd9T1xw2NB1DHrDUDI8Qpr3pCao8/6GlkoSitD8Fxf4UTAW4Mvrpq8GPiXWn+4WCfBxeEVojkHqqO4diLVm8bgEVbHQdV02n+JqdLm/h0OGgpDUMQuN9iwxJPfXYSXadzN8lu+q4E1FRBCxt74f0dlJy5Kx2Pwiz4= | design | unsqoicfjs h ospl urobahwkmgdjs jqdlm | 1 |
38,451 | 19,272,056,977 | IssuesEvent | 2021-12-10 07:15:22 | intel/llvm | https://api.github.com/repos/intel/llvm | opened | [CUDA][Gromacs] Suboptimal code generation for templated kernel | bug performance cuda | **Describe the bug**
In case of using templates + constexpr approach for defining SYCL kernels compiler may generate suboptimal (LLVM) code for PTX backend. Such an approach is using in Gromacs to SYCL version.
Performance impact is ~30% of kernel slowdown and ~20% of total benchmark slowdown for Gromacs SYCL version on NVidia GPUs (tested on RTX 2070).
**To Reproduce**
Reproducer is in attachment: [reproducer.zip](https://github.com/intel/llvm/files/7690762/reproducer.zip)
```
$ source <compiler>
$ unzip reproducer.zip
$ cd reproducer
$ ./build.sh
$ SYCL_DEVICE_FILTER=cuda ./reproducer
With template: 0.00357528
Without template: 0.000897871
```
Performance difference for the test is ~4x.
**Environment (please complete the following information):**
- OS: Linux
- Target device and vendor: NVidia RTX2070
- DPC++ version: clang version 14.0.0 (https://github.com/intel/llvm 626682032ac4f711cea9c73715b474c739b99b38)
- Dependencies version: CUDA 11.4
**Additional context**
Workaround for the problem is to declare function as `static`.
| True | [CUDA][Gromacs] Suboptimal code generation for templated kernel - **Describe the bug**
In case of using templates + constexpr approach for defining SYCL kernels compiler may generate suboptimal (LLVM) code for PTX backend. Such an approach is using in Gromacs to SYCL version.
Performance impact is ~30% of kernel slowdown and ~20% of total benchmark slowdown for Gromacs SYCL version on NVidia GPUs (tested on RTX 2070).
**To Reproduce**
Reproducer is in attachment: [reproducer.zip](https://github.com/intel/llvm/files/7690762/reproducer.zip)
```
$ source <compiler>
$ unzip reproducer.zip
$ cd reproducer
$ ./build.sh
$ SYCL_DEVICE_FILTER=cuda ./reproducer
With template: 0.00357528
Without template: 0.000897871
```
Performance difference for the test is ~4x.
**Environment (please complete the following information):**
- OS: Linux
- Target device and vendor: NVidia RTX2070
- DPC++ version: clang version 14.0.0 (https://github.com/intel/llvm 626682032ac4f711cea9c73715b474c739b99b38)
- Dependencies version: CUDA 11.4
**Additional context**
Workaround for the problem is to declare function as `static`.
| non_design | suboptimal code generation for templated kernel describe the bug in case of using templates constexpr approach for defining sycl kernels compiler may generate suboptimal llvm code for ptx backend such an approach is using in gromacs to sycl version performance impact is of kernel slowdown and of total benchmark slowdown for gromacs sycl version on nvidia gpus tested on rtx to reproduce reproducer is in attachment source unzip reproducer zip cd reproducer build sh sycl device filter cuda reproducer with template without template performance difference for the test is environment please complete the following information os linux target device and vendor nvidia dpc version clang version dependencies version cuda additional context workaround for the problem is to declare function as static | 0 |
168,799 | 26,700,081,505 | IssuesEvent | 2023-01-27 13:43:34 | VikeLabs/vikelabs.ca | https://api.github.com/repos/VikeLabs/vikelabs.ca | opened | Rename dashboard routes to make more sense | Development Design | In the future, there may be more dashboards for the user so there's little point in naming the dashboards 3 routes "Member", "Lead" and "Admin". Future development may include more account-accessible pages such as "Blog Posts", "Resume", etc.
To fix this and allow more leeway into future implementations, we can consolidate the 3 dashboard pages into one general dashboard, with separately accessible routes depending on the role. To start, rename the following pages/routes:
- `Member` to `Profile`
- `Lead` to `Project`
- `Admin` to `Moderation`
Make sure route restriction, naming, and route pathing are accounted for. | 1.0 | Rename dashboard routes to make more sense - In the future, there may be more dashboards for the user so there's little point in naming the dashboards 3 routes "Member", "Lead" and "Admin". Future development may include more account-accessible pages such as "Blog Posts", "Resume", etc.
To fix this and allow more leeway into future implementations, we can consolidate the 3 dashboard pages into one general dashboard, with separately accessible routes depending on the role. To start, rename the following pages/routes:
- `Member` to `Profile`
- `Lead` to `Project`
- `Admin` to `Moderation`
Make sure route restriction, naming, and route pathing are accounted for. | design | rename dashboard routes to make more sense in the future there may be more dashboards for the user so there s little point in naming the dashboards routes member lead and admin future development may include more account accessible pages such as blog posts resume etc to fix this and allow more leeway into future implementations we can consolidate the dashboard pages into one general dashboard with separately accessible routes depending on the role to start rename the following pages routes member to profile lead to project admin to moderation make sure route restriction naming and route pathing are accounted for | 1 |
107,954 | 13,533,369,418 | IssuesEvent | 2020-09-16 02:46:28 | psas/liquid-engine-test-stand | https://api.github.com/repos/psas/liquid-engine-test-stand | closed | (1) Acquisition Phase: FEA Analysis and Sizing of Load Cells | design help wanted | There will be four load cells measuring the engine's thrust. The design's measurements are in English units. The force should be applied to the bottom face of the hole that is above the relief cut. The file that needs to be analyzed can be found here: https://github.com/psas/liquid-engine-test-stand/tree/master/SW%20CAD/Test%20Stand%20Assembly Labeled as Loadcell7. The load cell needs to be analyzed for the maximum stress without yielding.
| 1.0 | (1) Acquisition Phase: FEA Analysis and Sizing of Load Cells - There will be four load cells measuring the engine's thrust. The design's measurements are in English units. The force should be applied to the bottom face of the hole that is above the relief cut. The file that needs to be analyzed can be found here: https://github.com/psas/liquid-engine-test-stand/tree/master/SW%20CAD/Test%20Stand%20Assembly Labeled as Loadcell7. The load cell needs to be analyzed for the maximum stress without yielding.
| design | acquisition phase fea analysis and sizing of load cells there will be four load cells measuring the engine s thrust the design s measurements are in english units the force should be applied to the bottom face of the hole that is above the relief cut the file that needs to be analyzed can be found here labeled as the load cell needs to be analyzed for the maximum stress without yielding | 1 |
141,882 | 21,635,960,310 | IssuesEvent | 2022-05-05 14:14:58 | kubeshop/tracetest | https://api.github.com/repos/kubeshop/tracetest | closed | Design for failed test | design | As a USER,
When I click on a test that did not complete properly, I need to see information explaining the state the test failed at
So I know why it failed and have a sense of what I need to do to correct the issue causing the problem | 1.0 | Design for failed test - As a USER,
When I click on a test that did not complete properly, I need to see information explaining the state the test failed at
So I know why it failed and have a sense of what I need to do to correct the issue causing the problem | design | design for failed test as a user when i click on a test that did not complete properly i need to see information explaining the state the test failed at so i know why it failed and have a sense of what i need to do to correct the issue causing the problem | 1 |
277,018 | 24,041,155,999 | IssuesEvent | 2022-09-16 02:02:11 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | closed | [Flaky Test] should be able to create a new tag with ' on the name | [Status] Stale [Type] Flaky Test | <!-- __META_DATA__:{"failedTimes":5,"totalCommits":1,"baseCommit":"610e449c8e9c3697d628a93e099b9c32643c4e7b"} -->
**Flaky test detected. This is an auto-generated issue by GitHub Actions. Please do NOT edit this manually.**
## Test title
should be able to create a new tag with ' on the name
## Test path
`specs/editor/various/taxonomies.test.js`
## Errors
<!-- __TEST_RESULTS_LIST__ -->
<!-- __TEST_RESULT__ --><time datetime="2022-02-15T17:20:52.173Z"><code>[2022-02-15T17:20:52.173Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/1848260289"><code>enhancement/search-block/accessibility-attr</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-03-23T12:30:35.070Z"><code>[2022-03-23T12:30:35.070Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2028246354"><code>update/sidebar-components-help-links</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-03-24T04:19:27.871Z"><code>[2022-03-24T04:19:27.871Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2032150942"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-03-28T11:16:01.274Z"><code>[2022-03-28T11:16:01.274Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2051762578"><code>rnmobile/feature/drag-and-drop-block-draggable-component</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-03-30T04:06:02.699Z"><code>[2022-03-30T04:06:02.699Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2062464929"><code>try/global-styles-skip-block-gap-style-generation</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-04-10T10:26:45.089Z"><code>[2022-04-10T10:26:45.089Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2143499136"><code>try/no-switcher-block-name</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-04-13T11:35:02.214Z"><code>[2022-04-13T11:35:02.214Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2160747441"><code>fix/39999-url-input-id-a11y-fix</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-04-28T20:11:45.648Z"><code>[2022-04-28T20:11:45.648Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2241562594"><code>revert-40701-revert-40659-fix/comment-author-prevent-spam-link-moderation-preview</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-05-14T17:18:26.125Z"><code>[2022-05-14T17:18:26.125Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2324592221"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-05-17T08:52:42.421Z"><code>[2022-05-17T08:52:42.421Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2336947893"><code>update/move-sticky-control-in-separate-file</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-05-26T06:55:18.828Z"><code>[2022-05-26T06:55:18.828Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2389077991"><code>add/flaky-tests-reporter-package</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-05-30T02:36:10.459Z"><code>[2022-05-30T02:36:10.459Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2406249046"><code>fix/gallery-css-gap-order-bug</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-06-19T10:11:47.649Z"><code>[2022-06-19T10:11:47.649Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2515560285"><code>fix/block-settings-menu-controls-check</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-06-23T12:46:54.999Z"><code>[2022-06-23T12:46:54.999Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2549035952"><code>add/strikethrough-shortcut</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><details>
<summary>
<time datetime="2022-09-14T08:40:22.816Z"><code>[2022-09-14T08:40:22.816Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/3051195547"><code>fix/multiple-templates-created-bug</code></a>.
</summary>
```
● Taxonomies › should be able to create a new tag with ' on the name
TypeError: Cannot read property 'click' of null
152 |
153 | // Click the tag input field.
> 154 | await tagInput.click();
| ^
155 |
156 | const tagName = "tag'-" + generateRandomNumber();
157 |
at Object.<anonymous> (specs/editor/various/taxonomies.test.js:154:18)
at runMicrotasks (<anonymous>)
```
</details><!-- /__TEST_RESULT__ -->
<!-- /__TEST_RESULTS_LIST__ -->
| 1.0 | [Flaky Test] should be able to create a new tag with ' on the name - <!-- __META_DATA__:{"failedTimes":5,"totalCommits":1,"baseCommit":"610e449c8e9c3697d628a93e099b9c32643c4e7b"} -->
**Flaky test detected. This is an auto-generated issue by GitHub Actions. Please do NOT edit this manually.**
## Test title
should be able to create a new tag with ' on the name
## Test path
`specs/editor/various/taxonomies.test.js`
## Errors
<!-- __TEST_RESULTS_LIST__ -->
<!-- __TEST_RESULT__ --><time datetime="2022-02-15T17:20:52.173Z"><code>[2022-02-15T17:20:52.173Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/1848260289"><code>enhancement/search-block/accessibility-attr</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-03-23T12:30:35.070Z"><code>[2022-03-23T12:30:35.070Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2028246354"><code>update/sidebar-components-help-links</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-03-24T04:19:27.871Z"><code>[2022-03-24T04:19:27.871Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2032150942"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-03-28T11:16:01.274Z"><code>[2022-03-28T11:16:01.274Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2051762578"><code>rnmobile/feature/drag-and-drop-block-draggable-component</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-03-30T04:06:02.699Z"><code>[2022-03-30T04:06:02.699Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2062464929"><code>try/global-styles-skip-block-gap-style-generation</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-04-10T10:26:45.089Z"><code>[2022-04-10T10:26:45.089Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2143499136"><code>try/no-switcher-block-name</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-04-13T11:35:02.214Z"><code>[2022-04-13T11:35:02.214Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2160747441"><code>fix/39999-url-input-id-a11y-fix</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-04-28T20:11:45.648Z"><code>[2022-04-28T20:11:45.648Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2241562594"><code>revert-40701-revert-40659-fix/comment-author-prevent-spam-link-moderation-preview</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-05-14T17:18:26.125Z"><code>[2022-05-14T17:18:26.125Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2324592221"><code>trunk</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-05-17T08:52:42.421Z"><code>[2022-05-17T08:52:42.421Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2336947893"><code>update/move-sticky-control-in-separate-file</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-05-26T06:55:18.828Z"><code>[2022-05-26T06:55:18.828Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2389077991"><code>add/flaky-tests-reporter-package</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-05-30T02:36:10.459Z"><code>[2022-05-30T02:36:10.459Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2406249046"><code>fix/gallery-css-gap-order-bug</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-06-19T10:11:47.649Z"><code>[2022-06-19T10:11:47.649Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2515560285"><code>fix/block-settings-menu-controls-check</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2022-06-23T12:46:54.999Z"><code>[2022-06-23T12:46:54.999Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/2549035952"><code>add/strikethrough-shortcut</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><details>
<summary>
<time datetime="2022-09-14T08:40:22.816Z"><code>[2022-09-14T08:40:22.816Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/3051195547"><code>fix/multiple-templates-created-bug</code></a>.
</summary>
```
● Taxonomies › should be able to create a new tag with ' on the name
TypeError: Cannot read property 'click' of null
152 |
153 | // Click the tag input field.
> 154 | await tagInput.click();
| ^
155 |
156 | const tagName = "tag'-" + generateRandomNumber();
157 |
at Object.<anonymous> (specs/editor/various/taxonomies.test.js:154:18)
at runMicrotasks (<anonymous>)
```
</details><!-- /__TEST_RESULT__ -->
<!-- /__TEST_RESULTS_LIST__ -->
| non_design | should be able to create a new tag with on the name flaky test detected this is an auto generated issue by github actions please do not edit this manually test title should be able to create a new tag with on the name test path specs editor various taxonomies test js errors test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on a href ● taxonomies › should be able to create a new tag with on the name typeerror cannot read property click of null click the tag input field await taginput click const tagname tag generaterandomnumber at object specs editor various taxonomies test js at runmicrotasks | 0 |
438,331 | 12,626,476,483 | IssuesEvent | 2020-06-14 16:46:03 | Tyresius92/le-chat | https://api.github.com/repos/Tyresius92/le-chat | closed | [Client] Create a Message component | Good First issue Priority: Low Status: Ready to Implement Type: Enhancement/Feature | ### Description
We will need a message component which just displays the content of a message in a vaguely reasonable way. Absolute MVP here.
### Acceptance Criteria
Not worried about whether the background color is different or if its on the left or the right based on if I'm the sender or not. Just a component that takes in `sender`, `messageText`, and `timeSent` props (names are changeable) and renders them out in a vaguely reasonable way. Additional styling can come later once we have a better graph integration. | 1.0 | [Client] Create a Message component - ### Description
We will need a message component which just displays the content of a message in a vaguely reasonable way. Absolute MVP here.
### Acceptance Criteria
Not worried about whether the background color is different or if its on the left or the right based on if I'm the sender or not. Just a component that takes in `sender`, `messageText`, and `timeSent` props (names are changeable) and renders them out in a vaguely reasonable way. Additional styling can come later once we have a better graph integration. | non_design | create a message component description we will need a message component which just displays the content of a message in a vaguely reasonable way absolute mvp here acceptance criteria not worried about whether the background color is different or if its on the left or the right based on if i m the sender or not just a component that takes in sender messagetext and timesent props names are changeable and renders them out in a vaguely reasonable way additional styling can come later once we have a better graph integration | 0 |
95,768 | 12,037,109,296 | IssuesEvent | 2020-04-13 21:08:02 | Princeton-CDH/startwords | https://api.github.com/repos/Princeton-CDH/startwords | closed | Design the article page for mobile + tablet | awaiting review design | must contain:
- all article metadata
- download/view to alternate versions (links)
- main body
- images + icons (at least one image for sampling)
- link style
- quotation style
- contextual note style
- nav | 1.0 | Design the article page for mobile + tablet - must contain:
- all article metadata
- download/view to alternate versions (links)
- main body
- images + icons (at least one image for sampling)
- link style
- quotation style
- contextual note style
- nav | design | design the article page for mobile tablet must contain all article metadata download view to alternate versions links main body images icons at least one image for sampling link style quotation style contextual note style nav | 1 |
120,025 | 15,691,117,382 | IssuesEvent | 2021-03-25 17:28:51 | wellcomecollection/wellcomecollection.org | https://api.github.com/repos/wellcomecollection/wellcomecollection.org | closed | Design and build components to support Library Registration (Digirati) | Project: collections access needs:design new feature | # What is it and who's it for?
Components for the library registration process, working with Ville (UX designer from Digirati)
Background:
https://wellcome.slack.com/archives/C0198JT4GTG/p1602236258085200
Indicative components:
https://preview.uxpin.com/775868669d3d6ccb455fe44726e86c875921efc6#/pages/132938583/simulate/sitemap?mode=i
- Link/button
- Delete button
- Login Divider
- Form label
- Neutral message
- Text input field: issue with colour contrast
## Acceptance criteria
- [ ] Components added to Cardigan
- [ ] Components pass accessibility tests
| 1.0 | Design and build components to support Library Registration (Digirati) - # What is it and who's it for?
Components for the library registration process, working with Ville (UX designer from Digirati)
Background:
https://wellcome.slack.com/archives/C0198JT4GTG/p1602236258085200
Indicative components:
https://preview.uxpin.com/775868669d3d6ccb455fe44726e86c875921efc6#/pages/132938583/simulate/sitemap?mode=i
- Link/button
- Delete button
- Login Divider
- Form label
- Neutral message
- Text input field: issue with colour contrast
## Acceptance criteria
- [ ] Components added to Cardigan
- [ ] Components pass accessibility tests
| design | design and build components to support library registration digirati what is it and who s it for components for the library registration process working with ville ux designer from digirati background indicative components link button delete button login divider form label neutral message text input field issue with colour contrast acceptance criteria components added to cardigan components pass accessibility tests | 1 |
230,026 | 25,408,524,793 | IssuesEvent | 2022-11-22 16:59:45 | OriginProtocol/website-frontend | https://api.github.com/repos/OriginProtocol/website-frontend | closed | Article page: HTML content sanitization | P1 Security | We are using CKEditor to create HTML content on Strapi.
The client then pulls it and displays it on the site using __dangerouslyInsetHTML.
There is a potential risk of an XSS in case one of the CMS admin user account getting hacked then the hacker could insert a malicious script in the content.
To guard against this, the client should sanitize the HTML we get from Strapi to only allow a whitelist of HTML tags. | True | Article page: HTML content sanitization - We are using CKEditor to create HTML content on Strapi.
The client then pulls it and displays it on the site using __dangerouslyInsetHTML.
There is a potential risk of an XSS in case one of the CMS admin user account getting hacked then the hacker could insert a malicious script in the content.
To guard against this, the client should sanitize the HTML we get from Strapi to only allow a whitelist of HTML tags. | non_design | article page html content sanitization we are using ckeditor to create html content on strapi the client then pulls it and displays it on the site using dangerouslyinsethtml there is a potential risk of an xss in case one of the cms admin user account getting hacked then the hacker could insert a malicious script in the content to guard against this the client should sanitize the html we get from strapi to only allow a whitelist of html tags | 0 |
414,892 | 28,008,685,903 | IssuesEvent | 2023-03-27 16:57:25 | insightsengineering/rtables | https://api.github.com/repos/insightsengineering/rtables | opened | Function documentation could have a "seealso" structure based on bookdown reference page | enhancement discussion documentation sme | This is a suggestion more than anything because it can be a useful way to avoid stand-alone doc pages that are very difficult to find or discover. Of course, the structure is already somehow present. We might bring it towards a more polished and complete state if needed. | 1.0 | Function documentation could have a "seealso" structure based on bookdown reference page - This is a suggestion more than anything because it can be a useful way to avoid stand-alone doc pages that are very difficult to find or discover. Of course, the structure is already somehow present. We might bring it towards a more polished and complete state if needed. | non_design | function documentation could have a seealso structure based on bookdown reference page this is a suggestion more than anything because it can be a useful way to avoid stand alone doc pages that are very difficult to find or discover of course the structure is already somehow present we might bring it towards a more polished and complete state if needed | 0 |
126,821 | 17,110,581,909 | IssuesEvent | 2021-07-10 07:43:17 | hal-shu-sato/apm | https://api.github.com/repos/hal-shu-sato/apm | closed | Change the color of the button on success | Feedback: enhancement Type: design Type: improvement | ## Is your feature request related to a problem? Please describe.
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
It is difficult to know if the program has been successfully executed.
## Describe the solution you'd like
<!-- A clear and concise description of what you want to happen. -->
Change the color of the button on success.
| 1.0 | Change the color of the button on success - ## Is your feature request related to a problem? Please describe.
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
It is difficult to know if the program has been successfully executed.
## Describe the solution you'd like
<!-- A clear and concise description of what you want to happen. -->
Change the color of the button on success.
| design | change the color of the button on success is your feature request related to a problem please describe it is difficult to know if the program has been successfully executed describe the solution you d like change the color of the button on success | 1 |
399,101 | 11,742,761,978 | IssuesEvent | 2020-03-12 02:00:11 | grpc/grpc | https://api.github.com/repos/grpc/grpc | closed | Unexpected delay(bug) for newer grpc version when issuing rpc frequently | kind/bug lang/c++ priority/P2 | <!--
This form is for bug reports and feature requests ONLY!
For general questions and troubleshooting, please ask/look for answers here:
- grpc.io mailing list: https://groups.google.com/forum/#!forum/grpc-io
- StackOverflow, with "grpc" tag: https://stackoverflow.com/questions/tagged/grpc
Issues specific to *grpc-java*, *grpc-go*, *grpc-node*, *grpc-dart*, *grpc-web* should be created in the repository they belong to (e.g. https://github.com/grpc/grpc-LANGUAGE/issues/new)
-->
### What version of gRPC and what language are you using?
grpc 20, cpp
### What operating system (Linux, Windows,...) and version?
ubuntu 16.04.4
### What runtime / compiler are you using (e.g. python version or version of gcc)
gcc 6.5.0
### What did you do?
My client includes several stubs to maintain rpc with two servers, the client may issue rpc requests to different servers at the same time.
### What did you expect to see?
I think maintaining multi stubs for different destination is quite common, they should not affect each other.
### What did you see instead?
I find when changing from one stub to another, it takes 10 seconds to complete the second rpc request, but things will be fine if the second stub is once used. At first I thought it would be my misuse of stubs, but when i try to use only one stub to issue many rpc calls sequentially, the delay still happens for the first time call sometimes.
Then I thought my code has problem and changed to run the example helloword provided from the repo. I found that if the client program is run too frequently in terminal, the 10-seconds delay also happens. So far this happens for both grpc version 19 and version 20(I only tested this two version), and the client program is test on three different ubuntu machines, all encountered the delay.
However, this **delay does not happen** when i changed to early grpc version [release-0_14](https://github.com/grpc/grpc/tree/release-0_14/), both my code and the helloworld perfectly worked without 10-seconds delay | 1.0 | Unexpected delay(bug) for newer grpc version when issuing rpc frequently - <!--
This form is for bug reports and feature requests ONLY!
For general questions and troubleshooting, please ask/look for answers here:
- grpc.io mailing list: https://groups.google.com/forum/#!forum/grpc-io
- StackOverflow, with "grpc" tag: https://stackoverflow.com/questions/tagged/grpc
Issues specific to *grpc-java*, *grpc-go*, *grpc-node*, *grpc-dart*, *grpc-web* should be created in the repository they belong to (e.g. https://github.com/grpc/grpc-LANGUAGE/issues/new)
-->
### What version of gRPC and what language are you using?
grpc 20, cpp
### What operating system (Linux, Windows,...) and version?
ubuntu 16.04.4
### What runtime / compiler are you using (e.g. python version or version of gcc)
gcc 6.5.0
### What did you do?
My client includes several stubs to maintain rpc with two servers, the client may issue rpc requests to different servers at the same time.
### What did you expect to see?
I think maintaining multi stubs for different destination is quite common, they should not affect each other.
### What did you see instead?
I find when changing from one stub to another, it takes 10 seconds to complete the second rpc request, but things will be fine if the second stub is once used. At first I thought it would be my misuse of stubs, but when i try to use only one stub to issue many rpc calls sequentially, the delay still happens for the first time call sometimes.
Then I thought my code has problem and changed to run the example helloword provided from the repo. I found that if the client program is run too frequently in terminal, the 10-seconds delay also happens. So far this happens for both grpc version 19 and version 20(I only tested this two version), and the client program is test on three different ubuntu machines, all encountered the delay.
However, this **delay does not happen** when i changed to early grpc version [release-0_14](https://github.com/grpc/grpc/tree/release-0_14/), both my code and the helloworld perfectly worked without 10-seconds delay | non_design | unexpected delay bug for newer grpc version when issuing rpc frequently this form is for bug reports and feature requests only for general questions and troubleshooting please ask look for answers here grpc io mailing list stackoverflow with grpc tag issues specific to grpc java grpc go grpc node grpc dart grpc web should be created in the repository they belong to e g what version of grpc and what language are you using grpc cpp what operating system linux windows and version ubuntu what runtime compiler are you using e g python version or version of gcc gcc what did you do my client includes several stubs to maintain rpc with two servers the client may issue rpc requests to different servers at the same time what did you expect to see i think maintaining multi stubs for different destination is quite common they should not affect each other what did you see instead i find when changing from one stub to another it takes seconds to complete the second rpc request but things will be fine if the second stub is once used at first i thought it would be my misuse of stubs but when i try to use only one stub to issue many rpc calls sequentially the delay still happens for the first time call sometimes then i thought my code has problem and changed to run the example helloword provided from the repo i found that if the client program is run too frequently in terminal the seconds delay also happens so far this happens for both grpc version and version i only tested this two version and the client program is test on three different ubuntu machines all encountered the delay however this delay does not happen when i changed to early grpc version both my code and the helloworld perfectly worked without seconds delay | 0 |
87,883 | 11,008,088,138 | IssuesEvent | 2019-12-04 09:50:52 | microsoft/vscode | https://api.github.com/repos/microsoft/vscode | closed | GIT isn't recognized in VsCode | *as-designed git |
Issue Type: <b>Bug</b>
Install vscode
install git using brew
edit settings.json and add
"git.enabled": true,
"git.path": "/usr/local/bin/git"
restart vscode
hit Ctrl+shift+G
Vscode tells me the following:
"No source control providers registered."
VS Code version: Code 1.40.2 (f359dd69833dd8800b54d458f6d37ab7c78df520, 2019-11-25T14:52:45.129Z)
OS version: Darwin x64 18.7.0
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-7660U CPU @ 2.50GHz (4 x 2500)|
|GPU Status|2d_canvas: enabled<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>oop_rasterization: disabled_off<br>protected_video_decode: unavailable_off<br>rasterization: enabled<br>skia_renderer: disabled_off<br>surface_control: disabled_off<br>surface_synchronization: enabled_on<br>video_decode: enabled<br>viz_display_compositor: enabled_on<br>viz_hit_test_surface_layer: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|2, 2, 2|
|Memory (System)|16.00GB (0.45GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (11)</summary>
Extension|Author (truncated)|Version
---|---|---
terraform|mau|1.4.0
vscode-azurefunctions|ms-|0.20.0
azure-account|ms-|0.8.7
java|red|0.53.1
vscode-xml|red|0.9.1
vscodeintellicode|Vis|1.2.0
vscode-java-debug|vsc|0.23.0
vscode-java-dependency|vsc|0.6.0
vscode-java-pack|vsc|0.8.1
vscode-java-test|vsc|0.21.0
vscode-maven|vsc|0.20.0
</details>
<!-- generated by issue reporter --> | 1.0 | GIT isn't recognized in VsCode -
Issue Type: <b>Bug</b>
Install vscode
install git using brew
edit settings.json and add
"git.enabled": true,
"git.path": "/usr/local/bin/git"
restart vscode
hit Ctrl+shift+G
Vscode tells me the following:
"No source control providers registered."
VS Code version: Code 1.40.2 (f359dd69833dd8800b54d458f6d37ab7c78df520, 2019-11-25T14:52:45.129Z)
OS version: Darwin x64 18.7.0
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-7660U CPU @ 2.50GHz (4 x 2500)|
|GPU Status|2d_canvas: enabled<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>oop_rasterization: disabled_off<br>protected_video_decode: unavailable_off<br>rasterization: enabled<br>skia_renderer: disabled_off<br>surface_control: disabled_off<br>surface_synchronization: enabled_on<br>video_decode: enabled<br>viz_display_compositor: enabled_on<br>viz_hit_test_surface_layer: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|2, 2, 2|
|Memory (System)|16.00GB (0.45GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (11)</summary>
Extension|Author (truncated)|Version
---|---|---
terraform|mau|1.4.0
vscode-azurefunctions|ms-|0.20.0
azure-account|ms-|0.8.7
java|red|0.53.1
vscode-xml|red|0.9.1
vscodeintellicode|Vis|1.2.0
vscode-java-debug|vsc|0.23.0
vscode-java-dependency|vsc|0.6.0
vscode-java-pack|vsc|0.8.1
vscode-java-test|vsc|0.21.0
vscode-maven|vsc|0.20.0
</details>
<!-- generated by issue reporter --> | design | git isn t recognized in vscode issue type bug install vscode install git using brew edit settings json and add git enabled true git path usr local bin git restart vscode hit ctrl shift g vscode tells me the following no source control providers registered vs code version code os version darwin system info item value cpus intel r core tm cpu x gpu status canvas enabled flash enabled flash enabled flash baseline enabled gpu compositing enabled metal disabled off multiple raster threads enabled on oop rasterization disabled off protected video decode unavailable off rasterization enabled skia renderer disabled off surface control disabled off surface synchronization enabled on video decode enabled viz display compositor enabled on viz hit test surface layer disabled off webgl enabled enabled load avg memory system free process argv screen reader no vm extensions extension author truncated version terraform mau vscode azurefunctions ms azure account ms java red vscode xml red vscodeintellicode vis vscode java debug vsc vscode java dependency vsc vscode java pack vsc vscode java test vsc vscode maven vsc | 1 |
284,535 | 21,443,571,500 | IssuesEvent | 2022-04-25 02:07:57 | jaisonschmidt/boilerplate-react-webpack | https://api.github.com/repos/jaisonschmidt/boilerplate-react-webpack | opened | Improve documentation | documentation enhancement Task | I have installed a lot of libraries and created new npm commands. I need to improve documentation with cool features and documenting npm commands. | 1.0 | Improve documentation - I have installed a lot of libraries and created new npm commands. I need to improve documentation with cool features and documenting npm commands. | non_design | improve documentation i have installed a lot of libraries and created new npm commands i need to improve documentation with cool features and documenting npm commands | 0 |
105,647 | 13,203,760,782 | IssuesEvent | 2020-08-14 14:43:21 | tektoncd/pipeline | https://api.github.com/repos/tektoncd/pipeline | closed | Tracking pipeline and task execution time as well as controller time | design help wanted lifecycle/rotten | ## Expected Behavior
As a developer of build-pipeline, being able to see an entire trace of someones pipeline execution as well as the execution context through the pipeline controller would help diagnose performance issues and give visibility into what is going on
It should be possible to query for metrics around:
* How long Tasks of a particular type are taking
* How long Steps of a particular Task are taking
* Number of TaskRuns and PipelineRuns being created (tied to the corresponding Task/Pipeline)
The mechanism that we use to collect metrics should not hold state globally, i.e. it should be possible to configure the metrics collecting mechanism in one section of the code without affecting other sections (the one currently used in knative/pkg is global, e.g. see [this code](https://github.com/knative/pkg/blob/fcb065651464d2668b5dffbfcdd1792bb732b86f/test/logging/logging.go#L128)).
## Actual Behavior
Some of this data is available via `startedAt` and `finishedAt` in the status fields, however it is not queryable, and we would like more data points.
## Additional Info
Having this information would be extremely valuable as it would quickly highlight points of interest in the pipeline controller and give visibility into the entire system. | 1.0 | Tracking pipeline and task execution time as well as controller time - ## Expected Behavior
As a developer of build-pipeline, being able to see an entire trace of someones pipeline execution as well as the execution context through the pipeline controller would help diagnose performance issues and give visibility into what is going on
It should be possible to query for metrics around:
* How long Tasks of a particular type are taking
* How long Steps of a particular Task are taking
* Number of TaskRuns and PipelineRuns being created (tied to the corresponding Task/Pipeline)
The mechanism that we use to collect metrics should not hold state globally, i.e. it should be possible to configure the metrics collecting mechanism in one section of the code without affecting other sections (the one currently used in knative/pkg is global, e.g. see [this code](https://github.com/knative/pkg/blob/fcb065651464d2668b5dffbfcdd1792bb732b86f/test/logging/logging.go#L128)).
## Actual Behavior
Some of this data is available via `startedAt` and `finishedAt` in the status fields, however it is not queryable, and we would like more data points.
## Additional Info
Having this information would be extremely valuable as it would quickly highlight points of interest in the pipeline controller and give visibility into the entire system. | design | tracking pipeline and task execution time as well as controller time expected behavior as a developer of build pipeline being able to see an entire trace of someones pipeline execution as well as the execution context through the pipeline controller would help diagnose performance issues and give visibility into what is going on it should be possible to query for metrics around how long tasks of a particular type are taking how long steps of a particular task are taking number of taskruns and pipelineruns being created tied to the corresponding task pipeline the mechanism that we use to collect metrics should not hold state globally i e it should be possible to configure the metrics collecting mechanism in one section of the code without affecting other sections the one currently used in knative pkg is global e g see actual behavior some of this data is available via startedat and finishedat in the status fields however it is not queryable and we would like more data points additional info having this information would be extremely valuable as it would quickly highlight points of interest in the pipeline controller and give visibility into the entire system | 1 |
128,690 | 17,600,239,942 | IssuesEvent | 2021-08-17 10:54:49 | hoprnet/hoprnet-org | https://api.github.com/repos/hoprnet/hoprnet-org | closed | Link is broken | workflow:new issue type:design | # Page
<!--- Tell us which page this is happening -->
<!--- e.g. Home (/) -->
Home page, under "Use Cases" headline.
# Current behavior
<!--- Tell us what's currently the issue. -->
<!--- e.g. The menu has the wrong right spacings on an iPhone6 -->
"HOPR protocol" has broken link: https://hoprnet.org/layer0-data-privacy#how | 1.0 | Link is broken - # Page
<!--- Tell us which page this is happening -->
<!--- e.g. Home (/) -->
Home page, under "Use Cases" headline.
# Current behavior
<!--- Tell us what's currently the issue. -->
<!--- e.g. The menu has the wrong right spacings on an iPhone6 -->
"HOPR protocol" has broken link: https://hoprnet.org/layer0-data-privacy#how | design | link is broken page home page under use cases headline current behavior hopr protocol has broken link | 1 |
331,731 | 10,076,408,371 | IssuesEvent | 2019-07-24 16:10:15 | SparkDevNetwork/Rock | https://api.github.com/repos/SparkDevNetwork/Rock | closed | Typo: Bio block 'Business Detail Page' help text | Priority: Low Status: Confirmed Topic: UI Type: Bug | Go to person bio page, modify the top Bio block, view the help text for the **Business Detail Page** field.
Help text reads: 'The page to redirect user to if a business is is requested.'
Correct duplicate 'is'.
While you're there - add a question mark to the end of the help text on the Display Graduation field, and Enable Call Origination. (And full stop on help text for Social Media Category.')
### Versions
demo site:
Rock Version: Rock McKinley 8.8 (1.8.8.3)
Client Culture Setting: en-NZ
| 1.0 | Typo: Bio block 'Business Detail Page' help text - Go to person bio page, modify the top Bio block, view the help text for the **Business Detail Page** field.
Help text reads: 'The page to redirect user to if a business is is requested.'
Correct duplicate 'is'.
While you're there - add a question mark to the end of the help text on the Display Graduation field, and Enable Call Origination. (And full stop on help text for Social Media Category.')
### Versions
demo site:
Rock Version: Rock McKinley 8.8 (1.8.8.3)
Client Culture Setting: en-NZ
| non_design | typo bio block business detail page help text go to person bio page modify the top bio block view the help text for the business detail page field help text reads the page to redirect user to if a business is is requested correct duplicate is while you re there add a question mark to the end of the help text on the display graduation field and enable call origination and full stop on help text for social media category versions demo site rock version rock mckinley client culture setting en nz | 0 |
58,020 | 7,112,817,485 | IssuesEvent | 2018-01-17 18:17:08 | phetsims/masses-and-springs | https://api.github.com/repos/phetsims/masses-and-springs | closed | Reducing floating boxes | design:polish meeting:design | @arouinfar here are some suggestions from @emily-phet - might be worth discussing at a future design meeting. I think there are a few places we could reduce the feeling of many floating control boxes (eg the spring constant controls may not even need a box, also possible the check boxes do not need a box).
@emily-phet said:
> I was looking again at Masses and Springs. I think it looks a bit overwhelming to me, in large part because each screen has so many different floating boxes. You guys know about “subitizing” I think (human’s ability to accurately know the the number of a small group of objects without individually counting). Most people are pretty good at subitizing up to at least four (e.g., abacus’ are designed to allow calculations without subitizing beyond five).
>
> When groups of things get larger than four-ish, I think they have the impression of…a lot. Which is not a good thing for sim control panels. In some screens of Masses and Springs, you can have as many as seven floating grey boxes. This feels like “a lot” and I feel like I have to kind of "brace myself" as I dig into figuring out what each one is for. I think if you visually grouped more of these floating boxes, it would help a lot. For example, instead of individual floating boxes along the right side, these could be grouped into one (multicomponent) grey panel. You could also group by having the background colors of some of the boxes be something besides grey. For example, the grey boxes holding the “spring constant” sliders for each spring could be each have the same non-grey color. Maybe that color could also be used for the little grey bar thing that holds the springs up, so that whole top panel piece looks like one thing, distinct from the side panels.
| 2.0 | Reducing floating boxes - @arouinfar here are some suggestions from @emily-phet - might be worth discussing at a future design meeting. I think there are a few places we could reduce the feeling of many floating control boxes (eg the spring constant controls may not even need a box, also possible the check boxes do not need a box).
@emily-phet said:
> I was looking again at Masses and Springs. I think it looks a bit overwhelming to me, in large part because each screen has so many different floating boxes. You guys know about “subitizing” I think (human’s ability to accurately know the the number of a small group of objects without individually counting). Most people are pretty good at subitizing up to at least four (e.g., abacus’ are designed to allow calculations without subitizing beyond five).
>
> When groups of things get larger than four-ish, I think they have the impression of…a lot. Which is not a good thing for sim control panels. In some screens of Masses and Springs, you can have as many as seven floating grey boxes. This feels like “a lot” and I feel like I have to kind of "brace myself" as I dig into figuring out what each one is for. I think if you visually grouped more of these floating boxes, it would help a lot. For example, instead of individual floating boxes along the right side, these could be grouped into one (multicomponent) grey panel. You could also group by having the background colors of some of the boxes be something besides grey. For example, the grey boxes holding the “spring constant” sliders for each spring could be each have the same non-grey color. Maybe that color could also be used for the little grey bar thing that holds the springs up, so that whole top panel piece looks like one thing, distinct from the side panels.
| design | reducing floating boxes arouinfar here are some suggestions from emily phet might be worth discussing at a future design meeting i think there are a few places we could reduce the feeling of many floating control boxes eg the spring constant controls may not even need a box also possible the check boxes do not need a box emily phet said i was looking again at masses and springs i think it looks a bit overwhelming to me in large part because each screen has so many different floating boxes you guys know about “subitizing” i think human’s ability to accurately know the the number of a small group of objects without individually counting most people are pretty good at subitizing up to at least four e g abacus’ are designed to allow calculations without subitizing beyond five when groups of things get larger than four ish i think they have the impression of…a lot which is not a good thing for sim control panels in some screens of masses and springs you can have as many as seven floating grey boxes this feels like “a lot” and i feel like i have to kind of brace myself as i dig into figuring out what each one is for i think if you visually grouped more of these floating boxes it would help a lot for example instead of individual floating boxes along the right side these could be grouped into one multicomponent grey panel you could also group by having the background colors of some of the boxes be something besides grey for example the grey boxes holding the “spring constant” sliders for each spring could be each have the same non grey color maybe that color could also be used for the little grey bar thing that holds the springs up so that whole top panel piece looks like one thing distinct from the side panels | 1 |
175,739 | 27,968,409,738 | IssuesEvent | 2023-03-24 22:07:23 | LeventErkok/sbv | https://api.github.com/repos/LeventErkok/sbv | closed | Support abduction in CVC5 | Design exploration | These days CVC5 can produce abducts. Would be cool to see if we can support this in SBV, at least as a technology preview. | 1.0 | Support abduction in CVC5 - These days CVC5 can produce abducts. Would be cool to see if we can support this in SBV, at least as a technology preview. | design | support abduction in these days can produce abducts would be cool to see if we can support this in sbv at least as a technology preview | 1 |
181,223 | 30,641,968,314 | IssuesEvent | 2023-07-24 23:06:58 | MetaMask/metamask-extension | https://api.github.com/repos/MetaMask/metamask-extension | opened | Replace deprecated Checkbox component with Checkbox from the component-library | good first issue team-design-system | ### Description
Currently, the extension is using an outdated `Checkbox` component, which needs to be replaced with the new `Checkbox` component.
This is a massive undertaking by itself and creating a single PR would be too large. Smaller PRs can be submitted against this issue to ensure easier review and gradual improvements.
### Technical Details
- Replace instances of `Checkbox` component (`ui/components/ui/check-box/check-box.component.js`) with `Checkbox` component (`ui/components/component-library/checkbox/checkbox.tsx`)
- Component APIs are slightly different so ensure all props have been migrated appropriately
### Acceptance Criteria
- Instances of Checkbox component are completely replaced with the new Checkbox component
- The component APIs are updated to reflect the changes in the new Checkbox component and there is no functional changes or visual regression
- Each Pull Request (PR) should include **no more than 3 files**
- The code changes should pass Jest tests, linting, and Storybook without any errors.
- The PR must include before and after screenshots of the UI to ensure there are no visual regressions.
If the acceptance criteria is not met, PRs may be closed.
### Difficulty: Intermediate
Good first issue for: External contributors who are familiar with running the extension locally, have knowledge of React, component props, Jest tests, linting, and Storybook, and want to contribute to improving the cohesiveness of UI in the extension
| 1.0 | Replace deprecated Checkbox component with Checkbox from the component-library - ### Description
Currently, the extension is using an outdated `Checkbox` component, which needs to be replaced with the new `Checkbox` component.
This is a massive undertaking by itself and creating a single PR would be too large. Smaller PRs can be submitted against this issue to ensure easier review and gradual improvements.
### Technical Details
- Replace instances of `Checkbox` component (`ui/components/ui/check-box/check-box.component.js`) with `Checkbox` component (`ui/components/component-library/checkbox/checkbox.tsx`)
- Component APIs are slightly different so ensure all props have been migrated appropriately
### Acceptance Criteria
- Instances of Checkbox component are completely replaced with the new Checkbox component
- The component APIs are updated to reflect the changes in the new Checkbox component and there is no functional changes or visual regression
- Each Pull Request (PR) should include **no more than 3 files**
- The code changes should pass Jest tests, linting, and Storybook without any errors.
- The PR must include before and after screenshots of the UI to ensure there are no visual regressions.
If the acceptance criteria is not met, PRs may be closed.
### Difficulty: Intermediate
Good first issue for: External contributors who are familiar with running the extension locally, have knowledge of React, component props, Jest tests, linting, and Storybook, and want to contribute to improving the cohesiveness of UI in the extension
| design | replace deprecated checkbox component with checkbox from the component library description currently the extension is using an outdated checkbox component which needs to be replaced with the new checkbox component this is a massive undertaking by itself and creating a single pr would be too large smaller prs can be submitted against this issue to ensure easier review and gradual improvements technical details replace instances of checkbox component ui components ui check box check box component js with checkbox component ui components component library checkbox checkbox tsx component apis are slightly different so ensure all props have been migrated appropriately acceptance criteria instances of checkbox component are completely replaced with the new checkbox component the component apis are updated to reflect the changes in the new checkbox component and there is no functional changes or visual regression each pull request pr should include no more than files the code changes should pass jest tests linting and storybook without any errors the pr must include before and after screenshots of the ui to ensure there are no visual regressions if the acceptance criteria is not met prs may be closed difficulty intermediate good first issue for external contributors who are familiar with running the extension locally have knowledge of react component props jest tests linting and storybook and want to contribute to improving the cohesiveness of ui in the extension | 1 |
199,598 | 15,050,822,928 | IssuesEvent | 2021-02-03 13:22:55 | packit/packit-service | https://api.github.com/repos/packit/packit-service | closed | No Epel-8 compose in Testing Farm | testing-farm | Sentry Issue: [PACKIT-SERVICE-343](https://sentry.io/organizations/red-hat-0p/issues/2185006468/?referrer=github_integration)
```
$ http https://api.dev.testing-farm.io/v0.1/composes
{"composes": [
{"name": "Fedora-31"},
{"name": "Fedora-32"},
{"name": "Fedora-33"},
{"name": "Fedora-Rawhide"}
]}
``` | 1.0 | No Epel-8 compose in Testing Farm - Sentry Issue: [PACKIT-SERVICE-343](https://sentry.io/organizations/red-hat-0p/issues/2185006468/?referrer=github_integration)
```
$ http https://api.dev.testing-farm.io/v0.1/composes
{"composes": [
{"name": "Fedora-31"},
{"name": "Fedora-32"},
{"name": "Fedora-33"},
{"name": "Fedora-Rawhide"}
]}
``` | non_design | no epel compose in testing farm sentry issue http composes name fedora name fedora name fedora name fedora rawhide | 0 |
266,045 | 23,219,493,076 | IssuesEvent | 2022-08-02 16:47:01 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | closed | Query Loop block displays incorrect posts when inheriting template query and filtering multiple terms per taxonomy | [Type] Bug Needs Testing [Block] Query Loop | ### Description
The Query Loop block doesn't display the correct list of posts when inheriting query from template and filtering multiple terms per taxonomy ( e.g.: ?category_name=block,media ). It **only** shows posts assigned to the first term. Using the same url and switching to a classic theme ( e.g.: TwentyTwentyOne ) the correct list of posts is displayed.
### Step-by-step reproduction instructions
1. Activate a FSE theme ( e.g.: Blockbase )
2. Add taxonomy filter parameters to your WordPress URL - multiple terms for one taxonomy (e.g: `?category_name=block,media` or `/category/block,media/`). Make sure there are posts that are assigned to **each and only one term** of the chosen terms ( e.g.: Post `A` has **only** category `block` and Post `B` has **only** category `media` ).
3. Observe the list of posts being displayed. E.g: **Only Post** `A` is being displayed
4. Flip the terms in the URL ( e.g.: `/category/media,block/` )
5. Observe the list of posts being displayed. E.g: **Only Post** `B` is being displayed
6. Copy the URL and activate a classic non-FSE theme ( e.g.: TwentyTwentyOne )
7. Reload the copied URL ( e.g.: `/category/media,block/` )
8. Observe the list of posts being displayed. E.g: **Post** `A` **and Post** `B` are being displayed
### Screenshots, screen recording, code snippet
The issue is caused by the new local `WP_Query` and the way the `$query_args` array is created when inheriting the query in the function `gutenberg_render_block_core_post_template` ( plugins/gutenberg/build/block-library/blocks/post-template.php:17 ). The `$query_args` array is based on the global `$wp_query->query_vars`. Those query vars have been parsed and now have **only one** taxonomy term set when filtering for multiple ones (e.g.: `/category/block,media/` results in `$query_vars['category_name']=> 'block']` ) and thus the new query filters only by one category.
This also creates issues with pagination. The pagination is based on the correct amount of posts which can result in an empty last page.
The Query Loop works as expected if the `$query_args` are based on the global `$wp_query->query` which still holds all terms.
Adding `$query_args = $wp_query->query;` At the end of the `if ( $use_global_query ) {` block on line 35 of `plugins/gutenberg/build/block-library/blocks/post-template.php`.
```php
function gutenberg_render_block_core_post_template( $attributes, $content, $block ) {
...
if ( $use_global_query ) {
global $wp_query;
...
$query_args = $wp_query->query;
}
```
Adding this line of code fixes the pagination as well.
The code comments mention the need to unset the `offset` param which would have to be refactored if still necessary.
Hope that helps, either as a fix or at least a start!
### Environment info
WordPress 5.8.1
Gutenberg 11.5.1
### Please confirm that you have searched existing issues in the repo.
Yes
### Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes | 1.0 | Query Loop block displays incorrect posts when inheriting template query and filtering multiple terms per taxonomy - ### Description
The Query Loop block doesn't display the correct list of posts when inheriting query from template and filtering multiple terms per taxonomy ( e.g.: ?category_name=block,media ). It **only** shows posts assigned to the first term. Using the same url and switching to a classic theme ( e.g.: TwentyTwentyOne ) the correct list of posts is displayed.
### Step-by-step reproduction instructions
1. Activate a FSE theme ( e.g.: Blockbase )
2. Add taxonomy filter parameters to your WordPress URL - multiple terms for one taxonomy (e.g: `?category_name=block,media` or `/category/block,media/`). Make sure there are posts that are assigned to **each and only one term** of the chosen terms ( e.g.: Post `A` has **only** category `block` and Post `B` has **only** category `media` ).
3. Observe the list of posts being displayed. E.g: **Only Post** `A` is being displayed
4. Flip the terms in the URL ( e.g.: `/category/media,block/` )
5. Observe the list of posts being displayed. E.g: **Only Post** `B` is being displayed
6. Copy the URL and activate a classic non-FSE theme ( e.g.: TwentyTwentyOne )
7. Reload the copied URL ( e.g.: `/category/media,block/` )
8. Observe the list of posts being displayed. E.g: **Post** `A` **and Post** `B` are being displayed
### Screenshots, screen recording, code snippet
The issue is caused by the new local `WP_Query` and the way the `$query_args` array is created when inheriting the query in the function `gutenberg_render_block_core_post_template` ( plugins/gutenberg/build/block-library/blocks/post-template.php:17 ). The `$query_args` array is based on the global `$wp_query->query_vars`. Those query vars have been parsed and now have **only one** taxonomy term set when filtering for multiple ones (e.g.: `/category/block,media/` results in `$query_vars['category_name']=> 'block']` ) and thus the new query filters only by one category.
This also creates issues with pagination. The pagination is based on the correct amount of posts which can result in an empty last page.
The Query Loop works as expected if the `$query_args` are based on the global `$wp_query->query` which still holds all terms.
Adding `$query_args = $wp_query->query;` At the end of the `if ( $use_global_query ) {` block on line 35 of `plugins/gutenberg/build/block-library/blocks/post-template.php`.
```php
function gutenberg_render_block_core_post_template( $attributes, $content, $block ) {
...
if ( $use_global_query ) {
global $wp_query;
...
$query_args = $wp_query->query;
}
```
Adding this line of code fixes the pagination as well.
The code comments mention the need to unset the `offset` param which would have to be refactored if still necessary.
Hope that helps, either as a fix or at least a start!
### Environment info
WordPress 5.8.1
Gutenberg 11.5.1
### Please confirm that you have searched existing issues in the repo.
Yes
### Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes | non_design | query loop block displays incorrect posts when inheriting template query and filtering multiple terms per taxonomy description the query loop block doesn t display the correct list of posts when inheriting query from template and filtering multiple terms per taxonomy e g category name block media it only shows posts assigned to the first term using the same url and switching to a classic theme e g twentytwentyone the correct list of posts is displayed step by step reproduction instructions activate a fse theme e g blockbase add taxonomy filter parameters to your wordpress url multiple terms for one taxonomy e g category name block media or category block media make sure there are posts that are assigned to each and only one term of the chosen terms e g post a has only category block and post b has only category media observe the list of posts being displayed e g only post a is being displayed flip the terms in the url e g category media block observe the list of posts being displayed e g only post b is being displayed copy the url and activate a classic non fse theme e g twentytwentyone reload the copied url e g category media block observe the list of posts being displayed e g post a and post b are being displayed screenshots screen recording code snippet the issue is caused by the new local wp query and the way the query args array is created when inheriting the query in the function gutenberg render block core post template plugins gutenberg build block library blocks post template php the query args array is based on the global wp query query vars those query vars have been parsed and now have only one taxonomy term set when filtering for multiple ones e g category block media results in query vars block and thus the new query filters only by one category this also creates issues with pagination the pagination is based on the correct amount of posts which can result in an empty last page the query loop works as expected if the query args are based on the global wp query query which still holds all terms adding query args wp query query at the end of the if use global query block on line of plugins gutenberg build block library blocks post template php php function gutenberg render block core post template attributes content block if use global query global wp query query args wp query query adding this line of code fixes the pagination as well the code comments mention the need to unset the offset param which would have to be refactored if still necessary hope that helps either as a fix or at least a start environment info wordpress gutenberg please confirm that you have searched existing issues in the repo yes please confirm that you have tested with all plugins deactivated except gutenberg yes | 0 |
358,810 | 25,205,063,165 | IssuesEvent | 2022-11-13 15:29:31 | Rust-Python-Packaging/pyver | https://api.github.com/repos/Rust-Python-Packaging/pyver | closed | Add a CHANGELOG update check for CI | documentation ci/cd | Add a Ci check that checks if the CHANGELOG was updated in a PR.
Based on the command:
```bash
git fetch origin $GITHUB_BASE_REF
HEAD_SHA=$(git rev-parse HEAD)
BASE_SHA=$(git rev-parse origin/$GITHUB_BASE_REF)
git diff --exit-code $HEAD_SHA $BASE_SHA -- CHANGELOG.md || exit 0 && exit 1
``` | 1.0 | Add a CHANGELOG update check for CI - Add a Ci check that checks if the CHANGELOG was updated in a PR.
Based on the command:
```bash
git fetch origin $GITHUB_BASE_REF
HEAD_SHA=$(git rev-parse HEAD)
BASE_SHA=$(git rev-parse origin/$GITHUB_BASE_REF)
git diff --exit-code $HEAD_SHA $BASE_SHA -- CHANGELOG.md || exit 0 && exit 1
``` | non_design | add a changelog update check for ci add a ci check that checks if the changelog was updated in a pr based on the command bash git fetch origin github base ref head sha git rev parse head base sha git rev parse origin github base ref git diff exit code head sha base sha changelog md exit exit | 0 |
69,458 | 8,407,738,052 | IssuesEvent | 2018-10-11 21:59:42 | gitcoinco/web | https://api.github.com/repos/gitcoinco/web | closed | Create/modify "Grants Index" Page - Design | design-help design-principles grants | ### User Story
As a Grants user, I want to see and search all possible grants so that I can contribute to projects that matter to me, as well as click into the different user flows of the Grants project.
### Why Is this Needed
Users need a central place to find active grants and choose different interactions to have with the grants process.
### Description
*Type*: Feature
### Definition of Done
- [x] Page has a "Dev Grants" Title
- [x] Page has a short description of the Grants Product and its different user flows
- [x] Page has thumbnail versions of all live grants in the Gitcoin ecosystem and should be paginated and clickable
- [x] Grant thumbnails display the project title, description, owner, and a current vs. desired monthly funding progress bar
- [x] Page has a search bar for searching/sorting by title and topic
- [x] Page has a "Create Grant" button
- [ ] Page has a "My Grants" button
- [x] Page has standard Gitcoin header and footer
- [x] Design must be on brand, see creative repo for brand guide
### Additional Information
To be reviewed with @PixelantDesign @mbeacom @captnseagraves
Existing assets can be found at this PR: https://github.com/gitcoinco/web/pull/674
More information about the Dev Grants project can be found here: https://github.com/gitcoinco/web/issues/1469
Please allow the core team a few rounds of revisions. | 2.0 | Create/modify "Grants Index" Page - Design - ### User Story
As a Grants user, I want to see and search all possible grants so that I can contribute to projects that matter to me, as well as click into the different user flows of the Grants project.
### Why Is this Needed
Users need a central place to find active grants and choose different interactions to have with the grants process.
### Description
*Type*: Feature
### Definition of Done
- [x] Page has a "Dev Grants" Title
- [x] Page has a short description of the Grants Product and its different user flows
- [x] Page has thumbnail versions of all live grants in the Gitcoin ecosystem and should be paginated and clickable
- [x] Grant thumbnails display the project title, description, owner, and a current vs. desired monthly funding progress bar
- [x] Page has a search bar for searching/sorting by title and topic
- [x] Page has a "Create Grant" button
- [ ] Page has a "My Grants" button
- [x] Page has standard Gitcoin header and footer
- [x] Design must be on brand, see creative repo for brand guide
### Additional Information
To be reviewed with @PixelantDesign @mbeacom @captnseagraves
Existing assets can be found at this PR: https://github.com/gitcoinco/web/pull/674
More information about the Dev Grants project can be found here: https://github.com/gitcoinco/web/issues/1469
Please allow the core team a few rounds of revisions. | design | create modify grants index page design user story as a grants user i want to see and search all possible grants so that i can contribute to projects that matter to me as well as click into the different user flows of the grants project why is this needed users need a central place to find active grants and choose different interactions to have with the grants process description type feature definition of done page has a dev grants title page has a short description of the grants product and its different user flows page has thumbnail versions of all live grants in the gitcoin ecosystem and should be paginated and clickable grant thumbnails display the project title description owner and a current vs desired monthly funding progress bar page has a search bar for searching sorting by title and topic page has a create grant button page has a my grants button page has standard gitcoin header and footer design must be on brand see creative repo for brand guide additional information to be reviewed with pixelantdesign mbeacom captnseagraves existing assets can be found at this pr more information about the dev grants project can be found here please allow the core team a few rounds of revisions | 1 |
89,957 | 11,306,200,570 | IssuesEvent | 2020-01-18 12:17:20 | navikt/Designsystemet | https://api.github.com/repos/navikt/Designsystemet | opened | Mønster/retningslinjer for å formidle skjemakrav til bruker | design design.nav.no diskusjon epic forbedring interne flater mønster utvikling uu | Vi trenger retningsnlinjer og muligens et eget mønster for hvordan vi best kan kommunisere kravene for riktig utfylling av skjema til bruker - uten at bruker skal være nødt til å få noen feilmeldinger fra validering først.
Avklare hvordan vi løser:
- [ ] påkrevd vs. valgfri (se #3)
- [ ] spesielle input-formater (datoer, tlf, fnr, space vs. `type="number"` osv)
- [ ] andre krav/instruksjoner som må forklares mer inngående (bruk av [Hjelpetekst](https://design.nav.no/components/hjelpetekst#kombinasjon-med-skjemafelt) osv)
- [ ] unntak for avanserte skjema (ekspertsystemer)?
Lage/publisere:
- [ ] Retningslinjer
- [ ] Mønster | 2.0 | Mønster/retningslinjer for å formidle skjemakrav til bruker - Vi trenger retningsnlinjer og muligens et eget mønster for hvordan vi best kan kommunisere kravene for riktig utfylling av skjema til bruker - uten at bruker skal være nødt til å få noen feilmeldinger fra validering først.
Avklare hvordan vi løser:
- [ ] påkrevd vs. valgfri (se #3)
- [ ] spesielle input-formater (datoer, tlf, fnr, space vs. `type="number"` osv)
- [ ] andre krav/instruksjoner som må forklares mer inngående (bruk av [Hjelpetekst](https://design.nav.no/components/hjelpetekst#kombinasjon-med-skjemafelt) osv)
- [ ] unntak for avanserte skjema (ekspertsystemer)?
Lage/publisere:
- [ ] Retningslinjer
- [ ] Mønster | design | mønster retningslinjer for å formidle skjemakrav til bruker vi trenger retningsnlinjer og muligens et eget mønster for hvordan vi best kan kommunisere kravene for riktig utfylling av skjema til bruker uten at bruker skal være nødt til å få noen feilmeldinger fra validering først avklare hvordan vi løser påkrevd vs valgfri se spesielle input formater datoer tlf fnr space vs type number osv andre krav instruksjoner som må forklares mer inngående bruk av osv unntak for avanserte skjema ekspertsystemer lage publisere retningslinjer mønster | 1 |
60,082 | 7,314,281,725 | IssuesEvent | 2018-03-01 06:19:13 | nextcloud/server | https://api.github.com/repos/nextcloud/server | closed | The icon in Security about sync client is missing like linux,mac and windows. | design enhancement | The icon in Security about sync client is missing like linux,mac and windows.
### Expected behaviour
All can see the icon.
### Actual behaviour
Sync client icons is missing like linux,mac and windows.
### Server configuration
Database:10.0.31-MariaDB-0ubuntu0.16.04.2 Ubuntu 16.04
PHP version:PHP 7.0.22
cloud server:Nextcloud
cloud version: 14.0.0.1 alpha | 1.0 | The icon in Security about sync client is missing like linux,mac and windows. - The icon in Security about sync client is missing like linux,mac and windows.
### Expected behaviour
All can see the icon.
### Actual behaviour
Sync client icons is missing like linux,mac and windows.
### Server configuration
Database:10.0.31-MariaDB-0ubuntu0.16.04.2 Ubuntu 16.04
PHP version:PHP 7.0.22
cloud server:Nextcloud
cloud version: 14.0.0.1 alpha | design | the icon in security about sync client is missing like linux mac and windows the icon in security about sync client is missing like linux mac and windows expected behaviour all can see the icon actual behaviour sync client icons is missing like linux mac and windows server configuration database mariadb ubuntu php version php cloud server nextcloud cloud version alpha | 1 |
442,849 | 30,860,161,178 | IssuesEvent | 2023-08-03 01:50:29 | argilla-io/argilla | https://api.github.com/repos/argilla-io/argilla | closed | docs: incomplete codeblocks in Metrics documentation | documentation enhancement stale | **Is your feature request related to a problem? Please describe.**
The [Metrics documentation](https://docs.argilla.io/en/latest/reference/python/python_metrics.html) is filled with codeblocks like:
```python
>>> from argilla.metrics.token_classification import f1
>>> summary = f1(name="example-dataset")
>>> summary.visualize() # will plot three bar charts with the results
>>> summary.data # returns the raw result data
```
However, in core Python, this will not trigger any visualization occurring - this only works in Jupyter Notebook if `summary.visualize()` is the last line of a cell. This is because `summary.visualize()` does not visualize, it only returns a plotly fig. This is fine, but just not well documented.
**Describe the solution you'd like**
Perhaps we can use the following structure instead:
```python
>>> from argilla.metrics.token_classification import f1
>>> summary = f1(name="example-dataset")
>>> fig = summary.visualize() # will plot three bar charts with the results
>>> fig.plot()
>>> summary.data # returns the raw result data
```
**Describe alternatives you've considered**
We can just leave it be.
**Additional context**
N\A
---
- Tom Aarsen
| 1.0 | docs: incomplete codeblocks in Metrics documentation - **Is your feature request related to a problem? Please describe.**
The [Metrics documentation](https://docs.argilla.io/en/latest/reference/python/python_metrics.html) is filled with codeblocks like:
```python
>>> from argilla.metrics.token_classification import f1
>>> summary = f1(name="example-dataset")
>>> summary.visualize() # will plot three bar charts with the results
>>> summary.data # returns the raw result data
```
However, in core Python, this will not trigger any visualization occurring - this only works in Jupyter Notebook if `summary.visualize()` is the last line of a cell. This is because `summary.visualize()` does not visualize, it only returns a plotly fig. This is fine, but just not well documented.
**Describe the solution you'd like**
Perhaps we can use the following structure instead:
```python
>>> from argilla.metrics.token_classification import f1
>>> summary = f1(name="example-dataset")
>>> fig = summary.visualize() # will plot three bar charts with the results
>>> fig.plot()
>>> summary.data # returns the raw result data
```
**Describe alternatives you've considered**
We can just leave it be.
**Additional context**
N\A
---
- Tom Aarsen
| non_design | docs incomplete codeblocks in metrics documentation is your feature request related to a problem please describe the is filled with codeblocks like python from argilla metrics token classification import summary name example dataset summary visualize will plot three bar charts with the results summary data returns the raw result data however in core python this will not trigger any visualization occurring this only works in jupyter notebook if summary visualize is the last line of a cell this is because summary visualize does not visualize it only returns a plotly fig this is fine but just not well documented describe the solution you d like perhaps we can use the following structure instead python from argilla metrics token classification import summary name example dataset fig summary visualize will plot three bar charts with the results fig plot summary data returns the raw result data describe alternatives you ve considered we can just leave it be additional context n a tom aarsen | 0 |
6,327 | 3,011,040,529 | IssuesEvent | 2015-07-28 15:57:07 | softlayer/sl-ember-components | https://api.github.com/repos/softlayer/sl-ember-components | closed | Confirm whether sl-panel has a dependency on Bootstrap-Datepicker | 2 - Working documentation research | The `#/browsers` page in the demo app indicates as such but I'm thinking this is not accurate. If it is not update the compatibility table.
<!---
@huboard:{"milestone_order":364.9999999925494}
-->
| 1.0 | Confirm whether sl-panel has a dependency on Bootstrap-Datepicker - The `#/browsers` page in the demo app indicates as such but I'm thinking this is not accurate. If it is not update the compatibility table.
<!---
@huboard:{"milestone_order":364.9999999925494}
-->
| non_design | confirm whether sl panel has a dependency on bootstrap datepicker the browsers page in the demo app indicates as such but i m thinking this is not accurate if it is not update the compatibility table huboard milestone order | 0 |
4,212 | 2,718,819,603 | IssuesEvent | 2015-04-12 18:10:27 | MozillaFoundation/movement-building | https://api.github.com/repos/MozillaFoundation/movement-building | opened | Advocacy Homepage Promo Block for Sec. 215 surveillance petition | needs-design section215 | Just flagging urgency on the homepage block, I don't see Jess on the bug yet here (I just commented there to get things moving again):
https://bugzilla.mozilla.org/show_bug.cgi?id=1152159
We have two options:
1. In the interest of time, keep the megaphone and update the copy;
2. Try out the eyeball on the homepage (I have to check with the moco folks, including Matej). I will ask on the bug if they're cool with trying the eyeball.
If eyeball is at all controversial we'll fall back to megaphone design that exists, and simply update copy (option #1).
Copy is in that bug, but i'll drop it here:
Help end mass surveillance
or
End mass surveillance
| 1.0 | Advocacy Homepage Promo Block for Sec. 215 surveillance petition - Just flagging urgency on the homepage block, I don't see Jess on the bug yet here (I just commented there to get things moving again):
https://bugzilla.mozilla.org/show_bug.cgi?id=1152159
We have two options:
1. In the interest of time, keep the megaphone and update the copy;
2. Try out the eyeball on the homepage (I have to check with the moco folks, including Matej). I will ask on the bug if they're cool with trying the eyeball.
If eyeball is at all controversial we'll fall back to megaphone design that exists, and simply update copy (option #1).
Copy is in that bug, but i'll drop it here:
Help end mass surveillance
or
End mass surveillance
| design | advocacy homepage promo block for sec surveillance petition just flagging urgency on the homepage block i don t see jess on the bug yet here i just commented there to get things moving again we have two options in the interest of time keep the megaphone and update the copy try out the eyeball on the homepage i have to check with the moco folks including matej i will ask on the bug if they re cool with trying the eyeball if eyeball is at all controversial we ll fall back to megaphone design that exists and simply update copy option copy is in that bug but i ll drop it here help end mass surveillance or end mass surveillance | 1 |
37,812 | 12,497,086,672 | IssuesEvent | 2020-06-01 15:54:16 | CarlsbergGBS/msrCrypto | https://api.github.com/repos/CarlsbergGBS/msrCrypto | opened | CVE-2018-1000620 (High) detected in cryptiles-2.0.5.tgz | security vulnerability | ## CVE-2018-1000620 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>cryptiles-2.0.5.tgz</b></p></summary>
<p>General purpose crypto utilities</p>
<p>Library home page: <a href="https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz">https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/msrCrypto/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/msrCrypto/node_modules/cryptiles/package.json</p>
<p>
Dependency Hierarchy:
- karma-2.0.5.tgz (Root Library)
- log4js-2.11.0.tgz
- loggly-1.1.1.tgz
- request-2.75.0.tgz
- hawk-3.1.3.tgz
- :x: **cryptiles-2.0.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/CarlsbergGBS/msrCrypto/commit/12f102f22fa72d82e1f76b3cb23847248716f60d">12f102f22fa72d82e1f76b3cb23847248716f60d</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Eran Hammer cryptiles version 4.1.1 earlier contains a CWE-331: Insufficient Entropy vulnerability in randomDigits() method that can result in An attacker is more likely to be able to brute force something that was supposed to be random.. This attack appear to be exploitable via Depends upon the calling application.. This vulnerability appears to have been fixed in 4.1.2.
<p>Publish Date: 2018-07-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000620>CVE-2018-1000620</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://nvd.nist.gov/vuln/detail/CVE-2018-1000620">https://nvd.nist.gov/vuln/detail/CVE-2018-1000620</a></p>
<p>Release Date: 2019-04-08</p>
<p>Fix Resolution: 4.1.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-1000620 (High) detected in cryptiles-2.0.5.tgz - ## CVE-2018-1000620 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>cryptiles-2.0.5.tgz</b></p></summary>
<p>General purpose crypto utilities</p>
<p>Library home page: <a href="https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz">https://registry.npmjs.org/cryptiles/-/cryptiles-2.0.5.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/msrCrypto/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/msrCrypto/node_modules/cryptiles/package.json</p>
<p>
Dependency Hierarchy:
- karma-2.0.5.tgz (Root Library)
- log4js-2.11.0.tgz
- loggly-1.1.1.tgz
- request-2.75.0.tgz
- hawk-3.1.3.tgz
- :x: **cryptiles-2.0.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/CarlsbergGBS/msrCrypto/commit/12f102f22fa72d82e1f76b3cb23847248716f60d">12f102f22fa72d82e1f76b3cb23847248716f60d</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Eran Hammer cryptiles version 4.1.1 earlier contains a CWE-331: Insufficient Entropy vulnerability in randomDigits() method that can result in An attacker is more likely to be able to brute force something that was supposed to be random.. This attack appear to be exploitable via Depends upon the calling application.. This vulnerability appears to have been fixed in 4.1.2.
<p>Publish Date: 2018-07-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000620>CVE-2018-1000620</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://nvd.nist.gov/vuln/detail/CVE-2018-1000620">https://nvd.nist.gov/vuln/detail/CVE-2018-1000620</a></p>
<p>Release Date: 2019-04-08</p>
<p>Fix Resolution: 4.1.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve high detected in cryptiles tgz cve high severity vulnerability vulnerable library cryptiles tgz general purpose crypto utilities library home page a href path to dependency file tmp ws scm msrcrypto package json path to vulnerable library tmp ws scm msrcrypto node modules cryptiles package json dependency hierarchy karma tgz root library tgz loggly tgz request tgz hawk tgz x cryptiles tgz vulnerable library found in head commit a href vulnerability details eran hammer cryptiles version earlier contains a cwe insufficient entropy vulnerability in randomdigits method that can result in an attacker is more likely to be able to brute force something that was supposed to be random this attack appear to be exploitable via depends upon the calling application this vulnerability appears to have been fixed in publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
105,507 | 13,190,242,751 | IssuesEvent | 2020-08-13 09:50:53 | tektoncd/dashboard | https://api.github.com/repos/tektoncd/dashboard | reopened | New storybook components | kind/design kind/documentation lifecycle/rotten lifecycle/stale | # Expected Behavior
The current storybook should have all of the custom components and patterns Tekton needs in the application so that it complies with Carbon standards. This list should be expected to grow as the application progresses over time.
# Actual Behavior
The current storybook only has a portion of the components and patterns needed in the product
# Steps to Reproduce the Problem
Here are some ideas for patterns in the Storybook:
1. Page Title Header: background color, page title, breadcrumbs, buttons, spacing, etc
2. YAML file component
3. Logs component
4. Tabbed Header and background
5. Forms and Create new flow (Secrets, Annotation, Service Accounts, etc)
6. Logs
7. Empty State (Carbon had a pattern, but not a component)
8. Lists or metadata (not sure what to call this one)
# Additional Info (Examples)
### Page title Header
example 1
example 2 - We may or may not decide to build the Filter component into the Page Title Header.
### Forms/ Creation Flows
This flow is different from other pages in that it has a $ui-background of color Gray 10. A Page Title isn't present, nor is a Search. This is essentially a mode the user goes into to "create".
### Empty State
### Metadata
### **Tabbed Area**
This could be a variation of the Page Title Header. The difference is the background-color and the presence of a tab
### YAML
### Logs
| 1.0 | New storybook components - # Expected Behavior
The current storybook should have all of the custom components and patterns Tekton needs in the application so that it complies with Carbon standards. This list should be expected to grow as the application progresses over time.
# Actual Behavior
The current storybook only has a portion of the components and patterns needed in the product
# Steps to Reproduce the Problem
Here are some ideas for patterns in the Storybook:
1. Page Title Header: background color, page title, breadcrumbs, buttons, spacing, etc
2. YAML file component
3. Logs component
4. Tabbed Header and background
5. Forms and Create new flow (Secrets, Annotation, Service Accounts, etc)
6. Logs
7. Empty State (Carbon had a pattern, but not a component)
8. Lists or metadata (not sure what to call this one)
# Additional Info (Examples)
### Page title Header
example 1
example 2 - We may or may not decide to build the Filter component into the Page Title Header.
### Forms/ Creation Flows
This flow is different from other pages in that it has a $ui-background of color Gray 10. A Page Title isn't present, nor is a Search. This is essentially a mode the user goes into to "create".
### Empty State
### Metadata
### **Tabbed Area**
This could be a variation of the Page Title Header. The difference is the background-color and the presence of a tab
### YAML
### Logs
| design | new storybook components expected behavior the current storybook should have all of the custom components and patterns tekton needs in the application so that it complies with carbon standards this list should be expected to grow as the application progresses over time actual behavior the current storybook only has a portion of the components and patterns needed in the product steps to reproduce the problem here are some ideas for patterns in the storybook page title header background color page title breadcrumbs buttons spacing etc yaml file component logs component tabbed header and background forms and create new flow secrets annotation service accounts etc logs empty state carbon had a pattern but not a component lists or metadata not sure what to call this one additional info examples page title header example example we may or may not decide to build the filter component into the page title header forms creation flows this flow is different from other pages in that it has a ui background of color gray a page title isn t present nor is a search this is essentially a mode the user goes into to create empty state metadata tabbed area this could be a variation of the page title header the difference is the background color and the presence of a tab yaml logs | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.