Technical Debt and it Types Datasets
Collection
24 items
•
Updated
•
1
Dataset Viewer
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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
73,144 | 8,825,026,207 | IssuesEvent | 2019-01-02 19:16:56 | envoyproxy/envoy | https://api.github.com/repos/envoyproxy/envoy | closed | Stream idle timeout behavior on gRPC streaming? | design proposal | Based on the documentation and reading the code it seems stream idle timeout breaks gRPC streaming streams when no information has been exchanged on the stream for a time longer than the stream idle timeout in effect.
It seems that if `max-grpc-timeout` has been specified (maybe as unlimited), stream idle timeout should not fire before the `grpc-timeout` (specified in gRPC headers) fires.
| 1.0 | Stream idle timeout behavior on gRPC streaming? - Based on the documentation and reading the code it seems stream idle timeout breaks gRPC streaming streams when no information has been exchanged on the stream for a time longer than the stream idle timeout in effect.
It seems that if `max-grpc-timeout` has been specified (maybe as unlimited), stream idle timeout should not fire before the `grpc-timeout` (specified in gRPC headers) fires.
| design | stream idle timeout behavior on grpc streaming based on the documentation and reading the code it seems stream idle timeout breaks grpc streaming streams when no information has been exchanged on the stream for a time longer than the stream idle timeout in effect it seems that if max grpc timeout has been specified maybe as unlimited stream idle timeout should not fire before the grpc timeout specified in grpc headers fires | 1 |
19,971 | 3,518,413,104 | IssuesEvent | 2016-01-12 12:47:35 | owncloud/client | https://api.github.com/repos/owncloud/client | closed | Display Server Version in Client Software? | Design & UX enhancement - proposed Feature | Is it possible to Display teh Server Software-Version in the Cilent?
http://i.imgur.com/YeljKcm.png | 1.0 | Display Server Version in Client Software? - Is it possible to Display teh Server Software-Version in the Cilent?
http://i.imgur.com/YeljKcm.png | design | display server version in client software is it possible to display teh server software version in the cilent | 1 |
145,442 | 22,688,593,679 | IssuesEvent | 2022-07-04 16:38:21 | Joystream/atlas | https://api.github.com/repos/Joystream/atlas | closed | Adding info about avatar size/ ratio | design | We could inform user about the dimensions of the image for the avatar - to allow users design custom graphics for their channels and videos easier. | 1.0 | Adding info about avatar size/ ratio - We could inform user about the dimensions of the image for the avatar - to allow users design custom graphics for their channels and videos easier. | design | adding info about avatar size ratio we could inform user about the dimensions of the image for the avatar to allow users design custom graphics for their channels and videos easier | 1 |
108,163 | 13,562,539,327 | IssuesEvent | 2020-09-18 07:03:42 | flutter/flutter | https://api.github.com/repos/flutter/flutter | closed | [i hope fiex]about flutter function showDialog can't create Real full screen | documentation f: material design framework waiting for customer response | about flutter function showDialog can't create Real full screen
example:
i wan't use showDialog create real full screen
in iphone6-iphone8 and android phone is full screen but in iphoneX - iphone xs Max have empty space i don't know why
help help help
this is iphone8:
demo:
```C
showDialog(
context: context,
builder: (ctx) => IjkPlayer(
mediaController: controller,
controllerWidgetBuilder: (ctl) =>
_buildFullScreenMediaController(ctl, true),
),
).then((_) {
IjkManager.unlockOrientation();
IjkManager.setCurrentOrientation(DeviceOrientation.portraitUp);
});
``` | 1.0 | [i hope fiex]about flutter function showDialog can't create Real full screen - about flutter function showDialog can't create Real full screen
example:
i wan't use showDialog create real full screen
in iphone6-iphone8 and android phone is full screen but in iphoneX - iphone xs Max have empty space i don't know why
help help help
this is iphone8:
demo:
```C
showDialog(
context: context,
builder: (ctx) => IjkPlayer(
mediaController: controller,
controllerWidgetBuilder: (ctl) =>
_buildFullScreenMediaController(ctl, true),
),
).then((_) {
IjkManager.unlockOrientation();
IjkManager.setCurrentOrientation(DeviceOrientation.portraitUp);
});
``` | design | about flutter function showdialog can t create real full screen about flutter function showdialog can t create real full screen example i wan t use showdialog create real full screen in and android phone is full screen but in iphonex iphone xs max have empty space i don t know why help help help this is demo c showdialog context context builder ctx ijkplayer mediacontroller controller controllerwidgetbuilder ctl buildfullscreenmediacontroller ctl true then ijkmanager unlockorientation ijkmanager setcurrentorientation deviceorientation portraitup | 1 |
177,072 | 28,316,083,313 | IssuesEvent | 2023-04-10 19:44:02 | bounswe/bounswe2023group2 | https://api.github.com/repos/bounswe/bounswe2023group2 | closed | Sequence Diagram - Guest registering user - by e-mail | required: design priority: high state: In progress effort: level 3 | ### Issue Description
Sequence Diagram for the guest registering themselves by e-mail.
- Mobile phone registration will be similar. So first let us finalize this one.
- Also a good revision will be very useful as we can continue with the SDs.
[Lucid Chart viewing is possible using this link](https://lucid.app/lucidchart/d5e5ea80-f1aa-4506-883d-36f6508bb933/edit?viewport_loc=214%2C834%2C1568%2C680%2C0_0&invitationId=inv_88d50c3b-e67a-486e-a987-a8f82cba36b6)
### Deadline of the Issue
08.04.2023
### Reviewer
Merve Gürbüz | 1.0 | Sequence Diagram - Guest registering user - by e-mail - ### Issue Description
Sequence Diagram for the guest registering themselves by e-mail.
- Mobile phone registration will be similar. So first let us finalize this one.
- Also a good revision will be very useful as we can continue with the SDs.
[Lucid Chart viewing is possible using this link](https://lucid.app/lucidchart/d5e5ea80-f1aa-4506-883d-36f6508bb933/edit?viewport_loc=214%2C834%2C1568%2C680%2C0_0&invitationId=inv_88d50c3b-e67a-486e-a987-a8f82cba36b6)
### Deadline of the Issue
08.04.2023
### Reviewer
Merve Gürbüz | design | sequence diagram guest registering user by e mail issue description sequence diagram for the guest registering themselves by e mail mobile phone registration will be similar so first let us finalize this one also a good revision will be very useful as we can continue with the sds deadline of the issue reviewer merve gürbüz | 1 |
168,534 | 26,660,771,603 | IssuesEvent | 2023-01-25 20:53:56 | hypha-dao/dho-web-client | https://api.github.com/repos/hypha-dao/dho-web-client | closed | Personal Sidebar (S) | Design MVP | **Summary:**
As a DHO user I would like to see the sidebar filled with personal and relevant information for me so I can quickly navigate to the most important tasks in the DHO.
**Description:**
The sidebar is always shown on the right side of the screen. It can be clicked away but also easily clicked to show up when clicking on my profile photo on the top right.
**Acceptance Criteria:**
- [x] X to close sidebar
Top Section:
- [x] Profile Photo
- [x] Username
- [ ] Badges Icons (if the person has no Badges show nothing)
Copy:
- [x] Headline: Hey {Username}, welcome to {DAO Name}
- [x] Copy: Nice to see you here. Go take a look around. This DAO is here to help you govern your decentralized organisation, reduce coordination cost and build your organisation.
- [x] You can voter for proposals (link proposal list), find other members (link members list) and find out what makes your organisation what it is (link to /organization)
- [x] Go to your profile (link to /@profile) and make sure its complete.
- [x] And most importantly - have fun and do the DHO.
Icons / Links:
- [x] My Wallet (link to wallet /@username)
- [x] My Profile (link to profile /@username)
- [x] Logout (link to /login page)
- [x] New Proposal (link to proposal creation wizard /proposals/create)
Design:
- [ ] Use correct grey for background of squares
- [x] Make squares squares (not rectangle)
- [ ] Use correct icons
**Ressources:**
Attachement:
https://xd.adobe.com/view/2e6dc275-76dc-4722-a922-cc60c5d7d653-7b3e/
| 1.0 | Personal Sidebar (S) - **Summary:**
As a DHO user I would like to see the sidebar filled with personal and relevant information for me so I can quickly navigate to the most important tasks in the DHO.
**Description:**
The sidebar is always shown on the right side of the screen. It can be clicked away but also easily clicked to show up when clicking on my profile photo on the top right.
**Acceptance Criteria:**
- [x] X to close sidebar
Top Section:
- [x] Profile Photo
- [x] Username
- [ ] Badges Icons (if the person has no Badges show nothing)
Copy:
- [x] Headline: Hey {Username}, welcome to {DAO Name}
- [x] Copy: Nice to see you here. Go take a look around. This DAO is here to help you govern your decentralized organisation, reduce coordination cost and build your organisation.
- [x] You can voter for proposals (link proposal list), find other members (link members list) and find out what makes your organisation what it is (link to /organization)
- [x] Go to your profile (link to /@profile) and make sure its complete.
- [x] And most importantly - have fun and do the DHO.
Icons / Links:
- [x] My Wallet (link to wallet /@username)
- [x] My Profile (link to profile /@username)
- [x] Logout (link to /login page)
- [x] New Proposal (link to proposal creation wizard /proposals/create)
Design:
- [ ] Use correct grey for background of squares
- [x] Make squares squares (not rectangle)
- [ ] Use correct icons
**Ressources:**
Attachement:
https://xd.adobe.com/view/2e6dc275-76dc-4722-a922-cc60c5d7d653-7b3e/
| design | personal sidebar s summary as a dho user i would like to see the sidebar filled with personal and relevant information for me so i can quickly navigate to the most important tasks in the dho description the sidebar is always shown on the right side of the screen it can be clicked away but also easily clicked to show up when clicking on my profile photo on the top right acceptance criteria x to close sidebar top section profile photo username badges icons if the person has no badges show nothing copy headline hey username welcome to dao name copy nice to see you here go take a look around this dao is here to help you govern your decentralized organisation reduce coordination cost and build your organisation you can voter for proposals link proposal list find other members link members list and find out what makes your organisation what it is link to organization go to your profile link to profile and make sure its complete and most importantly have fun and do the dho icons links my wallet link to wallet username my profile link to profile username logout link to login page new proposal link to proposal creation wizard proposals create design use correct grey for background of squares make squares squares not rectangle use correct icons ressources attachement | 1 |
135,905 | 19,681,904,892 | IssuesEvent | 2022-01-11 17:34:49 | vector-im/element-ios | https://api.github.com/repos/vector-im/element-ios | opened | Update Reactions component | T-Enhancement X-Needs-Design A-Reactions A-Message-Bubbles | ### Your use case
We'd like to improve the reactions component on iOS to be inline with the changes on Android and Web.
Verify or Build in iOS the ability to...
- [ ] Add a reaction from the Reaction row (emoji smiley with plus symbol, see comments)
- [ ] Add "Show all" when there's more than the maximum amount of emojis on a message that opens the bottom sheet
Related Android issues:
- https://github.com/vector-im/element-android/issues/4674
- https://github.com/vector-im/element-android/issues/3344
### Have you considered any alternatives?
_No response_
### Additional context
_No response_ | 1.0 | Update Reactions component - ### Your use case
We'd like to improve the reactions component on iOS to be inline with the changes on Android and Web.
Verify or Build in iOS the ability to...
- [ ] Add a reaction from the Reaction row (emoji smiley with plus symbol, see comments)
- [ ] Add "Show all" when there's more than the maximum amount of emojis on a message that opens the bottom sheet
Related Android issues:
- https://github.com/vector-im/element-android/issues/4674
- https://github.com/vector-im/element-android/issues/3344
### Have you considered any alternatives?
_No response_
### Additional context
_No response_ | design | update reactions component your use case we d like to improve the reactions component on ios to be inline with the changes on android and web verify or build in ios the ability to add a reaction from the reaction row emoji smiley with plus symbol see comments add show all when there s more than the maximum amount of emojis on a message that opens the bottom sheet related android issues have you considered any alternatives no response additional context no response | 1 |
151,298 | 12,030,822,897 | IssuesEvent | 2020-04-13 08:14:46 | microsoft/azure-tools-for-java | https://api.github.com/repos/microsoft/azure-tools-for-java | closed | There is no scroll wheel function to browse the instance | Internal Test | #### Environment:
```
OS: WIN/Mac
Plugins Version: Azure java toolkit for IntelliJ: 3.34.0
IDE Version: IU19.3.4 - jre11/IC19.3 - jre8
```
#### Repro Steps:
1. Add spring cloud dependency
2. Run deploy configuration with 20 instances.
3. Right click to open "show properties".
#### Result:
**There is no scroll wheel function to browse the instance
and can not show all instance even if the window is maximized.**
| 1.0 | There is no scroll wheel function to browse the instance - #### Environment:
```
OS: WIN/Mac
Plugins Version: Azure java toolkit for IntelliJ: 3.34.0
IDE Version: IU19.3.4 - jre11/IC19.3 - jre8
```
#### Repro Steps:
1. Add spring cloud dependency
2. Run deploy configuration with 20 instances.
3. Right click to open "show properties".
#### Result:
**There is no scroll wheel function to browse the instance
and can not show all instance even if the window is maximized.**
| non_design | there is no scroll wheel function to browse the instance environment os win mac plugins version azure java toolkit for intellij ide version repro steps add spring cloud dependency run deploy configuration with instances right click to open show properties result there is no scroll wheel function to browse the instance and can not show all instance even if the window is maximized | 0 |
96,381 | 12,126,153,017 | IssuesEvent | 2020-04-22 16:34:13 | beaverbuilder/assistant | https://api.github.com/repos/beaverbuilder/assistant | opened | Content App: Search | app: content enhancement needs design needs dev | It has been mentioned that it would be useful to have search directly in the content app as opposed to going to the main search app. | 1.0 | Content App: Search - It has been mentioned that it would be useful to have search directly in the content app as opposed to going to the main search app. | design | content app search it has been mentioned that it would be useful to have search directly in the content app as opposed to going to the main search app | 1 |
35,910 | 4,704,035,842 | IssuesEvent | 2016-10-13 10:01:03 | RestComm/mediaserver | https://api.github.com/repos/RestComm/mediaserver | closed | DTLS certificate configuration | designing dtls enhancement WebRTC | This issue is related to #254 and #255.
Cipher suite certificates are currently used as a internal resource, but maybe the location of the file should be configurable. Investigate and adapt as needed. | 1.0 | DTLS certificate configuration - This issue is related to #254 and #255.
Cipher suite certificates are currently used as a internal resource, but maybe the location of the file should be configurable. Investigate and adapt as needed. | design | dtls certificate configuration this issue is related to and cipher suite certificates are currently used as a internal resource but maybe the location of the file should be configurable investigate and adapt as needed | 1 |
46,160 | 13,150,872,284 | IssuesEvent | 2020-08-09 13:57:33 | shaundmorris/ddf | https://api.github.com/repos/shaundmorris/ddf | closed | CVE-2015-1832 High Severity Vulnerability detected by WhiteSource | security vulnerability wontfix | ## CVE-2015-1832 - High Severity Vulnerability
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>derby-10.9.1.0.jar</b></p></summary>
<p>Contains the core Apache Derby database engine, which also includes the embedded JDBC driver.</p>
<p>path: /ddf/distribution/kernel/target/dependencies/solr/example/example-DIH/solr/db/lib/derby-10.9.1.0.jar,/ddf/distribution/ddf/target/dependencies/solr/example/example-DIH/solr/db/lib/derby-10.9.1.0.jar,/ddf/distribution/solr-distro/target/solr-7.4.0/example/example-DIH/solr/db/lib/derby-10.9.1.0.jar</p>
<p>
Dependency Hierarchy:
- :x: **derby-10.9.1.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shaundmorris/ddf/commit/ea35fc52f05b85ef437e9a9e39a887ad51692ff0">ea35fc52f05b85ef437e9a9e39a887ad51692ff0</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
XML external entity (XXE) vulnerability in the SqlXmlUtil code in Apache Derby before 10.12.1.1, when a Java Security Manager is not in place, allows context-dependent attackers to read arbitrary files or cause a denial of service (resource consumption) via vectors involving XmlVTI and the XML datatype.
<p>Publish Date: 2016-10-03
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1832>CVE-2015-1832</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.1</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: 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://www.whitesourcesoftware.com/wp-content/uploads/2018/10/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2015-1832">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2015-1832</a></p>
<p>Fix Resolution: Upgrade to version derby 10.12.1.1 or greater</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2015-1832 High Severity Vulnerability detected by WhiteSource - ## CVE-2015-1832 - High Severity Vulnerability
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>derby-10.9.1.0.jar</b></p></summary>
<p>Contains the core Apache Derby database engine, which also includes the embedded JDBC driver.</p>
<p>path: /ddf/distribution/kernel/target/dependencies/solr/example/example-DIH/solr/db/lib/derby-10.9.1.0.jar,/ddf/distribution/ddf/target/dependencies/solr/example/example-DIH/solr/db/lib/derby-10.9.1.0.jar,/ddf/distribution/solr-distro/target/solr-7.4.0/example/example-DIH/solr/db/lib/derby-10.9.1.0.jar</p>
<p>
Dependency Hierarchy:
- :x: **derby-10.9.1.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shaundmorris/ddf/commit/ea35fc52f05b85ef437e9a9e39a887ad51692ff0">ea35fc52f05b85ef437e9a9e39a887ad51692ff0</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
XML external entity (XXE) vulnerability in the SqlXmlUtil code in Apache Derby before 10.12.1.1, when a Java Security Manager is not in place, allows context-dependent attackers to read arbitrary files or cause a denial of service (resource consumption) via vectors involving XmlVTI and the XML datatype.
<p>Publish Date: 2016-10-03
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1832>CVE-2015-1832</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.1</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: 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://www.whitesourcesoftware.com/wp-content/uploads/2018/10/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2015-1832">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2015-1832</a></p>
<p>Fix Resolution: Upgrade to version derby 10.12.1.1 or greater</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 severity vulnerability detected by whitesource cve high severity vulnerability vulnerable library derby jar contains the core apache derby database engine which also includes the embedded jdbc driver path ddf distribution kernel target dependencies solr example example dih solr db lib derby jar ddf distribution ddf target dependencies solr example example dih solr db lib derby jar ddf distribution solr distro target solr example example dih solr db lib derby jar dependency hierarchy x derby jar vulnerable library found in head commit a href vulnerability details xml external entity xxe vulnerability in the sqlxmlutil code in apache derby before when a java security manager is not in place allows context dependent attackers to read arbitrary files or cause a denial of service resource consumption via vectors involving xmlvti and the xml datatype 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 high for more information on scores click a href suggested fix type upgrade version origin a href fix resolution upgrade to version derby or greater step up your open source security game with whitesource | 0 |
65,284 | 7,869,437,336 | IssuesEvent | 2018-06-24 14:00:00 | CodeWarriorsOrganization/CodeWarriorsFinalYearProject | https://api.github.com/repos/CodeWarriorsOrganization/CodeWarriorsFinalYearProject | closed | CW0023/T0023.2 -Design a solution to incorporated sectors & stocks in the game (Priority-2) | design | ### User Story :
> AS a player,
> I NEED at least 4 sectors and at least 3 stocks per sector to be incorporated in the game,
> SO THAT there is a competition within sectors, I’ll be able to select shares from those companies.
### Task :
> **Design a solution to incorporated sectors & stocks in the game** | 1.0 | CW0023/T0023.2 -Design a solution to incorporated sectors & stocks in the game (Priority-2) - ### User Story :
> AS a player,
> I NEED at least 4 sectors and at least 3 stocks per sector to be incorporated in the game,
> SO THAT there is a competition within sectors, I’ll be able to select shares from those companies.
### Task :
> **Design a solution to incorporated sectors & stocks in the game** | design | design a solution to incorporated sectors stocks in the game priority user story as a player i need at least sectors and at least stocks per sector to be incorporated in the game so that there is a competition within sectors i’ll be able to select shares from those companies task design a solution to incorporated sectors stocks in the game | 1 |
85,154 | 3,687,255,950 | IssuesEvent | 2016-02-25 07:14:03 | wordpress-mobile/WordPress-iOS | https://api.github.com/repos/wordpress-mobile/WordPress-iOS | closed | Use reachability to avoid timeouts | General priority-low trac [Type] Enhancement | Reported by @koke
When the blog host can't be reached, some actions (like moderating comments), just lock the app for a long time until the request times out
We should use reachability features to check if the host is alive before sending requests
To reproduce, you can install and configure a local wordpress in your workstation and then change your ip
Trac thread [here](http://ios.trac.wordpress.org/ticket/567) | 1.0 | Use reachability to avoid timeouts - Reported by @koke
When the blog host can't be reached, some actions (like moderating comments), just lock the app for a long time until the request times out
We should use reachability features to check if the host is alive before sending requests
To reproduce, you can install and configure a local wordpress in your workstation and then change your ip
Trac thread [here](http://ios.trac.wordpress.org/ticket/567) | non_design | use reachability to avoid timeouts reported by koke when the blog host can t be reached some actions like moderating comments just lock the app for a long time until the request times out we should use reachability features to check if the host is alive before sending requests to reproduce you can install and configure a local wordpress in your workstation and then change your ip trac thread | 0 |
79,583 | 9,917,156,464 | IssuesEvent | 2019-06-28 22:41:51 | participedia/usersnaps | https://api.github.com/repos/participedia/usersnaps | closed | Usersnap Feedback - Organizers field not working - I can't enter more than 1 Primary Organizer[...] | design-feedback | **Sender**: [email protected]
**Comment**: Organizers field not working - I can't enter more than 1 Primary Organizer/Manager. Each new selection just replaces the old one
[Open #462 in Usersnap Dashboard](https://usersnap.com/a/#/participedia-dev/p/participedia-201-a37e4cf6/462)
<a href='https://usersnappublic.s3.amazonaws.com/2019-06-27/23-13/363b7d0e-8a0b-47a1-a69f-0652b588023a.png'></a>
<a href='https://usersnappublic.s3.amazonaws.com/2019-06-27/23-13/363b7d0e-8a0b-47a1-a69f-0652b588023a.png'>Download original image</a>
**Browser**: Chrome 75 (Windows 10)
**Referer**: [https://participedia.net/case/5861/edit?full=1](https://participedia.net/case/5861/edit?full=1)
**Screen size**: 1280 x 720 **Browser size**: 1920 x 867
Powered by [usersnap.com](https://usersnap.com/?utm_source=github_entry&utm_medium=web&utm_campaign=product)
| 1.0 | Usersnap Feedback - Organizers field not working - I can't enter more than 1 Primary Organizer[...] - **Sender**: [email protected]
**Comment**: Organizers field not working - I can't enter more than 1 Primary Organizer/Manager. Each new selection just replaces the old one
[Open #462 in Usersnap Dashboard](https://usersnap.com/a/#/participedia-dev/p/participedia-201-a37e4cf6/462)
<a href='https://usersnappublic.s3.amazonaws.com/2019-06-27/23-13/363b7d0e-8a0b-47a1-a69f-0652b588023a.png'></a>
<a href='https://usersnappublic.s3.amazonaws.com/2019-06-27/23-13/363b7d0e-8a0b-47a1-a69f-0652b588023a.png'>Download original image</a>
**Browser**: Chrome 75 (Windows 10)
**Referer**: [https://participedia.net/case/5861/edit?full=1](https://participedia.net/case/5861/edit?full=1)
**Screen size**: 1280 x 720 **Browser size**: 1920 x 867
Powered by [usersnap.com](https://usersnap.com/?utm_source=github_entry&utm_medium=web&utm_campaign=product)
| design | usersnap feedback organizers field not working i can t enter more than primary organizer sender scottowenfletcher gmail com comment organizers field not working i can t enter more than primary organizer manager each new selection just replaces the old one a href browser chrome windows referer screen size x browser size x powered by | 1 |
171,257 | 27,089,457,423 | IssuesEvent | 2023-02-14 19:42:32 | department-of-veterans-affairs/va.gov-team | https://api.github.com/repos/department-of-veterans-affairs/va.gov-team | opened | [Design] Create Content and Final Wireframes | content design ux HCE-Checkin | ## Scenario
Veteran is checked-in AND we submitted a travel claim for them. We need to tell them that we are going to send them a text message with the submission status of their travel claim.
## Tasks
- [ ] Create content for message
- [ ] Create final mockups with callouts
- [ ] Decide: Should a content and accessibility review be part of this ticket or separate tickets due to scope?
## Acceptance Criteria
- [ ] UI review meeting with product/UX team for feature capabilities
- [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above)
- [ ] Wireframe available on Sketch Cloud
- [ ] If the wireframes applies to an error state or text message, then update the [GitHub source of truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/design/text-and-error-messages.md) documentation.
| 1.0 | [Design] Create Content and Final Wireframes - ## Scenario
Veteran is checked-in AND we submitted a travel claim for them. We need to tell them that we are going to send them a text message with the submission status of their travel claim.
## Tasks
- [ ] Create content for message
- [ ] Create final mockups with callouts
- [ ] Decide: Should a content and accessibility review be part of this ticket or separate tickets due to scope?
## Acceptance Criteria
- [ ] UI review meeting with product/UX team for feature capabilities
- [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above)
- [ ] Wireframe available on Sketch Cloud
- [ ] If the wireframes applies to an error state or text message, then update the [GitHub source of truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/design/text-and-error-messages.md) documentation.
| design | create content and final wireframes scenario veteran is checked in and we submitted a travel claim for them we need to tell them that we are going to send them a text message with the submission status of their travel claim tasks create content for message create final mockups with callouts decide should a content and accessibility review be part of this ticket or separate tickets due to scope acceptance criteria ui review meeting with product ux team for feature capabilities ui review meeting with engineering for layout and callouts can be the same meeting as above wireframe available on sketch cloud if the wireframes applies to an error state or text message then update the documentation | 1 |
253,027 | 8,050,228,267 | IssuesEvent | 2018-08-01 12:51:25 | alipay/sofa-mosn | https://api.github.com/repos/alipay/sofa-mosn | closed | Connections migration on process smooth upgrade | area/net priority/P0 | Currently, existing connections are not properly processed during the smooth upgrade process, which depends on the specific protocol's behaviour. For protocols that does not support things like 'goaway', MOSN will wait for a while and then close connections. The goal of this issue is to build a protocol-independent mechanism which transfers existing connections to new process on smooth upgrade. | 1.0 | Connections migration on process smooth upgrade - Currently, existing connections are not properly processed during the smooth upgrade process, which depends on the specific protocol's behaviour. For protocols that does not support things like 'goaway', MOSN will wait for a while and then close connections. The goal of this issue is to build a protocol-independent mechanism which transfers existing connections to new process on smooth upgrade. | non_design | connections migration on process smooth upgrade currently existing connections are not properly processed during the smooth upgrade process which depends on the specific protocol s behaviour for protocols that does not support things like goaway mosn will wait for a while and then close connections the goal of this issue is to build a protocol independent mechanism which transfers existing connections to new process on smooth upgrade | 0 |
423,267 | 12,293,501,567 | IssuesEvent | 2020-05-10 19:17:41 | saesrpg/saesrpg | https://api.github.com/repos/saesrpg/saesrpg | closed | Arms Dealers - Gain Stars on Weapon Sell / Weapon Purchase | Priority: Low Type: Tweak | Hey,
This is an antiquated suggestion which was previously agreed and approved on the old forums.
The idea was to make it so when you purchased arms illegally, from an arms dealer, you would gain stars.
This should also give the arms dealer stars for selling them.
This would also solve the issue with people selling outside of an SR circle unwanted and then entering the circle at the last minute.
Double to this, it will have a marked impact on AFK selling, as they will become wanted.
The thread approving this is in a now closed forum, so I cannot link it here. | 1.0 | Arms Dealers - Gain Stars on Weapon Sell / Weapon Purchase - Hey,
This is an antiquated suggestion which was previously agreed and approved on the old forums.
The idea was to make it so when you purchased arms illegally, from an arms dealer, you would gain stars.
This should also give the arms dealer stars for selling them.
This would also solve the issue with people selling outside of an SR circle unwanted and then entering the circle at the last minute.
Double to this, it will have a marked impact on AFK selling, as they will become wanted.
The thread approving this is in a now closed forum, so I cannot link it here. | non_design | arms dealers gain stars on weapon sell weapon purchase hey this is an antiquated suggestion which was previously agreed and approved on the old forums the idea was to make it so when you purchased arms illegally from an arms dealer you would gain stars this should also give the arms dealer stars for selling them this would also solve the issue with people selling outside of an sr circle unwanted and then entering the circle at the last minute double to this it will have a marked impact on afk selling as they will become wanted the thread approving this is in a now closed forum so i cannot link it here | 0 |
121,700 | 16,016,371,849 | IssuesEvent | 2021-04-20 16:30:26 | ZcashFoundation/zebra | https://api.github.com/repos/ZcashFoundation/zebra | opened | Replace redpallas stub in zebra-chain with full implementation | A-rust C-enhancement NU-5-TBC P-Medium S-needs-design S-needs-investigation S-needs-triage | **Is your feature request related to a problem? Please describe.**
To suffice types in the sapling->orchard port in zebra-chain, we created [`redpallas`](https://github.com/ZcashFoundation/zebra/blob/b8fab0464695bc7ffd63f947d2a72345447c9f99/zebra-chain/src/primitives/redpallas.rs) types but they are functionally incomplete. They need to be functional to verify SpendAuth and Binding signatures for NU5.
**Describe the solution you'd like**
@str4d has implemented [`reddsa` as a fork of `redjubjub`](https://github.com/str4d/redjubjub/tree/orchard) to abstract the common types and traits into a dependency for the [`redpallas` types in the `orchard` crate](https://github.com/zcash/orchard/blob/4b05c20a2ddac0eee9fbf9153cb081442124aec4/src/primitives/redpallas.rs). The reddsa orchard branch there defines the Orchard basepoints, which is not my favorite.
Should the `redjubjub` crate turn into something a more shared `reddsa`, that includes the `redjubjub` and `reddsa`? With FROST, it may be annoying to have 3 crates to juggle: `reddsa` as a dependency, `redjubjub`, `redpallas`, with boilerplate across them.
Or should we just duplicate where necessary?
| 1.0 | Replace redpallas stub in zebra-chain with full implementation - **Is your feature request related to a problem? Please describe.**
To suffice types in the sapling->orchard port in zebra-chain, we created [`redpallas`](https://github.com/ZcashFoundation/zebra/blob/b8fab0464695bc7ffd63f947d2a72345447c9f99/zebra-chain/src/primitives/redpallas.rs) types but they are functionally incomplete. They need to be functional to verify SpendAuth and Binding signatures for NU5.
**Describe the solution you'd like**
@str4d has implemented [`reddsa` as a fork of `redjubjub`](https://github.com/str4d/redjubjub/tree/orchard) to abstract the common types and traits into a dependency for the [`redpallas` types in the `orchard` crate](https://github.com/zcash/orchard/blob/4b05c20a2ddac0eee9fbf9153cb081442124aec4/src/primitives/redpallas.rs). The reddsa orchard branch there defines the Orchard basepoints, which is not my favorite.
Should the `redjubjub` crate turn into something a more shared `reddsa`, that includes the `redjubjub` and `reddsa`? With FROST, it may be annoying to have 3 crates to juggle: `reddsa` as a dependency, `redjubjub`, `redpallas`, with boilerplate across them.
Or should we just duplicate where necessary?
| design | replace redpallas stub in zebra chain with full implementation is your feature request related to a problem please describe to suffice types in the sapling orchard port in zebra chain we created types but they are functionally incomplete they need to be functional to verify spendauth and binding signatures for describe the solution you d like has implemented to abstract the common types and traits into a dependency for the the reddsa orchard branch there defines the orchard basepoints which is not my favorite should the redjubjub crate turn into something a more shared reddsa that includes the redjubjub and reddsa with frost it may be annoying to have crates to juggle reddsa as a dependency redjubjub redpallas with boilerplate across them or should we just duplicate where necessary | 1 |
119,645 | 15,591,631,952 | IssuesEvent | 2021-03-18 10:41:44 | CMD-JOBS/CMD-JOBS | https://api.github.com/repos/CMD-JOBS/CMD-JOBS | closed | Flow schetsen | design | Ik heb wireframe schetsen gemaakt van de flow app, ik heb de volgende functies inbegrepen:
- [ ] (eventuele) start/login scherm (Account)
- [ ] Profiel aanmaken (Voorkeuren)
- [ ] Lijst met voorgestelde Jobs (filter + opslaan)
- [ ] Detail pagina jobs
- [ ] Reageren op jobs (Contact)
Ik heb 2 verschillende opties getekend voor de flow jobs opslaan en reageren op jobs.
[wireframe schetsen](https://github.com/CMD-JOBS/CMD-JOBS/blob/main/docs/wireframes%20cmd%20jobs.pdf) | 1.0 | Flow schetsen - Ik heb wireframe schetsen gemaakt van de flow app, ik heb de volgende functies inbegrepen:
- [ ] (eventuele) start/login scherm (Account)
- [ ] Profiel aanmaken (Voorkeuren)
- [ ] Lijst met voorgestelde Jobs (filter + opslaan)
- [ ] Detail pagina jobs
- [ ] Reageren op jobs (Contact)
Ik heb 2 verschillende opties getekend voor de flow jobs opslaan en reageren op jobs.
[wireframe schetsen](https://github.com/CMD-JOBS/CMD-JOBS/blob/main/docs/wireframes%20cmd%20jobs.pdf) | design | flow schetsen ik heb wireframe schetsen gemaakt van de flow app ik heb de volgende functies inbegrepen eventuele start login scherm account profiel aanmaken voorkeuren lijst met voorgestelde jobs filter opslaan detail pagina jobs reageren op jobs contact ik heb verschillende opties getekend voor de flow jobs opslaan en reageren op jobs | 1 |
81,956 | 10,208,890,177 | IssuesEvent | 2019-08-14 11:18:27 | mapa17/breakfastclub | https://api.github.com/repos/mapa17/breakfastclub | closed | Maybe don't try to chat with a angry agent? | Design enhancement | Maybe an agent should not try to chat with a agent that is either quarreling or has the desire to do so?
Because unhappy agents won't get to the low state in order to recover? | 1.0 | Maybe don't try to chat with a angry agent? - Maybe an agent should not try to chat with a agent that is either quarreling or has the desire to do so?
Because unhappy agents won't get to the low state in order to recover? | design | maybe don t try to chat with a angry agent maybe an agent should not try to chat with a agent that is either quarreling or has the desire to do so because unhappy agents won t get to the low state in order to recover | 1 |
289,796 | 8,876,552,525 | IssuesEvent | 2019-01-12 16:09:04 | buttercup/buttercup-browser-extension | https://api.github.com/repos/buttercup/buttercup-browser-extension | closed | some input fields are not recognized by buttercup | Priority: Low Status: Completed Type: Site Support | I don't know why this does happen but there are some pages with login forms not recognized correctly by the buttercup addon. There is no buttercup icon next to the input field for the login name.
One example is https://kunde.comdirect.de/lp/wt/login:
 | 1.0 | some input fields are not recognized by buttercup - I don't know why this does happen but there are some pages with login forms not recognized correctly by the buttercup addon. There is no buttercup icon next to the input field for the login name.
One example is https://kunde.comdirect.de/lp/wt/login:
 | non_design | some input fields are not recognized by buttercup i don t know why this does happen but there are some pages with login forms not recognized correctly by the buttercup addon there is no buttercup icon next to the input field for the login name one example is | 0 |
97,479 | 12,237,645,275 | IssuesEvent | 2020-05-04 18:23:14 | crev-dev/cargo-crev | https://api.github.com/repos/crev-dev/cargo-crev | closed | `proofdb` module should probably be it's own crate | design enhancement refactor | It should be called `crev-wot` and be a layer between `crev-data` and `crev-lib`. It should be io-free, and implement all the logic around WoT of `crev`, so people could potentially reuse it, without having to deal with `crev-lib`, which is more of an end-user implementation of common operations. `crev-wot` might be useful for bots, scappers, central databases etc. Having it in it's own crate will make sure no accidental dependencies on `crev-lib` will be made, breaking the ordering of the layers. | 1.0 | `proofdb` module should probably be it's own crate - It should be called `crev-wot` and be a layer between `crev-data` and `crev-lib`. It should be io-free, and implement all the logic around WoT of `crev`, so people could potentially reuse it, without having to deal with `crev-lib`, which is more of an end-user implementation of common operations. `crev-wot` might be useful for bots, scappers, central databases etc. Having it in it's own crate will make sure no accidental dependencies on `crev-lib` will be made, breaking the ordering of the layers. | design | proofdb module should probably be it s own crate it should be called crev wot and be a layer between crev data and crev lib it should be io free and implement all the logic around wot of crev so people could potentially reuse it without having to deal with crev lib which is more of an end user implementation of common operations crev wot might be useful for bots scappers central databases etc having it in it s own crate will make sure no accidental dependencies on crev lib will be made breaking the ordering of the layers | 1 |
30,007 | 7,155,382,212 | IssuesEvent | 2018-01-26 12:32:38 | openvstorage/framework | https://api.github.com/repos/openvstorage/framework | closed | VDisk creation name validation doesnt work | state_codecomplete type_bug | Tried to make a vdisk with name '2' or any other integer, could initalize creation only to receive an error afterwards
> Adding vDisk failed: 'int' object has no attribute 'strip'
2 checks are faulty here:
- length of the name should be longer then 3 (as stated in the description)
- pure integers should either be allowed or mentioned in the description as invalid
| 1.0 | VDisk creation name validation doesnt work - Tried to make a vdisk with name '2' or any other integer, could initalize creation only to receive an error afterwards
> Adding vDisk failed: 'int' object has no attribute 'strip'
2 checks are faulty here:
- length of the name should be longer then 3 (as stated in the description)
- pure integers should either be allowed or mentioned in the description as invalid
| non_design | vdisk creation name validation doesnt work tried to make a vdisk with name or any other integer could initalize creation only to receive an error afterwards adding vdisk failed int object has no attribute strip checks are faulty here length of the name should be longer then as stated in the description pure integers should either be allowed or mentioned in the description as invalid | 0 |
826,741 | 31,710,946,753 | IssuesEvent | 2023-09-09 09:01:47 | SkriptLang/Skript | https://api.github.com/repos/SkriptLang/Skript | closed | Variables are loaded after Skript is finished loading | bug priority: medium completed | ### Skript/Server Version
```markdown
> sk info
[11:15:13 INFO]: [Skript] Skript's aliases can be found here: https://github.com/SkriptLang/skript-aliases
[11:15:13 INFO]: [Skript] Skript's documentation can be found here: https://docs.skriptlang.org/
[11:15:13 INFO]: [Skript] Skript's tutorials can be found here: https://docs.skriptlang.org/tutorials
[11:15:13 INFO]: [Skript] Server Version: git-Paper-101 (MC: 1.20.1)
[11:15:13 INFO]: [Skript] Skript Version: 2.7.0-nightly-755f59c (skriptlang-nightly)
[11:15:13 INFO]: [Skript] Installed Skript Addons:
[11:15:13 INFO]: [Skript] - skript-reflect v2.4-dev1 (https://github.com/TPGamesNL/skript-reflect)
[11:15:13 INFO]: [Skript] Installed dependencies: None
```
### Bug Description
Skript is loading variables AFTER Skript has finished loading, therefor variables in a load event are useless.
This is due to LimeGlass adding a delay for variables
https://github.com/SkriptLang/Skript/blob/7632dd8fb367778bf9f28b59e4f147f091d37302/src/main/java/ch/njol/skript/Skript.java#L607
Thus pushing variables to load AFTER everything else
TPGames brought this up during the PR
https://github.com/SkriptLang/Skript/pull/4873#discussion_r1019256633
### Expected Behavior
for variables to load before scripts load
### Steps to Reproduce
test code
```vb
on load:
send "&aLOADED MY SCRIPT WITH VAR %{var}%"
wait 1 tick
send "&bAFTER VARIABLES ARE LOADED VAR: %{var}%"
```
Outcome:
<img width="495" alt="Screenshot 2023-08-05 at 11 19 41 AM" src="https://github.com/SkriptLang/Skript/assets/20008482/8bb031e7-86b5-4a81-bfc8-03eaee5b2e4d">
### Errors or Screenshots
see above
### Other
_No response_
### Agreement
- [X] I have read the guidelines above and affirm I am following them with this report. | 1.0 | Variables are loaded after Skript is finished loading - ### Skript/Server Version
```markdown
> sk info
[11:15:13 INFO]: [Skript] Skript's aliases can be found here: https://github.com/SkriptLang/skript-aliases
[11:15:13 INFO]: [Skript] Skript's documentation can be found here: https://docs.skriptlang.org/
[11:15:13 INFO]: [Skript] Skript's tutorials can be found here: https://docs.skriptlang.org/tutorials
[11:15:13 INFO]: [Skript] Server Version: git-Paper-101 (MC: 1.20.1)
[11:15:13 INFO]: [Skript] Skript Version: 2.7.0-nightly-755f59c (skriptlang-nightly)
[11:15:13 INFO]: [Skript] Installed Skript Addons:
[11:15:13 INFO]: [Skript] - skript-reflect v2.4-dev1 (https://github.com/TPGamesNL/skript-reflect)
[11:15:13 INFO]: [Skript] Installed dependencies: None
```
### Bug Description
Skript is loading variables AFTER Skript has finished loading, therefor variables in a load event are useless.
This is due to LimeGlass adding a delay for variables
https://github.com/SkriptLang/Skript/blob/7632dd8fb367778bf9f28b59e4f147f091d37302/src/main/java/ch/njol/skript/Skript.java#L607
Thus pushing variables to load AFTER everything else
TPGames brought this up during the PR
https://github.com/SkriptLang/Skript/pull/4873#discussion_r1019256633
### Expected Behavior
for variables to load before scripts load
### Steps to Reproduce
test code
```vb
on load:
send "&aLOADED MY SCRIPT WITH VAR %{var}%"
wait 1 tick
send "&bAFTER VARIABLES ARE LOADED VAR: %{var}%"
```
Outcome:
<img width="495" alt="Screenshot 2023-08-05 at 11 19 41 AM" src="https://github.com/SkriptLang/Skript/assets/20008482/8bb031e7-86b5-4a81-bfc8-03eaee5b2e4d">
### Errors or Screenshots
see above
### Other
_No response_
### Agreement
- [X] I have read the guidelines above and affirm I am following them with this report. | non_design | variables are loaded after skript is finished loading skript server version markdown sk info skript s aliases can be found here skript s documentation can be found here skript s tutorials can be found here server version git paper mc skript version nightly skriptlang nightly installed skript addons skript reflect installed dependencies none bug description skript is loading variables after skript has finished loading therefor variables in a load event are useless this is due to limeglass adding a delay for variables thus pushing variables to load after everything else tpgames brought this up during the pr expected behavior for variables to load before scripts load steps to reproduce test code vb on load send aloaded my script with var var wait tick send bafter variables are loaded var var outcome img width alt screenshot at am src errors or screenshots see above other no response agreement i have read the guidelines above and affirm i am following them with this report | 0 |
114,961 | 14,668,725,070 | IssuesEvent | 2020-12-29 22:06:18 | department-of-veterans-affairs/va.gov-cms | https://api.github.com/repos/department-of-veterans-affairs/va.gov-cms | closed | Create a support section/area within the CMS | Design Epic Helpdesk & support Needs refining Research User guides ⭐️ CMS UX |
There is no single place where a CMS user can go to access help guides, view training information, request support, submit feedback and submit feature requests. As the VA.gov CMS grows in number of users there will need to be substantial self service resources available to users
As a CMS user I want to be able to access a self-service support section that will allow me to find information on how to use the CMS, get training, ask questions, submit feedback and request feature enhancements and submit a help desk request if needed (among other things potentially). Sections could be initially:
- Self service Help
- Training center
- Help desk
- Feedback
### Affected users and stakeholders
* CMS users
* CMS team, primarily trainers and help desk
### Hypothesis
_A hypothesis may depend on a spike ticket to be completed._
We believe that by enhancing the self service and overall support capabilities of the CMS that this solution will provide a better user experience to theCMS users with a robust support structure. We'll know that to be true when the number of users requesting support decreases because they are able to easier access this information.
### Assumptions
* Users would prefer to access help themselves rather than have to submit a ticket or request and wait for a response
* This will result in an improved overall user experience
(How will these assumptions be validated?)
## Acceptance Criteria
* Testable_Outcome_X
* Testable_Outcome_Y
* Testable_Outcome_Z
## Runbook
This is particularly relevant for feature launches, or for making changes to the content model that require front end changes as well.
1. Step_to_get_to_production_X
1. Step_to_get_to_production_Y
1. Step_to_get_to_production_Z
## Possible tickets to create for this epic
- [ ] Spike task, with some of the following attributes:
* Identify the baseline against which we will measure improvements
* Ideation (sketching, cross-displinary meeting of minds around how the problem may be solved)
* Analysis of the drupal landscape
* Possible implementation(s)
* Proof of concept or prototype
* UX writing discovery
- [ ] User research
- [ ] Design
- [ ] UX writing
- [ ] Usability testing (eg with a prototype or other design stimula)
- [ ] Implementation
- [ ] Documentation (What needs changing or adding to the documentation?
- [ ] Product release notes (How will we describe this feature to CMS users?)
- [ ] Training (Will any users require additional training?)
- [ ] Metrics (How will we measure any improvements)
## Labels for this issue
- [/] Issue type (red) (defaults to Epic)
- [ ] CMS subsystem (green)
- [ ] CMS practice area (blue)
- [ ] CMS objective (orange)
- [ ] CMS-supported product (black)
| 1.0 | Create a support section/area within the CMS -
There is no single place where a CMS user can go to access help guides, view training information, request support, submit feedback and submit feature requests. As the VA.gov CMS grows in number of users there will need to be substantial self service resources available to users
As a CMS user I want to be able to access a self-service support section that will allow me to find information on how to use the CMS, get training, ask questions, submit feedback and request feature enhancements and submit a help desk request if needed (among other things potentially). Sections could be initially:
- Self service Help
- Training center
- Help desk
- Feedback
### Affected users and stakeholders
* CMS users
* CMS team, primarily trainers and help desk
### Hypothesis
_A hypothesis may depend on a spike ticket to be completed._
We believe that by enhancing the self service and overall support capabilities of the CMS that this solution will provide a better user experience to theCMS users with a robust support structure. We'll know that to be true when the number of users requesting support decreases because they are able to easier access this information.
### Assumptions
* Users would prefer to access help themselves rather than have to submit a ticket or request and wait for a response
* This will result in an improved overall user experience
(How will these assumptions be validated?)
## Acceptance Criteria
* Testable_Outcome_X
* Testable_Outcome_Y
* Testable_Outcome_Z
## Runbook
This is particularly relevant for feature launches, or for making changes to the content model that require front end changes as well.
1. Step_to_get_to_production_X
1. Step_to_get_to_production_Y
1. Step_to_get_to_production_Z
## Possible tickets to create for this epic
- [ ] Spike task, with some of the following attributes:
* Identify the baseline against which we will measure improvements
* Ideation (sketching, cross-displinary meeting of minds around how the problem may be solved)
* Analysis of the drupal landscape
* Possible implementation(s)
* Proof of concept or prototype
* UX writing discovery
- [ ] User research
- [ ] Design
- [ ] UX writing
- [ ] Usability testing (eg with a prototype or other design stimula)
- [ ] Implementation
- [ ] Documentation (What needs changing or adding to the documentation?
- [ ] Product release notes (How will we describe this feature to CMS users?)
- [ ] Training (Will any users require additional training?)
- [ ] Metrics (How will we measure any improvements)
## Labels for this issue
- [/] Issue type (red) (defaults to Epic)
- [ ] CMS subsystem (green)
- [ ] CMS practice area (blue)
- [ ] CMS objective (orange)
- [ ] CMS-supported product (black)
| design | create a support section area within the cms there is no single place where a cms user can go to access help guides view training information request support submit feedback and submit feature requests as the va gov cms grows in number of users there will need to be substantial self service resources available to users as a cms user i want to be able to access a self service support section that will allow me to find information on how to use the cms get training ask questions submit feedback and request feature enhancements and submit a help desk request if needed among other things potentially sections could be initially self service help training center help desk feedback affected users and stakeholders cms users cms team primarily trainers and help desk hypothesis a hypothesis may depend on a spike ticket to be completed we believe that by enhancing the self service and overall support capabilities of the cms that this solution will provide a better user experience to thecms users with a robust support structure we ll know that to be true when the number of users requesting support decreases because they are able to easier access this information assumptions users would prefer to access help themselves rather than have to submit a ticket or request and wait for a response this will result in an improved overall user experience how will these assumptions be validated acceptance criteria testable outcome x testable outcome y testable outcome z runbook this is particularly relevant for feature launches or for making changes to the content model that require front end changes as well step to get to production x step to get to production y step to get to production z possible tickets to create for this epic spike task with some of the following attributes identify the baseline against which we will measure improvements ideation sketching cross displinary meeting of minds around how the problem may be solved analysis of the drupal landscape possible implementation s proof of concept or prototype ux writing discovery user research design ux writing usability testing eg with a prototype or other design stimula implementation documentation what needs changing or adding to the documentation product release notes how will we describe this feature to cms users training will any users require additional training metrics how will we measure any improvements labels for this issue issue type red defaults to epic cms subsystem green cms practice area blue cms objective orange cms supported product black | 1 |
145,797 | 22,782,363,225 | IssuesEvent | 2022-07-08 21:36:01 | department-of-veterans-affairs/vets-design-system-documentation | https://api.github.com/repos/department-of-veterans-affairs/vets-design-system-documentation | closed | Update Experimental Design description and process | vsp-design-system-team | ### Duplicate check
- [X] I've searched for any related issues and avoided creating a duplicate issue.
### This update is for:
Other
### What is the name?
Experimental design process
### What is the nature of this update?
- [ ] How to build this component/pattern
- [ ] When to use this component/pattern
- [ ] When to use something else
- [X] Usability guidance
- [ ] Accessibility
- [ ] Implementation
- [ ] Research insights
- [ ] Package information
### What problem does this solve?
The experimental design process and description needs to be updated with the feedback we have received to make the process better for contributors and more streamlined.
### Additional Context
_No response_ | 1.0 | Update Experimental Design description and process - ### Duplicate check
- [X] I've searched for any related issues and avoided creating a duplicate issue.
### This update is for:
Other
### What is the name?
Experimental design process
### What is the nature of this update?
- [ ] How to build this component/pattern
- [ ] When to use this component/pattern
- [ ] When to use something else
- [X] Usability guidance
- [ ] Accessibility
- [ ] Implementation
- [ ] Research insights
- [ ] Package information
### What problem does this solve?
The experimental design process and description needs to be updated with the feedback we have received to make the process better for contributors and more streamlined.
### Additional Context
_No response_ | design | update experimental design description and process duplicate check i ve searched for any related issues and avoided creating a duplicate issue this update is for other what is the name experimental design process what is the nature of this update how to build this component pattern when to use this component pattern when to use something else usability guidance accessibility implementation research insights package information what problem does this solve the experimental design process and description needs to be updated with the feedback we have received to make the process better for contributors and more streamlined additional context no response | 1 |
16,646 | 10,547,781,776 | IssuesEvent | 2019-10-03 02:44:12 | terraform-providers/terraform-provider-azurerm | https://api.github.com/repos/terraform-providers/terraform-provider-azurerm | closed | Feature Request: Get object_id of current user | enhancement service/authentication | <!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Description
<!--- Please leave a helpful description of the feature request here. --->
Terraform AzureRM provider currently supports getting the object ID of the logged in Service Principal, but not the object ID of the logged in user.
We can use the `azurerm_client_config` data source to get the current Service Principal object ID (`service_principal_object_id`). It would be nice to be able to get the current user object ID as well.
Use case: For currently logged in user to be able to self-assign permissions, for example when creating Key Vault. For reference Azure CLI does this when creating Key Vault using `az keyvault create`.
### New or Affected Resource(s)
<!--- Please list the new or affected resources and data sources. --->
* azurerm_client_config
### Potential Terraform Configuration
<!--- Information about code formatting: https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code --->
```hcl
data "azurerm_client_config" "current" {}
output "user_object_id" {
value = "${data.azurerm_client_config.current.user_object_id}"
}
```
### References
<!---
Information about referencing Github Issues: https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests
Are there any other GitHub issues (open or closed) or pull requests that should be linked here? Vendor blog posts or documentation? For example:
* https://azure.microsoft.com/en-us/roadmap/virtual-network-service-endpoint-for-azure-cosmos-db/
--->
* https://godoc.org/github.com/Azure/azure-sdk-for-go/services/graphrbac/1.6/graphrbac#SignedInUserClient
* https://godoc.org/github.com/Azure/azure-sdk-for-go/services/graphrbac/1.6/graphrbac#User | 1.0 | Feature Request: Get object_id of current user - <!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Description
<!--- Please leave a helpful description of the feature request here. --->
Terraform AzureRM provider currently supports getting the object ID of the logged in Service Principal, but not the object ID of the logged in user.
We can use the `azurerm_client_config` data source to get the current Service Principal object ID (`service_principal_object_id`). It would be nice to be able to get the current user object ID as well.
Use case: For currently logged in user to be able to self-assign permissions, for example when creating Key Vault. For reference Azure CLI does this when creating Key Vault using `az keyvault create`.
### New or Affected Resource(s)
<!--- Please list the new or affected resources and data sources. --->
* azurerm_client_config
### Potential Terraform Configuration
<!--- Information about code formatting: https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code --->
```hcl
data "azurerm_client_config" "current" {}
output "user_object_id" {
value = "${data.azurerm_client_config.current.user_object_id}"
}
```
### References
<!---
Information about referencing Github Issues: https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests
Are there any other GitHub issues (open or closed) or pull requests that should be linked here? Vendor blog posts or documentation? For example:
* https://azure.microsoft.com/en-us/roadmap/virtual-network-service-endpoint-for-azure-cosmos-db/
--->
* https://godoc.org/github.com/Azure/azure-sdk-for-go/services/graphrbac/1.6/graphrbac#SignedInUserClient
* https://godoc.org/github.com/Azure/azure-sdk-for-go/services/graphrbac/1.6/graphrbac#User | non_design | feature request get object id of current user community note please vote on this issue by adding a 👍 to the original issue to help the community and maintainers prioritize this request please do not leave or me too comments they generate extra noise for issue followers and do not help prioritize the request if you are interested in working on this issue or have submitted a pull request please leave a comment description terraform azurerm provider currently supports getting the object id of the logged in service principal but not the object id of the logged in user we can use the azurerm client config data source to get the current service principal object id service principal object id it would be nice to be able to get the current user object id as well use case for currently logged in user to be able to self assign permissions for example when creating key vault for reference azure cli does this when creating key vault using az keyvault create new or affected resource s azurerm client config potential terraform configuration hcl data azurerm client config current output user object id value data azurerm client config current user object id references information about referencing github issues are there any other github issues open or closed or pull requests that should be linked here vendor blog posts or documentation for example | 0 |
113,526 | 14,443,617,356 | IssuesEvent | 2020-12-07 19:56:01 | stoolball-england/stoolball-org-uk | https://api.github.com/repos/stoolball-england/stoolball-org-uk | closed | Change icons to Material UI or IconMonstr | design mvp | Store the icons locally because Chrome sometimes blocks them as a cross origin resource from svgbox.io (plus it goes down).
* [x] account
* [x] menu
* [x] add
* [x] settings
* [x] delete
* [x] twitter
* [x] facebook
* [x] instagram
* [x] youtube
* [x] padlock
* [x] light bulb | 1.0 | Change icons to Material UI or IconMonstr - Store the icons locally because Chrome sometimes blocks them as a cross origin resource from svgbox.io (plus it goes down).
* [x] account
* [x] menu
* [x] add
* [x] settings
* [x] delete
* [x] twitter
* [x] facebook
* [x] instagram
* [x] youtube
* [x] padlock
* [x] light bulb | design | change icons to material ui or iconmonstr store the icons locally because chrome sometimes blocks them as a cross origin resource from svgbox io plus it goes down account menu add settings delete twitter facebook instagram youtube padlock light bulb | 1 |
92,945 | 11,727,408,808 | IssuesEvent | 2020-03-10 15:54:22 | ParabolInc/parabol | https://api.github.com/repos/ParabolInc/parabol | closed | Design custom max votes | design | Users want to customize how many votes each person gets & how many votes they can cast on each reflection group. Since this is a meeting setting, it should probably live in some kind of an input in the /new-meeting view
Ideas:
- 2 numeric inputs (good, but allows for errors, e.g. too big a number, max votes < max group votes, etc.
- 2 dropdowns (fewer errors, can adjust values after each field is updated)
- a slider with 2 dots (sliders are good for large numbers like volume sliders 0-100, maybe 0-10 isn't big enough)
- 2 steppers (a la airbnb) https://www.nngroup.com/articles/input-steppers/. this feels right for smaller, more exact values. when the max votes stepper is smaller than the max group votes, it updates both
AC
- [ ] When starting a retro, a user can select how many votes each person gets
- [ ] When starting a retro, a user can select how many votes each person can cast for a single reflection group
- [ ] it's impossible to have an invalid value or error message (e.g. when 1 updates & the other is relationally invalid, the other updates)
| 1.0 | Design custom max votes - Users want to customize how many votes each person gets & how many votes they can cast on each reflection group. Since this is a meeting setting, it should probably live in some kind of an input in the /new-meeting view
Ideas:
- 2 numeric inputs (good, but allows for errors, e.g. too big a number, max votes < max group votes, etc.
- 2 dropdowns (fewer errors, can adjust values after each field is updated)
- a slider with 2 dots (sliders are good for large numbers like volume sliders 0-100, maybe 0-10 isn't big enough)
- 2 steppers (a la airbnb) https://www.nngroup.com/articles/input-steppers/. this feels right for smaller, more exact values. when the max votes stepper is smaller than the max group votes, it updates both
AC
- [ ] When starting a retro, a user can select how many votes each person gets
- [ ] When starting a retro, a user can select how many votes each person can cast for a single reflection group
- [ ] it's impossible to have an invalid value or error message (e.g. when 1 updates & the other is relationally invalid, the other updates)
| design | design custom max votes users want to customize how many votes each person gets how many votes they can cast on each reflection group since this is a meeting setting it should probably live in some kind of an input in the new meeting view ideas numeric inputs good but allows for errors e g too big a number max votes max group votes etc dropdowns fewer errors can adjust values after each field is updated a slider with dots sliders are good for large numbers like volume sliders maybe isn t big enough steppers a la airbnb this feels right for smaller more exact values when the max votes stepper is smaller than the max group votes it updates both ac when starting a retro a user can select how many votes each person gets when starting a retro a user can select how many votes each person can cast for a single reflection group it s impossible to have an invalid value or error message e g when updates the other is relationally invalid the other updates | 1 |
147,688 | 23,255,143,472 | IssuesEvent | 2022-08-04 08:37:05 | BSData/wh40k | https://api.github.com/repos/BSData/wh40k | closed | Imperium - Adeptus Custodes: QoL request | Area: edit UX ✔ Res: by design 💾 Cat: Imperium - Adeptus Custodes Type: request enhancement | I would like to ask one request.
The Tarsus Buckler doesn't change the save characteristic to 2+ automatically.
Can someone program it for do it automatically?
Thank you guys, you are the best :).
| 1.0 | Imperium - Adeptus Custodes: QoL request - I would like to ask one request.
The Tarsus Buckler doesn't change the save characteristic to 2+ automatically.
Can someone program it for do it automatically?
Thank you guys, you are the best :).
| design | imperium adeptus custodes qol request i would like to ask one request the tarsus buckler doesn t change the save characteristic to automatically can someone program it for do it automatically thank you guys you are the best | 1 |
332,785 | 24,349,918,955 | IssuesEvent | 2022-10-02 20:20:15 | Harlem-Launch-Alliance/Catalyst-2 | https://api.github.com/repos/Harlem-Launch-Alliance/Catalyst-2 | closed | replace unsigned int | documentation beginner | in `void loop()`, tickTime should use `uint32_t` instead of `unsigned int`. This will help with clarity. | 1.0 | replace unsigned int - in `void loop()`, tickTime should use `uint32_t` instead of `unsigned int`. This will help with clarity. | non_design | replace unsigned int in void loop ticktime should use t instead of unsigned int this will help with clarity | 0 |
116,693 | 14,992,076,594 | IssuesEvent | 2021-01-29 09:21:15 | sButtons/sbuttons | https://api.github.com/repos/sButtons/sbuttons | opened | Sidebar behavior before scroll | Priority: Medium bug design good first issue help wanted up-for-grabs website | Before scroll, the sidebar's width is larger than when scrolling. The sidebar's width should always be the same. This is in the documentation and examples pages. | 1.0 | Sidebar behavior before scroll - Before scroll, the sidebar's width is larger than when scrolling. The sidebar's width should always be the same. This is in the documentation and examples pages. | design | sidebar behavior before scroll before scroll the sidebar s width is larger than when scrolling the sidebar s width should always be the same this is in the documentation and examples pages | 1 |
334,176 | 24,407,505,433 | IssuesEvent | 2022-10-05 09:18:02 | SolidLabResearch/solid-todo | https://api.github.com/repos/SolidLabResearch/solid-todo | closed | Discussion: Connect App with Solid | documentation | We are obviously going to use Solid, but where and for what? It believe it makes sense to think about the data we need and want for the app to function:
- storage for the Todos
- name Pod owner (profile picture?)
- friends (for sharing)
- annotating/enhancing Todos with data from our/foreign pods?
- ... | 1.0 | Discussion: Connect App with Solid - We are obviously going to use Solid, but where and for what? It believe it makes sense to think about the data we need and want for the app to function:
- storage for the Todos
- name Pod owner (profile picture?)
- friends (for sharing)
- annotating/enhancing Todos with data from our/foreign pods?
- ... | non_design | discussion connect app with solid we are obviously going to use solid but where and for what it believe it makes sense to think about the data we need and want for the app to function storage for the todos name pod owner profile picture friends for sharing annotating enhancing todos with data from our foreign pods | 0 |
81,647 | 10,163,916,355 | IssuesEvent | 2019-08-07 10:21:21 | iov-one/weave | https://api.github.com/repos/iov-one/weave | closed | Secure key management | :chipmunk: design | Implement Secure key management.
It is best to use key storage with the ability to set the current key. Then when we use bnscli it just automagically takes the chosen key or errors out if none is chosen. We won't have to tell bnscli anything then as it will already know.
Proposal (by @ruseinov):
1. Use Encrypt/Decrypt from cosmos-sdk as described here: https://github.com/iov-one/weave/issues/855#issuecomment-509589061 to encrypt/decrypt the file.
2. Use protobuf objects like these (write them into two separate files):
```
message EncryptedStore {
string mnemonic = 1;
repeated Key keys = 2; ( { name, hexEncodedprivateKey }, sequence is an index within the array
}
message PublicStore {
repeated PubKey keys = 1; ({ name, pubKey, address}), sequence and name correspond to those of encryptedStore
}
```
to store data.
3. Use the flow described in https://github.com/iov-one/weave/issues/855#issuecomment-509587069 for create/list/sign.
### Key derivation
See https://github.com/iov-one/weave/issues/856#issuecomment-509584815 for details | 1.0 | Secure key management - Implement Secure key management.
It is best to use key storage with the ability to set the current key. Then when we use bnscli it just automagically takes the chosen key or errors out if none is chosen. We won't have to tell bnscli anything then as it will already know.
Proposal (by @ruseinov):
1. Use Encrypt/Decrypt from cosmos-sdk as described here: https://github.com/iov-one/weave/issues/855#issuecomment-509589061 to encrypt/decrypt the file.
2. Use protobuf objects like these (write them into two separate files):
```
message EncryptedStore {
string mnemonic = 1;
repeated Key keys = 2; ( { name, hexEncodedprivateKey }, sequence is an index within the array
}
message PublicStore {
repeated PubKey keys = 1; ({ name, pubKey, address}), sequence and name correspond to those of encryptedStore
}
```
to store data.
3. Use the flow described in https://github.com/iov-one/weave/issues/855#issuecomment-509587069 for create/list/sign.
### Key derivation
See https://github.com/iov-one/weave/issues/856#issuecomment-509584815 for details | design | secure key management implement secure key management it is best to use key storage with the ability to set the current key then when we use bnscli it just automagically takes the chosen key or errors out if none is chosen we won t have to tell bnscli anything then as it will already know proposal by ruseinov use encrypt decrypt from cosmos sdk as described here to encrypt decrypt the file use protobuf objects like these write them into two separate files message encryptedstore string mnemonic repeated key keys name hexencodedprivatekey sequence is an index within the array message publicstore repeated pubkey keys name pubkey address sequence and name correspond to those of encryptedstore to store data use the flow described in for create list sign key derivation see for details | 1 |
426,497 | 29,521,593,829 | IssuesEvent | 2023-06-05 02:42:37 | jenkinsci/configuration-as-code-plugin | https://api.github.com/repos/jenkinsci/configuration-as-code-plugin | opened | Missing documentation link from the main page | documentation | ### Describe your use-case which is not covered by existing documentation.
In the [Initial Configuration](https://github.com/jenkinsci/configuration-as-code-plugin#initial-configuration) section of the main documentation, also used in the [main page](https://plugins.jenkins.io/configuration-as-code/) of the plugin, there is a missing reference to the documentation "Click the Documentation link at the bottom of the Configuration as Code page.".
The "Documentation link" doesn't exist anywhere on the page and furthermore, the [demos readme](https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/demos/jenkins/README.md) mentions that "The full list is available in the generated documentation.", without a reference to where the generated document is.
Happy to help improve the documentation if there would be any guidance from the maintainers regarding where the documentations for the two issues above could be given.
Thank you!
### Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.
_No response_ | 1.0 | Missing documentation link from the main page - ### Describe your use-case which is not covered by existing documentation.
In the [Initial Configuration](https://github.com/jenkinsci/configuration-as-code-plugin#initial-configuration) section of the main documentation, also used in the [main page](https://plugins.jenkins.io/configuration-as-code/) of the plugin, there is a missing reference to the documentation "Click the Documentation link at the bottom of the Configuration as Code page.".
The "Documentation link" doesn't exist anywhere on the page and furthermore, the [demos readme](https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/demos/jenkins/README.md) mentions that "The full list is available in the generated documentation.", without a reference to where the generated document is.
Happy to help improve the documentation if there would be any guidance from the maintainers regarding where the documentations for the two issues above could be given.
Thank you!
### Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.
_No response_ | non_design | missing documentation link from the main page describe your use case which is not covered by existing documentation in the section of the main documentation also used in the of the plugin there is a missing reference to the documentation click the documentation link at the bottom of the configuration as code page the documentation link doesn t exist anywhere on the page and furthermore the mentions that the full list is available in the generated documentation without a reference to where the generated document is happy to help improve the documentation if there would be any guidance from the maintainers regarding where the documentations for the two issues above could be given thank you reference any relevant documentation other materials or issues pull requests that can be used for inspiration no response | 0 |
138,817 | 20,727,183,007 | IssuesEvent | 2022-03-14 04:23:17 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | [Security Solution] Overview page left column grows too wide when timeline description text is long | bug design impact:low Team:Threat Hunting fixed Team: SecuritySolution responsive design Team:Threat Hunting:Explore | **Kibana version:** 8.1.0 BC1
**Elasticsearch version:** 8.1.0 BC1
**Server OS version:** Elastic Cloud ESS default
**Browser version:** Google Chrome Version 98.0.4758.102 (Official Build) (x86_64)
**Browser OS version:** macOS Monterey Version 12.2.1 (21D62)
**Original install method (e.g. download page, yum, from source, etc.):** Elastic Cloud ESS GCP Europe-West-1
**Describe the bug:**
When long text without spaces is added to a Timeline description and that Timeline is recent or favorited to appear on the Security Overview page, it causes the left "column" of the overview page to expand horizontally too far to the right
**Steps to reproduce:**
1. Create a Timeline investigation
2. Edit the timeline to give it a name and a description.
3. In the description, add a long string of characters without spaces, such as a URL.
4. Add the timeline to Favorites
5. Go to overview page and select favorite timelines
6. Note that the left "column" of the page extends as far right as the description string is long.
**Expected behavior:**
The description string should be force-wrapped if it exceeds some number of characters.
**Screenshots (if relevant):**
<img width="1254" alt="image" src="https://user-images.githubusercontent.com/22619280/155127250-7840dea4-8947-47ee-946d-d41bf22af262.png">
**Errors in browser console (if relevant):** None
**Provide logs and/or server output (if relevant):** N/A
**Any additional context:** Related bug first reported by Elastic InfoSec on 07-Feb-2022.
| 2.0 | [Security Solution] Overview page left column grows too wide when timeline description text is long - **Kibana version:** 8.1.0 BC1
**Elasticsearch version:** 8.1.0 BC1
**Server OS version:** Elastic Cloud ESS default
**Browser version:** Google Chrome Version 98.0.4758.102 (Official Build) (x86_64)
**Browser OS version:** macOS Monterey Version 12.2.1 (21D62)
**Original install method (e.g. download page, yum, from source, etc.):** Elastic Cloud ESS GCP Europe-West-1
**Describe the bug:**
When long text without spaces is added to a Timeline description and that Timeline is recent or favorited to appear on the Security Overview page, it causes the left "column" of the overview page to expand horizontally too far to the right
**Steps to reproduce:**
1. Create a Timeline investigation
2. Edit the timeline to give it a name and a description.
3. In the description, add a long string of characters without spaces, such as a URL.
4. Add the timeline to Favorites
5. Go to overview page and select favorite timelines
6. Note that the left "column" of the page extends as far right as the description string is long.
**Expected behavior:**
The description string should be force-wrapped if it exceeds some number of characters.
**Screenshots (if relevant):**
<img width="1254" alt="image" src="https://user-images.githubusercontent.com/22619280/155127250-7840dea4-8947-47ee-946d-d41bf22af262.png">
**Errors in browser console (if relevant):** None
**Provide logs and/or server output (if relevant):** N/A
**Any additional context:** Related bug first reported by Elastic InfoSec on 07-Feb-2022.
| design | overview page left column grows too wide when timeline description text is long kibana version elasticsearch version server os version elastic cloud ess default browser version google chrome version official build browser os version macos monterey version original install method e g download page yum from source etc elastic cloud ess gcp europe west describe the bug when long text without spaces is added to a timeline description and that timeline is recent or favorited to appear on the security overview page it causes the left column of the overview page to expand horizontally too far to the right steps to reproduce create a timeline investigation edit the timeline to give it a name and a description in the description add a long string of characters without spaces such as a url add the timeline to favorites go to overview page and select favorite timelines note that the left column of the page extends as far right as the description string is long expected behavior the description string should be force wrapped if it exceeds some number of characters screenshots if relevant img width alt image src errors in browser console if relevant none provide logs and or server output if relevant n a any additional context related bug first reported by elastic infosec on feb | 1 |
590,095 | 17,770,837,953 | IssuesEvent | 2021-08-30 13:29:24 | enviroCar/enviroCar-app | https://api.github.com/repos/enviroCar/enviroCar-app | closed | Enhance interaction with Paired devices | enhancement 0 - Backlog Priority - 3 - Low | **Actual Behaviour**
1) No option to deselect the paired device .
2) Clicking on whole view nothing happens.
https://user-images.githubusercontent.com/70392921/107059051-5d051b00-67fb-11eb-852d-769e34ed6e01.mp4
**I will work on this issue.**
| 1.0 | Enhance interaction with Paired devices - **Actual Behaviour**
1) No option to deselect the paired device .
2) Clicking on whole view nothing happens.
https://user-images.githubusercontent.com/70392921/107059051-5d051b00-67fb-11eb-852d-769e34ed6e01.mp4
**I will work on this issue.**
| non_design | enhance interaction with paired devices actual behaviour no option to deselect the paired device clicking on whole view nothing happens i will work on this issue | 0 |
704,943 | 24,215,599,077 | IssuesEvent | 2022-09-26 06:23:11 | OptimistikSAS/OIBus | https://api.github.com/repos/OptimistikSAS/OIBus | closed | [HistoryQuery] - Store values in the north cache database | bug priority:medium dev issue feature:history-query | The addValues method in history query engine may generate a problem since we cannot retrieve the queryPart (because of the flush function in the ProtocolHandler.class.js).
Instead, we should find a way to add the values in the associated north db (like OIBusEngine does). This db should be in the historyQuery cache folder. I think we have almost all we need to make this logic now | 1.0 | [HistoryQuery] - Store values in the north cache database - The addValues method in history query engine may generate a problem since we cannot retrieve the queryPart (because of the flush function in the ProtocolHandler.class.js).
Instead, we should find a way to add the values in the associated north db (like OIBusEngine does). This db should be in the historyQuery cache folder. I think we have almost all we need to make this logic now | non_design | store values in the north cache database the addvalues method in history query engine may generate a problem since we cannot retrieve the querypart because of the flush function in the protocolhandler class js instead we should find a way to add the values in the associated north db like oibusengine does this db should be in the historyquery cache folder i think we have almost all we need to make this logic now | 0 |
114,238 | 24,571,416,582 | IssuesEvent | 2022-10-13 08:56:39 | UniMath/UniMath | https://api.github.com/repos/UniMath/UniMath | reopened | Colimits in HSET | code change - just do | 1. To construct colimits of arbitrary functors C -> HSET (using setquot)
2. To construct, for any h-set X an isomorphism between X and the colimit of its finite subsets (a finite subset is defined as S : X -> hProp such that isfinite ( carrier S ) ) .
I have looked through it on paper and it seems to work.
| 1.0 | Colimits in HSET - 1. To construct colimits of arbitrary functors C -> HSET (using setquot)
2. To construct, for any h-set X an isomorphism between X and the colimit of its finite subsets (a finite subset is defined as S : X -> hProp such that isfinite ( carrier S ) ) .
I have looked through it on paper and it seems to work.
| non_design | colimits in hset to construct colimits of arbitrary functors c hset using setquot to construct for any h set x an isomorphism between x and the colimit of its finite subsets a finite subset is defined as s x hprop such that isfinite carrier s i have looked through it on paper and it seems to work | 0 |
175,892 | 27,989,643,985 | IssuesEvent | 2023-03-27 01:49:35 | 202212-GIZ-YE-FEW/iDev | https://api.github.com/repos/202212-GIZ-YE-FEW/iDev | opened | Design like-button Multiple Choices | needs-detailed-design | **Task title**
Design like-button Multiple Choices
**Task description**
Design well-apperance choices looks like button, taking into account checked input style.
**Screenshots**
**Link to the component on Figma**
[Checked choice](https://www.figma.com/file/r2YCuflKtmP8FK2KVXhnNx/Online-Therapist?node-id=279-5668&t=DD6EMQdwZQDBT8YE-4)
[Unchecked choice](https://www.figma.com/file/r2YCuflKtmP8FK2KVXhnNx/Online-Therapist?node-id=279-5671&t=DD6EMQdwZQDBT8YE-4)
| 1.0 | Design like-button Multiple Choices - **Task title**
Design like-button Multiple Choices
**Task description**
Design well-apperance choices looks like button, taking into account checked input style.
**Screenshots**
**Link to the component on Figma**
[Checked choice](https://www.figma.com/file/r2YCuflKtmP8FK2KVXhnNx/Online-Therapist?node-id=279-5668&t=DD6EMQdwZQDBT8YE-4)
[Unchecked choice](https://www.figma.com/file/r2YCuflKtmP8FK2KVXhnNx/Online-Therapist?node-id=279-5671&t=DD6EMQdwZQDBT8YE-4)
| design | design like button multiple choices task title design like button multiple choices task description design well apperance choices looks like button taking into account checked input style screenshots link to the component on figma | 1 |
62,235 | 3,179,644,620 | IssuesEvent | 2015-09-25 03:17:29 | cjfields/redmine-test | https://api.github.com/repos/cjfields/redmine-test | opened | implement Bio::PopGen::IO::haploview.pm | Category: Unclassified Priority: Low Status: New Tracker: Feature | ---
Author Name: **Albert Vilella** (Albert Vilella)
Original Redmine Issue: 1881, https://redmine.open-bio.org/issues/1881
Original Date: 2005-10-14
Original Assignee: Bioperl Guts
---
Haploview format is mostly similar to the already present (hapmap.org) Hapmap format, without a couple or three of the columns (that were added in hapmap).
snip
\#\#date Fri Oct 14 08:27:50 2005
\#\#population All
\#\#sequence-region Chr21 21000001 21500000
\#\#source gbrowse HaploviewDumper plugin
id alleles chrom pos strand assembly\# center NA17102 NA17103 NA17104 NA17105 NA17106 NA17107 NA17108 NA17109 NA17110 NA17111 NA17112 NA17113 NA17114 NA17115 NA17116 NA17133 NA17134 NA17135 NA17136 NA17137 NA17138 NA17139 NA17140 NA06990 NA07019 NA07348 NA07349 NA10830 NA10831 NA10842 NA10843 NA10844 NA10845 NA10848 NA10850 NA10851 NA10852 NA10853 NA10854 NA10857 NA10858 NA10860 NA10861 NA12547 NA12548 NA12560 NA17201 NA17733 NA17734 NA17735 NA17736 NA17737 NA17738 NA17739 NA17740 NA17741 NA17742 NA17743 NA17744 NA17745 NA17746 NA17747 NA17749 NA17752 NA17753 NA17754 NA17755 NA17756 NA17757 NA17759 NA17761
afd0023980 G/A chr21 21000458 + ncbi\_b34 perlegen AA GA GA AA NN AA AA AA AA NN AA AA AA AA AA AA AA GG AA AA AA AA AA NN AA AA AA AA NN AA GG AA AA AA AA AA AA GA AA AA AA AA GA AA AA AA AA AA GG AA AA AA AA AA AA AA AA AA GA GA AA AA AA GA AA AA AA AA AA GA AA
afd0023983 T/C chr21 21002155 + ncbi\_b34 perlegen TT TC TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TC TT TT TT TT TT TT TC TT TT TT TT TT TT TT TT TT TT TT TT TT CC TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT
| 1.0 | implement Bio::PopGen::IO::haploview.pm - ---
Author Name: **Albert Vilella** (Albert Vilella)
Original Redmine Issue: 1881, https://redmine.open-bio.org/issues/1881
Original Date: 2005-10-14
Original Assignee: Bioperl Guts
---
Haploview format is mostly similar to the already present (hapmap.org) Hapmap format, without a couple or three of the columns (that were added in hapmap).
snip
\#\#date Fri Oct 14 08:27:50 2005
\#\#population All
\#\#sequence-region Chr21 21000001 21500000
\#\#source gbrowse HaploviewDumper plugin
id alleles chrom pos strand assembly\# center NA17102 NA17103 NA17104 NA17105 NA17106 NA17107 NA17108 NA17109 NA17110 NA17111 NA17112 NA17113 NA17114 NA17115 NA17116 NA17133 NA17134 NA17135 NA17136 NA17137 NA17138 NA17139 NA17140 NA06990 NA07019 NA07348 NA07349 NA10830 NA10831 NA10842 NA10843 NA10844 NA10845 NA10848 NA10850 NA10851 NA10852 NA10853 NA10854 NA10857 NA10858 NA10860 NA10861 NA12547 NA12548 NA12560 NA17201 NA17733 NA17734 NA17735 NA17736 NA17737 NA17738 NA17739 NA17740 NA17741 NA17742 NA17743 NA17744 NA17745 NA17746 NA17747 NA17749 NA17752 NA17753 NA17754 NA17755 NA17756 NA17757 NA17759 NA17761
afd0023980 G/A chr21 21000458 + ncbi\_b34 perlegen AA GA GA AA NN AA AA AA AA NN AA AA AA AA AA AA AA GG AA AA AA AA AA NN AA AA AA AA NN AA GG AA AA AA AA AA AA GA AA AA AA AA GA AA AA AA AA AA GG AA AA AA AA AA AA AA AA AA GA GA AA AA AA GA AA AA AA AA AA GA AA
afd0023983 T/C chr21 21002155 + ncbi\_b34 perlegen TT TC TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TC TT TT TT TT TT TT TC TT TT TT TT TT TT TT TT TT TT TT TT TT CC TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT TT
| non_design | implement bio popgen io haploview pm author name albert vilella albert vilella original redmine issue original date original assignee bioperl guts haploview format is mostly similar to the already present hapmap org hapmap format without a couple or three of the columns that were added in hapmap snip date fri oct population all sequence region source gbrowse haploviewdumper plugin id alleles chrom pos strand assembly center g a ncbi perlegen aa ga ga aa nn aa aa aa aa nn aa aa aa aa aa aa aa gg aa aa aa aa aa nn aa aa aa aa nn aa gg aa aa aa aa aa aa ga aa aa aa aa ga aa aa aa aa aa gg aa aa aa aa aa aa aa aa aa ga ga aa aa aa ga aa aa aa aa aa ga aa t c ncbi perlegen tt tc tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tc tt tt tt tt tt tt tc tt tt tt tt tt tt tt tt tt tt tt tt tt cc tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt tt | 0 |
91,283 | 11,491,640,259 | IssuesEvent | 2020-02-11 19:23:16 | OpenLiberty/open-liberty | https://api.github.com/repos/OpenLiberty/open-liberty | closed | Liberty Dev Mode | Design Approved Epic In Progress Non-Release | What commercial Liberty edition does this feature belong in (pick one)?
Open Liberty
Should this feature be included in the Bluemix buildpack?
No
What SalesForce Skill/Mission Team and legacy RETAIN queue will be responsible for supporting this feature?
None. This feature will be part of the Maven plugins
Provide a Dev Mode for Liberty that enables developers to focus on coding without needing to repeatedly compile, package and then deploy their applications to test. IOW, fast and efficient inner loop development.
This includes doing hot deploy with background compilation of changed classes, hot reload of changed resource/properties files and reload on first request (e.g. browser refresh) should changes are detected in the workspace (project).
Developers can use Boost to launch Liberty into Dev Mode, edit their Maven or Gradle-built applications with their favourite editor (any IDE), changes will be automatically compiled and re-loaded where they can test right away.
Should enable developers to run and run JUnit tests simultaneous (from their IDE) with Dev Mode running too. Provide facilities (like Liberty-specific annotations) to developers to simplify what they need to do to setup their tests. | 1.0 | Liberty Dev Mode - What commercial Liberty edition does this feature belong in (pick one)?
Open Liberty
Should this feature be included in the Bluemix buildpack?
No
What SalesForce Skill/Mission Team and legacy RETAIN queue will be responsible for supporting this feature?
None. This feature will be part of the Maven plugins
Provide a Dev Mode for Liberty that enables developers to focus on coding without needing to repeatedly compile, package and then deploy their applications to test. IOW, fast and efficient inner loop development.
This includes doing hot deploy with background compilation of changed classes, hot reload of changed resource/properties files and reload on first request (e.g. browser refresh) should changes are detected in the workspace (project).
Developers can use Boost to launch Liberty into Dev Mode, edit their Maven or Gradle-built applications with their favourite editor (any IDE), changes will be automatically compiled and re-loaded where they can test right away.
Should enable developers to run and run JUnit tests simultaneous (from their IDE) with Dev Mode running too. Provide facilities (like Liberty-specific annotations) to developers to simplify what they need to do to setup their tests. | design | liberty dev mode what commercial liberty edition does this feature belong in pick one open liberty should this feature be included in the bluemix buildpack no what salesforce skill mission team and legacy retain queue will be responsible for supporting this feature none this feature will be part of the maven plugins provide a dev mode for liberty that enables developers to focus on coding without needing to repeatedly compile package and then deploy their applications to test iow fast and efficient inner loop development this includes doing hot deploy with background compilation of changed classes hot reload of changed resource properties files and reload on first request e g browser refresh should changes are detected in the workspace project developers can use boost to launch liberty into dev mode edit their maven or gradle built applications with their favourite editor any ide changes will be automatically compiled and re loaded where they can test right away should enable developers to run and run junit tests simultaneous from their ide with dev mode running too provide facilities like liberty specific annotations to developers to simplify what they need to do to setup their tests | 1 |
67,965 | 21,337,940,947 | IssuesEvent | 2022-04-18 16:44:48 | jccastillo0007/eFacturaT | https://api.github.com/repos/jccastillo0007/eFacturaT | closed | Conector CFDI 4.0 - Nomina, invocar a la plantilla correspondiente | resolved defect | Ahora mismo, cuando timbra la nómina jala la plantilla cfdi_base33.jrxml.
En web el nombre quedó como cfdi_nomina40.jrxml
Yo creo que lo manejamos igual en el conector, no?
| 1.0 | Conector CFDI 4.0 - Nomina, invocar a la plantilla correspondiente - Ahora mismo, cuando timbra la nómina jala la plantilla cfdi_base33.jrxml.
En web el nombre quedó como cfdi_nomina40.jrxml
Yo creo que lo manejamos igual en el conector, no?
| non_design | conector cfdi nomina invocar a la plantilla correspondiente ahora mismo cuando timbra la nómina jala la plantilla cfdi jrxml en web el nombre quedó como cfdi jrxml yo creo que lo manejamos igual en el conector no | 0 |
99,873 | 12,483,911,491 | IssuesEvent | 2020-05-30 12:02:47 | oppia/oppia-android | https://api.github.com/repos/oppia/oppia-android | opened | OngoingTopicList - Tablet (Portrait) (Highfi) | Priority: Essential Status: In design Type: Task Where: Topics/Stories Workstream: Highfi UI | Mocks: (not ready yet)
Implement high-fi UI for **OngoingTopicList** tablet portrait mode
**Target PR date**: 9 August 2020
**Target completion date**: 13 August 2020 | 1.0 | OngoingTopicList - Tablet (Portrait) (Highfi) - Mocks: (not ready yet)
Implement high-fi UI for **OngoingTopicList** tablet portrait mode
**Target PR date**: 9 August 2020
**Target completion date**: 13 August 2020 | design | ongoingtopiclist tablet portrait highfi mocks not ready yet implement high fi ui for ongoingtopiclist tablet portrait mode target pr date august target completion date august | 1 |
51,411 | 6,521,726,060 | IssuesEvent | 2017-08-28 21:48:10 | backdrop/backdrop-issues | https://api.github.com/repos/backdrop/backdrop-issues | closed | Update styling of progress bar: green burst to blue barber pole | audience - design status - fixed status - has pull request type - feature request | ## Describe your issue or idea
The progress bar in Backdrop has been a small point of contention since the restyling of the Seven theme in #736. See the progress-bar specific issue at #758.
The current design frequently looks downright terrible on projectors, with not enough contrast to see the animation, and the green/yellow color tints towards light yellow. Going with a high-contrast color and animation will display better in more situations, plus prevent clashing color schemes.
I'd like to propose we go with a less stylized implementation, and go with a blue barber-pole design that matches the blue from our color scheme:
---
PR by @quicksketch: https://github.com/backdrop/backdrop/pull/1968 | 1.0 | Update styling of progress bar: green burst to blue barber pole - ## Describe your issue or idea
The progress bar in Backdrop has been a small point of contention since the restyling of the Seven theme in #736. See the progress-bar specific issue at #758.
The current design frequently looks downright terrible on projectors, with not enough contrast to see the animation, and the green/yellow color tints towards light yellow. Going with a high-contrast color and animation will display better in more situations, plus prevent clashing color schemes.
I'd like to propose we go with a less stylized implementation, and go with a blue barber-pole design that matches the blue from our color scheme:
---
PR by @quicksketch: https://github.com/backdrop/backdrop/pull/1968 | design | update styling of progress bar green burst to blue barber pole describe your issue or idea the progress bar in backdrop has been a small point of contention since the restyling of the seven theme in see the progress bar specific issue at the current design frequently looks downright terrible on projectors with not enough contrast to see the animation and the green yellow color tints towards light yellow going with a high contrast color and animation will display better in more situations plus prevent clashing color schemes i d like to propose we go with a less stylized implementation and go with a blue barber pole design that matches the blue from our color scheme pr by quicksketch | 1 |
16,476 | 3,350,567,567 | IssuesEvent | 2015-11-17 15:13:55 | MarchyKarlo/YGWTP74W5JPFM2WUCP2D45UH | https://api.github.com/repos/MarchyKarlo/YGWTP74W5JPFM2WUCP2D45UH | closed | HJZgsWScSUtZO2q2VLLZ/P18+MRS4ZsREtaD6MX7GnXscaXfdc3mRFzttDUr/NROdQAZR5fgbwzbWyfcd7pDzIY0H1d5X0WvOcM5PigGMPUGjPNuvPt0jyqDnnPNSVRMiG2DfPAzgqhNu0hhHgRBudnMC1Rp+Fija7A+cOChlTc= | design | abljhNb3ry+j3o0jpYGmdHsknn3Iel4JALEbt83OpDs0jwZBHv5erAZzhmjjskr7KqZGZN6V5or9FVpA9Hm7bzeqGwzK+VSpZKDQ1TksLjbJWh2A8tShllMOrB8sMgpH/QVoQecZQ/GjvAWNWsPYTpyaRGKFx4ff7sXYeC8aEUcOENUHFaHQBA97M3Dvp7ytZbFln950P1mcEfYfkhjmmns3XfW69EN3H4kaVPW36RE09IagxULcY8ZkmPF0HqUvP8ctBBaykLuTscARNZMQFMkBd5gP4I60e1S/WGBrl0mP9N62BaALfB7Z0tnH1qsEe1D2v8c2gBhtAnWA3DIdBdi7ylKQtvEm1buopXuwugd1kS/E2kKcWtAOzvadxURT54SGL0ZzCk34xUhTh9uo8fvg/2MLx/T/wagNzl9KRLeUe3MeWW//wX1Ze7Tp8ZhZdplhSNvbmj+z576DwX3bSF9Y+q3JdZSJLqXH06RxwSUZPOAOeGB4z976FBHTAMo2kXEJ1+84av7Aq15a1XyrpIlnfS+JbfweiqWHxOlmIDxpK39Vi0RGQZ4qAXjFaGmNGPvaULzvsLM+tzu69YgmYY1m5BpuJFHJYv7tp26ojx+5lHT18+QGyNwMmZtQ/KfFwW2oJZ8kqWQENuj90s4jJGvGYyDNpKiHcMV+Ijs3ACne1N9+DBQLzldLESa3i7hv6ooaiCrJ7krxqzE/07mCJw3JA39F4eQ0TJzkifaBs02/ImhWeWDtKdu9sKqP2ERgpNDmtEmj0ST5RuXXB6W/6OGZkWQBJszZGb/n1Bx14vHSLrC4HZ+M9aR+RUssr5TnvQjsl+JtUblWuAB69pDzetv08CQdxTJ0inAVaebCRMBBBW6fJ/hEcAwnDbRG6Okds/cUq3KMJRdbcpmgieuNBDXu2usTypV44hGg79RBb03n6+o2NoknyPD0vhK2hAilLBafeC854mYR3u1KgtmOxmM+FE9DrIQV2jlNKW0l7oeCCGEj1seUTFJ0qC7G91Y06h268B9UMBcCJ/pvD0GCbBW4xqx50Gl3dnKOmlNXAqJe1pPnE7Y5NM0psWy9Ho787FQbYrzEUOaIQlzRt4Ve0U6WDNUQ5RZBNYgZ+1AuGnN9C6brRJ++bn7PZsK6oq/fZaQK8/PcJCtwiFVVQlM8ClyYmzNYlSrlyHuuMuDKs5oWFOdRvudE2pnSEh0C4wAe | 1.0 | HJZgsWScSUtZO2q2VLLZ/P18+MRS4ZsREtaD6MX7GnXscaXfdc3mRFzttDUr/NROdQAZR5fgbwzbWyfcd7pDzIY0H1d5X0WvOcM5PigGMPUGjPNuvPt0jyqDnnPNSVRMiG2DfPAzgqhNu0hhHgRBudnMC1Rp+Fija7A+cOChlTc= - abljhNb3ry+j3o0jpYGmdHsknn3Iel4JALEbt83OpDs0jwZBHv5erAZzhmjjskr7KqZGZN6V5or9FVpA9Hm7bzeqGwzK+VSpZKDQ1TksLjbJWh2A8tShllMOrB8sMgpH/QVoQecZQ/GjvAWNWsPYTpyaRGKFx4ff7sXYeC8aEUcOENUHFaHQBA97M3Dvp7ytZbFln950P1mcEfYfkhjmmns3XfW69EN3H4kaVPW36RE09IagxULcY8ZkmPF0HqUvP8ctBBaykLuTscARNZMQFMkBd5gP4I60e1S/WGBrl0mP9N62BaALfB7Z0tnH1qsEe1D2v8c2gBhtAnWA3DIdBdi7ylKQtvEm1buopXuwugd1kS/E2kKcWtAOzvadxURT54SGL0ZzCk34xUhTh9uo8fvg/2MLx/T/wagNzl9KRLeUe3MeWW//wX1Ze7Tp8ZhZdplhSNvbmj+z576DwX3bSF9Y+q3JdZSJLqXH06RxwSUZPOAOeGB4z976FBHTAMo2kXEJ1+84av7Aq15a1XyrpIlnfS+JbfweiqWHxOlmIDxpK39Vi0RGQZ4qAXjFaGmNGPvaULzvsLM+tzu69YgmYY1m5BpuJFHJYv7tp26ojx+5lHT18+QGyNwMmZtQ/KfFwW2oJZ8kqWQENuj90s4jJGvGYyDNpKiHcMV+Ijs3ACne1N9+DBQLzldLESa3i7hv6ooaiCrJ7krxqzE/07mCJw3JA39F4eQ0TJzkifaBs02/ImhWeWDtKdu9sKqP2ERgpNDmtEmj0ST5RuXXB6W/6OGZkWQBJszZGb/n1Bx14vHSLrC4HZ+M9aR+RUssr5TnvQjsl+JtUblWuAB69pDzetv08CQdxTJ0inAVaebCRMBBBW6fJ/hEcAwnDbRG6Okds/cUq3KMJRdbcpmgieuNBDXu2usTypV44hGg79RBb03n6+o2NoknyPD0vhK2hAilLBafeC854mYR3u1KgtmOxmM+FE9DrIQV2jlNKW0l7oeCCGEj1seUTFJ0qC7G91Y06h268B9UMBcCJ/pvD0GCbBW4xqx50Gl3dnKOmlNXAqJe1pPnE7Y5NM0psWy9Ho787FQbYrzEUOaIQlzRt4Ve0U6WDNUQ5RZBNYgZ+1AuGnN9C6brRJ++bn7PZsK6oq/fZaQK8/PcJCtwiFVVQlM8ClyYmzNYlSrlyHuuMuDKs5oWFOdRvudE2pnSEh0C4wAe | design | cochltc qvoqeczq t qgynwmmztq | 1 |
61,548 | 7,476,292,395 | IssuesEvent | 2018-04-04 02:14:13 | rayzhu12/SNACK-OVERFLOW | https://api.github.com/repos/rayzhu12/SNACK-OVERFLOW | closed | Create User Manager Class | design help wanted | fix logic and software arch for the user model and user manager class | 1.0 | Create User Manager Class - fix logic and software arch for the user model and user manager class | design | create user manager class fix logic and software arch for the user model and user manager class | 1 |
145,011 | 22,593,165,973 | IssuesEvent | 2022-06-28 22:07:41 | regen-network/regen-web | https://api.github.com/repos/regen-network/regen-web | closed | Create a UI version of the Pro Forma so sellers can calculate project costs and earnings | design | Translating this spreadsheet into an easy to use interface: https://docs.google.com/spreadsheets/d/1g5OmHpd7jPl-J7l7PZm4olEFoCK35LjqxtMhYYAGNo8/edit#gid=1107710388
Can use sliders, knobs, for price in dollars, project area in hectares, and sequestration rate tons of carbon / hectare / year
Add to onboarding at some stage
Stand alone component that can be used on the CarbonPlus Grasslands page, works for any credit type. User can select the credit and then do the calculations. We will to be able to plug it into a specific page for each credit page, and potentially in onboarding.
| 1.0 | Create a UI version of the Pro Forma so sellers can calculate project costs and earnings - Translating this spreadsheet into an easy to use interface: https://docs.google.com/spreadsheets/d/1g5OmHpd7jPl-J7l7PZm4olEFoCK35LjqxtMhYYAGNo8/edit#gid=1107710388
Can use sliders, knobs, for price in dollars, project area in hectares, and sequestration rate tons of carbon / hectare / year
Add to onboarding at some stage
Stand alone component that can be used on the CarbonPlus Grasslands page, works for any credit type. User can select the credit and then do the calculations. We will to be able to plug it into a specific page for each credit page, and potentially in onboarding.
| design | create a ui version of the pro forma so sellers can calculate project costs and earnings translating this spreadsheet into an easy to use interface can use sliders knobs for price in dollars project area in hectares and sequestration rate tons of carbon hectare year add to onboarding at some stage stand alone component that can be used on the carbonplus grasslands page works for any credit type user can select the credit and then do the calculations we will to be able to plug it into a specific page for each credit page and potentially in onboarding | 1 |
154,705 | 24,329,920,711 | IssuesEvent | 2022-09-30 18:22:06 | Opentrons/opentrons | https://api.github.com/repos/Opentrons/opentrons | closed | Update transfer volume tooltip copy to be inclusive of 1 to many transfers | protocol designer design | ## Background
Our current tooltip copy only works if a user is building a 1-to-many or an n:n transfer.
## Acceptance criteria
Update copy to read "Volume to dispense in each well in a 1-to-many or n-to-n transfer. Volume to aspirate from each well in a many-to-1 transfer." | 2.0 | Update transfer volume tooltip copy to be inclusive of 1 to many transfers - ## Background
Our current tooltip copy only works if a user is building a 1-to-many or an n:n transfer.
## Acceptance criteria
Update copy to read "Volume to dispense in each well in a 1-to-many or n-to-n transfer. Volume to aspirate from each well in a many-to-1 transfer." | design | update transfer volume tooltip copy to be inclusive of to many transfers background our current tooltip copy only works if a user is building a to many or an n n transfer acceptance criteria update copy to read volume to dispense in each well in a to many or n to n transfer volume to aspirate from each well in a many to transfer | 1 |
14,693 | 9,377,718,033 | IssuesEvent | 2019-04-04 11:02:26 | vtalbot/nova-mailgun-metrics | https://api.github.com/repos/vtalbot/nova-mailgun-metrics | closed | CVE-2019-6286 Medium Severity Vulnerability detected by WhiteSource | security vulnerability | ## CVE-2019-6286 - Medium Severity Vulnerability
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-sassv4.11.0</b></p></summary>
<p>
<p>:rainbow: Node.js bindings to libsass</p>
<p>Library home page: <a href=https://github.com/sass/node-sass.git>https://github.com/sass/node-sass.git</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Library Source Files (125)</summary>
<p></p>
<p> * The source files were matched to this source library based on a best effort match. Source libraries are selected from a list of probable public libraries.</p>
<p>
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/expand.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/color_maps.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass_util.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/utf8/unchecked.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/output.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass_values.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/util.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/emitter.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/lexer.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/test/test_node.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/plugins.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/include/sass/base.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/position.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/subset_map.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/operation.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/remove_placeholders.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/error_handling.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/custom_importer_bridge.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/contrib/plugin.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/functions.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/test/test_superselector.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/eval.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/utf8_string.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_context_wrapper.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/error_handling.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/node.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/parser.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/subset_map.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/emitter.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/listize.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/ast.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass_functions.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/memory/SharedPtr.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/output.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/check_nesting.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/ast_def_macros.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/functions.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/cssize.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/prelexer.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/paths.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/ast_fwd_decl.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/color.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/test/test_unification.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/inspect.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/values.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass_util.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/source_map.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/list.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/check_nesting.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/json.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/units.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/units.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/context.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/utf8/checked.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/listize.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/string.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/prelexer.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/context.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/boolean.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/include/sass2scss.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/eval.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/expand.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/factory.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/operators.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/boolean.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/source_map.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/value.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/utf8_string.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/callback_bridge.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/file.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/node.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/environment.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/extend.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass_context.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/operators.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/constants.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/ast_fwd_decl.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/parser.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/constants.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/list.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/cssize.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/include/sass/functions.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/util.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/custom_function_bridge.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/custom_importer_bridge.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/bind.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/inspect.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass_functions.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/backtrace.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/extend.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/sass_value_wrapper.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/debugger.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/cencode.c
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/base64vlq.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/number.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/color.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/c99func.c
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/position.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/remove_placeholders.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass_values.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/include/sass/values.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/test/test_subset_map.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass2scss.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/null.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/ast.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/include/sass/context.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/to_c.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/to_value.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/color_maps.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_context_wrapper.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/script/test-leaks.pl
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/lexer.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/memory/SharedPtr.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/to_c.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/to_value.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/b64/encode.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/file.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/map.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/environment.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/plugins.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/binding.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass_context.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/debug.hpp
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibSass 3.5.5, a heap-based buffer over-read exists in Sass::Prelexer::skip_over_scopes in prelexer.hpp when called from Sass::Parser::parse_import(), a similar issue to CVE-2018-11693.
<p>Publish Date: 2019-01-14
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6286>CVE-2019-6286</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/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: 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>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2019-6286 Medium Severity Vulnerability detected by WhiteSource - ## CVE-2019-6286 - Medium Severity Vulnerability
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-sassv4.11.0</b></p></summary>
<p>
<p>:rainbow: Node.js bindings to libsass</p>
<p>Library home page: <a href=https://github.com/sass/node-sass.git>https://github.com/sass/node-sass.git</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Library Source Files (125)</summary>
<p></p>
<p> * The source files were matched to this source library based on a best effort match. Source libraries are selected from a list of probable public libraries.</p>
<p>
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/expand.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/color_maps.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass_util.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/utf8/unchecked.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/output.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass_values.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/util.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/emitter.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/lexer.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/test/test_node.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/plugins.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/include/sass/base.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/position.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/subset_map.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/operation.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/remove_placeholders.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/error_handling.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/custom_importer_bridge.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/contrib/plugin.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/functions.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/test/test_superselector.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/eval.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/utf8_string.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_context_wrapper.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/error_handling.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/node.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/parser.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/subset_map.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/emitter.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/listize.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/ast.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass_functions.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/memory/SharedPtr.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/output.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/check_nesting.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/ast_def_macros.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/functions.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/cssize.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/prelexer.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/paths.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/ast_fwd_decl.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/color.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/test/test_unification.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/inspect.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/values.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass_util.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/source_map.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/list.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/check_nesting.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/json.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/units.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/units.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/context.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/utf8/checked.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/listize.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/string.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/prelexer.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/context.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/boolean.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/include/sass2scss.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/eval.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/expand.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/factory.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/operators.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/boolean.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/source_map.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/value.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/utf8_string.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/callback_bridge.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/file.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/node.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/environment.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/extend.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass_context.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/operators.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/constants.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/ast_fwd_decl.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/parser.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/constants.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/list.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/cssize.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/include/sass/functions.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/util.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/custom_function_bridge.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/custom_importer_bridge.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/bind.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/inspect.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass_functions.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/backtrace.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/extend.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/sass_value_wrapper.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/debugger.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/cencode.c
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/base64vlq.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/number.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/color.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/c99func.c
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/position.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/remove_placeholders.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass_values.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/include/sass/values.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/test/test_subset_map.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass2scss.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/null.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/ast.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/include/sass/context.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/to_c.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/to_value.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/color_maps.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_context_wrapper.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/script/test-leaks.pl
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/lexer.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/memory/SharedPtr.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/to_c.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/to_value.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/b64/encode.h
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/file.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/sass_types/map.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/environment.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/plugins.hpp
- /nova-mailgun-metrics/node_modules/node-sass/src/binding.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/sass_context.cpp
- /nova-mailgun-metrics/node_modules/node-sass/src/libsass/src/debug.hpp
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibSass 3.5.5, a heap-based buffer over-read exists in Sass::Prelexer::skip_over_scopes in prelexer.hpp when called from Sass::Parser::parse_import(), a similar issue to CVE-2018-11693.
<p>Publish Date: 2019-01-14
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6286>CVE-2019-6286</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/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: 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>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve medium severity vulnerability detected by whitesource cve medium severity vulnerability vulnerable library node rainbow node js bindings to libsass library home page a href library source files the source files were matched to this source library based on a best effort match source libraries are selected from a list of probable public libraries nova mailgun metrics node modules node sass src libsass src expand hpp nova mailgun metrics node modules node sass src libsass src color maps cpp nova mailgun metrics node modules node sass src libsass src sass util hpp nova mailgun metrics node modules node sass src libsass src unchecked h nova mailgun metrics node modules node sass src libsass src output hpp nova mailgun metrics node modules node sass src libsass src sass values hpp nova mailgun metrics node modules node sass src libsass src util hpp nova mailgun metrics node modules node sass src libsass src emitter hpp nova mailgun metrics node modules node sass src libsass src lexer cpp nova mailgun metrics node modules node sass src libsass test test node cpp nova mailgun metrics node modules node sass src libsass src plugins cpp nova mailgun metrics node modules node sass src libsass include sass base h nova mailgun metrics node modules node sass src libsass src position hpp nova mailgun metrics node modules node sass src libsass src subset map hpp nova mailgun metrics node modules node sass src libsass src operation hpp nova mailgun metrics node modules node sass src libsass src remove placeholders cpp nova mailgun metrics node modules node sass src libsass src error handling hpp nova mailgun metrics node modules node sass src custom importer bridge cpp nova mailgun metrics node modules node sass src libsass contrib plugin cpp nova mailgun metrics node modules node sass src libsass src functions hpp nova mailgun metrics node modules node sass src libsass test test superselector cpp nova mailgun metrics node modules node sass src libsass src eval hpp nova mailgun metrics node modules node sass src libsass src string hpp nova mailgun metrics node modules node sass src sass context wrapper h nova mailgun metrics node modules node sass src libsass src error handling cpp nova mailgun metrics node modules node sass src libsass src node cpp nova mailgun metrics node modules node sass src libsass src parser cpp nova mailgun metrics node modules node sass src libsass src subset map cpp nova mailgun metrics node modules node sass src libsass src emitter cpp nova mailgun metrics node modules node sass src libsass src listize cpp nova mailgun metrics node modules node sass src libsass src ast hpp nova mailgun metrics node modules node sass src libsass src sass functions hpp nova mailgun metrics node modules node sass src libsass src memory sharedptr cpp nova mailgun metrics node modules node sass src libsass src output cpp nova mailgun metrics node modules node sass src libsass src check nesting cpp nova mailgun metrics node modules node sass src libsass src ast def macros hpp nova mailgun metrics node modules node sass src libsass src functions cpp nova mailgun metrics node modules node sass src libsass src cssize hpp nova mailgun metrics node modules node sass src libsass src prelexer cpp nova mailgun metrics node modules node sass src libsass src paths hpp nova mailgun metrics node modules node sass src libsass src ast fwd decl hpp nova mailgun metrics node modules node sass src sass types color cpp nova mailgun metrics node modules node sass src libsass test test unification cpp nova mailgun metrics node modules node sass src libsass src inspect hpp nova mailgun metrics node modules node sass src libsass src values cpp nova mailgun metrics node modules node sass src libsass src sass util cpp nova mailgun metrics node modules node sass src libsass src source map hpp nova mailgun metrics node modules node sass src sass types list h nova mailgun metrics node modules node sass src libsass src check nesting hpp nova mailgun metrics node modules node sass src libsass src json cpp nova mailgun metrics node modules node sass src libsass src units cpp nova mailgun metrics node modules node sass src libsass src units hpp nova mailgun metrics node modules node sass src libsass src context cpp nova mailgun metrics node modules node sass src libsass src checked h nova mailgun metrics node modules node sass src libsass src listize hpp nova mailgun metrics node modules node sass src sass types string cpp nova mailgun metrics node modules node sass src libsass src prelexer hpp nova mailgun metrics node modules node sass src libsass src context hpp nova mailgun metrics node modules node sass src sass types boolean h nova mailgun metrics node modules node sass src libsass include h nova mailgun metrics node modules node sass src libsass src eval cpp nova mailgun metrics node modules node sass src libsass src expand cpp nova mailgun metrics node modules node sass src sass types factory cpp nova mailgun metrics node modules node sass src libsass src operators cpp nova mailgun metrics node modules node sass src sass types boolean cpp nova mailgun metrics node modules node sass src libsass src source map cpp nova mailgun metrics node modules node sass src sass types value h nova mailgun metrics node modules node sass src libsass src string cpp nova mailgun metrics node modules node sass src callback bridge h nova mailgun metrics node modules node sass src libsass src file cpp nova mailgun metrics node modules node sass src libsass src sass cpp nova mailgun metrics node modules node sass src libsass src node hpp nova mailgun metrics node modules node sass src libsass src environment cpp nova mailgun metrics node modules node sass src libsass src extend hpp nova mailgun metrics node modules node sass src libsass src sass context hpp nova mailgun metrics node modules node sass src libsass src operators hpp nova mailgun metrics node modules node sass src libsass src constants hpp nova mailgun metrics node modules node sass src libsass src sass hpp nova mailgun metrics node modules node sass src libsass src ast fwd decl cpp nova mailgun metrics node modules node sass src libsass src parser hpp nova mailgun metrics node modules node sass src libsass src constants cpp nova mailgun metrics node modules node sass src sass types list cpp nova mailgun metrics node modules node sass src libsass src cssize cpp nova mailgun metrics node modules node sass src libsass include sass functions h nova mailgun metrics node modules node sass src libsass src util cpp nova mailgun metrics node modules node sass src custom function bridge cpp nova mailgun metrics node modules node sass src custom importer bridge h nova mailgun metrics node modules node sass src libsass src bind cpp nova mailgun metrics node modules node sass src libsass src inspect cpp nova mailgun metrics node modules node sass src libsass src sass functions cpp nova mailgun metrics node modules node sass src libsass src backtrace cpp nova mailgun metrics node modules node sass src libsass src extend cpp nova mailgun metrics node modules node sass src sass types sass value wrapper h nova mailgun metrics node modules node sass src libsass src debugger hpp nova mailgun metrics node modules node sass src libsass src cencode c nova mailgun metrics node modules node sass src libsass src cpp nova mailgun metrics node modules node sass src sass types number cpp nova mailgun metrics node modules node sass src sass types color h nova mailgun metrics node modules node sass src libsass src c nova mailgun metrics node modules node sass src libsass src position cpp nova mailgun metrics node modules node sass src libsass src remove placeholders hpp nova mailgun metrics node modules node sass src libsass src sass values cpp nova mailgun metrics node modules node sass src libsass include sass values h nova mailgun metrics node modules node sass src libsass test test subset map cpp nova mailgun metrics node modules node sass src libsass src cpp nova mailgun metrics node modules node sass src sass types null cpp nova mailgun metrics node modules node sass src libsass src ast cpp nova mailgun metrics node modules node sass src libsass include sass context h nova mailgun metrics node modules node sass src libsass src to c cpp nova mailgun metrics node modules node sass src libsass src to value hpp nova mailgun metrics node modules node sass src libsass src color maps hpp nova mailgun metrics node modules node sass src sass context wrapper cpp nova mailgun metrics node modules node sass src libsass script test leaks pl nova mailgun metrics node modules node sass src libsass src lexer hpp nova mailgun metrics node modules node sass src libsass src memory sharedptr hpp nova mailgun metrics node modules node sass src libsass src to c hpp nova mailgun metrics node modules node sass src libsass src to value cpp nova mailgun metrics node modules node sass src libsass src encode h nova mailgun metrics node modules node sass src libsass src file hpp nova mailgun metrics node modules node sass src sass types map cpp nova mailgun metrics node modules node sass src libsass src environment hpp nova mailgun metrics node modules node sass src libsass src plugins hpp nova mailgun metrics node modules node sass src binding cpp nova mailgun metrics node modules node sass src libsass src sass context cpp nova mailgun metrics node modules node sass src libsass src debug hpp vulnerability details in libsass a heap based buffer over read exists in sass prelexer skip over scopes in prelexer hpp when called from sass parser parse import a similar issue to cve publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href step up your open source security game with whitesource | 0 |
107,481 | 13,463,371,867 | IssuesEvent | 2020-09-09 17:28:57 | practice-uffs/programa | https://api.github.com/repos/practice-uffs/programa | closed | Edição de videoaula para Prof. Morgana - Letras Chapecó | equipe:con-design equipe:con-media | Edição de videoaula de espanhol para a profa. Morgana - Letras Chapecó
Email: Coordenacao do Curso de Letras - Chapeco <[email protected]>
Material será disponibilizado no Drive da ISSUE na segunda-feira 07/09
Prazo de entrega: 08/09/2020 | 1.0 | Edição de videoaula para Prof. Morgana - Letras Chapecó - Edição de videoaula de espanhol para a profa. Morgana - Letras Chapecó
Email: Coordenacao do Curso de Letras - Chapeco <[email protected]>
Material será disponibilizado no Drive da ISSUE na segunda-feira 07/09
Prazo de entrega: 08/09/2020 | design | edição de videoaula para prof morgana letras chapecó edição de videoaula de espanhol para a profa morgana letras chapecó email coordenacao do curso de letras chapeco material será disponibilizado no drive da issue na segunda feira prazo de entrega | 1 |
164,202 | 25,936,384,084 | IssuesEvent | 2022-12-16 14:31:10 | OpenFlowLabs/website | https://api.github.com/repos/OpenFlowLabs/website | closed | Main text clashing with the steel bars in the background (PT: Texto principal colidindo com as barras de aço no fundo) | bug v1 responsive design | ### English:
Since text and steel are both dark, portions of the text become unreadable.
### Português (maquina de tradução):
Como o texto e o aço são escuros, partes do texto se tornam ilegíveis. | 1.0 | Main text clashing with the steel bars in the background (PT: Texto principal colidindo com as barras de aço no fundo) - ### English:
Since text and steel are both dark, portions of the text become unreadable.
### Português (maquina de tradução):
Como o texto e o aço são escuros, partes do texto se tornam ilegíveis. | design | main text clashing with the steel bars in the background pt texto principal colidindo com as barras de aço no fundo english since text and steel are both dark portions of the text become unreadable português maquina de tradução como o texto e o aço são escuros partes do texto se tornam ilegíveis | 1 |
531,589 | 15,500,719,386 | IssuesEvent | 2021-03-11 09:39:48 | AY2021S2-CS2113-W10-2/tp | https://api.github.com/repos/AY2021S2-CS2113-W10-2/tp | closed | List all emails by type | priority.High type.Story | As a user, I want to list all emails by type so that I can track my emails easily | 1.0 | List all emails by type - As a user, I want to list all emails by type so that I can track my emails easily | non_design | list all emails by type as a user i want to list all emails by type so that i can track my emails easily | 0 |
137,860 | 20,251,682,839 | IssuesEvent | 2022-02-14 18:31:43 | estuary/ui | https://api.github.com/repos/estuary/ui | reopened | Help menu links are not working and have odd UX/Styling | bug good first issue visual design ux | **UX Issues:**
1. When hovered in the AppBar the hover/active state is an oval. It should just be a circle.
- Current: 
- Expected: 
2. The links (which are buttons) are causing a doubling of the opacity for the background. This should not happen.
- 
3. When using keyboard navigation you do not see the active state on the hamburger menu, help icon or the account icon. The same visuals that show for hover should show for active.
- Current: 
- Expected: 
**Functionality Issues:**
1. When clicked on the links do not open a new window/tab and the menu just closes. It should open the links.
| 1.0 | Help menu links are not working and have odd UX/Styling - **UX Issues:**
1. When hovered in the AppBar the hover/active state is an oval. It should just be a circle.
- Current: 
- Expected: 
2. The links (which are buttons) are causing a doubling of the opacity for the background. This should not happen.
- 
3. When using keyboard navigation you do not see the active state on the hamburger menu, help icon or the account icon. The same visuals that show for hover should show for active.
- Current: 
- Expected: 
**Functionality Issues:**
1. When clicked on the links do not open a new window/tab and the menu just closes. It should open the links.
| design | help menu links are not working and have odd ux styling ux issues when hovered in the appbar the hover active state is an oval it should just be a circle current expected the links which are buttons are causing a doubling of the opacity for the background this should not happen when using keyboard navigation you do not see the active state on the hamburger menu help icon or the account icon the same visuals that show for hover should show for active current expected functionality issues when clicked on the links do not open a new window tab and the menu just closes it should open the links | 1 |
60,598 | 25,182,708,402 | IssuesEvent | 2022-11-11 15:04:02 | rtbf-ir/rtbf.ir | https://api.github.com/repos/rtbf-ir/rtbf.ir | opened | new website/service | new website/service | "name" : "ایران هاست"
"website": "https://iranhost.com/webhosting/"
"deleteurl": ""
"info": ""
بررسی شود. | 1.0 | new website/service - "name" : "ایران هاست"
"website": "https://iranhost.com/webhosting/"
"deleteurl": ""
"info": ""
بررسی شود. | non_design | new website service name ایران هاست website deleteurl info بررسی شود | 0 |
115,764 | 17,334,403,027 | IssuesEvent | 2021-07-28 08:26:32 | lukebroganws/Umbraco-CMS | https://api.github.com/repos/lukebroganws/Umbraco-CMS | opened | CVE-2018-8292 (High) detected in microsoft.codedom.providers.dotnetcompilerplatform.2.0.1.nupkg | security vulnerability | ## CVE-2018-8292 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>microsoft.codedom.providers.dotnetcompilerplatform.2.0.1.nupkg</b></p></summary>
<p>Replacement CodeDOM providers that use the new .NET Compiler Platform ("Roslyn") compiler as a servi...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.codedom.providers.dotnetcompilerplatform.2.0.1.nupkg">https://api.nuget.org/packages/microsoft.codedom.providers.dotnetcompilerplatform.2.0.1.nupkg</a></p>
<p>Path to dependency file: Umbraco-CMS/build/NuSpecs/UmbracoCms.nuspec</p>
<p>Path to vulnerable library: Umbraco-CMS/build/NuSpecs/UmbracoCms.nuspec,canner/.nuget/packages/microsoft.codedom.providers.dotnetcompilerplatform/2.0.1/microsoft.codedom.providers.dotnetcompilerplatform.2.0.1.nupkg,/home/wss-scanner/.nuget/packages/microsoft.codedom.providers.dotnetcompilerplatform/2.0.1/microsoft.codedom.providers.dotnetcompilerplatform.2.0.1.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.codedom.providers.dotnetcompilerplatform.2.0.1.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/lukebroganws/Umbraco-CMS/commit/24bd18757bbbe3324d85424fdabf1d6bdaf1695e">24bd18757bbbe3324d85424fdabf1d6bdaf1695e</a></p>
<p>Found in base branch: <b>v8/contrib</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 information disclosure vulnerability exists in .NET Core when authentication information is inadvertently exposed in a redirect, aka ".NET Core Information Disclosure Vulnerability." This affects .NET Core 2.1, .NET Core 1.0, .NET Core 1.1, PowerShell Core 6.0.
<p>Publish Date: 2018-10-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-8292>CVE-2018-8292</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://github.com/dotnet/announcements/issues/88">https://github.com/dotnet/announcements/issues/88</a></p>
<p>Release Date: 2018-10-10</p>
<p>Fix Resolution: System.Net.Http - 4.3.4;Microsoft.PowerShell.Commands.Utility - 6.1.0-rc.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Nuget","packageName":"Microsoft.CodeDom.Providers.DotNetCompilerPlatform","packageVersion":"2.0.1","packageFilePaths":["/build/NuSpecs/UmbracoCms.nuspec","/src/Umbraco.Tests.Benchmarks/Umbraco.Tests.Benchmarks.csproj"],"isTransitiveDependency":false,"dependencyTree":"Microsoft.CodeDom.Providers.DotNetCompilerPlatform:2.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"System.Net.Http - 4.3.4;Microsoft.PowerShell.Commands.Utility - 6.1.0-rc.1"}],"baseBranches":["v8/contrib"],"vulnerabilityIdentifier":"CVE-2018-8292","vulnerabilityDetails":"An information disclosure vulnerability exists in .NET Core when authentication information is inadvertently exposed in a redirect, aka \".NET Core Information Disclosure Vulnerability.\" This affects .NET Core 2.1, .NET Core 1.0, .NET Core 1.1, PowerShell Core 6.0.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-8292","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2018-8292 (High) detected in microsoft.codedom.providers.dotnetcompilerplatform.2.0.1.nupkg - ## CVE-2018-8292 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>microsoft.codedom.providers.dotnetcompilerplatform.2.0.1.nupkg</b></p></summary>
<p>Replacement CodeDOM providers that use the new .NET Compiler Platform ("Roslyn") compiler as a servi...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.codedom.providers.dotnetcompilerplatform.2.0.1.nupkg">https://api.nuget.org/packages/microsoft.codedom.providers.dotnetcompilerplatform.2.0.1.nupkg</a></p>
<p>Path to dependency file: Umbraco-CMS/build/NuSpecs/UmbracoCms.nuspec</p>
<p>Path to vulnerable library: Umbraco-CMS/build/NuSpecs/UmbracoCms.nuspec,canner/.nuget/packages/microsoft.codedom.providers.dotnetcompilerplatform/2.0.1/microsoft.codedom.providers.dotnetcompilerplatform.2.0.1.nupkg,/home/wss-scanner/.nuget/packages/microsoft.codedom.providers.dotnetcompilerplatform/2.0.1/microsoft.codedom.providers.dotnetcompilerplatform.2.0.1.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.codedom.providers.dotnetcompilerplatform.2.0.1.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/lukebroganws/Umbraco-CMS/commit/24bd18757bbbe3324d85424fdabf1d6bdaf1695e">24bd18757bbbe3324d85424fdabf1d6bdaf1695e</a></p>
<p>Found in base branch: <b>v8/contrib</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 information disclosure vulnerability exists in .NET Core when authentication information is inadvertently exposed in a redirect, aka ".NET Core Information Disclosure Vulnerability." This affects .NET Core 2.1, .NET Core 1.0, .NET Core 1.1, PowerShell Core 6.0.
<p>Publish Date: 2018-10-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-8292>CVE-2018-8292</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://github.com/dotnet/announcements/issues/88">https://github.com/dotnet/announcements/issues/88</a></p>
<p>Release Date: 2018-10-10</p>
<p>Fix Resolution: System.Net.Http - 4.3.4;Microsoft.PowerShell.Commands.Utility - 6.1.0-rc.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Nuget","packageName":"Microsoft.CodeDom.Providers.DotNetCompilerPlatform","packageVersion":"2.0.1","packageFilePaths":["/build/NuSpecs/UmbracoCms.nuspec","/src/Umbraco.Tests.Benchmarks/Umbraco.Tests.Benchmarks.csproj"],"isTransitiveDependency":false,"dependencyTree":"Microsoft.CodeDom.Providers.DotNetCompilerPlatform:2.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"System.Net.Http - 4.3.4;Microsoft.PowerShell.Commands.Utility - 6.1.0-rc.1"}],"baseBranches":["v8/contrib"],"vulnerabilityIdentifier":"CVE-2018-8292","vulnerabilityDetails":"An information disclosure vulnerability exists in .NET Core when authentication information is inadvertently exposed in a redirect, aka \".NET Core Information Disclosure Vulnerability.\" This affects .NET Core 2.1, .NET Core 1.0, .NET Core 1.1, PowerShell Core 6.0.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-8292","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_design | cve high detected in microsoft codedom providers dotnetcompilerplatform nupkg cve high severity vulnerability vulnerable library microsoft codedom providers dotnetcompilerplatform nupkg replacement codedom providers that use the new net compiler platform roslyn compiler as a servi library home page a href path to dependency file umbraco cms build nuspecs umbracocms nuspec path to vulnerable library umbraco cms build nuspecs umbracocms nuspec canner nuget packages microsoft codedom providers dotnetcompilerplatform microsoft codedom providers dotnetcompilerplatform nupkg home wss scanner nuget packages microsoft codedom providers dotnetcompilerplatform microsoft codedom providers dotnetcompilerplatform nupkg dependency hierarchy x microsoft codedom providers dotnetcompilerplatform nupkg vulnerable library found in head commit a href found in base branch contrib vulnerability details an information disclosure vulnerability exists in net core when authentication information is inadvertently exposed in a redirect aka net core information disclosure vulnerability this affects net core net core net core powershell core 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 system net http microsoft powershell commands utility rc isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree microsoft codedom providers dotnetcompilerplatform isminimumfixversionavailable true minimumfixversion system net http microsoft powershell commands utility rc basebranches vulnerabilityidentifier cve vulnerabilitydetails an information disclosure vulnerability exists in net core when authentication information is inadvertently exposed in a redirect aka net core information disclosure vulnerability this affects net core net core net core powershell core vulnerabilityurl | 0 |
141,286 | 21,475,437,958 | IssuesEvent | 2022-04-26 13:18:50 | Energinet-DataHub/greenforce-frontend | https://api.github.com/repos/Energinet-DataHub/greenforce-frontend | closed | Text colors (emphasis) and text colors based on context | Frontend Migthy Ducks Fenris Design system (Watt) | In Figma, Storybook, and `@energinet-datahub/watt`.
Emphasized text. for example global style, class, and/or mixin.
Context-based colors, for example:
- Text color on top of primary color background
- Text color on top of secondary color background
Opacity for *interactive text*?
Feature environment for this is located at:
https://eo-u-textemphasisan.westeurope.cloudapp.azure.com/origin-of-energy | 1.0 | Text colors (emphasis) and text colors based on context - In Figma, Storybook, and `@energinet-datahub/watt`.
Emphasized text. for example global style, class, and/or mixin.
Context-based colors, for example:
- Text color on top of primary color background
- Text color on top of secondary color background
Opacity for *interactive text*?
Feature environment for this is located at:
https://eo-u-textemphasisan.westeurope.cloudapp.azure.com/origin-of-energy | design | text colors emphasis and text colors based on context in figma storybook and energinet datahub watt emphasized text for example global style class and or mixin context based colors for example text color on top of primary color background text color on top of secondary color background opacity for interactive text feature environment for this is located at | 1 |
22,344 | 3,783,330,779 | IssuesEvent | 2016-03-19 02:38:40 | angular/angular.io | https://api.github.com/repos/angular/angular.io | closed | flicker on autocomplete in map of angular page | design love | when typing in the autocomplete box, the page flickers in and out. can we fix this?
see https://angular.io/docs/ts/latest/api/# | 1.0 | flicker on autocomplete in map of angular page - when typing in the autocomplete box, the page flickers in and out. can we fix this?
see https://angular.io/docs/ts/latest/api/# | design | flicker on autocomplete in map of angular page when typing in the autocomplete box the page flickers in and out can we fix this see | 1 |
56,425 | 3,079,800,155 | IssuesEvent | 2015-08-21 18:20:28 | pavel-pimenov/flylinkdc-r5xx | https://api.github.com/repos/pavel-pimenov/flylinkdc-r5xx | closed | Перетащить функционал Util::getDataFromInet в класс HttpConnection заменив имеющийся там велосипед. | imported invalid Maintainability Priority-Medium Type-Review | _From [[email protected]](https://code.google.com/u/117892482479228821242/) on December 17, 2011 15:23:34_
Util::getDataFromInet
1) написан на голом WinApi и не вливается в общую идеологию DC++.
2) скорее всего является избыточным и свободно может быть заменён на HttpConnection.
p.s: класс IDateReceiveReporter так же подлежит удалению.
_Original issue: http://code.google.com/p/flylinkdc/issues/detail?id=631_ | 1.0 | Перетащить функционал Util::getDataFromInet в класс HttpConnection заменив имеющийся там велосипед. - _From [[email protected]](https://code.google.com/u/117892482479228821242/) on December 17, 2011 15:23:34_
Util::getDataFromInet
1) написан на голом WinApi и не вливается в общую идеологию DC++.
2) скорее всего является избыточным и свободно может быть заменён на HttpConnection.
p.s: класс IDateReceiveReporter так же подлежит удалению.
_Original issue: http://code.google.com/p/flylinkdc/issues/detail?id=631_ | non_design | перетащить функционал util getdatafrominet в класс httpconnection заменив имеющийся там велосипед from on december util getdatafrominet написан на голом winapi и не вливается в общую идеологию dc скорее всего является избыточным и свободно может быть заменён на httpconnection p s класс idatereceivereporter так же подлежит удалению original issue | 0 |
39,828 | 5,142,745,587 | IssuesEvent | 2017-01-12 14:14:32 | zulip/zulip-mobile | https://api.github.com/repos/zulip/zulip-mobile | closed | Login modal remains displayed after the login is finished | design | After clicking 'Sign in' (having entered all required credentials), the login modal remains in view until it gives way to the main stream view. We should instead immediately present the stream view to the user. | 1.0 | Login modal remains displayed after the login is finished - After clicking 'Sign in' (having entered all required credentials), the login modal remains in view until it gives way to the main stream view. We should instead immediately present the stream view to the user. | design | login modal remains displayed after the login is finished after clicking sign in having entered all required credentials the login modal remains in view until it gives way to the main stream view we should instead immediately present the stream view to the user | 1 |
126,552 | 17,079,387,503 | IssuesEvent | 2021-07-08 01:17:21 | pieforproviders/pieforproviders | https://api.github.com/repos/pieforproviders/pieforproviders | closed | Incorporate the edge case of >24 hours of care into UI and formulas | Data design spike | ## ✨ What new feature do you want to see?
The attendance release currently in process does not account for situations of >24 hours of care. Currently, our UI does not incorporate this use case. Instead, if I enter a check out time that is earlier than my check in time, the system assumes that check out occurred on the following date. Otherwise, the system assumes the check in/out time are on the same date.
While I initially had the assumption that states would not allow billing >24 hours, new guidance from NE seems to indicate that providers can bill for an indefinite number of hours (p. 8): https://dhhs.ne.gov/Guidance%20Docs/Title%20392%20Guidance%20Document.pdf
While most providers will not have children for >24 hours, we should still have a clear decision about how to handle this case.
Should users simply enter hours 24.01 and after as a separate attendance entry? Will this impact their dashboard estimates and make them incorrect? How likely is it that other states will allow for billing >24 hours? Please think through an approach here and bring to the team for discussion.
## 🇺🇸 States this change applies to
- [ ] Nebraska
- [ ] Illinois
## 🧶 Acceptance Criteria
<!-- what needs to happen before this feature is able to be merged? How will we know it's done? -->
## 🖍️ Implementation Details
> **NOTE TO ENGINEERS**
>
> Please ensure that you are running Google Lighthouse and/or WebAIM (Wave) on any UI elements in your pull request to check for accessibility issues.
>
> If it is out of scope to address those accessibility issues in your pull request (because the issue is in a parent component and needs refactoring to work, for example), **you are responsible for noting those issues in your pull request and writing bug tickets to address the issues - make sure you link the new tickets in your pull request**
<!-- Any technical details that need to be taken into consideration as we implement -->
## 🥧 Additional context
<!-- Add any other context or screenshots about the feature request here. -->
| 1.0 | Incorporate the edge case of >24 hours of care into UI and formulas - ## ✨ What new feature do you want to see?
The attendance release currently in process does not account for situations of >24 hours of care. Currently, our UI does not incorporate this use case. Instead, if I enter a check out time that is earlier than my check in time, the system assumes that check out occurred on the following date. Otherwise, the system assumes the check in/out time are on the same date.
While I initially had the assumption that states would not allow billing >24 hours, new guidance from NE seems to indicate that providers can bill for an indefinite number of hours (p. 8): https://dhhs.ne.gov/Guidance%20Docs/Title%20392%20Guidance%20Document.pdf
While most providers will not have children for >24 hours, we should still have a clear decision about how to handle this case.
Should users simply enter hours 24.01 and after as a separate attendance entry? Will this impact their dashboard estimates and make them incorrect? How likely is it that other states will allow for billing >24 hours? Please think through an approach here and bring to the team for discussion.
## 🇺🇸 States this change applies to
- [ ] Nebraska
- [ ] Illinois
## 🧶 Acceptance Criteria
<!-- what needs to happen before this feature is able to be merged? How will we know it's done? -->
## 🖍️ Implementation Details
> **NOTE TO ENGINEERS**
>
> Please ensure that you are running Google Lighthouse and/or WebAIM (Wave) on any UI elements in your pull request to check for accessibility issues.
>
> If it is out of scope to address those accessibility issues in your pull request (because the issue is in a parent component and needs refactoring to work, for example), **you are responsible for noting those issues in your pull request and writing bug tickets to address the issues - make sure you link the new tickets in your pull request**
<!-- Any technical details that need to be taken into consideration as we implement -->
## 🥧 Additional context
<!-- Add any other context or screenshots about the feature request here. -->
| design | incorporate the edge case of hours of care into ui and formulas ✨ what new feature do you want to see the attendance release currently in process does not account for situations of hours of care currently our ui does not incorporate this use case instead if i enter a check out time that is earlier than my check in time the system assumes that check out occurred on the following date otherwise the system assumes the check in out time are on the same date while i initially had the assumption that states would not allow billing hours new guidance from ne seems to indicate that providers can bill for an indefinite number of hours p while most providers will not have children for hours we should still have a clear decision about how to handle this case should users simply enter hours and after as a separate attendance entry will this impact their dashboard estimates and make them incorrect how likely is it that other states will allow for billing hours please think through an approach here and bring to the team for discussion 🇺🇸 states this change applies to nebraska illinois 🧶 acceptance criteria 🖍️ implementation details note to engineers please ensure that you are running google lighthouse and or webaim wave on any ui elements in your pull request to check for accessibility issues if it is out of scope to address those accessibility issues in your pull request because the issue is in a parent component and needs refactoring to work for example you are responsible for noting those issues in your pull request and writing bug tickets to address the issues make sure you link the new tickets in your pull request 🥧 additional context | 1 |
End of preview. Expand
in Data Studio
- Downloads last month
- 18
Size of downloaded dataset files:
523 MB
Size of the auto-converted Parquet files:
523 MB
Number of rows:
276,320