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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
151,751 | 23,869,378,082 | IssuesEvent | 2022-09-07 13:44:01 | department-of-veterans-affairs/vets-design-system-documentation | https://api.github.com/repos/department-of-veterans-affairs/vets-design-system-documentation | closed | Additional info content is sometimes clipped | vsp-design-system-team va-additional-info | ## What happened
Content is sometimes clipped inside the container that expands in our `va-additional-info` component.
We've had 2 reports of this happening with different types of content.
- [Clipped images Slack support discussion](https://dsva.slack.com/archives/CBU0KDSB1/p1658428535793199)
<img width="520" alt="image" src="https://user-images.githubusercontent.com/36863582/181835074-5dd4f20e-c82b-4011-9772-302bf9ea8bcd.png">
- [Clipped content Slack support discussion](https://dsva.slack.com/archives/CBU0KDSB1/p1659121622294679)
## What I expected to happen
va-additional-info content should not be clipped
## Reproducing
- Formation version:
- Device: (e.g. iPhone 8, Macbook)
- Browser: (e.g. Firefox, IE 11)
Steps to reproduce:
1. See [Robin's comments on Slack](https://dsva.slack.com/archives/CBU0KDSB1/p1659121622294679) to test this on staging
| 1.0 | Additional info content is sometimes clipped - ## What happened
Content is sometimes clipped inside the container that expands in our `va-additional-info` component.
We've had 2 reports of this happening with different types of content.
- [Clipped images Slack support discussion](https://dsva.slack.com/archives/CBU0KDSB1/p1658428535793199)
<img width="520" alt="image" src="https://user-images.githubusercontent.com/36863582/181835074-5dd4f20e-c82b-4011-9772-302bf9ea8bcd.png">
- [Clipped content Slack support discussion](https://dsva.slack.com/archives/CBU0KDSB1/p1659121622294679)
## What I expected to happen
va-additional-info content should not be clipped
## Reproducing
- Formation version:
- Device: (e.g. iPhone 8, Macbook)
- Browser: (e.g. Firefox, IE 11)
Steps to reproduce:
1. See [Robin's comments on Slack](https://dsva.slack.com/archives/CBU0KDSB1/p1659121622294679) to test this on staging
| design | additional info content is sometimes clipped what happened content is sometimes clipped inside the container that expands in our va additional info component we ve had reports of this happening with different types of content img width alt image src what i expected to happen va additional info content should not be clipped reproducing formation version device e g iphone macbook browser e g firefox ie steps to reproduce see to test this on staging | 1 |
173,777 | 27,522,752,065 | IssuesEvent | 2023-03-06 16:01:35 | vegaprotocol/frontend-monorepo | https://api.github.com/repos/vegaprotocol/frontend-monorepo | closed | Show when a position's PnL or status has been affected by the network | Trading 🎨 design :pencil2: UX | ## Story
As a trader
I want to see when my PnL has been affected by the network
So that I understand why that has happened
## Acceptance Criteria
- [ ] I can see when a position has been affected by network conditions
- [ ] I can see when a position's status has been affected by network conditions
- [ ] I can inspect the resulting system transactions
## Tasks
- [ ] Tech discussion around feasibility given that the position query doesn't provide anything for this
- [ ] Visual Design
- [ ] Team review
## Additional details / background info
There is nothing in the positions API to make this easy so we probably need a spike to figure out the following:
- If something can be added to the API to make this simpler
- If there is a client side only solution, perhaps subscribing to orders and looking for system transactions for the given markets.
- Core PR https://github.com/vegaprotocol/vega/pull/7485
| 1.0 | Show when a position's PnL or status has been affected by the network - ## Story
As a trader
I want to see when my PnL has been affected by the network
So that I understand why that has happened
## Acceptance Criteria
- [ ] I can see when a position has been affected by network conditions
- [ ] I can see when a position's status has been affected by network conditions
- [ ] I can inspect the resulting system transactions
## Tasks
- [ ] Tech discussion around feasibility given that the position query doesn't provide anything for this
- [ ] Visual Design
- [ ] Team review
## Additional details / background info
There is nothing in the positions API to make this easy so we probably need a spike to figure out the following:
- If something can be added to the API to make this simpler
- If there is a client side only solution, perhaps subscribing to orders and looking for system transactions for the given markets.
- Core PR https://github.com/vegaprotocol/vega/pull/7485
| design | show when a position s pnl or status has been affected by the network story as a trader i want to see when my pnl has been affected by the network so that i understand why that has happened acceptance criteria i can see when a position has been affected by network conditions i can see when a position s status has been affected by network conditions i can inspect the resulting system transactions tasks tech discussion around feasibility given that the position query doesn t provide anything for this visual design team review additional details background info there is nothing in the positions api to make this easy so we probably need a spike to figure out the following if something can be added to the api to make this simpler if there is a client side only solution perhaps subscribing to orders and looking for system transactions for the given markets core pr | 1 |
100,952 | 12,603,268,986 | IssuesEvent | 2020-06-11 13:13:20 | cityofaustin/techstack | https://api.github.com/repos/cityofaustin/techstack | closed | Joplin: page picker inventory | Joplin Alpha Team: Design + Research | We need to get a handle on how certain UI elements are being used and reused, within Joplin.
#4203 List of places where picking happens
- Abstract Joplin branch: https://share.goabstract.com/c8d1f405-5433-418c-b091-3a3b65f34b4a
- Joplin microcopy [spreadsheet](https://docs.google.com/spreadsheets/d/1ZwQmQFPh-YK0tXbc5oFoTz0IM_jAOZNrA_z6XpyrdaE/edit?ouid=117580441351251740719&usp=sheets_home&ths=true) | 1.0 | Joplin: page picker inventory - We need to get a handle on how certain UI elements are being used and reused, within Joplin.
#4203 List of places where picking happens
- Abstract Joplin branch: https://share.goabstract.com/c8d1f405-5433-418c-b091-3a3b65f34b4a
- Joplin microcopy [spreadsheet](https://docs.google.com/spreadsheets/d/1ZwQmQFPh-YK0tXbc5oFoTz0IM_jAOZNrA_z6XpyrdaE/edit?ouid=117580441351251740719&usp=sheets_home&ths=true) | design | joplin page picker inventory we need to get a handle on how certain ui elements are being used and reused within joplin list of places where picking happens abstract joplin branch joplin microcopy | 1 |
227,771 | 18,099,199,471 | IssuesEvent | 2021-09-22 12:34:49 | elastic/elasticsearch | https://api.github.com/repos/elastic/elasticsearch | opened | [CI] IndexShardTests testRestoreLocalHistoryFromTranslogOnPromotion failing | >test-failure :Distributed/Engine | **Build scan:**
https://gradle-enterprise.elastic.co/s/w6y3kdqr5nilg/tests/:server:test/org.elasticsearch.index.shard.IndexShardTests/testRestoreLocalHistoryFromTranslogOnPromotion
**Reproduction line:**
`./gradlew ':server:test' --tests "org.elasticsearch.index.shard.IndexShardTests.testRestoreLocalHistoryFromTranslogOnPromotion" -Dtests.seed=4B08A52FDCDED242 -Dtests.locale=hi -Dtests.timezone=America/Detroit -Druntime.java=8`
**Applicable branches:**
7.x
**Reproduces locally?:**
Didn't try
**Failure history:**
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.index.shard.IndexShardTests&tests.test=testRestoreLocalHistoryFromTranslogOnPromotion
**Failure excerpt:**
```
java.lang.AssertionError:
Expected: <16L>
but: was <15L>
at __randomizedtesting.SeedInfo.seed([4B08A52FDCDED242:FBC2DB8E2D1FE6BB]:0)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
at org.junit.Assert.assertThat(Assert.java:956)
at org.junit.Assert.assertThat(Assert.java:923)
at org.elasticsearch.index.shard.IndexShardTests.testRestoreLocalHistoryFromTranslogOnPromotion(IndexShardTests.java:1208)
at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1750)
at com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:938)
at com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:974)
at com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:988)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:49)
at org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:45)
at org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:48)
at org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:64)
at org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:47)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:368)
at com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:817)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:468)
at com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:947)
at com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:832)
at com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:883)
at com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:894)
at org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:45)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:41)
at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:53)
at org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:47)
at org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:64)
at org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:54)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:368)
at java.lang.Thread.run(Thread.java:748)
``` | 1.0 | [CI] IndexShardTests testRestoreLocalHistoryFromTranslogOnPromotion failing - **Build scan:**
https://gradle-enterprise.elastic.co/s/w6y3kdqr5nilg/tests/:server:test/org.elasticsearch.index.shard.IndexShardTests/testRestoreLocalHistoryFromTranslogOnPromotion
**Reproduction line:**
`./gradlew ':server:test' --tests "org.elasticsearch.index.shard.IndexShardTests.testRestoreLocalHistoryFromTranslogOnPromotion" -Dtests.seed=4B08A52FDCDED242 -Dtests.locale=hi -Dtests.timezone=America/Detroit -Druntime.java=8`
**Applicable branches:**
7.x
**Reproduces locally?:**
Didn't try
**Failure history:**
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.index.shard.IndexShardTests&tests.test=testRestoreLocalHistoryFromTranslogOnPromotion
**Failure excerpt:**
```
java.lang.AssertionError:
Expected: <16L>
but: was <15L>
at __randomizedtesting.SeedInfo.seed([4B08A52FDCDED242:FBC2DB8E2D1FE6BB]:0)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
at org.junit.Assert.assertThat(Assert.java:956)
at org.junit.Assert.assertThat(Assert.java:923)
at org.elasticsearch.index.shard.IndexShardTests.testRestoreLocalHistoryFromTranslogOnPromotion(IndexShardTests.java:1208)
at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1750)
at com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:938)
at com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:974)
at com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:988)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:49)
at org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:45)
at org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:48)
at org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:64)
at org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:47)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:368)
at com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:817)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:468)
at com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:947)
at com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:832)
at com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:883)
at com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:894)
at org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:45)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:41)
at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:53)
at org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:47)
at org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:64)
at org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:54)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:368)
at java.lang.Thread.run(Thread.java:748)
``` | non_design | indexshardtests testrestorelocalhistoryfromtranslogonpromotion failing build scan reproduction line gradlew server test tests org elasticsearch index shard indexshardtests testrestorelocalhistoryfromtranslogonpromotion dtests seed dtests locale hi dtests timezone america detroit druntime java applicable branches x reproduces locally didn t try failure history failure excerpt java lang assertionerror expected but was at randomizedtesting seedinfo seed at org hamcrest matcherassert assertthat matcherassert java at org junit assert assertthat assert java at org junit assert assertthat assert java at org elasticsearch index shard indexshardtests testrestorelocalhistoryfromtranslogonpromotion indexshardtests java at sun reflect nativemethodaccessorimpl nativemethodaccessorimpl java at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at com carrotsearch randomizedtesting randomizedrunner invoke randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at org apache lucene util testrulesetupteardownchained evaluate testrulesetupteardownchained java at org apache lucene util abstractbeforeafterrule evaluate abstractbeforeafterrule java at org apache lucene util testrulethreadandtestname evaluate testrulethreadandtestname java at org apache lucene util testruleignoreaftermaxfailures evaluate testruleignoreaftermaxfailures java at org apache lucene util testrulemarkfailure evaluate testrulemarkfailure java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at com carrotsearch randomizedtesting threadleakcontrol statementrunner run threadleakcontrol java at com carrotsearch randomizedtesting threadleakcontrol forktimeoutingtask threadleakcontrol java at com carrotsearch randomizedtesting threadleakcontrol evaluate threadleakcontrol java at com carrotsearch randomizedtesting randomizedrunner runsingletest randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at org apache lucene util abstractbeforeafterrule evaluate abstractbeforeafterrule java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at org apache lucene util testrulestoreclassname evaluate testrulestoreclassname java at com carrotsearch randomizedtesting rules noshadowingoroverridesonmethodsrule evaluate noshadowingoroverridesonmethodsrule java at com carrotsearch randomizedtesting rules noshadowingoroverridesonmethodsrule evaluate noshadowingoroverridesonmethodsrule java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at org apache lucene util testruleassertionsrequired evaluate testruleassertionsrequired java at org apache lucene util testrulemarkfailure evaluate testrulemarkfailure java at org apache lucene util testruleignoreaftermaxfailures evaluate testruleignoreaftermaxfailures java at org apache lucene util testruleignoretestsuites evaluate testruleignoretestsuites java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at com carrotsearch randomizedtesting threadleakcontrol statementrunner run threadleakcontrol java at java lang thread run thread java | 0 |
42,404 | 5,440,340,453 | IssuesEvent | 2017-03-06 15:36:22 | gudell/bnymal | https://api.github.com/repos/gudell/bnymal | closed | Map - Pins | Barknyapp Design Map Page Umajin | We need to do a deep dive on what the best way display pins on the map. I will discuss with Lucas and Glenn will discuss with Dave | 1.0 | Map - Pins - We need to do a deep dive on what the best way display pins on the map. I will discuss with Lucas and Glenn will discuss with Dave | design | map pins we need to do a deep dive on what the best way display pins on the map i will discuss with lucas and glenn will discuss with dave | 1 |
163,519 | 25,830,832,898 | IssuesEvent | 2022-12-12 15:59:43 | patternfly/patternfly-org | https://api.github.com/repos/patternfly/patternfly-org | closed | Calendar month design guidelines update | PF4 design Guidelines Consistency effort | Updating calendar month's design guidelines for consistency
| 1.0 | Calendar month design guidelines update - Updating calendar month's design guidelines for consistency
| design | calendar month design guidelines update updating calendar month s design guidelines for consistency | 1 |
121,169 | 15,864,079,180 | IssuesEvent | 2021-04-08 13:28:45 | contentful/forma-36 | https://api.github.com/repos/contentful/forma-36 | opened | 💡 v4 Proposal - New icon sizes | needs design review proposal | # Forma 36 contribution proposal
We want to add new `20px` and `28px` icon size, which might make more sense to introduce together with a new token.
We currently have these sizes:
- `large: 32px`
- `medium: 24px`
- `small: 20px`
- `tiny: 16px`
## The proposed solution
We can either create a new scale for icon size naming ranging from `xs` to `large`, or we can align icon sizing with our spacing tokens and their names. The latter would probably be too weird to use since our smallest icon is `16px` which is our `m` token. So if we go with the first option of a custom size scale for icons it would be something like this:
- `xl: 32px`
- `l: 28px`
- `m: 24px`
- `s: 20px`
- `xs: 16px`
Is this the way we want to go? | 1.0 | 💡 v4 Proposal - New icon sizes - # Forma 36 contribution proposal
We want to add new `20px` and `28px` icon size, which might make more sense to introduce together with a new token.
We currently have these sizes:
- `large: 32px`
- `medium: 24px`
- `small: 20px`
- `tiny: 16px`
## The proposed solution
We can either create a new scale for icon size naming ranging from `xs` to `large`, or we can align icon sizing with our spacing tokens and their names. The latter would probably be too weird to use since our smallest icon is `16px` which is our `m` token. So if we go with the first option of a custom size scale for icons it would be something like this:
- `xl: 32px`
- `l: 28px`
- `m: 24px`
- `s: 20px`
- `xs: 16px`
Is this the way we want to go? | design | 💡 proposal new icon sizes forma contribution proposal we want to add new and icon size which might make more sense to introduce together with a new token we currently have these sizes large medium small tiny the proposed solution we can either create a new scale for icon size naming ranging from xs to large or we can align icon sizing with our spacing tokens and their names the latter would probably be too weird to use since our smallest icon is which is our m token so if we go with the first option of a custom size scale for icons it would be something like this xl l m s xs is this the way we want to go | 1 |
163,902 | 6,216,616,521 | IssuesEvent | 2017-07-08 05:54:33 | OperationCode/operationcode_frontend | https://api.github.com/repos/OperationCode/operationcode_frontend | closed | Link /team /faq and /contact to footer | Priority: High Status: In Progress Type: Bug | # Bug Report
## What is the current behavior?
/team /faq and /contact are existing endpoints, but it does not appear in the navigation of our website.
## What is the expected behavior?
There should be links in both the footer component leading a user to the listed routes. | 1.0 | Link /team /faq and /contact to footer - # Bug Report
## What is the current behavior?
/team /faq and /contact are existing endpoints, but it does not appear in the navigation of our website.
## What is the expected behavior?
There should be links in both the footer component leading a user to the listed routes. | non_design | link team faq and contact to footer bug report what is the current behavior team faq and contact are existing endpoints but it does not appear in the navigation of our website what is the expected behavior there should be links in both the footer component leading a user to the listed routes | 0 |
458,039 | 13,167,346,742 | IssuesEvent | 2020-08-11 10:06:36 | SkriptLang/Skript | https://api.github.com/repos/SkriptLang/Skript | closed | Furnace slot support for smokers, blast furnace | bug completed priority: medium | ### Description
Furnace slot expression does not support new type of furnaces (Smokers, Blast furnace)
### Steps to Reproduce
Call the expression on smokers and blast furnace
### Expected Behavior
Shows the inventory slot for ore slot, fuel slot, result slot
### Errors / Screenshots
### Server Information
* **Server version/platform:** git-Paper-132 (MC: 1.16.1)
* **Skript version:** 2.5-beta1
### Additional Context
Expression reference:
- https://skriptlang.github.io/Skript/expressions.html#ExprFurnaceSlot
- https://skripthub.net/docs/?id=963
| 1.0 | Furnace slot support for smokers, blast furnace - ### Description
Furnace slot expression does not support new type of furnaces (Smokers, Blast furnace)
### Steps to Reproduce
Call the expression on smokers and blast furnace
### Expected Behavior
Shows the inventory slot for ore slot, fuel slot, result slot
### Errors / Screenshots
### Server Information
* **Server version/platform:** git-Paper-132 (MC: 1.16.1)
* **Skript version:** 2.5-beta1
### Additional Context
Expression reference:
- https://skriptlang.github.io/Skript/expressions.html#ExprFurnaceSlot
- https://skripthub.net/docs/?id=963
| non_design | furnace slot support for smokers blast furnace description furnace slot expression does not support new type of furnaces smokers blast furnace steps to reproduce call the expression on smokers and blast furnace expected behavior shows the inventory slot for ore slot fuel slot result slot errors screenshots server information server version platform git paper mc skript version additional context expression reference | 0 |
70,524 | 9,419,863,870 | IssuesEvent | 2019-04-10 23:36:08 | uccser/cs-field-guide | https://api.github.com/repos/uccser/cs-field-guide | closed | Decide how to deal with licences for third-party libraries in interactives | documentation interactives | Typically we include this within the interactives folder, but CSU proposed storing these in a 'LICENSE-THIRD-PARTY` folder....
The decision will need to be noted in the docs. | 1.0 | Decide how to deal with licences for third-party libraries in interactives - Typically we include this within the interactives folder, but CSU proposed storing these in a 'LICENSE-THIRD-PARTY` folder....
The decision will need to be noted in the docs. | non_design | decide how to deal with licences for third party libraries in interactives typically we include this within the interactives folder but csu proposed storing these in a license third party folder the decision will need to be noted in the docs | 0 |
175,120 | 13,535,578,575 | IssuesEvent | 2020-09-16 07:48:08 | gradle/gradle | https://api.github.com/repos/gradle/gradle | closed | Unrolled Spock feature methods can not be executed via an include pattern when using the JUnit Platform | @jvm a:bug from:member in:testing | ### Expected Behavior
Give the following Spock test class, running `gradle test --tests "spock.SpockExample.flakyTest #number"` should execute the data-driven Spock method.
```groovy
package spock
import spock.lang.Specification
import spock.lang.Unroll
class SpockExample extends Specification {
@Unroll
void 'flakyTest #number'() {
expect:
if (number == 1) {
assert false
}
where:
number << [1, 2, 3]
}
}
```
<!--- Tell us what should happen -->
### Current Behavior
```
> Task :test FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':test'.
> No tests found for given includes: [spock.SpockExample.flakyTest #number](--tests filter)
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
* Get more help at https://help.gradle.org
BUILD FAILED in 5s
3 actionable tasks: 1 executed, 2 from cache
```
### Context
This works when the Test task is not using the JUnit Platform but JUnit 4 directly.
The root cause of the problem is the `@Unroll` annotation. Vintage uses JUnit 4's `Runner.getDescription()` API to report the test methods of a test class. However, Spock's Runner (called `Sputnik`), does not include `@Unroll` methods:
https://github.com/spockframework/spock/blob/spock-1.3/spock-core/src/main/java/org/spockframework/runtime/JUnitDescriptionGenerator.java#L58
Gradle's JUnit Platform support uses the String passed with `--tests` as in a `PostDiscoveryFilter` that doesn't have access to `TestDescriptors` for `@Unroll` methods, either:
https://github.com/gradle/gradle/blob/01b4d16ab8ca7669599078cf71f455b129932bbd/subprojects/testing-junit-platform/src/main/java/org/gradle/api/internal/tasks/testing/junitplatform/JUnitPlatformTestClassProcessor.java#L181-L190
Instead, Gradle should convert these patterns into instances of `ClassSelector` and `MethodSelector`. That would also work for `@Unroll` methods as soon as my recent fix in the Vintage engine is released: https://github.com/junit-team/junit5/pull/2264
However, such a change would not support wildcard patterns.
### Steps to Reproduce
1. Extract [junit-vintage-examples.zip](https://github.com/gradle/gradle/files/4715243/junit-vintage-examples.zip)
1. Run `./gradlew test --tests "spock.SpockExample.flakyTest #number"`
### Your Environment
Build scan URL: https://scans.gradle.com/s/23xbccunzj3iw
| 1.0 | Unrolled Spock feature methods can not be executed via an include pattern when using the JUnit Platform - ### Expected Behavior
Give the following Spock test class, running `gradle test --tests "spock.SpockExample.flakyTest #number"` should execute the data-driven Spock method.
```groovy
package spock
import spock.lang.Specification
import spock.lang.Unroll
class SpockExample extends Specification {
@Unroll
void 'flakyTest #number'() {
expect:
if (number == 1) {
assert false
}
where:
number << [1, 2, 3]
}
}
```
<!--- Tell us what should happen -->
### Current Behavior
```
> Task :test FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':test'.
> No tests found for given includes: [spock.SpockExample.flakyTest #number](--tests filter)
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
* Get more help at https://help.gradle.org
BUILD FAILED in 5s
3 actionable tasks: 1 executed, 2 from cache
```
### Context
This works when the Test task is not using the JUnit Platform but JUnit 4 directly.
The root cause of the problem is the `@Unroll` annotation. Vintage uses JUnit 4's `Runner.getDescription()` API to report the test methods of a test class. However, Spock's Runner (called `Sputnik`), does not include `@Unroll` methods:
https://github.com/spockframework/spock/blob/spock-1.3/spock-core/src/main/java/org/spockframework/runtime/JUnitDescriptionGenerator.java#L58
Gradle's JUnit Platform support uses the String passed with `--tests` as in a `PostDiscoveryFilter` that doesn't have access to `TestDescriptors` for `@Unroll` methods, either:
https://github.com/gradle/gradle/blob/01b4d16ab8ca7669599078cf71f455b129932bbd/subprojects/testing-junit-platform/src/main/java/org/gradle/api/internal/tasks/testing/junitplatform/JUnitPlatformTestClassProcessor.java#L181-L190
Instead, Gradle should convert these patterns into instances of `ClassSelector` and `MethodSelector`. That would also work for `@Unroll` methods as soon as my recent fix in the Vintage engine is released: https://github.com/junit-team/junit5/pull/2264
However, such a change would not support wildcard patterns.
### Steps to Reproduce
1. Extract [junit-vintage-examples.zip](https://github.com/gradle/gradle/files/4715243/junit-vintage-examples.zip)
1. Run `./gradlew test --tests "spock.SpockExample.flakyTest #number"`
### Your Environment
Build scan URL: https://scans.gradle.com/s/23xbccunzj3iw
| non_design | unrolled spock feature methods can not be executed via an include pattern when using the junit platform expected behavior give the following spock test class running gradle test tests spock spockexample flakytest number should execute the data driven spock method groovy package spock import spock lang specification import spock lang unroll class spockexample extends specification unroll void flakytest number expect if number assert false where number current behavior task test failed failure build failed with an exception what went wrong execution failed for task test no tests found for given includes tests filter try run with stacktrace option to get the stack trace run with info or debug option to get more log output run with scan to get full insights get more help at build failed in actionable tasks executed from cache context this works when the test task is not using the junit platform but junit directly the root cause of the problem is the unroll annotation vintage uses junit s runner getdescription api to report the test methods of a test class however spock s runner called sputnik does not include unroll methods gradle s junit platform support uses the string passed with tests as in a postdiscoveryfilter that doesn t have access to testdescriptors for unroll methods either instead gradle should convert these patterns into instances of classselector and methodselector that would also work for unroll methods as soon as my recent fix in the vintage engine is released however such a change would not support wildcard patterns steps to reproduce extract run gradlew test tests spock spockexample flakytest number your environment build scan url | 0 |
282,322 | 30,889,275,440 | IssuesEvent | 2023-08-04 02:29:30 | maddyCode23/linux-4.1.15 | https://api.github.com/repos/maddyCode23/linux-4.1.15 | reopened | CVE-2022-1975 (Medium) detected in linux-stable-rtv4.1.33 | Mend: dependency security vulnerability | ## CVE-2022-1975 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/maddyCode23/linux-4.1.15/commit/f1f3d2b150be669390b32dfea28e773471bdd6e7">f1f3d2b150be669390b32dfea28e773471bdd6e7</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
There is a sleep-in-atomic bug in /net/nfc/netlink.c that allows an attacker to crash the Linux kernel by simulating a nfc device from user-space.
<p>Publish Date: 2022-08-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-1975>CVE-2022-1975</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2022-1975">https://www.linuxkernelcves.com/cves/CVE-2022-1975</a></p>
<p>Release Date: 2022-08-31</p>
<p>Fix Resolution: v4.9.313,v4.14.278,v4.19.242,v5.4.193,v5.10.115,v5.15.39,v5.17.7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-1975 (Medium) detected in linux-stable-rtv4.1.33 - ## CVE-2022-1975 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/maddyCode23/linux-4.1.15/commit/f1f3d2b150be669390b32dfea28e773471bdd6e7">f1f3d2b150be669390b32dfea28e773471bdd6e7</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
There is a sleep-in-atomic bug in /net/nfc/netlink.c that allows an attacker to crash the Linux kernel by simulating a nfc device from user-space.
<p>Publish Date: 2022-08-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-1975>CVE-2022-1975</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2022-1975">https://www.linuxkernelcves.com/cves/CVE-2022-1975</a></p>
<p>Release Date: 2022-08-31</p>
<p>Fix Resolution: v4.9.313,v4.14.278,v4.19.242,v5.4.193,v5.10.115,v5.15.39,v5.17.7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve medium detected in linux stable cve medium severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href found in base branch master vulnerable source files vulnerability details there is a sleep in atomic bug in net nfc netlink c that allows an attacker to crash the linux kernel by simulating a nfc device from user space publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
85,910 | 8,007,129,940 | IssuesEvent | 2018-07-24 00:29:30 | linkerd/linkerd2 | https://api.github.com/repos/linkerd/linkerd2 | closed | TestVersionCheck/Passes_when_versions_are_latest is flaky | area/controller area/test priority/P2 | It looks like this go unit test is occasionally failing in CI:
```
=== RUN TestVersionCheck/Passes_when_versions_are_latest
panic: runtime error: index out of range [recovered]
panic: runtime error: index out of range
goroutine 27 [running]:
testing.tRunner.func1(0xc4203641e0)
/home/travis/.gimme/versions/go1.10.2.linux.amd64/src/testing/testing.go:742 +0x567
panic(0x1753c00, 0x2272af0)
/home/travis/.gimme/versions/go1.10.2.linux.amd64/src/runtime/panic.go:502 +0x24a
github.com/runconduit/conduit/pkg/version_test.TestVersionCheck.func2(0xc4203641e0)
/home/travis/gopath/src/github.com/runconduit/conduit/pkg/version/version_test.go:31 +0xca1
testing.tRunner(0xc4203641e0, 0x19378a8)
/home/travis/.gimme/versions/go1.10.2.linux.amd64/src/testing/testing.go:777 +0x16e
created by testing.(*T).Run
/home/travis/.gimme/versions/go1.10.2.linux.amd64/src/testing/testing.go:824 +0x565
FAIL github.com/runconduit/conduit/pkg/version 0.050s
``` | 1.0 | TestVersionCheck/Passes_when_versions_are_latest is flaky - It looks like this go unit test is occasionally failing in CI:
```
=== RUN TestVersionCheck/Passes_when_versions_are_latest
panic: runtime error: index out of range [recovered]
panic: runtime error: index out of range
goroutine 27 [running]:
testing.tRunner.func1(0xc4203641e0)
/home/travis/.gimme/versions/go1.10.2.linux.amd64/src/testing/testing.go:742 +0x567
panic(0x1753c00, 0x2272af0)
/home/travis/.gimme/versions/go1.10.2.linux.amd64/src/runtime/panic.go:502 +0x24a
github.com/runconduit/conduit/pkg/version_test.TestVersionCheck.func2(0xc4203641e0)
/home/travis/gopath/src/github.com/runconduit/conduit/pkg/version/version_test.go:31 +0xca1
testing.tRunner(0xc4203641e0, 0x19378a8)
/home/travis/.gimme/versions/go1.10.2.linux.amd64/src/testing/testing.go:777 +0x16e
created by testing.(*T).Run
/home/travis/.gimme/versions/go1.10.2.linux.amd64/src/testing/testing.go:824 +0x565
FAIL github.com/runconduit/conduit/pkg/version 0.050s
``` | non_design | testversioncheck passes when versions are latest is flaky it looks like this go unit test is occasionally failing in ci run testversioncheck passes when versions are latest panic runtime error index out of range panic runtime error index out of range goroutine testing trunner home travis gimme versions linux src testing testing go panic home travis gimme versions linux src runtime panic go github com runconduit conduit pkg version test testversioncheck home travis gopath src github com runconduit conduit pkg version version test go testing trunner home travis gimme versions linux src testing testing go created by testing t run home travis gimme versions linux src testing testing go fail github com runconduit conduit pkg version | 0 |
33,548 | 12,216,721,255 | IssuesEvent | 2020-05-01 15:43:06 | kpango/grpc-sample | https://api.github.com/repos/kpango/grpc-sample | opened | WS-2017-3757 (Medium) detected in content-type-parser-1.0.2.tgz | security vulnerability | ## WS-2017-3757 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>content-type-parser-1.0.2.tgz</b></p></summary>
<p>Parse the value of the Content-Type header</p>
<p>Library home page: <a href="https://registry.npmjs.org/content-type-parser/-/content-type-parser-1.0.2.tgz">https://registry.npmjs.org/content-type-parser/-/content-type-parser-1.0.2.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/grpc-sample/web/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/grpc-sample/web/node_modules/content-type-parser/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-ts-2.13.0.tgz (Root Library)
- jest-20.0.4.tgz
- jest-cli-20.0.4.tgz
- jest-environment-jsdom-20.0.3.tgz
- jsdom-9.12.0.tgz
- :x: **content-type-parser-1.0.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kpango/grpc-sample/commit/96e3a9ab40b89cf8220803cfa662c7b4710348eb">96e3a9ab40b89cf8220803cfa662c7b4710348eb</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
all versions prior to 2.0.0 of content-type-parser npm package are vulnerable to ReDoS via the user agent parser. the vulnerability was fixed by reintroducing a new parser and deleting the old one.
<p>Publish Date: 2017-12-10
<p>URL: <a href=https://github.com/jsdom/whatwg-mimetype/commit/26c539a699778f8743b8319c298b5fb28a4328d0>WS-2017-3757</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</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/jsdom/whatwg-mimetype/issues/3">https://github.com/jsdom/whatwg-mimetype/issues/3</a></p>
<p>Release Date: 2020-04-30</p>
<p>Fix Resolution: v2.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2017-3757 (Medium) detected in content-type-parser-1.0.2.tgz - ## WS-2017-3757 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>content-type-parser-1.0.2.tgz</b></p></summary>
<p>Parse the value of the Content-Type header</p>
<p>Library home page: <a href="https://registry.npmjs.org/content-type-parser/-/content-type-parser-1.0.2.tgz">https://registry.npmjs.org/content-type-parser/-/content-type-parser-1.0.2.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/grpc-sample/web/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/grpc-sample/web/node_modules/content-type-parser/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-ts-2.13.0.tgz (Root Library)
- jest-20.0.4.tgz
- jest-cli-20.0.4.tgz
- jest-environment-jsdom-20.0.3.tgz
- jsdom-9.12.0.tgz
- :x: **content-type-parser-1.0.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kpango/grpc-sample/commit/96e3a9ab40b89cf8220803cfa662c7b4710348eb">96e3a9ab40b89cf8220803cfa662c7b4710348eb</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
all versions prior to 2.0.0 of content-type-parser npm package are vulnerable to ReDoS via the user agent parser. the vulnerability was fixed by reintroducing a new parser and deleting the old one.
<p>Publish Date: 2017-12-10
<p>URL: <a href=https://github.com/jsdom/whatwg-mimetype/commit/26c539a699778f8743b8319c298b5fb28a4328d0>WS-2017-3757</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</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/jsdom/whatwg-mimetype/issues/3">https://github.com/jsdom/whatwg-mimetype/issues/3</a></p>
<p>Release Date: 2020-04-30</p>
<p>Fix Resolution: v2.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | ws medium detected in content type parser tgz ws medium severity vulnerability vulnerable library content type parser tgz parse the value of the content type header library home page a href path to dependency file tmp ws scm grpc sample web package json path to vulnerable library tmp ws scm grpc sample web node modules content type parser package json dependency hierarchy react scripts ts tgz root library jest tgz jest cli tgz jest environment jsdom tgz jsdom tgz x content type parser tgz vulnerable library found in head commit a href vulnerability details all versions prior to of content type parser npm package are vulnerable to redos via the user agent parser the vulnerability was fixed by reintroducing a new parser and deleting the old one publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
211,964 | 23,856,878,696 | IssuesEvent | 2022-09-07 01:12:40 | lokesh5654/gittest | https://api.github.com/repos/lokesh5654/gittest | opened | WS-2021-0638 (High) detected in mocha-6.2.0.tgz, mocha-5.2.0.tgz | security vulnerability | ## WS-2021-0638 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>mocha-6.2.0.tgz</b>, <b>mocha-5.2.0.tgz</b></p></summary>
<p>
<details><summary><b>mocha-6.2.0.tgz</b></p></summary>
<p>simple, flexible, fun test framework</p>
<p>Library home page: <a href="https://registry.npmjs.org/mocha/-/mocha-6.2.0.tgz">https://registry.npmjs.org/mocha/-/mocha-6.2.0.tgz</a></p>
<p>Path to dependency file: /gittest/package.json</p>
<p>Path to vulnerable library: /node_modules/@open-wc/testing-karma-bs/node_modules/mocha/package.json</p>
<p>
Dependency Hierarchy:
- testing-karma-bs-1.1.28.tgz (Root Library)
- testing-karma-3.1.3.tgz
- :x: **mocha-6.2.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>mocha-5.2.0.tgz</b></p></summary>
<p>simple, flexible, fun test framework</p>
<p>Library home page: <a href="https://registry.npmjs.org/mocha/-/mocha-5.2.0.tgz">https://registry.npmjs.org/mocha/-/mocha-5.2.0.tgz</a></p>
<p>Path to dependency file: /gittest/package.json</p>
<p>Path to vulnerable library: /node_modules/mocha/package.json</p>
<p>
Dependency Hierarchy:
- :x: **mocha-5.2.0.tgz** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
There is regular Expression Denial of Service (ReDoS) vulnerability in mocha.
It allows cause a denial of service when stripping crafted invalid function definition from strs.
<p>Publish Date: 2021-09-18
<p>URL: <a href=https://github.com/mochajs/mocha/commit/61b4b9209c2c64b32c8d48b1761c3b9384d411ea>WS-2021-0638</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://huntr.dev/bounties/1d8a3d95-d199-4129-a6ad-8eafe5e77b9e/">https://huntr.dev/bounties/1d8a3d95-d199-4129-a6ad-8eafe5e77b9e/</a></p>
<p>Release Date: 2021-09-18</p>
<p>Fix Resolution: 6.0.0-0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2021-0638 (High) detected in mocha-6.2.0.tgz, mocha-5.2.0.tgz - ## WS-2021-0638 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>mocha-6.2.0.tgz</b>, <b>mocha-5.2.0.tgz</b></p></summary>
<p>
<details><summary><b>mocha-6.2.0.tgz</b></p></summary>
<p>simple, flexible, fun test framework</p>
<p>Library home page: <a href="https://registry.npmjs.org/mocha/-/mocha-6.2.0.tgz">https://registry.npmjs.org/mocha/-/mocha-6.2.0.tgz</a></p>
<p>Path to dependency file: /gittest/package.json</p>
<p>Path to vulnerable library: /node_modules/@open-wc/testing-karma-bs/node_modules/mocha/package.json</p>
<p>
Dependency Hierarchy:
- testing-karma-bs-1.1.28.tgz (Root Library)
- testing-karma-3.1.3.tgz
- :x: **mocha-6.2.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>mocha-5.2.0.tgz</b></p></summary>
<p>simple, flexible, fun test framework</p>
<p>Library home page: <a href="https://registry.npmjs.org/mocha/-/mocha-5.2.0.tgz">https://registry.npmjs.org/mocha/-/mocha-5.2.0.tgz</a></p>
<p>Path to dependency file: /gittest/package.json</p>
<p>Path to vulnerable library: /node_modules/mocha/package.json</p>
<p>
Dependency Hierarchy:
- :x: **mocha-5.2.0.tgz** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
There is regular Expression Denial of Service (ReDoS) vulnerability in mocha.
It allows cause a denial of service when stripping crafted invalid function definition from strs.
<p>Publish Date: 2021-09-18
<p>URL: <a href=https://github.com/mochajs/mocha/commit/61b4b9209c2c64b32c8d48b1761c3b9384d411ea>WS-2021-0638</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://huntr.dev/bounties/1d8a3d95-d199-4129-a6ad-8eafe5e77b9e/">https://huntr.dev/bounties/1d8a3d95-d199-4129-a6ad-8eafe5e77b9e/</a></p>
<p>Release Date: 2021-09-18</p>
<p>Fix Resolution: 6.0.0-0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | ws high detected in mocha tgz mocha tgz ws high severity vulnerability vulnerable libraries mocha tgz mocha tgz mocha tgz simple flexible fun test framework library home page a href path to dependency file gittest package json path to vulnerable library node modules open wc testing karma bs node modules mocha package json dependency hierarchy testing karma bs tgz root library testing karma tgz x mocha tgz vulnerable library mocha tgz simple flexible fun test framework library home page a href path to dependency file gittest package json path to vulnerable library node modules mocha package json dependency hierarchy x mocha tgz vulnerable library vulnerability details there is regular expression denial of service redos vulnerability in mocha it allows cause a denial of service when stripping crafted invalid function definition from strs publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
70,863 | 8,584,732,242 | IssuesEvent | 2018-11-13 23:58:02 | HuskyGameDev/2018-team3 | https://api.github.com/repos/HuskyGameDev/2018-team3 | closed | Create test level | design sprint 1 | We need to design a test level in order to test and tweak the characters movement options as desired | 1.0 | Create test level - We need to design a test level in order to test and tweak the characters movement options as desired | design | create test level we need to design a test level in order to test and tweak the characters movement options as desired | 1 |
421,997 | 12,264,767,431 | IssuesEvent | 2020-05-07 05:25:58 | StrangeLoopGames/EcoIssues | https://api.github.com/repos/StrangeLoopGames/EcoIssues | closed | Lumber Signs need a Material for Icon | Category: Art Priority: Low Status: Fixed Week Task | Lumber signs still have the old style for icons. To convert them to the new style, we need a Lumber material for the icons. | 1.0 | Lumber Signs need a Material for Icon - Lumber signs still have the old style for icons. To convert them to the new style, we need a Lumber material for the icons. | non_design | lumber signs need a material for icon lumber signs still have the old style for icons to convert them to the new style we need a lumber material for the icons | 0 |
129,900 | 17,933,377,397 | IssuesEvent | 2021-09-10 12:26:16 | carbon-design-system/carbon-for-ibm-dotcom | https://api.github.com/repos/carbon-design-system/carbon-for-ibm-dotcom | closed | [Support bot] Continue Project kick-off with conversational scientist (second sprint) | design priority: medium adopter support content | This issue covers the work to kick-off the content creation part of the Slack bot project, reviewing the initial Slack audit from the interns and working with Bob Moore of IBM Research to begin structuring the content.
Link to Airtable with Slack audit: https://airtable.com/tblSE95CtwV9p6KdX/viwscL9lwWbZxCUu5?blocks=bip2lqJzadfUwXa5Q
#### Additional Information
- Related issues for this ongoing work
- Sprint 21-16: issue (#6637 )
| 1.0 | [Support bot] Continue Project kick-off with conversational scientist (second sprint) - This issue covers the work to kick-off the content creation part of the Slack bot project, reviewing the initial Slack audit from the interns and working with Bob Moore of IBM Research to begin structuring the content.
Link to Airtable with Slack audit: https://airtable.com/tblSE95CtwV9p6KdX/viwscL9lwWbZxCUu5?blocks=bip2lqJzadfUwXa5Q
#### Additional Information
- Related issues for this ongoing work
- Sprint 21-16: issue (#6637 )
| design | continue project kick off with conversational scientist second sprint this issue covers the work to kick off the content creation part of the slack bot project reviewing the initial slack audit from the interns and working with bob moore of ibm research to begin structuring the content link to airtable with slack audit additional information related issues for this ongoing work sprint issue | 1 |
281,938 | 21,315,450,476 | IssuesEvent | 2022-04-16 07:30:18 | tanweien/pe | https://api.github.com/repos/tanweien/pe | opened | Omission of end of lifeline in UML diagrams | type.DocumentationBug severity.Low | UML diagram should include end of lifeline (x) to show its deletion.
<!--session: 1650088444143-8f738eb3-57c2-4a25-908a-b4722dfedcd1-->
<!--Version: Web v3.4.2--> | 1.0 | Omission of end of lifeline in UML diagrams - UML diagram should include end of lifeline (x) to show its deletion.
<!--session: 1650088444143-8f738eb3-57c2-4a25-908a-b4722dfedcd1-->
<!--Version: Web v3.4.2--> | non_design | omission of end of lifeline in uml diagrams uml diagram should include end of lifeline x to show its deletion | 0 |
24,223 | 17,020,039,335 | IssuesEvent | 2021-07-02 17:24:19 | cds-snc/covid-alert-metrics-terraform | https://api.github.com/repos/cds-snc/covid-alert-metrics-terraform | closed | Enhancement: new CloudWatch metric alarms for `save-metrics` Lambda errors | enhancement infrastructure medium priority | Rather than capturing `save-metrics` Lambda invocation errors in with the API Gateway 5xx errors, we should look for specific Lambda failures and create alarms based on their occurrence.
This will allow us to narrow down our focus to problems with the Lambda code and its supporting services.
Related #122, #124 | 1.0 | Enhancement: new CloudWatch metric alarms for `save-metrics` Lambda errors - Rather than capturing `save-metrics` Lambda invocation errors in with the API Gateway 5xx errors, we should look for specific Lambda failures and create alarms based on their occurrence.
This will allow us to narrow down our focus to problems with the Lambda code and its supporting services.
Related #122, #124 | non_design | enhancement new cloudwatch metric alarms for save metrics lambda errors rather than capturing save metrics lambda invocation errors in with the api gateway errors we should look for specific lambda failures and create alarms based on their occurrence this will allow us to narrow down our focus to problems with the lambda code and its supporting services related | 0 |
64,547 | 14,666,236,206 | IssuesEvent | 2020-12-29 15:53:15 | turkdevops/vuenut | https://api.github.com/repos/turkdevops/vuenut | opened | CVE-2020-7608 (Medium) detected in yargs-parser-7.0.0.tgz, yargs-parser-4.2.1.tgz | security vulnerability | ## CVE-2020-7608 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>yargs-parser-7.0.0.tgz</b>, <b>yargs-parser-4.2.1.tgz</b></p></summary>
<p>
<details><summary><b>yargs-parser-7.0.0.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-7.0.0.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-7.0.0.tgz</a></p>
<p>Path to dependency file: vuenut/package.json</p>
<p>Path to vulnerable library: vuenut/node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- cli-service-3.0.0-beta.6.tgz (Root Library)
- webpack-3.11.0.tgz
- yargs-8.0.2.tgz
- :x: **yargs-parser-7.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-4.2.1.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-4.2.1.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-4.2.1.tgz</a></p>
<p>Path to dependency file: vuenut/package.json</p>
<p>Path to vulnerable library: vuenut/node_modules/webpack-dev-server/node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- cli-service-3.0.0-beta.6.tgz (Root Library)
- webpack-dev-server-2.11.2.tgz
- yargs-6.6.0.tgz
- :x: **yargs-parser-4.2.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/vuenut/commit/8ef0c5a1523ba08434c5a1320f09f557f566724a">8ef0c5a1523ba08434c5a1320f09f557f566724a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
yargs-parser could be tricked into adding or modifying properties of Object.prototype using a "__proto__" payload.
<p>Publish Date: 2020-03-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7608>CVE-2020-7608</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7608">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7608</a></p>
<p>Release Date: 2020-03-16</p>
<p>Fix Resolution: v18.1.1;13.1.2;15.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-7608 (Medium) detected in yargs-parser-7.0.0.tgz, yargs-parser-4.2.1.tgz - ## CVE-2020-7608 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>yargs-parser-7.0.0.tgz</b>, <b>yargs-parser-4.2.1.tgz</b></p></summary>
<p>
<details><summary><b>yargs-parser-7.0.0.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-7.0.0.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-7.0.0.tgz</a></p>
<p>Path to dependency file: vuenut/package.json</p>
<p>Path to vulnerable library: vuenut/node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- cli-service-3.0.0-beta.6.tgz (Root Library)
- webpack-3.11.0.tgz
- yargs-8.0.2.tgz
- :x: **yargs-parser-7.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-4.2.1.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-4.2.1.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-4.2.1.tgz</a></p>
<p>Path to dependency file: vuenut/package.json</p>
<p>Path to vulnerable library: vuenut/node_modules/webpack-dev-server/node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- cli-service-3.0.0-beta.6.tgz (Root Library)
- webpack-dev-server-2.11.2.tgz
- yargs-6.6.0.tgz
- :x: **yargs-parser-4.2.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/vuenut/commit/8ef0c5a1523ba08434c5a1320f09f557f566724a">8ef0c5a1523ba08434c5a1320f09f557f566724a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
yargs-parser could be tricked into adding or modifying properties of Object.prototype using a "__proto__" payload.
<p>Publish Date: 2020-03-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7608>CVE-2020-7608</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7608">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7608</a></p>
<p>Release Date: 2020-03-16</p>
<p>Fix Resolution: v18.1.1;13.1.2;15.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve medium detected in yargs parser tgz yargs parser tgz cve medium severity vulnerability vulnerable libraries yargs parser tgz yargs parser tgz yargs parser tgz the mighty option parser used by yargs library home page a href path to dependency file vuenut package json path to vulnerable library vuenut node modules yargs parser package json dependency hierarchy cli service beta tgz root library webpack tgz yargs tgz x yargs parser tgz vulnerable library yargs parser tgz the mighty option parser used by yargs library home page a href path to dependency file vuenut package json path to vulnerable library vuenut node modules webpack dev server node modules yargs parser package json dependency hierarchy cli service beta tgz root library webpack dev server tgz yargs tgz x yargs parser tgz vulnerable library found in head commit a href found in base branch master vulnerability details yargs parser could be tricked into adding or modifying properties of object prototype using a proto payload publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
514,688 | 14,942,741,174 | IssuesEvent | 2021-01-25 21:47:32 | bounswe/bounswe2020group3 | https://api.github.com/repos/bounswe/bounswe2020group3 | closed | [Front-End] [Bug] Recommendation project name looks weird when it is too long | Frontend Priority: Critical Status: In Progress Type: Bug | * **Project: FRONTEND**
* **This is a: BUG REPORT**
* **Description of the issue**
* Recommendation projects' names look buggy in homepage.
* **For bug reports: Explanation of how to reproduce the bug, and what was the expected behaviour.**
Go to homepage . Look at recommendations, find a long named project. You'll understand :)
* **Deadline for resolution:**
25.01.2020
| 1.0 | [Front-End] [Bug] Recommendation project name looks weird when it is too long - * **Project: FRONTEND**
* **This is a: BUG REPORT**
* **Description of the issue**
* Recommendation projects' names look buggy in homepage.
* **For bug reports: Explanation of how to reproduce the bug, and what was the expected behaviour.**
Go to homepage . Look at recommendations, find a long named project. You'll understand :)
* **Deadline for resolution:**
25.01.2020
| non_design | recommendation project name looks weird when it is too long project frontend this is a bug report description of the issue recommendation projects names look buggy in homepage for bug reports explanation of how to reproduce the bug and what was the expected behaviour go to homepage look at recommendations find a long named project you ll understand deadline for resolution | 0 |
417,091 | 12,155,767,309 | IssuesEvent | 2020-04-25 14:34:29 | yalla-coop/tempo | https://api.github.com/repos/yalla-coop/tempo | opened | [component] Create Misc Components | priority-2 technical | Refer to wireframes
### Acceptance Criteria:
- [ ] Popover
- [ ] Go back button
- [ ] Big Button
- [ ] Copy Button
- [ ] Remove / Re-join button
| 1.0 | [component] Create Misc Components - Refer to wireframes
### Acceptance Criteria:
- [ ] Popover
- [ ] Go back button
- [ ] Big Button
- [ ] Copy Button
- [ ] Remove / Re-join button
| non_design | create misc components refer to wireframes acceptance criteria popover go back button big button copy button remove re join button | 0 |
59,323 | 11,958,209,529 | IssuesEvent | 2020-04-04 17:15:45 | SharePoint/sp-dev-fx-webparts | https://api.github.com/repos/SharePoint/sp-dev-fx-webparts | closed | Missing files on npm install | area:sample-code status:answered type:question | After downloading (both by using the ZIP and Git), I am instructed to execute npm install. However, this results in an enormous amount of warmings due to missing files and the end result are errors.
gulp serve als gives errors.
So I'm stuck on getting the files before starting.
How can I get all the files and all dependencies and/or make sure that the code I download is complete and working? | 1.0 | Missing files on npm install - After downloading (both by using the ZIP and Git), I am instructed to execute npm install. However, this results in an enormous amount of warmings due to missing files and the end result are errors.
gulp serve als gives errors.
So I'm stuck on getting the files before starting.
How can I get all the files and all dependencies and/or make sure that the code I download is complete and working? | non_design | missing files on npm install after downloading both by using the zip and git i am instructed to execute npm install however this results in an enormous amount of warmings due to missing files and the end result are errors gulp serve als gives errors so i m stuck on getting the files before starting how can i get all the files and all dependencies and or make sure that the code i download is complete and working | 0 |
114,073 | 14,528,602,781 | IssuesEvent | 2020-12-14 16:44:20 | google/web-stories-wp | https://api.github.com/repos/google/web-stories-wp | closed | Border controls | Bug Bash: 1.2 Group: Design Panel Pod: Prometheus Type: Enhancement | <!-- NOTE: For help requests, support questions, or general feedback, please use the WordPress.org forums instead: https://wordpress.org/support/plugin/web-stories/ -->
## Enhancement
1. ~Remove inside and center option for border.~- completed in #5529.
2. Swap out unlock for new version found in the design. (Please ensure this icon is used throughout the editor).
[Figma](https://www.figma.com/file/NHHMwIfxMnz39NxqkrFb7R/Stories---Post-Stable?node-id=1391%3A118)
## Acceptance Criteria
<!-- One or more bullet points for acceptance criteria. -->
## Implementation Brief
* Make sure that the lock-buttons are the exact same HTML elements both locked and unlocked, so that keyboard focus stays on the button when pressed (the former is the easiest way to implement the latter).
| 1.0 | Border controls - <!-- NOTE: For help requests, support questions, or general feedback, please use the WordPress.org forums instead: https://wordpress.org/support/plugin/web-stories/ -->
## Enhancement
1. ~Remove inside and center option for border.~- completed in #5529.
2. Swap out unlock for new version found in the design. (Please ensure this icon is used throughout the editor).
[Figma](https://www.figma.com/file/NHHMwIfxMnz39NxqkrFb7R/Stories---Post-Stable?node-id=1391%3A118)
## Acceptance Criteria
<!-- One or more bullet points for acceptance criteria. -->
## Implementation Brief
* Make sure that the lock-buttons are the exact same HTML elements both locked and unlocked, so that keyboard focus stays on the button when pressed (the former is the easiest way to implement the latter).
| design | border controls enhancement remove inside and center option for border completed in swap out unlock for new version found in the design please ensure this icon is used throughout the editor acceptance criteria implementation brief make sure that the lock buttons are the exact same html elements both locked and unlocked so that keyboard focus stays on the button when pressed the former is the easiest way to implement the latter | 1 |
123,144 | 16,448,389,271 | IssuesEvent | 2021-05-20 23:19:46 | matomo-org/matomo | https://api.github.com/repos/matomo-org/matomo | closed | annoying banner (the 'refer matomo' banner at the bottom of the page) | c: Design / UI c: Usability | No, seriously folks, I don't need this *reminder* in order to recommend something. Pls don't clutter already cluttered space with ridiculous popups and banners and what not. Pls don't make us use ad-blocker on our own self-hosted analytics ffs. Thx.
Instead, it would be better to actually ad a changelog for the latest version 4.3.0 here https://matomo.org/changelog/ | 1.0 | annoying banner (the 'refer matomo' banner at the bottom of the page) - No, seriously folks, I don't need this *reminder* in order to recommend something. Pls don't clutter already cluttered space with ridiculous popups and banners and what not. Pls don't make us use ad-blocker on our own self-hosted analytics ffs. Thx.
Instead, it would be better to actually ad a changelog for the latest version 4.3.0 here https://matomo.org/changelog/ | design | annoying banner the refer matomo banner at the bottom of the page no seriously folks i don t need this reminder in order to recommend something pls don t clutter already cluttered space with ridiculous popups and banners and what not pls don t make us use ad blocker on our own self hosted analytics ffs thx instead it would be better to actually ad a changelog for the latest version here | 1 |
227,782 | 7,542,697,901 | IssuesEvent | 2018-04-17 13:42:56 | EdwardHinkle/indigenous-ios | https://api.github.com/repos/EdwardHinkle/indigenous-ios | closed | Send access_token in the POST parameters | Micropub Support enhancement high priority | Wordpress and some other sites require access_token to be sent in post parameters. | 1.0 | Send access_token in the POST parameters - Wordpress and some other sites require access_token to be sent in post parameters. | non_design | send access token in the post parameters wordpress and some other sites require access token to be sent in post parameters | 0 |
727,453 | 25,035,965,033 | IssuesEvent | 2022-11-04 16:02:46 | AY2223S1-CS2113-F11-4/tp | https://api.github.com/repos/AY2223S1-CS2113-F11-4/tp | closed | [PE-D][Tester A] Cannot specify the dosage in more detailed way | type.Task priority.Medium | I cannot specify the dosage in a more detailed way, such as 1 tablet / meal, or 1 tablet every meal
<!--session: 1666946592587-a81ae0d5-535c-44da-bc8f-02bb8d100155--><!--Version: Web v3.4.4-->
-------------
Labels: `type.FunctionalityBug` `severity.Medium`
original: AmethystQ/ped#6 | 1.0 | [PE-D][Tester A] Cannot specify the dosage in more detailed way - I cannot specify the dosage in a more detailed way, such as 1 tablet / meal, or 1 tablet every meal
<!--session: 1666946592587-a81ae0d5-535c-44da-bc8f-02bb8d100155--><!--Version: Web v3.4.4-->
-------------
Labels: `type.FunctionalityBug` `severity.Medium`
original: AmethystQ/ped#6 | non_design | cannot specify the dosage in more detailed way i cannot specify the dosage in a more detailed way such as tablet meal or tablet every meal labels type functionalitybug severity medium original amethystq ped | 0 |
136,072 | 19,702,098,241 | IssuesEvent | 2022-01-12 17:37:28 | synthein/synthein | https://api.github.com/repos/synthein/synthein | closed | Give missiles an area of effect | game design | Currently the only kind of damage we have in the game is from collisions. Missiles explode, and that's different that a normal collision between two objects. We need to design and implement a way to do damage in this new kind of way. | 1.0 | Give missiles an area of effect - Currently the only kind of damage we have in the game is from collisions. Missiles explode, and that's different that a normal collision between two objects. We need to design and implement a way to do damage in this new kind of way. | design | give missiles an area of effect currently the only kind of damage we have in the game is from collisions missiles explode and that s different that a normal collision between two objects we need to design and implement a way to do damage in this new kind of way | 1 |
117,697 | 15,165,603,046 | IssuesEvent | 2021-02-12 15:16:37 | department-of-veterans-affairs/va.gov-team | https://api.github.com/repos/department-of-veterans-affairs/va.gov-team | closed | [Design] MyVA 2.0 Convo guide for usability testing of finalized designs | design my-va-dashboard vsa-authenticated-exp | ## Background
Now that we have finalized the designs for MyVA 2.0, we need to create a research plan and conversation guide in preparation for usability testing.
## Tasks
- [x] [Create conversation guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/my-va/2.0-redesign/product/Research%20V2/MyVA2-conversation-guide.md)
- [x] Review with Matt/Samara | 1.0 | [Design] MyVA 2.0 Convo guide for usability testing of finalized designs - ## Background
Now that we have finalized the designs for MyVA 2.0, we need to create a research plan and conversation guide in preparation for usability testing.
## Tasks
- [x] [Create conversation guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/my-va/2.0-redesign/product/Research%20V2/MyVA2-conversation-guide.md)
- [x] Review with Matt/Samara | design | myva convo guide for usability testing of finalized designs background now that we have finalized the designs for myva we need to create a research plan and conversation guide in preparation for usability testing tasks review with matt samara | 1 |
115,498 | 9,797,472,244 | IssuesEvent | 2019-06-11 10:01:19 | w3c/wot-thing-description | https://api.github.com/repos/w3c/wot-thing-description | closed | [Testing] Test results for op in Form seem to be incorrect | Testing by PR transition | Test results for op in Form are coming back as "not implemented" from AssertionTester although they exist. The test should be for at least one valid value; it is not necessary to check for all possible valid values. | 1.0 | [Testing] Test results for op in Form seem to be incorrect - Test results for op in Form are coming back as "not implemented" from AssertionTester although they exist. The test should be for at least one valid value; it is not necessary to check for all possible valid values. | non_design | test results for op in form seem to be incorrect test results for op in form are coming back as not implemented from assertiontester although they exist the test should be for at least one valid value it is not necessary to check for all possible valid values | 0 |
127,223 | 17,200,124,847 | IssuesEvent | 2021-07-17 03:45:28 | GakkiLov3/Githubio.Comment | https://api.github.com/repos/GakkiLov3/Githubio.Comment | opened | Baker Street Irrgulars策划案 0.0.1 | GakkiLov3的Gaming Life🎮 | /post/baker-street-irrgulars-design001/ Gitalk | https://gakkilov3.github.io/post/baker-street-irrgulars-design001/
学校让我做一个游戏当作业。我并不想就随便做做糊弄过去，我还是打算弄个策划案好好规划一下。
游戏名称叫Baker Street Irrgulars，也就是贝克街游击队。是因为我最近正好重温了一遍《名侦探柯南：贝克街的亡灵》，我对里面少年游击队... | 1.0 | Baker Street Irrgulars策划案 0.0.1 | GakkiLov3的Gaming Life🎮 - https://gakkilov3.github.io/post/baker-street-irrgulars-design001/
学校让我做一个游戏当作业。我并不想就随便做做糊弄过去，我还是打算弄个策划案好好规划一下。
游戏名称叫Baker Street Irrgulars，也就是贝克街游击队。是因为我最近正好重温了一遍《名侦探柯南：贝克街的亡灵》，我对里面少年游击队... | design | baker street irrgulars策划案 life🎮 学校让我做一个游戏当作业。我并不想就随便做做糊弄过去，我还是打算弄个策划案好好规划一下。 游戏名称叫baker street irrgulars，也就是贝克街游击队。是因为我最近正好重温了一遍《名侦探柯南：贝克街的亡灵》，我对里面少年游击队 | 1 |
55,681 | 6,916,366,294 | IssuesEvent | 2017-11-29 02:08:41 | w3c/accessibility-intro | https://api.github.com/repos/w3c/accessibility-intro | closed | [W3C] Consistency/inconsistency of bolding | W3C page wai-redesign-before | I think the content of the page is spot on. Its a wonderful introduction to accessibility. However, the few bold sentences (or partially bold sentences) under the intro and Why is throwing me off. Is it just because you're trying to make the case most for the Why of accessibility. And if so, then I think that "Accessibility also benefits people without disabilities" needs to be bolded too.
Nothing else is bolded/strong in the What or How which makes it seem like those things aren't as important as the Why.
| 1.0 | [W3C] Consistency/inconsistency of bolding - I think the content of the page is spot on. Its a wonderful introduction to accessibility. However, the few bold sentences (or partially bold sentences) under the intro and Why is throwing me off. Is it just because you're trying to make the case most for the Why of accessibility. And if so, then I think that "Accessibility also benefits people without disabilities" needs to be bolded too.
Nothing else is bolded/strong in the What or How which makes it seem like those things aren't as important as the Why.
| design | consistency inconsistency of bolding i think the content of the page is spot on its a wonderful introduction to accessibility however the few bold sentences or partially bold sentences under the intro and why is throwing me off is it just because you re trying to make the case most for the why of accessibility and if so then i think that accessibility also benefits people without disabilities needs to be bolded too nothing else is bolded strong in the what or how which makes it seem like those things aren t as important as the why | 1 |
28,060 | 4,077,362,024 | IssuesEvent | 2016-05-30 07:43:32 | geetsisbac/HYUDMDQI7KH46FHYFHPJLMSI | https://api.github.com/repos/geetsisbac/HYUDMDQI7KH46FHYFHPJLMSI | closed | knDhrX2rsStVutnDtZ41d/+95SMqplHWztliykc5mYoYdje3VFcdKPFOLiOX8JP49qizWkbkdNuDl+WECVqB4Y/9IYB2IbolbH7lmmZDEi9aXmFdqWKRxzOMIRmXBBiNnVYMWJ40//6bFPvH6GFKNyM+3roGXxPJp8d7lCA36EY= | design | Y96T1hY4LfnlGB6Pv+Jip6lWNYWm7eYnWqIPL0l5e0pEzcxRhq77c0b6/LXYmOlyWYHf3K722sIxR8n+scWNNxRaIDTkMkX3FVoIXHTbmk0UmM77/Va09O0I20yO6p3ZHZ77RL34Lx/71W+LfpPepZmTAqAhg22MfgrKzMYHFz4V93aP3O2HHWXl18GIsn0VCAzVB8fq79bmBe99gHVuxxV66BXLTe3l5m7JIVq+86tK8/B0j+GyLo/qhw5hT9tkD+G3n0TDsODtC5Z/YAHQXfg4+eH2VrF9bgUQPHcvyAaeyTd3qaWjHLRt8Z6FJqtbxjpGUXLTFRcrExpdkjzfzeHibrfUAjCilaa+TtUPDwDKKH+ID0euHEmw4zZY3NDwOtUI4Qv4v7dCKn9ip5vBcXqxeyIvIS8FemXKVXm8h24Gu6gqoz3bEp1/vHk1N/ciAMyY85PDdAB2yrpNxYp+wPTom+LiFUhn9eSt+PjPGZ91jvzJMJGEdWOwXjUZAxK2/H0zKRdbesjio7aAZRmFYpDiv37emzV3FkxhZc962iXZPKiTPCPx8+o4MaPl9HwS5H12ChnZ+vOmhl3qTfToh+AchvQBwqL40nLU5NiBI5pG/rYh9WUaIt1ibQi7co+I3NZXLX8M40UpiyJ+LywdFw/kmwD0IBLE/oNFIieWVXDAsDJtdwUfviGn2nohs+p3FZNT9C+f93NNPeAklEVPA9G1Zvx0jA/MvS5g4J7AIWqT82npirUJXxaQE/jgth4XO85B1yjQfpVq7pcRkuyvd+fJX+W2waa39OmU2TE0Lk+3kA+INlfwpfg1hctaSMhqA4kYusM2PGRt8Dtv4FrsSH/k5NHSQabqhvz4Wc/agk9JeCGVqqOFTdDpV00+U5MdH+F1tXI7nUAiB8qD1RDLzC9Yw20meKmDUDW+gRMdW/Gk9qwexfwwTXpyllQFbt4UpPY/uD9ntZ8D7dEne8DunQ== | 1.0 | knDhrX2rsStVutnDtZ41d/+95SMqplHWztliykc5mYoYdje3VFcdKPFOLiOX8JP49qizWkbkdNuDl+WECVqB4Y/9IYB2IbolbH7lmmZDEi9aXmFdqWKRxzOMIRmXBBiNnVYMWJ40//6bFPvH6GFKNyM+3roGXxPJp8d7lCA36EY= - Y96T1hY4LfnlGB6Pv+Jip6lWNYWm7eYnWqIPL0l5e0pEzcxRhq77c0b6/LXYmOlyWYHf3K722sIxR8n+scWNNxRaIDTkMkX3FVoIXHTbmk0UmM77/Va09O0I20yO6p3ZHZ77RL34Lx/71W+LfpPepZmTAqAhg22MfgrKzMYHFz4V93aP3O2HHWXl18GIsn0VCAzVB8fq79bmBe99gHVuxxV66BXLTe3l5m7JIVq+86tK8/B0j+GyLo/qhw5hT9tkD+G3n0TDsODtC5Z/YAHQXfg4+eH2VrF9bgUQPHcvyAaeyTd3qaWjHLRt8Z6FJqtbxjpGUXLTFRcrExpdkjzfzeHibrfUAjCilaa+TtUPDwDKKH+ID0euHEmw4zZY3NDwOtUI4Qv4v7dCKn9ip5vBcXqxeyIvIS8FemXKVXm8h24Gu6gqoz3bEp1/vHk1N/ciAMyY85PDdAB2yrpNxYp+wPTom+LiFUhn9eSt+PjPGZ91jvzJMJGEdWOwXjUZAxK2/H0zKRdbesjio7aAZRmFYpDiv37emzV3FkxhZc962iXZPKiTPCPx8+o4MaPl9HwS5H12ChnZ+vOmhl3qTfToh+AchvQBwqL40nLU5NiBI5pG/rYh9WUaIt1ibQi7co+I3NZXLX8M40UpiyJ+LywdFw/kmwD0IBLE/oNFIieWVXDAsDJtdwUfviGn2nohs+p3FZNT9C+f93NNPeAklEVPA9G1Zvx0jA/MvS5g4J7AIWqT82npirUJXxaQE/jgth4XO85B1yjQfpVq7pcRkuyvd+fJX+W2waa39OmU2TE0Lk+3kA+INlfwpfg1hctaSMhqA4kYusM2PGRt8Dtv4FrsSH/k5NHSQabqhvz4Wc/agk9JeCGVqqOFTdDpV00+U5MdH+F1tXI7nUAiB8qD1RDLzC9Yw20meKmDUDW+gRMdW/Gk9qwexfwwTXpyllQFbt4UpPY/uD9ntZ8D7dEne8DunQ== | design | gylo ttupdwdkkh wptom lywdfw fjx grmdw | 1 |
152,068 | 23,909,747,183 | IssuesEvent | 2022-09-09 06:57:41 | baloise-incubator/design-system | https://api.github.com/repos/baloise-incubator/design-system | closed | [Status: Refined] Component review & adjustment | 🎨 Design Support | All components marked components (white / [link](https://confluence.ibmix.de/display/BaloiseRebranding/Priorisierung+und+Status)) have been reviewed and adapted according to following criteria.
**AC:**
1. Concept review (review old implementation incl. [headline implementation](https://confluence.ibmix.de/pages/viewpage.action?spaceKey=BaloiseRebranding&title=Dokumentation+Headlines))
3. Typography
4. Spacing (padding, margin) | 1.0 | [Status: Refined] Component review & adjustment - All components marked components (white / [link](https://confluence.ibmix.de/display/BaloiseRebranding/Priorisierung+und+Status)) have been reviewed and adapted according to following criteria.
**AC:**
1. Concept review (review old implementation incl. [headline implementation](https://confluence.ibmix.de/pages/viewpage.action?spaceKey=BaloiseRebranding&title=Dokumentation+Headlines))
3. Typography
4. Spacing (padding, margin) | design | component review adjustment all components marked components white have been reviewed and adapted according to following criteria ac concept review review old implementation incl typography spacing padding margin | 1 |
2,232 | 2,600,200,436 | IssuesEvent | 2015-02-23 14:58:59 | lsecities/lsecities-wp-theme | https://api.github.com/repos/lsecities/lsecities-wp-theme | opened | publications list - overall list, with filters | from:2014-12 collated feedback needs:design needs:UX | suggestion:
*Would be great to have one place where all publications can be found, possibly organised by year and then author. Did we not have something like that allowing for custom sorting?* | 1.0 | publications list - overall list, with filters - suggestion:
*Would be great to have one place where all publications can be found, possibly organised by year and then author. Did we not have something like that allowing for custom sorting?* | design | publications list overall list with filters suggestion would be great to have one place where all publications can be found possibly organised by year and then author did we not have something like that allowing for custom sorting | 1 |
79,238 | 9,855,148,814 | IssuesEvent | 2019-06-19 18:38:49 | Opentrons/opentrons | https://api.github.com/repos/Opentrons/opentrons | closed | PD: Fix labware name disambiguation numbers | bug medium protocol designer | ## overview
Loaded files should show the labware disambiguation numbers, but they don't!
## acceptance criteria
- [ ] Labware names should work like file name defaults on most OSs:
```
"my labware"
then "my labware (1)"
then "my labware (2)"
```
If you have nicknames
```
"my labware (2)"
"my labware (2)"
"my labware (10)"
```
Pick the highest number and increment it, so the next should be `"my labware (11)"`
### Implementation Note
Probably we should keep the number in the `nickname` itself, not in some `disambiguationNumber` thing, so it passes down to Run App and load file works.
### Some edge cases:
- [ ] Creating a labware should increment the number
- [ ] Duplicating a labware should increment the number (not copy it)
- [ ] After saving a protocol and loading it again, disambiguation numbers should be maintained (previously we had a bug where it dropped them, make sure this doesn't sneak back in)
- [ ] If a user renames a labware, do the same thing as if they were naming a labware initially. No distinction btw custom names and default displayName names as far as disambiguation numbers go | 1.0 | PD: Fix labware name disambiguation numbers - ## overview
Loaded files should show the labware disambiguation numbers, but they don't!
## acceptance criteria
- [ ] Labware names should work like file name defaults on most OSs:
```
"my labware"
then "my labware (1)"
then "my labware (2)"
```
If you have nicknames
```
"my labware (2)"
"my labware (2)"
"my labware (10)"
```
Pick the highest number and increment it, so the next should be `"my labware (11)"`
### Implementation Note
Probably we should keep the number in the `nickname` itself, not in some `disambiguationNumber` thing, so it passes down to Run App and load file works.
### Some edge cases:
- [ ] Creating a labware should increment the number
- [ ] Duplicating a labware should increment the number (not copy it)
- [ ] After saving a protocol and loading it again, disambiguation numbers should be maintained (previously we had a bug where it dropped them, make sure this doesn't sneak back in)
- [ ] If a user renames a labware, do the same thing as if they were naming a labware initially. No distinction btw custom names and default displayName names as far as disambiguation numbers go | design | pd fix labware name disambiguation numbers overview loaded files should show the labware disambiguation numbers but they don t acceptance criteria labware names should work like file name defaults on most oss my labware then my labware then my labware if you have nicknames my labware my labware my labware pick the highest number and increment it so the next should be my labware implementation note probably we should keep the number in the nickname itself not in some disambiguationnumber thing so it passes down to run app and load file works some edge cases creating a labware should increment the number duplicating a labware should increment the number not copy it after saving a protocol and loading it again disambiguation numbers should be maintained previously we had a bug where it dropped them make sure this doesn t sneak back in if a user renames a labware do the same thing as if they were naming a labware initially no distinction btw custom names and default displayname names as far as disambiguation numbers go | 1 |
2,146 | 2,590,850,291 | IssuesEvent | 2015-02-18 21:27:47 | IQSS/dataverse | https://api.github.com/repos/IQSS/dataverse | closed | Color Scheme/Layout/UI Components - General Application UI Design | Priority: High Status: Design Status: QA Type: Feature | ---
Author Name: **Mike Heppler** (@mheppler)
Original Redmine Issue: 3511, https://redmine.hmdc.harvard.edu/issues/3511
Original Date: 2014-02-24
Original Assignee: Mike Heppler
---
Clean up the general look and feel of the application, by applying a consistent layout, with a unique color scheme, as well as font face, font size, link color, etc.
Related issue: font size on the create version of dataset is different than the edit version.
| 1.0 | Color Scheme/Layout/UI Components - General Application UI Design - ---
Author Name: **Mike Heppler** (@mheppler)
Original Redmine Issue: 3511, https://redmine.hmdc.harvard.edu/issues/3511
Original Date: 2014-02-24
Original Assignee: Mike Heppler
---
Clean up the general look and feel of the application, by applying a consistent layout, with a unique color scheme, as well as font face, font size, link color, etc.
Related issue: font size on the create version of dataset is different than the edit version.
| design | color scheme layout ui components general application ui design author name mike heppler mheppler original redmine issue original date original assignee mike heppler clean up the general look and feel of the application by applying a consistent layout with a unique color scheme as well as font face font size link color etc related issue font size on the create version of dataset is different than the edit version | 1 |
33,343 | 4,470,039,308 | IssuesEvent | 2016-08-25 14:49:18 | Qabel/qabel-desktop | https://api.github.com/repos/Qabel/qabel-desktop | closed | Final implementation of Orange Theme | design |
Please check these facts for proper implementation:
**Left Sidebar:**
* "Normal" State = white (icons and text)
* "mouse-over" state = 80% black (icons and text)
* "active" state = 80% black (icons and text) and white background with drop-shadow at upper and lower edge
* the same for the icons on the lower end of the left sidebar without the drop-shadow
**The Middle-Menue-entry-highlight:**
* "Normal" State = 80% black (icons and text) & no background
* "mouse-over" state = 80% black (icons and text) & 10% black background
* "active" state = 80% black (icons and text) and 30% black background and white sidebar pointer with drop-shadow
**The Buttons:**
* "Normal" State = 80% black (icons, text and outline) & no background
* "mouse-over" state = 50% black (icons, text and outline) & no background
* "active" state = qabel orange (R: 255 G: 89 B: 8) (icons, text and outline) & no background
| 1.0 | Final implementation of Orange Theme -
Please check these facts for proper implementation:
**Left Sidebar:**
* "Normal" State = white (icons and text)
* "mouse-over" state = 80% black (icons and text)
* "active" state = 80% black (icons and text) and white background with drop-shadow at upper and lower edge
* the same for the icons on the lower end of the left sidebar without the drop-shadow
**The Middle-Menue-entry-highlight:**
* "Normal" State = 80% black (icons and text) & no background
* "mouse-over" state = 80% black (icons and text) & 10% black background
* "active" state = 80% black (icons and text) and 30% black background and white sidebar pointer with drop-shadow
**The Buttons:**
* "Normal" State = 80% black (icons, text and outline) & no background
* "mouse-over" state = 50% black (icons, text and outline) & no background
* "active" state = qabel orange (R: 255 G: 89 B: 8) (icons, text and outline) & no background
| design | final implementation of orange theme please check these facts for proper implementation left sidebar normal state white icons and text mouse over state black icons and text active state black icons and text and white background with drop shadow at upper and lower edge the same for the icons on the lower end of the left sidebar without the drop shadow the middle menue entry highlight normal state black icons and text no background mouse over state black icons and text black background active state black icons and text and black background and white sidebar pointer with drop shadow the buttons normal state black icons text and outline no background mouse over state black icons text and outline no background active state qabel orange r g b icons text and outline no background | 1 |
61,780 | 7,517,628,811 | IssuesEvent | 2018-04-12 04:48:46 | BrianZ1/CapstoneProject | https://api.github.com/repos/BrianZ1/CapstoneProject | closed | Deployment | Final Website design | Move from development environment to hosting my website somewhere. Django has a check list of things to do before deployment. | 1.0 | Deployment - Move from development environment to hosting my website somewhere. Django has a check list of things to do before deployment. | design | deployment move from development environment to hosting my website somewhere django has a check list of things to do before deployment | 1 |
508,648 | 14,704,081,086 | IssuesEvent | 2021-01-04 15:58:22 | geodesymiami/rsmas_insar | https://api.github.com/repos/geodesymiami/rsmas_insar | closed | Move `overwrite_stored_date_file` to `process_rsmas.py` | Priority: Medium Status: On Hold Type: Maintenance / Refactor | We should move the `overwrite_stored_date_file` function that is used in `run_operations.py` to overwrite the the `stored_date.date` file to the end of `process_rsmas.py`. This will make sure that the `stored_date.date` file is not overwritten if `process_rsmas.py` fails in the middle of execution. This also make more sense, as the updating of the `stored_date.date` file is more of a `process_rsmas.py` routine than a `run_operations.py` routine.
This can be easily accomplished by adding a `--update` command-line parameter to `process_rsmas.py` and executing the `overwrite_stored_date_file` function if that parameter is given. | 1.0 | Move `overwrite_stored_date_file` to `process_rsmas.py` - We should move the `overwrite_stored_date_file` function that is used in `run_operations.py` to overwrite the the `stored_date.date` file to the end of `process_rsmas.py`. This will make sure that the `stored_date.date` file is not overwritten if `process_rsmas.py` fails in the middle of execution. This also make more sense, as the updating of the `stored_date.date` file is more of a `process_rsmas.py` routine than a `run_operations.py` routine.
This can be easily accomplished by adding a `--update` command-line parameter to `process_rsmas.py` and executing the `overwrite_stored_date_file` function if that parameter is given. | non_design | move overwrite stored date file to process rsmas py we should move the overwrite stored date file function that is used in run operations py to overwrite the the stored date date file to the end of process rsmas py this will make sure that the stored date date file is not overwritten if process rsmas py fails in the middle of execution this also make more sense as the updating of the stored date date file is more of a process rsmas py routine than a run operations py routine this can be easily accomplished by adding a update command line parameter to process rsmas py and executing the overwrite stored date file function if that parameter is given | 0 |
94,033 | 15,962,225,995 | IssuesEvent | 2021-04-16 00:47:45 | elastic/kibana | https://api.github.com/repos/elastic/kibana | opened | [Security Solution][Detections] Error Toast is displayed if user has no configured SecSol indices | Team: SecuritySolution Team:Detections and Resp bug v7.12.0 | **Describe the bug:**
If the user has detections alerts but has deleted their `securitySolution:defaultIndex` UI setting, an error toast will be displayed due to a 404 from an errant call to an ML API.
**Steps to reproduce:**
1. Enable ML
2. Generate Detections Alerts
3. Delete the `securitySolution:defaultIndex` UI setting
**Current behavior:**
An error toast is displayed
**Expected behavior:**
No error toast is displayed
**Screenshots (if relevant):**
<img width="950" alt="Detections_-_Kibana (1)" src="https://user-images.githubusercontent.com/657252/114955922-54e0e180-9e23-11eb-9fee-0c7a752fd6a6.png">
| True | [Security Solution][Detections] Error Toast is displayed if user has no configured SecSol indices - **Describe the bug:**
If the user has detections alerts but has deleted their `securitySolution:defaultIndex` UI setting, an error toast will be displayed due to a 404 from an errant call to an ML API.
**Steps to reproduce:**
1. Enable ML
2. Generate Detections Alerts
3. Delete the `securitySolution:defaultIndex` UI setting
**Current behavior:**
An error toast is displayed
**Expected behavior:**
No error toast is displayed
**Screenshots (if relevant):**
<img width="950" alt="Detections_-_Kibana (1)" src="https://user-images.githubusercontent.com/657252/114955922-54e0e180-9e23-11eb-9fee-0c7a752fd6a6.png">
| non_design | error toast is displayed if user has no configured secsol indices describe the bug if the user has detections alerts but has deleted their securitysolution defaultindex ui setting an error toast will be displayed due to a from an errant call to an ml api steps to reproduce enable ml generate detections alerts delete the securitysolution defaultindex ui setting current behavior an error toast is displayed expected behavior no error toast is displayed screenshots if relevant img width alt detections kibana src | 0 |
169,938 | 26,878,132,214 | IssuesEvent | 2023-02-05 09:45:08 | YAPP-Github/21st-Web-Team-1-FE | https://api.github.com/repos/YAPP-Github/21st-Web-Team-1-FE | closed | 💄 밈 상세 페이지 디자인 반영 | design | ### 정보
- 담당자 : @elbica
- 개요 :
- 기한 :
### 설명
해당 컴포넌트 디자인 사진과 설명을 서술합니다.
### 체크리스트
- [x] 토스트 스타일 & 애니메이션 반영
- [x] 밈 내보내기 드롭다운 기능, 애니메이션 반영
- [x] 밈 공유 모달 기능, 애니메이션 반영
- [x] 연관밈 (현재 인기밈) 반영
- [x] 모달 설계 | 1.0 | 💄 밈 상세 페이지 디자인 반영 - ### 정보
- 담당자 : @elbica
- 개요 :
- 기한 :
### 설명
해당 컴포넌트 디자인 사진과 설명을 서술합니다.
### 체크리스트
- [x] 토스트 스타일 & 애니메이션 반영
- [x] 밈 내보내기 드롭다운 기능, 애니메이션 반영
- [x] 밈 공유 모달 기능, 애니메이션 반영
- [x] 연관밈 (현재 인기밈) 반영
- [x] 모달 설계 | design | 💄 밈 상세 페이지 디자인 반영 정보 담당자 elbica 개요 기한 설명 해당 컴포넌트 디자인 사진과 설명을 서술합니다 체크리스트 토스트 스타일 애니메이션 반영 밈 내보내기 드롭다운 기능 애니메이션 반영 밈 공유 모달 기능 애니메이션 반영 연관밈 현재 인기밈 반영 모달 설계 | 1 |
178,000 | 29,479,236,680 | IssuesEvent | 2023-06-02 03:01:22 | hackforla/food-oasis | https://api.github.com/repos/hackforla/food-oasis | opened | Design System: FIgma Tokens | Role: Design UI/UX | Create and update Figma tokens for a robust design system that works with dev codebase.
Input the following:
[ ] buttons
[ ] states
[ ] color
[ ] icons
[ ] images
[ ] typography
[ ] fonts
[ ] other inputs
Creating basic documentation of when to use certain parts in the design system. | 1.0 | Design System: FIgma Tokens - Create and update Figma tokens for a robust design system that works with dev codebase.
Input the following:
[ ] buttons
[ ] states
[ ] color
[ ] icons
[ ] images
[ ] typography
[ ] fonts
[ ] other inputs
Creating basic documentation of when to use certain parts in the design system. | design | design system figma tokens create and update figma tokens for a robust design system that works with dev codebase input the following buttons states color icons images typography fonts other inputs creating basic documentation of when to use certain parts in the design system | 1 |
157,809 | 24,731,564,577 | IssuesEvent | 2022-10-20 18:03:29 | uwscope/scope-web | https://api.github.com/repos/uwscope/scope-web | opened | Notify patients of resources assigned | enhancement Registry client Patient client App service Registry design Patient design Low priority Backend | **Problem**
"Want a way to assign resources (Behavioral Strategies) through the app" Allow the care team to notify patients in the app of a resource.
**Describe Desired Solution**
Similarly to the PHQ and GAD a prompt on the app home screen will show up to let the patient know they have have been assigned a resource. from the registry.
**Describe Alternatives**
A clear and concise description of any alternative solutions or features you've considered.
**Additional Context**
Add any other context or screenshots about the feature request here.
| 2.0 | Notify patients of resources assigned - **Problem**
"Want a way to assign resources (Behavioral Strategies) through the app" Allow the care team to notify patients in the app of a resource.
**Describe Desired Solution**
Similarly to the PHQ and GAD a prompt on the app home screen will show up to let the patient know they have have been assigned a resource. from the registry.
**Describe Alternatives**
A clear and concise description of any alternative solutions or features you've considered.
**Additional Context**
Add any other context or screenshots about the feature request here.
| design | notify patients of resources assigned problem want a way to assign resources behavioral strategies through the app allow the care team to notify patients in the app of a resource describe desired solution similarly to the phq and gad a prompt on the app home screen will show up to let the patient know they have have been assigned a resource from the registry describe alternatives a clear and concise description of any alternative solutions or features you ve considered additional context add any other context or screenshots about the feature request here | 1 |
13,603 | 16,129,234,790 | IssuesEvent | 2021-04-29 00:08:35 | AzureAD/microsoft-authentication-library-for-js | https://api.github.com/repos/AzureAD/microsoft-authentication-library-for-js | closed | Handling IE11's cache-control issues | answered compatibility msal-browser no-issue-activity question | ## Library
- [ ] `msal@1.x.x` or `@azure/msal@1.x.x`
- [x] `@azure/msal-browser@2.11.0`
- [ ] `@azure/msal-node@1.x.x`
- [x] `@azure/msal-react@1.0.0-alpha.4`
- [ ] `@azure/msal-angular@0.x.x`
- [ ] `@azure/msal-angular@1.x.x`
- [ ] `@azure/msal-angular@2.x.x`
- [ ] `@azure/msal-angularjs@1.x.x`
## Description
We came across an interesting problem trying to use our site, msal and IE11.
We have a site which is available in two languages, so each site is on a separate subdomain. I don't want to publish the URLs here, but they're similar to lang1.web.core.windows.net and lang2.web.core.windows.net, while we're testing them. The user can click a button which redirects them to the same location on the other language site, and they should stay logged in.
On IE11 the problem is that when you're on the lang1 site, MSAL makes a request to the openid-configuration endpoint. When it comes back, it has an Access-Control-Allow-Origin header set to the lang1 domain, and a Cache-Control header set to 'private'. This should mean that when you switch to lang2 and request the config, it should re-request the config, as it's a different domain.
Unfortunately, IE11 thinks that sub-domains are the same domain for the sake of caching, so when you request the config from the lang1 domain then again from the lang2 domain, it gives you the cached version the second time. This shouldn't be a problem, as the content is identical.
Unfortunately, IE11 thinks that sub-domains are different domains for sake of CORS, and so it then rejects its own cached copy of the config.
We have got(ten) around this by passing a patched version of XhrClient in config.system.networkClient when we create the PublicClientApplication instance and the browser is IE11, which sends "Cache-Control: no-cache", "Pragma: no-cache" and "Expires: -1" headers with GET requests, which seems to do the job.
But I was wondering if I'm missing something here. And also wondering if there should be an option to do this in the library instead of having to patch it like this. I don't think you'd necessarily want to always send the cache busting headers, as caching would still be useful if you weren't using subdomains. (I'm guessing. Unless there are other IE11 issues I haven't come across yet, which is quite possible.)
## Source
- [ ] Internal (Microsoft)
- [x] Customer request
| True | Handling IE11's cache-control issues - ## Library
- [ ] `msal@1.x.x` or `@azure/msal@1.x.x`
- [x] `@azure/msal-browser@2.11.0`
- [ ] `@azure/msal-node@1.x.x`
- [x] `@azure/msal-react@1.0.0-alpha.4`
- [ ] `@azure/msal-angular@0.x.x`
- [ ] `@azure/msal-angular@1.x.x`
- [ ] `@azure/msal-angular@2.x.x`
- [ ] `@azure/msal-angularjs@1.x.x`
## Description
We came across an interesting problem trying to use our site, msal and IE11.
We have a site which is available in two languages, so each site is on a separate subdomain. I don't want to publish the URLs here, but they're similar to lang1.web.core.windows.net and lang2.web.core.windows.net, while we're testing them. The user can click a button which redirects them to the same location on the other language site, and they should stay logged in.
On IE11 the problem is that when you're on the lang1 site, MSAL makes a request to the openid-configuration endpoint. When it comes back, it has an Access-Control-Allow-Origin header set to the lang1 domain, and a Cache-Control header set to 'private'. This should mean that when you switch to lang2 and request the config, it should re-request the config, as it's a different domain.
Unfortunately, IE11 thinks that sub-domains are the same domain for the sake of caching, so when you request the config from the lang1 domain then again from the lang2 domain, it gives you the cached version the second time. This shouldn't be a problem, as the content is identical.
Unfortunately, IE11 thinks that sub-domains are different domains for sake of CORS, and so it then rejects its own cached copy of the config.
We have got(ten) around this by passing a patched version of XhrClient in config.system.networkClient when we create the PublicClientApplication instance and the browser is IE11, which sends "Cache-Control: no-cache", "Pragma: no-cache" and "Expires: -1" headers with GET requests, which seems to do the job.
But I was wondering if I'm missing something here. And also wondering if there should be an option to do this in the library instead of having to patch it like this. I don't think you'd necessarily want to always send the cache busting headers, as caching would still be useful if you weren't using subdomains. (I'm guessing. Unless there are other IE11 issues I haven't come across yet, which is quite possible.)
## Source
- [ ] Internal (Microsoft)
- [x] Customer request
| non_design | handling s cache control issues library msal x x or azure msal x x azure msal browser azure msal node x x azure msal react alpha azure msal angular x x azure msal angular x x azure msal angular x x azure msal angularjs x x description we came across an interesting problem trying to use our site msal and we have a site which is available in two languages so each site is on a separate subdomain i don t want to publish the urls here but they re similar to web core windows net and web core windows net while we re testing them the user can click a button which redirects them to the same location on the other language site and they should stay logged in on the problem is that when you re on the site msal makes a request to the openid configuration endpoint when it comes back it has an access control allow origin header set to the domain and a cache control header set to private this should mean that when you switch to and request the config it should re request the config as it s a different domain unfortunately thinks that sub domains are the same domain for the sake of caching so when you request the config from the domain then again from the domain it gives you the cached version the second time this shouldn t be a problem as the content is identical unfortunately thinks that sub domains are different domains for sake of cors and so it then rejects its own cached copy of the config we have got ten around this by passing a patched version of xhrclient in config system networkclient when we create the publicclientapplication instance and the browser is which sends cache control no cache pragma no cache and expires headers with get requests which seems to do the job but i was wondering if i m missing something here and also wondering if there should be an option to do this in the library instead of having to patch it like this i don t think you d necessarily want to always send the cache busting headers as caching would still be useful if you weren t using subdomains i m guessing unless there are other issues i haven t come across yet which is quite possible source internal microsoft customer request | 0 |
2,283 | 2,602,523,316 | IssuesEvent | 2015-02-24 09:35:21 | calblueprint/worldreader | https://api.github.com/repos/calblueprint/worldreader | closed | Move header elements into grid | Design | The worldreader logo and the links on the right in the header would be easier to see if they weren't on the side but in the grid with everything else. | 1.0 | Move header elements into grid - The worldreader logo and the links on the right in the header would be easier to see if they weren't on the side but in the grid with everything else. | design | move header elements into grid the worldreader logo and the links on the right in the header would be easier to see if they weren t on the side but in the grid with everything else | 1 |
156,100 | 24,567,194,077 | IssuesEvent | 2022-10-13 04:57:40 | laurenkiyomi/fa22-cse110-lab3 | https://api.github.com/repos/laurenkiyomi/fa22-cse110-lab3 | opened | Style media and form | design frontend | ## What's the issue?
Media and form don't have CSS styling
## How are you fixing this issue?
## Add a screenshot of the updated component!!
| 1.0 | Style media and form - ## What's the issue?
Media and form don't have CSS styling
## How are you fixing this issue?
## Add a screenshot of the updated component!!
| design | style media and form what s the issue media and form don t have css styling how are you fixing this issue add a screenshot of the updated component | 1 |
44,468 | 12,196,728,572 | IssuesEvent | 2020-04-29 19:30:28 | department-of-veterans-affairs/va.gov-cms | https://api.github.com/repos/department-of-veterans-affairs/va.gov-cms | opened | Maintenance mode causes infinite redirect for non-admin users logging in. | Defect | **Describe the defect**
If the site is in maintenance mode and a non-admin user logs in, an infinite redirect is created as drupal tries to send them to the maintenance mode and our own code tries to send them to the systems page.
We need to alter our logic to not redirect if the site is in maintenance mode.
**To Reproduce**
Steps to reproduce the behavior:
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information if relevant, or delete):**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
**Additional context**
Add any other context about the problem here.
## Labels
- [/] Issue type (red) (defaults to "Defect")
- [ ] CMS subsystem (green)
- [ ] CMS practice area (blue)
- [/] CMS objective (orange) (not needed for bug tickets)
- [ ] CMS-supported product (black)
| 1.0 | Maintenance mode causes infinite redirect for non-admin users logging in. - **Describe the defect**
If the site is in maintenance mode and a non-admin user logs in, an infinite redirect is created as drupal tries to send them to the maintenance mode and our own code tries to send them to the systems page.
We need to alter our logic to not redirect if the site is in maintenance mode.
**To Reproduce**
Steps to reproduce the behavior:
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information if relevant, or delete):**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
**Additional context**
Add any other context about the problem here.
## Labels
- [/] Issue type (red) (defaults to "Defect")
- [ ] CMS subsystem (green)
- [ ] CMS practice area (blue)
- [/] CMS objective (orange) (not needed for bug tickets)
- [ ] CMS-supported product (black)
| non_design | maintenance mode causes infinite redirect for non admin users logging in describe the defect if the site is in maintenance mode and a non admin user logs in an infinite redirect is created as drupal tries to send them to the maintenance mode and our own code tries to send them to the systems page we need to alter our logic to not redirect if the site is in maintenance mode to reproduce steps to reproduce the behavior expected behavior a clear and concise description of what you expected to happen screenshots if applicable add screenshots to help explain your problem desktop please complete the following information if relevant or delete os browser version additional context add any other context about the problem here labels issue type red defaults to defect cms subsystem green cms practice area blue cms objective orange not needed for bug tickets cms supported product black | 0 |
24,214 | 3,897,295,951 | IssuesEvent | 2016-04-16 09:59:33 | BobbyDarkbean/consumer-producer-solutions | https://api.github.com/repos/BobbyDarkbean/consumer-producer-solutions | closed | CP-31: add ServerDaemon virtual class | abstract design prototype | A class setting up and running the work loop. Subclasses provide concrete chart and valid context, also are meant to manage server settings configured in external file like _settings.ini_.
Inspired by the concept of 'main application object'. | 1.0 | CP-31: add ServerDaemon virtual class - A class setting up and running the work loop. Subclasses provide concrete chart and valid context, also are meant to manage server settings configured in external file like _settings.ini_.
Inspired by the concept of 'main application object'. | design | cp add serverdaemon virtual class a class setting up and running the work loop subclasses provide concrete chart and valid context also are meant to manage server settings configured in external file like settings ini inspired by the concept of main application object | 1 |
32,636 | 4,387,571,049 | IssuesEvent | 2016-08-08 16:09:27 | Wisembly/tapestry | https://api.github.com/repos/Wisembly/tapestry | closed | Generic UI states | need-design on-hold | Something is missing from most CSS Frameworks, UI States;
Considering 6 UI States;
- Default
- Is Empty
- Is Disabled / Suspended
- Is Loading / Busy
- Is Loaded / Success
- Is Selected
Quite hard to implement in a generic way | 1.0 | Generic UI states - Something is missing from most CSS Frameworks, UI States;
Considering 6 UI States;
- Default
- Is Empty
- Is Disabled / Suspended
- Is Loading / Busy
- Is Loaded / Success
- Is Selected
Quite hard to implement in a generic way | design | generic ui states something is missing from most css frameworks ui states considering ui states default is empty is disabled suspended is loading busy is loaded success is selected quite hard to implement in a generic way | 1 |
170,486 | 26,966,616,168 | IssuesEvent | 2023-02-08 23:05:11 | PyNorte/pynorte2023-org | https://api.github.com/repos/PyNorte/pynorte2023-org | opened | Reunião do time de Design - 06/02/2023 | Design Reunião | Eduarda Venturelli (Liderança)
Christian Alencar (@christianalencar)
Thainara Wulfert
Links:
https://stg-pybr-2022.netlify.app/
Trello - UI/UX
https://trello.com/invite/b/BHmIrFzg/ATTI07fd14ff230a79d3828f6566d4d4577752CCDAE3/organizacao-ux-ui
Instagram - PytonBrasil
https://www.instagram.com/pythonbrasil/
1 - Baixa fidelidade do site;
2 - Desgin da Logo, definir e o responsavel pelo mesmo;
3 - Criação do Trelo para as atividades;
4 - Utilização do Figma para design e informação para equipe de Web;
5 - Ideia para identidade;
6 - Sobre como vai ser a questão do patrocinio;
7 - Procurar pessoal para RP;
| 1.0 | Reunião do time de Design - 06/02/2023 - Eduarda Venturelli (Liderança)
Christian Alencar (@christianalencar)
Thainara Wulfert
Links:
https://stg-pybr-2022.netlify.app/
Trello - UI/UX
https://trello.com/invite/b/BHmIrFzg/ATTI07fd14ff230a79d3828f6566d4d4577752CCDAE3/organizacao-ux-ui
Instagram - PytonBrasil
https://www.instagram.com/pythonbrasil/
1 - Baixa fidelidade do site;
2 - Desgin da Logo, definir e o responsavel pelo mesmo;
3 - Criação do Trelo para as atividades;
4 - Utilização do Figma para design e informação para equipe de Web;
5 - Ideia para identidade;
6 - Sobre como vai ser a questão do patrocinio;
7 - Procurar pessoal para RP;
| design | reunião do time de design eduarda venturelli liderança christian alencar christianalencar thainara wulfert links trello ui ux instagram pytonbrasil baixa fidelidade do site desgin da logo definir e o responsavel pelo mesmo criação do trelo para as atividades utilização do figma para design e informação para equipe de web ideia para identidade sobre como vai ser a questão do patrocinio procurar pessoal para rp | 1 |
461,242 | 13,227,183,630 | IssuesEvent | 2020-08-18 02:21:23 | Kodular/Kodular-Creator-Issue-Tracker | https://api.github.com/repos/Kodular/Kodular-Creator-Issue-Tracker | opened | Option to prevent split-screen | community request enhancement feature request noted for future work priority: low | All Kodular apps can be put into split-screen mode but there may be cases where the app developer doesn't want this. Consider adding a Screen1-only property to allow/disallow split-screen. | 1.0 | Option to prevent split-screen - All Kodular apps can be put into split-screen mode but there may be cases where the app developer doesn't want this. Consider adding a Screen1-only property to allow/disallow split-screen. | non_design | option to prevent split screen all kodular apps can be put into split screen mode but there may be cases where the app developer doesn t want this consider adding a only property to allow disallow split screen | 0 |
108,972 | 13,697,708,320 | IssuesEvent | 2020-10-01 03:51:29 | thenewboston-developers/Account-Manager | https://api.github.com/repos/thenewboston-developers/Account-Manager | closed | [Desktop Windows] Loader should be bigger in size | design | **Bug Description**
Loader should be bigger in size
**Steps to Reproduce**
1. Go to any app window
2. See loader
**Expected behavior**
Loader should be bigger in size
**Actual behavior**
Loader looks too small
**Screenshots/Recordings**
**OS and Browser*
- OS: [Windows 7]
**Additional context**
App version : v1.0.0-alpha.16
**Account Number**
Your account number where the reward points for this bug bounty will be sent (pending review and approval).
[How to Create an Account](https://thenewboston.com/account-manager/create-an-account)
| 1.0 | [Desktop Windows] Loader should be bigger in size - **Bug Description**
Loader should be bigger in size
**Steps to Reproduce**
1. Go to any app window
2. See loader
**Expected behavior**
Loader should be bigger in size
**Actual behavior**
Loader looks too small
**Screenshots/Recordings**
**OS and Browser*
- OS: [Windows 7]
**Additional context**
App version : v1.0.0-alpha.16
**Account Number**
Your account number where the reward points for this bug bounty will be sent (pending review and approval).
[How to Create an Account](https://thenewboston.com/account-manager/create-an-account)
| design | loader should be bigger in size bug description loader should be bigger in size steps to reproduce go to any app window see loader expected behavior loader should be bigger in size actual behavior loader looks too small screenshots recordings os and browser os additional context app version alpha account number your account number where the reward points for this bug bounty will be sent pending review and approval | 1 |
291,901 | 25,184,537,550 | IssuesEvent | 2022-11-11 16:37:20 | redpanda-data/redpanda | https://api.github.com/repos/redpanda-data/redpanda | closed | Failure to wait until indexes_gone in TxAbortSnapshotTest.test_index_removal | kind/bug area/tests ci-failure area/transactions sev/high | https://buildkite.com/redpanda/redpanda/builds/16588#0183cfca-1bb1-4563-98f8-8e97bf4284b4
This is on ARM, reproduces reliably
```
Class: TxAbortSnapshotTest
Method: test_index_removal
```
```
TimeoutError('')
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/ducktape/tests/runner_client.py", line 135, in run
data = self.run_test()
File "/usr/local/lib/python3.10/dist-packages/ducktape/tests/runner_client.py", line 227, in run_test
return self.test_context.function(self.test)
File "/root/tests/rptest/services/cluster.py", line 35, in wrapped
r = f(self, *args, **kwargs)
File "/root/tests/rptest/tests/tx_abort_index_test.py", line 143, in test_index_removal
wait_until(indices_gone, timeout_sec=30, backoff_sec=1)
File "/usr/local/lib/python3.10/dist-packages/ducktape/utils/util.py", line 58, in wait_until
raise TimeoutError(err_msg() if callable(err_msg) else err_msg) from last_exception
ducktape.errors.TimeoutError
``` | 1.0 | Failure to wait until indexes_gone in TxAbortSnapshotTest.test_index_removal - https://buildkite.com/redpanda/redpanda/builds/16588#0183cfca-1bb1-4563-98f8-8e97bf4284b4
This is on ARM, reproduces reliably
```
Class: TxAbortSnapshotTest
Method: test_index_removal
```
```
TimeoutError('')
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/ducktape/tests/runner_client.py", line 135, in run
data = self.run_test()
File "/usr/local/lib/python3.10/dist-packages/ducktape/tests/runner_client.py", line 227, in run_test
return self.test_context.function(self.test)
File "/root/tests/rptest/services/cluster.py", line 35, in wrapped
r = f(self, *args, **kwargs)
File "/root/tests/rptest/tests/tx_abort_index_test.py", line 143, in test_index_removal
wait_until(indices_gone, timeout_sec=30, backoff_sec=1)
File "/usr/local/lib/python3.10/dist-packages/ducktape/utils/util.py", line 58, in wait_until
raise TimeoutError(err_msg() if callable(err_msg) else err_msg) from last_exception
ducktape.errors.TimeoutError
``` | non_design | failure to wait until indexes gone in txabortsnapshottest test index removal this is on arm reproduces reliably class txabortsnapshottest method test index removal timeouterror traceback most recent call last file usr local lib dist packages ducktape tests runner client py line in run data self run test file usr local lib dist packages ducktape tests runner client py line in run test return self test context function self test file root tests rptest services cluster py line in wrapped r f self args kwargs file root tests rptest tests tx abort index test py line in test index removal wait until indices gone timeout sec backoff sec file usr local lib dist packages ducktape utils util py line in wait until raise timeouterror err msg if callable err msg else err msg from last exception ducktape errors timeouterror | 0 |
4,023 | 2,713,421,796 | IssuesEvent | 2015-04-09 19:10:52 | ccowmu/whatistheplan.com | https://api.github.com/repos/ccowmu/whatistheplan.com | closed | Decide on standard tab width in source files | design decision | Oh, python
Our most practical choices are:
4 spaces (that's what cpg likes and has in his vimrc)
tab characters
2 spaces
8 spaces
If you want to do something weird like 7 spaces we can discuss it, but we'll probably laugh at you. | 1.0 | Decide on standard tab width in source files - Oh, python
Our most practical choices are:
4 spaces (that's what cpg likes and has in his vimrc)
tab characters
2 spaces
8 spaces
If you want to do something weird like 7 spaces we can discuss it, but we'll probably laugh at you. | design | decide on standard tab width in source files oh python our most practical choices are spaces that s what cpg likes and has in his vimrc tab characters spaces spaces if you want to do something weird like spaces we can discuss it but we ll probably laugh at you | 1 |
175,040 | 27,778,280,536 | IssuesEvent | 2023-03-16 18:53:10 | Expensify/App | https://api.github.com/repos/Expensify/App | closed | [HOLD for payment 2023-03-14] Implement better default avatars | Daily Internal Design Awaiting Payment | Note: This issue is part of the greater **[Implement Our New Branding in NewDot](https://github.com/Expensify/Expensify/issues/239140)** project.
**What is it:**
- Add a wider variety of default avatars in the app for users
- Use the first initial/number from the workspace name as the default workspace title along with a random color pairing
<img width="1333" alt="image" src="https://user-images.githubusercontent.com/2319350/200912891-db452ac4-2396-460d-997d-f3a9fa971ba4.png">
**Does it require a mini design doc:**
Yes
**Design finished:**
Yes
cc @GabiHExpensify
<details><summary>Upwork Automation - Do Not Edit</summary>
<ul>
<li>Upwork Job URL: https://www.upwork.com/jobs/~01136d72ed85b4e6cf</li>
<li>Upwork Job ID: 1625441221891223552</li>
<li>Last Price Increase: 2023-02-14</li>
</ul>
</details> | 1.0 | [HOLD for payment 2023-03-14] Implement better default avatars - Note: This issue is part of the greater **[Implement Our New Branding in NewDot](https://github.com/Expensify/Expensify/issues/239140)** project.
**What is it:**
- Add a wider variety of default avatars in the app for users
- Use the first initial/number from the workspace name as the default workspace title along with a random color pairing
<img width="1333" alt="image" src="https://user-images.githubusercontent.com/2319350/200912891-db452ac4-2396-460d-997d-f3a9fa971ba4.png">
**Does it require a mini design doc:**
Yes
**Design finished:**
Yes
cc @GabiHExpensify
<details><summary>Upwork Automation - Do Not Edit</summary>
<ul>
<li>Upwork Job URL: https://www.upwork.com/jobs/~01136d72ed85b4e6cf</li>
<li>Upwork Job ID: 1625441221891223552</li>
<li>Last Price Increase: 2023-02-14</li>
</ul>
</details> | design | implement better default avatars note this issue is part of the greater project what is it add a wider variety of default avatars in the app for users use the first initial number from the workspace name as the default workspace title along with a random color pairing img width alt image src does it require a mini design doc yes design finished yes cc gabihexpensify upwork automation do not edit upwork job url upwork job id last price increase | 1 |
68,685 | 8,319,431,340 | IssuesEvent | 2018-09-25 17:12:26 | cyberark/terraform-provider-conjur | https://api.github.com/repos/cyberark/terraform-provider-conjur | closed | Terraform has a Conjur Provider | component/terraform kind/XDD kind/design kind/epic | ETA for completion of this epic: 2018-09-21
Confidence level of ETA accuracy: High
## Context
HashiCorp's [Terraform](https://www.terraform.io/) is a widely-used tool used to manage infrastructure as code. Terraform manifests are written in [HCL](https://www.terraform.io/docs/configuration/syntax.html).
Terraform is extendable with [providers](https://www.terraform.io/docs/providers/index.html), which can declare their own resources. A Conjur provider does not yet exist. Secrets are often needed in Terraform manifests, so being able to fetch them from Conjur improves the security stance of Terraform.
### Current Capabilities
It is currently possible to fetch secrets from Conjur within Terraform by injecting them via environment variables. This requires the use of `summon` and specially named environment variables. While this is possible, the goal of creating a Conjur provider is to provide a better experience.
In order to use `summon` + environment variables, the user running `terraform` must already be authenticated with Conjur.
Terraform's [`TF_VAR_name` syntax](https://www.terraform.io/docs/configuration/environment-variables.html#tf_var_name) allows a user to set Terraform variables via environment variables. To use Terraform with Summon, prefix the environment variable names in secrets.yml with `TF_VAR_`.
**secrets.yml**
```
TF_VAR_access_key: !var aws/dev/sys_powerful/access_key_id
TF_VAR_secret_key: !var aws/dev/sys_powerful/secret_access_key
```
**variables.tf**
```
variable "access_key" {} /* Variable pulled from TF_VAR_access_key environment variable */
variable "secret_key" {} /* Variable pulled from TF_VAR_secret_key environment variable */
```
Run Terraform with Summon:
```
summon terraform apply
```
## Objective
Provide a Terraform `conjur` provider with a `conjur_secret` resource that can be used to fetch secrets from a configured Conjur v5 instance.
We should also instruct customers on how to use rotation (and possible encryption) to handle [exposed secrets in plan files](https://github.com/hashicorp/terraform/issues/516).
## Original Epic Goal & Resources
### Initial support
When using Terraform, credentials will be able to be pulled out of Conjur.
This should mirror what HC currently implements as part of their Vault provider. Our provider will leverage rotation to remove credentials exposed.
- https://github.com/hashicorp/terraform/issues/516
- https://www.terraform.io/docs/extend/writing-custom-providers.html
- https://github.com/terraform-providers/terraform-provider-vault
### Terraform Provider Configuration
Prerequisite is a setup and configured Conjur instance. In order to configure the Terraform provider, configuration values can be included in the Terraform manifest, or can be loaded using the standard Conjur client configuration mechanisms (e.g. `~/.conjurrc`, environment variables, etc). Values specified in the configuration file take precedence over other values.
#### Policy For Examples
<insert policy file contents here>
#### Terraform Manifest Provider Configuration
```
provider "conjur" {
appliance_url = "http://localhost:8080" /* The Conjur appliance URL */
account = "quick-start" /* The Conjur account */
login = "admin" /* The Conjur authn login */
api_key = "3ahcddy39rcxzh3ggac4cwk3j2r8pqwdg33059y835ys2rh2kzs2a" /* The Conjur authn API key */
ssl_cert_path = "/etc/conjur.pem" /* The Conjur certificate file */
}
```
#### Environment Variable Provider Configuration
```
export CONJUR_APPLIANCE_URL="https://localhost:8080"
export CONJUR_ACCOUNT="quick-start"
export CONJUR_AUTHN_LOGIN="admin"
export CONJUR_AUTHN_API_KEY="3ahcddy39rcxzh3ggac4cwk3j2r8pqwdg33059y835ys2rh2kzs2a"
export CONJUR_CERT_FILE="/etc/conjur.pem"
```
And then within the Terraform manifest:
```
provider "conjur" {}
```
### Fetching Secrets Within Terraform
Secrets are dynamically fetched from the Conjur service and injected as variables into the Terraform manifest when used. They need to be defined within the Terraform manifest prior to use.
#### Declaring Conjur Sourced Variables
The variables need to be declared prior to use. They are declared like any other data variable with Terraform, using the path within Conjur for the name.
```
data "conjur_secret" "dbpass" {
name = "path/to/secret" /* The Conjur secret to fetch */
}
```
#### Using Variables
The data for the variable is extracted into data.<declared_path>.<declared_name>.value. This can be then tied to a Terraform output in order to be used. The 'sensitive' declaration of true will prevent the value from being printed to the console, but will not prevent it from showing up in .plan files or logs.
```
output "dbpass_output" {
value = "${data.conjur_secret.dbpass.value}" /* Extract the value from the declared variable */
sensitive = true /* Whether to log the value to the console when running */
}
```
### Full Terraform Manifest example
**main.tf**
```
provider "conjur" {
appliance_url = "http://localhost:8080" /* The Conjur appliance URL */
account = "quick-start" /* The Conjur account */
login = "admin" /* The Conjur authn login */
api_key = "3ahcddy39rcxzh3ggac4cwk3j2r8pqwdg33059y835ys2rh2kzs2a" /* The Conjur authn API key */
ssl_cert_path = "/etc/conjur.pem" /* The Conjur certificate file */
}
data "conjur_secret" "dbpass" {
name = "path/to/secret" /* The Conjur secret to fetch */
}
output "dbpass_output" {
value = "${data.conjur_secret.dbpass.value}" /* Extract the value from the declared variable */
sensitive = true /* Whether to log the value to the console when running */
}
```
## Additional Notes
* If any of the provided credentials change and are needed in any resources, `terraform apply` needs to be run so that the secrets are available.
---
- [x] Test Conjur v5 Enterprise w/ Jenkins pipeline - parent of #2
- [x] Add homebrew release - parent of #3
- [x] Document summon + terraform flow - parent of #4
- [x] Use a better, more interesting test policy - parent of #5
- [x] Is there a way to avoid the secrets ending up in state files? - parent of #6 (closed)
- [x] Document how to install this provider - parent of #11
- [x] The provider uses the API to load configuration - parent of #12
- [ ] A demo shows that the provider can be part of creating a Rails app - parent of #13
- [x] Provider should be documented on conjur.org - parent of #19
- [x] README is missing Authentication and Policy sections - parent of #20
_Copied from original issue: conjurinc/appliance#262_ | 1.0 | Terraform has a Conjur Provider - ETA for completion of this epic: 2018-09-21
Confidence level of ETA accuracy: High
## Context
HashiCorp's [Terraform](https://www.terraform.io/) is a widely-used tool used to manage infrastructure as code. Terraform manifests are written in [HCL](https://www.terraform.io/docs/configuration/syntax.html).
Terraform is extendable with [providers](https://www.terraform.io/docs/providers/index.html), which can declare their own resources. A Conjur provider does not yet exist. Secrets are often needed in Terraform manifests, so being able to fetch them from Conjur improves the security stance of Terraform.
### Current Capabilities
It is currently possible to fetch secrets from Conjur within Terraform by injecting them via environment variables. This requires the use of `summon` and specially named environment variables. While this is possible, the goal of creating a Conjur provider is to provide a better experience.
In order to use `summon` + environment variables, the user running `terraform` must already be authenticated with Conjur.
Terraform's [`TF_VAR_name` syntax](https://www.terraform.io/docs/configuration/environment-variables.html#tf_var_name) allows a user to set Terraform variables via environment variables. To use Terraform with Summon, prefix the environment variable names in secrets.yml with `TF_VAR_`.
**secrets.yml**
```
TF_VAR_access_key: !var aws/dev/sys_powerful/access_key_id
TF_VAR_secret_key: !var aws/dev/sys_powerful/secret_access_key
```
**variables.tf**
```
variable "access_key" {} /* Variable pulled from TF_VAR_access_key environment variable */
variable "secret_key" {} /* Variable pulled from TF_VAR_secret_key environment variable */
```
Run Terraform with Summon:
```
summon terraform apply
```
## Objective
Provide a Terraform `conjur` provider with a `conjur_secret` resource that can be used to fetch secrets from a configured Conjur v5 instance.
We should also instruct customers on how to use rotation (and possible encryption) to handle [exposed secrets in plan files](https://github.com/hashicorp/terraform/issues/516).
## Original Epic Goal & Resources
### Initial support
When using Terraform, credentials will be able to be pulled out of Conjur.
This should mirror what HC currently implements as part of their Vault provider. Our provider will leverage rotation to remove credentials exposed.
- https://github.com/hashicorp/terraform/issues/516
- https://www.terraform.io/docs/extend/writing-custom-providers.html
- https://github.com/terraform-providers/terraform-provider-vault
### Terraform Provider Configuration
Prerequisite is a setup and configured Conjur instance. In order to configure the Terraform provider, configuration values can be included in the Terraform manifest, or can be loaded using the standard Conjur client configuration mechanisms (e.g. `~/.conjurrc`, environment variables, etc). Values specified in the configuration file take precedence over other values.
#### Policy For Examples
<insert policy file contents here>
#### Terraform Manifest Provider Configuration
```
provider "conjur" {
appliance_url = "http://localhost:8080" /* The Conjur appliance URL */
account = "quick-start" /* The Conjur account */
login = "admin" /* The Conjur authn login */
api_key = "3ahcddy39rcxzh3ggac4cwk3j2r8pqwdg33059y835ys2rh2kzs2a" /* The Conjur authn API key */
ssl_cert_path = "/etc/conjur.pem" /* The Conjur certificate file */
}
```
#### Environment Variable Provider Configuration
```
export CONJUR_APPLIANCE_URL="https://localhost:8080"
export CONJUR_ACCOUNT="quick-start"
export CONJUR_AUTHN_LOGIN="admin"
export CONJUR_AUTHN_API_KEY="3ahcddy39rcxzh3ggac4cwk3j2r8pqwdg33059y835ys2rh2kzs2a"
export CONJUR_CERT_FILE="/etc/conjur.pem"
```
And then within the Terraform manifest:
```
provider "conjur" {}
```
### Fetching Secrets Within Terraform
Secrets are dynamically fetched from the Conjur service and injected as variables into the Terraform manifest when used. They need to be defined within the Terraform manifest prior to use.
#### Declaring Conjur Sourced Variables
The variables need to be declared prior to use. They are declared like any other data variable with Terraform, using the path within Conjur for the name.
```
data "conjur_secret" "dbpass" {
name = "path/to/secret" /* The Conjur secret to fetch */
}
```
#### Using Variables
The data for the variable is extracted into data.<declared_path>.<declared_name>.value. This can be then tied to a Terraform output in order to be used. The 'sensitive' declaration of true will prevent the value from being printed to the console, but will not prevent it from showing up in .plan files or logs.
```
output "dbpass_output" {
value = "${data.conjur_secret.dbpass.value}" /* Extract the value from the declared variable */
sensitive = true /* Whether to log the value to the console when running */
}
```
### Full Terraform Manifest example
**main.tf**
```
provider "conjur" {
appliance_url = "http://localhost:8080" /* The Conjur appliance URL */
account = "quick-start" /* The Conjur account */
login = "admin" /* The Conjur authn login */
api_key = "3ahcddy39rcxzh3ggac4cwk3j2r8pqwdg33059y835ys2rh2kzs2a" /* The Conjur authn API key */
ssl_cert_path = "/etc/conjur.pem" /* The Conjur certificate file */
}
data "conjur_secret" "dbpass" {
name = "path/to/secret" /* The Conjur secret to fetch */
}
output "dbpass_output" {
value = "${data.conjur_secret.dbpass.value}" /* Extract the value from the declared variable */
sensitive = true /* Whether to log the value to the console when running */
}
```
## Additional Notes
* If any of the provided credentials change and are needed in any resources, `terraform apply` needs to be run so that the secrets are available.
---
- [x] Test Conjur v5 Enterprise w/ Jenkins pipeline - parent of #2
- [x] Add homebrew release - parent of #3
- [x] Document summon + terraform flow - parent of #4
- [x] Use a better, more interesting test policy - parent of #5
- [x] Is there a way to avoid the secrets ending up in state files? - parent of #6 (closed)
- [x] Document how to install this provider - parent of #11
- [x] The provider uses the API to load configuration - parent of #12
- [ ] A demo shows that the provider can be part of creating a Rails app - parent of #13
- [x] Provider should be documented on conjur.org - parent of #19
- [x] README is missing Authentication and Policy sections - parent of #20
_Copied from original issue: conjurinc/appliance#262_ | design | terraform has a conjur provider eta for completion of this epic confidence level of eta accuracy high context hashicorp s is a widely used tool used to manage infrastructure as code terraform manifests are written in terraform is extendable with which can declare their own resources a conjur provider does not yet exist secrets are often needed in terraform manifests so being able to fetch them from conjur improves the security stance of terraform current capabilities it is currently possible to fetch secrets from conjur within terraform by injecting them via environment variables this requires the use of summon and specially named environment variables while this is possible the goal of creating a conjur provider is to provide a better experience in order to use summon environment variables the user running terraform must already be authenticated with conjur terraform s allows a user to set terraform variables via environment variables to use terraform with summon prefix the environment variable names in secrets yml with tf var secrets yml tf var access key var aws dev sys powerful access key id tf var secret key var aws dev sys powerful secret access key variables tf variable access key variable pulled from tf var access key environment variable variable secret key variable pulled from tf var secret key environment variable run terraform with summon summon terraform apply objective provide a terraform conjur provider with a conjur secret resource that can be used to fetch secrets from a configured conjur instance we should also instruct customers on how to use rotation and possible encryption to handle original epic goal resources initial support when using terraform credentials will be able to be pulled out of conjur this should mirror what hc currently implements as part of their vault provider our provider will leverage rotation to remove credentials exposed terraform provider configuration prerequisite is a setup and configured conjur instance in order to configure the terraform provider configuration values can be included in the terraform manifest or can be loaded using the standard conjur client configuration mechanisms e g conjurrc environment variables etc values specified in the configuration file take precedence over other values policy for examples terraform manifest provider configuration provider conjur appliance url the conjur appliance url account quick start the conjur account login admin the conjur authn login api key the conjur authn api key ssl cert path etc conjur pem the conjur certificate file environment variable provider configuration export conjur appliance url export conjur account quick start export conjur authn login admin export conjur authn api key export conjur cert file etc conjur pem and then within the terraform manifest provider conjur fetching secrets within terraform secrets are dynamically fetched from the conjur service and injected as variables into the terraform manifest when used they need to be defined within the terraform manifest prior to use declaring conjur sourced variables the variables need to be declared prior to use they are declared like any other data variable with terraform using the path within conjur for the name data conjur secret dbpass name path to secret the conjur secret to fetch using variables the data for the variable is extracted into data value this can be then tied to a terraform output in order to be used the sensitive declaration of true will prevent the value from being printed to the console but will not prevent it from showing up in plan files or logs output dbpass output value data conjur secret dbpass value extract the value from the declared variable sensitive true whether to log the value to the console when running full terraform manifest example main tf provider conjur appliance url the conjur appliance url account quick start the conjur account login admin the conjur authn login api key the conjur authn api key ssl cert path etc conjur pem the conjur certificate file data conjur secret dbpass name path to secret the conjur secret to fetch output dbpass output value data conjur secret dbpass value extract the value from the declared variable sensitive true whether to log the value to the console when running additional notes if any of the provided credentials change and are needed in any resources terraform apply needs to be run so that the secrets are available test conjur enterprise w jenkins pipeline parent of add homebrew release parent of document summon terraform flow parent of use a better more interesting test policy parent of is there a way to avoid the secrets ending up in state files parent of closed document how to install this provider parent of the provider uses the api to load configuration parent of a demo shows that the provider can be part of creating a rails app parent of provider should be documented on conjur org parent of readme is missing authentication and policy sections parent of copied from original issue conjurinc appliance | 1 |
750,426 | 26,201,640,370 | IssuesEvent | 2023-01-03 18:03:08 | Kong/kubernetes-ingress-controller | https://api.github.com/repos/Kong/kubernetes-ingress-controller | closed | Feature proposal: add a flag to disable compression on kubeconfig | area/feature priority/low | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Problem Statement
When querying API server with a big amount (depending on size ~100s or ~1000s) of secrets the connection to API server times out.
### Proposed Solution
- Implement a feature/runtime flag that will disable compression on kubeconfig to minimize API processing
### Additional information
Related bug report #2382
### Open questions
- We still need to decide if we want to:
- disable compression on the whole client (as you've proposed in your diff)
- or disable it only for the initial list and the recreate the client with the already established defaults (compression enabled)
- Whether this should be done as a feature or runtime flag
### Acceptance Criteria
- [ ] As a user I should be able to toggle a flag which will allow me to disable compression when issuing calls to API server | 1.0 | Feature proposal: add a flag to disable compression on kubeconfig - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Problem Statement
When querying API server with a big amount (depending on size ~100s or ~1000s) of secrets the connection to API server times out.
### Proposed Solution
- Implement a feature/runtime flag that will disable compression on kubeconfig to minimize API processing
### Additional information
Related bug report #2382
### Open questions
- We still need to decide if we want to:
- disable compression on the whole client (as you've proposed in your diff)
- or disable it only for the initial list and the recreate the client with the already established defaults (compression enabled)
- Whether this should be done as a feature or runtime flag
### Acceptance Criteria
- [ ] As a user I should be able to toggle a flag which will allow me to disable compression when issuing calls to API server | non_design | feature proposal add a flag to disable compression on kubeconfig is there an existing issue for this i have searched the existing issues problem statement when querying api server with a big amount depending on size or of secrets the connection to api server times out proposed solution implement a feature runtime flag that will disable compression on kubeconfig to minimize api processing additional information related bug report open questions we still need to decide if we want to disable compression on the whole client as you ve proposed in your diff or disable it only for the initial list and the recreate the client with the already established defaults compression enabled whether this should be done as a feature or runtime flag acceptance criteria as a user i should be able to toggle a flag which will allow me to disable compression when issuing calls to api server | 0 |
177,587 | 28,596,820,165 | IssuesEvent | 2023-04-23 00:03:09 | helpwave/web | https://api.github.com/repos/helpwave/web | closed | Dashboard Page | priority:high tasks design-in-progress | Obviously we need to introduce some new components:
- [x] FeatureBlock
- [x] #254
- [x] TwoColumnLayout (#167 + icon: 5% top) | 1.0 | Dashboard Page - Obviously we need to introduce some new components:
- [x] FeatureBlock
- [x] #254
- [x] TwoColumnLayout (#167 + icon: 5% top) | design | dashboard page obviously we need to introduce some new components featureblock twocolumnlayout icon top | 1 |
44,120 | 17,835,675,863 | IssuesEvent | 2021-09-03 00:27:42 | Azure/azure-cli | https://api.github.com/repos/Azure/azure-cli | closed | Azure Portal CLI error when trying to disable web app auto-swap | Web Apps Service Attention | Hi everyone!
I'm getting this error when trying to disable an auto-swap on Web App using Portal CLI.
What I'm trying to do is:
az webapp deployment slot auto-swap --name <name> --resource-group <resourcegroup> --slot <slot> --disable
**Command Name**
`az webapp deployment slot auto-swap`
**Errors:**
```
The command failed with an unexpected error. Here is the traceback:
Unable to build a model: Unable to deserialize to object: type, AttributeError: 'str' object has no attribute 'get', DeserializationError: Unable to deserialize to object: type, AttributeError: 'str' object has no attribute 'get'
Traceback (most recent call last):
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1428, in _deserialize
found_value = key_extractor(attr, attr_desc, data)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1193, in rest_key_case_insensitive_extractor
return attribute_key_case_insensitive_extractor(key, None, working_data)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1222, in attribute_key_case_insensitive_extractor
return data.get(found_key)
AttributeError: 'str' object has no attribute 'get'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 620, in body
data = deserializer._deserialize(data_type, data)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1446, in _deserialize
raise_with_traceback(DeserializationError, msg, err)
File "/opt/az/lib/python3.6/site-packages/msrest/exceptions.py", line 51, in raise_with_traceback
raise error.with_traceback(exc_traceback)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1428, in _deserialize
found_value = key_extractor(attr, attr_desc, data)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1193, in rest_key_case_insensitive_extractor
return attribute_key_case_insensitive_extractor(key, None, working_data)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1222, in attribute_key_case_insensitive_extractor
return data.get(found_key)
msrest.exceptions.DeserializationError: Unable to deserialize to object: type, AttributeError: 'str' object has no attribute 'get'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 231, in invoke
cmd_result = self.invocation.execute(args)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 657, in execute
raise ex
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 720, in _run_jobs_serially
results.append(self._run_job(expanded_arg, cmd_copy))
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 691, in _run_job
result = cmd_copy(params)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 328, in __call__
return self.handler(*args, **kwargs)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
return op(**command_args)
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/custom.py", line 2152, in config_slot_auto_swap
return client.web_apps.update_configuration_slot(resource_group_name, webapp, site_config, slot)
File "/opt/az/lib/python3.6/site-packages/azure/mgmt/web/v2020_09_01/operations/_web_apps_operations.py", line 14737, in update_configuration_slot
body_content = self._serialize.body(site_config, 'SiteConfigResource')
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 623, in body
SerializationError, "Unable to build a model: "+str(err), err)
File "/opt/az/lib/python3.6/site-packages/msrest/exceptions.py", line 51, in raise_with_traceback
raise error.with_traceback(exc_traceback)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 620, in body
data = deserializer._deserialize(data_type, data)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1446, in _deserialize
raise_with_traceback(DeserializationError, msg, err)
File "/opt/az/lib/python3.6/site-packages/msrest/exceptions.py", line 51, in raise_with_traceback
raise error.with_traceback(exc_traceback)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1428, in _deserialize
found_value = key_extractor(attr, attr_desc, data)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1193, in rest_key_case_insensitive_extractor
return attribute_key_case_insensitive_extractor(key, None, working_data)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1222, in attribute_key_case_insensitive_extractor
return data.get(found_key)
msrest.exceptions.SerializationError: Unable to build a model: Unable to deserialize to object: type, AttributeError: 'str' object has no attribute 'get', DeserializationError: Unable to deserialize to object: type, AttributeError: 'str' object has no attribute 'get'
```
## To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
- _Put any pre-requisite steps here..._
- `az webapp deployment slot auto-swap --name {} --resource-group {} --slot {} --disable`
## Expected Behavior
## Environment Summary
```
Linux-5.4.0-1055-azure-x86_64-with-debian-10.2 (Cloud Shell)
Python 3.6.10
Installer: DEB
azure-cli 2.26.0 *
Extensions:
ai-examples 0.2.5
ssh 0.1.5
```
## Additional Context
<!--Please don't remove this:-->
<!--auto-generated-->
| 1.0 | Azure Portal CLI error when trying to disable web app auto-swap - Hi everyone!
I'm getting this error when trying to disable an auto-swap on Web App using Portal CLI.
What I'm trying to do is:
az webapp deployment slot auto-swap --name <name> --resource-group <resourcegroup> --slot <slot> --disable
**Command Name**
`az webapp deployment slot auto-swap`
**Errors:**
```
The command failed with an unexpected error. Here is the traceback:
Unable to build a model: Unable to deserialize to object: type, AttributeError: 'str' object has no attribute 'get', DeserializationError: Unable to deserialize to object: type, AttributeError: 'str' object has no attribute 'get'
Traceback (most recent call last):
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1428, in _deserialize
found_value = key_extractor(attr, attr_desc, data)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1193, in rest_key_case_insensitive_extractor
return attribute_key_case_insensitive_extractor(key, None, working_data)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1222, in attribute_key_case_insensitive_extractor
return data.get(found_key)
AttributeError: 'str' object has no attribute 'get'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 620, in body
data = deserializer._deserialize(data_type, data)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1446, in _deserialize
raise_with_traceback(DeserializationError, msg, err)
File "/opt/az/lib/python3.6/site-packages/msrest/exceptions.py", line 51, in raise_with_traceback
raise error.with_traceback(exc_traceback)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1428, in _deserialize
found_value = key_extractor(attr, attr_desc, data)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1193, in rest_key_case_insensitive_extractor
return attribute_key_case_insensitive_extractor(key, None, working_data)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1222, in attribute_key_case_insensitive_extractor
return data.get(found_key)
msrest.exceptions.DeserializationError: Unable to deserialize to object: type, AttributeError: 'str' object has no attribute 'get'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 231, in invoke
cmd_result = self.invocation.execute(args)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 657, in execute
raise ex
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 720, in _run_jobs_serially
results.append(self._run_job(expanded_arg, cmd_copy))
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 691, in _run_job
result = cmd_copy(params)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 328, in __call__
return self.handler(*args, **kwargs)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
return op(**command_args)
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/custom.py", line 2152, in config_slot_auto_swap
return client.web_apps.update_configuration_slot(resource_group_name, webapp, site_config, slot)
File "/opt/az/lib/python3.6/site-packages/azure/mgmt/web/v2020_09_01/operations/_web_apps_operations.py", line 14737, in update_configuration_slot
body_content = self._serialize.body(site_config, 'SiteConfigResource')
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 623, in body
SerializationError, "Unable to build a model: "+str(err), err)
File "/opt/az/lib/python3.6/site-packages/msrest/exceptions.py", line 51, in raise_with_traceback
raise error.with_traceback(exc_traceback)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 620, in body
data = deserializer._deserialize(data_type, data)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1446, in _deserialize
raise_with_traceback(DeserializationError, msg, err)
File "/opt/az/lib/python3.6/site-packages/msrest/exceptions.py", line 51, in raise_with_traceback
raise error.with_traceback(exc_traceback)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1428, in _deserialize
found_value = key_extractor(attr, attr_desc, data)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1193, in rest_key_case_insensitive_extractor
return attribute_key_case_insensitive_extractor(key, None, working_data)
File "/opt/az/lib/python3.6/site-packages/msrest/serialization.py", line 1222, in attribute_key_case_insensitive_extractor
return data.get(found_key)
msrest.exceptions.SerializationError: Unable to build a model: Unable to deserialize to object: type, AttributeError: 'str' object has no attribute 'get', DeserializationError: Unable to deserialize to object: type, AttributeError: 'str' object has no attribute 'get'
```
## To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
- _Put any pre-requisite steps here..._
- `az webapp deployment slot auto-swap --name {} --resource-group {} --slot {} --disable`
## Expected Behavior
## Environment Summary
```
Linux-5.4.0-1055-azure-x86_64-with-debian-10.2 (Cloud Shell)
Python 3.6.10
Installer: DEB
azure-cli 2.26.0 *
Extensions:
ai-examples 0.2.5
ssh 0.1.5
```
## Additional Context
<!--Please don't remove this:-->
<!--auto-generated-->
| non_design | azure portal cli error when trying to disable web app auto swap hi everyone i m getting this error when trying to disable an auto swap on web app using portal cli what i m trying to do is az webapp deployment slot auto swap name resource group slot disable command name az webapp deployment slot auto swap errors the command failed with an unexpected error here is the traceback unable to build a model unable to deserialize to object type attributeerror str object has no attribute get deserializationerror unable to deserialize to object type attributeerror str object has no attribute get traceback most recent call last file opt az lib site packages msrest serialization py line in deserialize found value key extractor attr attr desc data file opt az lib site packages msrest serialization py line in rest key case insensitive extractor return attribute key case insensitive extractor key none working data file opt az lib site packages msrest serialization py line in attribute key case insensitive extractor return data get found key attributeerror str object has no attribute get during handling of the above exception another exception occurred traceback most recent call last file opt az lib site packages msrest serialization py line in body data deserializer deserialize data type data file opt az lib site packages msrest serialization py line in deserialize raise with traceback deserializationerror msg err file opt az lib site packages msrest exceptions py line in raise with traceback raise error with traceback exc traceback file opt az lib site packages msrest serialization py line in deserialize found value key extractor attr attr desc data file opt az lib site packages msrest serialization py line in rest key case insensitive extractor return attribute key case insensitive extractor key none working data file opt az lib site packages msrest serialization py line in attribute key case insensitive extractor return data get found key msrest exceptions deserializationerror unable to deserialize to object type attributeerror str object has no attribute get during handling of the above exception another exception occurred traceback most recent call last file opt az lib site packages knack cli py line in invoke cmd result self invocation execute args file opt az lib site packages azure cli core commands init py line in execute raise ex file opt az lib site packages azure cli core commands init py line in run jobs serially results append self run job expanded arg cmd copy file opt az lib site packages azure cli core commands init py line in run job result cmd copy params file opt az lib site packages azure cli core commands init py line in call return self handler args kwargs file opt az lib site packages azure cli core commands command operation py line in handler return op command args file opt az lib site packages azure cli command modules appservice custom py line in config slot auto swap return client web apps update configuration slot resource group name webapp site config slot file opt az lib site packages azure mgmt web operations web apps operations py line in update configuration slot body content self serialize body site config siteconfigresource file opt az lib site packages msrest serialization py line in body serializationerror unable to build a model str err err file opt az lib site packages msrest exceptions py line in raise with traceback raise error with traceback exc traceback file opt az lib site packages msrest serialization py line in body data deserializer deserialize data type data file opt az lib site packages msrest serialization py line in deserialize raise with traceback deserializationerror msg err file opt az lib site packages msrest exceptions py line in raise with traceback raise error with traceback exc traceback file opt az lib site packages msrest serialization py line in deserialize found value key extractor attr attr desc data file opt az lib site packages msrest serialization py line in rest key case insensitive extractor return attribute key case insensitive extractor key none working data file opt az lib site packages msrest serialization py line in attribute key case insensitive extractor return data get found key msrest exceptions serializationerror unable to build a model unable to deserialize to object type attributeerror str object has no attribute get deserializationerror unable to deserialize to object type attributeerror str object has no attribute get to reproduce steps to reproduce the behavior note that argument values have been redacted as they may contain sensitive information put any pre requisite steps here az webapp deployment slot auto swap name resource group slot disable expected behavior environment summary linux azure with debian cloud shell python installer deb azure cli extensions ai examples ssh additional context | 0 |
63,298 | 7,714,352,797 | IssuesEvent | 2018-05-23 01:33:03 | Microsoft/TypeScript | https://api.github.com/repos/Microsoft/TypeScript | closed | Data type error | Design Limitation | url : http://localhost:4200/product/5
router: { path: 'products/:id', component: ProductDetailComponent }
| 1.0 | Data type error - url : http://localhost:4200/product/5
router: { path: 'products/:id', component: ProductDetailComponent }
| design | data type error url router path products id component productdetailcomponent | 1 |
38,408 | 4,955,063,028 | IssuesEvent | 2016-12-01 19:23:20 | OpenTreeMap/otm-core | https://api.github.com/repos/OpenTreeMap/otm-core | closed | On iPad in vertical mode, the species search box disappears | bug design low | May be linked to the logo being so large that it interferes with the search boxes.
| 1.0 | On iPad in vertical mode, the species search box disappears - May be linked to the logo being so large that it interferes with the search boxes.
| design | on ipad in vertical mode the species search box disappears may be linked to the logo being so large that it interferes with the search boxes | 1 |
162,914 | 25,716,306,530 | IssuesEvent | 2022-12-07 10:33:54 | Altinn/altinn-studio | https://api.github.com/repos/Altinn/altinn-studio | closed | Automatisk opprettelse av modell når utviklingen starter i ux-editor | kind/feature-request area/data-modeling area/ui-editor solution/studio/designer Epic status/duplicate ux kind/product-feature | Som tjenesteutvikler ønsker jeg at modellen til tjenesten automatisk blir opprettet når jeg starter med å lage brukergrensesnittet til tjenesten i ux-editor slik at jeg slipper å manuelt modellere modellen i etterkant og så koble denne til grensesnittet til tjenesten.
**Kommentar:**
Eks. legger til felt med forskjellige feltegenskaper (datatyper som f.eks. tekstfelt, nedtrekksliste osv., feltstørrelse, restriksjoner) og gir dem navn og ev. annen informasjon i ux-editor. I modell-editor må det opprettes en modell og metadata som speiler informasjonen lagt til i ux-editoren.
| 1.0 | Automatisk opprettelse av modell når utviklingen starter i ux-editor - Som tjenesteutvikler ønsker jeg at modellen til tjenesten automatisk blir opprettet når jeg starter med å lage brukergrensesnittet til tjenesten i ux-editor slik at jeg slipper å manuelt modellere modellen i etterkant og så koble denne til grensesnittet til tjenesten.
**Kommentar:**
Eks. legger til felt med forskjellige feltegenskaper (datatyper som f.eks. tekstfelt, nedtrekksliste osv., feltstørrelse, restriksjoner) og gir dem navn og ev. annen informasjon i ux-editor. I modell-editor må det opprettes en modell og metadata som speiler informasjonen lagt til i ux-editoren.
| design | automatisk opprettelse av modell når utviklingen starter i ux editor som tjenesteutvikler ønsker jeg at modellen til tjenesten automatisk blir opprettet når jeg starter med å lage brukergrensesnittet til tjenesten i ux editor slik at jeg slipper å manuelt modellere modellen i etterkant og så koble denne til grensesnittet til tjenesten kommentar eks legger til felt med forskjellige feltegenskaper datatyper som f eks tekstfelt nedtrekksliste osv feltstørrelse restriksjoner og gir dem navn og ev annen informasjon i ux editor i modell editor må det opprettes en modell og metadata som speiler informasjonen lagt til i ux editoren | 1 |
671,185 | 22,747,163,733 | IssuesEvent | 2022-07-07 10:09:27 | paratestphp/paratest | https://api.github.com/repos/paratestphp/paratest | closed | Feature request: Support phpunit's --testdox option | enhancement priority backlog | Feature request: Support phpunit's --testdox option
It will be nice to see the info about the current test(s) which are bieng run. | 1.0 | Feature request: Support phpunit's --testdox option - Feature request: Support phpunit's --testdox option
It will be nice to see the info about the current test(s) which are bieng run. | non_design | feature request support phpunit s testdox option feature request support phpunit s testdox option it will be nice to see the info about the current test s which are bieng run | 0 |
368,212 | 10,868,086,579 | IssuesEvent | 2019-11-15 02:21:24 | scalableinternetservices/whispr | https://api.github.com/repos/scalableinternetservices/whispr | closed | Fix How Providers are Associated with Users | bug enhancement high priority | Currently, it seems like all users are automatically associated with themselves, and any provider that exists. The process should flow like this:
1. User is presented with a list of all providers. Can select them as he/she pleases.
2. User can edit their selections at any time via their profile.
3. Providers can search for users, and request access.
a. Users will be able to see incoming requests, and approve/reject them. If approved, they'll be able to be managed via the profile exactly as if the user had sought them out to start. | 1.0 | Fix How Providers are Associated with Users - Currently, it seems like all users are automatically associated with themselves, and any provider that exists. The process should flow like this:
1. User is presented with a list of all providers. Can select them as he/she pleases.
2. User can edit their selections at any time via their profile.
3. Providers can search for users, and request access.
a. Users will be able to see incoming requests, and approve/reject them. If approved, they'll be able to be managed via the profile exactly as if the user had sought them out to start. | non_design | fix how providers are associated with users currently it seems like all users are automatically associated with themselves and any provider that exists the process should flow like this user is presented with a list of all providers can select them as he she pleases user can edit their selections at any time via their profile providers can search for users and request access a users will be able to see incoming requests and approve reject them if approved they ll be able to be managed via the profile exactly as if the user had sought them out to start | 0 |
30,631 | 24,951,636,168 | IssuesEvent | 2022-11-01 07:54:58 | Altinn/altinn-platform | https://api.github.com/repos/Altinn/altinn-platform | opened | Set up and verify app cluster for NKOM - NASJONAL KOMMUNIKASJONSMYNDIGHET (Test) | solution/apps ops/infrastructure | Description
Set up app cluster for NKOM Test
Infrastructure tasks
- [ ] Prepare subscription for NKOM test and production @Herskis
- Rename reserved subscriptions and grant "Contributor" and "User Access Administrator" permissions to "Altinn Apps Terraform".
- [ ] Create AD-groups for NKOM @Herskis
- [ ] Prepare pipeline for NKOM test
- [ ] Run pipeline for NKOM test
- [ ] Create and add access token certificate
- [ ] Add dns record for NKOM cluster @Herskis
Acceptance criteria
- [ ] An application is successfully instantiated and submitted.
- [ ] Instance is successfully cleaned up: guid
Development tasks
- [ ] Give NKOM rights to deploy to Test on cdn
- [ ] Create and deploy app to NKOM for NKOM
- [ ] Create slack-channel for NKOM
- [ ] Notfify that cluster is ready in slack
- [ ] Create scopes in Maskinporten @SandGrainOne
- [ ] Clean up testdata.
- [ ] Complete confirm+ hard delete instance
- [ ] Delete deployment + resources from cluster
- [ ] Delete repository from gitea | 1.0 | Set up and verify app cluster for NKOM - NASJONAL KOMMUNIKASJONSMYNDIGHET (Test) - Description
Set up app cluster for NKOM Test
Infrastructure tasks
- [ ] Prepare subscription for NKOM test and production @Herskis
- Rename reserved subscriptions and grant "Contributor" and "User Access Administrator" permissions to "Altinn Apps Terraform".
- [ ] Create AD-groups for NKOM @Herskis
- [ ] Prepare pipeline for NKOM test
- [ ] Run pipeline for NKOM test
- [ ] Create and add access token certificate
- [ ] Add dns record for NKOM cluster @Herskis
Acceptance criteria
- [ ] An application is successfully instantiated and submitted.
- [ ] Instance is successfully cleaned up: guid
Development tasks
- [ ] Give NKOM rights to deploy to Test on cdn
- [ ] Create and deploy app to NKOM for NKOM
- [ ] Create slack-channel for NKOM
- [ ] Notfify that cluster is ready in slack
- [ ] Create scopes in Maskinporten @SandGrainOne
- [ ] Clean up testdata.
- [ ] Complete confirm+ hard delete instance
- [ ] Delete deployment + resources from cluster
- [ ] Delete repository from gitea | non_design | set up and verify app cluster for nkom nasjonal kommunikasjonsmyndighet test description set up app cluster for nkom test infrastructure tasks prepare subscription for nkom test and production herskis rename reserved subscriptions and grant contributor and user access administrator permissions to altinn apps terraform create ad groups for nkom herskis prepare pipeline for nkom test run pipeline for nkom test create and add access token certificate add dns record for nkom cluster herskis acceptance criteria an application is successfully instantiated and submitted instance is successfully cleaned up guid development tasks give nkom rights to deploy to test on cdn create and deploy app to nkom for nkom create slack channel for nkom notfify that cluster is ready in slack create scopes in maskinporten sandgrainone clean up testdata complete confirm hard delete instance delete deployment resources from cluster delete repository from gitea | 0 |
119,118 | 15,415,218,134 | IssuesEvent | 2021-03-05 02:05:22 | alexthompson207/overlook | https://api.github.com/repos/alexthompson207/overlook | opened | Build/Design Login Page for Guest/Manager | design/accessibility new feature | Using my wireframe, design login view for both Guest and Manager | 1.0 | Build/Design Login Page for Guest/Manager - Using my wireframe, design login view for both Guest and Manager | design | build design login page for guest manager using my wireframe design login view for both guest and manager | 1 |
600,199 | 18,291,472,736 | IssuesEvent | 2021-10-05 15:40:38 | microsoft/CSS-Exchange | https://api.github.com/repos/microsoft/CSS-Exchange | closed | [Work Item] Improve PageFile object logic | Work Item High Priority Health Checker | **Describe the work**
Currently only provide if auto page is set or not. Currently not doing that even correctly when multiple page files are detected.
Look at creating a new view for this:
```
Page File:
Location Size
---------- -----
c:\pagefile.sys 32778
```
This will be a list for each of the page files, providing a new `Out-Columns` view. Where `Size` is `0` automatic system manage is set and is incorrect and additional wording is provided. Same goes if multiple page files are detected.
| 1.0 | [Work Item] Improve PageFile object logic - **Describe the work**
Currently only provide if auto page is set or not. Currently not doing that even correctly when multiple page files are detected.
Look at creating a new view for this:
```
Page File:
Location Size
---------- -----
c:\pagefile.sys 32778
```
This will be a list for each of the page files, providing a new `Out-Columns` view. Where `Size` is `0` automatic system manage is set and is incorrect and additional wording is provided. Same goes if multiple page files are detected.
| non_design | improve pagefile object logic describe the work currently only provide if auto page is set or not currently not doing that even correctly when multiple page files are detected look at creating a new view for this page file location size c pagefile sys this will be a list for each of the page files providing a new out columns view where size is automatic system manage is set and is incorrect and additional wording is provided same goes if multiple page files are detected | 0 |
86,980 | 10,855,756,317 | IssuesEvent | 2019-11-13 19:06:03 | The-Squadratics/openMRS_security_project | https://api.github.com/repos/The-Squadratics/openMRS_security_project | closed | Designing for SSE - Task 3 - Threat Modal Analysis | Design | ### Designing for SSE - Task 3 - Threat Modal Analysis
The intent of this issue is to examine assigned identified threats and document mitigation strategies for those threats
### Deliverables
1. Document mitigations for the assigned identified threats. | 1.0 | Designing for SSE - Task 3 - Threat Modal Analysis - ### Designing for SSE - Task 3 - Threat Modal Analysis
The intent of this issue is to examine assigned identified threats and document mitigation strategies for those threats
### Deliverables
1. Document mitigations for the assigned identified threats. | design | designing for sse task threat modal analysis designing for sse task threat modal analysis the intent of this issue is to examine assigned identified threats and document mitigation strategies for those threats deliverables document mitigations for the assigned identified threats | 1 |
74,392 | 7,422,572,241 | IssuesEvent | 2018-03-23 00:02:47 | kubeflow/tf-operator | https://api.github.com/repos/kubeflow/tf-operator | closed | [test] All log is 404 in argo | area/testing kind/e2e-test-failure kind/enhancement priority/p1 | http://testing-argo.kubeflow.org/workflows/kubeflow-test-infra/kubeflow-tf-operator-presubmit-tfjob-e2e-492-b317aef-225-99c4?tab=workflow&nodeId=kubeflow-tf-operator-presubmit-tfjob-e2e-492-b317aef-225-99c4-3605379172&sidePanel=logs%3Akubeflow-tf-operator-presubmit-tfjob-e2e-492-b317aef-225-99c4-3605379172%3Amain
The log of element in argo DAG is 404 although the element is succeeded
```
{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods \"kubeflow-tf-operator-presubmit-tfjob-e2e-492-b317aef-225-99c4-3605379172\" not found","r
eason":"NotFound","details":{"name":"kubeflow-tf-operator-presubmit-tfjob-e2e-492-b317aef-225-99c4-3605379172","kind":"pods"},"code":404}
```
| 2.0 | [test] All log is 404 in argo - http://testing-argo.kubeflow.org/workflows/kubeflow-test-infra/kubeflow-tf-operator-presubmit-tfjob-e2e-492-b317aef-225-99c4?tab=workflow&nodeId=kubeflow-tf-operator-presubmit-tfjob-e2e-492-b317aef-225-99c4-3605379172&sidePanel=logs%3Akubeflow-tf-operator-presubmit-tfjob-e2e-492-b317aef-225-99c4-3605379172%3Amain
The log of element in argo DAG is 404 although the element is succeeded
```
{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods \"kubeflow-tf-operator-presubmit-tfjob-e2e-492-b317aef-225-99c4-3605379172\" not found","r
eason":"NotFound","details":{"name":"kubeflow-tf-operator-presubmit-tfjob-e2e-492-b317aef-225-99c4-3605379172","kind":"pods"},"code":404}
```
| non_design | all log is in argo the log of element in argo dag is although the element is succeeded kind status apiversion metadata status failure message pods kubeflow tf operator presubmit tfjob not found r eason notfound details name kubeflow tf operator presubmit tfjob kind pods code | 0 |
315,993 | 9,634,660,419 | IssuesEvent | 2019-05-15 21:53:39 | coding-eval-platform/executor-service | https://api.github.com/repos/coding-eval-platform/executor-service | closed | Timeout only for running step | Enhancement Priority: High | Separate running code into phases
- Copy code + compile
- Run code
The timeout should only be taken into account for the "Run code" phase | 1.0 | Timeout only for running step - Separate running code into phases
- Copy code + compile
- Run code
The timeout should only be taken into account for the "Run code" phase | non_design | timeout only for running step separate running code into phases copy code compile run code the timeout should only be taken into account for the run code phase | 0 |
72,180 | 8,709,984,129 | IssuesEvent | 2018-12-06 15:21:06 | johns2s/johndo | https://api.github.com/repos/johns2s/johndo | closed | UI fixes | design enhancement low priority | Some little niggles like "Task Name" vs "Task Title". Decide on terminology. Also, Settings page usually has small text as a title for text <input> but password change field is referred to as "Account Details". Maybe add a new header size??? | 1.0 | UI fixes - Some little niggles like "Task Name" vs "Task Title". Decide on terminology. Also, Settings page usually has small text as a title for text <input> but password change field is referred to as "Account Details". Maybe add a new header size??? | design | ui fixes some little niggles like task name vs task title decide on terminology also settings page usually has small text as a title for text but password change field is referred to as account details maybe add a new header size | 1 |
43,972 | 5,722,976,791 | IssuesEvent | 2017-04-20 10:54:23 | IgniteUI/ignite-ui | https://api.github.com/repos/IgniteUI/ignite-ui | closed | [igNumericEditor] When you set a string value to numeric editor no exception is thrown. | numeric-editor severity: low status: by-design version: 17.1 | ### Description
When you set a string value to numeric editor no exception is thrown.
### Steps to reproduce
1. Create an editor with the following code:
`$("#editor").igNumericEditor();`
2. Run time set the value option or through the value method string "Hello"
### Result
No exception is thrown
### Expected result
An exception should be thrown
| 1.0 | [igNumericEditor] When you set a string value to numeric editor no exception is thrown. - ### Description
When you set a string value to numeric editor no exception is thrown.
### Steps to reproduce
1. Create an editor with the following code:
`$("#editor").igNumericEditor();`
2. Run time set the value option or through the value method string "Hello"
### Result
No exception is thrown
### Expected result
An exception should be thrown
| design | when you set a string value to numeric editor no exception is thrown description when you set a string value to numeric editor no exception is thrown steps to reproduce create an editor with the following code editor ignumericeditor run time set the value option or through the value method string hello result no exception is thrown expected result an exception should be thrown | 1 |
12,913 | 3,669,376,141 | IssuesEvent | 2016-02-21 06:15:07 | drdhaval2785/SanskritVerb | https://api.github.com/repos/drdhaval2785/SanskritVerb | opened | Round 2 started | Documentation | Once the whole exercise was over. Necessary corrections were made in the code.
These may have cause erstwhile correct forms to fail.
Therefore, trying a cursory testing named Round 2.
Will release the code at the end of round 1 of testing as a release version.
This is just for documentation. | 1.0 | Round 2 started - Once the whole exercise was over. Necessary corrections were made in the code.
These may have cause erstwhile correct forms to fail.
Therefore, trying a cursory testing named Round 2.
Will release the code at the end of round 1 of testing as a release version.
This is just for documentation. | non_design | round started once the whole exercise was over necessary corrections were made in the code these may have cause erstwhile correct forms to fail therefore trying a cursory testing named round will release the code at the end of round of testing as a release version this is just for documentation | 0 |
53,422 | 6,721,389,901 | IssuesEvent | 2017-10-16 11:32:13 | idris-lang/Idris-dev | https://api.github.com/repos/idris-lang/Idris-dev | closed | Incorrect behaviour when using 'singleton' and 'chr' | A-Confirmed C-Low Hanging Fruit G-C Backend S-Normal U-Library Design | I compiled and executed this code with the `c` backend using Idris 1.0
This bug doesn't happen in the REPL and I only see the issue when combing `singleton` and `chr`.
```
module main
main : IO ()
main = do
printLn "\x141"
printLn (chr 0x141)
printLn (singleton '\x141')
printLn (singleton (chr 0x141))
```
The output is this:
```
"\321"
'\321'
"\321"
"A"
```
However if you replace `x141` with `x1B1` the output is this:
```
"\433"
'\433'
"\433"
"\433"
```
I looked into it and whenever bit 8 is zero on the input integer, the integer is masked so that only the 8 least significant bits are used. So in the above example, `0x141` was changed to `0x041` which is the letter `A`, but `0x1B1` has bit 8 set to one so it doesn't happen. | 1.0 | Incorrect behaviour when using 'singleton' and 'chr' - I compiled and executed this code with the `c` backend using Idris 1.0
This bug doesn't happen in the REPL and I only see the issue when combing `singleton` and `chr`.
```
module main
main : IO ()
main = do
printLn "\x141"
printLn (chr 0x141)
printLn (singleton '\x141')
printLn (singleton (chr 0x141))
```
The output is this:
```
"\321"
'\321'
"\321"
"A"
```
However if you replace `x141` with `x1B1` the output is this:
```
"\433"
'\433'
"\433"
"\433"
```
I looked into it and whenever bit 8 is zero on the input integer, the integer is masked so that only the 8 least significant bits are used. So in the above example, `0x141` was changed to `0x041` which is the letter `A`, but `0x1B1` has bit 8 set to one so it doesn't happen. | design | incorrect behaviour when using singleton and chr i compiled and executed this code with the c backend using idris this bug doesn t happen in the repl and i only see the issue when combing singleton and chr module main main io main do println println chr println singleton println singleton chr the output is this a however if you replace with the output is this i looked into it and whenever bit is zero on the input integer the integer is masked so that only the least significant bits are used so in the above example was changed to which is the letter a but has bit set to one so it doesn t happen | 1 |
37,010 | 12,464,594,353 | IssuesEvent | 2020-05-28 12:44:58 | akka/akka | https://api.github.com/repos/akka/akka | closed | Support certificate rotation on Akka Remote mTLS | 1 - triaged t:security | Akka Remote's `SSLEngineProvider` only ships with a config-based implementation.
Certain deployment targets use more strict mTLS setups with rotation credentials. Akka Remote could include a `SSLEngineProvider` implementation that read from the credentials file location periodically to load new certificates/keys as they are provided. | True | Support certificate rotation on Akka Remote mTLS - Akka Remote's `SSLEngineProvider` only ships with a config-based implementation.
Certain deployment targets use more strict mTLS setups with rotation credentials. Akka Remote could include a `SSLEngineProvider` implementation that read from the credentials file location periodically to load new certificates/keys as they are provided. | non_design | support certificate rotation on akka remote mtls akka remote s sslengineprovider only ships with a config based implementation certain deployment targets use more strict mtls setups with rotation credentials akka remote could include a sslengineprovider implementation that read from the credentials file location periodically to load new certificates keys as they are provided | 0 |
15,817 | 9,629,496,652 | IssuesEvent | 2019-05-15 09:43:56 | MicrosoftDocs/windows-itpro-docs | https://api.github.com/repos/MicrosoftDocs/windows-itpro-docs | closed | Planningsheet has on 4. Active Directory 4a Windows server 2016? | assigned-to-author hello-for-business identity protection security | If I go for the hybrid with certificate trust (no 2016 DC's) there is no change for 4b. ? Do I need then the windows server 2016 schema? (It was already filled in)
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 5739fab2-c6db-a7a9-b0e7-2bf4b85912a7
* Version Independent ID: 82c58053-c1d7-d938-1b0f-f3f7f70ada3b
* Content: [Planning a Windows Hello for Business Deployment](https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-planning-guide#using-this-guide)
* Content Source: [windows/security/identity-protection/hello-for-business/hello-planning-guide.md](https://github.com/MicrosoftDocs/windows-itpro-docs/blob/master/windows/security/identity-protection/hello-for-business/hello-planning-guide.md)
* Product: **w10**
* GitHub Login: @MikeStephens-MS
* Microsoft Alias: **mstephen** | True | Planningsheet has on 4. Active Directory 4a Windows server 2016? - If I go for the hybrid with certificate trust (no 2016 DC's) there is no change for 4b. ? Do I need then the windows server 2016 schema? (It was already filled in)
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 5739fab2-c6db-a7a9-b0e7-2bf4b85912a7
* Version Independent ID: 82c58053-c1d7-d938-1b0f-f3f7f70ada3b
* Content: [Planning a Windows Hello for Business Deployment](https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-planning-guide#using-this-guide)
* Content Source: [windows/security/identity-protection/hello-for-business/hello-planning-guide.md](https://github.com/MicrosoftDocs/windows-itpro-docs/blob/master/windows/security/identity-protection/hello-for-business/hello-planning-guide.md)
* Product: **w10**
* GitHub Login: @MikeStephens-MS
* Microsoft Alias: **mstephen** | non_design | planningsheet has on active directory windows server if i go for the hybrid with certificate trust no dc s there is no change for do i need then the windows server schema it was already filled in document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source product github login mikestephens ms microsoft alias mstephen | 0 |
142,210 | 21,690,347,962 | IssuesEvent | 2022-05-09 14:51:50 | department-of-veterans-affairs/va.gov-team | https://api.github.com/repos/department-of-veterans-affairs/va.gov-team | closed | Platform Orientation Template [Nicole Rodriguez] | service-design | ## Welcome and Introduction
Welcome to the Veteran's Administration (VA) Veteran Facing Services (VFS) team!
As a new VFS team member, you will be working in the web ecosystem we call the VA.gov Platform (or "**The Platform,**" for short). The tasks on this list are designed to get you up to speed on the role of Platform, making it easier for you to do your job.
Because the VA is a huge organization that serves millions, the Platform it runs on is equally big, complex and multilayered. Most people find that even learning the basics for their own practice area entails a significant learning curve. The tasks on this checklist will help you acquire those basics as quickly and efficiently as possible.
## User Story
As a new VFS team member, I need to complete onboarding activities so I can successfully work on my project and support the VA.gov Platform.
## How to fill out this ticket
- [x] Add your github handle as the Assignee
- [x] Add your teams github label under Labels
- [x] Add your name to the ticket title
- [x] Complete the Onboarding Checklist below
- [x] Under **Get set up for your practice area,** you only need to complete the items for your role
- [x] You can close this ticket when all items are completed in the Onboarding Checklist and the Platform Checklist
## Onboarding Checklist
### Share your info with Platform
- [x] Complete the fields below:
- Name: Nicole Rodriguez
- Preferred pronouns (e.g. she/her): she/her
- Role: Managing Staff Designer
- Email: nicole.rodriguez@adhocteam.us
- Github handle: gopixelsgo
- Start date: 3/14/22
- VFS Team: VSP/Service Design
### General
- [x] Attend General Orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/general-orientation-for-va-gov-platform?month=2021-11))
- [x] Watch [VA.gov overview video](https://depo-platform-documentation.scrollhelp.site/getting-started/Platform-Orientation.1877344532.html#PlatformOrientation-Purpose)
- [x] Update your [Slack profile](https://depo-platform-documentation.scrollhelp.site/getting-started/Request-access-to-tools.969605215.html#Requestaccesstotools-Slack) with Program, Team, Role and Company
- [x] Review [Welcome](https://depo-platform-documentation.scrollhelp.site/getting-started/Welcome.1255276574.html) documentation
- [x] Review [Support Overview](https://depo-platform-documentation.scrollhelp.site/support/Support-overview.604012552.html) documentation
- [x] [Request Access to Tools](https://depo-platform-documentation.scrollhelp.site/getting-started/Request-access-to-tools.969605215.html)
- [x] Review the guidance on [Submitting a feature request](https://depo-platform-documentation.scrollhelp.site/support/Submitting-a-feature-request.1938915400.html)
### Norms and standards
- [x] Review the [Code of Conduct](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/policies-work-norms/code-of-conduct.md)
- [x] Review the [Norms for Communication](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/policies-work-norms/norms-communication.md)
- [x] Review [Orientation materials](https://depo-platform-documentation.scrollhelp.site/getting-started/Platform-Orientation.1877344532.html) on Platform Website
- [x] Review the [Guidelines for Working Safely in an Open Source Repo](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/policies-work-norms/sensitive-guidance.md)
- [x] Review the [Norms for Using Tools](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/policies-work-norms/norms-tools.md)
### Working on the platform
- [x] Review the [Platform Principles](https://vfs.atlassian.net/wiki/spaces/AP/pages/1391853669/Platform+Crew+Principles)
- [x] Review the [GitHub Markdown Cheatsheet](https://help.github.com/en/categories/writing-on-github) to learn the syntax for formatting documents in GitHub
- [x] Review the [Digital Modernization Strategy](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/va-gov-relaunch-2018/va-gov-strategy/digitalmodernizationstrategy.pdf)
- [x] Review the [Web Brand Consolidation](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/va-gov-relaunch-2018/va-gov-strategy/the-new-va.gov-briefing-2019-07.pdf) documentation
- [x] Review the [Collaboration Cycle](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/index.html) documentation on Platform Website
- [x] Review the [Collaboration Point Tracker](https://docs.google.com/spreadsheets/d/1OgPyEvUlNF6EnaYMFAXJkV6FKOvZnlPnbOQ2fAJ7W7A/edit#gid=1116695886)
### Get set up for your practice area
#### Designers & Researchers
- [x] Review [Design & Research Onboarding Documentation](https://design.va.gov/documentation/designers)
- [x] Review the [VA.gov Design System](https://design.va.gov/)
- [x] Review the [Research and Design Guide](https://depo-platform-documentation.scrollhelp.site/research-design/index.html) on Platform Website
- [x] Attend Design orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/design-orientation-for-va-gov-platform))
- [x] Attend Accessibility orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/accessibility-orientation-for-va-gov-platform))
#### Front-end Engineers
- [ ] Review [frontend developer documentation](https://depo-platform-documentation.scrollhelp.site/developer-docs/Frontend-developer-documentation.687931428.html) on Platform Website
- [ ] [Confirm that You Can Log In as a Test User](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/accessing-staging.md)
- [ ] Attend Front-end orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/front-end-orientation-for-va-gov-platform))
- [ ] Attend Analytics orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/analytics-orientation-for-va-gov-platform))
- [ ] Attend Accessibility orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/accessibility-orientation-for-va-gov-platform))
- [ ] Attend QA orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/qa-orientation-for-va-gov-platform))
#### Back-end Engineers
- [ ] Review [backend developer documentation](https://depo-platform-documentation.scrollhelp.site/developer-docs/Backend-developer-documentation.1886289964.html) on Platform Website
- [ ] [Confirm that You Can Log In as a Test User](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/accessing-staging.md)
- [ ] Attend Back-end orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/back-end-orientation-for-va-gov-platform))
- [ ] Attend QA orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/qa-orientation-for-va-gov-platform))
#### Product Managers
- [ ] Request PM intro with @ Shira Goodman in Slack
- [ ] Attend Analytics orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/analytics-orientation-for-va-gov-platform))
- [ ] Attend Accessibility orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/accessibility-orientation-for-va-gov-platform))
- [ ] Attend QA orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/qa-orientation-for-va-gov-platform))
### Off-boarding of teammates
- [x] Review [process for when a teammate leaves](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/contractoroffboarding.md)
## Platform Checklist
The items in this checklist are for Platform to complete. If you are ready to close the ticket and the Platform Checklist section has not been completed, please reach out to Platform via the guidance provided in [Getting help from Platform in Slack](https://depo-platform-documentation.scrollhelp.site/support/Getting-help-from-the-Platform-in-Slack.1439138197.html).
- [ ] New VFS Team member has been added to the [VFS Team Roster](https://docs.google.com/spreadsheets/d/11dpCJjhs007uC6CWJI6djy3OAvjB8rHB65m0Yj8HXIw/edit?folder=0ALlyxurHpUilUk9PVA#gid=0)
CC: @department-of-veterans-affairs/vsp-product-support
| 1.0 | Platform Orientation Template [Nicole Rodriguez] - ## Welcome and Introduction
Welcome to the Veteran's Administration (VA) Veteran Facing Services (VFS) team!
As a new VFS team member, you will be working in the web ecosystem we call the VA.gov Platform (or "**The Platform,**" for short). The tasks on this list are designed to get you up to speed on the role of Platform, making it easier for you to do your job.
Because the VA is a huge organization that serves millions, the Platform it runs on is equally big, complex and multilayered. Most people find that even learning the basics for their own practice area entails a significant learning curve. The tasks on this checklist will help you acquire those basics as quickly and efficiently as possible.
## User Story
As a new VFS team member, I need to complete onboarding activities so I can successfully work on my project and support the VA.gov Platform.
## How to fill out this ticket
- [x] Add your github handle as the Assignee
- [x] Add your teams github label under Labels
- [x] Add your name to the ticket title
- [x] Complete the Onboarding Checklist below
- [x] Under **Get set up for your practice area,** you only need to complete the items for your role
- [x] You can close this ticket when all items are completed in the Onboarding Checklist and the Platform Checklist
## Onboarding Checklist
### Share your info with Platform
- [x] Complete the fields below:
- Name: Nicole Rodriguez
- Preferred pronouns (e.g. she/her): she/her
- Role: Managing Staff Designer
- Email: nicole.rodriguez@adhocteam.us
- Github handle: gopixelsgo
- Start date: 3/14/22
- VFS Team: VSP/Service Design
### General
- [x] Attend General Orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/general-orientation-for-va-gov-platform?month=2021-11))
- [x] Watch [VA.gov overview video](https://depo-platform-documentation.scrollhelp.site/getting-started/Platform-Orientation.1877344532.html#PlatformOrientation-Purpose)
- [x] Update your [Slack profile](https://depo-platform-documentation.scrollhelp.site/getting-started/Request-access-to-tools.969605215.html#Requestaccesstotools-Slack) with Program, Team, Role and Company
- [x] Review [Welcome](https://depo-platform-documentation.scrollhelp.site/getting-started/Welcome.1255276574.html) documentation
- [x] Review [Support Overview](https://depo-platform-documentation.scrollhelp.site/support/Support-overview.604012552.html) documentation
- [x] [Request Access to Tools](https://depo-platform-documentation.scrollhelp.site/getting-started/Request-access-to-tools.969605215.html)
- [x] Review the guidance on [Submitting a feature request](https://depo-platform-documentation.scrollhelp.site/support/Submitting-a-feature-request.1938915400.html)
### Norms and standards
- [x] Review the [Code of Conduct](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/policies-work-norms/code-of-conduct.md)
- [x] Review the [Norms for Communication](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/policies-work-norms/norms-communication.md)
- [x] Review [Orientation materials](https://depo-platform-documentation.scrollhelp.site/getting-started/Platform-Orientation.1877344532.html) on Platform Website
- [x] Review the [Guidelines for Working Safely in an Open Source Repo](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/policies-work-norms/sensitive-guidance.md)
- [x] Review the [Norms for Using Tools](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/policies-work-norms/norms-tools.md)
### Working on the platform
- [x] Review the [Platform Principles](https://vfs.atlassian.net/wiki/spaces/AP/pages/1391853669/Platform+Crew+Principles)
- [x] Review the [GitHub Markdown Cheatsheet](https://help.github.com/en/categories/writing-on-github) to learn the syntax for formatting documents in GitHub
- [x] Review the [Digital Modernization Strategy](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/va-gov-relaunch-2018/va-gov-strategy/digitalmodernizationstrategy.pdf)
- [x] Review the [Web Brand Consolidation](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/va-gov-relaunch-2018/va-gov-strategy/the-new-va.gov-briefing-2019-07.pdf) documentation
- [x] Review the [Collaboration Cycle](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/index.html) documentation on Platform Website
- [x] Review the [Collaboration Point Tracker](https://docs.google.com/spreadsheets/d/1OgPyEvUlNF6EnaYMFAXJkV6FKOvZnlPnbOQ2fAJ7W7A/edit#gid=1116695886)
### Get set up for your practice area
#### Designers & Researchers
- [x] Review [Design & Research Onboarding Documentation](https://design.va.gov/documentation/designers)
- [x] Review the [VA.gov Design System](https://design.va.gov/)
- [x] Review the [Research and Design Guide](https://depo-platform-documentation.scrollhelp.site/research-design/index.html) on Platform Website
- [x] Attend Design orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/design-orientation-for-va-gov-platform))
- [x] Attend Accessibility orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/accessibility-orientation-for-va-gov-platform))
#### Front-end Engineers
- [ ] Review [frontend developer documentation](https://depo-platform-documentation.scrollhelp.site/developer-docs/Frontend-developer-documentation.687931428.html) on Platform Website
- [ ] [Confirm that You Can Log In as a Test User](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/accessing-staging.md)
- [ ] Attend Front-end orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/front-end-orientation-for-va-gov-platform))
- [ ] Attend Analytics orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/analytics-orientation-for-va-gov-platform))
- [ ] Attend Accessibility orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/accessibility-orientation-for-va-gov-platform))
- [ ] Attend QA orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/qa-orientation-for-va-gov-platform))
#### Back-end Engineers
- [ ] Review [backend developer documentation](https://depo-platform-documentation.scrollhelp.site/developer-docs/Backend-developer-documentation.1886289964.html) on Platform Website
- [ ] [Confirm that You Can Log In as a Test User](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/accessing-staging.md)
- [ ] Attend Back-end orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/back-end-orientation-for-va-gov-platform))
- [ ] Attend QA orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/qa-orientation-for-va-gov-platform))
#### Product Managers
- [ ] Request PM intro with @ Shira Goodman in Slack
- [ ] Attend Analytics orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/analytics-orientation-for-va-gov-platform))
- [ ] Attend Accessibility orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/accessibility-orientation-for-va-gov-platform))
- [ ] Attend QA orientation meeting ([schedule via Calendly](https://calendly.com/collaboration-cycle/qa-orientation-for-va-gov-platform))
### Off-boarding of teammates
- [x] Review [process for when a teammate leaves](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/contractoroffboarding.md)
## Platform Checklist
The items in this checklist are for Platform to complete. If you are ready to close the ticket and the Platform Checklist section has not been completed, please reach out to Platform via the guidance provided in [Getting help from Platform in Slack](https://depo-platform-documentation.scrollhelp.site/support/Getting-help-from-the-Platform-in-Slack.1439138197.html).
- [ ] New VFS Team member has been added to the [VFS Team Roster](https://docs.google.com/spreadsheets/d/11dpCJjhs007uC6CWJI6djy3OAvjB8rHB65m0Yj8HXIw/edit?folder=0ALlyxurHpUilUk9PVA#gid=0)
CC: @department-of-veterans-affairs/vsp-product-support
| design | platform orientation template welcome and introduction welcome to the veteran s administration va veteran facing services vfs team as a new vfs team member you will be working in the web ecosystem we call the va gov platform or the platform for short the tasks on this list are designed to get you up to speed on the role of platform making it easier for you to do your job because the va is a huge organization that serves millions the platform it runs on is equally big complex and multilayered most people find that even learning the basics for their own practice area entails a significant learning curve the tasks on this checklist will help you acquire those basics as quickly and efficiently as possible user story as a new vfs team member i need to complete onboarding activities so i can successfully work on my project and support the va gov platform how to fill out this ticket add your github handle as the assignee add your teams github label under labels add your name to the ticket title complete the onboarding checklist below under get set up for your practice area you only need to complete the items for your role you can close this ticket when all items are completed in the onboarding checklist and the platform checklist onboarding checklist share your info with platform complete the fields below name nicole rodriguez preferred pronouns e g she her she her role managing staff designer email nicole rodriguez adhocteam us github handle gopixelsgo start date vfs team vsp service design general attend general orientation meeting watch update your with program team role and company review documentation review documentation review the guidance on norms and standards review the review the review on platform website review the review the working on the platform review the review the to learn the syntax for formatting documents in github review the review the documentation review the documentation on platform website review the get set up for your practice area designers researchers review review the review the on platform website attend design orientation meeting attend accessibility orientation meeting front end engineers review on platform website attend front end orientation meeting attend analytics orientation meeting attend accessibility orientation meeting attend qa orientation meeting back end engineers review on platform website attend back end orientation meeting attend qa orientation meeting product managers request pm intro with shira goodman in slack attend analytics orientation meeting attend accessibility orientation meeting attend qa orientation meeting off boarding of teammates review platform checklist the items in this checklist are for platform to complete if you are ready to close the ticket and the platform checklist section has not been completed please reach out to platform via the guidance provided in new vfs team member has been added to the cc department of veterans affairs vsp product support | 1 |
160,214 | 12,505,868,470 | IssuesEvent | 2020-06-02 11:32:35 | aliasrobotics/RVD | https://api.github.com/repos/aliasrobotics/RVD | opened | Possible SQL injection vector through string-based query construction., /opt/ros_melodic_ws/src/ros_comm/rosbag/src/rosbag/migration.py:743 | bandit bug static analysis testing triage | ```yaml
{
"id": 1,
"title": "Possible SQL injection vector through string-based query construction., /opt/ros_melodic_ws/src/ros_comm/rosbag/src/rosbag/migration.py:743",
"type": "bug",
"description": "LOW confidence of MEDIUM severity bug. Possible SQL injection vector through string-based query construction. at /opt/ros_melodic_ws/src/ros_comm/rosbag/src/rosbag/migration.py:743 See links for more info on the bug.",
"cwe": "None",
"cve": "None",
"keywords": [
"bandit",
"bug",
"static analysis",
"testing",
"triage",
"bug"
],
"system": "",
"vendor": null,
"severity": {
"rvss-score": 0,
"rvss-vector": "",
"severity-description": "",
"cvss-score": 0,
"cvss-vector": ""
},
"links": "",
"flaw": {
"phase": "testing",
"specificity": "subject-specific",
"architectural-location": "application-specific",
"application": "N/A",
"subsystem": "N/A",
"package": "N/A",
"languages": "None",
"date-detected": "2020-06-02 (11:32)",
"detected-by": "Alias Robotics",
"detected-by-method": "testing static",
"date-reported": "2020-06-02 (11:32)",
"reported-by": "Alias Robotics",
"reported-by-relationship": "automatic",
"issue": "",
"reproducibility": "always",
"trace": "/opt/ros_melodic_ws/src/ros_comm/rosbag/src/rosbag/migration.py:743",
"reproduction": "See artifacts below (if available)",
"reproduction-image": ""
},
"exploitation": {
"description": "",
"exploitation-image": "",
"exploitation-vector": ""
},
"mitigation": {
"description": "",
"pull-request": "",
"date-mitigation": ""
}
}
``` | 1.0 | Possible SQL injection vector through string-based query construction., /opt/ros_melodic_ws/src/ros_comm/rosbag/src/rosbag/migration.py:743 - ```yaml
{
"id": 1,
"title": "Possible SQL injection vector through string-based query construction., /opt/ros_melodic_ws/src/ros_comm/rosbag/src/rosbag/migration.py:743",
"type": "bug",
"description": "LOW confidence of MEDIUM severity bug. Possible SQL injection vector through string-based query construction. at /opt/ros_melodic_ws/src/ros_comm/rosbag/src/rosbag/migration.py:743 See links for more info on the bug.",
"cwe": "None",
"cve": "None",
"keywords": [
"bandit",
"bug",
"static analysis",
"testing",
"triage",
"bug"
],
"system": "",
"vendor": null,
"severity": {
"rvss-score": 0,
"rvss-vector": "",
"severity-description": "",
"cvss-score": 0,
"cvss-vector": ""
},
"links": "",
"flaw": {
"phase": "testing",
"specificity": "subject-specific",
"architectural-location": "application-specific",
"application": "N/A",
"subsystem": "N/A",
"package": "N/A",
"languages": "None",
"date-detected": "2020-06-02 (11:32)",
"detected-by": "Alias Robotics",
"detected-by-method": "testing static",
"date-reported": "2020-06-02 (11:32)",
"reported-by": "Alias Robotics",
"reported-by-relationship": "automatic",
"issue": "",
"reproducibility": "always",
"trace": "/opt/ros_melodic_ws/src/ros_comm/rosbag/src/rosbag/migration.py:743",
"reproduction": "See artifacts below (if available)",
"reproduction-image": ""
},
"exploitation": {
"description": "",
"exploitation-image": "",
"exploitation-vector": ""
},
"mitigation": {
"description": "",
"pull-request": "",
"date-mitigation": ""
}
}
``` | non_design | possible sql injection vector through string based query construction opt ros melodic ws src ros comm rosbag src rosbag migration py yaml id title possible sql injection vector through string based query construction opt ros melodic ws src ros comm rosbag src rosbag migration py type bug description low confidence of medium severity bug possible sql injection vector through string based query construction at opt ros melodic ws src ros comm rosbag src rosbag migration py see links for more info on the bug cwe none cve none keywords bandit bug static analysis testing triage bug system vendor null severity rvss score rvss vector severity description cvss score cvss vector links flaw phase testing specificity subject specific architectural location application specific application n a subsystem n a package n a languages none date detected detected by alias robotics detected by method testing static date reported reported by alias robotics reported by relationship automatic issue reproducibility always trace opt ros melodic ws src ros comm rosbag src rosbag migration py reproduction see artifacts below if available reproduction image exploitation description exploitation image exploitation vector mitigation description pull request date mitigation | 0 |
36,079 | 4,713,431,030 | IssuesEvent | 2016-10-14 20:03:06 | elegantthemes/Divi-Beta | https://api.github.com/repos/elegantthemes/Divi-Beta | closed | Text Module :: Text Line Height value is changed from em to px on mobiles | BUG DESIGN SIGNOFF QUALITY ASSURED READY FOR REVIEW | ### Problem:
When you add a text module with some text, then try to set the line height to different values on desktops and mobiles you will see that the value em is changing to px which may create some confusion. You can manually change/fix it of course
| 1.0 | Text Module :: Text Line Height value is changed from em to px on mobiles - ### Problem:
When you add a text module with some text, then try to set the line height to different values on desktops and mobiles you will see that the value em is changing to px which may create some confusion. You can manually change/fix it of course
| design | text module text line height value is changed from em to px on mobiles problem when you add a text module with some text then try to set the line height to different values on desktops and mobiles you will see that the value em is changing to px which may create some confusion you can manually change fix it of course | 1 |
173,108 | 27,388,240,012 | IssuesEvent | 2023-02-28 14:41:46 | authelia/authelia | https://api.github.com/repos/authelia/authelia | opened | Cache user details for basic authentication | priority/4/normal type/feature status/needs-design | ### Description
For the `/api/verify?auth=basic` endpoint, caching user details would considerably increase the performance of the endpoint, as Authelia would not have to fetch details from an LDAP server or calculate expensive password hashes for every request.
The key could be derived from the user credentials. e.g. `hmac_sha256(username + password, secret_key)`
There are a couple security tradeoffs:
- The password hashing algorithm is downgraded. However, this hash would only live in memory.
- Brute force attacks are faster when the credentials are cached in memory. However, regulation policies could help protect against that.
The caching feature could be opt-in behind a setting. My one-factor apps use only long, randomly-generated passwords, so I'm comfortable with the tradeoffs.
### Use Case
Services like WebDAV still rely on basic auth, but the current implementation can make resource usage and request latencies impractically high.
### Details
_No response_
### Documentation
There is a [similar proposal](https://github.com/traefik/traefik/issues/7897) for Traefik.
### Pre-Submission Checklist
- [X] I agree to follow the [Code of Conduct](http://www.authelia.com/code-of-conduct)
- [X] I have checked for related issues and checked the documentation | 1.0 | Cache user details for basic authentication - ### Description
For the `/api/verify?auth=basic` endpoint, caching user details would considerably increase the performance of the endpoint, as Authelia would not have to fetch details from an LDAP server or calculate expensive password hashes for every request.
The key could be derived from the user credentials. e.g. `hmac_sha256(username + password, secret_key)`
There are a couple security tradeoffs:
- The password hashing algorithm is downgraded. However, this hash would only live in memory.
- Brute force attacks are faster when the credentials are cached in memory. However, regulation policies could help protect against that.
The caching feature could be opt-in behind a setting. My one-factor apps use only long, randomly-generated passwords, so I'm comfortable with the tradeoffs.
### Use Case
Services like WebDAV still rely on basic auth, but the current implementation can make resource usage and request latencies impractically high.
### Details
_No response_
### Documentation
There is a [similar proposal](https://github.com/traefik/traefik/issues/7897) for Traefik.
### Pre-Submission Checklist
- [X] I agree to follow the [Code of Conduct](http://www.authelia.com/code-of-conduct)
- [X] I have checked for related issues and checked the documentation | design | cache user details for basic authentication description for the api verify auth basic endpoint caching user details would considerably increase the performance of the endpoint as authelia would not have to fetch details from an ldap server or calculate expensive password hashes for every request the key could be derived from the user credentials e g hmac username password secret key there are a couple security tradeoffs the password hashing algorithm is downgraded however this hash would only live in memory brute force attacks are faster when the credentials are cached in memory however regulation policies could help protect against that the caching feature could be opt in behind a setting my one factor apps use only long randomly generated passwords so i m comfortable with the tradeoffs use case services like webdav still rely on basic auth but the current implementation can make resource usage and request latencies impractically high details no response documentation there is a for traefik pre submission checklist i agree to follow the i have checked for related issues and checked the documentation | 1 |
159,518 | 20,068,294,328 | IssuesEvent | 2022-02-04 01:08:27 | vlaship/spark | https://api.github.com/repos/vlaship/spark | opened | CVE-2022-23437 (Medium) detected in xercesImpl-2.9.1.jar | security vulnerability | ## CVE-2022-23437 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xercesImpl-2.9.1.jar</b></p></summary>
<p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the
Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI),
a complete framework for building parser components and configurations that is extremely
modular and easy to program.</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /root/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.9.1/7bc7e49ddfe4fb5f193ed37ecc96c12292c8ceb6/xercesImpl-2.9.1.jar,/root/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.9.1/7bc7e49ddfe4fb5f193ed37ecc96c12292c8ceb6/xercesImpl-2.9.1.jar</p>
<p>
Dependency Hierarchy:
- spark-sql_2.12-2.4.4.jar (Root Library)
- spark-core_2.12-2.4.4.jar
- hadoop-client-2.6.5.jar
- hadoop-hdfs-2.6.5.jar
- :x: **xercesImpl-2.9.1.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads. This causes, the XercesJ XML parser to wait in an infinite loop, which may sometimes consume system resources for prolonged duration. This vulnerability is present within XercesJ version 2.12.1 and the previous versions.
<p>Publish Date: 2022-01-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437>CVE-2022-23437</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-h65f-jvqw-m9fj">https://github.com/advisories/GHSA-h65f-jvqw-m9fj</a></p>
<p>Release Date: 2022-01-24</p>
<p>Fix Resolution: xerces:xercesImpl:2.12.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-23437 (Medium) detected in xercesImpl-2.9.1.jar - ## CVE-2022-23437 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xercesImpl-2.9.1.jar</b></p></summary>
<p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the
Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI),
a complete framework for building parser components and configurations that is extremely
modular and easy to program.</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /root/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.9.1/7bc7e49ddfe4fb5f193ed37ecc96c12292c8ceb6/xercesImpl-2.9.1.jar,/root/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.9.1/7bc7e49ddfe4fb5f193ed37ecc96c12292c8ceb6/xercesImpl-2.9.1.jar</p>
<p>
Dependency Hierarchy:
- spark-sql_2.12-2.4.4.jar (Root Library)
- spark-core_2.12-2.4.4.jar
- hadoop-client-2.6.5.jar
- hadoop-hdfs-2.6.5.jar
- :x: **xercesImpl-2.9.1.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads. This causes, the XercesJ XML parser to wait in an infinite loop, which may sometimes consume system resources for prolonged duration. This vulnerability is present within XercesJ version 2.12.1 and the previous versions.
<p>Publish Date: 2022-01-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437>CVE-2022-23437</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-h65f-jvqw-m9fj">https://github.com/advisories/GHSA-h65f-jvqw-m9fj</a></p>
<p>Release Date: 2022-01-24</p>
<p>Fix Resolution: xerces:xercesImpl:2.12.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve medium detected in xercesimpl jar cve medium severity vulnerability vulnerable library xercesimpl jar is the next generation of high performance fully compliant xml parsers in the apache xerces family this new version of xerces introduces the xerces native interface xni a complete framework for building parser components and configurations that is extremely modular and easy to program path to dependency file build gradle path to vulnerable library root gradle caches modules files xerces xercesimpl xercesimpl jar root gradle caches modules files xerces xercesimpl xercesimpl jar dependency hierarchy spark sql jar root library spark core jar hadoop client jar hadoop hdfs jar x xercesimpl jar vulnerable library vulnerability details there s a vulnerability within the apache xerces java xercesj xml parser when handling specially crafted xml document payloads this causes the xercesj xml parser to wait in an infinite loop which may sometimes consume system resources for prolonged duration this vulnerability is present within xercesj version and the previous versions 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 suggested fix type upgrade version origin a href release date fix resolution xerces xercesimpl step up your open source security game with whitesource | 0 |
162,211 | 6,148,889,689 | IssuesEvent | 2017-06-27 18:50:15 | opengovfoundation/madison | https://api.github.com/repos/opengovfoundation/madison | closed | Can't unlike/unflag a comment | Priority Type: Bug | Only way to remove a like is to flag the comment (and vice versa).
| 1.0 | Can't unlike/unflag a comment - Only way to remove a like is to flag the comment (and vice versa).
| non_design | can t unlike unflag a comment only way to remove a like is to flag the comment and vice versa | 0 |
169,862 | 26,868,842,283 | IssuesEvent | 2023-02-04 07:18:17 | Team-B1ND/dui-android | https://api.github.com/repos/Team-B1ND/dui-android | opened | DUI Input, Button, Select 등 사이즈 조정 | DESIGN 🎨 BUG 🐛 | ## 문제 상황
Font가 작아지면서 생각보다 Button, Input, Select의 여백이 커졌습니다.
## 원인
원래 좀 넓었던 여백이 폰트로 인해 더 넓어짐..
## 해결안
- [ ] Button, Input, Select Space을 40으로 줄여 디자인을 수정합니다.
- [ ] 공통되는 Padding 값을 개발합니다.
- [ ] Padding 값을 조정하여 적용합니다.
- [ ] Round 또한 10, 15 둘 중 명확하게 결정합니다. -> medium
## 기타 사항
디자이너가 필요합니다... | 1.0 | DUI Input, Button, Select 등 사이즈 조정 - ## 문제 상황
Font가 작아지면서 생각보다 Button, Input, Select의 여백이 커졌습니다.
## 원인
원래 좀 넓었던 여백이 폰트로 인해 더 넓어짐..
## 해결안
- [ ] Button, Input, Select Space을 40으로 줄여 디자인을 수정합니다.
- [ ] 공통되는 Padding 값을 개발합니다.
- [ ] Padding 값을 조정하여 적용합니다.
- [ ] Round 또한 10, 15 둘 중 명확하게 결정합니다. -> medium
## 기타 사항
디자이너가 필요합니다... | design | dui input button select 등 사이즈 조정 문제 상황 font가 작아지면서 생각보다 button input select의 여백이 커졌습니다 원인 원래 좀 넓었던 여백이 폰트로 인해 더 넓어짐 해결안 button input select space을 줄여 디자인을 수정합니다 공통되는 padding 값을 개발합니다 padding 값을 조정하여 적용합니다 round 또한 둘 중 명확하게 결정합니다 medium 기타 사항 디자이너가 필요합니다 | 1 |
145,594 | 22,738,991,066 | IssuesEvent | 2022-07-07 00:29:05 | microsoft/pyright | https://api.github.com/repos/microsoft/pyright | closed | Potentially incorrect type error for operator + for 2 lists | as designed |
**Code**
```
l1 = [1, 2, 3]
l2 = [[1, 2]]
l1 + l2
# output: [1, 2, 3, [1, 2]]
```
**Observed behavior**
Get type error: `Operator "+" not supported for types "list[int]" and "list[list[int]]"`
**Expected behavior**
Since this operation is allowed in python, perhaps there shouldn't be any type error.
The output list has type: `list[Union[list[int], int]]`.
| 1.0 | Potentially incorrect type error for operator + for 2 lists -
**Code**
```
l1 = [1, 2, 3]
l2 = [[1, 2]]
l1 + l2
# output: [1, 2, 3, [1, 2]]
```
**Observed behavior**
Get type error: `Operator "+" not supported for types "list[int]" and "list[list[int]]"`
**Expected behavior**
Since this operation is allowed in python, perhaps there shouldn't be any type error.
The output list has type: `list[Union[list[int], int]]`.
| design | potentially incorrect type error for operator for lists code output observed behavior get type error operator not supported for types list and list expected behavior since this operation is allowed in python perhaps there shouldn t be any type error the output list has type list int | 1 |
196,794 | 22,571,578,937 | IssuesEvent | 2022-06-28 01:00:46 | billmcchesney1/superagent | https://api.github.com/repos/billmcchesney1/superagent | opened | CVE-2021-42740 (High) detected in shell-quote-1.4.1.tgz, shell-quote-1.7.2.tgz | security vulnerability | ## CVE-2021-42740 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>shell-quote-1.4.1.tgz</b>, <b>shell-quote-1.7.2.tgz</b></p></summary>
<p>
<details><summary><b>shell-quote-1.4.1.tgz</b></p></summary>
<p>quote and parse shell commands</p>
<p>Library home page: <a href="https://registry.npmjs.org/shell-quote/-/shell-quote-1.4.1.tgz">https://registry.npmjs.org/shell-quote/-/shell-quote-1.4.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/zuul/node_modules/shell-quote/package.json</p>
<p>
Dependency Hierarchy:
- zuul-3.12.0.tgz (Root Library)
- :x: **shell-quote-1.4.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>shell-quote-1.7.2.tgz</b></p></summary>
<p>quote and parse shell commands</p>
<p>Library home page: <a href="https://registry.npmjs.org/shell-quote/-/shell-quote-1.7.2.tgz">https://registry.npmjs.org/shell-quote/-/shell-quote-1.7.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/shell-quote/package.json,/node_modules/zuul/node_modules/browserify/node_modules/shell-quote/package.json</p>
<p>
Dependency Hierarchy:
- browserify-16.5.2.tgz (Root Library)
- :x: **shell-quote-1.7.2.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/billmcchesney1/superagent/commit/77fefdaffd4ef3cef2e5b252e165b5f40fae61d5">77fefdaffd4ef3cef2e5b252e165b5f40fae61d5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The shell-quote package before 1.7.3 for Node.js allows command injection. An attacker can inject unescaped shell metacharacters through a regex designed to support Windows drive letters. If the output of this package is passed to a real shell as a quoted argument to a command with exec(), an attacker can inject arbitrary commands. This is because the Windows drive letter regex character class is {A-z] instead of the correct {A-Za-z]. Several shell metacharacters exist in the space between capital letter Z and lower case letter a, such as the backtick character.
<p>Publish Date: 2021-10-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-42740>CVE-2021-42740</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-42740">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-42740</a></p>
<p>Release Date: 2021-10-21</p>
<p>Fix Resolution (shell-quote): 1.7.3</p>
<p>Direct dependency fix Resolution (browserify): 17.0.0</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| True | CVE-2021-42740 (High) detected in shell-quote-1.4.1.tgz, shell-quote-1.7.2.tgz - ## CVE-2021-42740 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>shell-quote-1.4.1.tgz</b>, <b>shell-quote-1.7.2.tgz</b></p></summary>
<p>
<details><summary><b>shell-quote-1.4.1.tgz</b></p></summary>
<p>quote and parse shell commands</p>
<p>Library home page: <a href="https://registry.npmjs.org/shell-quote/-/shell-quote-1.4.1.tgz">https://registry.npmjs.org/shell-quote/-/shell-quote-1.4.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/zuul/node_modules/shell-quote/package.json</p>
<p>
Dependency Hierarchy:
- zuul-3.12.0.tgz (Root Library)
- :x: **shell-quote-1.4.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>shell-quote-1.7.2.tgz</b></p></summary>
<p>quote and parse shell commands</p>
<p>Library home page: <a href="https://registry.npmjs.org/shell-quote/-/shell-quote-1.7.2.tgz">https://registry.npmjs.org/shell-quote/-/shell-quote-1.7.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/shell-quote/package.json,/node_modules/zuul/node_modules/browserify/node_modules/shell-quote/package.json</p>
<p>
Dependency Hierarchy:
- browserify-16.5.2.tgz (Root Library)
- :x: **shell-quote-1.7.2.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/billmcchesney1/superagent/commit/77fefdaffd4ef3cef2e5b252e165b5f40fae61d5">77fefdaffd4ef3cef2e5b252e165b5f40fae61d5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The shell-quote package before 1.7.3 for Node.js allows command injection. An attacker can inject unescaped shell metacharacters through a regex designed to support Windows drive letters. If the output of this package is passed to a real shell as a quoted argument to a command with exec(), an attacker can inject arbitrary commands. This is because the Windows drive letter regex character class is {A-z] instead of the correct {A-Za-z]. Several shell metacharacters exist in the space between capital letter Z and lower case letter a, such as the backtick character.
<p>Publish Date: 2021-10-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-42740>CVE-2021-42740</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-42740">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-42740</a></p>
<p>Release Date: 2021-10-21</p>
<p>Fix Resolution (shell-quote): 1.7.3</p>
<p>Direct dependency fix Resolution (browserify): 17.0.0</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| non_design | cve high detected in shell quote tgz shell quote tgz cve high severity vulnerability vulnerable libraries shell quote tgz shell quote tgz shell quote tgz quote and parse shell commands library home page a href path to dependency file package json path to vulnerable library node modules zuul node modules shell quote package json dependency hierarchy zuul tgz root library x shell quote tgz vulnerable library shell quote tgz quote and parse shell commands library home page a href path to dependency file package json path to vulnerable library node modules shell quote package json node modules zuul node modules browserify node modules shell quote package json dependency hierarchy browserify tgz root library x shell quote tgz vulnerable library found in head commit a href found in base branch master vulnerability details the shell quote package before for node js allows command injection an attacker can inject unescaped shell metacharacters through a regex designed to support windows drive letters if the output of this package is passed to a real shell as a quoted argument to a command with exec an attacker can inject arbitrary commands this is because the windows drive letter regex character class is a z instead of the correct a za z several shell metacharacters exist in the space between capital letter z and lower case letter a such as the backtick character publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution shell quote direct dependency fix resolution browserify check this box to open an automated fix pr | 0 |
109,325 | 11,633,209,269 | IssuesEvent | 2020-02-28 07:39:50 | bounswe/bounswe2020group8 | https://api.github.com/repos/bounswe/bounswe2020group8 | closed | Add group photo to README | documentation | We decided to put a group photo to README, so we took a photo at the 3rd meeting. Unfortunately, 2 members were absent. We are planning to take another one with all team, this photo is temporary :)
I will edit the page accordingly.
[Link to README](https://github.com/bounswe/bounswe2020group8/blob/master/README.md) | 1.0 | Add group photo to README - We decided to put a group photo to README, so we took a photo at the 3rd meeting. Unfortunately, 2 members were absent. We are planning to take another one with all team, this photo is temporary :)
I will edit the page accordingly.
[Link to README](https://github.com/bounswe/bounswe2020group8/blob/master/README.md) | non_design | add group photo to readme we decided to put a group photo to readme so we took a photo at the meeting unfortunately members were absent we are planning to take another one with all team this photo is temporary i will edit the page accordingly | 0 |
33,846 | 16,167,829,224 | IssuesEvent | 2021-05-01 21:28:13 | crystal-lang/crystal | https://api.github.com/repos/crystal-lang/crystal | closed | optimize rotate? | kind:refactor performance status:someday topic:stdlib:collection | while doing adventofcode i noticed rotate method a bit slow. checked implementation, does copy of array, allocates memory, not very good. implementation in ruby (copied from perl) does reverse three times:
https://github.com/ruby/ruby/blob/027b576b31cd12bad575b3a39476726273f58c41/array.c#L2296-L2315
i did benchmark with different sizes, seem after size 100 faster to allocate memory, otherwise do in place. or maybe always do in place?
```crystal
class Array
def new_rotate!(n = 1)
return self if size == 0
n %= size
return self if n == 0
Slice.new(@buffer, n).reverse! if n > 1
Slice.new(@buffer + n, size - n).reverse! if n < size - 1
reverse!
end
end
def bench
Time.measure do
1_000_000.times do
yield
end
end
end
sizes = [10, 20, 50, 100, 110, 200, 500, 1000, 5000]
rotate_counts = (1..9).to_a
puts "size, rotate, time old, time new"
sizes.each do |size|
ary = Array.new(size, &.itself)
rotate_counts.each do |rotate_count|
time_old = bench { ary.rotate!(rotate_count) }
time_new = bench { ary.new_rotate!(rotate_count) }
puts "#{size}, #{rotate_count}, #{time_old}, #{time_new}"
end
end
```
Output:
```
size, rotate, time old, time new
10, 1, 00:00:00.120928263, 00:00:00.016859090
10, 2, 00:00:00.101144279, 00:00:00.020961746
10, 3, 00:00:00.123458672, 00:00:00.017167817
10, 4, 00:00:00.122454864, 00:00:00.020344335
10, 5, 00:00:00.122315772, 00:00:00.017891776
10, 6, 00:00:00.123336572, 00:00:00.020212703
10, 7, 00:00:00.105817244, 00:00:00.018086583
10, 8, 00:00:00.100856720, 00:00:00.018376816
10, 9, 00:00:00.104535931, 00:00:00.018839083
20, 1, 00:00:00.100450762, 00:00:00.031587526
20, 2, 00:00:00.099028190, 00:00:00.031607453
20, 3, 00:00:00.116294172, 00:00:00.029703566
20, 4, 00:00:00.119623513, 00:00:00.030364195
20, 5, 00:00:00.116714344, 00:00:00.029344444
20, 6, 00:00:00.117427029, 00:00:00.034127133
20, 7, 00:00:00.134617673, 00:00:00.030561268
20, 8, 00:00:00.136022428, 00:00:00.030929011
20, 9, 00:00:00.129268385, 00:00:00.031708755
50, 1, 00:00:00.102764069, 00:00:00.067362985
50, 2, 00:00:00.106949262, 00:00:00.070628290
50, 3, 00:00:00.126886781, 00:00:00.072188116
50, 4, 00:00:00.128371287, 00:00:00.072219045
50, 5, 00:00:00.128669877, 00:00:00.070250427
50, 6, 00:00:00.128479294, 00:00:00.075750366
50, 7, 00:00:00.135220582, 00:00:00.069463664
50, 8, 00:00:00.137785256, 00:00:00.067685157
50, 9, 00:00:00.136315260, 00:00:00.071669669
100, 1, 00:00:00.099206141, 00:00:00.148144148
100, 2, 00:00:00.101125638, 00:00:00.147913928
100, 3, 00:00:00.131678238, 00:00:00.146786222
100, 4, 00:00:00.130791922, 00:00:00.156125615
100, 5, 00:00:00.128752702, 00:00:00.147817690
100, 6, 00:00:00.127315555, 00:00:00.148849068
100, 7, 00:00:00.137780093, 00:00:00.144140311
100, 8, 00:00:00.138602604, 00:00:00.149558444
100, 9, 00:00:00.140234268, 00:00:00.145874548
110, 1, 00:00:00.099337242, 00:00:00.153697442
110, 2, 00:00:00.099129942, 00:00:00.155149370
110, 3, 00:00:00.130136229, 00:00:00.160515708
110, 4, 00:00:00.131667602, 00:00:00.168184856
110, 5, 00:00:00.131960925, 00:00:00.158351375
110, 6, 00:00:00.131936713, 00:00:00.154146729
110, 7, 00:00:00.135346357, 00:00:00.153732246
110, 8, 00:00:00.137149644, 00:00:00.157924828
110, 9, 00:00:00.137761492, 00:00:00.162084057
200, 1, 00:00:00.114391576, 00:00:00.251576523
200, 2, 00:00:00.117437000, 00:00:00.269928936
200, 3, 00:00:00.138339056, 00:00:00.259907637
200, 4, 00:00:00.134251915, 00:00:00.251692345
200, 5, 00:00:00.134088314, 00:00:00.260822818
200, 6, 00:00:00.135678999, 00:00:00.263625594
200, 7, 00:00:00.141953332, 00:00:00.262330444
200, 8, 00:00:00.146124534, 00:00:00.267452469
200, 9, 00:00:00.147708968, 00:00:00.264784848
500, 1, 00:00:00.132368178, 00:00:00.615199123
500, 2, 00:00:00.127191336, 00:00:00.601483802
500, 3, 00:00:00.142068062, 00:00:00.594493267
500, 4, 00:00:00.142437275, 00:00:00.611995902
500, 5, 00:00:00.142401548, 00:00:00.587588649
500, 6, 00:00:00.144097188, 00:00:00.620041256
500, 7, 00:00:00.159433517, 00:00:00.608937110
500, 8, 00:00:00.165959937, 00:00:00.610409642
500, 9, 00:00:00.157916469, 00:00:00.613097371
1000, 1, 00:00:00.158271143, 00:00:01.176496980
1000, 2, 00:00:00.158373790, 00:00:01.181245065
1000, 3, 00:00:00.178311050, 00:00:01.150156520
1000, 4, 00:00:00.177887367, 00:00:01.215450674
1000, 5, 00:00:00.182622815, 00:00:01.233552764
1000, 6, 00:00:00.210927084, 00:00:01.241661947
1000, 7, 00:00:00.196003425, 00:00:01.189561179
1000, 8, 00:00:00.194813398, 00:00:01.193315692
1000, 9, 00:00:00.196365969, 00:00:01.203671327
5000, 1, 00:00:00.431793514, 00:00:06.029244231
5000, 2, 00:00:00.437870275, 00:00:05.902887141
5000, 3, 00:00:00.451904861, 00:00:06.663213585
5000, 4, 00:00:00.649389702, 00:00:06.158866684
5000, 5, 00:00:00.456520997, 00:00:06.533285982
5000, 6, 00:00:00.534730195, 00:00:07.382842737
5000, 7, 00:00:00.477839905, 00:00:05.966309350
5000, 8, 00:00:00.447289937, 00:00:06.108911938
5000, 9, 00:00:00.509821664, 00:00:05.920721640
``` | True | optimize rotate? - while doing adventofcode i noticed rotate method a bit slow. checked implementation, does copy of array, allocates memory, not very good. implementation in ruby (copied from perl) does reverse three times:
https://github.com/ruby/ruby/blob/027b576b31cd12bad575b3a39476726273f58c41/array.c#L2296-L2315
i did benchmark with different sizes, seem after size 100 faster to allocate memory, otherwise do in place. or maybe always do in place?
```crystal
class Array
def new_rotate!(n = 1)
return self if size == 0
n %= size
return self if n == 0
Slice.new(@buffer, n).reverse! if n > 1
Slice.new(@buffer + n, size - n).reverse! if n < size - 1
reverse!
end
end
def bench
Time.measure do
1_000_000.times do
yield
end
end
end
sizes = [10, 20, 50, 100, 110, 200, 500, 1000, 5000]
rotate_counts = (1..9).to_a
puts "size, rotate, time old, time new"
sizes.each do |size|
ary = Array.new(size, &.itself)
rotate_counts.each do |rotate_count|
time_old = bench { ary.rotate!(rotate_count) }
time_new = bench { ary.new_rotate!(rotate_count) }
puts "#{size}, #{rotate_count}, #{time_old}, #{time_new}"
end
end
```
Output:
```
size, rotate, time old, time new
10, 1, 00:00:00.120928263, 00:00:00.016859090
10, 2, 00:00:00.101144279, 00:00:00.020961746
10, 3, 00:00:00.123458672, 00:00:00.017167817
10, 4, 00:00:00.122454864, 00:00:00.020344335
10, 5, 00:00:00.122315772, 00:00:00.017891776
10, 6, 00:00:00.123336572, 00:00:00.020212703
10, 7, 00:00:00.105817244, 00:00:00.018086583
10, 8, 00:00:00.100856720, 00:00:00.018376816
10, 9, 00:00:00.104535931, 00:00:00.018839083
20, 1, 00:00:00.100450762, 00:00:00.031587526
20, 2, 00:00:00.099028190, 00:00:00.031607453
20, 3, 00:00:00.116294172, 00:00:00.029703566
20, 4, 00:00:00.119623513, 00:00:00.030364195
20, 5, 00:00:00.116714344, 00:00:00.029344444
20, 6, 00:00:00.117427029, 00:00:00.034127133
20, 7, 00:00:00.134617673, 00:00:00.030561268
20, 8, 00:00:00.136022428, 00:00:00.030929011
20, 9, 00:00:00.129268385, 00:00:00.031708755
50, 1, 00:00:00.102764069, 00:00:00.067362985
50, 2, 00:00:00.106949262, 00:00:00.070628290
50, 3, 00:00:00.126886781, 00:00:00.072188116
50, 4, 00:00:00.128371287, 00:00:00.072219045
50, 5, 00:00:00.128669877, 00:00:00.070250427
50, 6, 00:00:00.128479294, 00:00:00.075750366
50, 7, 00:00:00.135220582, 00:00:00.069463664
50, 8, 00:00:00.137785256, 00:00:00.067685157
50, 9, 00:00:00.136315260, 00:00:00.071669669
100, 1, 00:00:00.099206141, 00:00:00.148144148
100, 2, 00:00:00.101125638, 00:00:00.147913928
100, 3, 00:00:00.131678238, 00:00:00.146786222
100, 4, 00:00:00.130791922, 00:00:00.156125615
100, 5, 00:00:00.128752702, 00:00:00.147817690
100, 6, 00:00:00.127315555, 00:00:00.148849068
100, 7, 00:00:00.137780093, 00:00:00.144140311
100, 8, 00:00:00.138602604, 00:00:00.149558444
100, 9, 00:00:00.140234268, 00:00:00.145874548
110, 1, 00:00:00.099337242, 00:00:00.153697442
110, 2, 00:00:00.099129942, 00:00:00.155149370
110, 3, 00:00:00.130136229, 00:00:00.160515708
110, 4, 00:00:00.131667602, 00:00:00.168184856
110, 5, 00:00:00.131960925, 00:00:00.158351375
110, 6, 00:00:00.131936713, 00:00:00.154146729
110, 7, 00:00:00.135346357, 00:00:00.153732246
110, 8, 00:00:00.137149644, 00:00:00.157924828
110, 9, 00:00:00.137761492, 00:00:00.162084057
200, 1, 00:00:00.114391576, 00:00:00.251576523
200, 2, 00:00:00.117437000, 00:00:00.269928936
200, 3, 00:00:00.138339056, 00:00:00.259907637
200, 4, 00:00:00.134251915, 00:00:00.251692345
200, 5, 00:00:00.134088314, 00:00:00.260822818
200, 6, 00:00:00.135678999, 00:00:00.263625594
200, 7, 00:00:00.141953332, 00:00:00.262330444
200, 8, 00:00:00.146124534, 00:00:00.267452469
200, 9, 00:00:00.147708968, 00:00:00.264784848
500, 1, 00:00:00.132368178, 00:00:00.615199123
500, 2, 00:00:00.127191336, 00:00:00.601483802
500, 3, 00:00:00.142068062, 00:00:00.594493267
500, 4, 00:00:00.142437275, 00:00:00.611995902
500, 5, 00:00:00.142401548, 00:00:00.587588649
500, 6, 00:00:00.144097188, 00:00:00.620041256
500, 7, 00:00:00.159433517, 00:00:00.608937110
500, 8, 00:00:00.165959937, 00:00:00.610409642
500, 9, 00:00:00.157916469, 00:00:00.613097371
1000, 1, 00:00:00.158271143, 00:00:01.176496980
1000, 2, 00:00:00.158373790, 00:00:01.181245065
1000, 3, 00:00:00.178311050, 00:00:01.150156520
1000, 4, 00:00:00.177887367, 00:00:01.215450674
1000, 5, 00:00:00.182622815, 00:00:01.233552764
1000, 6, 00:00:00.210927084, 00:00:01.241661947
1000, 7, 00:00:00.196003425, 00:00:01.189561179
1000, 8, 00:00:00.194813398, 00:00:01.193315692
1000, 9, 00:00:00.196365969, 00:00:01.203671327
5000, 1, 00:00:00.431793514, 00:00:06.029244231
5000, 2, 00:00:00.437870275, 00:00:05.902887141
5000, 3, 00:00:00.451904861, 00:00:06.663213585
5000, 4, 00:00:00.649389702, 00:00:06.158866684
5000, 5, 00:00:00.456520997, 00:00:06.533285982
5000, 6, 00:00:00.534730195, 00:00:07.382842737
5000, 7, 00:00:00.477839905, 00:00:05.966309350
5000, 8, 00:00:00.447289937, 00:00:06.108911938
5000, 9, 00:00:00.509821664, 00:00:05.920721640
``` | non_design | optimize rotate while doing adventofcode i noticed rotate method a bit slow checked implementation does copy of array allocates memory not very good implementation in ruby copied from perl does reverse three times i did benchmark with different sizes seem after size faster to allocate memory otherwise do in place or maybe always do in place crystal class array def new rotate n return self if size n size return self if n slice new buffer n reverse if n slice new buffer n size n reverse if n size reverse end end def bench time measure do times do yield end end end sizes rotate counts to a puts size rotate time old time new sizes each do size ary array new size itself rotate counts each do rotate count time old bench ary rotate rotate count time new bench ary new rotate rotate count puts size rotate count time old time new end end output size rotate time old time new | 0 |
118,170 | 15,244,099,849 | IssuesEvent | 2021-02-19 12:16:11 | StrangeLoopGames/EcoIssues | https://api.github.com/repos/StrangeLoopGames/EcoIssues | opened | [0.9.3 Staging-1935]Torch Stand Delay | Category: Design Priority: Low Type: Task | Tested on 0.9.3 Staging 1935.
Issue: The torch stand light effect has a significant amount of delay when switching it on. The same issue can be observed when switching it off.
Repro:
1. Grab a Torch and a Torch Stand.
2. Place the Torch as the fuel supply of the Torch Stand.
3. Turn ON Torch Stand and observe.
Result: Significant delays in light effect on Torch Stand.
Video Repro:
https://images.zenhubusercontent.com/42199084/d5137a7c-1260-4139-9781-75d52adcdd80/2021_02_19_20_13.mp4
Can be linked and added to #12338. | 1.0 | [0.9.3 Staging-1935]Torch Stand Delay - Tested on 0.9.3 Staging 1935.
Issue: The torch stand light effect has a significant amount of delay when switching it on. The same issue can be observed when switching it off.
Repro:
1. Grab a Torch and a Torch Stand.
2. Place the Torch as the fuel supply of the Torch Stand.
3. Turn ON Torch Stand and observe.
Result: Significant delays in light effect on Torch Stand.
Video Repro:
https://images.zenhubusercontent.com/42199084/d5137a7c-1260-4139-9781-75d52adcdd80/2021_02_19_20_13.mp4
Can be linked and added to #12338. | design | torch stand delay tested on staging issue the torch stand light effect has a significant amount of delay when switching it on the same issue can be observed when switching it off repro grab a torch and a torch stand place the torch as the fuel supply of the torch stand turn on torch stand and observe result significant delays in light effect on torch stand video repro can be linked and added to | 1 |
8,055 | 2,867,171,983 | IssuesEvent | 2015-06-05 11:35:11 | eGovlab/sense4us-simulation | https://api.github.com/repos/eGovlab/sense4us-simulation | closed | [Simulate] If node IDs start above 0 and are not in sequential order the returning array will contain empty elements | DESIGN ERROR | The empty elements (containing NULL) will crash a loop on the frontend which is setting up the simulation model. The loop will anticipate nodes in every element. | 1.0 | [Simulate] If node IDs start above 0 and are not in sequential order the returning array will contain empty elements - The empty elements (containing NULL) will crash a loop on the frontend which is setting up the simulation model. The loop will anticipate nodes in every element. | design | if node ids start above and are not in sequential order the returning array will contain empty elements the empty elements containing null will crash a loop on the frontend which is setting up the simulation model the loop will anticipate nodes in every element | 1 |
9,755 | 8,700,459,589 | IssuesEvent | 2018-12-05 08:48:34 | hyperledger/composer | https://api.github.com/repos/hyperledger/composer | closed | [0.19.x, Master] Transaction ID in runtime trace is not reliable | P1 bug serviceability | It is due to this bit of code really
```
async initLogging(stub) {
this.stub = stub;
let logCFG = await this.getLoggerCfg();
Logger.setLoggerCfg(logCFG, true);
Logger.setCallBack(function(logLevel) {
const timestamp = new Date().toISOString();
const shortTxId = stub.getTxID().substring(0, 8);
return `${timestamp} [${shortTxId}] ${logLevel.toUpperCase().padEnd(8)} `;
});
}
```
initLogging is called whenever a request comes in. As the Logger implementation is a singleton the callback get's overwritten with a new version and the TxId changes which then will be used for other inflight transactions. Also what might be causing log entries to not get written is that setLoggerCfg is always being called and probably doesn't need to be called unless something has changed so probably shouldn't be in this method anyway.
The problem is how will any log entry called from the runtime be able to get the right transaction id to output ? There is no easy way. It's likely the whole logging infrastructure might have to be re-written in order for txid to be attached to all log entries without doing it manually for each call. But it's necessary to be able to correlate interleaved log messages . | 1.0 | [0.19.x, Master] Transaction ID in runtime trace is not reliable - It is due to this bit of code really
```
async initLogging(stub) {
this.stub = stub;
let logCFG = await this.getLoggerCfg();
Logger.setLoggerCfg(logCFG, true);
Logger.setCallBack(function(logLevel) {
const timestamp = new Date().toISOString();
const shortTxId = stub.getTxID().substring(0, 8);
return `${timestamp} [${shortTxId}] ${logLevel.toUpperCase().padEnd(8)} `;
});
}
```
initLogging is called whenever a request comes in. As the Logger implementation is a singleton the callback get's overwritten with a new version and the TxId changes which then will be used for other inflight transactions. Also what might be causing log entries to not get written is that setLoggerCfg is always being called and probably doesn't need to be called unless something has changed so probably shouldn't be in this method anyway.
The problem is how will any log entry called from the runtime be able to get the right transaction id to output ? There is no easy way. It's likely the whole logging infrastructure might have to be re-written in order for txid to be attached to all log entries without doing it manually for each call. But it's necessary to be able to correlate interleaved log messages . | non_design | transaction id in runtime trace is not reliable it is due to this bit of code really async initlogging stub this stub stub let logcfg await this getloggercfg logger setloggercfg logcfg true logger setcallback function loglevel const timestamp new date toisostring const shorttxid stub gettxid substring return timestamp loglevel touppercase padend initlogging is called whenever a request comes in as the logger implementation is a singleton the callback get s overwritten with a new version and the txid changes which then will be used for other inflight transactions also what might be causing log entries to not get written is that setloggercfg is always being called and probably doesn t need to be called unless something has changed so probably shouldn t be in this method anyway the problem is how will any log entry called from the runtime be able to get the right transaction id to output there is no easy way it s likely the whole logging infrastructure might have to be re written in order for txid to be attached to all log entries without doing it manually for each call but it s necessary to be able to correlate interleaved log messages | 0 |
123,114 | 16,445,109,588 | IssuesEvent | 2021-05-20 18:35:41 | sul-dlss/mise | https://api.github.com/repos/sul-dlss/mise | opened | Auto-save workspaces or enhance the Save workspace button | design needed question | This is more of a question/design needed issue at this stage. I'm not certain which of the alternative user stories below best represent our real potential users.
**User story A**: As Mise user, when working on resources in my workspace, the current state of my workspace should be saved automatically so I don't have to know to and remember to save the workspace or risk losing changes I've made when leaving the workspace.
**User story B**: As Mise user, when working on resources in my workspace, I should have a clear and noticeable indication when the current state of my workspace has unsaved changes so I know that I either need to save the workspace or intentionally lose recent changes I've made when leaving the workspace. | 1.0 | Auto-save workspaces or enhance the Save workspace button - This is more of a question/design needed issue at this stage. I'm not certain which of the alternative user stories below best represent our real potential users.
**User story A**: As Mise user, when working on resources in my workspace, the current state of my workspace should be saved automatically so I don't have to know to and remember to save the workspace or risk losing changes I've made when leaving the workspace.
**User story B**: As Mise user, when working on resources in my workspace, I should have a clear and noticeable indication when the current state of my workspace has unsaved changes so I know that I either need to save the workspace or intentionally lose recent changes I've made when leaving the workspace. | design | auto save workspaces or enhance the save workspace button this is more of a question design needed issue at this stage i m not certain which of the alternative user stories below best represent our real potential users user story a as mise user when working on resources in my workspace the current state of my workspace should be saved automatically so i don t have to know to and remember to save the workspace or risk losing changes i ve made when leaving the workspace user story b as mise user when working on resources in my workspace i should have a clear and noticeable indication when the current state of my workspace has unsaved changes so i know that i either need to save the workspace or intentionally lose recent changes i ve made when leaving the workspace | 1 |
38,738 | 5,003,140,179 | IssuesEvent | 2016-12-11 19:20:45 | thewca/worldcubeassociation.org | https://api.github.com/repos/thewca/worldcubeassociation.org | opened | Competition pages sidebar menu tweaks: improve menu item highlighting, positioning | design low-priority | Maybe a separate "information" menu item is needed?
Eg, when viewing a schedule, having "results" highlighted off to the side doesn't make much sense:
The positioning of the sidebar also makes more sense to me to have below the competition title. Having it below implicitly suggests that different information about the same competition will be displayed, rather than something more general. Eg:
| 1.0 | Competition pages sidebar menu tweaks: improve menu item highlighting, positioning - Maybe a separate "information" menu item is needed?
Eg, when viewing a schedule, having "results" highlighted off to the side doesn't make much sense:
The positioning of the sidebar also makes more sense to me to have below the competition title. Having it below implicitly suggests that different information about the same competition will be displayed, rather than something more general. Eg:
| design | competition pages sidebar menu tweaks improve menu item highlighting positioning maybe a separate information menu item is needed eg when viewing a schedule having results highlighted off to the side doesn t make much sense the positioning of the sidebar also makes more sense to me to have below the competition title having it below implicitly suggests that different information about the same competition will be displayed rather than something more general eg | 1 |
117,668 | 15,162,322,249 | IssuesEvent | 2021-02-12 10:25:55 | flutter/flutter | https://api.github.com/repos/flutter/flutter | closed | PaginatedDataTable: non logical PageRowsInfoTitle | f: material design framework in triage waiting for customer response | If we want a table that can show 10 rows (we set `rowsPerPage` in the constructor) and the current data has 5 rows. The `PageRowsInfoTitle` at the bottom of the table shows `1-10 of 5` which is not a great info. The correct way in this situation should be `1-5 of 5` even if the grid is showing 10 rows (5 blank).
I resolved that issue by doing my implementation of the `PaginatedDataTable` and correcting the part that is generating the `PageRowsInfoTitle`:
```dart
new Text(localizations.pageRowsInfoTitle(
_firstRowIndex + 1,
_rowCount >= 0 && _firstRowIndex + widget.rowsPerPage > _rowCount ? _rowCount : _firstRowIndex + widget.rowsPerPage,
_rowCount,
_rowCountApproximate)),
```
Hope you implement that check in the official track. | 1.0 | PaginatedDataTable: non logical PageRowsInfoTitle - If we want a table that can show 10 rows (we set `rowsPerPage` in the constructor) and the current data has 5 rows. The `PageRowsInfoTitle` at the bottom of the table shows `1-10 of 5` which is not a great info. The correct way in this situation should be `1-5 of 5` even if the grid is showing 10 rows (5 blank).
I resolved that issue by doing my implementation of the `PaginatedDataTable` and correcting the part that is generating the `PageRowsInfoTitle`:
```dart
new Text(localizations.pageRowsInfoTitle(
_firstRowIndex + 1,
_rowCount >= 0 && _firstRowIndex + widget.rowsPerPage > _rowCount ? _rowCount : _firstRowIndex + widget.rowsPerPage,
_rowCount,
_rowCountApproximate)),
```
Hope you implement that check in the official track. | design | paginateddatatable non logical pagerowsinfotitle if we want a table that can show rows we set rowsperpage in the constructor and the current data has rows the pagerowsinfotitle at the bottom of the table shows of which is not a great info the correct way in this situation should be of even if the grid is showing rows blank i resolved that issue by doing my implementation of the paginateddatatable and correcting the part that is generating the pagerowsinfotitle dart new text localizations pagerowsinfotitle firstrowindex rowcount firstrowindex widget rowsperpage rowcount rowcount firstrowindex widget rowsperpage rowcount rowcountapproximate hope you implement that check in the official track | 1 |
181,784 | 14,074,594,203 | IssuesEvent | 2020-11-04 07:37:23 | OpenMined/PySyft | https://api.github.com/repos/OpenMined/PySyft | closed | Add torch.Tensor.reshape to allowlist and test suite | Priority: 2 - High :cold_sweat: Severity: 3 - Medium :unamused: Status: Available :wave: Type: New Feature :heavy_plus_sign: Type: Testing :test_tube: |
# Description
This issue is a part of Syft 0.3.0 Epic 2: https://github.com/OpenMined/PySyft/issues/3696
In this issue, you will be adding support for remote execution of the torch.Tensor.reshape
method or property. This might be a really small project (literally a one-liner) or
it might require adding significant functionality to PySyft OR to the testing suite
in order to make sure the feature is both functional and tested.
## Step 0: Run tests and ./scripts/pre_commit.sh
Before you get started with this project, let's make sure you have everything building and testing
correctly. Clone the codebase and run:
```pip uninstall syft```
followed by
```pip install -e .```
Then run the pre-commit file (which will also run the tests)
```./scripts/pre_commit.sh```
If all of these tests pass, continue on. If not, make sure you have all the
dependencies in requirements.txt installed, etc.
## Step 1: Uncomment your method in the allowlist.py file
Inside [allowlist.py](https://github.com/OpenMined/PySyft/blob/syft_0.3.0/src/syft/lib/torch/allowlist.py) you will find a huge dictionary of methods. Find your method and uncomment the line its on. At the time
of writing this Issue (WARNING: THIS MAY HAVE CHANGED) the dictionary maps from the
string name of the method (in your case 'torch.Tensor.reshape') to the string representation
of the type the method returns.
## Step 2: Run Unit Tests
Run the following:
```python setup.py test```
And wait to see if some of the tests fail. Why might the tests fail now? I'm so glad you asked!
https://github.com/OpenMined/PySyft/blob/syft_0.3.0/tests/syft/lib/torch/tensor/tensor_remote_method_api_suite_test.py
In this file you'll find the torch method test suite. It AUTOMATICALLY loads all methods
from the allowlist.py file you modified in the previous step. It attempts to test them.
# Step 3: If you get a Failing Test
If you get a failing test, this could be for one of a few reasons:
### Reason 1 - The testing suite passed in non-compatible arguments
The testing suite is pretty dumb. It literally just has a permutation of possible
arguments to pass into every method on torch tensors. So, if one of those permutations
doesn't work for your method (aka... perhaps it tries to call your method without
any arguments but torch.Tensor.reshape actually requires some) then the test will
fail if the error hasn't been seen before.
If this happens - don't worry! Just look inside the only test in that file and look
for the huge lists of error types to ignore. Add your error to the list and keep
going!!!
*WARNING:* make sure that the testing suite actually tests your method via remote
execution once you've gotten all the tests passing. Aka - if the testing suite
doesn't have ANY matching argument permutations for your method, then you're
literally creating a bunch of unit tests that do absolutely nothing. If this is the
case, then ADD MORE ARGUMENT TYPES TO THE TESTING SUITE so that your argument
gets run via remote execution. DO NOT CLOSE THIS ISSUE until you can verify that
torch.Tensor.reshape is actually executed remotely inside of a unit tests (and not
skipped). Aka - at least one of the test_all_allowlisted_tensor_methods_work_remotely_on_all_types
unit tests with your method should run ALL THE WAY TO THE END (instead of skipping
the last part.)
*Note:* adding another argument type might require some serialization work if
we don't support arguments of that type yet. If so, this is your job to add it
to the protobuf files in order to close this issue!
### Reason 2 - torch.Tensor.reshape returns a non-supported type
If this happens, you've got a little bit of work in front of you. We don't have
pointer objects to very many remote object types. So, if your method returns anything
other than a single tensor, you probably need to add support for the type it returns
(Such as a bool, None, int, or other types).
*IMPORTANT:* do NOT return the value itself to the end user!!! Return a pointer object
to that type!
*NOTE:* at the time of writing - there are several core pieces of Syft not yet working
to allow you to return any type other than a torch tensor. If you're not comfortable
investigating what those might be - skip this issue and try again later once
someone else has solved these issues.
### Reason 3 - There's something else broken
Chase those stack traces! Talk to friends in Slack. Look at how other methods are supported.
This is a challenging project in a fast moving codebase!
And don't forget - if this project seems to complex - there are plenty of others that
might be easier.
| 2.0 | Add torch.Tensor.reshape to allowlist and test suite -
# Description
This issue is a part of Syft 0.3.0 Epic 2: https://github.com/OpenMined/PySyft/issues/3696
In this issue, you will be adding support for remote execution of the torch.Tensor.reshape
method or property. This might be a really small project (literally a one-liner) or
it might require adding significant functionality to PySyft OR to the testing suite
in order to make sure the feature is both functional and tested.
## Step 0: Run tests and ./scripts/pre_commit.sh
Before you get started with this project, let's make sure you have everything building and testing
correctly. Clone the codebase and run:
```pip uninstall syft```
followed by
```pip install -e .```
Then run the pre-commit file (which will also run the tests)
```./scripts/pre_commit.sh```
If all of these tests pass, continue on. If not, make sure you have all the
dependencies in requirements.txt installed, etc.
## Step 1: Uncomment your method in the allowlist.py file
Inside [allowlist.py](https://github.com/OpenMined/PySyft/blob/syft_0.3.0/src/syft/lib/torch/allowlist.py) you will find a huge dictionary of methods. Find your method and uncomment the line its on. At the time
of writing this Issue (WARNING: THIS MAY HAVE CHANGED) the dictionary maps from the
string name of the method (in your case 'torch.Tensor.reshape') to the string representation
of the type the method returns.
## Step 2: Run Unit Tests
Run the following:
```python setup.py test```
And wait to see if some of the tests fail. Why might the tests fail now? I'm so glad you asked!
https://github.com/OpenMined/PySyft/blob/syft_0.3.0/tests/syft/lib/torch/tensor/tensor_remote_method_api_suite_test.py
In this file you'll find the torch method test suite. It AUTOMATICALLY loads all methods
from the allowlist.py file you modified in the previous step. It attempts to test them.
# Step 3: If you get a Failing Test
If you get a failing test, this could be for one of a few reasons:
### Reason 1 - The testing suite passed in non-compatible arguments
The testing suite is pretty dumb. It literally just has a permutation of possible
arguments to pass into every method on torch tensors. So, if one of those permutations
doesn't work for your method (aka... perhaps it tries to call your method without
any arguments but torch.Tensor.reshape actually requires some) then the test will
fail if the error hasn't been seen before.
If this happens - don't worry! Just look inside the only test in that file and look
for the huge lists of error types to ignore. Add your error to the list and keep
going!!!
*WARNING:* make sure that the testing suite actually tests your method via remote
execution once you've gotten all the tests passing. Aka - if the testing suite
doesn't have ANY matching argument permutations for your method, then you're
literally creating a bunch of unit tests that do absolutely nothing. If this is the
case, then ADD MORE ARGUMENT TYPES TO THE TESTING SUITE so that your argument
gets run via remote execution. DO NOT CLOSE THIS ISSUE until you can verify that
torch.Tensor.reshape is actually executed remotely inside of a unit tests (and not
skipped). Aka - at least one of the test_all_allowlisted_tensor_methods_work_remotely_on_all_types
unit tests with your method should run ALL THE WAY TO THE END (instead of skipping
the last part.)
*Note:* adding another argument type might require some serialization work if
we don't support arguments of that type yet. If so, this is your job to add it
to the protobuf files in order to close this issue!
### Reason 2 - torch.Tensor.reshape returns a non-supported type
If this happens, you've got a little bit of work in front of you. We don't have
pointer objects to very many remote object types. So, if your method returns anything
other than a single tensor, you probably need to add support for the type it returns
(Such as a bool, None, int, or other types).
*IMPORTANT:* do NOT return the value itself to the end user!!! Return a pointer object
to that type!
*NOTE:* at the time of writing - there are several core pieces of Syft not yet working
to allow you to return any type other than a torch tensor. If you're not comfortable
investigating what those might be - skip this issue and try again later once
someone else has solved these issues.
### Reason 3 - There's something else broken
Chase those stack traces! Talk to friends in Slack. Look at how other methods are supported.
This is a challenging project in a fast moving codebase!
And don't forget - if this project seems to complex - there are plenty of others that
might be easier.
| non_design | add torch tensor reshape to allowlist and test suite description this issue is a part of syft epic in this issue you will be adding support for remote execution of the torch tensor reshape method or property this might be a really small project literally a one liner or it might require adding significant functionality to pysyft or to the testing suite in order to make sure the feature is both functional and tested step run tests and scripts pre commit sh before you get started with this project let s make sure you have everything building and testing correctly clone the codebase and run pip uninstall syft followed by pip install e then run the pre commit file which will also run the tests scripts pre commit sh if all of these tests pass continue on if not make sure you have all the dependencies in requirements txt installed etc step uncomment your method in the allowlist py file inside you will find a huge dictionary of methods find your method and uncomment the line its on at the time of writing this issue warning this may have changed the dictionary maps from the string name of the method in your case torch tensor reshape to the string representation of the type the method returns step run unit tests run the following python setup py test and wait to see if some of the tests fail why might the tests fail now i m so glad you asked in this file you ll find the torch method test suite it automatically loads all methods from the allowlist py file you modified in the previous step it attempts to test them step if you get a failing test if you get a failing test this could be for one of a few reasons reason the testing suite passed in non compatible arguments the testing suite is pretty dumb it literally just has a permutation of possible arguments to pass into every method on torch tensors so if one of those permutations doesn t work for your method aka perhaps it tries to call your method without any arguments but torch tensor reshape actually requires some then the test will fail if the error hasn t been seen before if this happens don t worry just look inside the only test in that file and look for the huge lists of error types to ignore add your error to the list and keep going warning make sure that the testing suite actually tests your method via remote execution once you ve gotten all the tests passing aka if the testing suite doesn t have any matching argument permutations for your method then you re literally creating a bunch of unit tests that do absolutely nothing if this is the case then add more argument types to the testing suite so that your argument gets run via remote execution do not close this issue until you can verify that torch tensor reshape is actually executed remotely inside of a unit tests and not skipped aka at least one of the test all allowlisted tensor methods work remotely on all types unit tests with your method should run all the way to the end instead of skipping the last part note adding another argument type might require some serialization work if we don t support arguments of that type yet if so this is your job to add it to the protobuf files in order to close this issue reason torch tensor reshape returns a non supported type if this happens you ve got a little bit of work in front of you we don t have pointer objects to very many remote object types so if your method returns anything other than a single tensor you probably need to add support for the type it returns such as a bool none int or other types important do not return the value itself to the end user return a pointer object to that type note at the time of writing there are several core pieces of syft not yet working to allow you to return any type other than a torch tensor if you re not comfortable investigating what those might be skip this issue and try again later once someone else has solved these issues reason there s something else broken chase those stack traces talk to friends in slack look at how other methods are supported this is a challenging project in a fast moving codebase and don t forget if this project seems to complex there are plenty of others that might be easier | 0 |
171,707 | 20,987,795,066 | IssuesEvent | 2022-03-29 06:13:48 | Satheesh575555/external_pdfium | https://api.github.com/repos/Satheesh575555/external_pdfium | opened | CVE-2018-19210 (Medium) detected in external_pdfiumtinker_edge_r-android9-1.0.2 | security vulnerability | ## CVE-2018-19210 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>external_pdfiumtinker_edge_r-android9-1.0.2</b></p></summary>
<p>
<p>Library home page: <a href=https://github.com/TinkerEdgeR-Android/external_pdfium.git>https://github.com/TinkerEdgeR-Android/external_pdfium.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Satheesh575555/external_pdfium/commit/ac9e7ad2804cd2e179b787cb6e286be7591f4014">ac9e7ad2804cd2e179b787cb6e286be7591f4014</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/third_party/libtiff/tif_dirwrite.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibTIFF 4.0.9, there is a NULL pointer dereference in the TIFFWriteDirectorySec function in tif_dirwrite.c that will lead to a denial of service attack, as demonstrated by tiffset.
<p>Publish Date: 2018-11-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19210>CVE-2018-19210</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19210">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19210</a></p>
<p>Release Date: 2018-11-12</p>
<p>Fix Resolution: v4.0.10</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-19210 (Medium) detected in external_pdfiumtinker_edge_r-android9-1.0.2 - ## CVE-2018-19210 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>external_pdfiumtinker_edge_r-android9-1.0.2</b></p></summary>
<p>
<p>Library home page: <a href=https://github.com/TinkerEdgeR-Android/external_pdfium.git>https://github.com/TinkerEdgeR-Android/external_pdfium.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Satheesh575555/external_pdfium/commit/ac9e7ad2804cd2e179b787cb6e286be7591f4014">ac9e7ad2804cd2e179b787cb6e286be7591f4014</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/third_party/libtiff/tif_dirwrite.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibTIFF 4.0.9, there is a NULL pointer dereference in the TIFFWriteDirectorySec function in tif_dirwrite.c that will lead to a denial of service attack, as demonstrated by tiffset.
<p>Publish Date: 2018-11-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19210>CVE-2018-19210</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19210">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19210</a></p>
<p>Release Date: 2018-11-12</p>
<p>Fix Resolution: v4.0.10</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_design | cve medium detected in external pdfiumtinker edge r cve medium severity vulnerability vulnerable library external pdfiumtinker edge r library home page a href found in head commit a href found in base branch master vulnerable source files third party libtiff tif dirwrite c vulnerability details in libtiff there is a null pointer dereference in the tiffwritedirectorysec function in tif dirwrite c that will lead to a denial of service attack as demonstrated by tiffset 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 suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
22,013 | 2,644,242,279 | IssuesEvent | 2015-03-12 15:57:01 | Connexions/webview | https://api.github.com/repos/Connexions/webview | closed | Editor commenting out Processing Instructions | bug editor High Priority | 1. Derive /contents/031da8d3-b525-429c-80cf-6c8ed997733a@8.32:2/College_Physics
2. Save the page without making any changes in the editor. View the draft json and the processing instructions are included in proper format.
3. Now make a change to the text in the editor and save. View the draft json again. The processing instructions are commented out. | 1.0 | Editor commenting out Processing Instructions - 1. Derive /contents/031da8d3-b525-429c-80cf-6c8ed997733a@8.32:2/College_Physics
2. Save the page without making any changes in the editor. View the draft json and the processing instructions are included in proper format.
3. Now make a change to the text in the editor and save. View the draft json again. The processing instructions are commented out. | non_design | editor commenting out processing instructions derive contents college physics save the page without making any changes in the editor view the draft json and the processing instructions are included in proper format now make a change to the text in the editor and save view the draft json again the processing instructions are commented out | 0 |
30,144 | 4,203,822,437 | IssuesEvent | 2016-06-28 07:33:36 | pythonapis/6ZJYP2PXGY5CWP2LWTZZFRIL | https://api.github.com/repos/pythonapis/6ZJYP2PXGY5CWP2LWTZZFRIL | closed | m20fsc1WuKLGDY4HFEyaWUwG3nf47TgWFs0EsiQTy6zM1GQKahMKOtwPx0Htj9gcXeQqVXoRonqKcoZAjgPipHT5c7COESnAKL/+5rbIy1OL/cmPjNcUblKgatQ2EZzDXuB9HdPt5JaQLjlLPpih0ZUKYPR48M9rR4b+7ohoWTo= | design | 3rTy8UgSPS/t2ZLfI9I+n/pqNYaHsfczWv4nyU6Qzysw4815Uug351zY+4iRl2Nn5dXKw8zuYt8egVit7UTTWLfc/SN1fBMwDvcY8cX4e6h2wZoo6oW5hHIDT6J7gkSWLXYWDnkbjM5kLarAuc4iUyDaXC85OGfUnBb8NmWT47lWMKlQoxzBbKsfxfxL9Tmbvf+bYw7uJk7W8vDi/Pt8Dx84H9A/lqC4uG4HF3ZtIVVV812h1uSmdGVxGnttC+zDcB1FRfqDGPySybzHLfd2/UTqX2XEXnMtS0OMIeC3bH2S8tWpINAyBeVqD95krnTMU7wW9HBl0eRU/giNyAHHl8LlsuqV4WU0PSx3rx9JjLc7ONLfS0Kl2K7NjfrJ0j2hqX+NY/qr4GcOMhREZ6/PaYSG70Cgf3qjPesJzHodCKpuNZue5rHb2juf0Ale50do3baZXQm3C99O3GfaM4GAQ+XqBirWuHQ5Z958QRof5NqjzWLBAXARdlWv02sWzBSeEDNq8JMuwRAZ88NzxXKpzb/1kttcdg8Xo5qkX5bwqrzPStJXPVmazLg7VMWg8ccodItAmRgjXGnnCVRh1bgdtdb44TN+I+KNilP9phCLSgbowc3a1fbH6hdsqLoYVvSZOFLgBz++n+/kwY8s0c966g5qebxYYV4Y+/aVyqpurRbPStJXPVmazLg7VMWg8ccoyZPg99RKsKmDvTj0uT6txPJTsK4491Xtqr6vhWLf+gpifuZs5KQNm7EXBddONVNZiUVm/+Sy+m6RPJ9Arpwu6YobjckUu8B8Stjs15IKaPI4qkJ/OYHBCFK4EfV7Ys4RKcIUqFNAgbWEc+eSW6YiLJn6dgAZER/OC5/QIiY2einG9EdzB5Y05EnqvCgBy93kQKBmmuQQJhPfee+olKYGAHLn+4EbNZGblj0DtDVO4TjNXiXGFI9wYMdNWWedacCB9BW9MzxSAcFIBGzZk2viPM/hCoY8IvV3+lJL9q4Qrrhh7ryTsQKowF9PK+Ugci2Cj+n/75/ourwpxWluqUHjyAmd1bL7veblJe92tdIUxFG31qWUjZlf0jmwHNc0XC4mPKHyntdF/9PimlmcRIqmIq0hXP/FfBnVmFg/+Nsg5dMIuaCBcYcyRzHDQ0cGTkqt | 1.0 | m20fsc1WuKLGDY4HFEyaWUwG3nf47TgWFs0EsiQTy6zM1GQKahMKOtwPx0Htj9gcXeQqVXoRonqKcoZAjgPipHT5c7COESnAKL/+5rbIy1OL/cmPjNcUblKgatQ2EZzDXuB9HdPt5JaQLjlLPpih0ZUKYPR48M9rR4b+7ohoWTo= - 3rTy8UgSPS/t2ZLfI9I+n/pqNYaHsfczWv4nyU6Qzysw4815Uug351zY+4iRl2Nn5dXKw8zuYt8egVit7UTTWLfc/SN1fBMwDvcY8cX4e6h2wZoo6oW5hHIDT6J7gkSWLXYWDnkbjM5kLarAuc4iUyDaXC85OGfUnBb8NmWT47lWMKlQoxzBbKsfxfxL9Tmbvf+bYw7uJk7W8vDi/Pt8Dx84H9A/lqC4uG4HF3ZtIVVV812h1uSmdGVxGnttC+zDcB1FRfqDGPySybzHLfd2/UTqX2XEXnMtS0OMIeC3bH2S8tWpINAyBeVqD95krnTMU7wW9HBl0eRU/giNyAHHl8LlsuqV4WU0PSx3rx9JjLc7ONLfS0Kl2K7NjfrJ0j2hqX+NY/qr4GcOMhREZ6/PaYSG70Cgf3qjPesJzHodCKpuNZue5rHb2juf0Ale50do3baZXQm3C99O3GfaM4GAQ+XqBirWuHQ5Z958QRof5NqjzWLBAXARdlWv02sWzBSeEDNq8JMuwRAZ88NzxXKpzb/1kttcdg8Xo5qkX5bwqrzPStJXPVmazLg7VMWg8ccodItAmRgjXGnnCVRh1bgdtdb44TN+I+KNilP9phCLSgbowc3a1fbH6hdsqLoYVvSZOFLgBz++n+/kwY8s0c966g5qebxYYV4Y+/aVyqpurRbPStJXPVmazLg7VMWg8ccoyZPg99RKsKmDvTj0uT6txPJTsK4491Xtqr6vhWLf+gpifuZs5KQNm7EXBddONVNZiUVm/+Sy+m6RPJ9Arpwu6YobjckUu8B8Stjs15IKaPI4qkJ/OYHBCFK4EfV7Ys4RKcIUqFNAgbWEc+eSW6YiLJn6dgAZER/OC5/QIiY2einG9EdzB5Y05EnqvCgBy93kQKBmmuQQJhPfee+olKYGAHLn+4EbNZGblj0DtDVO4TjNXiXGFI9wYMdNWWedacCB9BW9MzxSAcFIBGzZk2viPM/hCoY8IvV3+lJL9q4Qrrhh7ryTsQKowF9PK+Ugci2Cj+n/75/ourwpxWluqUHjyAmd1bL7veblJe92tdIUxFG31qWUjZlf0jmwHNc0XC4mPKHyntdF/9PimlmcRIqmIq0hXP/FfBnVmFg/+Nsg5dMIuaCBcYcyRzHDQ0cGTkqt | design | n ny i n sy olkygahln n ffbnvmfg | 1 |
375,154 | 11,100,773,857 | IssuesEvent | 2019-12-16 19:57:14 | openhab/openhab-docs | https://api.github.com/repos/openhab/openhab-docs | closed | Add concepts/categories page again | priority: high :fire: section => concepts section => development | I'm also missing this page :-)
For the reference the very old page: https://docs.openhab.org/v2.2/concepts/categories.html
_Originally posted by @martinvw in https://github.com/openhab/openhab-docs/issues/1061#issuecomment-563437801_
---
We should add this one again, since it is referenced in https://github.com/openhab/openhab-docs/blob/master/developers/bindings/thing-xml.md
| 1.0 | Add concepts/categories page again - I'm also missing this page :-)
For the reference the very old page: https://docs.openhab.org/v2.2/concepts/categories.html
_Originally posted by @martinvw in https://github.com/openhab/openhab-docs/issues/1061#issuecomment-563437801_
---
We should add this one again, since it is referenced in https://github.com/openhab/openhab-docs/blob/master/developers/bindings/thing-xml.md
| non_design | add concepts categories page again i m also missing this page for the reference the very old page originally posted by martinvw in we should add this one again since it is referenced in | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.