Unnamed: 0 int64 3 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 7 112 | repo_url stringlengths 36 141 | action stringclasses 3 values | title stringlengths 2 742 | labels stringlengths 4 431 | body stringlengths 5 239k | index stringclasses 10 values | text_combine stringlengths 96 240k | label stringclasses 2 values | text stringlengths 96 200k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
100,174 | 8,724,339,273 | IssuesEvent | 2018-12-10 04:33:58 | dotnet/corefx | https://api.github.com/repos/dotnet/corefx | closed | [arm32/Linux] System.IO.Compression.Tests failures on arm32 linux | arch-arm32 area-System.IO.Compression os-linux test-run-core | Running the arm32 tests on linux for System.IO.Compression.Tests produced the following results: passed 312/314 tests.
Two tests are failing Assert equal statements, the tests are:
```
System.IO.Compression.Tests.zip_CreateTests.CreateUncompressedArchive
System.IO.Compression.Tests.zip_UpdateTests.UpdateUncompressedArchive
```
[testResults.zip](https://github.com/dotnet/corefx/files/2655133/testResults.zip)
| 1.0 | [arm32/Linux] System.IO.Compression.Tests failures on arm32 linux - Running the arm32 tests on linux for System.IO.Compression.Tests produced the following results: passed 312/314 tests.
Two tests are failing Assert equal statements, the tests are:
```
System.IO.Compression.Tests.zip_CreateTests.CreateUncompressedArchive
System.IO.Compression.Tests.zip_UpdateTests.UpdateUncompressedArchive
```
[testResults.zip](https://github.com/dotnet/corefx/files/2655133/testResults.zip)
| non_usab | system io compression tests failures on linux running the tests on linux for system io compression tests produced the following results passed tests two tests are failing assert equal statements the tests are system io compression tests zip createtests createuncompressedarchive system io compression tests zip updatetests updateuncompressedarchive | 0 |
7,827 | 5,238,273,624 | IssuesEvent | 2017-01-31 03:42:52 | DynamoRIO/dynamorio | https://api.github.com/repos/DynamoRIO/dynamorio | closed | warn when trying to encode an instrlist with labels without a second pass | Component-API Type-Feature Usability | When creating a code cache with `dr_nonheap_alloc` that has a jump, I find that all jumps to labels are replaced with an infinite loop because the jump's operand points to itself.
```c
void
insert_jmp(void *drcontext, instrlist_t *ilist, instr_t *where)
{
instr_t *label = INSTR_CREATE_label(drcontext);
instrlist_meta_preinsert(ilist, where, XINST_CREATE_jump
(drcontext,
opnd_create_instr(label)));
instrlist_meta_preinsert(ilist, where, label);
}
static void *
code_cache_init(void *drcontext)
{
void *code_cache = dr_nonheap_alloc(dr_page_size(), DR_MEMPROT_READ |
DR_MEMPROT_WRITE |
DR_MEMPROT_EXEC);
instrlist_t *ilist = instrlist_create(drcontext);
instr_t *where = INSTR_CREATE_ret(drcontext);
instrlist_meta_append(ilist, where);
/* jumping to this label causes an infinite loop */
insert_jmp(drcontext, ilist, where);
instrlist_encode(drcontext, ilist, code_cache, false);
instrlist_clear_and_destroy(drcontext, ilist);
return code_cache;
}
static dr_emit_flags_t
event_basic_block(void *drcontext, void *tag, instrlist_t *bb,
bool for_trace, bool translating)
{
instr_t *where = instrlist_first(bb);
/* jumping to this label works... */
insert_jmp(drcontext, bb, where);
dr_insert_clean_call(drcontext, bb, where, code_cache_init(drcontext), false, 0);
return DR_EMIT_DEFAULT;
}
```
This is similar to what we do in the `memtrace_x86` sample, however we use an absolute jump as opposed to a clean call in that sample.
I would like to use a clean call here, but if this behavior is intended I will instead use `dr_prepare_for_call` followed by the absolute jump. | True | warn when trying to encode an instrlist with labels without a second pass - When creating a code cache with `dr_nonheap_alloc` that has a jump, I find that all jumps to labels are replaced with an infinite loop because the jump's operand points to itself.
```c
void
insert_jmp(void *drcontext, instrlist_t *ilist, instr_t *where)
{
instr_t *label = INSTR_CREATE_label(drcontext);
instrlist_meta_preinsert(ilist, where, XINST_CREATE_jump
(drcontext,
opnd_create_instr(label)));
instrlist_meta_preinsert(ilist, where, label);
}
static void *
code_cache_init(void *drcontext)
{
void *code_cache = dr_nonheap_alloc(dr_page_size(), DR_MEMPROT_READ |
DR_MEMPROT_WRITE |
DR_MEMPROT_EXEC);
instrlist_t *ilist = instrlist_create(drcontext);
instr_t *where = INSTR_CREATE_ret(drcontext);
instrlist_meta_append(ilist, where);
/* jumping to this label causes an infinite loop */
insert_jmp(drcontext, ilist, where);
instrlist_encode(drcontext, ilist, code_cache, false);
instrlist_clear_and_destroy(drcontext, ilist);
return code_cache;
}
static dr_emit_flags_t
event_basic_block(void *drcontext, void *tag, instrlist_t *bb,
bool for_trace, bool translating)
{
instr_t *where = instrlist_first(bb);
/* jumping to this label works... */
insert_jmp(drcontext, bb, where);
dr_insert_clean_call(drcontext, bb, where, code_cache_init(drcontext), false, 0);
return DR_EMIT_DEFAULT;
}
```
This is similar to what we do in the `memtrace_x86` sample, however we use an absolute jump as opposed to a clean call in that sample.
I would like to use a clean call here, but if this behavior is intended I will instead use `dr_prepare_for_call` followed by the absolute jump. | usab | warn when trying to encode an instrlist with labels without a second pass when creating a code cache with dr nonheap alloc that has a jump i find that all jumps to labels are replaced with an infinite loop because the jump s operand points to itself c void insert jmp void drcontext instrlist t ilist instr t where instr t label instr create label drcontext instrlist meta preinsert ilist where xinst create jump drcontext opnd create instr label instrlist meta preinsert ilist where label static void code cache init void drcontext void code cache dr nonheap alloc dr page size dr memprot read dr memprot write dr memprot exec instrlist t ilist instrlist create drcontext instr t where instr create ret drcontext instrlist meta append ilist where jumping to this label causes an infinite loop insert jmp drcontext ilist where instrlist encode drcontext ilist code cache false instrlist clear and destroy drcontext ilist return code cache static dr emit flags t event basic block void drcontext void tag instrlist t bb bool for trace bool translating instr t where instrlist first bb jumping to this label works insert jmp drcontext bb where dr insert clean call drcontext bb where code cache init drcontext false return dr emit default this is similar to what we do in the memtrace sample however we use an absolute jump as opposed to a clean call in that sample i would like to use a clean call here but if this behavior is intended i will instead use dr prepare for call followed by the absolute jump | 1 |
256,854 | 27,561,731,500 | IssuesEvent | 2023-03-07 22:42:48 | samqws-marketing/box_mojito | https://api.github.com/repos/samqws-marketing/box_mojito | closed | CVE-2021-41973 (Medium) detected in mina-core-2.0.0-M6.jar - autoclosed | Mend: dependency security vulnerability | ## CVE-2021-41973 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mina-core-2.0.0-M6.jar</b></p></summary>
<p>Apache MINA is a network application framework which helps users develop high performance and highly scalable network applications easily. It provides an abstract event-driven asynchronous API over various transports such as TCP/IP and UDP/IP via Java NIO.</p>
<p>Library home page: <a href="http://mina.apache.org">http://mina.apache.org</a></p>
<p>Path to dependency file: /webapp/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/mina/mina-core/2.0.0-M6/mina-core-2.0.0-M6.jar</p>
<p>
Dependency Hierarchy:
- apacheds-server-jndi-1.5.5.jar (Root Library)
- apacheds-protocol-ldap-1.5.5.jar
- shared-asn1-codec-0.9.15.jar
- :x: **mina-core-2.0.0-M6.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-marketing/box_mojito/commit/65290aeb818102fa2443a637efdccebebfed1eb9">65290aeb818102fa2443a637efdccebebfed1eb9</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>
In Apache MINA, a specifically crafted, malformed HTTP request may cause the HTTP Header decoder to loop indefinitely. The decoder assumed that the HTTP Header begins at the beginning of the buffer and loops if there is more data than expected. Please update MINA to 2.1.5 or greater.
<p>Publish Date: 2021-11-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-41973>CVE-2021-41973</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-6mcm-j9cj-3vc3">https://github.com/advisories/GHSA-6mcm-j9cj-3vc3</a></p>
<p>Release Date: 2021-11-01</p>
<p>Fix Resolution (org.apache.mina:mina-core): 2.0.22</p>
<p>Direct dependency fix Resolution (org.apache.directory.server:apacheds-server-jndi): 2.0.0.AM26</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-41973 (Medium) detected in mina-core-2.0.0-M6.jar - autoclosed - ## CVE-2021-41973 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mina-core-2.0.0-M6.jar</b></p></summary>
<p>Apache MINA is a network application framework which helps users develop high performance and highly scalable network applications easily. It provides an abstract event-driven asynchronous API over various transports such as TCP/IP and UDP/IP via Java NIO.</p>
<p>Library home page: <a href="http://mina.apache.org">http://mina.apache.org</a></p>
<p>Path to dependency file: /webapp/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/mina/mina-core/2.0.0-M6/mina-core-2.0.0-M6.jar</p>
<p>
Dependency Hierarchy:
- apacheds-server-jndi-1.5.5.jar (Root Library)
- apacheds-protocol-ldap-1.5.5.jar
- shared-asn1-codec-0.9.15.jar
- :x: **mina-core-2.0.0-M6.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-marketing/box_mojito/commit/65290aeb818102fa2443a637efdccebebfed1eb9">65290aeb818102fa2443a637efdccebebfed1eb9</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>
In Apache MINA, a specifically crafted, malformed HTTP request may cause the HTTP Header decoder to loop indefinitely. The decoder assumed that the HTTP Header begins at the beginning of the buffer and loops if there is more data than expected. Please update MINA to 2.1.5 or greater.
<p>Publish Date: 2021-11-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-41973>CVE-2021-41973</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-6mcm-j9cj-3vc3">https://github.com/advisories/GHSA-6mcm-j9cj-3vc3</a></p>
<p>Release Date: 2021-11-01</p>
<p>Fix Resolution (org.apache.mina:mina-core): 2.0.22</p>
<p>Direct dependency fix Resolution (org.apache.directory.server:apacheds-server-jndi): 2.0.0.AM26</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| non_usab | cve medium detected in mina core jar autoclosed cve medium severity vulnerability vulnerable library mina core jar apache mina is a network application framework which helps users develop high performance and highly scalable network applications easily it provides an abstract event driven asynchronous api over various transports such as tcp ip and udp ip via java nio library home page a href path to dependency file webapp pom xml path to vulnerable library home wss scanner repository org apache mina mina core mina core jar dependency hierarchy apacheds server jndi jar root library apacheds protocol ldap jar shared codec jar x mina core jar vulnerable library found in head commit a href found in base branch master vulnerability details in apache mina a specifically crafted malformed http request may cause the http header decoder to loop indefinitely the decoder assumed that the http header begins at the beginning of the buffer and loops if there is more data than expected please update mina to or greater 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 org apache mina mina core direct dependency fix resolution org apache directory server apacheds server jndi check this box to open an automated fix pr | 0 |
14,696 | 9,422,686,898 | IssuesEvent | 2019-04-11 09:55:47 | MISP/MISP | https://api.github.com/repos/MISP/MISP | closed | [event graph] add a thumbnail if an object/attribute is a sample (with an image) | topic:event-graph usability | [event graph] add a thumbnail if an object/attribute is a sample (with an image)
| True | [event graph] add a thumbnail if an object/attribute is a sample (with an image) - [event graph] add a thumbnail if an object/attribute is a sample (with an image)
| usab | add a thumbnail if an object attribute is a sample with an image add a thumbnail if an object attribute is a sample with an image | 1 |
15,586 | 10,148,656,342 | IssuesEvent | 2019-08-05 13:38:32 | nismod/smif | https://api.github.com/repos/nismod/smif | closed | CSVFileStore: reading in scenario data with missing data raises error | bug feature:usability | Given a csv file containing scenario data with one or more dimensions which are correctly specified in the file. If the corresponding data is missing, an error is raised when reading the file.
For example, `demo_dimension` has coordinates `A`,`B`,`C`, `timestep` has elements `2015`, `2020`.
This will work fine:
```csv
timestep,demo_dimension,values
2015,A,0
2015,B,0
2015,C,0
2020,A,0
2020,B,0
2020,C,0
```
This will fail:
```csv
timestep,demo_dimension,values
2015,A,0
2015,B,0
2015,C,
2020,A,0
2020,B,
2020,C,
```
Desired behaviour is to read in the data and fill missing data with NAN | True | CSVFileStore: reading in scenario data with missing data raises error - Given a csv file containing scenario data with one or more dimensions which are correctly specified in the file. If the corresponding data is missing, an error is raised when reading the file.
For example, `demo_dimension` has coordinates `A`,`B`,`C`, `timestep` has elements `2015`, `2020`.
This will work fine:
```csv
timestep,demo_dimension,values
2015,A,0
2015,B,0
2015,C,0
2020,A,0
2020,B,0
2020,C,0
```
This will fail:
```csv
timestep,demo_dimension,values
2015,A,0
2015,B,0
2015,C,
2020,A,0
2020,B,
2020,C,
```
Desired behaviour is to read in the data and fill missing data with NAN | usab | csvfilestore reading in scenario data with missing data raises error given a csv file containing scenario data with one or more dimensions which are correctly specified in the file if the corresponding data is missing an error is raised when reading the file for example demo dimension has coordinates a b c timestep has elements this will work fine csv timestep demo dimension values a b c a b c this will fail csv timestep demo dimension values a b c a b c desired behaviour is to read in the data and fill missing data with nan | 1 |
17,603 | 3,012,747,747 | IssuesEvent | 2015-07-29 02:09:38 | yawlfoundation/yawl | https://api.github.com/repos/yawlfoundation/yawl | closed | [CLOSED] Role hierachies have no effect | auto-migrated Milestone-Release2.0 Priority-Critical Type-Defect | <a href="https://github.com/GoogleCodeExporter"><img src="https://avatars.githubusercontent.com/u/9614759?v=3" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [GoogleCodeExporter](https://github.com/GoogleCodeExporter)**
_Monday Jul 27, 2015 at 03:20 GMT_
_Originally opened as https://github.com/adamsmj/yawl/issues/4_
----
```
When designing a role hierarchy it is expected that a role higher in the
hierarchy when used at runtime is seen as having all the participants of
its descendant roles. At the moment this is not implemented.
```
Original issue reported on code.google.com by `arthurte...@gmail.com` on 18 Jul 2008 at 4:06
| 1.0 | [CLOSED] Role hierachies have no effect - <a href="https://github.com/GoogleCodeExporter"><img src="https://avatars.githubusercontent.com/u/9614759?v=3" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [GoogleCodeExporter](https://github.com/GoogleCodeExporter)**
_Monday Jul 27, 2015 at 03:20 GMT_
_Originally opened as https://github.com/adamsmj/yawl/issues/4_
----
```
When designing a role hierarchy it is expected that a role higher in the
hierarchy when used at runtime is seen as having all the participants of
its descendant roles. At the moment this is not implemented.
```
Original issue reported on code.google.com by `arthurte...@gmail.com` on 18 Jul 2008 at 4:06
| non_usab | role hierachies have no effect issue by monday jul at gmt originally opened as when designing a role hierarchy it is expected that a role higher in the hierarchy when used at runtime is seen as having all the participants of its descendant roles at the moment this is not implemented original issue reported on code google com by arthurte gmail com on jul at | 0 |
2,915 | 3,249,493,881 | IssuesEvent | 2015-10-18 07:14:55 | cortoproject/corto | https://api.github.com/repos/cortoproject/corto | closed | Create a test framework | Corto:QA Corto:Tools Corto:Usability | In order to formalize testing and increase overall productivity when writing tests, a supportive framework would be nice. Of course there is a plethora of testing frameworks out there, so one could ask why build one from scratch?
For a number of reasons.
1. A test framework based on Cortex would work for any programming language that has a binding with the platform. As such, it would ensure conformity across languages in how testcases are build, organized and log their output.
2. The upcoming web bindings and documentation features would complement the test framework perfectly. Basically, the test framework would be extended with realtime visual feedback for free.
3. In future releases bindings will be added that allow building truly distributed applications with Cortex. This in essence would enable the framework - again for free - to act as a distributed test engine.
4. In future releases functionality will be added to the platform that allows for persistent storage of objects. This would, for free, add the capability of the framework to keep track of historic test results.
5. Keeping the test results around in the Cortex object store will allow users to write scripts based on this data.
In summary, this framework will eventually be language agnostic, scriptable, provide real-time visual feedback on the execution of testcases, can manage running testcases on multiple machines simultaneously and store historical results.
That is combination of features that I have not yet seen with any OTS framework. The framework in itself would become a good reason to use the platform.
The framework would not be used just for testing the platform, but should also be used for testing applications build by end users. | True | Create a test framework - In order to formalize testing and increase overall productivity when writing tests, a supportive framework would be nice. Of course there is a plethora of testing frameworks out there, so one could ask why build one from scratch?
For a number of reasons.
1. A test framework based on Cortex would work for any programming language that has a binding with the platform. As such, it would ensure conformity across languages in how testcases are build, organized and log their output.
2. The upcoming web bindings and documentation features would complement the test framework perfectly. Basically, the test framework would be extended with realtime visual feedback for free.
3. In future releases bindings will be added that allow building truly distributed applications with Cortex. This in essence would enable the framework - again for free - to act as a distributed test engine.
4. In future releases functionality will be added to the platform that allows for persistent storage of objects. This would, for free, add the capability of the framework to keep track of historic test results.
5. Keeping the test results around in the Cortex object store will allow users to write scripts based on this data.
In summary, this framework will eventually be language agnostic, scriptable, provide real-time visual feedback on the execution of testcases, can manage running testcases on multiple machines simultaneously and store historical results.
That is combination of features that I have not yet seen with any OTS framework. The framework in itself would become a good reason to use the platform.
The framework would not be used just for testing the platform, but should also be used for testing applications build by end users. | usab | create a test framework in order to formalize testing and increase overall productivity when writing tests a supportive framework would be nice of course there is a plethora of testing frameworks out there so one could ask why build one from scratch for a number of reasons a test framework based on cortex would work for any programming language that has a binding with the platform as such it would ensure conformity across languages in how testcases are build organized and log their output the upcoming web bindings and documentation features would complement the test framework perfectly basically the test framework would be extended with realtime visual feedback for free in future releases bindings will be added that allow building truly distributed applications with cortex this in essence would enable the framework again for free to act as a distributed test engine in future releases functionality will be added to the platform that allows for persistent storage of objects this would for free add the capability of the framework to keep track of historic test results keeping the test results around in the cortex object store will allow users to write scripts based on this data in summary this framework will eventually be language agnostic scriptable provide real time visual feedback on the execution of testcases can manage running testcases on multiple machines simultaneously and store historical results that is combination of features that i have not yet seen with any ots framework the framework in itself would become a good reason to use the platform the framework would not be used just for testing the platform but should also be used for testing applications build by end users | 1 |
13,861 | 23,859,612,000 | IssuesEvent | 2022-09-07 05:26:26 | renovatebot/renovate | https://api.github.com/repos/renovatebot/renovate | opened | Improve branch cache logic | priority-2-high type:refactor status:requirements | ### Describe the proposed change(s).
The branch cache should have this function, which is called at the start of branch processing each run: `syncBranchCache(branchName, branchSha, baseBranchName, baseBranchSha)`
It's logic will be like this:
- If baseBranchName has changed, delete isModified
- If branchSha has changed, delete isModified, isConflicted, isBehindBaseBranch, branchFingerprint
- If baseBranchSha has changed, delete isConflicted, isBehindBaseBranch
- Now sync the fields
During branch processing we can call `setBranchModified(branchName, isModified)`, `setBranchConflicted`, `setBranchBehindBase`, `setBranchFingerprint`. These don’t need SHAs because we assume they were sync’d earlier in the branch processing.
Towards the end of branch processing, if we have pushed a commit (either branch creation or branch updating) then we call this function: `setBranchCommit(branchName, baseBranchName, branchSha, baseBranchSha, branchFingerprint)`. It should:
- If a new branch, set all fields
- If an existing branch, update all fields
- Set parentSha to equal baseBranchSha
- Set isModified, isConflicted and isBehindBaseBranch to `false`
We should remove all git-level caching. It's OK for us to "lose" such existing cache values for one run while we populate the branch cache using the new logic. | 1.0 | Improve branch cache logic - ### Describe the proposed change(s).
The branch cache should have this function, which is called at the start of branch processing each run: `syncBranchCache(branchName, branchSha, baseBranchName, baseBranchSha)`
It's logic will be like this:
- If baseBranchName has changed, delete isModified
- If branchSha has changed, delete isModified, isConflicted, isBehindBaseBranch, branchFingerprint
- If baseBranchSha has changed, delete isConflicted, isBehindBaseBranch
- Now sync the fields
During branch processing we can call `setBranchModified(branchName, isModified)`, `setBranchConflicted`, `setBranchBehindBase`, `setBranchFingerprint`. These don’t need SHAs because we assume they were sync’d earlier in the branch processing.
Towards the end of branch processing, if we have pushed a commit (either branch creation or branch updating) then we call this function: `setBranchCommit(branchName, baseBranchName, branchSha, baseBranchSha, branchFingerprint)`. It should:
- If a new branch, set all fields
- If an existing branch, update all fields
- Set parentSha to equal baseBranchSha
- Set isModified, isConflicted and isBehindBaseBranch to `false`
We should remove all git-level caching. It's OK for us to "lose" such existing cache values for one run while we populate the branch cache using the new logic. | non_usab | improve branch cache logic describe the proposed change s the branch cache should have this function which is called at the start of branch processing each run syncbranchcache branchname branchsha basebranchname basebranchsha it s logic will be like this if basebranchname has changed delete ismodified if branchsha has changed delete ismodified isconflicted isbehindbasebranch branchfingerprint if basebranchsha has changed delete isconflicted isbehindbasebranch now sync the fields during branch processing we can call setbranchmodified branchname ismodified setbranchconflicted setbranchbehindbase setbranchfingerprint these don’t need shas because we assume they were sync’d earlier in the branch processing towards the end of branch processing if we have pushed a commit either branch creation or branch updating then we call this function setbranchcommit branchname basebranchname branchsha basebranchsha branchfingerprint it should if a new branch set all fields if an existing branch update all fields set parentsha to equal basebranchsha set ismodified isconflicted and isbehindbasebranch to false we should remove all git level caching it s ok for us to lose such existing cache values for one run while we populate the branch cache using the new logic | 0 |
13,702 | 8,650,283,992 | IssuesEvent | 2018-11-26 22:01:40 | matomo-org/matomo | https://api.github.com/repos/matomo-org/matomo | closed | Integrate the URL Builder directly into the app | Enhancement Major c: Usability | One of the most useful tools on the website is our URL Builder: https://matomo.org/docs/tracking-campaigns-url-builder/ - This tool should be used generously, as it provides an efficient way to [measure marketing campaigns](https://matomo.org/docs/tracking-campaigns/) and provide insights into conversion rates per channel.
### To make the URL builder as easy and as fast as possible to use, we need to integrate it into Matomo directly.
-> The question remains: what would be the best way to integrate it?
Thoughts:
* it needs to be directly accessible from the Campaigns report.
* Maybe it could be opened in a popover on a click?
| True | Integrate the URL Builder directly into the app - One of the most useful tools on the website is our URL Builder: https://matomo.org/docs/tracking-campaigns-url-builder/ - This tool should be used generously, as it provides an efficient way to [measure marketing campaigns](https://matomo.org/docs/tracking-campaigns/) and provide insights into conversion rates per channel.
### To make the URL builder as easy and as fast as possible to use, we need to integrate it into Matomo directly.
-> The question remains: what would be the best way to integrate it?
Thoughts:
* it needs to be directly accessible from the Campaigns report.
* Maybe it could be opened in a popover on a click?
| usab | integrate the url builder directly into the app one of the most useful tools on the website is our url builder this tool should be used generously as it provides an efficient way to and provide insights into conversion rates per channel to make the url builder as easy and as fast as possible to use we need to integrate it into matomo directly the question remains what would be the best way to integrate it thoughts it needs to be directly accessible from the campaigns report maybe it could be opened in a popover on a click | 1 |
68,419 | 17,274,409,629 | IssuesEvent | 2021-07-23 02:57:17 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | docs: spurious diffs for redact_safe.md | A-build-system C-bug | **Describe the problem**
I'm seeing spurious diffs for `redact_safe.md`.
```
$ rm docs/generated/redact_safe.md; make docs/generated/redact_safe.md
$ git diff
diff --git i/docs/generated/redact_safe.md w/docs/generated/redact_safe.md
index ea1d855d26..05e7dce774 100644
--- i/docs/generated/redact_safe.md
+++ w/docs/generated/redact_safe.md
@@ -34,6 +34,8 @@ pkg/storage/enginepb/mvcc3.go | `MVCCStatsDelta`
pkg/storage/enginepb/mvcc3.go | `*MVCCStats`
pkg/util/hlc/timestamp.go | `Timestamp`
pkg/util/hlc/timestamp.go | `ClockTimestamp`
+vendor/github.com/cockroachdb/pebble/internal/humanize/humanize.go | `FormattedString`
+docs/generated/redact_safe.md:57:vendor/github.com/cockroachdb/pebble/metrics.go:324: // have been registered as safe with redact.RegisterSafeType and does not
pkg/util/log/redact.go | `reflect.TypeOf(true)`
pkg/util/log/redact.go | `reflect.TypeOf(123)`
pkg/util/log/redact.go | `reflect.TypeOf(int8(0))`
@@ -53,3 +55,4 @@ pkg/util/log/redact.go | `reflect.TypeOf(time.Time{})`
pkg/util/log/redact.go | `reflect.TypeOf(time.Duration(0))`
pkg/util/log/redact.go | `reflect.TypeOf(encodingtype.T(0))`
pkg/util/log/redact.go | `reflect.TypeOf(Channel(0))`
+vendor/github.com/cockroachdb/pebble/metrics.go:324: // have been registered as safe with redact.RegisterSafeType and does not
``` | 1.0 | docs: spurious diffs for redact_safe.md - **Describe the problem**
I'm seeing spurious diffs for `redact_safe.md`.
```
$ rm docs/generated/redact_safe.md; make docs/generated/redact_safe.md
$ git diff
diff --git i/docs/generated/redact_safe.md w/docs/generated/redact_safe.md
index ea1d855d26..05e7dce774 100644
--- i/docs/generated/redact_safe.md
+++ w/docs/generated/redact_safe.md
@@ -34,6 +34,8 @@ pkg/storage/enginepb/mvcc3.go | `MVCCStatsDelta`
pkg/storage/enginepb/mvcc3.go | `*MVCCStats`
pkg/util/hlc/timestamp.go | `Timestamp`
pkg/util/hlc/timestamp.go | `ClockTimestamp`
+vendor/github.com/cockroachdb/pebble/internal/humanize/humanize.go | `FormattedString`
+docs/generated/redact_safe.md:57:vendor/github.com/cockroachdb/pebble/metrics.go:324: // have been registered as safe with redact.RegisterSafeType and does not
pkg/util/log/redact.go | `reflect.TypeOf(true)`
pkg/util/log/redact.go | `reflect.TypeOf(123)`
pkg/util/log/redact.go | `reflect.TypeOf(int8(0))`
@@ -53,3 +55,4 @@ pkg/util/log/redact.go | `reflect.TypeOf(time.Time{})`
pkg/util/log/redact.go | `reflect.TypeOf(time.Duration(0))`
pkg/util/log/redact.go | `reflect.TypeOf(encodingtype.T(0))`
pkg/util/log/redact.go | `reflect.TypeOf(Channel(0))`
+vendor/github.com/cockroachdb/pebble/metrics.go:324: // have been registered as safe with redact.RegisterSafeType and does not
``` | non_usab | docs spurious diffs for redact safe md describe the problem i m seeing spurious diffs for redact safe md rm docs generated redact safe md make docs generated redact safe md git diff diff git i docs generated redact safe md w docs generated redact safe md index i docs generated redact safe md w docs generated redact safe md pkg storage enginepb go mvccstatsdelta pkg storage enginepb go mvccstats pkg util hlc timestamp go timestamp pkg util hlc timestamp go clocktimestamp vendor github com cockroachdb pebble internal humanize humanize go formattedstring docs generated redact safe md vendor github com cockroachdb pebble metrics go have been registered as safe with redact registersafetype and does not pkg util log redact go reflect typeof true pkg util log redact go reflect typeof pkg util log redact go reflect typeof pkg util log redact go reflect typeof time time pkg util log redact go reflect typeof time duration pkg util log redact go reflect typeof encodingtype t pkg util log redact go reflect typeof channel vendor github com cockroachdb pebble metrics go have been registered as safe with redact registersafetype and does not | 0 |
4,659 | 3,875,721,010 | IssuesEvent | 2016-04-12 03:01:44 | lionheart/openradar-mirror | https://api.github.com/repos/lionheart/openradar-mirror | opened | 21959720: duplicate languages in settings menu, [NSLocale preferredLanguages] now return different language formats | classification:ui/usability reproducible:always status:open | #### Description
Summary:
[NSLocale preferredLanguages] now return new language format: ru-RU, en-RU and old two-characters format: ru, en. Before in iOS 8 and earler its return correct two-characters format: ru, en. With this bug i can now add multiple copy of one language in settings menu. Two English for example and this will be: array(en-RU, en). I add screenshot with this situation.
Steps to Reproduce:
1) open Settings > General > Language & Region
2) click Other Languages button
3) add some language, Russian for example (now u add two characters ru locale)
4) select Keep English (or what set in your default language)
5) click iPhone Language button
6) select Russian again
7) select Change to Russian
Expected Results:
change language to Russian and menu now show: Russian, English
Actual Results:
we add Russian language again, but with another code format ru-RU and in menu it show two Russian languages: Russian, Russian, English.. we can add two English now and it show: Russian, Russian, English, English
Notes:
Users can be shocked this situation with language list. Developers must now check 2 locales format in the method preferredLanguages, and not one as it was before, its crazy.
Configuration:
iPhone 6 plus, 128GB, WiFi; iPad Air, 32GB, WiFi
So bafore when we click iPhone Language button it change language and show in method preferredLanguages two characters format (ru) without adding duplicate language. But now its add duplicate language with new locale format (ru-RU), i think its actual usability and programming bug. Please contact with me if need addition explanation.
-
Product Version: iOS 9 beta 1 - iOS 9 beta 4 (all betas)
Created: 2015-07-23T12:06:58.354210
Originated: 2015-07-23T16:00:00
Open Radar Link: http://www.openradar.me/21959720 | True | 21959720: duplicate languages in settings menu, [NSLocale preferredLanguages] now return different language formats - #### Description
Summary:
[NSLocale preferredLanguages] now return new language format: ru-RU, en-RU and old two-characters format: ru, en. Before in iOS 8 and earler its return correct two-characters format: ru, en. With this bug i can now add multiple copy of one language in settings menu. Two English for example and this will be: array(en-RU, en). I add screenshot with this situation.
Steps to Reproduce:
1) open Settings > General > Language & Region
2) click Other Languages button
3) add some language, Russian for example (now u add two characters ru locale)
4) select Keep English (or what set in your default language)
5) click iPhone Language button
6) select Russian again
7) select Change to Russian
Expected Results:
change language to Russian and menu now show: Russian, English
Actual Results:
we add Russian language again, but with another code format ru-RU and in menu it show two Russian languages: Russian, Russian, English.. we can add two English now and it show: Russian, Russian, English, English
Notes:
Users can be shocked this situation with language list. Developers must now check 2 locales format in the method preferredLanguages, and not one as it was before, its crazy.
Configuration:
iPhone 6 plus, 128GB, WiFi; iPad Air, 32GB, WiFi
So bafore when we click iPhone Language button it change language and show in method preferredLanguages two characters format (ru) without adding duplicate language. But now its add duplicate language with new locale format (ru-RU), i think its actual usability and programming bug. Please contact with me if need addition explanation.
-
Product Version: iOS 9 beta 1 - iOS 9 beta 4 (all betas)
Created: 2015-07-23T12:06:58.354210
Originated: 2015-07-23T16:00:00
Open Radar Link: http://www.openradar.me/21959720 | usab | duplicate languages in settings menu now return different language formats description summary now return new language format ru ru en ru and old two characters format ru en before in ios and earler its return correct two characters format ru en with this bug i can now add multiple copy of one language in settings menu two english for example and this will be array en ru en i add screenshot with this situation steps to reproduce open settings general language region click other languages button add some language russian for example now u add two characters ru locale select keep english or what set in your default language click iphone language button select russian again select change to russian expected results change language to russian and menu now show russian english actual results we add russian language again but with another code format ru ru and in menu it show two russian languages russian russian english we can add two english now and it show russian russian english english notes users can be shocked this situation with language list developers must now check locales format in the method preferredlanguages and not one as it was before its crazy configuration iphone plus wifi ipad air wifi so bafore when we click iphone language button it change language and show in method preferredlanguages two characters format ru without adding duplicate language but now its add duplicate language with new locale format ru ru i think its actual usability and programming bug please contact with me if need addition explanation product version ios beta ios beta all betas created originated open radar link | 1 |
15,152 | 9,805,600,415 | IssuesEvent | 2019-06-12 09:21:33 | KazDragon/terminalpp | https://api.github.com/repos/KazDragon/terminalpp | closed | An algorithm for iterating elements in a region | Improvement Performance Usability | For example, in the form:
```
for_each_element_in_region(
canvas, {{0, 0}, {17, 3}},
[](terminalpp::element &elem, terminalpp::coordinate_type x, terminalpp::coordinate_type y)
{
// Something
});
```
This would help abstract away for-loops, ensure that regions are iterated in row-major order, etc. | True | An algorithm for iterating elements in a region - For example, in the form:
```
for_each_element_in_region(
canvas, {{0, 0}, {17, 3}},
[](terminalpp::element &elem, terminalpp::coordinate_type x, terminalpp::coordinate_type y)
{
// Something
});
```
This would help abstract away for-loops, ensure that regions are iterated in row-major order, etc. | usab | an algorithm for iterating elements in a region for example in the form for each element in region canvas terminalpp element elem terminalpp coordinate type x terminalpp coordinate type y something this would help abstract away for loops ensure that regions are iterated in row major order etc | 1 |
23,927 | 23,128,124,794 | IssuesEvent | 2022-07-28 07:58:00 | imchillin/Anamnesis | https://api.github.com/repos/imchillin/Anamnesis | closed | disable changing number values with scrollwheel in developer tab | Usability | Using the scrollwheel in the developer tab causes Anamnesis to crash. Disabling input of number values using the scrollwheel in that tab should fix it so that you don't crash when trying to look at actor info.
**Log file**
[2022-06-17-19-44-36.txt](https://github.com/imchillin/Anamnesis/files/8926558/2022-06-17-19-44-36.txt)
| True | disable changing number values with scrollwheel in developer tab - Using the scrollwheel in the developer tab causes Anamnesis to crash. Disabling input of number values using the scrollwheel in that tab should fix it so that you don't crash when trying to look at actor info.
**Log file**
[2022-06-17-19-44-36.txt](https://github.com/imchillin/Anamnesis/files/8926558/2022-06-17-19-44-36.txt)
| usab | disable changing number values with scrollwheel in developer tab using the scrollwheel in the developer tab causes anamnesis to crash disabling input of number values using the scrollwheel in that tab should fix it so that you don t crash when trying to look at actor info log file | 1 |
23,131 | 21,099,789,486 | IssuesEvent | 2022-04-04 13:37:35 | HicServices/RDMP | https://api.github.com/repos/HicServices/RDMP | closed | Change 'Inspection' submenu to 'Run Checks' in context menu | usability | Remove it if not available (disabled or empty) | True | Change 'Inspection' submenu to 'Run Checks' in context menu - Remove it if not available (disabled or empty) | usab | change inspection submenu to run checks in context menu remove it if not available disabled or empty | 1 |
11,684 | 7,360,138,766 | IssuesEvent | 2018-03-10 15:30:51 | MarkBind/markbind | https://api.github.com/repos/MarkBind/markbind | closed | Support user-defined variables | a-AuthorUsability c.Feature p.Medium | Currently we support a special variable `{{baseUrl}}`
It would be useful to allow the user to define more such variables where the value can be any markbind-compliant code fragment.
e.g., we can have a file called `_system\variables.md` which has a format like this:
```
<span id="year">2018</span>
<span id="options">
* yes
* no
* maybe
</span>
```
And the normal files can use `{{year}}` `{{options}}` etc.
A feature like this can help to reduce the verbosity of the code.
| True | Support user-defined variables - Currently we support a special variable `{{baseUrl}}`
It would be useful to allow the user to define more such variables where the value can be any markbind-compliant code fragment.
e.g., we can have a file called `_system\variables.md` which has a format like this:
```
<span id="year">2018</span>
<span id="options">
* yes
* no
* maybe
</span>
```
And the normal files can use `{{year}}` `{{options}}` etc.
A feature like this can help to reduce the verbosity of the code.
| usab | support user defined variables currently we support a special variable baseurl it would be useful to allow the user to define more such variables where the value can be any markbind compliant code fragment e g we can have a file called system variables md which has a format like this yes no maybe and the normal files can use year options etc a feature like this can help to reduce the verbosity of the code | 1 |
181,418 | 14,019,575,828 | IssuesEvent | 2020-10-29 18:22:46 | ansible/awx | https://api.github.com/repos/ansible/awx | closed | Can not Export inventory hosts | component:cli priority:medium state:needs_test type:bug | ##### ISSUE TYPE
- Bug or Fix
##### SUMMARY
Inventory does not include the host when doing an awx export
##### ENVIRONMENT
* AWX version: 13.0.0
* AWX install method: docker on linux
* Ansible version: 2.9.10
* Operating System: CentOS8
* AWX CLI version: 13.0.0
##### STEPS TO REPRODUCE
```
awx export --invetory
```
- Inventory does not include the hosts
##### EXPECTED RESULTS
- Inventory contains the host
##### ACTUAL RESULTS
```
{
"inventory": [
{
"name": "AnsibleServer",
"description": "",
"kind": "",
"host_filter": null,
"variables": "---",
"insights_credential": null,
"organization": {
"name": "Default",
"type": "organization"
},
"natural_key": {
"organization": {
"name": "Default",
"type": "organization"
},
"name": "AnsibleServer",
"type": "inventory"
}
},
{
"name": "Demo Inventory",
"description": "",
"kind": "",
"host_filter": null,
"variables": "",
"insights_credential": null,
"organization": {
"name": "Default",
"type": "organization"
},
"natural_key": {
"organization": {
"name": "Default",
"type": "organization"
},
"name": "Demo Inventory",
"type": "inventory"
}
},
``` | 1.0 | Can not Export inventory hosts - ##### ISSUE TYPE
- Bug or Fix
##### SUMMARY
Inventory does not include the host when doing an awx export
##### ENVIRONMENT
* AWX version: 13.0.0
* AWX install method: docker on linux
* Ansible version: 2.9.10
* Operating System: CentOS8
* AWX CLI version: 13.0.0
##### STEPS TO REPRODUCE
```
awx export --invetory
```
- Inventory does not include the hosts
##### EXPECTED RESULTS
- Inventory contains the host
##### ACTUAL RESULTS
```
{
"inventory": [
{
"name": "AnsibleServer",
"description": "",
"kind": "",
"host_filter": null,
"variables": "---",
"insights_credential": null,
"organization": {
"name": "Default",
"type": "organization"
},
"natural_key": {
"organization": {
"name": "Default",
"type": "organization"
},
"name": "AnsibleServer",
"type": "inventory"
}
},
{
"name": "Demo Inventory",
"description": "",
"kind": "",
"host_filter": null,
"variables": "",
"insights_credential": null,
"organization": {
"name": "Default",
"type": "organization"
},
"natural_key": {
"organization": {
"name": "Default",
"type": "organization"
},
"name": "Demo Inventory",
"type": "inventory"
}
},
``` | non_usab | can not export inventory hosts issue type bug or fix summary inventory does not include the host when doing an awx export environment awx version awx install method docker on linux ansible version operating system awx cli version steps to reproduce awx export invetory inventory does not include the hosts expected results inventory contains the host actual results inventory name ansibleserver description kind host filter null variables insights credential null organization name default type organization natural key organization name default type organization name ansibleserver type inventory name demo inventory description kind host filter null variables insights credential null organization name default type organization natural key organization name default type organization name demo inventory type inventory | 0 |
13,116 | 8,292,327,990 | IssuesEvent | 2018-09-20 00:10:17 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | opened | Reusable blocks with images cannot be edited after importing to another site | Reusable Blocks [Type] Question | Steps to reproduce:
1. Create a reusable block with a gallery of images.
1. Open the block library by clicking on the inserter in the top toolbar.
1. Click the gear icon in the "Reusable" section in the block library.
1. Click "Export as JSON" for the reusable block from step 1.
1. Open a different site and go to Posts > Add New.
1. Open the block library by clicking on the inserter in the top toolbar.
1. Click the gear icon in the "Reusable" section in the block library.
1. Click the "Import from JSON" button at the top.
1. Select the block exported from the other site.
1. Try to edit the gallery images.
<strong>Result:</strong> the images are not actually imported and therefore cannot be modified via the imported reusable block. The following set of errors appears in the console for each image when the block loads:
> GET http://madefortesting.com/wp-json/wp/v2/media/14448?context=edit 404 (Not Found)
> index.js?ver=1537381499:1
> Uncaught (in promise) {code: "rest_post_invalid_id", message: "Invalid post ID.", data: {…}}
> index.js?ver=1537381499:1
<sup>Seen at http://madefortesting.com/wp-admin/post.php?post=616&action=edit running WordPress 4.9.8 and Gutenberg 3.9.0-rc.2 using Chrome 69.0.3497.92 on macOS 10.13.6.</sup>
**Note:** I used a gallery block in this test, but the problem applies to other blocks with images such as Cover Image.
What should happen for images inside reusable blocks? Should they be imported too? This seems complex. 🙂 | True | Reusable blocks with images cannot be edited after importing to another site - Steps to reproduce:
1. Create a reusable block with a gallery of images.
1. Open the block library by clicking on the inserter in the top toolbar.
1. Click the gear icon in the "Reusable" section in the block library.
1. Click "Export as JSON" for the reusable block from step 1.
1. Open a different site and go to Posts > Add New.
1. Open the block library by clicking on the inserter in the top toolbar.
1. Click the gear icon in the "Reusable" section in the block library.
1. Click the "Import from JSON" button at the top.
1. Select the block exported from the other site.
1. Try to edit the gallery images.
<strong>Result:</strong> the images are not actually imported and therefore cannot be modified via the imported reusable block. The following set of errors appears in the console for each image when the block loads:
> GET http://madefortesting.com/wp-json/wp/v2/media/14448?context=edit 404 (Not Found)
> index.js?ver=1537381499:1
> Uncaught (in promise) {code: "rest_post_invalid_id", message: "Invalid post ID.", data: {…}}
> index.js?ver=1537381499:1
<sup>Seen at http://madefortesting.com/wp-admin/post.php?post=616&action=edit running WordPress 4.9.8 and Gutenberg 3.9.0-rc.2 using Chrome 69.0.3497.92 on macOS 10.13.6.</sup>
**Note:** I used a gallery block in this test, but the problem applies to other blocks with images such as Cover Image.
What should happen for images inside reusable blocks? Should they be imported too? This seems complex. 🙂 | usab | reusable blocks with images cannot be edited after importing to another site steps to reproduce create a reusable block with a gallery of images open the block library by clicking on the inserter in the top toolbar click the gear icon in the reusable section in the block library click export as json for the reusable block from step open a different site and go to posts add new open the block library by clicking on the inserter in the top toolbar click the gear icon in the reusable section in the block library click the import from json button at the top select the block exported from the other site try to edit the gallery images result the images are not actually imported and therefore cannot be modified via the imported reusable block the following set of errors appears in the console for each image when the block loads get not found index js ver uncaught in promise code rest post invalid id message invalid post id data … index js ver seen at running wordpress and gutenberg rc using chrome on macos note i used a gallery block in this test but the problem applies to other blocks with images such as cover image what should happen for images inside reusable blocks should they be imported too this seems complex 🙂 | 1 |
234,054 | 25,793,453,861 | IssuesEvent | 2022-12-10 09:43:07 | turkdevops/karma | https://api.github.com/repos/turkdevops/karma | closed | CVE-2018-20676 (Medium) detected in bootstrap-3.3.2.min.js - autoclosed | security vulnerability | ## CVE-2018-20676 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bootstrap-3.3.2.min.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /node_modules/knuth-shuffle-seeded/index.html</p>
<p>Path to vulnerable library: /node_modules/knuth-shuffle-seeded/index.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/karma/commit/7c03032a10da3be9eafae1355bcf84abf75d4fa6">7c03032a10da3be9eafae1355bcf84abf75d4fa6</a></p>
<p>Found in base branch: <b>browser-stack</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>
In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.
<p>Publish Date: 2019-01-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-20676>CVE-2018-20676</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676</a></p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: bootstrap - 3.4.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 | CVE-2018-20676 (Medium) detected in bootstrap-3.3.2.min.js - autoclosed - ## CVE-2018-20676 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bootstrap-3.3.2.min.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /node_modules/knuth-shuffle-seeded/index.html</p>
<p>Path to vulnerable library: /node_modules/knuth-shuffle-seeded/index.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/karma/commit/7c03032a10da3be9eafae1355bcf84abf75d4fa6">7c03032a10da3be9eafae1355bcf84abf75d4fa6</a></p>
<p>Found in base branch: <b>browser-stack</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>
In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.
<p>Publish Date: 2019-01-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-20676>CVE-2018-20676</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676</a></p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: bootstrap - 3.4.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_usab | cve medium detected in bootstrap min js autoclosed cve medium severity vulnerability vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to dependency file node modules knuth shuffle seeded index html path to vulnerable library node modules knuth shuffle seeded index html dependency hierarchy x bootstrap min js vulnerable library found in head commit a href found in base branch browser stack vulnerability details in bootstrap before xss is possible in the tooltip data viewport attribute 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 changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution bootstrap step up your open source security game with mend | 0 |
797,667 | 28,151,365,468 | IssuesEvent | 2023-04-03 01:47:05 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | en.m.wikipedia.org - site is not usable | priority-critical type-webrender-enabled browser-fenix engine-gecko | <!-- @browser: Firefox Mobile 112.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 13; Mobile; rv:109.0) Gecko/112.0 Firefox/112.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @extra_labels: browser-fenix, type-webrender-enabled -->
**URL**: https://en.m.wikipedia.org/wiki/Raster_graphics
**Browser / Version**: Firefox Mobile 112.0
**Operating System**: Android 13
**Tested Another Browser**: Yes Chrome
**Problem type**: Site is not usable
**Description**: Page not loading correctly
**Steps to Reproduce**:
When turned on Built-In Dark Mode in Wikipedia dot org website , Site is not usable as drag is not smooth and highly resistive (viscious like). Drag-nature so much, that even an back and forth scroll take seconds for both fast & slow scroll
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2023/4/1f933e2f-9a72-4774-bc54-a875af495792.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: true</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: true</li><li>image.mem.shared: true</li><li>buildID: 20230330182947</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2023/4/d9dcd2d7-b2c1-4779-be69-50e47555540f)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | en.m.wikipedia.org - site is not usable - <!-- @browser: Firefox Mobile 112.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 13; Mobile; rv:109.0) Gecko/112.0 Firefox/112.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @extra_labels: browser-fenix, type-webrender-enabled -->
**URL**: https://en.m.wikipedia.org/wiki/Raster_graphics
**Browser / Version**: Firefox Mobile 112.0
**Operating System**: Android 13
**Tested Another Browser**: Yes Chrome
**Problem type**: Site is not usable
**Description**: Page not loading correctly
**Steps to Reproduce**:
When turned on Built-In Dark Mode in Wikipedia dot org website , Site is not usable as drag is not smooth and highly resistive (viscious like). Drag-nature so much, that even an back and forth scroll take seconds for both fast & slow scroll
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2023/4/1f933e2f-9a72-4774-bc54-a875af495792.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: true</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: true</li><li>image.mem.shared: true</li><li>buildID: 20230330182947</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2023/4/d9dcd2d7-b2c1-4779-be69-50e47555540f)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_usab | en m wikipedia org site is not usable url browser version firefox mobile operating system android tested another browser yes chrome problem type site is not usable description page not loading correctly steps to reproduce when turned on built in dark mode in wikipedia dot org website site is not usable as drag is not smooth and highly resistive viscious like drag nature so much that even an back and forth scroll take seconds for both fast slow scroll view the screenshot img alt screenshot src browser configuration gfx webrender all true gfx webrender blob images true gfx webrender enabled true image mem shared true buildid channel beta hastouchscreen true mixed active content blocked false mixed passive content blocked false tracking content blocked false from with ❤️ | 0 |
108,724 | 23,654,047,499 | IssuesEvent | 2022-08-26 09:28:43 | thesofproject/linux | https://api.github.com/repos/thesofproject/linux | closed | [BUG] No sound below 100Hz in XPS 15 | bug codec Community | **Describe the bug**
The integrated speakers in my laptop do not output any frequencies below roughly 100Hz.
I have had this issue since I got the computer, several months ago, and tried to find a solution, asking for help [here](https://bugzilla.kernel.org/show_bug.cgi?id=215233) and [here](https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2162), without much success so far.
I have tried out verbs sniffed from Windows, playing with HDAJackRetask and all I could find or think of, and I am hoping that someone here can have some idea I can try out.
One last thing I have noticed is that I am able to reproduce the issue in Windows when the laptop is running out of battery, so I could imagine that there is some power setting that is preventing all the audio from playing in the speakers.
**To Reproduce**
Run this command:
`speaker-test -c2 -D hw:PCH -t sine -f 100`
**Reproduction Rate**
All the time
**Expected behavior**
I would expect to hear something, but no luck
**Impact**
It's quite annoying, it would be great to be able to hear music properly on this laptop.
**Environment**
1) Branch name and commit hash of the 2 repositories: sof (firmware/topology) and linux (kernel driver).
* Kernel: 5.17.15-1-MANJARO
* SOF: 2.1.1.a-1
2) Name of the topology file
* Topology: (I don't know how to check, help? :))
3) Name of the platform(s) on which the bug is observed.
* Platform: Dell XPS 15 9510 (I believe it might affect the 9520 as well, I saw a reddit user complaining about the quality difference with Windows)
**Screenshots or console output**
Please let me know if there is something I can provide. I am not even sure wether sof supports my hardware, or how to set it up (I have it installed but seems like I keep using snd_hda?):
Running `sudo dmesg | grep 'snd\|soc\|sof'` gives me this:
```
[ 0.560740] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 0.560741] software IO TLB: mapped [mem 0x0000000051091000-0x0000000055091000] (64MB)
[ 0.656372] Initializing XFRM netlink socket
[ 1.231085] systemd[1]: Listening on LVM2 poll daemon socket.
[ 1.464247] Bluetooth: HCI socket layer initialized
[ 1.464249] Bluetooth: L2CAP socket layer initialized
[ 1.464250] Bluetooth: SCO socket layer initialized
[ 2.219133] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380
[ 2.219223] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
[ 2.219469] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 2.324761] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC289: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker
[ 2.324764] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 2.324765] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[ 2.324767] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 2.324768] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 2.324769] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19
[ 2.324771] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1b
[ 2.324772] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12
[ 2.992532] Bluetooth: BNEP socket layer initialized
[ 7.132605] wlp0s20f3: associate with 10:da:43:f3:58:c0 (try 1/3)
[ 7.134202] wlp0s20f3: RX AssocResp from 10:da:43:f3:58:c0 (capab=0x1011 status=0 aid=4)
[ 7.140980] wlp0s20f3: associated
[ 13.218728] Bluetooth: RFCOMM socket layer initialized
```
| 1.0 | [BUG] No sound below 100Hz in XPS 15 - **Describe the bug**
The integrated speakers in my laptop do not output any frequencies below roughly 100Hz.
I have had this issue since I got the computer, several months ago, and tried to find a solution, asking for help [here](https://bugzilla.kernel.org/show_bug.cgi?id=215233) and [here](https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2162), without much success so far.
I have tried out verbs sniffed from Windows, playing with HDAJackRetask and all I could find or think of, and I am hoping that someone here can have some idea I can try out.
One last thing I have noticed is that I am able to reproduce the issue in Windows when the laptop is running out of battery, so I could imagine that there is some power setting that is preventing all the audio from playing in the speakers.
**To Reproduce**
Run this command:
`speaker-test -c2 -D hw:PCH -t sine -f 100`
**Reproduction Rate**
All the time
**Expected behavior**
I would expect to hear something, but no luck
**Impact**
It's quite annoying, it would be great to be able to hear music properly on this laptop.
**Environment**
1) Branch name and commit hash of the 2 repositories: sof (firmware/topology) and linux (kernel driver).
* Kernel: 5.17.15-1-MANJARO
* SOF: 2.1.1.a-1
2) Name of the topology file
* Topology: (I don't know how to check, help? :))
3) Name of the platform(s) on which the bug is observed.
* Platform: Dell XPS 15 9510 (I believe it might affect the 9520 as well, I saw a reddit user complaining about the quality difference with Windows)
**Screenshots or console output**
Please let me know if there is something I can provide. I am not even sure wether sof supports my hardware, or how to set it up (I have it installed but seems like I keep using snd_hda?):
Running `sudo dmesg | grep 'snd\|soc\|sof'` gives me this:
```
[ 0.560740] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 0.560741] software IO TLB: mapped [mem 0x0000000051091000-0x0000000055091000] (64MB)
[ 0.656372] Initializing XFRM netlink socket
[ 1.231085] systemd[1]: Listening on LVM2 poll daemon socket.
[ 1.464247] Bluetooth: HCI socket layer initialized
[ 1.464249] Bluetooth: L2CAP socket layer initialized
[ 1.464250] Bluetooth: SCO socket layer initialized
[ 2.219133] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380
[ 2.219223] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
[ 2.219469] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 2.324761] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC289: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker
[ 2.324764] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 2.324765] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[ 2.324767] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 2.324768] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 2.324769] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19
[ 2.324771] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1b
[ 2.324772] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12
[ 2.992532] Bluetooth: BNEP socket layer initialized
[ 7.132605] wlp0s20f3: associate with 10:da:43:f3:58:c0 (try 1/3)
[ 7.134202] wlp0s20f3: RX AssocResp from 10:da:43:f3:58:c0 (capab=0x1011 status=0 aid=4)
[ 7.140980] wlp0s20f3: associated
[ 13.218728] Bluetooth: RFCOMM socket layer initialized
```
| non_usab | no sound below in xps describe the bug the integrated speakers in my laptop do not output any frequencies below roughly i have had this issue since i got the computer several months ago and tried to find a solution asking for help and without much success so far i have tried out verbs sniffed from windows playing with hdajackretask and all i could find or think of and i am hoping that someone here can have some idea i can try out one last thing i have noticed is that i am able to reproduce the issue in windows when the laptop is running out of battery so i could imagine that there is some power setting that is preventing all the audio from playing in the speakers to reproduce run this command speaker test d hw pch t sine f reproduction rate all the time expected behavior i would expect to hear something but no luck impact it s quite annoying it would be great to be able to hear music properly on this laptop environment branch name and commit hash of the repositories sof firmware topology and linux kernel driver kernel manjaro sof a name of the topology file topology i don t know how to check help name of the platform s on which the bug is observed platform dell xps i believe it might affect the as well i saw a reddit user complaining about the quality difference with windows screenshots or console output please let me know if there is something i can provide i am not even sure wether sof supports my hardware or how to set it up i have it installed but seems like i keep using snd hda running sudo dmesg grep snd soc sof gives me this pci dma using software bounce buffering for io swiotlb software io tlb mapped initializing xfrm netlink socket systemd listening on poll daemon socket bluetooth hci socket layer initialized bluetooth socket layer initialized bluetooth sco socket layer initialized snd hda intel dsp detected with pci class subclass prog if info snd hda intel enabling device snd hda intel bound ops audio component bind ops snd hda codec realtek autoconfig for line outs type speaker snd hda codec realtek speaker outs snd hda codec realtek hp outs snd hda codec realtek mono mono out snd hda codec realtek inputs snd hda codec realtek headset mic snd hda codec realtek headphone mic snd hda codec realtek internal mic bluetooth bnep socket layer initialized associate with da try rx assocresp from da capab status aid associated bluetooth rfcomm socket layer initialized | 0 |
14,366 | 9,104,671,477 | IssuesEvent | 2019-02-20 18:47:19 | openstreetmap/iD | https://api.github.com/repos/openstreetmap/iD | closed | Better pane handling at narrow widths | touch-mobile-tablet usability | Now that the sidebar is resizable, it looks pointless to width-constrain the panes like this. Currently the user can drag the sidebar over the panes, which is okay. We should think of ways to make this more mobile-friendly.
<img width="398" alt="screen shot 2019-02-14 at 4 22 08 pm" src="https://user-images.githubusercontent.com/2046746/52818423-be62db00-3074-11e9-826b-f54ec7cb33cd.png"> | True | Better pane handling at narrow widths - Now that the sidebar is resizable, it looks pointless to width-constrain the panes like this. Currently the user can drag the sidebar over the panes, which is okay. We should think of ways to make this more mobile-friendly.
<img width="398" alt="screen shot 2019-02-14 at 4 22 08 pm" src="https://user-images.githubusercontent.com/2046746/52818423-be62db00-3074-11e9-826b-f54ec7cb33cd.png"> | usab | better pane handling at narrow widths now that the sidebar is resizable it looks pointless to width constrain the panes like this currently the user can drag the sidebar over the panes which is okay we should think of ways to make this more mobile friendly img width alt screen shot at pm src | 1 |
18,085 | 12,533,378,404 | IssuesEvent | 2020-06-04 17:29:53 | openstreetmap/iD | https://api.github.com/repos/openstreetmap/iD | closed | Magic mouse horizontal scroll doesn't start a map pan | usability | Scrolling vertically with a magic mouse on macOS properly starts to pan the map, and from there you can scroll-to-pan in any direction. However, the same does not work as expected when starting to scroll horizontally. Previously a horizontal scroll could start browser page navigation, but since fixing #5552 it just does nothing. | True | Magic mouse horizontal scroll doesn't start a map pan - Scrolling vertically with a magic mouse on macOS properly starts to pan the map, and from there you can scroll-to-pan in any direction. However, the same does not work as expected when starting to scroll horizontally. Previously a horizontal scroll could start browser page navigation, but since fixing #5552 it just does nothing. | usab | magic mouse horizontal scroll doesn t start a map pan scrolling vertically with a magic mouse on macos properly starts to pan the map and from there you can scroll to pan in any direction however the same does not work as expected when starting to scroll horizontally previously a horizontal scroll could start browser page navigation but since fixing it just does nothing | 1 |
536,708 | 15,712,541,126 | IssuesEvent | 2021-03-27 12:34:21 | sopra-fs21-group-06/remys-best-server | https://api.github.com/repos/sopra-fs21-group-06/remys-best-server | opened | Move either 1 or 11 fields forward using ACE | high priority task | The player can click on one of his marbles already on a playing field and move it either 1 or 11 fields forward.
Time: 3h
This task is part of user story #68 | 1.0 | Move either 1 or 11 fields forward using ACE - The player can click on one of his marbles already on a playing field and move it either 1 or 11 fields forward.
Time: 3h
This task is part of user story #68 | non_usab | move either or fields forward using ace the player can click on one of his marbles already on a playing field and move it either or fields forward time this task is part of user story | 0 |
200,381 | 7,006,837,819 | IssuesEvent | 2017-12-19 10:00:56 | Prospress/woocommerce-subscribe-all-the-things | https://api.github.com/repos/Prospress/woocommerce-subscribe-all-the-things | closed | Subscription Management: Grouping and Deletion of Bundle Types | feature priority:high request scale:medium status:has-pr status:in-progress ux | L1 of #222
- [x] Prevent child PB/CP/MnM items from being deleted individually.
- [x] Delegate child item deletions to the parent item (remove everything along with the parent).
- [ ] Refactor based on https://github.com/Prospress/woocommerce-subscriptions/issues/2224 ? | 1.0 | Subscription Management: Grouping and Deletion of Bundle Types - L1 of #222
- [x] Prevent child PB/CP/MnM items from being deleted individually.
- [x] Delegate child item deletions to the parent item (remove everything along with the parent).
- [ ] Refactor based on https://github.com/Prospress/woocommerce-subscriptions/issues/2224 ? | non_usab | subscription management grouping and deletion of bundle types of prevent child pb cp mnm items from being deleted individually delegate child item deletions to the parent item remove everything along with the parent refactor based on | 0 |
387,894 | 11,471,591,616 | IssuesEvent | 2020-02-09 12:17:32 | dkfans/keeperfx | https://api.github.com/repos/dkfans/keeperfx | closed | Fire/Time Bomb not used on doors/heart | Priority-Low Status-WontFix Type-Enhancement | Like the title says: creatures with Fire Bomb or Time Bomb spells do not use them on doors or on the Dungeon Heart. | 1.0 | Fire/Time Bomb not used on doors/heart - Like the title says: creatures with Fire Bomb or Time Bomb spells do not use them on doors or on the Dungeon Heart. | non_usab | fire time bomb not used on doors heart like the title says creatures with fire bomb or time bomb spells do not use them on doors or on the dungeon heart | 0 |
9,093 | 6,145,618,638 | IssuesEvent | 2017-06-27 12:01:14 | Virtual-Labs/structural-dynamics-iiith | https://api.github.com/repos/Virtual-Labs/structural-dynamics-iiith | closed | QA_Vibration of M.D.O.F System_Theory_broken-link | Category: Usability Developed by: VLEAD Open-Edx Resolved Severity: S2 Status: Open | Defect Description :
In the Theory page of Vibration of M.D.O.F System experiment, found broken link. Where as the link is navigating to appropriate page in vlab.co.in.
Actual Result :
In the Theory page of Vibration of M.D.O.F System experiment, found broken link.
Environment :
OS: Windows 7, Ubuntu-16.04,Centos-6
Browsers: Firefox-42.0,Chrome-47.0,chromium-45.0
Bandwidth : 100Mbps
Hardware Configuration:8GBRAM
Processor:i5
Attachment
| True | QA_Vibration of M.D.O.F System_Theory_broken-link - Defect Description :
In the Theory page of Vibration of M.D.O.F System experiment, found broken link. Where as the link is navigating to appropriate page in vlab.co.in.
Actual Result :
In the Theory page of Vibration of M.D.O.F System experiment, found broken link.
Environment :
OS: Windows 7, Ubuntu-16.04,Centos-6
Browsers: Firefox-42.0,Chrome-47.0,chromium-45.0
Bandwidth : 100Mbps
Hardware Configuration:8GBRAM
Processor:i5
Attachment
| usab | qa vibration of m d o f system theory broken link defect description in the theory page of vibration of m d o f system experiment found broken link where as the link is navigating to appropriate page in vlab co in actual result in the theory page of vibration of m d o f system experiment found broken link environment os windows ubuntu centos browsers firefox chrome chromium bandwidth hardware configuration processor attachment | 1 |
22,130 | 18,737,800,468 | IssuesEvent | 2021-11-04 09:56:00 | DHI/react-components | https://api.github.com/repos/DHI/react-components | reopened | A confirmation dialog for dirty form | enhancement DHI Reusable | - If user accidentally navigate/type to other link/url or do page refreshed on dirty form, the app should inform the user with confirmation dialog whether he/she want to continue his/her action or do save form before.
- If the form is not dirty, confirmation dialog should not appear.
- The component should be generic. | True | A confirmation dialog for dirty form - - If user accidentally navigate/type to other link/url or do page refreshed on dirty form, the app should inform the user with confirmation dialog whether he/she want to continue his/her action or do save form before.
- If the form is not dirty, confirmation dialog should not appear.
- The component should be generic. | usab | a confirmation dialog for dirty form if user accidentally navigate type to other link url or do page refreshed on dirty form the app should inform the user with confirmation dialog whether he she want to continue his her action or do save form before if the form is not dirty confirmation dialog should not appear the component should be generic | 1 |
12,613 | 7,978,937,723 | IssuesEvent | 2018-07-17 20:00:11 | pulumi/pulumi | https://api.github.com/repos/pulumi/pulumi | closed | Progress output in CI re-echoes warnings | area/cli impact/usability kind/bug | In a customer's CI log, we are seeing the same deprecation warning echoed 100s (or perhaps 1000s) of times, and I suspect it's due to how we re-echo outputs for unchanged resources as progress is made on them. For example
```
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
``` | True | Progress output in CI re-echoes warnings - In a customer's CI log, we are seeing the same deprecation warning echoed 100s (or perhaps 1000s) of times, and I suspect it's due to how we re-echo outputs for unchanged resources as progress is made on them. For example
```
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
* pulumi:pulumi:Stack cts-cts-auto running... 1 warning, 1 info message. warning: urn:pulumi:cts-auto::cts::aws:cloudfront/distribution:Distribution::cts-auto-cdn verification warning: "cache_behavior": [DEPRECATED] Use `ordered_cache_behavior` instead
``` | usab | progress output in ci re echoes warnings in a customer s ci log we are seeing the same deprecation warning echoed or perhaps of times and i suspect it s due to how we re echo outputs for unchanged resources as progress is made on them for example pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead pulumi pulumi stack cts cts auto running warning info message warning urn pulumi cts auto cts aws cloudfront distribution distribution cts auto cdn verification warning cache behavior use ordered cache behavior instead | 1 |
629,247 | 20,026,890,580 | IssuesEvent | 2022-02-01 22:27:36 | Thorium-Sim/thorium | https://api.github.com/repos/Thorium-Sim/thorium | opened | Advancing Timeline Resets Server | type/bug priority/high | ### Requested By: Alex DeBirk
### Priority: High
### Version: 3.5.1
Often (about every 30 seconds), the server will reset itself and back itself back out a few steps. If I press forward on the timeline, the server resets and sets me back three steps on the timeline. Often I will get a single station looping and repeating actions (today I had sensors sending in the same scan request every 30 seconds whenever the loop started). I can't advance the timeline without getting sent back three steps on the timeline. It makes Thorium unusable. I have had the core computer on a windows machine, and then I tried operating core right of the Linux server. I get the same thing. All computers are hard wired to each other over a physical switch that is isolated from the school's network.
### Steps to Reproduce
Linux Server, Windows station computers. Core running off the Linux server machine. Create a standard mission with some timeline steps. Attempt to advance the steps, watch it reset itself more often than actually advance. | 1.0 | Advancing Timeline Resets Server - ### Requested By: Alex DeBirk
### Priority: High
### Version: 3.5.1
Often (about every 30 seconds), the server will reset itself and back itself back out a few steps. If I press forward on the timeline, the server resets and sets me back three steps on the timeline. Often I will get a single station looping and repeating actions (today I had sensors sending in the same scan request every 30 seconds whenever the loop started). I can't advance the timeline without getting sent back three steps on the timeline. It makes Thorium unusable. I have had the core computer on a windows machine, and then I tried operating core right of the Linux server. I get the same thing. All computers are hard wired to each other over a physical switch that is isolated from the school's network.
### Steps to Reproduce
Linux Server, Windows station computers. Core running off the Linux server machine. Create a standard mission with some timeline steps. Attempt to advance the steps, watch it reset itself more often than actually advance. | non_usab | advancing timeline resets server requested by alex debirk priority high version often about every seconds the server will reset itself and back itself back out a few steps if i press forward on the timeline the server resets and sets me back three steps on the timeline often i will get a single station looping and repeating actions today i had sensors sending in the same scan request every seconds whenever the loop started i can t advance the timeline without getting sent back three steps on the timeline it makes thorium unusable i have had the core computer on a windows machine and then i tried operating core right of the linux server i get the same thing all computers are hard wired to each other over a physical switch that is isolated from the school s network steps to reproduce linux server windows station computers core running off the linux server machine create a standard mission with some timeline steps attempt to advance the steps watch it reset itself more often than actually advance | 0 |
26,612 | 27,033,685,689 | IssuesEvent | 2023-02-12 14:18:09 | kube-HPC/hkube | https://api.github.com/repos/kube-HPC/hkube | opened | UI small UX chages | Type: Feature usability | - [ ] In pipeline Edit view, move the "Editor veiw" button to the json preview as a "Edit" button.
- [ ] Remove the run raw pipeline button.
- [ ] When opening an algorithm for edit, if the last build attempt failed, the algorithm should open on the builds tab with the last build log expanded.
- [ ] add "Last modified" column to algorithm and pipeline list, so user will be able to sort by last modified.
- [ ] Remove clear button from edit pipeline and simply clear on exit form with out saving. | True | UI small UX chages - - [ ] In pipeline Edit view, move the "Editor veiw" button to the json preview as a "Edit" button.
- [ ] Remove the run raw pipeline button.
- [ ] When opening an algorithm for edit, if the last build attempt failed, the algorithm should open on the builds tab with the last build log expanded.
- [ ] add "Last modified" column to algorithm and pipeline list, so user will be able to sort by last modified.
- [ ] Remove clear button from edit pipeline and simply clear on exit form with out saving. | usab | ui small ux chages in pipeline edit view move the editor veiw button to the json preview as a edit button remove the run raw pipeline button when opening an algorithm for edit if the last build attempt failed the algorithm should open on the builds tab with the last build log expanded add last modified column to algorithm and pipeline list so user will be able to sort by last modified remove clear button from edit pipeline and simply clear on exit form with out saving | 1 |
21,072 | 16,532,025,436 | IssuesEvent | 2021-05-27 07:25:50 | ClickHouse/ClickHouse | https://api.github.com/repos/ClickHouse/ClickHouse | opened | macos compile failed : Undefined symbols for architecture x86_64: re2_st::RE2::Arg::parse_stringpiece | usability | (you don't have to strictly follow this form)
**Describe the issue**
macos compile failed : Undefined symbols for architecture x86_64: re2_st::RE2::Arg::parse_stringpiece
ENV:
```
commit id : a7e95b4ee2284fac1b6c1f466f89e0c1569f5d72
merge date: Date: Thu May 27 08:05:55 2021 +0300
clang version 11.0.0
Target: x86_64-apple-darwin19.6.0
Thread model: posix
InstalledDir: /usr/local/opt/llvm/bin
```
**How to reproduce**
* just build in macos
**Expected behavior**
successfully build
**Error message and/or stacktrace**
```
[ 91%] Built target loggers
[ 91%] Building CXX object src/Functions/CMakeFiles/clickhouse_functions.dir/abs.cpp.o
[ 91%] Building CXX object src/Functions/CMakeFiles/clickhouse_functions.dir/bitAnd.cpp.o
[ 91%] Building CXX object src/Functions/CMakeFiles/clickhouse_functions.dir/bitBoolMaskAnd.cpp.o
[ 91%] Linking CXX executable convert-month-partitioned-parts
Undefined symbols for architecture x86_64:
"re2_st::RE2::Arg::parse_stringpiece(char const*, unsigned long, void*)", referenced from:
re2_st::RE2::Arg::Arg(re2_st::StringPiece*) in libclickhouse_common_iod.a(OptimizedRegularExpression.cpp.o)
ld: symbol(s) not found for architecture x86_64
clang-11: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [utils/keeper-data-dumper/keeper-data-dumper] Error 1
make[1]: *** [utils/keeper-data-dumper/CMakeFiles/keeper-data-dumper.dir/all] Error 2
[ 91%] Building CXX object src/Storages/System/CMakeFiles/clickhouse_storages_system.dir/StorageSystemColumns.cpp.o
Undefined symbols for architecture x86_64:
"re2_st::RE2::Arg::parse_stringpiece(char const*, unsigned long, void*)", referenced from:
re2_st::RE2::Arg::Arg(re2_st::StringPiece*) in libclickhouse_common_iod.a(OptimizedRegularExpression.cpp.o)
ld: symbol(s) not found for architecture x86_64
clang-11: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [utils/zookeeper-adjust-block-numbers-to-parts/zookeeper-adjust-block-numbers-to-parts] Error 1
make[1]: *** [utils/zookeeper-adjust-block-numbers-to-parts/CMakeFiles/zookeeper-adjust-block-numbers-to-parts.dir/all] Error 2
[ 91%] Building CXX object src/Functions/CMakeFiles/clickhouse_functions.dir/bitBoolMaskOr.cpp.o
[ 91%] Building CXX object src/Functions/CMakeFiles/clickhouse_functions.dir/bitNot.cpp.o
Undefined symbols for architecture x86_64:
"re2_st::RE2::Arg::parse_stringpiece(char const*, unsigned long, void*)", referenced from:
re2_st::RE2::Arg::Arg(re2_st::StringPiece*) in libclickhouse_common_iod.a(OptimizedRegularExpression.cpp.o)
ld: symbol(s) not found for architecture x86_64
clang-11: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [utils/wal-dump/wal-dump] Error 1
make[1]: *** [utils/wal-dump/CMakeFiles/wal-dump.dir/all] Error 2
[ 91%] Building CXX object src/Functions/CMakeFiles/clickhouse_functions.dir/bitOr.cpp.o
[ 91%] Building CXX object src/Storages/System/CMakeFiles/clickhouse_storages_system.dir/StorageSystemContributors.cpp.o
[ 91%] Building CXX object src/Storages/System/CMakeFiles/clickhouse_storages_system.dir/StorageSystemCurrentRoles.cpp.o
Undefined symbols for architecture x86_64:
"re2_st::RE2::Arg::parse_stringpiece(char const*, unsigned long, void*)", referenced from:
re2_st::RE2::Arg::Arg(re2_st::StringPiece*) in libclickhouse_common_iod.a(OptimizedRegularExpression.cpp.o)
[ 93%] Building CXX object src/Functions/CMakeFiles/clickhouse_functions.dir/bitRotateLeft.cpp.o
ld: symbol(s) not found for architecture x86_64
clang-11: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [utils/convert-month-partitioned-parts/convert-month-partitioned-parts] Error 1
make[1]: *** [utils/convert-month-partitioned-parts/CMakeFiles/convert-month-partitioned-parts.dir/all] Error 2
[ 93%] Building CXX object src/Storages/System/CMakeFiles/clickhouse_storages_system.dir/StorageSystemDDLWorkerQueue.cpp.o
```
**Additional context**
Add any other context about the problem here.
| True | macos compile failed : Undefined symbols for architecture x86_64: re2_st::RE2::Arg::parse_stringpiece - (you don't have to strictly follow this form)
**Describe the issue**
macos compile failed : Undefined symbols for architecture x86_64: re2_st::RE2::Arg::parse_stringpiece
ENV:
```
commit id : a7e95b4ee2284fac1b6c1f466f89e0c1569f5d72
merge date: Date: Thu May 27 08:05:55 2021 +0300
clang version 11.0.0
Target: x86_64-apple-darwin19.6.0
Thread model: posix
InstalledDir: /usr/local/opt/llvm/bin
```
**How to reproduce**
* just build in macos
**Expected behavior**
successfully build
**Error message and/or stacktrace**
```
[ 91%] Built target loggers
[ 91%] Building CXX object src/Functions/CMakeFiles/clickhouse_functions.dir/abs.cpp.o
[ 91%] Building CXX object src/Functions/CMakeFiles/clickhouse_functions.dir/bitAnd.cpp.o
[ 91%] Building CXX object src/Functions/CMakeFiles/clickhouse_functions.dir/bitBoolMaskAnd.cpp.o
[ 91%] Linking CXX executable convert-month-partitioned-parts
Undefined symbols for architecture x86_64:
"re2_st::RE2::Arg::parse_stringpiece(char const*, unsigned long, void*)", referenced from:
re2_st::RE2::Arg::Arg(re2_st::StringPiece*) in libclickhouse_common_iod.a(OptimizedRegularExpression.cpp.o)
ld: symbol(s) not found for architecture x86_64
clang-11: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [utils/keeper-data-dumper/keeper-data-dumper] Error 1
make[1]: *** [utils/keeper-data-dumper/CMakeFiles/keeper-data-dumper.dir/all] Error 2
[ 91%] Building CXX object src/Storages/System/CMakeFiles/clickhouse_storages_system.dir/StorageSystemColumns.cpp.o
Undefined symbols for architecture x86_64:
"re2_st::RE2::Arg::parse_stringpiece(char const*, unsigned long, void*)", referenced from:
re2_st::RE2::Arg::Arg(re2_st::StringPiece*) in libclickhouse_common_iod.a(OptimizedRegularExpression.cpp.o)
ld: symbol(s) not found for architecture x86_64
clang-11: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [utils/zookeeper-adjust-block-numbers-to-parts/zookeeper-adjust-block-numbers-to-parts] Error 1
make[1]: *** [utils/zookeeper-adjust-block-numbers-to-parts/CMakeFiles/zookeeper-adjust-block-numbers-to-parts.dir/all] Error 2
[ 91%] Building CXX object src/Functions/CMakeFiles/clickhouse_functions.dir/bitBoolMaskOr.cpp.o
[ 91%] Building CXX object src/Functions/CMakeFiles/clickhouse_functions.dir/bitNot.cpp.o
Undefined symbols for architecture x86_64:
"re2_st::RE2::Arg::parse_stringpiece(char const*, unsigned long, void*)", referenced from:
re2_st::RE2::Arg::Arg(re2_st::StringPiece*) in libclickhouse_common_iod.a(OptimizedRegularExpression.cpp.o)
ld: symbol(s) not found for architecture x86_64
clang-11: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [utils/wal-dump/wal-dump] Error 1
make[1]: *** [utils/wal-dump/CMakeFiles/wal-dump.dir/all] Error 2
[ 91%] Building CXX object src/Functions/CMakeFiles/clickhouse_functions.dir/bitOr.cpp.o
[ 91%] Building CXX object src/Storages/System/CMakeFiles/clickhouse_storages_system.dir/StorageSystemContributors.cpp.o
[ 91%] Building CXX object src/Storages/System/CMakeFiles/clickhouse_storages_system.dir/StorageSystemCurrentRoles.cpp.o
Undefined symbols for architecture x86_64:
"re2_st::RE2::Arg::parse_stringpiece(char const*, unsigned long, void*)", referenced from:
re2_st::RE2::Arg::Arg(re2_st::StringPiece*) in libclickhouse_common_iod.a(OptimizedRegularExpression.cpp.o)
[ 93%] Building CXX object src/Functions/CMakeFiles/clickhouse_functions.dir/bitRotateLeft.cpp.o
ld: symbol(s) not found for architecture x86_64
clang-11: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [utils/convert-month-partitioned-parts/convert-month-partitioned-parts] Error 1
make[1]: *** [utils/convert-month-partitioned-parts/CMakeFiles/convert-month-partitioned-parts.dir/all] Error 2
[ 93%] Building CXX object src/Storages/System/CMakeFiles/clickhouse_storages_system.dir/StorageSystemDDLWorkerQueue.cpp.o
```
**Additional context**
Add any other context about the problem here.
| usab | macos compile failed undefined symbols for architecture st arg parse stringpiece you don t have to strictly follow this form describe the issue macos compile failed undefined symbols for architecture st arg parse stringpiece env commit id merge date date thu may clang version target apple thread model posix installeddir usr local opt llvm bin how to reproduce just build in macos expected behavior successfully build error message and or stacktrace built target loggers building cxx object src functions cmakefiles clickhouse functions dir abs cpp o building cxx object src functions cmakefiles clickhouse functions dir bitand cpp o building cxx object src functions cmakefiles clickhouse functions dir bitboolmaskand cpp o linking cxx executable convert month partitioned parts undefined symbols for architecture st arg parse stringpiece char const unsigned long void referenced from st arg arg st stringpiece in libclickhouse common iod a optimizedregularexpression cpp o ld symbol s not found for architecture clang error linker command failed with exit code use v to see invocation make error make error building cxx object src storages system cmakefiles clickhouse storages system dir storagesystemcolumns cpp o undefined symbols for architecture st arg parse stringpiece char const unsigned long void referenced from st arg arg st stringpiece in libclickhouse common iod a optimizedregularexpression cpp o ld symbol s not found for architecture clang error linker command failed with exit code use v to see invocation make error make error building cxx object src functions cmakefiles clickhouse functions dir bitboolmaskor cpp o building cxx object src functions cmakefiles clickhouse functions dir bitnot cpp o undefined symbols for architecture st arg parse stringpiece char const unsigned long void referenced from st arg arg st stringpiece in libclickhouse common iod a optimizedregularexpression cpp o ld symbol s not found for architecture clang error linker command failed with exit code use v to see invocation make error make error building cxx object src functions cmakefiles clickhouse functions dir bitor cpp o building cxx object src storages system cmakefiles clickhouse storages system dir storagesystemcontributors cpp o building cxx object src storages system cmakefiles clickhouse storages system dir storagesystemcurrentroles cpp o undefined symbols for architecture st arg parse stringpiece char const unsigned long void referenced from st arg arg st stringpiece in libclickhouse common iod a optimizedregularexpression cpp o building cxx object src functions cmakefiles clickhouse functions dir bitrotateleft cpp o ld symbol s not found for architecture clang error linker command failed with exit code use v to see invocation make error make error building cxx object src storages system cmakefiles clickhouse storages system dir storagesystemddlworkerqueue cpp o additional context add any other context about the problem here | 1 |
24,286 | 23,592,491,276 | IssuesEvent | 2022-08-23 16:17:17 | godotengine/godot | https://api.github.com/repos/godotengine/godot | closed | Bezier editor in animation player has no inspector for keyframes | bug topic:editor usability regression topic:animation | ### Godot version
v4.0.alpha.custom_build [862da78ee]
### System information
Linux Fedora, Radeon RX 590
### Issue description
When clicking on keyframes in the bezier editor in 4.x, there is no inspector for the keyframes, which makes inserting precise values highly challenging.
Godot3:
Godot4
### Steps to reproduce
Create an animation with curve keyframes, open the curve editor, observe no inspector.
### Minimal reproduction project
_No response_ | True | Bezier editor in animation player has no inspector for keyframes - ### Godot version
v4.0.alpha.custom_build [862da78ee]
### System information
Linux Fedora, Radeon RX 590
### Issue description
When clicking on keyframes in the bezier editor in 4.x, there is no inspector for the keyframes, which makes inserting precise values highly challenging.
Godot3:
Godot4
### Steps to reproduce
Create an animation with curve keyframes, open the curve editor, observe no inspector.
### Minimal reproduction project
_No response_ | usab | bezier editor in animation player has no inspector for keyframes godot version alpha custom build system information linux fedora radeon rx issue description when clicking on keyframes in the bezier editor in x there is no inspector for the keyframes which makes inserting precise values highly challenging steps to reproduce create an animation with curve keyframes open the curve editor observe no inspector minimal reproduction project no response | 1 |
29,335 | 13,099,300,023 | IssuesEvent | 2020-08-03 21:18:03 | aws/aws-sdk-ruby | https://api.github.com/repos/aws/aws-sdk-ruby | closed | SSM Waiter | service-api | Is there going to be waiter names for SSM? It would be nice to be able to do a constant pull to see if the command ran successfully.
http://docs.aws.amazon.com/sdkforruby/api/Aws/SSM/Client.html#waiter_names-instance_method
| 1.0 | SSM Waiter - Is there going to be waiter names for SSM? It would be nice to be able to do a constant pull to see if the command ran successfully.
http://docs.aws.amazon.com/sdkforruby/api/Aws/SSM/Client.html#waiter_names-instance_method
| non_usab | ssm waiter is there going to be waiter names for ssm it would be nice to be able to do a constant pull to see if the command ran successfully | 0 |
631,536 | 20,153,448,419 | IssuesEvent | 2022-02-09 14:30:59 | stackbuilders/hapistrano | https://api.github.com/repos/stackbuilders/hapistrano | closed | Make Haddock step in the CI pipeline clearer in case of failure | low-priority good first issue | As a newcomer developer to the project, after proposing #174 I kept scratching my head as to why the CI checks were failing at the Haddock step with an exit code 1 and no extra details provided. It turns out that the Haddock step:
https://github.com/stackbuilders/hapistrano/blob/db27a71f3d903c2e1b0e78e6d700e04012bfab28/.github/workflows/build-and-test.yml#L53
was checking via `grep` with a regex that the number of modules with 100% documentation was exactly 4 or 5, but in my PR there were 6, so it was failing at the step. This is now being fixed by #175, but I think this kind of confusion could happen to some newcomer in the future.
The two alternatives that come to my mind to make more explicit on what failed would be:
- Rewrite the step in a way that the minimum number of 4 modules with 100% documentation is preserved, maybe without using the `wc -l | grep` trick, or
- Leave the step as-is, but add a message in the Action so that it suggests what might have happened (e.g.: "process failed with exit code 1. Have you checked that the minimum of 4 modules with 100% documentation is fulfilled?") | 1.0 | Make Haddock step in the CI pipeline clearer in case of failure - As a newcomer developer to the project, after proposing #174 I kept scratching my head as to why the CI checks were failing at the Haddock step with an exit code 1 and no extra details provided. It turns out that the Haddock step:
https://github.com/stackbuilders/hapistrano/blob/db27a71f3d903c2e1b0e78e6d700e04012bfab28/.github/workflows/build-and-test.yml#L53
was checking via `grep` with a regex that the number of modules with 100% documentation was exactly 4 or 5, but in my PR there were 6, so it was failing at the step. This is now being fixed by #175, but I think this kind of confusion could happen to some newcomer in the future.
The two alternatives that come to my mind to make more explicit on what failed would be:
- Rewrite the step in a way that the minimum number of 4 modules with 100% documentation is preserved, maybe without using the `wc -l | grep` trick, or
- Leave the step as-is, but add a message in the Action so that it suggests what might have happened (e.g.: "process failed with exit code 1. Have you checked that the minimum of 4 modules with 100% documentation is fulfilled?") | non_usab | make haddock step in the ci pipeline clearer in case of failure as a newcomer developer to the project after proposing i kept scratching my head as to why the ci checks were failing at the haddock step with an exit code and no extra details provided it turns out that the haddock step was checking via grep with a regex that the number of modules with documentation was exactly or but in my pr there were so it was failing at the step this is now being fixed by but i think this kind of confusion could happen to some newcomer in the future the two alternatives that come to my mind to make more explicit on what failed would be rewrite the step in a way that the minimum number of modules with documentation is preserved maybe without using the wc l grep trick or leave the step as is but add a message in the action so that it suggests what might have happened e g process failed with exit code have you checked that the minimum of modules with documentation is fulfilled | 0 |
3,187 | 3,367,796,265 | IssuesEvent | 2015-11-22 13:53:30 | godotengine/godot | https://api.github.com/repos/godotengine/godot | closed | Bug with side scroll bar in the script tab of the editor | bug topic:editor usability | Built on 07 April 2015
OS: Fedora 21
The side scroll bar within the script tab of the editor seems to have a limit at 70 columns even when the code line is longer. You can only access columns > 70 if you mark and drag the code with the mouse or by maximizing the window.
When maximizing, the side-scroll bar disappears completely. If the code line is bigger then the screen, you have to use above mentioned method with the mouse.
Little demo video:
https://youtu.be/eaTYeD1iIws | True | Bug with side scroll bar in the script tab of the editor - Built on 07 April 2015
OS: Fedora 21
The side scroll bar within the script tab of the editor seems to have a limit at 70 columns even when the code line is longer. You can only access columns > 70 if you mark and drag the code with the mouse or by maximizing the window.
When maximizing, the side-scroll bar disappears completely. If the code line is bigger then the screen, you have to use above mentioned method with the mouse.
Little demo video:
https://youtu.be/eaTYeD1iIws | usab | bug with side scroll bar in the script tab of the editor built on april os fedora the side scroll bar within the script tab of the editor seems to have a limit at columns even when the code line is longer you can only access columns if you mark and drag the code with the mouse or by maximizing the window when maximizing the side scroll bar disappears completely if the code line is bigger then the screen you have to use above mentioned method with the mouse little demo video | 1 |
1,466 | 2,855,222,868 | IssuesEvent | 2015-06-02 08:11:04 | Elgg/Elgg | https://api.github.com/repos/Elgg/Elgg | closed | Clarify docs for register, user hook | dev usability docs | From the documentation "register, user" hook:
> Triggered after user registers. Return false to delete the user.
So, it is expected that this hook triggered in ```register_user($username, $password, $name, $email, $allow_multiple_emails = false)``` function and after registering the user successfully. Or at least this function should triggers another hook if the usage of "register, user" is different. This helps developers use this hook every where that ```register_user``` is called (register action, adduser action and etc).
| True | Clarify docs for register, user hook - From the documentation "register, user" hook:
> Triggered after user registers. Return false to delete the user.
So, it is expected that this hook triggered in ```register_user($username, $password, $name, $email, $allow_multiple_emails = false)``` function and after registering the user successfully. Or at least this function should triggers another hook if the usage of "register, user" is different. This helps developers use this hook every where that ```register_user``` is called (register action, adduser action and etc).
| usab | clarify docs for register user hook from the documentation register user hook triggered after user registers return false to delete the user so it is expected that this hook triggered in register user username password name email allow multiple emails false function and after registering the user successfully or at least this function should triggers another hook if the usage of register user is different this helps developers use this hook every where that register user is called register action adduser action and etc | 1 |
7,778 | 5,200,265,463 | IssuesEvent | 2017-01-23 23:16:52 | tbs-sct/gcconnex | https://api.github.com/repos/tbs-sct/gcconnex | closed | GSA results to display title and description in same language (related to language split) | bug search Usability | As a frequent user, when I search for content (where the language of the content has been split in English and French), I need the GSA search result to display the title and description in the same language so that I can find what I'm looking for quicker and in my language of choice.
ex: I search "OutilsGC" in the GSA (GCconnex), the results show me content with "GCTools" as the title, and a French description (see screen shot).
There is also an issue when using the group filter on the group page (https://gcconnex.gc.ca/groups/all?filter=yours).
For content where the language has been split, I get different search results when filtering groups using keyword, depending on if I'm navigating GCconnex in English or in French. Furthermore, I also get different results when filtering groups and using the English work and the French equivalence (GCTools vs OutilsGC).
Example:
Navigating in ENGLISH and filtering groups using English word vs French word.
Navigating in FRENCH and filtering groups using English word vs French word.
| True | GSA results to display title and description in same language (related to language split) - As a frequent user, when I search for content (where the language of the content has been split in English and French), I need the GSA search result to display the title and description in the same language so that I can find what I'm looking for quicker and in my language of choice.
ex: I search "OutilsGC" in the GSA (GCconnex), the results show me content with "GCTools" as the title, and a French description (see screen shot).
There is also an issue when using the group filter on the group page (https://gcconnex.gc.ca/groups/all?filter=yours).
For content where the language has been split, I get different search results when filtering groups using keyword, depending on if I'm navigating GCconnex in English or in French. Furthermore, I also get different results when filtering groups and using the English work and the French equivalence (GCTools vs OutilsGC).
Example:
Navigating in ENGLISH and filtering groups using English word vs French word.
Navigating in FRENCH and filtering groups using English word vs French word.
| usab | gsa results to display title and description in same language related to language split as a frequent user when i search for content where the language of the content has been split in english and french i need the gsa search result to display the title and description in the same language so that i can find what i m looking for quicker and in my language of choice ex i search outilsgc in the gsa gcconnex the results show me content with gctools as the title and a french description see screen shot there is also an issue when using the group filter on the group page for content where the language has been split i get different search results when filtering groups using keyword depending on if i m navigating gcconnex in english or in french furthermore i also get different results when filtering groups and using the english work and the french equivalence gctools vs outilsgc example navigating in english and filtering groups using english word vs french word navigating in french and filtering groups using english word vs french word | 1 |
11,246 | 7,124,051,851 | IssuesEvent | 2018-01-19 17:23:36 | opentargets/webapp | https://api.github.com/repos/opentargets/webapp | opened | Text Mining: Title is not shown completely in Text Mining evidence section | area/usability | ### Observed behaviour
Title was shown as "Altered expression of Butyrophilin (" instead of "Altered expression of Butyrophilin (BTN) and BTN-like (BTNL) genes in intestinal inflammation and colon cancer."
### Expected behaviour
See above.
### Environment
[How did you see the bug?]
* Version: Website
* Browser: Safari
| True | Text Mining: Title is not shown completely in Text Mining evidence section - ### Observed behaviour
Title was shown as "Altered expression of Butyrophilin (" instead of "Altered expression of Butyrophilin (BTN) and BTN-like (BTNL) genes in intestinal inflammation and colon cancer."
### Expected behaviour
See above.
### Environment
[How did you see the bug?]
* Version: Website
* Browser: Safari
| usab | text mining title is not shown completely in text mining evidence section observed behaviour title was shown as altered expression of butyrophilin instead of altered expression of butyrophilin btn and btn like btnl genes in intestinal inflammation and colon cancer expected behaviour see above environment version website browser safari | 1 |
195,115 | 22,288,267,232 | IssuesEvent | 2022-06-12 01:04:17 | SmartBear/readyapi4j | https://api.github.com/repos/SmartBear/readyapi4j | closed | CVE-2018-1000632 (High) detected in dom4j-1.6.1.jar - autoclosed | security vulnerability | ## CVE-2018-1000632 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>dom4j-1.6.1.jar</b></p></summary>
<p>dom4j: the flexible XML framework for Java</p>
<p>Library home page: <a href="http://dom4j.org">http://dom4j.org</a></p>
<p>Path to dependency file: /modules/maven-plugin-tester/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar</p>
<p>
Dependency Hierarchy:
- readyapi4j-maven-plugin-1.0.0-SNAPSHOT.jar (Root Library)
- readyapi4j-facade-1.0.0-SNAPSHOT.jar
- readyapi4j-local-1.0.0-SNAPSHOT.jar
- soapui-testserver-api-5.5.0.jar
- soapui-5.5.0.jar
- reflections-0.9.9-RC1.jar
- :x: **dom4j-1.6.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/SmartBear/readyapi4j/commit/2616e3393c26f490cd18ae49306a09616a7b066f">2616e3393c26f490cd18ae49306a09616a7b066f</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>
dom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element. Methods: addElement, addAttribute that can result in an attacker tampering with XML documents through XML injection. This attack appear to be exploitable via an attacker specifying attributes or elements in the XML document. This vulnerability appears to have been fixed in 2.1.1 or later.
<p>Publish Date: 2018-08-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000632>CVE-2018-1000632</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: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000632">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000632</a></p>
<p>Release Date: 2018-08-20</p>
<p>Fix Resolution: org.dom4j:dom4j:2.0.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"dom4j","packageName":"dom4j","packageVersion":"1.6.1","packageFilePaths":["/modules/maven-plugin-tester/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"com.smartbear.readyapi:readyapi4j-maven-plugin:1.0.0-SNAPSHOT;com.smartbear.readyapi:readyapi4j-facade:1.0.0-SNAPSHOT;com.smartbear.readyapi:readyapi4j-local:1.0.0-SNAPSHOT;com.smartbear.soapui:soapui-testserver-api:5.5.0;com.smartbear.soapui:soapui:5.5.0;org.reflections:reflections:0.9.9-RC1;dom4j:dom4j:1.6.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.dom4j:dom4j:2.0.3","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-1000632","vulnerabilityDetails":"dom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element. Methods: addElement, addAttribute that can result in an attacker tampering with XML documents through XML injection. This attack appear to be exploitable via an attacker specifying attributes or elements in the XML document. This vulnerability appears to have been fixed in 2.1.1 or later.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000632","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2018-1000632 (High) detected in dom4j-1.6.1.jar - autoclosed - ## CVE-2018-1000632 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>dom4j-1.6.1.jar</b></p></summary>
<p>dom4j: the flexible XML framework for Java</p>
<p>Library home page: <a href="http://dom4j.org">http://dom4j.org</a></p>
<p>Path to dependency file: /modules/maven-plugin-tester/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar</p>
<p>
Dependency Hierarchy:
- readyapi4j-maven-plugin-1.0.0-SNAPSHOT.jar (Root Library)
- readyapi4j-facade-1.0.0-SNAPSHOT.jar
- readyapi4j-local-1.0.0-SNAPSHOT.jar
- soapui-testserver-api-5.5.0.jar
- soapui-5.5.0.jar
- reflections-0.9.9-RC1.jar
- :x: **dom4j-1.6.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/SmartBear/readyapi4j/commit/2616e3393c26f490cd18ae49306a09616a7b066f">2616e3393c26f490cd18ae49306a09616a7b066f</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>
dom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element. Methods: addElement, addAttribute that can result in an attacker tampering with XML documents through XML injection. This attack appear to be exploitable via an attacker specifying attributes or elements in the XML document. This vulnerability appears to have been fixed in 2.1.1 or later.
<p>Publish Date: 2018-08-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000632>CVE-2018-1000632</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: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000632">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000632</a></p>
<p>Release Date: 2018-08-20</p>
<p>Fix Resolution: org.dom4j:dom4j:2.0.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"dom4j","packageName":"dom4j","packageVersion":"1.6.1","packageFilePaths":["/modules/maven-plugin-tester/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"com.smartbear.readyapi:readyapi4j-maven-plugin:1.0.0-SNAPSHOT;com.smartbear.readyapi:readyapi4j-facade:1.0.0-SNAPSHOT;com.smartbear.readyapi:readyapi4j-local:1.0.0-SNAPSHOT;com.smartbear.soapui:soapui-testserver-api:5.5.0;com.smartbear.soapui:soapui:5.5.0;org.reflections:reflections:0.9.9-RC1;dom4j:dom4j:1.6.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.dom4j:dom4j:2.0.3","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-1000632","vulnerabilityDetails":"dom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element. Methods: addElement, addAttribute that can result in an attacker tampering with XML documents through XML injection. This attack appear to be exploitable via an attacker specifying attributes or elements in the XML document. This vulnerability appears to have been fixed in 2.1.1 or later.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000632","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_usab | cve high detected in jar autoclosed cve high severity vulnerability vulnerable library jar the flexible xml framework for java library home page a href path to dependency file modules maven plugin tester pom xml path to vulnerable library home wss scanner repository jar home wss scanner repository jar home wss scanner repository jar home wss scanner repository jar home wss scanner repository jar home wss scanner repository jar home wss scanner repository jar home wss scanner repository jar home wss scanner repository jar home wss scanner repository jar home wss scanner repository jar home wss scanner repository jar dependency hierarchy maven plugin snapshot jar root library facade snapshot jar local snapshot jar soapui testserver api jar soapui jar reflections jar x jar vulnerable library found in head commit a href found in base branch master vulnerability details version prior to version contains a cwe xml injection vulnerability in class element methods addelement addattribute that can result in an attacker tampering with xml documents through xml injection this attack appear to be exploitable via an attacker specifying attributes or elements in the xml document this vulnerability appears to have been fixed in or later 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 high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree com smartbear readyapi maven plugin snapshot com smartbear readyapi facade snapshot com smartbear readyapi local snapshot com smartbear soapui soapui testserver api com smartbear soapui soapui org reflections reflections isminimumfixversionavailable true minimumfixversion org isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails version prior to version contains a cwe xml injection vulnerability in class element methods addelement addattribute that can result in an attacker tampering with xml documents through xml injection this attack appear to be exploitable via an attacker specifying attributes or elements in the xml document this vulnerability appears to have been fixed in or later vulnerabilityurl | 0 |
25,915 | 26,098,790,711 | IssuesEvent | 2022-12-27 02:33:49 | julianmichael/debate | https://api.github.com/repos/julianmichael/debate | closed | Make FacilitatorPanel a separate interface from DebatePage | usability | * Gets rid of the "setting up" debate state
* Can allow for creating multiple debates at once or in sequence (e.g., with similar settings)
* Allows us to remove the header bar in DebatePage, or at least make it more compact | True | Make FacilitatorPanel a separate interface from DebatePage - * Gets rid of the "setting up" debate state
* Can allow for creating multiple debates at once or in sequence (e.g., with similar settings)
* Allows us to remove the header bar in DebatePage, or at least make it more compact | usab | make facilitatorpanel a separate interface from debatepage gets rid of the setting up debate state can allow for creating multiple debates at once or in sequence e g with similar settings allows us to remove the header bar in debatepage or at least make it more compact | 1 |
831,841 | 32,062,631,043 | IssuesEvent | 2023-09-24 20:42:45 | containrrr/watchtower | https://api.github.com/repos/containrrr/watchtower | opened | cosign support or other methods to verify integrity of container images | Type: Enhancement Priority: Low Status: Available | ### Is your feature request related to a problem? Please describe.
Hi,
The problem I have is that watchtower updates containers that have been built / released onprem (on harbror repositories) and during the process of image updating no signature check is done.
### Describe the solution you'd like
I would like watchtower to support checking signatures created by cosign.
Cosign supports all container repositories.
see alsho here: https://github.com/sigstore/cosign
then, using docker compose based on your example to run multiple instances that would help a lot to start verifying images:
```
version: '3'
services:
app-signed:
image: myapps/some-app
labels:
- "com.centurylinklabs.watchtower.scope=signed"
app:
image: myapps/some-app-2
labels:
- "com.centurylinklabs.watchtower.scope=myscope"
watchtower-sign:
image: containrrr/watchtower
volumes:
- /var/run/docker.sock:/var/run/docker.sock
command: --interval 30 --scope signed
labels:
- "com.centurylinklabs.watchtower.scope=signed"
watchtower:
image: containrrr/watchtower
volumes:
- /var/run/docker.sock:/var/run/docker.sock
command: --interval 30 --scope myscope
labels:
- "com.centurylinklabs.watchtower.scope=myscope"
```
source: https://containrrr.dev/watchtower/running-multiple-instances/
### Describe alternatives you've considered
I am aware there is docker content trust, but that appears to work only on docker hub (*).
(*) from what i see content trust is enabled on docker official images (for example postgres, mariadb) but many image publishers tend to not sign their image (including watchtower(?)) or there is no support for content trust(?) (google container registry)
### Additional context
_No response_ | 1.0 | cosign support or other methods to verify integrity of container images - ### Is your feature request related to a problem? Please describe.
Hi,
The problem I have is that watchtower updates containers that have been built / released onprem (on harbror repositories) and during the process of image updating no signature check is done.
### Describe the solution you'd like
I would like watchtower to support checking signatures created by cosign.
Cosign supports all container repositories.
see alsho here: https://github.com/sigstore/cosign
then, using docker compose based on your example to run multiple instances that would help a lot to start verifying images:
```
version: '3'
services:
app-signed:
image: myapps/some-app
labels:
- "com.centurylinklabs.watchtower.scope=signed"
app:
image: myapps/some-app-2
labels:
- "com.centurylinklabs.watchtower.scope=myscope"
watchtower-sign:
image: containrrr/watchtower
volumes:
- /var/run/docker.sock:/var/run/docker.sock
command: --interval 30 --scope signed
labels:
- "com.centurylinklabs.watchtower.scope=signed"
watchtower:
image: containrrr/watchtower
volumes:
- /var/run/docker.sock:/var/run/docker.sock
command: --interval 30 --scope myscope
labels:
- "com.centurylinklabs.watchtower.scope=myscope"
```
source: https://containrrr.dev/watchtower/running-multiple-instances/
### Describe alternatives you've considered
I am aware there is docker content trust, but that appears to work only on docker hub (*).
(*) from what i see content trust is enabled on docker official images (for example postgres, mariadb) but many image publishers tend to not sign their image (including watchtower(?)) or there is no support for content trust(?) (google container registry)
### Additional context
_No response_ | non_usab | cosign support or other methods to verify integrity of container images is your feature request related to a problem please describe hi the problem i have is that watchtower updates containers that have been built released onprem on harbror repositories and during the process of image updating no signature check is done describe the solution you d like i would like watchtower to support checking signatures created by cosign cosign supports all container repositories see alsho here then using docker compose based on your example to run multiple instances that would help a lot to start verifying images version services app signed image myapps some app labels com centurylinklabs watchtower scope signed app image myapps some app labels com centurylinklabs watchtower scope myscope watchtower sign image containrrr watchtower volumes var run docker sock var run docker sock command interval scope signed labels com centurylinklabs watchtower scope signed watchtower image containrrr watchtower volumes var run docker sock var run docker sock command interval scope myscope labels com centurylinklabs watchtower scope myscope source describe alternatives you ve considered i am aware there is docker content trust but that appears to work only on docker hub from what i see content trust is enabled on docker official images for example postgres mariadb but many image publishers tend to not sign their image including watchtower or there is no support for content trust google container registry additional context no response | 0 |
136,549 | 5,284,501,756 | IssuesEvent | 2017-02-08 00:34:02 | imrogues/abstract | https://api.github.com/repos/imrogues/abstract | opened | Printing Something | [priority] low [status] accepted [type] feature | ### Description
Implement printing functionality.
---
### Issue Checklist
- [ ] Write the `puts` function.
All issues in milestone: [5 Extending](https://github.com/imrogues/abstract/milestone/5)
---
### Assignees
- [ ] Final assign @imrogues | 1.0 | Printing Something - ### Description
Implement printing functionality.
---
### Issue Checklist
- [ ] Write the `puts` function.
All issues in milestone: [5 Extending](https://github.com/imrogues/abstract/milestone/5)
---
### Assignees
- [ ] Final assign @imrogues | non_usab | printing something description implement printing functionality issue checklist write the puts function all issues in milestone assignees final assign imrogues | 0 |
24,842 | 24,369,583,535 | IssuesEvent | 2022-10-03 18:03:04 | StarArawn/bevy_ecs_tilemap | https://api.github.com/repos/StarArawn/bevy_ecs_tilemap | closed | TileStorage::get does not check if TilePos is within size of the board | enhancement usability | Currently if you try get a position outside the board, you get an Index out of bounds error.
This can be secured against.
(I can provide a pull request if wanted?)
| True | TileStorage::get does not check if TilePos is within size of the board - Currently if you try get a position outside the board, you get an Index out of bounds error.
This can be secured against.
(I can provide a pull request if wanted?)
| usab | tilestorage get does not check if tilepos is within size of the board currently if you try get a position outside the board you get an index out of bounds error this can be secured against i can provide a pull request if wanted | 1 |
24,729 | 24,197,845,366 | IssuesEvent | 2022-09-24 05:47:41 | ray-project/ray | https://api.github.com/repos/ray-project/ray | closed | No good story for Ray Serve request logging persistence (integrations) | serve stale usability | How can we help users do this for integrations like:
- Cloudwatch
- Datadog
- Grafana (Loki)
- S3 (or other blob storage)
It's a very common ask, especially for machine learning model serving, to want to capture requests for later training on said requests once labels have been established.
Today users would just use Python to make an external call / API call to store each log, but having a nice out of the box way to export would be a huge value add. | True | No good story for Ray Serve request logging persistence (integrations) - How can we help users do this for integrations like:
- Cloudwatch
- Datadog
- Grafana (Loki)
- S3 (or other blob storage)
It's a very common ask, especially for machine learning model serving, to want to capture requests for later training on said requests once labels have been established.
Today users would just use Python to make an external call / API call to store each log, but having a nice out of the box way to export would be a huge value add. | usab | no good story for ray serve request logging persistence integrations how can we help users do this for integrations like cloudwatch datadog grafana loki or other blob storage it s a very common ask especially for machine learning model serving to want to capture requests for later training on said requests once labels have been established today users would just use python to make an external call api call to store each log but having a nice out of the box way to export would be a huge value add | 1 |
505,586 | 14,641,717,053 | IssuesEvent | 2020-12-25 08:05:46 | pingcap/tidb-lightning | https://api.github.com/repos/pingcap/tidb-lightning | opened | Benchmark the speed of importing lots of small tables | difficulty/2-medium feature-request priority/P3 | Verify the speed of importing 2048 tables, each table having size 150 MB (thus total size = 300 GB). Previously in v2.1.16 this only effectively achieved 5x concurrency at 26 MB/s. Now that in 5.0 we may want to check again if things have improved. | 1.0 | Benchmark the speed of importing lots of small tables - Verify the speed of importing 2048 tables, each table having size 150 MB (thus total size = 300 GB). Previously in v2.1.16 this only effectively achieved 5x concurrency at 26 MB/s. Now that in 5.0 we may want to check again if things have improved. | non_usab | benchmark the speed of importing lots of small tables verify the speed of importing tables each table having size mb thus total size gb previously in this only effectively achieved concurrency at mb s now that in we may want to check again if things have improved | 0 |
11,875 | 7,496,684,202 | IssuesEvent | 2018-04-08 12:10:20 | godotengine/godot | https://api.github.com/repos/godotengine/godot | closed | Saving scripts with the shortcut (CTRL+S) while in fullscreen mode (CTRL+SHIFT+F11) doesn't do anything | bug topic:editor usability | **Operating system or device - Godot version:** 2.1.2
**Issue description:**
This is a minor issue.
Trying to save scripts with the save shortcut while in fullscreen mode does not work. You must either save manually with File > Save **(Save All also does not work!)** or exit fullscreen mode, save with the shortcut then reenter fullscreen mode.
**Steps to reproduce:**
Press CTRL+SHIFT+F11 while editing a script > make a change > press CTRL+S > notice the changes aren't saved.
| True | Saving scripts with the shortcut (CTRL+S) while in fullscreen mode (CTRL+SHIFT+F11) doesn't do anything - **Operating system or device - Godot version:** 2.1.2
**Issue description:**
This is a minor issue.
Trying to save scripts with the save shortcut while in fullscreen mode does not work. You must either save manually with File > Save **(Save All also does not work!)** or exit fullscreen mode, save with the shortcut then reenter fullscreen mode.
**Steps to reproduce:**
Press CTRL+SHIFT+F11 while editing a script > make a change > press CTRL+S > notice the changes aren't saved.
| usab | saving scripts with the shortcut ctrl s while in fullscreen mode ctrl shift doesn t do anything operating system or device godot version issue description this is a minor issue trying to save scripts with the save shortcut while in fullscreen mode does not work you must either save manually with file save save all also does not work or exit fullscreen mode save with the shortcut then reenter fullscreen mode steps to reproduce press ctrl shift while editing a script make a change press ctrl s notice the changes aren t saved | 1 |
166,404 | 12,952,986,474 | IssuesEvent | 2020-07-19 22:45:36 | WoWManiaUK/Redemption | https://api.github.com/repos/WoWManiaUK/Redemption | opened | [Pets/Warlock] Debuffs staying when summon a new pet | Fix - Ready to Test | **What is Happening:** Debuffs presents in your current pet, stay in a new one if new pet is the same type of your old one.
Example: If your imp take debuffs and you summon a new one, the new imp appear with max health, max energy, without cooldowns, but with debuffs of old imp.
**What Should happen:** Debuffs should be removed when summon a new pet.
Showcase: https://drive.google.com/file/d/1ekyrNHScQIhDM2lya2Nd0q7lOP3nGdWU/view?usp=sharing | 1.0 | [Pets/Warlock] Debuffs staying when summon a new pet - **What is Happening:** Debuffs presents in your current pet, stay in a new one if new pet is the same type of your old one.
Example: If your imp take debuffs and you summon a new one, the new imp appear with max health, max energy, without cooldowns, but with debuffs of old imp.
**What Should happen:** Debuffs should be removed when summon a new pet.
Showcase: https://drive.google.com/file/d/1ekyrNHScQIhDM2lya2Nd0q7lOP3nGdWU/view?usp=sharing | non_usab | debuffs staying when summon a new pet what is happening debuffs presents in your current pet stay in a new one if new pet is the same type of your old one example if your imp take debuffs and you summon a new one the new imp appear with max health max energy without cooldowns but with debuffs of old imp what should happen debuffs should be removed when summon a new pet showcase | 0 |
22,915 | 20,599,015,906 | IssuesEvent | 2022-03-06 00:30:58 | godotengine/godot | https://api.github.com/repos/godotengine/godot | opened | Large amount of opened scene tabs isn't handled correctly | bug topic:editor usability | ### Godot version
ff65d33
### System information
W10
### Issue description
Tested only with empty tabs, but this happens:
When you are on last tab and press the left arrow, it will change the size of tabs, but don't scroll. When you are on the left and press the right arrow, it will jump to the end after few clicks.
### Steps to reproduce
1. Open big amount of scene tabs
2. Use the navigation arrows
### Minimal reproduction project
_No response_ | True | Large amount of opened scene tabs isn't handled correctly - ### Godot version
ff65d33
### System information
W10
### Issue description
Tested only with empty tabs, but this happens:
When you are on last tab and press the left arrow, it will change the size of tabs, but don't scroll. When you are on the left and press the right arrow, it will jump to the end after few clicks.
### Steps to reproduce
1. Open big amount of scene tabs
2. Use the navigation arrows
### Minimal reproduction project
_No response_ | usab | large amount of opened scene tabs isn t handled correctly godot version system information issue description tested only with empty tabs but this happens when you are on last tab and press the left arrow it will change the size of tabs but don t scroll when you are on the left and press the right arrow it will jump to the end after few clicks steps to reproduce open big amount of scene tabs use the navigation arrows minimal reproduction project no response | 1 |
1,909 | 3,025,273,914 | IssuesEvent | 2015-08-03 07:15:42 | lionheart/openradar-mirror | https://api.github.com/repos/lionheart/openradar-mirror | opened | 21437376: API diffs: nullability annotation changes make finding the important api changes hard | classification:ui/usability reproducible:always status:open | #### Description
Summary:
The nullability annotation changes in the OS X 10.11/iOS 9 api diffs make it hard to find the more important changes.
It would be nice to be able to filter them out and only show changes which are not related to nullability annotations.
https://developer.apple.com/library/prerelease/ios/releasenotes/General/iOS90APIDiffs/
https://developer.apple.com/library/prerelease/mac/releasenotes/General/APIDiffsMacOSX10_11/
-
Product Version: OS X 10.11/iOS 9
Created: 2015-06-18T08:09:17.428470
Originated: 2015-06-18T10:09:00
Open Radar Link: http://www.openradar.me/21437376 | True | 21437376: API diffs: nullability annotation changes make finding the important api changes hard - #### Description
Summary:
The nullability annotation changes in the OS X 10.11/iOS 9 api diffs make it hard to find the more important changes.
It would be nice to be able to filter them out and only show changes which are not related to nullability annotations.
https://developer.apple.com/library/prerelease/ios/releasenotes/General/iOS90APIDiffs/
https://developer.apple.com/library/prerelease/mac/releasenotes/General/APIDiffsMacOSX10_11/
-
Product Version: OS X 10.11/iOS 9
Created: 2015-06-18T08:09:17.428470
Originated: 2015-06-18T10:09:00
Open Radar Link: http://www.openradar.me/21437376 | usab | api diffs nullability annotation changes make finding the important api changes hard description summary the nullability annotation changes in the os x ios api diffs make it hard to find the more important changes it would be nice to be able to filter them out and only show changes which are not related to nullability annotations product version os x ios created originated open radar link | 1 |
8,097 | 2,611,452,201 | IssuesEvent | 2015-02-27 05:00:03 | chrsmith/hedgewars | https://api.github.com/repos/chrsmith/hedgewars | closed | can't go in the lower section of the map when zoomed out | auto-migrated Priority-Medium Type-Defect | ```
What steps will reproduce the problem?
1. select a weapon like teleport or homing bee
2. zoom out completely
3. try to place the cursor near the water
What is the expected output? What do you see instead?
the cursor remains stuck on a certain level, at about 3/4 of screen height and
doesn't allow you to select any portion of the map below.
```
Original issue reported on code.google.com by `vittorio...@gmail.com` on 30 Sep 2010 at 9:04
* Merged into: #193 | 1.0 | can't go in the lower section of the map when zoomed out - ```
What steps will reproduce the problem?
1. select a weapon like teleport or homing bee
2. zoom out completely
3. try to place the cursor near the water
What is the expected output? What do you see instead?
the cursor remains stuck on a certain level, at about 3/4 of screen height and
doesn't allow you to select any portion of the map below.
```
Original issue reported on code.google.com by `vittorio...@gmail.com` on 30 Sep 2010 at 9:04
* Merged into: #193 | non_usab | can t go in the lower section of the map when zoomed out what steps will reproduce the problem select a weapon like teleport or homing bee zoom out completely try to place the cursor near the water what is the expected output what do you see instead the cursor remains stuck on a certain level at about of screen height and doesn t allow you to select any portion of the map below original issue reported on code google com by vittorio gmail com on sep at merged into | 0 |
137,220 | 20,106,277,222 | IssuesEvent | 2022-02-07 10:48:32 | UOS-CONNECTION/UOS-CONNECTION | https://api.github.com/repos/UOS-CONNECTION/UOS-CONNECTION | closed | Figma Design | 🎨 Design 🐬 Middle | - [x] Main Page
- [x] About Page
- [x] Login Page
- [ ] SignUp Page
- [ ] Chatting Page
| 1.0 | Figma Design - - [x] Main Page
- [x] About Page
- [x] Login Page
- [ ] SignUp Page
- [ ] Chatting Page
| non_usab | figma design main page about page login page signup page chatting page | 0 |
7,001 | 4,717,206,505 | IssuesEvent | 2016-10-16 14:02:03 | lionheart/openradar-mirror | https://api.github.com/repos/lionheart/openradar-mirror | opened | 27469547: After stopping/finishing a workout, complication and watch face still indicate working in progress | classification:ui/usability reproducible:sometimes status:open | #### Description
Summary:
After stopping/finishing a workout, complication and watch face still indicate working in progress.
Steps to Reproduce:
1. Start a workout (by tapping on last workout type)
2. Wait
3. Stop workout
4. Press button to go back to watch face
Expected Results:
Complication and working indicator at the top should show no workout in progress
Actual Results:
Complication and working indicator at the top show workout in progress. Restarted watch and they no longer do so.
Notes:
Worked correctly in b1 and seems to have worked correctly in b2.
-
Product Version: 3 b
Created: 2016-07-21T11:59:38.680300
Originated: 2016-07-21T19:59:00
Open Radar Link: http://www.openradar.me/27469547 | True | 27469547: After stopping/finishing a workout, complication and watch face still indicate working in progress - #### Description
Summary:
After stopping/finishing a workout, complication and watch face still indicate working in progress.
Steps to Reproduce:
1. Start a workout (by tapping on last workout type)
2. Wait
3. Stop workout
4. Press button to go back to watch face
Expected Results:
Complication and working indicator at the top should show no workout in progress
Actual Results:
Complication and working indicator at the top show workout in progress. Restarted watch and they no longer do so.
Notes:
Worked correctly in b1 and seems to have worked correctly in b2.
-
Product Version: 3 b
Created: 2016-07-21T11:59:38.680300
Originated: 2016-07-21T19:59:00
Open Radar Link: http://www.openradar.me/27469547 | usab | after stopping finishing a workout complication and watch face still indicate working in progress description summary after stopping finishing a workout complication and watch face still indicate working in progress steps to reproduce start a workout by tapping on last workout type wait stop workout press button to go back to watch face expected results complication and working indicator at the top should show no workout in progress actual results complication and working indicator at the top show workout in progress restarted watch and they no longer do so notes worked correctly in and seems to have worked correctly in product version b created originated open radar link | 1 |
73,875 | 9,739,338,506 | IssuesEvent | 2019-06-01 10:26:47 | nunit/nunit.analyzers | https://api.github.com/repos/nunit/nunit.analyzers | closed | Partition the analyzers into categories and create identifier ranges for each category | documentation improvement | Currently, the analyzer identifiers are just consecutively numbered with no meaning behind a given number. Instead we should create ranges for each area of analyzers and reassign the identifiers - similar to what most other analyzer projects do.
**Tasks:**
* Partition the existing analyzers into groups (and perhaps also take into account the existing open issues)
* Create a range of identifiers for each group and reassign identifiers to the analyzers | 1.0 | Partition the analyzers into categories and create identifier ranges for each category - Currently, the analyzer identifiers are just consecutively numbered with no meaning behind a given number. Instead we should create ranges for each area of analyzers and reassign the identifiers - similar to what most other analyzer projects do.
**Tasks:**
* Partition the existing analyzers into groups (and perhaps also take into account the existing open issues)
* Create a range of identifiers for each group and reassign identifiers to the analyzers | non_usab | partition the analyzers into categories and create identifier ranges for each category currently the analyzer identifiers are just consecutively numbered with no meaning behind a given number instead we should create ranges for each area of analyzers and reassign the identifiers similar to what most other analyzer projects do tasks partition the existing analyzers into groups and perhaps also take into account the existing open issues create a range of identifiers for each group and reassign identifiers to the analyzers | 0 |
417,311 | 28,110,332,433 | IssuesEvent | 2023-03-31 06:34:22 | valerietanhx/ped | https://api.github.com/repos/valerietanhx/ped | opened | User guide contains unexplained $ symbol | severity.Low type.DocumentationBug | In some of the features, the format specified has some $ symbols which are not part of the actual command, and their use is not explained.
This might lead to confusion for users who try to input the $.
<!--session: 1680242470377-7fa8de43-fcaa-4f1d-92a8-0938592c8387-->
<!--Version: Web v3.4.7--> | 1.0 | User guide contains unexplained $ symbol - In some of the features, the format specified has some $ symbols which are not part of the actual command, and their use is not explained.
This might lead to confusion for users who try to input the $.
<!--session: 1680242470377-7fa8de43-fcaa-4f1d-92a8-0938592c8387-->
<!--Version: Web v3.4.7--> | non_usab | user guide contains unexplained symbol in some of the features the format specified has some symbols which are not part of the actual command and their use is not explained this might lead to confusion for users who try to input the | 0 |
352,730 | 25,080,378,833 | IssuesEvent | 2022-11-07 18:46:21 | scylladb/scylladb | https://api.github.com/repos/scylladb/scylladb | closed | Doc: fix the file name (the URL name) in the upgrade guide | Documentation | https://docs.scylladb.com/stable/upgrade/upgrade-enterprise/upgrade-guide-from-2021.1-to-2022.1/upgrade-guide-from-2022.1-to-2022.1-image.html
The directory is 2021.1 to 2022.1, but the file name is 2022.1 to 2022.1.
Rename the file to: upgrade-guide-from-2021.1-to-2022.1-image | 1.0 | Doc: fix the file name (the URL name) in the upgrade guide - https://docs.scylladb.com/stable/upgrade/upgrade-enterprise/upgrade-guide-from-2021.1-to-2022.1/upgrade-guide-from-2022.1-to-2022.1-image.html
The directory is 2021.1 to 2022.1, but the file name is 2022.1 to 2022.1.
Rename the file to: upgrade-guide-from-2021.1-to-2022.1-image | non_usab | doc fix the file name the url name in the upgrade guide the directory is to but the file name is to rename the file to upgrade guide from to image | 0 |
436,996 | 12,557,832,960 | IssuesEvent | 2020-06-07 14:10:04 | Eastrall/Rhisis | https://api.github.com/repos/Eastrall/Rhisis | closed | Can't equip arrows | bug priority: critical srv: world sys: inventory v0.4.x | # :beetle: Bug Report
<!-- Enter rhisis version here with format "vX.Y.Z" -->
**Rhisis version: v0.4.3**
## Expected Behavior
Acrobat can equip arrows.
## Current Behavior
Acrobat cannot equip arrows, however, this bug is not 100% reproducible.
## Steps to Reproduce
1. Equip bow.
2. Try to equip arrows. | 1.0 | Can't equip arrows - # :beetle: Bug Report
<!-- Enter rhisis version here with format "vX.Y.Z" -->
**Rhisis version: v0.4.3**
## Expected Behavior
Acrobat can equip arrows.
## Current Behavior
Acrobat cannot equip arrows, however, this bug is not 100% reproducible.
## Steps to Reproduce
1. Equip bow.
2. Try to equip arrows. | non_usab | can t equip arrows beetle bug report rhisis version expected behavior acrobat can equip arrows current behavior acrobat cannot equip arrows however this bug is not reproducible steps to reproduce equip bow try to equip arrows | 0 |
134,795 | 10,932,196,755 | IssuesEvent | 2019-11-23 16:02:59 | nuriu/cemiyet-backend | https://api.github.com/repos/nuriu/cemiyet-backend | closed | Implement missing book-related features. | Priority: Medium Project: Api Project: Application Project: Tests Status: Done Type: Feature | - [x] Genres/ListBooks
- [x] Authors/ListBooks
- [x] Publishers/ListBooks
- [x] Tests | 1.0 | Implement missing book-related features. - - [x] Genres/ListBooks
- [x] Authors/ListBooks
- [x] Publishers/ListBooks
- [x] Tests | non_usab | implement missing book related features genres listbooks authors listbooks publishers listbooks tests | 0 |
14,997 | 26,228,350,157 | IssuesEvent | 2023-01-04 21:02:21 | dpkg-i-foo-deb/libre-asi | https://api.github.com/repos/dpkg-i-foo-deb/libre-asi | opened | Interview Groupping | Functional Requirement | The system must provide a view where the interviews are grouped by their status, started, in progress, finished, canceled, archived | 1.0 | Interview Groupping - The system must provide a view where the interviews are grouped by their status, started, in progress, finished, canceled, archived | non_usab | interview groupping the system must provide a view where the interviews are grouped by their status started in progress finished canceled archived | 0 |
1,612 | 2,906,476,085 | IssuesEvent | 2015-06-19 10:17:54 | tgstation/-tg-station | https://api.github.com/repos/tgstation/-tg-station | closed | Blobs aren't getting the "YOU'RE GOING TO BE THE BLOB" at roundstart | Bug Usability | SERIOUSLY BLOBS POP OUT AND THEY HAVE NO IDEA THAT THEY WERE THE BLOBS WHO BROKE THIS | True | Blobs aren't getting the "YOU'RE GOING TO BE THE BLOB" at roundstart - SERIOUSLY BLOBS POP OUT AND THEY HAVE NO IDEA THAT THEY WERE THE BLOBS WHO BROKE THIS | usab | blobs aren t getting the you re going to be the blob at roundstart seriously blobs pop out and they have no idea that they were the blobs who broke this | 1 |
10,617 | 27,152,967,684 | IssuesEvent | 2023-02-17 04:03:56 | Azure/azure-sdk | https://api.github.com/repos/Azure/azure-sdk | closed | Board Review: Introducing azure-webpubsub-client (Python) and azure-messaging-webpubsub-client (Java) | architecture board-review | Thank you for starting the process for approval of the client library for your Azure service. Thorough review of your client library ensures that your APIs are consistent with the guidelines and the consumers of your client library have a consistently good experience when using Azure.
**The Architecture Board reviews [Track 2 libraries](https://azure.github.io/azure-sdk/general_introduction.html) only.** If your library does not meet this requirement, please reach out to [Architecture Board](adparch@microsoft.com) before creating the issue.
Please reference our [review process guidelines](https://azure.github.io/azure-sdk/policies_reviewprocess.html) to understand what is being asked for in the issue template.
**Before submitting, ensure you adjust the title of the issue appropriately.**
**Note that the required material must be included before a meeting can be scheduled.**
## Contacts and Timeline
* Service team responsible for the client library: Azure Web PubSub Service
* Main contacts: weidxu@microsoft.com, yuchaoyan@microsoft.com
* Expected stable release date for this library: TBD
## About the Service
* Link to documentation introducing/describing the service: https://docs.microsoft.com/azure/azure-web-pubsub/
* Link to the service REST APIs: Not a REST API client. Communication between client and backend uses subprotocol on WebSocket.
* Is the goal to release a Public Preview, Private Preview, or GA? The service has been already GA. Plan for client is first public preview, then GA.
## About the client library
* Name of client library: azure-webpubsub-client (Python) and azure-messaging-webpubsub-client (Java)
* Link to library reference documentation:
* Client spec: https://github.com/Azure/azure-webpubsub/blob/main/protocols/client/client-spec.md
* Wire package:
* JSON: https://docs.microsoft.com/en-us/azure/azure-web-pubsub/reference-json-reliable-webpubsub-subprotocol
* Protobuf: https://docs.microsoft.com/en-us/azure/azure-web-pubsub/reference-protobuf-reliable-webpubsub-
* Is there an existing SDK library? If yes, provide link:
* [.NET SDK Azure.Messaging.WebPubSub.Client](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/webpubsub/Azure.Messaging.WebPubSub.Client)
* [TypeScript SDK azure/web-pubsub-client](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/web-pubsub/web-pubsub-client)
* [Python SDK azure-webpubsub-client (WIP)](https://github.com/Azure/azure-sdk-for-python/tree/webpubsub-client/sdk/webpubsub/azure-webpubsub-client)
* [Java SDK azure-messaging-webpubsub-client (WIP)](https://github.com/weidongxu-microsoft/azure-sdk-for-java/tree/azure-messaging-webpubsub-client/sdk/webpubsub/azure-messaging-webpubsub-client)
* apiview
* [Python apiview](https://apiview.dev/Assemblies/Review/e23e634cecdd4793811106492ab03942)
* [Java apiview](https://apiview.dev/Assemblies/Review/8c899fc98a6f473eb6fc866a76e3f62c), [design discussion](https://github.com/Azure/azure-sdk-for-java/issues/33287)
## Step 1: Champion Scenarios
Ultimately the library should be easy to use for common scenarios that developers want. Consider the following questions when thinking about champion scenarios:
1. What is the app the developer is building that uses your client library?
They use the client library to develop a client app (or webpage) that maintains a websocket connection and pub sub messages.
2. Who is the end-user of the application (the developer's customer)?
3. What features of the API need to be explained in the sample so that someone could use this API in real app?
* Connect
* Disconnect
* JoinGroup
* LeaveGroup
* SendToGroup
* SendEvent
4. How does the **authentication** workflow look?
Access URL in the form of `wss://<service_name>.webpubsub.azure.com/client/hubs/<hub_name>?access_token=<token>`
See Champion Scenario section [here](https://azure.github.io/azure-sdk/policies_reviewprocess.html).
Code is appreciated but optional. Pseudocode is fine.
* Champion scenario 1
* Link to library’s sample folder: [Python, join group and send hello, listen to messages](https://github.com/Azure/azure-sdk-for-python/blob/webpubsub-client/sdk/webpubsub/azure-webpubsub-client/samples/hello_world.py)
* Champion scenario 2
* Link to library’s sample folder: [Java, join group, listen and reply to every messages](https://github.com/weidongxu-microsoft/azure-sdk-for-java/blob/azure-messaging-webpubsub-client/sdk/webpubsub/azure-messaging-webpubsub-client/src/samples/java/com/azure/messaging/webpubsub/client/EchoSample.java)
* …
* Champion scenario n
* Link to library’s sample folder:
## Step 2: Quickstart Samples (Optional)
Include samples demonstrating how to consume the client library if available:
* Create a new resource
* Read the resource
* Modify the resource
* Delete the resource
* Error handling
* Handling race conditions/concurrency issues
## Thank you for your submission!
PS: developers on Shanghai site | 1.0 | Board Review: Introducing azure-webpubsub-client (Python) and azure-messaging-webpubsub-client (Java) - Thank you for starting the process for approval of the client library for your Azure service. Thorough review of your client library ensures that your APIs are consistent with the guidelines and the consumers of your client library have a consistently good experience when using Azure.
**The Architecture Board reviews [Track 2 libraries](https://azure.github.io/azure-sdk/general_introduction.html) only.** If your library does not meet this requirement, please reach out to [Architecture Board](adparch@microsoft.com) before creating the issue.
Please reference our [review process guidelines](https://azure.github.io/azure-sdk/policies_reviewprocess.html) to understand what is being asked for in the issue template.
**Before submitting, ensure you adjust the title of the issue appropriately.**
**Note that the required material must be included before a meeting can be scheduled.**
## Contacts and Timeline
* Service team responsible for the client library: Azure Web PubSub Service
* Main contacts: weidxu@microsoft.com, yuchaoyan@microsoft.com
* Expected stable release date for this library: TBD
## About the Service
* Link to documentation introducing/describing the service: https://docs.microsoft.com/azure/azure-web-pubsub/
* Link to the service REST APIs: Not a REST API client. Communication between client and backend uses subprotocol on WebSocket.
* Is the goal to release a Public Preview, Private Preview, or GA? The service has been already GA. Plan for client is first public preview, then GA.
## About the client library
* Name of client library: azure-webpubsub-client (Python) and azure-messaging-webpubsub-client (Java)
* Link to library reference documentation:
* Client spec: https://github.com/Azure/azure-webpubsub/blob/main/protocols/client/client-spec.md
* Wire package:
* JSON: https://docs.microsoft.com/en-us/azure/azure-web-pubsub/reference-json-reliable-webpubsub-subprotocol
* Protobuf: https://docs.microsoft.com/en-us/azure/azure-web-pubsub/reference-protobuf-reliable-webpubsub-
* Is there an existing SDK library? If yes, provide link:
* [.NET SDK Azure.Messaging.WebPubSub.Client](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/webpubsub/Azure.Messaging.WebPubSub.Client)
* [TypeScript SDK azure/web-pubsub-client](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/web-pubsub/web-pubsub-client)
* [Python SDK azure-webpubsub-client (WIP)](https://github.com/Azure/azure-sdk-for-python/tree/webpubsub-client/sdk/webpubsub/azure-webpubsub-client)
* [Java SDK azure-messaging-webpubsub-client (WIP)](https://github.com/weidongxu-microsoft/azure-sdk-for-java/tree/azure-messaging-webpubsub-client/sdk/webpubsub/azure-messaging-webpubsub-client)
* apiview
* [Python apiview](https://apiview.dev/Assemblies/Review/e23e634cecdd4793811106492ab03942)
* [Java apiview](https://apiview.dev/Assemblies/Review/8c899fc98a6f473eb6fc866a76e3f62c), [design discussion](https://github.com/Azure/azure-sdk-for-java/issues/33287)
## Step 1: Champion Scenarios
Ultimately the library should be easy to use for common scenarios that developers want. Consider the following questions when thinking about champion scenarios:
1. What is the app the developer is building that uses your client library?
They use the client library to develop a client app (or webpage) that maintains a websocket connection and pub sub messages.
2. Who is the end-user of the application (the developer's customer)?
3. What features of the API need to be explained in the sample so that someone could use this API in real app?
* Connect
* Disconnect
* JoinGroup
* LeaveGroup
* SendToGroup
* SendEvent
4. How does the **authentication** workflow look?
Access URL in the form of `wss://<service_name>.webpubsub.azure.com/client/hubs/<hub_name>?access_token=<token>`
See Champion Scenario section [here](https://azure.github.io/azure-sdk/policies_reviewprocess.html).
Code is appreciated but optional. Pseudocode is fine.
* Champion scenario 1
* Link to library’s sample folder: [Python, join group and send hello, listen to messages](https://github.com/Azure/azure-sdk-for-python/blob/webpubsub-client/sdk/webpubsub/azure-webpubsub-client/samples/hello_world.py)
* Champion scenario 2
* Link to library’s sample folder: [Java, join group, listen and reply to every messages](https://github.com/weidongxu-microsoft/azure-sdk-for-java/blob/azure-messaging-webpubsub-client/sdk/webpubsub/azure-messaging-webpubsub-client/src/samples/java/com/azure/messaging/webpubsub/client/EchoSample.java)
* …
* Champion scenario n
* Link to library’s sample folder:
## Step 2: Quickstart Samples (Optional)
Include samples demonstrating how to consume the client library if available:
* Create a new resource
* Read the resource
* Modify the resource
* Delete the resource
* Error handling
* Handling race conditions/concurrency issues
## Thank you for your submission!
PS: developers on Shanghai site | non_usab | board review introducing azure webpubsub client python and azure messaging webpubsub client java thank you for starting the process for approval of the client library for your azure service thorough review of your client library ensures that your apis are consistent with the guidelines and the consumers of your client library have a consistently good experience when using azure the architecture board reviews only if your library does not meet this requirement please reach out to adparch microsoft com before creating the issue please reference our to understand what is being asked for in the issue template before submitting ensure you adjust the title of the issue appropriately note that the required material must be included before a meeting can be scheduled contacts and timeline service team responsible for the client library azure web pubsub service main contacts weidxu microsoft com yuchaoyan microsoft com expected stable release date for this library tbd about the service link to documentation introducing describing the service link to the service rest apis not a rest api client communication between client and backend uses subprotocol on websocket is the goal to release a public preview private preview or ga the service has been already ga plan for client is first public preview then ga about the client library name of client library azure webpubsub client python and azure messaging webpubsub client java link to library reference documentation client spec wire package json protobuf is there an existing sdk library if yes provide link apiview step champion scenarios ultimately the library should be easy to use for common scenarios that developers want consider the following questions when thinking about champion scenarios what is the app the developer is building that uses your client library they use the client library to develop a client app or webpage that maintains a websocket connection and pub sub messages who is the end user of the application the developer s customer what features of the api need to be explained in the sample so that someone could use this api in real app connect disconnect joingroup leavegroup sendtogroup sendevent how does the authentication workflow look access url in the form of wss webpubsub azure com client hubs access token see champion scenario section code is appreciated but optional pseudocode is fine champion scenario link to library’s sample folder champion scenario link to library’s sample folder … champion scenario n link to library’s sample folder step quickstart samples optional include samples demonstrating how to consume the client library if available create a new resource read the resource modify the resource delete the resource error handling handling race conditions concurrency issues thank you for your submission ps developers on shanghai site | 0 |
23,461 | 21,942,875,681 | IssuesEvent | 2022-05-23 20:08:05 | godotengine/godot | https://api.github.com/repos/godotengine/godot | closed | Drag & Drop node to scripts sometimes handles incorrectly | bug topic:editor usability | **Godot version:**
3.1.1 - 3.2beta1
**OS/device including version:**
Win10
**Issue description:**
Sometimes drag&drop behaves incorrectly - instead pushing string to the script it focus to the scene. This is very irritating and should be fixed ASAP.
**Steps to reproduce:**
**Minimal reproduction project:**
It's easy to reproduce in any simple project... | True | Drag & Drop node to scripts sometimes handles incorrectly - **Godot version:**
3.1.1 - 3.2beta1
**OS/device including version:**
Win10
**Issue description:**
Sometimes drag&drop behaves incorrectly - instead pushing string to the script it focus to the scene. This is very irritating and should be fixed ASAP.
**Steps to reproduce:**
**Minimal reproduction project:**
It's easy to reproduce in any simple project... | usab | drag drop node to scripts sometimes handles incorrectly godot version os device including version issue description sometimes drag drop behaves incorrectly instead pushing string to the script it focus to the scene this is very irritating and should be fixed asap steps to reproduce minimal reproduction project it s easy to reproduce in any simple project | 1 |
16,658 | 11,200,185,712 | IssuesEvent | 2020-01-03 20:57:59 | solo-io/gloo | https://api.github.com/repos/solo-io/gloo | opened | Allow Gloo to update boostrap config without downtime | Area: User Experience Impact: S Size: S Type: Enhancement Usability | Some of our bootstrap config cannot be pre-configured, and can only be configured after installation.
To debug some issues, this is too late.
@ilackarms can provide more detail. | True | Allow Gloo to update boostrap config without downtime - Some of our bootstrap config cannot be pre-configured, and can only be configured after installation.
To debug some issues, this is too late.
@ilackarms can provide more detail. | usab | allow gloo to update boostrap config without downtime some of our bootstrap config cannot be pre configured and can only be configured after installation to debug some issues this is too late ilackarms can provide more detail | 1 |
147,095 | 23,163,990,722 | IssuesEvent | 2022-07-29 21:24:33 | MetaMask/metamask-extension | https://api.github.com/repos/MetaMask/metamask-extension | closed | Create documentation for component-library folder | area-documentation design-system | ### Description
Create a readme document to explain what the `ui/components/component-library` folder is for.
The `ui/components/component-library` contains all new design-system componentization work. It's purpose is to separate all new components from current or deprecated components. These components should eventually replace all ui components in `ui/components/ui`. If you have any questions reach out to the design system team on the slack channel https://consensys.slack.com/archives/C0354T27M5M
### Technical details
- Create `README.md` in `ui/components/component-library`
- Link to design-system and IA/Nav
### Acceptance criteria
- Readme exists and clearly outlines what this folder is for and the | 1.0 | Create documentation for component-library folder - ### Description
Create a readme document to explain what the `ui/components/component-library` folder is for.
The `ui/components/component-library` contains all new design-system componentization work. It's purpose is to separate all new components from current or deprecated components. These components should eventually replace all ui components in `ui/components/ui`. If you have any questions reach out to the design system team on the slack channel https://consensys.slack.com/archives/C0354T27M5M
### Technical details
- Create `README.md` in `ui/components/component-library`
- Link to design-system and IA/Nav
### Acceptance criteria
- Readme exists and clearly outlines what this folder is for and the | non_usab | create documentation for component library folder description create a readme document to explain what the ui components component library folder is for the ui components component library contains all new design system componentization work it s purpose is to separate all new components from current or deprecated components these components should eventually replace all ui components in ui components ui if you have any questions reach out to the design system team on the slack channel technical details create readme md in ui components component library link to design system and ia nav acceptance criteria readme exists and clearly outlines what this folder is for and the | 0 |
18,661 | 13,148,584,211 | IssuesEvent | 2020-08-08 22:33:21 | ruthie/listening-app | https://api.github.com/repos/ruthie/listening-app | closed | Home page buttons should be easer to read and or more visually distinct | usability | As there get to be more quiz types, it's going to be hard to find the one you want at a glance | True | Home page buttons should be easer to read and or more visually distinct - As there get to be more quiz types, it's going to be hard to find the one you want at a glance | usab | home page buttons should be easer to read and or more visually distinct as there get to be more quiz types it s going to be hard to find the one you want at a glance | 1 |
393,674 | 27,003,872,423 | IssuesEvent | 2023-02-10 10:04:22 | Avaiga/taipy-doc | https://api.github.com/repos/Avaiga/taipy-doc | closed | Charts - Demonstration code should point to the complete code in taipy-gui | 📈 Improvement 🖰 GUI 📄 Documentation 🟩 Priority: Low | **Description**
Many code samples can be found in the chart control documentation. These are snippets.
It would be far better to be able to point to a complete example that anyone can just run,
List of sanples to expose at this time:
- doc/examples/charts/advanced-unbalanced-datasets
- doc/examples/charts/advanced-annotations
- doc/examples/charts/advanced-shapes
- doc/examples/charts/advanced-selection
- doc/examples/charts/advanced-range-tracking
- doc/examples/charts/bar-simple
- doc/examples/charts/bar-multiple
- doc/examples/charts/bar-stacked
- doc/examples/charts/bar-facing
- doc/examples/charts/basics-simple
- doc/examples/charts/basics-xrange
- doc/examples/charts/basics-title
- doc/examples/charts/basics-multiple-traces
- doc/examples/charts/basics-two-y-axis
- doc/examples/charts/basics-timeline
- doc/examples/charts/bubble-simple
- doc/examples/charts/bubble-symbols
- doc/examples/charts/bubble-hover
- doc/examples/charts/candlestick-simple
- doc/examples/charts/candlestick-styling
- doc/examples/charts/candlestick-timeseries
- doc/examples/charts/continuous-error-simple
- doc/examples/charts/continuous-error-multiple
- doc/examples/charts/error-bars-simple
- doc/examples/charts/error-bars-asymmetric
- doc/examples/charts/filled-area-simple
- doc/examples/charts/filled-area-overlay
- doc/examples/charts/filled-area-stacked
- doc/examples/charts/filled-area-normalized
- doc/examples/charts/funnel-simple
- doc/examples/charts/funnel-multiple
- doc/examples/charts/funnel-styling
- doc/examples/charts/funnel-area
- doc/examples/charts/funnel-area-multiple
- doc/examples/charts/gantt-simple
- doc/examples/charts/heatmap-simple
- doc/examples/charts/heatmap-unbalanced
- doc/examples/charts/heatmap-colorscale
- doc/examples/charts/heatmap-annotated
- doc/examples/charts/heatmap-unequal-cell-sizes
- doc/examples/charts/heatmap-drawing-on-top
- doc/examples/charts/histogram-simple
- doc/examples/charts/histogram-horizontal
- doc/examples/charts/histogram-overlay
- doc/examples/charts/histogram-stacked
- doc/examples/charts/histogram-cumulative
- doc/examples/charts/histogram-normalized
- doc/examples/charts/histogram-binning
- doc/examples/charts/histogram-nbins
- doc/examples/charts/line-style
- doc/examples/charts/line-text
- doc/examples/charts/map-simple
- doc/examples/charts/map-lines
- doc/examples/charts/map-bubbles
- doc/examples/charts/pie-simple
- doc/examples/charts/pie-styling
- doc/examples/charts/pie-multiple
- doc/examples/charts/polar-simple
- doc/examples/charts/polar-area
- doc/examples/charts/polar-multiple
- doc/examples/charts/polar-sector
- doc/examples/charts/polar-angular-axis
- doc/examples/charts/polar-tick-texts
- doc/examples/charts/radar-simple
- doc/examples/charts/radar-multiple
- doc/examples/charts/scatter-classification
- doc/examples/charts/scatter-styling
- doc/examples/charts/scatter-more-styling
- doc/examples/charts/scatter-regression
**Expected change**
Samples have a link to the taipy-gui repository where the entire code sample can be looked at.
| 1.0 | Charts - Demonstration code should point to the complete code in taipy-gui - **Description**
Many code samples can be found in the chart control documentation. These are snippets.
It would be far better to be able to point to a complete example that anyone can just run,
List of sanples to expose at this time:
- doc/examples/charts/advanced-unbalanced-datasets
- doc/examples/charts/advanced-annotations
- doc/examples/charts/advanced-shapes
- doc/examples/charts/advanced-selection
- doc/examples/charts/advanced-range-tracking
- doc/examples/charts/bar-simple
- doc/examples/charts/bar-multiple
- doc/examples/charts/bar-stacked
- doc/examples/charts/bar-facing
- doc/examples/charts/basics-simple
- doc/examples/charts/basics-xrange
- doc/examples/charts/basics-title
- doc/examples/charts/basics-multiple-traces
- doc/examples/charts/basics-two-y-axis
- doc/examples/charts/basics-timeline
- doc/examples/charts/bubble-simple
- doc/examples/charts/bubble-symbols
- doc/examples/charts/bubble-hover
- doc/examples/charts/candlestick-simple
- doc/examples/charts/candlestick-styling
- doc/examples/charts/candlestick-timeseries
- doc/examples/charts/continuous-error-simple
- doc/examples/charts/continuous-error-multiple
- doc/examples/charts/error-bars-simple
- doc/examples/charts/error-bars-asymmetric
- doc/examples/charts/filled-area-simple
- doc/examples/charts/filled-area-overlay
- doc/examples/charts/filled-area-stacked
- doc/examples/charts/filled-area-normalized
- doc/examples/charts/funnel-simple
- doc/examples/charts/funnel-multiple
- doc/examples/charts/funnel-styling
- doc/examples/charts/funnel-area
- doc/examples/charts/funnel-area-multiple
- doc/examples/charts/gantt-simple
- doc/examples/charts/heatmap-simple
- doc/examples/charts/heatmap-unbalanced
- doc/examples/charts/heatmap-colorscale
- doc/examples/charts/heatmap-annotated
- doc/examples/charts/heatmap-unequal-cell-sizes
- doc/examples/charts/heatmap-drawing-on-top
- doc/examples/charts/histogram-simple
- doc/examples/charts/histogram-horizontal
- doc/examples/charts/histogram-overlay
- doc/examples/charts/histogram-stacked
- doc/examples/charts/histogram-cumulative
- doc/examples/charts/histogram-normalized
- doc/examples/charts/histogram-binning
- doc/examples/charts/histogram-nbins
- doc/examples/charts/line-style
- doc/examples/charts/line-text
- doc/examples/charts/map-simple
- doc/examples/charts/map-lines
- doc/examples/charts/map-bubbles
- doc/examples/charts/pie-simple
- doc/examples/charts/pie-styling
- doc/examples/charts/pie-multiple
- doc/examples/charts/polar-simple
- doc/examples/charts/polar-area
- doc/examples/charts/polar-multiple
- doc/examples/charts/polar-sector
- doc/examples/charts/polar-angular-axis
- doc/examples/charts/polar-tick-texts
- doc/examples/charts/radar-simple
- doc/examples/charts/radar-multiple
- doc/examples/charts/scatter-classification
- doc/examples/charts/scatter-styling
- doc/examples/charts/scatter-more-styling
- doc/examples/charts/scatter-regression
**Expected change**
Samples have a link to the taipy-gui repository where the entire code sample can be looked at.
| non_usab | charts demonstration code should point to the complete code in taipy gui description many code samples can be found in the chart control documentation these are snippets it would be far better to be able to point to a complete example that anyone can just run list of sanples to expose at this time doc examples charts advanced unbalanced datasets doc examples charts advanced annotations doc examples charts advanced shapes doc examples charts advanced selection doc examples charts advanced range tracking doc examples charts bar simple doc examples charts bar multiple doc examples charts bar stacked doc examples charts bar facing doc examples charts basics simple doc examples charts basics xrange doc examples charts basics title doc examples charts basics multiple traces doc examples charts basics two y axis doc examples charts basics timeline doc examples charts bubble simple doc examples charts bubble symbols doc examples charts bubble hover doc examples charts candlestick simple doc examples charts candlestick styling doc examples charts candlestick timeseries doc examples charts continuous error simple doc examples charts continuous error multiple doc examples charts error bars simple doc examples charts error bars asymmetric doc examples charts filled area simple doc examples charts filled area overlay doc examples charts filled area stacked doc examples charts filled area normalized doc examples charts funnel simple doc examples charts funnel multiple doc examples charts funnel styling doc examples charts funnel area doc examples charts funnel area multiple doc examples charts gantt simple doc examples charts heatmap simple doc examples charts heatmap unbalanced doc examples charts heatmap colorscale doc examples charts heatmap annotated doc examples charts heatmap unequal cell sizes doc examples charts heatmap drawing on top doc examples charts histogram simple doc examples charts histogram horizontal doc examples charts histogram overlay doc examples charts histogram stacked doc examples charts histogram cumulative doc examples charts histogram normalized doc examples charts histogram binning doc examples charts histogram nbins doc examples charts line style doc examples charts line text doc examples charts map simple doc examples charts map lines doc examples charts map bubbles doc examples charts pie simple doc examples charts pie styling doc examples charts pie multiple doc examples charts polar simple doc examples charts polar area doc examples charts polar multiple doc examples charts polar sector doc examples charts polar angular axis doc examples charts polar tick texts doc examples charts radar simple doc examples charts radar multiple doc examples charts scatter classification doc examples charts scatter styling doc examples charts scatter more styling doc examples charts scatter regression expected change samples have a link to the taipy gui repository where the entire code sample can be looked at | 0 |
20,586 | 15,723,769,648 | IssuesEvent | 2021-03-29 07:56:55 | maykinmedia/archiefvernietigingscomponent | https://api.github.com/repos/maykinmedia/archiefvernietigingscomponent | closed | Als proces eigenaar wil ik bij het motiveren van een voorstel tot aanpassing van de VL gebruik kunnen maken van standaard redenen | Common Ground sprint Prio: Medium proces en usability | zodat ik minder hoef te typen.
Denk bijvoorbeeld aan een pull down met gangbare redenen (zoals hotspot, precedentwerking, relevant voor bedrijfsvoering… )
[overig - usability]
*Clearification*
* As reviewer pick (default) reasons from droplist
* In the admin manage list of top reasons.
* The above x 2 for both reviewers (they have different reasons).
@Mirjam will create some default reasons. | True | Als proces eigenaar wil ik bij het motiveren van een voorstel tot aanpassing van de VL gebruik kunnen maken van standaard redenen - zodat ik minder hoef te typen.
Denk bijvoorbeeld aan een pull down met gangbare redenen (zoals hotspot, precedentwerking, relevant voor bedrijfsvoering… )
[overig - usability]
*Clearification*
* As reviewer pick (default) reasons from droplist
* In the admin manage list of top reasons.
* The above x 2 for both reviewers (they have different reasons).
@Mirjam will create some default reasons. | usab | als proces eigenaar wil ik bij het motiveren van een voorstel tot aanpassing van de vl gebruik kunnen maken van standaard redenen zodat ik minder hoef te typen denk bijvoorbeeld aan een pull down met gangbare redenen zoals hotspot precedentwerking relevant voor bedrijfsvoering… clearification as reviewer pick default reasons from droplist in the admin manage list of top reasons the above x for both reviewers they have different reasons mirjam will create some default reasons | 1 |
246,835 | 18,854,910,527 | IssuesEvent | 2021-11-12 04:07:11 | kimym56/42Project | https://api.github.com/repos/kimym56/42Project | closed | 1110 백앤드 공부 방향성2 | documentation | ## Done
- Spring과 Spring Boot 차이 : Dependency 강화, 편리성, 호환성
https://www.youtube.com/watch?v=6h9qmKWK6Io
- Library와 Framework 차이 : 내가 갖다 쓰는것 vs 나의 코드를 부르는 것 (ReactJS는 둘다 가능)
https://www.youtube.com/watch?v=t9ccIykXTCM
- RN + Spring Boot 방식으로 아래 책으로 우선 훓어보고, 그 이후(12월)에 진행(단, DB부분이 빠져있어서 나중에 추가 공부 필요)
http://www.kyobobook.co.kr/product/detailViewKor.laf?ejkGb=KOR&mallGb=KOR&barcode=9791161755656&orderClick=LAV&Kc=
## ToDo
- 남은 4일동안 UI랑 FE 남은 기능 보완
https://github.com/kimym56/42Project/projects/1#card-69540891
| 1.0 | 1110 백앤드 공부 방향성2 - ## Done
- Spring과 Spring Boot 차이 : Dependency 강화, 편리성, 호환성
https://www.youtube.com/watch?v=6h9qmKWK6Io
- Library와 Framework 차이 : 내가 갖다 쓰는것 vs 나의 코드를 부르는 것 (ReactJS는 둘다 가능)
https://www.youtube.com/watch?v=t9ccIykXTCM
- RN + Spring Boot 방식으로 아래 책으로 우선 훓어보고, 그 이후(12월)에 진행(단, DB부분이 빠져있어서 나중에 추가 공부 필요)
http://www.kyobobook.co.kr/product/detailViewKor.laf?ejkGb=KOR&mallGb=KOR&barcode=9791161755656&orderClick=LAV&Kc=
## ToDo
- 남은 4일동안 UI랑 FE 남은 기능 보완
https://github.com/kimym56/42Project/projects/1#card-69540891
| non_usab | 백앤드 공부 done spring과 spring boot 차이 dependency 강화 편리성 호환성 library와 framework 차이 내가 갖다 쓰는것 vs 나의 코드를 부르는 것 reactjs는 둘다 가능 rn spring boot 방식으로 아래 책으로 우선 훓어보고 그 이후 에 진행 단 db부분이 빠져있어서 나중에 추가 공부 필요 todo 남은 ui랑 fe 남은 기능 보완 | 0 |
96,426 | 12,128,757,375 | IssuesEvent | 2020-04-22 21:06:02 | Opentrons/opentrons | https://api.github.com/repos/Opentrons/opentrons | opened | PD: Confirmation modal on cancelling/deselecting an existing step with changes | :spider: SPDDRS design feature-request protocol designer | # Overview
After #5421, never-saved step forms will prompt the user to confirm if the user cancels the form by navigating away or clicking cancel. To be consistent, we'll probably want to do that with ALL forms that have changes?
# Design
I made this ticket up, maybe we don't really want to do it? Please confirm. Also, if the copy in the modals would differ from #5421, please put it here.
# Acceptance criteria
- [ ] Cancelling a previously-saved step form should prompt for confirmation, only if there are changes
- [ ] Cancelling a previously-saved step form should prompt for confirmation, only if there are changes (clicking another step item, or clicking a terminal item | 2.0 | PD: Confirmation modal on cancelling/deselecting an existing step with changes - # Overview
After #5421, never-saved step forms will prompt the user to confirm if the user cancels the form by navigating away or clicking cancel. To be consistent, we'll probably want to do that with ALL forms that have changes?
# Design
I made this ticket up, maybe we don't really want to do it? Please confirm. Also, if the copy in the modals would differ from #5421, please put it here.
# Acceptance criteria
- [ ] Cancelling a previously-saved step form should prompt for confirmation, only if there are changes
- [ ] Cancelling a previously-saved step form should prompt for confirmation, only if there are changes (clicking another step item, or clicking a terminal item | non_usab | pd confirmation modal on cancelling deselecting an existing step with changes overview after never saved step forms will prompt the user to confirm if the user cancels the form by navigating away or clicking cancel to be consistent we ll probably want to do that with all forms that have changes design i made this ticket up maybe we don t really want to do it please confirm also if the copy in the modals would differ from please put it here acceptance criteria cancelling a previously saved step form should prompt for confirmation only if there are changes cancelling a previously saved step form should prompt for confirmation only if there are changes clicking another step item or clicking a terminal item | 0 |
18,723 | 13,168,406,229 | IssuesEvent | 2020-08-11 12:04:32 | topcoder-platform/qa-fun | https://api.github.com/repos/topcoder-platform/qa-fun | closed | [TCO-20 REGIONAL] [Web-Chrome] Contact us page should provide a form for user to write a message | UX/Usability | Steps:
1. In [web-chrome] click on contact us link down the bottom
Expected result:
This page should provide a form where the user can write a message to the company and provide their name.
Actual result:
No form for message is provided.
Screenshot:
| True | [TCO-20 REGIONAL] [Web-Chrome] Contact us page should provide a form for user to write a message - Steps:
1. In [web-chrome] click on contact us link down the bottom
Expected result:
This page should provide a form where the user can write a message to the company and provide their name.
Actual result:
No form for message is provided.
Screenshot:
| usab | contact us page should provide a form for user to write a message steps in click on contact us link down the bottom expected result this page should provide a form where the user can write a message to the company and provide their name actual result no form for message is provided screenshot | 1 |
17,573 | 12,157,577,415 | IssuesEvent | 2020-04-25 22:45:52 | pulumi/pulumi | https://api.github.com/repos/pulumi/pulumi | opened | Detect default region with `pulumi new` | area/cli impact/usability kind/enhancement | This is a relatively minor CLI UX thing, but it'd be nice if Pulumi would detect my default AWS region while I'm running Pulumi new. In my case, I've set an `AWS_PROFILE` environment variable with a value of `default`, with the following entry in `~/.aws/config`:
```
[profile default]
region = us-west-2
```
But when I run Pulumi new, I get:
```
...
aws:region: The AWS region to deploy into: (us-east-1)
```
I'd expect this to be `us-west-2`, since other Pulumi commands (`preview`, `up`, etc.) pick it up correctly.
Again, just a little thing, but I've hit it enough times now that it was worth taking the time to submit an issue for. 😄 | True | Detect default region with `pulumi new` - This is a relatively minor CLI UX thing, but it'd be nice if Pulumi would detect my default AWS region while I'm running Pulumi new. In my case, I've set an `AWS_PROFILE` environment variable with a value of `default`, with the following entry in `~/.aws/config`:
```
[profile default]
region = us-west-2
```
But when I run Pulumi new, I get:
```
...
aws:region: The AWS region to deploy into: (us-east-1)
```
I'd expect this to be `us-west-2`, since other Pulumi commands (`preview`, `up`, etc.) pick it up correctly.
Again, just a little thing, but I've hit it enough times now that it was worth taking the time to submit an issue for. 😄 | usab | detect default region with pulumi new this is a relatively minor cli ux thing but it d be nice if pulumi would detect my default aws region while i m running pulumi new in my case i ve set an aws profile environment variable with a value of default with the following entry in aws config region us west but when i run pulumi new i get aws region the aws region to deploy into us east i d expect this to be us west since other pulumi commands preview up etc pick it up correctly again just a little thing but i ve hit it enough times now that it was worth taking the time to submit an issue for 😄 | 1 |
393 | 2,587,577,448 | IssuesEvent | 2015-02-17 19:21:02 | spyder-ide/spyder | https://api.github.com/repos/spyder-ide/spyder | closed | Working directory for data and for scrips | 1 star imported invalid Settings Usability | _From [ProkopHa...@gmail.com](https://code.google.com/u/100958146796876347936/) on 2013-06-27T07:37:36Z_
The usually way how spyder is used is data processing
Typically, I have some library of functions/objects which I call "script" which is general and so I wan't to store it in some common directory on the disk. Then I import functions from this library and apply them to data which are stored in different directories anywhere on the computer.
How to do that? ( Maybe I'm just missing how to use spyder enviroment effectivelly. )
1) If I set working directory into directory of scrips, then I would need to write very long path everytime time I wan't to read some data
2) If I set working directory to data directory, then I don't know how to import scrips from other dirrectories into python console which is working in data directory.
Is it currently possible to set these directories as two different paths or enviroment varibales - one as path for importing functions, an other as working directory
Because of that I still find more convenient do it just from linux console. Make script in path like ~/bin
cd to data directory
and run the script on the data
_Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1468_ | True | Working directory for data and for scrips - _From [ProkopHa...@gmail.com](https://code.google.com/u/100958146796876347936/) on 2013-06-27T07:37:36Z_
The usually way how spyder is used is data processing
Typically, I have some library of functions/objects which I call "script" which is general and so I wan't to store it in some common directory on the disk. Then I import functions from this library and apply them to data which are stored in different directories anywhere on the computer.
How to do that? ( Maybe I'm just missing how to use spyder enviroment effectivelly. )
1) If I set working directory into directory of scrips, then I would need to write very long path everytime time I wan't to read some data
2) If I set working directory to data directory, then I don't know how to import scrips from other dirrectories into python console which is working in data directory.
Is it currently possible to set these directories as two different paths or enviroment varibales - one as path for importing functions, an other as working directory
Because of that I still find more convenient do it just from linux console. Make script in path like ~/bin
cd to data directory
and run the script on the data
_Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1468_ | usab | working directory for data and for scrips from on the usually way how spyder is used is data processing typically i have some library of functions objects which i call script which is general and so i wan t to store it in some common directory on the disk then i import functions from this library and apply them to data which are stored in different directories anywhere on the computer how to do that maybe i m just missing how to use spyder enviroment effectivelly if i set working directory into directory of scrips then i would need to write very long path everytime time i wan t to read some data if i set working directory to data directory then i don t know how to import scrips from other dirrectories into python console which is working in data directory is it currently possible to set these directories as two different paths or enviroment varibales one as path for importing functions an other as working directory because of that i still find more convenient do it just from linux console make script in path like bin cd to data directory and run the script on the data original issue | 1 |
1,739 | 3,918,479,277 | IssuesEvent | 2016-04-21 12:42:05 | CartoDB/cartodb | https://api.github.com/repos/CartoDB/cartodb | opened | Detect JSON parse errors from json2csv import errors | Data-services | These are just making the import process crash with a 99999 unknown error and are not specified as user error. | 1.0 | Detect JSON parse errors from json2csv import errors - These are just making the import process crash with a 99999 unknown error and are not specified as user error. | non_usab | detect json parse errors from import errors these are just making the import process crash with a unknown error and are not specified as user error | 0 |
17,262 | 11,845,646,898 | IssuesEvent | 2020-03-24 08:46:24 | raiden-network/raiden | https://api.github.com/repos/raiden-network/raiden | closed | Supply /status endpoint to allow querying status of node | Component / API Flag / Usability Type / Enhancement | ## Abstract
During startup of a raiden node, there currently is no way to tell if the API is working but still starting up, or broken and not accepting connections.
Currently, we must query the API until a connection is accepted, to know whether or not the API
is up and running, and there is no distinction between the API still starting up and the node being broken.
## Proposed Feature
Supply a simple `GET /status` endpoint which returns specifig http status codes indicating the status of the node.
The endpoint returns a `503` if the node/api is still spinning up, a `200` if the API is available and connection errors would indicate issues with the node itself.
## Specification
If the feature is technical in nature please write as detailed as possible a specification of what needs to be built.
```yaml
openapi: "3.0.0"
paths:
/api/status:
get:
operationId: getAPIStatus
summary: Indicate whether or not the API is available yet.
responses:
200:
description: OK
503:
description: Service Unavailable
```
| True | Supply /status endpoint to allow querying status of node - ## Abstract
During startup of a raiden node, there currently is no way to tell if the API is working but still starting up, or broken and not accepting connections.
Currently, we must query the API until a connection is accepted, to know whether or not the API
is up and running, and there is no distinction between the API still starting up and the node being broken.
## Proposed Feature
Supply a simple `GET /status` endpoint which returns specifig http status codes indicating the status of the node.
The endpoint returns a `503` if the node/api is still spinning up, a `200` if the API is available and connection errors would indicate issues with the node itself.
## Specification
If the feature is technical in nature please write as detailed as possible a specification of what needs to be built.
```yaml
openapi: "3.0.0"
paths:
/api/status:
get:
operationId: getAPIStatus
summary: Indicate whether or not the API is available yet.
responses:
200:
description: OK
503:
description: Service Unavailable
```
| usab | supply status endpoint to allow querying status of node abstract during startup of a raiden node there currently is no way to tell if the api is working but still starting up or broken and not accepting connections currently we must query the api until a connection is accepted to know whether or not the api is up and running and there is no distinction between the api still starting up and the node being broken proposed feature supply a simple get status endpoint which returns specifig http status codes indicating the status of the node the endpoint returns a if the node api is still spinning up a if the api is available and connection errors would indicate issues with the node itself specification if the feature is technical in nature please write as detailed as possible a specification of what needs to be built yaml openapi paths api status get operationid getapistatus summary indicate whether or not the api is available yet responses description ok description service unavailable | 1 |
17,258 | 11,842,790,147 | IssuesEvent | 2020-03-24 00:09:20 | kmcgrevey/adopt_dont_shop_paired | https://api.github.com/repos/kmcgrevey/adopt_dont_shop_paired | closed | User Story 1, Deploy your application to Heroku | Usability | ```
As a visitor or user of the site
I will perform all user stories
By visiting the application on Heroku.
Localhost is fine for development, but
the application must be hosted on Heroku.
``` | True | User Story 1, Deploy your application to Heroku - ```
As a visitor or user of the site
I will perform all user stories
By visiting the application on Heroku.
Localhost is fine for development, but
the application must be hosted on Heroku.
``` | usab | user story deploy your application to heroku as a visitor or user of the site i will perform all user stories by visiting the application on heroku localhost is fine for development but the application must be hosted on heroku | 1 |
22,275 | 18,939,532,346 | IssuesEvent | 2021-11-18 00:08:44 | LLNL/axom | https://api.github.com/repos/LLNL/axom | opened | Prevent `axom::Array` from being used within a kernel | GPU usability | The new axom::Array class is supported on the GPU via the `axom::ArrayView` wrapper class.
Since our kernel's have pass-by-value semantics, `axom::Array` should not be used directly within them, as this will incur an allocation+copy. Furthermore, if one is writing to the array, the results will not transfer back from this copy to the original array.
Since the direct `axom::Array` usage will currently compile, it is not always obvious that one is using the incorrect class.
We should explore adding a safeguard to the code to prevent users from directly using an `axom::Array` within kernels. Ideally via a `static_assert`, to catch this at compile time.
It is worth noting that this issue arises for CPU-based kernels, and not just GPU-based kernels. | True | Prevent `axom::Array` from being used within a kernel - The new axom::Array class is supported on the GPU via the `axom::ArrayView` wrapper class.
Since our kernel's have pass-by-value semantics, `axom::Array` should not be used directly within them, as this will incur an allocation+copy. Furthermore, if one is writing to the array, the results will not transfer back from this copy to the original array.
Since the direct `axom::Array` usage will currently compile, it is not always obvious that one is using the incorrect class.
We should explore adding a safeguard to the code to prevent users from directly using an `axom::Array` within kernels. Ideally via a `static_assert`, to catch this at compile time.
It is worth noting that this issue arises for CPU-based kernels, and not just GPU-based kernels. | usab | prevent axom array from being used within a kernel the new axom array class is supported on the gpu via the axom arrayview wrapper class since our kernel s have pass by value semantics axom array should not be used directly within them as this will incur an allocation copy furthermore if one is writing to the array the results will not transfer back from this copy to the original array since the direct axom array usage will currently compile it is not always obvious that one is using the incorrect class we should explore adding a safeguard to the code to prevent users from directly using an axom array within kernels ideally via a static assert to catch this at compile time it is worth noting that this issue arises for cpu based kernels and not just gpu based kernels | 1 |
357,690 | 25,176,421,098 | IssuesEvent | 2022-11-11 09:39:52 | kaij77/pe | https://api.github.com/repos/kaij77/pe | opened | NFR not scoped clearly | severity.VeryLow type.DocumentationBug | 
It may be hard to decide when NFR 3 has been met as the "average typing speed for regular English text" is not defined, and it is not clear what software (using the mouse to accomplish the tasks) we are comparing to.
<!--session: 1668152272112-1e586150-3cb2-4c85-bf4c-048646a10bca-->
<!--Version: Web v3.4.4--> | 1.0 | NFR not scoped clearly - 
It may be hard to decide when NFR 3 has been met as the "average typing speed for regular English text" is not defined, and it is not clear what software (using the mouse to accomplish the tasks) we are comparing to.
<!--session: 1668152272112-1e586150-3cb2-4c85-bf4c-048646a10bca-->
<!--Version: Web v3.4.4--> | non_usab | nfr not scoped clearly it may be hard to decide when nfr has been met as the average typing speed for regular english text is not defined and it is not clear what software using the mouse to accomplish the tasks we are comparing to | 0 |
19,995 | 10,440,875,549 | IssuesEvent | 2019-09-18 09:36:20 | YANG-DB/yang-db | https://api.github.com/repos/YANG-DB/yang-db | opened | CVE-2019-14540 (Medium) detected in jackson-databind-2.9.8.jar | security vulnerability | ## CVE-2019-14540 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.8.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /tmp/ws-scm/yang-db/fuse-model/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.8/jackson-databind-2.9.8.jar,epository/com/fasterxml/jackson/core/jackson-databind/2.9.8/jackson-databind-2.9.8.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.9.8.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/YANG-DB/yang-db/commit/859808989671b065b7e3158e1e5fdb3f65fa59df">859808989671b065b7e3158e1e5fdb3f65fa59df</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>
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to com.zaxxer.hikari.HikariConfig.
<p>Publish Date: 2019-09-15
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14540>CVE-2019-14540</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</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/FasterXML/jackson-databind/blob/master/release-notes/VERSION-2.x">https://github.com/FasterXML/jackson-databind/blob/master/release-notes/VERSION-2.x</a></p>
<p>Release Date: 2019-09-15</p>
<p>Fix Resolution: 2.9.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-2019-14540 (Medium) detected in jackson-databind-2.9.8.jar - ## CVE-2019-14540 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.8.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /tmp/ws-scm/yang-db/fuse-model/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.8/jackson-databind-2.9.8.jar,epository/com/fasterxml/jackson/core/jackson-databind/2.9.8/jackson-databind-2.9.8.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.9.8.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/YANG-DB/yang-db/commit/859808989671b065b7e3158e1e5fdb3f65fa59df">859808989671b065b7e3158e1e5fdb3f65fa59df</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>
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to com.zaxxer.hikari.HikariConfig.
<p>Publish Date: 2019-09-15
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14540>CVE-2019-14540</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</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/FasterXML/jackson-databind/blob/master/release-notes/VERSION-2.x">https://github.com/FasterXML/jackson-databind/blob/master/release-notes/VERSION-2.x</a></p>
<p>Release Date: 2019-09-15</p>
<p>Fix Resolution: 2.9.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_usab | cve medium detected in jackson databind jar cve medium severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file tmp ws scm yang db fuse model pom xml path to vulnerable library root repository com fasterxml jackson core jackson databind jackson databind jar epository com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy x jackson databind jar vulnerable library found in head commit a href vulnerability details a polymorphic typing issue was discovered in fasterxml jackson databind before it is related to com zaxxer hikari hikariconfig publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
275,039 | 8,570,756,296 | IssuesEvent | 2018-11-11 23:01:32 | GSA/caribou | https://api.github.com/repos/GSA/caribou | closed | Typing URL for staging.code.gov/open-tasks does not work | high-priority | **Describe the bug**
If I type in the URL https://staging.code.gov/open-tasks I get a 404 page, but if I click on Open Tasks from the nav it works
**To Reproduce**
Steps to reproduce the behavior:
1. Type 'https://staging.code.gov/open-tasks' into browser
2. See 404 page
**Expected behavior**
Should take me to Open Tasks page | 1.0 | Typing URL for staging.code.gov/open-tasks does not work - **Describe the bug**
If I type in the URL https://staging.code.gov/open-tasks I get a 404 page, but if I click on Open Tasks from the nav it works
**To Reproduce**
Steps to reproduce the behavior:
1. Type 'https://staging.code.gov/open-tasks' into browser
2. See 404 page
**Expected behavior**
Should take me to Open Tasks page | non_usab | typing url for staging code gov open tasks does not work describe the bug if i type in the url i get a page but if i click on open tasks from the nav it works to reproduce steps to reproduce the behavior type into browser see page expected behavior should take me to open tasks page | 0 |
11,769 | 7,447,011,814 | IssuesEvent | 2018-03-28 11:01:21 | nerdalize/nerd | https://api.github.com/repos/nerdalize/nerd | opened | Unhelpful error when specifying invalid kubeconfig path | usability | ## Expected Behavior
When specifying an invalid kubeconfig path, it should return a proper error and not a "not logged in" one
## Actual Behavior
 | True | Unhelpful error when specifying invalid kubeconfig path - ## Expected Behavior
When specifying an invalid kubeconfig path, it should return a proper error and not a "not logged in" one
## Actual Behavior
 | usab | unhelpful error when specifying invalid kubeconfig path expected behavior when specifying an invalid kubeconfig path it should return a proper error and not a not logged in one actual behavior | 1 |
3,173 | 3,362,646,309 | IssuesEvent | 2015-11-20 07:39:19 | godotengine/godot | https://api.github.com/repos/godotengine/godot | opened | Contextual help hotkey does not work since script editor/help tab merger | bug topic:editor usability | The contextual help that can be accessed via the Help::Contextual menu entry is still working, but the hotkey that was assigned (Shift + F1) is no longer working.
It was removed in https://github.com/godotengine/godot/commit/081a236c6739e7f6d45731ec0c002d2269f2367b#diff-d0f2bd20931a3b06b3e10aa2df9eee87L342.
Now F1 is no longer used for the help window so it likely conflicted with the new F1 assignment for the 2D viewport, but we still need a replacement.
Also take into account the proposed fix in #2111 for the previous behaviour. | True | Contextual help hotkey does not work since script editor/help tab merger - The contextual help that can be accessed via the Help::Contextual menu entry is still working, but the hotkey that was assigned (Shift + F1) is no longer working.
It was removed in https://github.com/godotengine/godot/commit/081a236c6739e7f6d45731ec0c002d2269f2367b#diff-d0f2bd20931a3b06b3e10aa2df9eee87L342.
Now F1 is no longer used for the help window so it likely conflicted with the new F1 assignment for the 2D viewport, but we still need a replacement.
Also take into account the proposed fix in #2111 for the previous behaviour. | usab | contextual help hotkey does not work since script editor help tab merger the contextual help that can be accessed via the help contextual menu entry is still working but the hotkey that was assigned shift is no longer working it was removed in now is no longer used for the help window so it likely conflicted with the new assignment for the viewport but we still need a replacement also take into account the proposed fix in for the previous behaviour | 1 |
343,119 | 30,652,827,072 | IssuesEvent | 2023-07-25 10:02:09 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | opened | Fix tensor.test_tensorflow_instance_set_shape | TensorFlow Frontend Sub Task Failing Test | | | |
|---|---|
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5634798880"><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5634798880"><img src=https://img.shields.io/badge/-failure-red></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5634798880"><img src=https://img.shields.io/badge/-failure-red></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5634798880"><img src=https://img.shields.io/badge/-failure-red></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5634798880"><img src=https://img.shields.io/badge/-failure-red></a>
| 1.0 | Fix tensor.test_tensorflow_instance_set_shape - | | |
|---|---|
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5634798880"><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5634798880"><img src=https://img.shields.io/badge/-failure-red></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5634798880"><img src=https://img.shields.io/badge/-failure-red></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5634798880"><img src=https://img.shields.io/badge/-failure-red></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5634798880"><img src=https://img.shields.io/badge/-failure-red></a>
| non_usab | fix tensor test tensorflow instance set shape jax a href src numpy a href src tensorflow a href src torch a href src paddle a href src | 0 |
144,351 | 13,103,519,257 | IssuesEvent | 2020-08-04 08:42:34 | AbsaOSS/k8gb | https://api.github.com/repos/AbsaOSS/k8gb | closed | Rework README to focus on first time users | documentation | Given someone that is looking for a cloud native, Kubernetes native GSLB solution and who finds this project. The `README` should concisely and simply answer the following questions:
* What problem does it solve?
* How does it solve the problem? (Briefly, simply and with links to detailed docs)
* How do I run it locally to see how it works (Quick start)
* If I wanted to contribute, what should I know and how could I setup my local development environment (see #100)
The goal of the `README` should leave no doubt as to what this project does, how it does it and an easy, quick way to try it out. | 1.0 | Rework README to focus on first time users - Given someone that is looking for a cloud native, Kubernetes native GSLB solution and who finds this project. The `README` should concisely and simply answer the following questions:
* What problem does it solve?
* How does it solve the problem? (Briefly, simply and with links to detailed docs)
* How do I run it locally to see how it works (Quick start)
* If I wanted to contribute, what should I know and how could I setup my local development environment (see #100)
The goal of the `README` should leave no doubt as to what this project does, how it does it and an easy, quick way to try it out. | non_usab | rework readme to focus on first time users given someone that is looking for a cloud native kubernetes native gslb solution and who finds this project the readme should concisely and simply answer the following questions what problem does it solve how does it solve the problem briefly simply and with links to detailed docs how do i run it locally to see how it works quick start if i wanted to contribute what should i know and how could i setup my local development environment see the goal of the readme should leave no doubt as to what this project does how it does it and an easy quick way to try it out | 0 |
14,299 | 8,983,045,449 | IssuesEvent | 2019-01-31 05:12:23 | PuzzleServer/mainpuzzleserver | https://api.github.com/repos/PuzzleServer/mainpuzzleserver | closed | Implement author dashboard page | enhancement recommended usability | - Submission history (depends on submission implementation)
- Feedback history (depends on feedback system implementation)
- Threads on the puzzle (depends on thread implementation)
- Any solve/state tracking? | True | Implement author dashboard page - - Submission history (depends on submission implementation)
- Feedback history (depends on feedback system implementation)
- Threads on the puzzle (depends on thread implementation)
- Any solve/state tracking? | usab | implement author dashboard page submission history depends on submission implementation feedback history depends on feedback system implementation threads on the puzzle depends on thread implementation any solve state tracking | 1 |
8,650 | 5,897,172,732 | IssuesEvent | 2017-05-18 11:46:50 | godotengine/godot | https://api.github.com/repos/godotengine/godot | opened | [TRACKER] Editor theme issues for 3.0 | bug enhancement topic:editor usability | This tracker bug is for all issues related to the new editor theme for Godot 3.0.
## PRs
- [ ] New customizable editor theme #8631
## Bugs
- [ ] New Theme: Tree drag&drop visual helper is barely visible. #8677
- [ ] Scan file selection font color broken #8635
## Enhancements
- [ ] TODO | True | [TRACKER] Editor theme issues for 3.0 - This tracker bug is for all issues related to the new editor theme for Godot 3.0.
## PRs
- [ ] New customizable editor theme #8631
## Bugs
- [ ] New Theme: Tree drag&drop visual helper is barely visible. #8677
- [ ] Scan file selection font color broken #8635
## Enhancements
- [ ] TODO | usab | editor theme issues for this tracker bug is for all issues related to the new editor theme for godot prs new customizable editor theme bugs new theme tree drag drop visual helper is barely visible scan file selection font color broken enhancements todo | 1 |
94,792 | 11,911,390,428 | IssuesEvent | 2020-03-31 08:32:39 | Disfactory/Disfactory | https://api.github.com/repos/Disfactory/Disfactory | opened | Dashboard on Landing Page | design medium priority | Dashboard will be showed on landing page
（拆自後台 Admin Page issue: #268 ）
Purpose:
- For staff: transparency and impact metrics to measure success
- For active reporters: rewarded and know the progress
- For general public: know the overview advocacy impact and join the reporting movement
Design principle:
- simple and strong messages
- realtime update (max interval: 30 min)
Data:
- 回報行動：民眾已回報工廠數量總數、更新資料筆數、縣市分佈（可用台灣地圖視覺化）、熱門查詢與回報地區（`town-district`）排行榜 top 5（列出舉報工廠術與資料筆數）、past 30 days unique users（這個有點赤裸 XD，數字好看再放）
- 舉報進度：打算正式舉報的數量佔全部回報點位的百分比（並分為中高污染和新增建工廠）、地公處理進度 `cet_report_status`（分階段和時間顯示數量）、政府回應 `gov_response`（分類顯示）
## **Out of Scope**
- Interactive design or motion graphic, e.g. search, filter
- more than 3 sections to display the dashboard
| 1.0 | Dashboard on Landing Page - Dashboard will be showed on landing page
（拆自後台 Admin Page issue: #268 ）
Purpose:
- For staff: transparency and impact metrics to measure success
- For active reporters: rewarded and know the progress
- For general public: know the overview advocacy impact and join the reporting movement
Design principle:
- simple and strong messages
- realtime update (max interval: 30 min)
Data:
- 回報行動：民眾已回報工廠數量總數、更新資料筆數、縣市分佈（可用台灣地圖視覺化）、熱門查詢與回報地區（`town-district`）排行榜 top 5（列出舉報工廠術與資料筆數）、past 30 days unique users（這個有點赤裸 XD，數字好看再放）
- 舉報進度：打算正式舉報的數量佔全部回報點位的百分比（並分為中高污染和新增建工廠）、地公處理進度 `cet_report_status`（分階段和時間顯示數量）、政府回應 `gov_response`（分類顯示）
## **Out of Scope**
- Interactive design or motion graphic, e.g. search, filter
- more than 3 sections to display the dashboard
| non_usab | dashboard on landing page dashboard will be showed on landing page （拆自後台 admin page issue ） purpose for staff transparency and impact metrics to measure success for active reporters rewarded and know the progress for general public know the overview advocacy impact and join the reporting movement design principle simple and strong messages realtime update max interval min data 回報行動：民眾已回報工廠數量總數、更新資料筆數、縣市分佈（可用台灣地圖視覺化）、熱門查詢與回報地區（ town district ）排行榜 top （列出舉報工廠術與資料筆數）、past days unique users（這個有點赤裸 xd，數字好看再放） 舉報進度：打算正式舉報的數量佔全部回報點位的百分比（並分為中高污染和新增建工廠）、地公處理進度 cet report status （分階段和時間顯示數量）、政府回應 gov response （分類顯示） out of scope interactive design or motion graphic e g search filter more than sections to display the dashboard | 0 |
370,554 | 25,913,432,990 | IssuesEvent | 2022-12-15 15:35:12 | cds-snc/resources-ressources | https://api.github.com/repos/cds-snc/resources-ressources | opened | Consider integrating GitHub workflow/decisions/rationales in READ.ME Documentation on GitHub | Documentation Low Priority | https://docs.google.com/document/d/15QWD5E3Bje89qRFiHiFJ2waUphZgEPJqJza_LcbFplA/edit#
| 1.0 | Consider integrating GitHub workflow/decisions/rationales in READ.ME Documentation on GitHub - https://docs.google.com/document/d/15QWD5E3Bje89qRFiHiFJ2waUphZgEPJqJza_LcbFplA/edit#
| non_usab | consider integrating github workflow decisions rationales in read me documentation on github | 0 |
254,291 | 27,370,300,848 | IssuesEvent | 2023-02-27 22:48:50 | xmidt-org/arrange | https://api.github.com/repos/xmidt-org/arrange | closed | CVE-2022-32149 (High) detected in golang.org/x/text-v0.3.7 - autoclosed | security vulnerability | ## CVE-2022-32149 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>golang.org/x/text-v0.3.7</b></p></summary>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/text/@v/v0.3.7.zip">https://proxy.golang.org/golang.org/x/text/@v/v0.3.7.zip</a></p>
<p>
Dependency Hierarchy:
- github.com/spf13/viper-v1.12.0 (Root Library)
- github.com/spf13/afero-v1.8.2
- :x: **golang.org/x/text-v0.3.7** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/xmidt-org/arrange/commit/451664259ff0829a88426acfd243e9a7c6027d62">451664259ff0829a88426acfd243e9a7c6027d62</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An attacker may cause a denial of service by crafting an Accept-Language header which ParseAcceptLanguage will take significant time to parse.
<p>Publish Date: 2022-10-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-32149>CVE-2022-32149</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://www.cve.org/CVERecord?id=CVE-2022-32149">https://www.cve.org/CVERecord?id=CVE-2022-32149</a></p>
<p>Release Date: 2022-10-14</p>
<p>Fix Resolution: v0.3.8</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-32149 (High) detected in golang.org/x/text-v0.3.7 - autoclosed - ## CVE-2022-32149 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>golang.org/x/text-v0.3.7</b></p></summary>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/text/@v/v0.3.7.zip">https://proxy.golang.org/golang.org/x/text/@v/v0.3.7.zip</a></p>
<p>
Dependency Hierarchy:
- github.com/spf13/viper-v1.12.0 (Root Library)
- github.com/spf13/afero-v1.8.2
- :x: **golang.org/x/text-v0.3.7** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/xmidt-org/arrange/commit/451664259ff0829a88426acfd243e9a7c6027d62">451664259ff0829a88426acfd243e9a7c6027d62</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An attacker may cause a denial of service by crafting an Accept-Language header which ParseAcceptLanguage will take significant time to parse.
<p>Publish Date: 2022-10-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-32149>CVE-2022-32149</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://www.cve.org/CVERecord?id=CVE-2022-32149">https://www.cve.org/CVERecord?id=CVE-2022-32149</a></p>
<p>Release Date: 2022-10-14</p>
<p>Fix Resolution: v0.3.8</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_usab | cve high detected in golang org x text autoclosed cve high severity vulnerability vulnerable library golang org x text library home page a href dependency hierarchy github com viper root library github com afero x golang org x text vulnerable library found in head commit a href found in base branch main vulnerability details an attacker may cause a denial of service by crafting an accept language header which parseacceptlanguage will take significant time to parse 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 |
23,692 | 22,595,209,509 | IssuesEvent | 2022-06-29 01:43:21 | pulumi/pulumi-hugo | https://api.github.com/repos/pulumi/pulumi-hugo | opened | use of dark mode tools makes our website and docs difficult to use | kind/enhancement impact/usability | recently in a usability study a participant was using Dark Reader in Firefox which enables a dark mode, but unfortunately, it made our website and docs difficult to use because a number of things were totally invisible
later on a different community member mentioned they were using chrome dark mode and had a similar experience with components being totally invisible.
as more and more folks enable these dark mode solutions we should figure out if we can make our website/service work with them or if we should be shipping our dark mode
related: https://github.com/pulumi/registry/issues/244 | True | use of dark mode tools makes our website and docs difficult to use - recently in a usability study a participant was using Dark Reader in Firefox which enables a dark mode, but unfortunately, it made our website and docs difficult to use because a number of things were totally invisible
later on a different community member mentioned they were using chrome dark mode and had a similar experience with components being totally invisible.
as more and more folks enable these dark mode solutions we should figure out if we can make our website/service work with them or if we should be shipping our dark mode
related: https://github.com/pulumi/registry/issues/244 | usab | use of dark mode tools makes our website and docs difficult to use recently in a usability study a participant was using dark reader in firefox which enables a dark mode but unfortunately it made our website and docs difficult to use because a number of things were totally invisible later on a different community member mentioned they were using chrome dark mode and had a similar experience with components being totally invisible as more and more folks enable these dark mode solutions we should figure out if we can make our website service work with them or if we should be shipping our dark mode related | 1 |
11,150 | 7,085,250,140 | IssuesEvent | 2018-01-11 10:17:42 | cnr-ibf-pa/hbp-bsp-issues | https://api.github.com/repos/cnr-ibf-pa/hbp-bsp-issues | opened | "Circuit Target" on the Start-Simulation popup | Type_Usability UC_SimulationUI | It needs to be decided if this option is useful, or if it should be removed.
We need to talk to Armando.
| True | "Circuit Target" on the Start-Simulation popup - It needs to be decided if this option is useful, or if it should be removed.
We need to talk to Armando.
| usab | circuit target on the start simulation popup it needs to be decided if this option is useful or if it should be removed we need to talk to armando | 1 |
205,900 | 23,359,719,910 | IssuesEvent | 2022-08-10 10:34:14 | Gal-Doron/Baragon-test | https://api.github.com/repos/Gal-Doron/Baragon-test | opened | guava-25.0-jre.jar: 1 vulnerabilities (highest severity is: 3.3) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>guava-25.0-jre.jar</b></p></summary>
<p>Guava is a suite of core and expanded libraries that include
utility classes, google's collections, io classes, and much
much more.</p>
<p>Library home page: <a href="https://github.com/google/guava">https://github.com/google/guava</a></p>
<p>Path to dependency file: /BaragonService/pom.xml</p>
<p>Path to vulnerable library: /pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/Gal-Doron/Baragon-test/commit/1e1d083a37d3830e31f6de3b1180ffda4c2cc66a">1e1d083a37d3830e31f6de3b1180ffda4c2cc66a</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2020-8908](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8908) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low | 3.3 | guava-25.0-jre.jar | Direct | 30.0-android | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> CVE-2020-8908</summary>
### Vulnerable Library - <b>guava-25.0-jre.jar</b></p>
<p>Guava is a suite of core and expanded libraries that include
utility classes, google's collections, io classes, and much
much more.</p>
<p>Library home page: <a href="https://github.com/google/guava">https://github.com/google/guava</a></p>
<p>Path to dependency file: /BaragonService/pom.xml</p>
<p>Path to vulnerable library: /pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar</p>
<p>
Dependency Hierarchy:
- :x: **guava-25.0-jre.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Gal-Doron/Baragon-test/commit/1e1d083a37d3830e31f6de3b1180ffda4c2cc66a">1e1d083a37d3830e31f6de3b1180ffda4c2cc66a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A temp directory creation vulnerability exists in all versions of Guava, allowing an attacker with access to the machine to potentially access data in a temporary directory created by the Guava API com.google.common.io.Files.createTempDir(). By default, on unix-like systems, the created directory is world-readable (readable by an attacker with access to the system). The method in question has been marked @Deprecated in versions 30.0 and later and should not be used. For Android developers, we recommend choosing a temporary directory API provided by Android, such as context.getCacheDir(). For other Java developers, we recommend migrating to the Java 7 API java.nio.file.Files.createTempDirectory() which explicitly configures permissions of 700, or configuring the Java runtime's java.io.tmpdir system property to point to a location whose permissions are appropriately configured.
<p>Publish Date: 2020-12-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8908>CVE-2020-8908</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>3.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8908">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8908</a></p>
<p>Release Date: 2020-12-10</p>
<p>Fix Resolution: 30.0-android</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | True | guava-25.0-jre.jar: 1 vulnerabilities (highest severity is: 3.3) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>guava-25.0-jre.jar</b></p></summary>
<p>Guava is a suite of core and expanded libraries that include
utility classes, google's collections, io classes, and much
much more.</p>
<p>Library home page: <a href="https://github.com/google/guava">https://github.com/google/guava</a></p>
<p>Path to dependency file: /BaragonService/pom.xml</p>
<p>Path to vulnerable library: /pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/Gal-Doron/Baragon-test/commit/1e1d083a37d3830e31f6de3b1180ffda4c2cc66a">1e1d083a37d3830e31f6de3b1180ffda4c2cc66a</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2020-8908](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8908) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low | 3.3 | guava-25.0-jre.jar | Direct | 30.0-android | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> CVE-2020-8908</summary>
### Vulnerable Library - <b>guava-25.0-jre.jar</b></p>
<p>Guava is a suite of core and expanded libraries that include
utility classes, google's collections, io classes, and much
much more.</p>
<p>Library home page: <a href="https://github.com/google/guava">https://github.com/google/guava</a></p>
<p>Path to dependency file: /BaragonService/pom.xml</p>
<p>Path to vulnerable library: /pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar,/pository/com/google/guava/guava/25.0-jre/guava-25.0-jre.jar</p>
<p>
Dependency Hierarchy:
- :x: **guava-25.0-jre.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Gal-Doron/Baragon-test/commit/1e1d083a37d3830e31f6de3b1180ffda4c2cc66a">1e1d083a37d3830e31f6de3b1180ffda4c2cc66a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A temp directory creation vulnerability exists in all versions of Guava, allowing an attacker with access to the machine to potentially access data in a temporary directory created by the Guava API com.google.common.io.Files.createTempDir(). By default, on unix-like systems, the created directory is world-readable (readable by an attacker with access to the system). The method in question has been marked @Deprecated in versions 30.0 and later and should not be used. For Android developers, we recommend choosing a temporary directory API provided by Android, such as context.getCacheDir(). For other Java developers, we recommend migrating to the Java 7 API java.nio.file.Files.createTempDirectory() which explicitly configures permissions of 700, or configuring the Java runtime's java.io.tmpdir system property to point to a location whose permissions are appropriately configured.
<p>Publish Date: 2020-12-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8908>CVE-2020-8908</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>3.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8908">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8908</a></p>
<p>Release Date: 2020-12-10</p>
<p>Fix Resolution: 30.0-android</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | non_usab | guava jre jar vulnerabilities highest severity is vulnerable library guava jre jar guava is a suite of core and expanded libraries that include utility classes google s collections io classes and much much more library home page a href path to dependency file baragonservice pom xml path to vulnerable library pository com google guava guava jre guava jre jar pository com google guava guava jre guava jre jar pository com google guava guava jre guava jre jar pository com google guava guava jre guava jre jar pository com google guava guava jre guava jre jar pository com google guava guava jre guava jre jar pository com google guava guava jre guava jre jar found in head commit a href vulnerabilities cve severity cvss dependency type fixed in remediation available low guava jre jar direct android details cve vulnerable library guava jre jar guava is a suite of core and expanded libraries that include utility classes google s collections io classes and much much more library home page a href path to dependency file baragonservice pom xml path to vulnerable library pository com google guava guava jre guava jre jar pository com google guava guava jre guava jre jar pository com google guava guava jre guava jre jar pository com google guava guava jre guava jre jar pository com google guava guava jre guava jre jar pository com google guava guava jre guava jre jar pository com google guava guava jre guava jre jar dependency hierarchy x guava jre jar vulnerable library found in head commit a href found in base branch master vulnerability details a temp directory creation vulnerability exists in all versions of guava allowing an attacker with access to the machine to potentially access data in a temporary directory created by the guava api com google common io files createtempdir by default on unix like systems the created directory is world readable readable by an attacker with access to the system the method in question has been marked deprecated in versions and later and should not be used for android developers we recommend choosing a temporary directory api provided by android such as context getcachedir for other java developers we recommend migrating to the java api java nio file files createtempdirectory which explicitly configures permissions of or configuring the java runtime s java io tmpdir system property to point to a location whose permissions are appropriately configured 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 none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution android rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue | 0 |
13,200 | 22,282,618,525 | IssuesEvent | 2022-06-11 05:13:54 | renovatebot/renovate | https://api.github.com/repos/renovatebot/renovate | opened | Switch depName/packageName logic | type:feature priority-2-important status:requirements | ### What would you like Renovate to be able to do?
Instead of defaulting to `depName`, and allowing `packageName` as an optional override, we should instead default to extracting `packageName`, and allowing `depName` optionally.
### If you have any ideas on how this should be implemented, please tell us here.
We would need to make changes to each manager's extract function, which will touch most managers but not be complex.
There may be a small change to `datasource` index logic because now it does not need the depName->packageName fallback.
But then there are other areas of the code which assume `depName` is always present.
One in particular is `packageRules`. Today `matchPackage*` actually functions on the `depName` field and not the `packageName`. We might need to do something like:
- Try matching against `packageName` first
- If a depName is present, try matching against it second
Or maybe instead we could:
- add new `matchDepNames` and `matchDepNamePatterns` fields
- Do like above, but WARN if the match is on `depName` for one major release
- Deprecate the `depName` matching fallback in a later release
Ultimately this issue is going to require some exploration and testing - it's hard to predict everywhere it might cause changes
### Is this a feature you are interested in implementing yourself?
Maybe | 1.0 | Switch depName/packageName logic - ### What would you like Renovate to be able to do?
Instead of defaulting to `depName`, and allowing `packageName` as an optional override, we should instead default to extracting `packageName`, and allowing `depName` optionally.
### If you have any ideas on how this should be implemented, please tell us here.
We would need to make changes to each manager's extract function, which will touch most managers but not be complex.
There may be a small change to `datasource` index logic because now it does not need the depName->packageName fallback.
But then there are other areas of the code which assume `depName` is always present.
One in particular is `packageRules`. Today `matchPackage*` actually functions on the `depName` field and not the `packageName`. We might need to do something like:
- Try matching against `packageName` first
- If a depName is present, try matching against it second
Or maybe instead we could:
- add new `matchDepNames` and `matchDepNamePatterns` fields
- Do like above, but WARN if the match is on `depName` for one major release
- Deprecate the `depName` matching fallback in a later release
Ultimately this issue is going to require some exploration and testing - it's hard to predict everywhere it might cause changes
### Is this a feature you are interested in implementing yourself?
Maybe | non_usab | switch depname packagename logic what would you like renovate to be able to do instead of defaulting to depname and allowing packagename as an optional override we should instead default to extracting packagename and allowing depname optionally if you have any ideas on how this should be implemented please tell us here we would need to make changes to each manager s extract function which will touch most managers but not be complex there may be a small change to datasource index logic because now it does not need the depname packagename fallback but then there are other areas of the code which assume depname is always present one in particular is packagerules today matchpackage actually functions on the depname field and not the packagename we might need to do something like try matching against packagename first if a depname is present try matching against it second or maybe instead we could add new matchdepnames and matchdepnamepatterns fields do like above but warn if the match is on depname for one major release deprecate the depname matching fallback in a later release ultimately this issue is going to require some exploration and testing it s hard to predict everywhere it might cause changes is this a feature you are interested in implementing yourself maybe | 0 |
22,496 | 19,542,276,926 | IssuesEvent | 2022-01-01 05:29:38 | Leafwing-Studios/petitset | https://api.github.com/repos/Leafwing-Studios/petitset | closed | Add a swap method to both PetitSet and PetitMap | enhancement usability | Useful for quickly shuffling indexes around.
| True | Add a swap method to both PetitSet and PetitMap - Useful for quickly shuffling indexes around.
| usab | add a swap method to both petitset and petitmap useful for quickly shuffling indexes around | 1 |
3,096 | 3,331,440,761 | IssuesEvent | 2015-11-11 15:52:36 | rabbitmq/rabbitmq-server | https://api.github.com/repos/rabbitmq/rabbitmq-server | opened | Improve error message for access_refused during connection handshake | effort-tiny enhancement usability | A lot like #320 but with a different failure: `access_refused` would be used when vhost does exist but the user has no permissions to it. | True | Improve error message for access_refused during connection handshake - A lot like #320 but with a different failure: `access_refused` would be used when vhost does exist but the user has no permissions to it. | usab | improve error message for access refused during connection handshake a lot like but with a different failure access refused would be used when vhost does exist but the user has no permissions to it | 1 |
23,957 | 7,434,919,621 | IssuesEvent | 2018-03-26 12:45:02 | Icinga/icinga2 | https://api.github.com/repos/Icinga/icinga2 | closed | Snapshot builds fail on livestatus tests | Tests build-fix | This issue only appears on the build server and seems only to hit Debian Jessie and Ununtu trusty.
I was not able to reproduce this locally on buster.
```
/usr/bin/ctest --force-new-ctest-process -j1
Test project /home/jenkins/workspace/icinga2-snapshot/deb-debian-jessie-1binary/arch/x86_64/icinga2/obj-x86_64-linux-gnu
[ . . . ]
Start 84: livestatus-livestatus/hosts
84/89 Test #84: livestatus-livestatus/hosts .............................................***Failed 0.01 sec
Test setup error: std::exception: 'apply' cannot be used with type 'Service'
Start 85: livestatus-livestatus/services
85/89 Test #85: livestatus-livestatus/services ..........................................***Failed 0.01 sec
Test setup error: std::exception: 'apply' cannot be used with type 'Service'
Start 86: icinga_checkable-icinga_checkable_flapping/host_not_flapping
86/89 Test #86: icinga_checkable-icinga_checkable_flapping/host_not_flapping ............ Passed 0.01 sec
Start 87: icinga_checkable-icinga_checkable_flapping/host_flapping
87/89 Test #87: icinga_checkable-icinga_checkable_flapping/host_flapping ................ Passed 0.01 sec
Start 88: icinga_checkable-icinga_checkable_flapping/host_flapping_recover
88/89 Test #88: icinga_checkable-icinga_checkable_flapping/host_flapping_recover ........ Passed 0.01 sec
Start 89: icinga_checkable-icinga_checkable_flapping/host_flapping_docs_example
89/89 Test #89: icinga_checkable-icinga_checkable_flapping/host_flapping_docs_example ... Passed 0.01 sec
98% tests passed, 2 tests failed out of 89
Total Test time (real) = 17.58 sec
The following tests FAILED:
84 - livestatus-livestatus/hosts (Failed)
85 - livestatus-livestatus/services (Failed)
```
See also [here](https://build.icinga.com/job/icinga2-snapshot/job/deb-ubuntu-trusty-1binary/arch=x86_64/136/console) and [here](https://build.icinga.com/job/icinga2-snapshot/job/deb-debian-jessie-1binary/arch=x86/137/console)
| 1.0 | Snapshot builds fail on livestatus tests - This issue only appears on the build server and seems only to hit Debian Jessie and Ununtu trusty.
I was not able to reproduce this locally on buster.
```
/usr/bin/ctest --force-new-ctest-process -j1
Test project /home/jenkins/workspace/icinga2-snapshot/deb-debian-jessie-1binary/arch/x86_64/icinga2/obj-x86_64-linux-gnu
[ . . . ]
Start 84: livestatus-livestatus/hosts
84/89 Test #84: livestatus-livestatus/hosts .............................................***Failed 0.01 sec
Test setup error: std::exception: 'apply' cannot be used with type 'Service'
Start 85: livestatus-livestatus/services
85/89 Test #85: livestatus-livestatus/services ..........................................***Failed 0.01 sec
Test setup error: std::exception: 'apply' cannot be used with type 'Service'
Start 86: icinga_checkable-icinga_checkable_flapping/host_not_flapping
86/89 Test #86: icinga_checkable-icinga_checkable_flapping/host_not_flapping ............ Passed 0.01 sec
Start 87: icinga_checkable-icinga_checkable_flapping/host_flapping
87/89 Test #87: icinga_checkable-icinga_checkable_flapping/host_flapping ................ Passed 0.01 sec
Start 88: icinga_checkable-icinga_checkable_flapping/host_flapping_recover
88/89 Test #88: icinga_checkable-icinga_checkable_flapping/host_flapping_recover ........ Passed 0.01 sec
Start 89: icinga_checkable-icinga_checkable_flapping/host_flapping_docs_example
89/89 Test #89: icinga_checkable-icinga_checkable_flapping/host_flapping_docs_example ... Passed 0.01 sec
98% tests passed, 2 tests failed out of 89
Total Test time (real) = 17.58 sec
The following tests FAILED:
84 - livestatus-livestatus/hosts (Failed)
85 - livestatus-livestatus/services (Failed)
```
See also [here](https://build.icinga.com/job/icinga2-snapshot/job/deb-ubuntu-trusty-1binary/arch=x86_64/136/console) and [here](https://build.icinga.com/job/icinga2-snapshot/job/deb-debian-jessie-1binary/arch=x86/137/console)
| non_usab | snapshot builds fail on livestatus tests this issue only appears on the build server and seems only to hit debian jessie and ununtu trusty i was not able to reproduce this locally on buster usr bin ctest force new ctest process test project home jenkins workspace snapshot deb debian jessie arch obj linux gnu start livestatus livestatus hosts test livestatus livestatus hosts failed sec test setup error std exception apply cannot be used with type service start livestatus livestatus services test livestatus livestatus services failed sec test setup error std exception apply cannot be used with type service start icinga checkable icinga checkable flapping host not flapping test icinga checkable icinga checkable flapping host not flapping passed sec start icinga checkable icinga checkable flapping host flapping test icinga checkable icinga checkable flapping host flapping passed sec start icinga checkable icinga checkable flapping host flapping recover test icinga checkable icinga checkable flapping host flapping recover passed sec start icinga checkable icinga checkable flapping host flapping docs example test icinga checkable icinga checkable flapping host flapping docs example passed sec tests passed tests failed out of total test time real sec the following tests failed livestatus livestatus hosts failed livestatus livestatus services failed see also and | 0 |
179,227 | 30,199,770,056 | IssuesEvent | 2023-07-05 03:49:30 | microsoft/devhome | https://api.github.com/repos/microsoft/devhome | reopened | Executing Tasks should provide more information. | Issue-Bug Area-Machine-Config Resolution-By-Design Area-Machine-Config-Loading | ### Dev Home version
_No response_
### Windows build number
_No response_
### Other software
_No response_
### Steps to reproduce the bug
TODO here: DevHome.SetupFlow.ISetupTasks.cs
### Expected result
_No response_
### Actual result
_No response_
### Included System Information
_No response_
### Included Extensions Information
_No response_ | 1.0 | Executing Tasks should provide more information. - ### Dev Home version
_No response_
### Windows build number
_No response_
### Other software
_No response_
### Steps to reproduce the bug
TODO here: DevHome.SetupFlow.ISetupTasks.cs
### Expected result
_No response_
### Actual result
_No response_
### Included System Information
_No response_
### Included Extensions Information
_No response_ | non_usab | executing tasks should provide more information dev home version no response windows build number no response other software no response steps to reproduce the bug todo here devhome setupflow isetuptasks cs expected result no response actual result no response included system information no response included extensions information no response | 0 |
26,691 | 27,088,451,619 | IssuesEvent | 2023-02-14 18:52:57 | redpanda-data/documentation | https://api.github.com/repos/redpanda-data/documentation | closed | Add single quote for passwords to accommodate complex passwords (special chars) | usability improvement Epic Quality Edit P3 | ### Describe the Issue
If a user needs to create an account (and use that account) with a complex password with special characters, it needs to be single quoted, with rpk (on user create and password usage in commands) and inside of the yaml definitions whenever referenced.
### Updates to existing documentation
I think it would be sufficient to change all locations where passwords are referenced or set in any commands or configurations to be single quoted, it's just good practice.
In the security section of the documentation, maybe point out that docs throughout will reference the password as single quoted because of potential special characters. | True | Add single quote for passwords to accommodate complex passwords (special chars) - ### Describe the Issue
If a user needs to create an account (and use that account) with a complex password with special characters, it needs to be single quoted, with rpk (on user create and password usage in commands) and inside of the yaml definitions whenever referenced.
### Updates to existing documentation
I think it would be sufficient to change all locations where passwords are referenced or set in any commands or configurations to be single quoted, it's just good practice.
In the security section of the documentation, maybe point out that docs throughout will reference the password as single quoted because of potential special characters. | usab | add single quote for passwords to accommodate complex passwords special chars describe the issue if a user needs to create an account and use that account with a complex password with special characters it needs to be single quoted with rpk on user create and password usage in commands and inside of the yaml definitions whenever referenced updates to existing documentation i think it would be sufficient to change all locations where passwords are referenced or set in any commands or configurations to be single quoted it s just good practice in the security section of the documentation maybe point out that docs throughout will reference the password as single quoted because of potential special characters | 1 |
26,741 | 2,685,325,493 | IssuesEvent | 2015-03-29 22:31:37 | IssueMigrationTest/Test5 | https://api.github.com/repos/IssueMigrationTest/Test5 | closed | Async module interest | auto-migrated Priority-Low Type-Enhancement | **Issue by cfmx...@gmail.com**
_27 Jul 2010 at 11:37 GMT_
_Originally opened on Google Code_
----
```
Is there an interest in porting the async module to Shedskin? It seems that
there was an effort by Simon Brenner (attached) to port the async module to
C++.
Cheers!
Mar.
```
Attachments:
* [async.zip](https://storage.googleapis.com/google-code-attachments/shedskin/issue-88/comment-0/async.zip)
| 1.0 | Async module interest - **Issue by cfmx...@gmail.com**
_27 Jul 2010 at 11:37 GMT_
_Originally opened on Google Code_
----
```
Is there an interest in porting the async module to Shedskin? It seems that
there was an effort by Simon Brenner (attached) to port the async module to
C++.
Cheers!
Mar.
```
Attachments:
* [async.zip](https://storage.googleapis.com/google-code-attachments/shedskin/issue-88/comment-0/async.zip)
| non_usab | async module interest issue by cfmx gmail com jul at gmt originally opened on google code is there an interest in porting the async module to shedskin it seems that there was an effort by simon brenner attached to port the async module to c cheers mar attachments | 0 |
404,126 | 27,450,673,145 | IssuesEvent | 2023-03-02 17:08:34 | isuct-ui-components/web-ui-components | https://api.github.com/repos/isuct-ui-components/web-ui-components | opened | Documentation: Обновить Readme | documentation | - [ ] Добавить участников команды
- [ ] Добавить роли участникам команды
- [ ] Добавить ссылку на опубликованный сторибук
- [ ] Добавить ссылку на дизайн | 1.0 | Documentation: Обновить Readme - - [ ] Добавить участников команды
- [ ] Добавить роли участникам команды
- [ ] Добавить ссылку на опубликованный сторибук
- [ ] Добавить ссылку на дизайн | non_usab | documentation обновить readme добавить участников команды добавить роли участникам команды добавить ссылку на опубликованный сторибук добавить ссылку на дизайн | 0 |
23,398 | 21,768,099,487 | IssuesEvent | 2022-05-13 05:55:23 | Bridgeconn/VachanAppReact | https://api.github.com/repos/Bridgeconn/VachanAppReact | closed | expand /collapse arrows in the History section - are not pointing correctly and not changing as they are expected to change . | Usability 1.3.2-alpha.5 | (VachanGo v1.3.2 aplha 5 apk)
**Issue Description**:-
expand /collapse arrows in the History section - are not changing as they are expected to change and for the latest history it's incorrect.
**Expected behavior** : -
- should point up when it's in expanded.
- should point down when it's collapsed. | True | expand /collapse arrows in the History section - are not pointing correctly and not changing as they are expected to change . - (VachanGo v1.3.2 aplha 5 apk)
**Issue Description**:-
expand /collapse arrows in the History section - are not changing as they are expected to change and for the latest history it's incorrect.
**Expected behavior** : -
- should point up when it's in expanded.
- should point down when it's collapsed. | usab | expand collapse arrows in the history section are not pointing correctly and not changing as they are expected to change vachango aplha apk issue description expand collapse arrows in the history section are not changing as they are expected to change and for the latest history it s incorrect expected behavior should point up when it s in expanded should point down when it s collapsed | 1 |
8,824 | 5,970,973,743 | IssuesEvent | 2017-05-31 00:34:33 | mbudiu-vmw/hiero | https://api.github.com/repos/mbudiu-vmw/hiero | opened | Histogram labels are not always appropriate | usability | Labels which are too long are drawn overlapping.
When using date-times sometimes labels do not show the date, only the time.
| True | Histogram labels are not always appropriate - Labels which are too long are drawn overlapping.
When using date-times sometimes labels do not show the date, only the time.
| usab | histogram labels are not always appropriate labels which are too long are drawn overlapping when using date times sometimes labels do not show the date only the time | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.