Unnamed: 0
int64 0
832k
| id
float64 2.49B
32.1B
| type
stringclasses 1
value | created_at
stringlengths 19
19
| repo
stringlengths 4
112
| repo_url
stringlengths 33
141
| action
stringclasses 3
values | title
stringlengths 1
957
| labels
stringlengths 4
1.11k
| body
stringlengths 1
261k
| index
stringclasses 11
values | text_combine
stringlengths 95
261k
| label
stringclasses 2
values | text
stringlengths 96
250k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2,079
| 11,357,013,673
|
IssuesEvent
|
2020-01-25 01:18:15
|
IBM/FHIR
|
https://api.github.com/repos/IBM/FHIR
|
closed
|
Incorporate and Improve test coverage in the build/site
|
automation
|
Incorporate and Improve test coverage in the build/site
**STEPS**
- Investigate Sonar Cloud
- Investigate CodeCov.io
- Determine how to report effectively for the FHIR build
- Review with team
- Add to build
|
1.0
|
Incorporate and Improve test coverage in the build/site - Incorporate and Improve test coverage in the build/site
**STEPS**
- Investigate Sonar Cloud
- Investigate CodeCov.io
- Determine how to report effectively for the FHIR build
- Review with team
- Add to build
|
non_design
|
incorporate and improve test coverage in the build site incorporate and improve test coverage in the build site steps investigate sonar cloud investigate codecov io determine how to report effectively for the fhir build review with team add to build
| 0
|
200,037
| 15,789,308,258
|
IssuesEvent
|
2021-04-01 22:28:04
|
onflow/cadence
|
https://api.github.com/repos/onflow/cadence
|
opened
|
Document contract update checker
|
Documentation
|
## Context
Contract updates are now checked and invalid updates are rejected.
Document current rules and design decisions.
## Definition of Done
- [ ] Documented current rules and design decisions
- [ ] Examples for most frequent use-cases
## Additional Info
The contract update checker ensures that:
1. Stored data doesn't change its meaning when a contract is updated
2. Decoding and using stored data does not lead to crashes.
For example, it is invalid to add a field because existing stored data won't have the new field.
A static check of the access of the field would be valid, but then a crash would occur in the interpreter when accessing the field, because the field is missing in the decoded value (wrong shape)
Some rules:
- Importing contracts don't matter. If a change breaks an importing contract, that's valid.
This ensures that changes / fixes can be applied at the root of the dependency chain.
- It is not valid to change a field type to a subtype, because existing stored data might be of a supertype.
- Remove conformance of composite to interface is OK, the stored data only stores concrete type identifier
- Changing the body of a function is valid, as long as the signature stays the same
|
1.0
|
Document contract update checker - ## Context
Contract updates are now checked and invalid updates are rejected.
Document current rules and design decisions.
## Definition of Done
- [ ] Documented current rules and design decisions
- [ ] Examples for most frequent use-cases
## Additional Info
The contract update checker ensures that:
1. Stored data doesn't change its meaning when a contract is updated
2. Decoding and using stored data does not lead to crashes.
For example, it is invalid to add a field because existing stored data won't have the new field.
A static check of the access of the field would be valid, but then a crash would occur in the interpreter when accessing the field, because the field is missing in the decoded value (wrong shape)
Some rules:
- Importing contracts don't matter. If a change breaks an importing contract, that's valid.
This ensures that changes / fixes can be applied at the root of the dependency chain.
- It is not valid to change a field type to a subtype, because existing stored data might be of a supertype.
- Remove conformance of composite to interface is OK, the stored data only stores concrete type identifier
- Changing the body of a function is valid, as long as the signature stays the same
|
non_design
|
document contract update checker context contract updates are now checked and invalid updates are rejected document current rules and design decisions definition of done documented current rules and design decisions examples for most frequent use cases additional info the contract update checker ensures that stored data doesn t change its meaning when a contract is updated decoding and using stored data does not lead to crashes for example it is invalid to add a field because existing stored data won t have the new field a static check of the access of the field would be valid but then a crash would occur in the interpreter when accessing the field because the field is missing in the decoded value wrong shape some rules importing contracts don t matter if a change breaks an importing contract that s valid this ensures that changes fixes can be applied at the root of the dependency chain it is not valid to change a field type to a subtype because existing stored data might be of a supertype remove conformance of composite to interface is ok the stored data only stores concrete type identifier changing the body of a function is valid as long as the signature stays the same
| 0
|
123,755
| 16,534,514,439
|
IssuesEvent
|
2021-05-27 10:10:57
|
edamontology/edam-browser
|
https://api.github.com/repos/edamontology/edam-browser
|
closed
|
Propose changing the mouse cursor to a hand when moving the tree around
|
ux/ui design
|
@matuskalas @hmenager @bryan-brancotte It could be useful to have a hand cursor icon when interacting with the tree instead of the mouse cursor to alert the user that they're able to pull and push the tree around. When hovering over the nodes on the tree, a pointer cursor appears, but outside of that there is only the mouse cursor.
Would having a hand/grabbing cursor be more helpful instead?
|
1.0
|
Propose changing the mouse cursor to a hand when moving the tree around - @matuskalas @hmenager @bryan-brancotte It could be useful to have a hand cursor icon when interacting with the tree instead of the mouse cursor to alert the user that they're able to pull and push the tree around. When hovering over the nodes on the tree, a pointer cursor appears, but outside of that there is only the mouse cursor.
Would having a hand/grabbing cursor be more helpful instead?
|
design
|
propose changing the mouse cursor to a hand when moving the tree around matuskalas hmenager bryan brancotte it could be useful to have a hand cursor icon when interacting with the tree instead of the mouse cursor to alert the user that they re able to pull and push the tree around when hovering over the nodes on the tree a pointer cursor appears but outside of that there is only the mouse cursor would having a hand grabbing cursor be more helpful instead
| 1
|
389,690
| 26,829,848,947
|
IssuesEvent
|
2023-02-02 15:18:50
|
Glassait/Computer_craft
|
https://api.github.com/repos/Glassait/Computer_craft
|
closed
|
[UPDATE] Rework Computer 3 Tellraw with strategy patter
|
documentation update
|
## **Update**
**Describe the solution you'd like**
Rework `ArenaTellraw` with strategy pattern
|
1.0
|
[UPDATE] Rework Computer 3 Tellraw with strategy patter - ## **Update**
**Describe the solution you'd like**
Rework `ArenaTellraw` with strategy pattern
|
non_design
|
rework computer tellraw with strategy patter update describe the solution you d like rework arenatellraw with strategy pattern
| 0
|
55,293
| 7,973,712,661
|
IssuesEvent
|
2018-07-17 00:48:37
|
nozavroni/csvelte
|
https://api.github.com/repos/nozavroni/csvelte
|
closed
|
Design stream decorator interface and functionality
|
documentation feature testing
|
I need a way to decorate a stream with functionality. I don't want to use inheritance because it's too restrictive. I want to to keep a stream exactly the same, only add decorator objects to it at runtime to add (or remove) functionality. For example,
``` php
$stream = Stream::open($filename, 'r+b');
// pseudo-code
// name is not set in stone by any means (came off the top of head)
$stream->decorate(new Stream\MakeBuffered);
// this would emulate the ability to seek on a non-seakable stream by reading
// it into a buffer and then seeking around on the buffer
$stream->decorate(new Stream\MakeSeekable);
```
|
1.0
|
Design stream decorator interface and functionality - I need a way to decorate a stream with functionality. I don't want to use inheritance because it's too restrictive. I want to to keep a stream exactly the same, only add decorator objects to it at runtime to add (or remove) functionality. For example,
``` php
$stream = Stream::open($filename, 'r+b');
// pseudo-code
// name is not set in stone by any means (came off the top of head)
$stream->decorate(new Stream\MakeBuffered);
// this would emulate the ability to seek on a non-seakable stream by reading
// it into a buffer and then seeking around on the buffer
$stream->decorate(new Stream\MakeSeekable);
```
|
non_design
|
design stream decorator interface and functionality i need a way to decorate a stream with functionality i don t want to use inheritance because it s too restrictive i want to to keep a stream exactly the same only add decorator objects to it at runtime to add or remove functionality for example php stream stream open filename r b pseudo code name is not set in stone by any means came off the top of head stream decorate new stream makebuffered this would emulate the ability to seek on a non seakable stream by reading it into a buffer and then seeking around on the buffer stream decorate new stream makeseekable
| 0
|
40,022
| 5,168,570,355
|
IssuesEvent
|
2017-01-17 21:57:02
|
maryvilledev/skilldirectoryui
|
https://api.github.com/repos/maryvilledev/skilldirectoryui
|
closed
|
Add a display of team information on the Home Page
|
in progress UIDesign
|
Display
```
Team Members: # (links to Team Page)
Unique Skills: # (links to Skills Page)+
Recent Skill Events: List Last 5 TM_Skill and/or Skill Reviews"
```
|
1.0
|
Add a display of team information on the Home Page - Display
```
Team Members: # (links to Team Page)
Unique Skills: # (links to Skills Page)+
Recent Skill Events: List Last 5 TM_Skill and/or Skill Reviews"
```
|
design
|
add a display of team information on the home page display team members links to team page unique skills links to skills page recent skill events list last tm skill and or skill reviews
| 1
|
136,976
| 5,290,986,694
|
IssuesEvent
|
2017-02-08 21:20:01
|
Alexey-Yakovenko/deadbeef
|
https://api.github.com/repos/Alexey-Yakovenko/deadbeef
|
closed
|
Very long files mess up due to sample count overflow
|
2.0 bug Priority-Medium
|
Original [issue 1108](https://code.google.com/p/ddb/issues/detail?id=1108) created by Alexey-Yakovenko on 2014-05-06T15:20:25.000Z:
<b>What steps will reproduce the problem?</b>
<b>Какие шаги приводят к воспроизведению</b>
<b>проблемы?</b>
1. Create a file longer than about 12.5 hours (at 44.1kHz)
2. Attempt to play
<b>3.</b>
<b>What is the expected output? What do you see instead?</b>
<b>Какой ожидаемый вывод? Что вы видите</b>
<b>вместо него?</b>
Depending on the codec, it may not play at all, or seeking may be really messed up.
<b>What version of the product are you using? On what operating system and CPU</b>
<b>architecture?</b>
<b>Какую версию продукта вы используете? На</b>
<b>какой операционной системе и</b>
<b>архитектуре CPU?</b>
trunk
Crunchbang Linux
Pentium 4
<b>How did you install the product?</b>
<b>Как вы установили продукт?</b>
Build from source
<b>Please provide any additional information below.</b>
<b>Пожалуйста, предоставьте любую</b>
<b>дополнительную информацию ниже.</b>
This appears to be due to startsample and endsample in ddb_playitem_t having simple int data types, so on 32 bit and some 64 bit platforms it is limited to about 2 billion samples. There may be other variables that have similar limits (cuesheets?). This is less than 3 hours at 192kHz, more at lower rates. Most people will never see this, but chain together a few albums and you'll hit the limit.
|
1.0
|
Very long files mess up due to sample count overflow - Original [issue 1108](https://code.google.com/p/ddb/issues/detail?id=1108) created by Alexey-Yakovenko on 2014-05-06T15:20:25.000Z:
<b>What steps will reproduce the problem?</b>
<b>Какие шаги приводят к воспроизведению</b>
<b>проблемы?</b>
1. Create a file longer than about 12.5 hours (at 44.1kHz)
2. Attempt to play
<b>3.</b>
<b>What is the expected output? What do you see instead?</b>
<b>Какой ожидаемый вывод? Что вы видите</b>
<b>вместо него?</b>
Depending on the codec, it may not play at all, or seeking may be really messed up.
<b>What version of the product are you using? On what operating system and CPU</b>
<b>architecture?</b>
<b>Какую версию продукта вы используете? На</b>
<b>какой операционной системе и</b>
<b>архитектуре CPU?</b>
trunk
Crunchbang Linux
Pentium 4
<b>How did you install the product?</b>
<b>Как вы установили продукт?</b>
Build from source
<b>Please provide any additional information below.</b>
<b>Пожалуйста, предоставьте любую</b>
<b>дополнительную информацию ниже.</b>
This appears to be due to startsample and endsample in ddb_playitem_t having simple int data types, so on 32 bit and some 64 bit platforms it is limited to about 2 billion samples. There may be other variables that have similar limits (cuesheets?). This is less than 3 hours at 192kHz, more at lower rates. Most people will never see this, but chain together a few albums and you'll hit the limit.
|
non_design
|
very long files mess up due to sample count overflow original created by alexey yakovenko on what steps will reproduce the problem какие шаги приводят к воспроизведению проблемы create a file longer than about hours at attempt to play what is the expected output what do you see instead какой ожидаемый вывод что вы видите вместо него depending on the codec it may not play at all or seeking may be really messed up what version of the product are you using on what operating system and cpu architecture какую версию продукта вы используете на какой операционной системе и архитектуре cpu trunk crunchbang linux pentium how did you install the product как вы установили продукт build from source please provide any additional information below пожалуйста предоставьте любую дополнительную информацию ниже this appears to be due to startsample and endsample in ddb playitem t having simple int data types so on bit and some bit platforms it is limited to about billion samples there may be other variables that have similar limits cuesheets this is less than hours at more at lower rates most people will never see this but chain together a few albums and you ll hit the limit
| 0
|
130,212
| 18,052,023,796
|
IssuesEvent
|
2021-09-19 22:36:48
|
alan-turing-institute/sktime
|
https://api.github.com/repos/alan-turing-institute/sktime
|
closed
|
Questions and comments on forecasting base classes and refactoring
|
API design module:forecasting
|
I am trying to understand as much as possible before doing any actual refactoring. Here are several comments/questions/suggestions. High chance I am mistaken or missing the point - if so, just say so!
1. _base.py. the docstrings that an end-user will see are the docstrings in the BaseForecaster. E.g. for `fit`, they will see docstring containing `The base forecaster specifies the methods and method signatures that all forecasters have to implement.`
2. _base.py. `update_predict`
1. What *is* `update_predict`? My guess is that it would be shorthand for `update` and then `predict` (similar to `fit_transform`). But this does not seem to be what is going on. Maybe it needs to be renamed.
2. I think `cv` needs to be renamed. `cv` stands for cross validation, but I do not think there is any cross validation happening here.
3. You raise a `NotImplementedError` if `return_pred_int`. I do not think we should have `NotImplementedError` in functions that will not be overwritten in children classes. In my head there are two options: have NotImplementedError in appropriate place in the children or simply not have `return_pred_int` as a parameter
4. Currently, `update_predict` does input checks and then calls` _predict_moving_cutoff`. This is confusing; it does not look like any updating happens. Furthermore, it is different convention to other functions: `fit` calls `_fit`, `predict` calls `_predict`. Note that my confusion here is related to point 2.i about not knowing what update_predict is intended to do.
3. `score`. minor points only:
1. change 'MAPE' to 'sMAPE' in first line of docstring
2. maybe rename 'score' to 'sMAPE_score' or 'sMAPE'??
3. where is this `score` method used?
4. `_get_y_pred` and `_get_pred_int`.
1. using the name `get` makes it sound like the method is a getter method (as in setters and getters), but I don't think these are getter methods. I suggest renaming these
2. the functions are hard to read. need to add some whitespace at least
3. `_get_pred_int` is used in only place (according to my vscode search), namely _tbats. seems unusual that a helper function defined in base is used in only one place, but maybe there is intentions to use it more.
5. `_set_fh`. The very first if condition and error message seems incorrect to me. We have `if not requires_fh` in if condition and the error message says 'fh must be passed'. Presumably the rest of the if loops need to be checked; I have not checked them.
|
1.0
|
Questions and comments on forecasting base classes and refactoring - I am trying to understand as much as possible before doing any actual refactoring. Here are several comments/questions/suggestions. High chance I am mistaken or missing the point - if so, just say so!
1. _base.py. the docstrings that an end-user will see are the docstrings in the BaseForecaster. E.g. for `fit`, they will see docstring containing `The base forecaster specifies the methods and method signatures that all forecasters have to implement.`
2. _base.py. `update_predict`
1. What *is* `update_predict`? My guess is that it would be shorthand for `update` and then `predict` (similar to `fit_transform`). But this does not seem to be what is going on. Maybe it needs to be renamed.
2. I think `cv` needs to be renamed. `cv` stands for cross validation, but I do not think there is any cross validation happening here.
3. You raise a `NotImplementedError` if `return_pred_int`. I do not think we should have `NotImplementedError` in functions that will not be overwritten in children classes. In my head there are two options: have NotImplementedError in appropriate place in the children or simply not have `return_pred_int` as a parameter
4. Currently, `update_predict` does input checks and then calls` _predict_moving_cutoff`. This is confusing; it does not look like any updating happens. Furthermore, it is different convention to other functions: `fit` calls `_fit`, `predict` calls `_predict`. Note that my confusion here is related to point 2.i about not knowing what update_predict is intended to do.
3. `score`. minor points only:
1. change 'MAPE' to 'sMAPE' in first line of docstring
2. maybe rename 'score' to 'sMAPE_score' or 'sMAPE'??
3. where is this `score` method used?
4. `_get_y_pred` and `_get_pred_int`.
1. using the name `get` makes it sound like the method is a getter method (as in setters and getters), but I don't think these are getter methods. I suggest renaming these
2. the functions are hard to read. need to add some whitespace at least
3. `_get_pred_int` is used in only place (according to my vscode search), namely _tbats. seems unusual that a helper function defined in base is used in only one place, but maybe there is intentions to use it more.
5. `_set_fh`. The very first if condition and error message seems incorrect to me. We have `if not requires_fh` in if condition and the error message says 'fh must be passed'. Presumably the rest of the if loops need to be checked; I have not checked them.
|
design
|
questions and comments on forecasting base classes and refactoring i am trying to understand as much as possible before doing any actual refactoring here are several comments questions suggestions high chance i am mistaken or missing the point if so just say so base py the docstrings that an end user will see are the docstrings in the baseforecaster e g for fit they will see docstring containing the base forecaster specifies the methods and method signatures that all forecasters have to implement base py update predict what is update predict my guess is that it would be shorthand for update and then predict similar to fit transform but this does not seem to be what is going on maybe it needs to be renamed i think cv needs to be renamed cv stands for cross validation but i do not think there is any cross validation happening here you raise a notimplementederror if return pred int i do not think we should have notimplementederror in functions that will not be overwritten in children classes in my head there are two options have notimplementederror in appropriate place in the children or simply not have return pred int as a parameter currently update predict does input checks and then calls predict moving cutoff this is confusing it does not look like any updating happens furthermore it is different convention to other functions fit calls fit predict calls predict note that my confusion here is related to point i about not knowing what update predict is intended to do score minor points only change mape to smape in first line of docstring maybe rename score to smape score or smape where is this score method used get y pred and get pred int using the name get makes it sound like the method is a getter method as in setters and getters but i don t think these are getter methods i suggest renaming these the functions are hard to read need to add some whitespace at least get pred int is used in only place according to my vscode search namely tbats seems unusual that a helper function defined in base is used in only one place but maybe there is intentions to use it more set fh the very first if condition and error message seems incorrect to me we have if not requires fh in if condition and the error message says fh must be passed presumably the rest of the if loops need to be checked i have not checked them
| 1
|
30,721
| 11,842,888,134
|
IssuesEvent
|
2020-03-24 00:28:06
|
MicrosoftDocs/vsts-docs
|
https://api.github.com/repos/MicrosoftDocs/vsts-docs
|
closed
|
Links from this page don't resolve to expected content
|
Pri2 devops-security/tech devops/prod doc-enhancement
|
When clicking on a link in the index, I'm redirected to a content page that doesn't contain the expected information. For example, I want to know more about "Make requests on behalf of others". The link goes to a page that doesn't tell me anything about the permission I'm keen to know more about. This is one or many examples. Make it simple please. 🙏
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: c399d3d3-3442-91a7-eb72-f0451b735cd1
* Version Independent ID: 5c4f77ec-5ef8-afe7-8e96-f1b4238f8f44
* Content: [Permissions and role lookup guide - Azure DevOps](https://docs.microsoft.com/en-us/azure/devops/organizations/security/permissions-lookup-guide?toc=%2Fazure%2Fdevops%2Fsecurity-access-billing%2Ftoc.json&bc=%2Fazure%2Fdevops%2Fsecurity-access-billing%2Fbreadcrumb%2Ftoc.json&view=azure-devops#feedback)
* Content Source: [docs/organizations/security/permissions-lookup-guide.md](https://github.com/MicrosoftDocs/vsts-docs/blob/master/docs/organizations/security/permissions-lookup-guide.md)
* Product: **devops**
* Technology: **devops-security**
* GitHub Login: @KathrynEE
* Microsoft Alias: **kaelli**
|
True
|
Links from this page don't resolve to expected content - When clicking on a link in the index, I'm redirected to a content page that doesn't contain the expected information. For example, I want to know more about "Make requests on behalf of others". The link goes to a page that doesn't tell me anything about the permission I'm keen to know more about. This is one or many examples. Make it simple please. 🙏
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: c399d3d3-3442-91a7-eb72-f0451b735cd1
* Version Independent ID: 5c4f77ec-5ef8-afe7-8e96-f1b4238f8f44
* Content: [Permissions and role lookup guide - Azure DevOps](https://docs.microsoft.com/en-us/azure/devops/organizations/security/permissions-lookup-guide?toc=%2Fazure%2Fdevops%2Fsecurity-access-billing%2Ftoc.json&bc=%2Fazure%2Fdevops%2Fsecurity-access-billing%2Fbreadcrumb%2Ftoc.json&view=azure-devops#feedback)
* Content Source: [docs/organizations/security/permissions-lookup-guide.md](https://github.com/MicrosoftDocs/vsts-docs/blob/master/docs/organizations/security/permissions-lookup-guide.md)
* Product: **devops**
* Technology: **devops-security**
* GitHub Login: @KathrynEE
* Microsoft Alias: **kaelli**
|
non_design
|
links from this page don t resolve to expected content when clicking on a link in the index i m redirected to a content page that doesn t contain the expected information for example i want to know more about make requests on behalf of others the link goes to a page that doesn t tell me anything about the permission i m keen to know more about this is one or many examples make it simple please 🙏 document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source product devops technology devops security github login kathrynee microsoft alias kaelli
| 0
|
114,916
| 14,663,299,725
|
IssuesEvent
|
2020-12-29 09:23:38
|
Runbhumi/Runbhumi
|
https://api.github.com/repos/Runbhumi/Runbhumi
|
closed
|
add events info page
|
design enhancement frontend
|
**Describe the solution you'd like**
when the event card is pressed it should open up a page which has all the buttons and other info init
|
1.0
|
add events info page - **Describe the solution you'd like**
when the event card is pressed it should open up a page which has all the buttons and other info init
|
design
|
add events info page describe the solution you d like when the event card is pressed it should open up a page which has all the buttons and other info init
| 1
|
68,168
| 8,224,818,242
|
IssuesEvent
|
2018-09-06 14:39:24
|
covexo/devspace
|
https://api.github.com/repos/covexo/devspace
|
closed
|
v1.Config.DevSpace.SyncConfig.ExcludePaths/DownloadExcludePaths/UploadExcludePaths
|
area/sync kind/design kind/documentation kind/enhancement priority/backlog
|
- [x] Make design decision regarding ignorefile vs config @FabianK1991
- [x] Change code
- [x] Add documentation
|
1.0
|
v1.Config.DevSpace.SyncConfig.ExcludePaths/DownloadExcludePaths/UploadExcludePaths - - [x] Make design decision regarding ignorefile vs config @FabianK1991
- [x] Change code
- [x] Add documentation
|
design
|
config devspace syncconfig excludepaths downloadexcludepaths uploadexcludepaths make design decision regarding ignorefile vs config change code add documentation
| 1
|
156,389
| 24,613,093,119
|
IssuesEvent
|
2022-10-15 01:35:39
|
Ronneesley/quizestatistico
|
https://api.github.com/repos/Ronneesley/quizestatistico
|
closed
|
Criar página HTML descrevendo os conceitos: o que é, população, amostra, elemento
|
4 dev design html entregar proxima semana
|
● O que é estatística descritiva?
● População.
● Amostra.
● Elemento.
|
1.0
|
Criar página HTML descrevendo os conceitos: o que é, população, amostra, elemento - ● O que é estatística descritiva?
● População.
● Amostra.
● Elemento.
|
design
|
criar página html descrevendo os conceitos o que é população amostra elemento ● o que é estatística descritiva ● população ● amostra ● elemento
| 1
|
411,668
| 12,027,337,875
|
IssuesEvent
|
2020-04-12 17:57:26
|
cci-toast/backend
|
https://api.github.com/repos/cci-toast/backend
|
opened
|
Create a model for Debt
|
Priority 1
|
This will be a separate model and will have its own end-points for GET, POST, PATCH
Fields required:
- [ ] debt_monthly_amount
- [ ] debt_remaining_total
- [ ] debt_interest_rate
|
1.0
|
Create a model for Debt - This will be a separate model and will have its own end-points for GET, POST, PATCH
Fields required:
- [ ] debt_monthly_amount
- [ ] debt_remaining_total
- [ ] debt_interest_rate
|
non_design
|
create a model for debt this will be a separate model and will have its own end points for get post patch fields required debt monthly amount debt remaining total debt interest rate
| 0
|
153,086
| 24,066,708,464
|
IssuesEvent
|
2022-09-17 15:45:52
|
vegaprotocol/brand
|
https://api.github.com/repos/vegaprotocol/brand
|
opened
|
Create brand guidelines
|
ux & visual design brand
|
As the Vega team or community member
I want to be able to understand how to use the Vega brand and it's assets
So that I can easily and effectively create projects that look and feel like part of the Vega ecosystem
**Acceptance Criteria**
- I can read about how to use the Vega brand - including logo, typography, visual styles etc.
- I can find and use all the key brand assets in the brand repo
- I can learn about the Vega Tone of Voice and examples of it's use
- I am pointed in the direction of external tools to help me implement the brand i.e. Figma Design System, Storybook etc.
|
1.0
|
Create brand guidelines - As the Vega team or community member
I want to be able to understand how to use the Vega brand and it's assets
So that I can easily and effectively create projects that look and feel like part of the Vega ecosystem
**Acceptance Criteria**
- I can read about how to use the Vega brand - including logo, typography, visual styles etc.
- I can find and use all the key brand assets in the brand repo
- I can learn about the Vega Tone of Voice and examples of it's use
- I am pointed in the direction of external tools to help me implement the brand i.e. Figma Design System, Storybook etc.
|
design
|
create brand guidelines as the vega team or community member i want to be able to understand how to use the vega brand and it s assets so that i can easily and effectively create projects that look and feel like part of the vega ecosystem acceptance criteria i can read about how to use the vega brand including logo typography visual styles etc i can find and use all the key brand assets in the brand repo i can learn about the vega tone of voice and examples of it s use i am pointed in the direction of external tools to help me implement the brand i e figma design system storybook etc
| 1
|
60,945
| 7,431,720,425
|
IssuesEvent
|
2018-03-25 17:27:05
|
rkt/rkt
|
https://api.github.com/repos/rkt/rkt
|
closed
|
run-prepared: restarting exited pods
|
area/usability kind/design kind/enhancement kind/question
|
**Environment**
Linux ubuntu-1gb-blr1-01 4.4.0-83-generic # 106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
```rkt Version: 1.27.0
appc Version: 0.8.10
Go Version: go1.7.4
Go OS/Arch: linux/amd64
Features: -TPM +SDJOURNAL
--
Linux 4.4.0-83-generic x86_64
--
NAME="Ubuntu"
VERSION="16.04.2 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
--
systemd 229
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN
```
**What did you do?**
```
root@ubuntu-1gb-blr1-01:/# rkt run quay.io/coreos/alpine-sh --interactive
/ # ls
bin dev etc home lib linuxrc media mnt proc root run sbin sys tmp usr var
/ # }}}Container rkt-0ea19d08-0cc8-4e90-8997-051764083fc0 terminated by signal KILL.
root@ubuntu-1gb-blr1-01:/#
root@ubuntu-1gb-blr1-01:/# rkt list
UUID APP IMAGE NAME STATE CREATED STARTED NETWORKS
0ea19d08 alpine-sh quay.io/coreos/alpine-sh:latest exited 34 seconds ago 34 seconds ago
root@ubuntu-1gb-blr1-01:/# rkt run-prepared 0ea19d08
run-prepared: pod "0ea19d08-0cc8-4e90-8997-051764083fc0" is not prepared
```
**What did you expect to see?**
well, a restarted pod
i want to re-run an exit'd pod
**What did you see instead?**
```
root@ubuntu-1gb-blr1-01:/# rkt run-prepared 0ea19d08
run-prepared: pod "0ea19d08-0cc8-4e90-8997-051764083fc0" is not prepared
```
|
1.0
|
run-prepared: restarting exited pods - **Environment**
Linux ubuntu-1gb-blr1-01 4.4.0-83-generic # 106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
```rkt Version: 1.27.0
appc Version: 0.8.10
Go Version: go1.7.4
Go OS/Arch: linux/amd64
Features: -TPM +SDJOURNAL
--
Linux 4.4.0-83-generic x86_64
--
NAME="Ubuntu"
VERSION="16.04.2 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
--
systemd 229
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN
```
**What did you do?**
```
root@ubuntu-1gb-blr1-01:/# rkt run quay.io/coreos/alpine-sh --interactive
/ # ls
bin dev etc home lib linuxrc media mnt proc root run sbin sys tmp usr var
/ # }}}Container rkt-0ea19d08-0cc8-4e90-8997-051764083fc0 terminated by signal KILL.
root@ubuntu-1gb-blr1-01:/#
root@ubuntu-1gb-blr1-01:/# rkt list
UUID APP IMAGE NAME STATE CREATED STARTED NETWORKS
0ea19d08 alpine-sh quay.io/coreos/alpine-sh:latest exited 34 seconds ago 34 seconds ago
root@ubuntu-1gb-blr1-01:/# rkt run-prepared 0ea19d08
run-prepared: pod "0ea19d08-0cc8-4e90-8997-051764083fc0" is not prepared
```
**What did you expect to see?**
well, a restarted pod
i want to re-run an exit'd pod
**What did you see instead?**
```
root@ubuntu-1gb-blr1-01:/# rkt run-prepared 0ea19d08
run-prepared: pod "0ea19d08-0cc8-4e90-8997-051764083fc0" is not prepared
```
|
design
|
run prepared restarting exited pods environment linux ubuntu generic ubuntu smp mon jun utc gnu linux rkt version appc version go version go os arch linux features tpm sdjournal linux generic name ubuntu version lts xenial xerus id ubuntu id like debian pretty name ubuntu lts version id home url support url bug report url version codename xenial ubuntu codename xenial systemd pam audit selinux ima apparmor smack sysvinit utmp libcryptsetup gcrypt gnutls acl xz seccomp blkid elfutils kmod idn what did you do root ubuntu rkt run quay io coreos alpine sh interactive ls bin dev etc home lib linuxrc media mnt proc root run sbin sys tmp usr var container rkt terminated by signal kill root ubuntu root ubuntu rkt list uuid app image name state created started networks alpine sh quay io coreos alpine sh latest exited seconds ago seconds ago root ubuntu rkt run prepared run prepared pod is not prepared what did you expect to see well a restarted pod i want to re run an exit d pod what did you see instead root ubuntu rkt run prepared run prepared pod is not prepared
| 1
|
51,874
| 6,553,440,728
|
IssuesEvent
|
2017-09-05 22:38:59
|
flutter/flutter
|
https://api.github.com/repos/flutter/flutter
|
opened
|
Hero should link to something that explains what a Hero Animation is
|
dev: docs - api prod: material design
|
https://docs.flutter.io/flutter/widgets/Hero-class.html
Doesn't link to any part of the Material Design spec which explains/shows what a hero animation is. It's not clear to me (from some minimal searching) that hero is a term which is used in Material?
|
1.0
|
Hero should link to something that explains what a Hero Animation is - https://docs.flutter.io/flutter/widgets/Hero-class.html
Doesn't link to any part of the Material Design spec which explains/shows what a hero animation is. It's not clear to me (from some minimal searching) that hero is a term which is used in Material?
|
design
|
hero should link to something that explains what a hero animation is doesn t link to any part of the material design spec which explains shows what a hero animation is it s not clear to me from some minimal searching that hero is a term which is used in material
| 1
|
261,006
| 27,785,094,101
|
IssuesEvent
|
2023-03-17 02:02:41
|
kapseliboi/bui
|
https://api.github.com/repos/kapseliboi/bui
|
opened
|
CVE-2023-28155 (Medium) detected in request-2.88.2.tgz
|
Mend: dependency security vulnerability
|
## CVE-2023-28155 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>request-2.88.2.tgz</b></p></summary>
<p>Simplified HTTP request client.</p>
<p>Library home page: <a href="https://registry.npmjs.org/request/-/request-2.88.2.tgz">https://registry.npmjs.org/request/-/request-2.88.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/request/package.json</p>
<p>
Dependency Hierarchy:
- parcel-bundler-1.12.5.tgz (Root Library)
- htmlnano-0.2.9.tgz
- uncss-0.17.3.tgz
- :x: **request-2.88.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kapseliboi/bui/commit/e8304e6335e5d45f5599a6dd9950348f734192b7">e8304e6335e5d45f5599a6dd9950348f734192b7</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>
** UNSUPPORTED WHEN ASSIGNED ** The Request package through 2.88.1 for Node.js allows a bypass of SSRF mitigations via an attacker-controller server that does a cross-protocol redirect (HTTP to HTTPS, or HTTPS to HTTP). NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
<p>Publish Date: 2023-03-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-28155>CVE-2023-28155</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2023-28155 (Medium) detected in request-2.88.2.tgz - ## CVE-2023-28155 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>request-2.88.2.tgz</b></p></summary>
<p>Simplified HTTP request client.</p>
<p>Library home page: <a href="https://registry.npmjs.org/request/-/request-2.88.2.tgz">https://registry.npmjs.org/request/-/request-2.88.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/request/package.json</p>
<p>
Dependency Hierarchy:
- parcel-bundler-1.12.5.tgz (Root Library)
- htmlnano-0.2.9.tgz
- uncss-0.17.3.tgz
- :x: **request-2.88.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kapseliboi/bui/commit/e8304e6335e5d45f5599a6dd9950348f734192b7">e8304e6335e5d45f5599a6dd9950348f734192b7</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>
** UNSUPPORTED WHEN ASSIGNED ** The Request package through 2.88.1 for Node.js allows a bypass of SSRF mitigations via an attacker-controller server that does a cross-protocol redirect (HTTP to HTTPS, or HTTPS to HTTP). NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
<p>Publish Date: 2023-03-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-28155>CVE-2023-28155</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_design
|
cve medium detected in request tgz cve medium severity vulnerability vulnerable library request tgz simplified http request client library home page a href path to dependency file package json path to vulnerable library node modules request package json dependency hierarchy parcel bundler tgz root library htmlnano tgz uncss tgz x request tgz vulnerable library found in head commit a href found in base branch master vulnerability details unsupported when assigned the request package through for node js allows a bypass of ssrf mitigations via an attacker controller server that does a cross protocol redirect http to https or https to http note this vulnerability only affects products that are no longer supported by the maintainer publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href step up your open source security game with mend
| 0
|
156,895
| 24,626,173,235
|
IssuesEvent
|
2022-10-16 14:51:41
|
dotnet/efcore
|
https://api.github.com/repos/dotnet/efcore
|
closed
|
Null encapsulated collection using PropertyAccessMode.Field and Lazy Loading Proxies
|
closed-by-design customer-reported
|
<!-- Describe what isn't working as expected -->
I have an encapsulated one to many collection:
```C#
private readonly ICollection<Proficiency> _proficiencies;
```
which is accessed by some simple logic within the domain object, and has a public accessor property:
```C#
public virtual IEnumerable<Proficiency> Proficiencies { get { return _proficiencies.ToList(); } }}
```
```C#
public virtual bool HasProficiencyAt(int skillLevel)
{
return _proficiencies.Any(p => p.SkillLevel == skillLevel);
```
This is mapped as follows:
```C#
builder.HasMany(s => s.Proficiencies).WithOne().HasForeignKey(p => p.SkillUid);
builder.Metadata
.FindNavigation(nameof(Domain.Ibm.Skill.Proficiencies))
.SetPropertyAccessMode(PropertyAccessMode.Field);
````
If an entity is loaded from the db and the HasProficiencyAt(int skillLevel) method is called by the client code BEFORE the public accessor propery has been called, then the encapsulated _proficiencies collection is null.
So this does not work:
```C#
if(skill.HasProficiencyAt(skillLevel))
{
```
But this does:
```C#
IEnumerable<Proficiency> ps = skill.Proficiencies;
if(skill.HasProficiencyAt(skillLevel))
{
````
Note this is with LazyLoadingProxies turned on.
Stepping through in the debugger and viewing the object causes the proxy to initialize properly and the bug is then avoided.
EF Core version: 3.0
Target framework: NET Core 3.0
IDE: Visual Studio 2019 16.3.1
|
1.0
|
Null encapsulated collection using PropertyAccessMode.Field and Lazy Loading Proxies - <!-- Describe what isn't working as expected -->
I have an encapsulated one to many collection:
```C#
private readonly ICollection<Proficiency> _proficiencies;
```
which is accessed by some simple logic within the domain object, and has a public accessor property:
```C#
public virtual IEnumerable<Proficiency> Proficiencies { get { return _proficiencies.ToList(); } }}
```
```C#
public virtual bool HasProficiencyAt(int skillLevel)
{
return _proficiencies.Any(p => p.SkillLevel == skillLevel);
```
This is mapped as follows:
```C#
builder.HasMany(s => s.Proficiencies).WithOne().HasForeignKey(p => p.SkillUid);
builder.Metadata
.FindNavigation(nameof(Domain.Ibm.Skill.Proficiencies))
.SetPropertyAccessMode(PropertyAccessMode.Field);
````
If an entity is loaded from the db and the HasProficiencyAt(int skillLevel) method is called by the client code BEFORE the public accessor propery has been called, then the encapsulated _proficiencies collection is null.
So this does not work:
```C#
if(skill.HasProficiencyAt(skillLevel))
{
```
But this does:
```C#
IEnumerable<Proficiency> ps = skill.Proficiencies;
if(skill.HasProficiencyAt(skillLevel))
{
````
Note this is with LazyLoadingProxies turned on.
Stepping through in the debugger and viewing the object causes the proxy to initialize properly and the bug is then avoided.
EF Core version: 3.0
Target framework: NET Core 3.0
IDE: Visual Studio 2019 16.3.1
|
design
|
null encapsulated collection using propertyaccessmode field and lazy loading proxies i have an encapsulated one to many collection c private readonly icollection proficiencies which is accessed by some simple logic within the domain object and has a public accessor property c public virtual ienumerable proficiencies get return proficiencies tolist c public virtual bool hasproficiencyat int skilllevel return proficiencies any p p skilllevel skilllevel this is mapped as follows c builder hasmany s s proficiencies withone hasforeignkey p p skilluid builder metadata findnavigation nameof domain ibm skill proficiencies setpropertyaccessmode propertyaccessmode field if an entity is loaded from the db and the hasproficiencyat int skilllevel method is called by the client code before the public accessor propery has been called then the encapsulated proficiencies collection is null so this does not work c if skill hasproficiencyat skilllevel but this does c ienumerable ps skill proficiencies if skill hasproficiencyat skilllevel note this is with lazyloadingproxies turned on stepping through in the debugger and viewing the object causes the proxy to initialize properly and the bug is then avoided ef core version target framework net core ide visual studio
| 1
|
53,763
| 6,757,402,980
|
IssuesEvent
|
2017-10-24 10:40:02
|
WordPress/gutenberg
|
https://api.github.com/repos/WordPress/gutenberg
|
closed
|
Inserter: go larger font-size and single column
|
Accessibility Design Priority High [Component] Inserter
|
I struggle with the current inspector in quickly finding the right blocks. Somehow having to scan both horizontally and vertically is adding cognitive load. I propose we explore going single column and larger font-size:
|
1.0
|
Inserter: go larger font-size and single column - I struggle with the current inspector in quickly finding the right blocks. Somehow having to scan both horizontally and vertically is adding cognitive load. I propose we explore going single column and larger font-size:
|
design
|
inserter go larger font size and single column i struggle with the current inspector in quickly finding the right blocks somehow having to scan both horizontally and vertically is adding cognitive load i propose we explore going single column and larger font size
| 1
|
4,818
| 2,610,157,274
|
IssuesEvent
|
2015-02-26 18:49:59
|
chrsmith/republic-at-war
|
https://api.github.com/repos/chrsmith/republic-at-war
|
opened
|
Text
|
auto-migrated Priority-Medium Type-Defect
|
```
FIx new planet descriptions
```
-----
Original issue reported on code.google.com by `z3r0...@gmail.com` on 30 Jan 2011 at 2:42
|
1.0
|
Text - ```
FIx new planet descriptions
```
-----
Original issue reported on code.google.com by `z3r0...@gmail.com` on 30 Jan 2011 at 2:42
|
non_design
|
text fix new planet descriptions original issue reported on code google com by gmail com on jan at
| 0
|
8,477
| 22,621,865,834
|
IssuesEvent
|
2022-06-30 07:14:17
|
kubernetes/enhancements
|
https://api.github.com/repos/kubernetes/enhancements
|
closed
|
Clarify or remove the "status is only observations" rule
|
sig/architecture lifecycle/rotten
|
# Enhancement Description
- One-line enhancement description: Clarify if/how controllers can use status to track non-observable state
- Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/2527-clarify-status-observations-vs-rbac
- Discussion Link: https://groups.google.com/g/kubernetes-sig-architecture/c/d96tt2Mw69s
- Primary contact (assignee): thockin
- Responsible SIGs: sig-architecture
- Enhancement target (which target equals to which milestone): N/A
<!-- Uncomment these as you prepare the enhancement for the next stage
- Alpha release target (x.y):
- Beta release target (x.y):
- Stable release target (x.y):
- [ ] Alpha
- [ ] KEP (`k/enhancements`) update PR(s):
- [ ] Code (`k/k`) update PR(s):
- [ ] Docs (`k/website`) update PR(s):
- [ ] Beta
- [ ] KEP (`k/enhancements`) update PR(s):
- [ ] Code (`k/k`) update PR(s):
- [ ] Docs (`k/website`) update(s):
- [ ] Stable
- [ ] KEP (`k/enhancements`) update PR(s):
- [ ] Code (`k/k`) update PR(s):
- [ ] Docs (`k/website`) update(s):
-->
|
1.0
|
Clarify or remove the "status is only observations" rule - # Enhancement Description
- One-line enhancement description: Clarify if/how controllers can use status to track non-observable state
- Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/2527-clarify-status-observations-vs-rbac
- Discussion Link: https://groups.google.com/g/kubernetes-sig-architecture/c/d96tt2Mw69s
- Primary contact (assignee): thockin
- Responsible SIGs: sig-architecture
- Enhancement target (which target equals to which milestone): N/A
<!-- Uncomment these as you prepare the enhancement for the next stage
- Alpha release target (x.y):
- Beta release target (x.y):
- Stable release target (x.y):
- [ ] Alpha
- [ ] KEP (`k/enhancements`) update PR(s):
- [ ] Code (`k/k`) update PR(s):
- [ ] Docs (`k/website`) update PR(s):
- [ ] Beta
- [ ] KEP (`k/enhancements`) update PR(s):
- [ ] Code (`k/k`) update PR(s):
- [ ] Docs (`k/website`) update(s):
- [ ] Stable
- [ ] KEP (`k/enhancements`) update PR(s):
- [ ] Code (`k/k`) update PR(s):
- [ ] Docs (`k/website`) update(s):
-->
|
non_design
|
clarify or remove the status is only observations rule enhancement description one line enhancement description clarify if how controllers can use status to track non observable state kubernetes enhancement proposal discussion link primary contact assignee thockin responsible sigs sig architecture enhancement target which target equals to which milestone n a uncomment these as you prepare the enhancement for the next stage alpha release target x y beta release target x y stable release target x y alpha kep k enhancements update pr s code k k update pr s docs k website update pr s beta kep k enhancements update pr s code k k update pr s docs k website update s stable kep k enhancements update pr s code k k update pr s docs k website update s
| 0
|
139,556
| 20,910,036,405
|
IssuesEvent
|
2022-03-24 08:25:34
|
vector-im/element-ios
|
https://api.github.com/repos/vector-im/element-ios
|
closed
|
[Spaces] M11.11 Expose legacy Communities -> Spaces migrator on Web
|
X-Needs-Design A-Spaces
|
* Somewhere sensible, we should let people know a migrator exists on Element Web
* Related issue: https://github.com/vector-im/element-web/issues/18092
|
1.0
|
[Spaces] M11.11 Expose legacy Communities -> Spaces migrator on Web - * Somewhere sensible, we should let people know a migrator exists on Element Web
* Related issue: https://github.com/vector-im/element-web/issues/18092
|
design
|
expose legacy communities spaces migrator on web somewhere sensible we should let people know a migrator exists on element web related issue
| 1
|
122,454
| 16,129,609,391
|
IssuesEvent
|
2021-04-29 01:03:03
|
neuroailab/tdw_physics
|
https://api.github.com/repos/neuroailab/tdw_physics
|
closed
|
Collision: additional variance
|
controller-design
|
Collisions with one or more intermediate objects
Scenes with 2+ moving objects, requiring harder trajectory estimation
Collisions where impacting object is pointy
|
1.0
|
Collision: additional variance - Collisions with one or more intermediate objects
Scenes with 2+ moving objects, requiring harder trajectory estimation
Collisions where impacting object is pointy
|
design
|
collision additional variance collisions with one or more intermediate objects scenes with moving objects requiring harder trajectory estimation collisions where impacting object is pointy
| 1
|
120,079
| 15,701,259,389
|
IssuesEvent
|
2021-03-26 10:57:08
|
OurMachinery/themachinery-public
|
https://api.github.com/repos/OurMachinery/themachinery-public
|
closed
|
Cannot input Russian text
|
by-design design-decision enhancement later
|
The Machinery 2021.2.a
Windows 10 Pro Version 1909
When trying to input text in Russian keyboard layout into a text field, it looks as if an incorrect 8-bit encoding is used instead of UTF-8. For example, instead of `Привет` you get `Ïðèâåò`.
Also, if you try to copy and paste `Привет`, you get spaces instead of the string.
|
2.0
|
Cannot input Russian text - The Machinery 2021.2.a
Windows 10 Pro Version 1909
When trying to input text in Russian keyboard layout into a text field, it looks as if an incorrect 8-bit encoding is used instead of UTF-8. For example, instead of `Привет` you get `Ïðèâåò`.
Also, if you try to copy and paste `Привет`, you get spaces instead of the string.
|
design
|
cannot input russian text the machinery a windows pro version when trying to input text in russian keyboard layout into a text field it looks as if an incorrect bit encoding is used instead of utf for example instead of привет you get ïðèâåò also if you try to copy and paste привет you get spaces instead of the string
| 1
|
35,510
| 4,684,170,036
|
IssuesEvent
|
2016-10-10 02:35:56
|
ceylon/ceylon.ast
|
https://api.github.com/repos/ceylon/ceylon.ast
|
closed
|
Should ceylon.ast comply with the compiler instead of the specification?
|
API design discussion
|
The `ceylon.ast.core` module documentation says:
> `ceylon.ast` seeks to comply only with the [Ceylon Language Specification][spec], not its implementation in the compiler.
[spec]: https://ceylon-lang.org/documentation/1.3/spec/html_single/
Should we abandon this, and instead seek compliance with the compiler?
If yes: how far do we go? The module documentation cites the example of empty resource lists for `try`, which are permitted by the grammar so that the compiler can give you a better error message than a syntax error. Should cases like this be allowed as well, or only cases that are actually legal on at least one backend, without any error messages, like #122?
Pros:
- It would probably make `ceylon.ast` more useful.
- @jvasileff might finally stop pestering me with non-bugs like #122.
Cons:
- The additional rules in the compiler are undocumented and subject to change with even less notice than the specification. I recall several cases where I only noticed a spec change relevant to `ceylon.ast` or `ceylon.formatter` by sheer luck, and it’s likely that I already missed some that @gavinking smuggled past me. I can’t imagine how I could hope to keep up with the compiler if *every* change potentially needs to be reflected by `ceylon.ast`.
- If a feature is later adopted in the specification, the specification’s description of it might be different from the `ceylon.ast` model, and `ceylon.ast` would have to be updated, breaking users’ code.
- We boast an “exhaustive… specification” in our [quick intro](https://ceylon-lang.org/documentation/current/introduction/), so this issue *should* not even be up for debate in my opinion.
- @jvasileff might pester me with a lot more now-actually-bugs like #122.
|
1.0
|
Should ceylon.ast comply with the compiler instead of the specification? - The `ceylon.ast.core` module documentation says:
> `ceylon.ast` seeks to comply only with the [Ceylon Language Specification][spec], not its implementation in the compiler.
[spec]: https://ceylon-lang.org/documentation/1.3/spec/html_single/
Should we abandon this, and instead seek compliance with the compiler?
If yes: how far do we go? The module documentation cites the example of empty resource lists for `try`, which are permitted by the grammar so that the compiler can give you a better error message than a syntax error. Should cases like this be allowed as well, or only cases that are actually legal on at least one backend, without any error messages, like #122?
Pros:
- It would probably make `ceylon.ast` more useful.
- @jvasileff might finally stop pestering me with non-bugs like #122.
Cons:
- The additional rules in the compiler are undocumented and subject to change with even less notice than the specification. I recall several cases where I only noticed a spec change relevant to `ceylon.ast` or `ceylon.formatter` by sheer luck, and it’s likely that I already missed some that @gavinking smuggled past me. I can’t imagine how I could hope to keep up with the compiler if *every* change potentially needs to be reflected by `ceylon.ast`.
- If a feature is later adopted in the specification, the specification’s description of it might be different from the `ceylon.ast` model, and `ceylon.ast` would have to be updated, breaking users’ code.
- We boast an “exhaustive… specification” in our [quick intro](https://ceylon-lang.org/documentation/current/introduction/), so this issue *should* not even be up for debate in my opinion.
- @jvasileff might pester me with a lot more now-actually-bugs like #122.
|
design
|
should ceylon ast comply with the compiler instead of the specification the ceylon ast core module documentation says ceylon ast seeks to comply only with the not its implementation in the compiler should we abandon this and instead seek compliance with the compiler if yes how far do we go the module documentation cites the example of empty resource lists for try which are permitted by the grammar so that the compiler can give you a better error message than a syntax error should cases like this be allowed as well or only cases that are actually legal on at least one backend without any error messages like pros it would probably make ceylon ast more useful jvasileff might finally stop pestering me with non bugs like cons the additional rules in the compiler are undocumented and subject to change with even less notice than the specification i recall several cases where i only noticed a spec change relevant to ceylon ast or ceylon formatter by sheer luck and it’s likely that i already missed some that gavinking smuggled past me i can’t imagine how i could hope to keep up with the compiler if every change potentially needs to be reflected by ceylon ast if a feature is later adopted in the specification the specification’s description of it might be different from the ceylon ast model and ceylon ast would have to be updated breaking users’ code we boast an “exhaustive… specification” in our so this issue should not even be up for debate in my opinion jvasileff might pester me with a lot more now actually bugs like
| 1
|
97,124
| 12,215,762,986
|
IssuesEvent
|
2020-05-01 13:42:28
|
JuliaRobotics/DistributedFactorGraphs.jl
|
https://api.github.com/repos/JuliaRobotics/DistributedFactorGraphs.jl
|
closed
|
Sentinel node behavior in CGDFG and matching InMemory
|
cloudgraphs design designdecision user experience
|
We have to define how user/robot/session nodes are handled.
My suggestion is to always force user/robot and auto generate session if it is not supplied. I previously used `string(uuid4())[1:6]`
user/robot can default to something like defaultUser/defaultRobot
|
2.0
|
Sentinel node behavior in CGDFG and matching InMemory - We have to define how user/robot/session nodes are handled.
My suggestion is to always force user/robot and auto generate session if it is not supplied. I previously used `string(uuid4())[1:6]`
user/robot can default to something like defaultUser/defaultRobot
|
design
|
sentinel node behavior in cgdfg and matching inmemory we have to define how user robot session nodes are handled my suggestion is to always force user robot and auto generate session if it is not supplied i previously used string user robot can default to something like defaultuser defaultrobot
| 1
|
807,775
| 30,018,872,100
|
IssuesEvent
|
2023-06-26 21:05:48
|
spiffe/spire
|
https://api.github.com/repos/spiffe/spire
|
opened
|
WorkloadAttestor(k8s): Inconsistent attestation with 1-hash-to-many-tags
|
help wanted priority/backlog
|
Originally reported by @nweedon-u:
* **Version**: 1.3.x - 1.6.x (could also be earlier, untested in 1.7.x)
* **Platform**: Linux
* **Subsystem**: k8s workload attestor
I was investigating why a Kubernetes pod approved with k8s:pod-image:: was failing to attest on some Kubernetes workers and not others. Sample log from the app: `Failed to watch the Workload API: rpc error: code = PermissionDenied desc = no identity issued.`
It turns out that the Kubernetes workload attestor can incorrectly attest pods if two or more docker images are downloaded to a node which share the same container hash - this can be observed by turning on debug-level logging on the affected spire-agent.
**Reproduction steps:**
1. Entry added to spire-server with k8s:pod-image:/image:tag-a selector
2. Push image to registry with two tags (for example, tag-a and tag-b).
3. Start a pod with tag-a. It should start properly.
4. Start a pod with tag-b on the same node. It will not attest correctly as spire-agent will attest the container with tag-a.
**Workaround steps:**
This can be worked around by using pod-image with a SHA-256 hash, for example with a docker runtime:docker-pullable://@sha256:.
|
1.0
|
WorkloadAttestor(k8s): Inconsistent attestation with 1-hash-to-many-tags - Originally reported by @nweedon-u:
* **Version**: 1.3.x - 1.6.x (could also be earlier, untested in 1.7.x)
* **Platform**: Linux
* **Subsystem**: k8s workload attestor
I was investigating why a Kubernetes pod approved with k8s:pod-image:: was failing to attest on some Kubernetes workers and not others. Sample log from the app: `Failed to watch the Workload API: rpc error: code = PermissionDenied desc = no identity issued.`
It turns out that the Kubernetes workload attestor can incorrectly attest pods if two or more docker images are downloaded to a node which share the same container hash - this can be observed by turning on debug-level logging on the affected spire-agent.
**Reproduction steps:**
1. Entry added to spire-server with k8s:pod-image:/image:tag-a selector
2. Push image to registry with two tags (for example, tag-a and tag-b).
3. Start a pod with tag-a. It should start properly.
4. Start a pod with tag-b on the same node. It will not attest correctly as spire-agent will attest the container with tag-a.
**Workaround steps:**
This can be worked around by using pod-image with a SHA-256 hash, for example with a docker runtime:docker-pullable://@sha256:.
|
non_design
|
workloadattestor inconsistent attestation with hash to many tags originally reported by nweedon u version x x could also be earlier untested in x platform linux subsystem workload attestor i was investigating why a kubernetes pod approved with pod image was failing to attest on some kubernetes workers and not others sample log from the app failed to watch the workload api rpc error code permissiondenied desc no identity issued it turns out that the kubernetes workload attestor can incorrectly attest pods if two or more docker images are downloaded to a node which share the same container hash this can be observed by turning on debug level logging on the affected spire agent reproduction steps entry added to spire server with pod image image tag a selector push image to registry with two tags for example tag a and tag b start a pod with tag a it should start properly start a pod with tag b on the same node it will not attest correctly as spire agent will attest the container with tag a workaround steps this can be worked around by using pod image with a sha hash for example with a docker runtime docker pullable
| 0
|
74,578
| 9,792,922,314
|
IssuesEvent
|
2019-06-10 18:37:33
|
SergeyKurmenev/elama-exam
|
https://api.github.com/repos/SergeyKurmenev/elama-exam
|
opened
|
Дописать необходимые опции декораторам swagger в классе Categories
|
documentation swagger составная задача
|
Часть #249
Состоит из:
* Дописать необходимые опции декоратору `@swagger.operation` метода `get`
* Дописать необходимые опции декоратору `@swagger.operation` метода `post`
* Дописать необходимые опции декоратору `@swagger.operation` метода `put`
|
1.0
|
Дописать необходимые опции декораторам swagger в классе Categories - Часть #249
Состоит из:
* Дописать необходимые опции декоратору `@swagger.operation` метода `get`
* Дописать необходимые опции декоратору `@swagger.operation` метода `post`
* Дописать необходимые опции декоратору `@swagger.operation` метода `put`
|
non_design
|
дописать необходимые опции декораторам swagger в классе categories часть состоит из дописать необходимые опции декоратору swagger operation метода get дописать необходимые опции декоратору swagger operation метода post дописать необходимые опции декоратору swagger operation метода put
| 0
|
80,644
| 15,586,306,778
|
IssuesEvent
|
2021-03-18 01:38:40
|
hudsonnog/locadora
|
https://api.github.com/repos/hudsonnog/locadora
|
opened
|
CVE-2019-14900 (Medium) detected in hibernate-core-5.2.11.Final.jar
|
security vulnerability
|
## CVE-2019-14900 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hibernate-core-5.2.11.Final.jar</b></p></summary>
<p>The core O/RM functionality as provided by Hibernate</p>
<p>Library home page: <a href="http://hibernate.org">http://hibernate.org</a></p>
<p>Path to dependency file: locadora/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/org/hibernate/hibernate-core/5.2.11.Final/hibernate-core-5.2.11.Final.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-jpa-2.0.0.M5.jar (Root Library)
- :x: **hibernate-core-5.2.11.Final.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was found in Hibernate ORM in versions before 5.3.18, 5.4.18 and 5.5.0.Beta1. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SELECT or GROUP BY parts of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks.
<p>Publish Date: 2020-07-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14900>CVE-2019-14900</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14900">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14900</a></p>
<p>Release Date: 2020-07-06</p>
<p>Fix Resolution: org.hibernate:hibernate-core:5.4.18.Final</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-14900 (Medium) detected in hibernate-core-5.2.11.Final.jar - ## CVE-2019-14900 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hibernate-core-5.2.11.Final.jar</b></p></summary>
<p>The core O/RM functionality as provided by Hibernate</p>
<p>Library home page: <a href="http://hibernate.org">http://hibernate.org</a></p>
<p>Path to dependency file: locadora/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/org/hibernate/hibernate-core/5.2.11.Final/hibernate-core-5.2.11.Final.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-jpa-2.0.0.M5.jar (Root Library)
- :x: **hibernate-core-5.2.11.Final.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was found in Hibernate ORM in versions before 5.3.18, 5.4.18 and 5.5.0.Beta1. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SELECT or GROUP BY parts of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks.
<p>Publish Date: 2020-07-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14900>CVE-2019-14900</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14900">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14900</a></p>
<p>Release Date: 2020-07-06</p>
<p>Fix Resolution: org.hibernate:hibernate-core:5.4.18.Final</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_design
|
cve medium detected in hibernate core final jar cve medium severity vulnerability vulnerable library hibernate core final jar the core o rm functionality as provided by hibernate library home page a href path to dependency file locadora pom xml path to vulnerable library root repository org hibernate hibernate core final hibernate core final jar dependency hierarchy spring boot starter data jpa jar root library x hibernate core final jar vulnerable library vulnerability details a flaw was found in hibernate orm in versions before and a sql injection in the implementation of the jpa criteria api can permit unsanitized literals when a literal is used in the select or group by parts of the query this flaw could allow an attacker to access unauthorized information or possibly conduct further attacks publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org hibernate hibernate core final step up your open source security game with whitesource
| 0
|
156,763
| 24,625,625,758
|
IssuesEvent
|
2022-10-16 13:34:27
|
dotnet/efcore
|
https://api.github.com/repos/dotnet/efcore
|
closed
|
dotnet-ef 2.1.4 is targeting runtime 2.1.5
|
closed-by-design customer-reported
|
https://github.com/dotnet/cli/issues/10112
If the `dotnet-ef` does not intent to align with runtime version please close this issue.
Describe what is not working as expected.
### Steps to reproduce
Download dotnet-ef 2.1.4 nupkg, https://www.nuget.org/api/v2/package/dotnet-ef/2.1.4
find the file `dotnet-ef.2.1.4\tools\netcoreapp2.1\any\dotnet-ef.runtimeconfig.json`
it is targeting
```json
"framework": {
"name": "Microsoft.NETCore.App",
"version": "2.1.5"
}
```
### Further technical details
dotnet-ef 2.1.4
|
1.0
|
dotnet-ef 2.1.4 is targeting runtime 2.1.5 - https://github.com/dotnet/cli/issues/10112
If the `dotnet-ef` does not intent to align with runtime version please close this issue.
Describe what is not working as expected.
### Steps to reproduce
Download dotnet-ef 2.1.4 nupkg, https://www.nuget.org/api/v2/package/dotnet-ef/2.1.4
find the file `dotnet-ef.2.1.4\tools\netcoreapp2.1\any\dotnet-ef.runtimeconfig.json`
it is targeting
```json
"framework": {
"name": "Microsoft.NETCore.App",
"version": "2.1.5"
}
```
### Further technical details
dotnet-ef 2.1.4
|
design
|
dotnet ef is targeting runtime if the dotnet ef does not intent to align with runtime version please close this issue describe what is not working as expected steps to reproduce download dotnet ef nupkg find the file dotnet ef tools any dotnet ef runtimeconfig json it is targeting json framework name microsoft netcore app version further technical details dotnet ef
| 1
|
17,760
| 5,512,274,459
|
IssuesEvent
|
2017-03-17 08:54:24
|
akvo/akvo-flow-mobile
|
https://api.github.com/repos/akvo/akvo-flow-mobile
|
closed
|
Database refactor phase 1
|
Code Refactoring Ready for release Resolved issues
|
The [SurveyDbAdapter ](https://github.com/akvo/akvo-flow-mobile/blob/develop/app/src/main/java/org/akvo/flow/dao/SurveyDbAdapter.java) is quite big and is used everywhere in the app. I would like to see if we can separe it in and maybe move tables to another database to simplify the refactor.
Posible scenarios:
1) Move PREFERENCES table to another database
2) Move USER to another database
3) Have the PREFERENCES in [SharedPreferences](https://developer.android.com/reference/android/content/SharedPreferences.html) instead of database.
But after talking to @stellanl he explained to me that none of these scenarios are actually possible at the moment because users want to be able to provide all the settings in a single .sql file that would be placed in a folder and then executed in the app.
I would like to discuss what are the actual requirements, who uses the sqlite importing tool? Would it be possible to import a json or a configuration file?
@muloem @janagombitova would love your thoughts on this.
|
1.0
|
Database refactor phase 1 - The [SurveyDbAdapter ](https://github.com/akvo/akvo-flow-mobile/blob/develop/app/src/main/java/org/akvo/flow/dao/SurveyDbAdapter.java) is quite big and is used everywhere in the app. I would like to see if we can separe it in and maybe move tables to another database to simplify the refactor.
Posible scenarios:
1) Move PREFERENCES table to another database
2) Move USER to another database
3) Have the PREFERENCES in [SharedPreferences](https://developer.android.com/reference/android/content/SharedPreferences.html) instead of database.
But after talking to @stellanl he explained to me that none of these scenarios are actually possible at the moment because users want to be able to provide all the settings in a single .sql file that would be placed in a folder and then executed in the app.
I would like to discuss what are the actual requirements, who uses the sqlite importing tool? Would it be possible to import a json or a configuration file?
@muloem @janagombitova would love your thoughts on this.
|
non_design
|
database refactor phase the is quite big and is used everywhere in the app i would like to see if we can separe it in and maybe move tables to another database to simplify the refactor posible scenarios move preferences table to another database move user to another database have the preferences in instead of database but after talking to stellanl he explained to me that none of these scenarios are actually possible at the moment because users want to be able to provide all the settings in a single sql file that would be placed in a folder and then executed in the app i would like to discuss what are the actual requirements who uses the sqlite importing tool would it be possible to import a json or a configuration file muloem janagombitova would love your thoughts on this
| 0
|
161,055
| 25,280,132,874
|
IssuesEvent
|
2022-11-16 15:15:06
|
PastVu/pastvu
|
https://api.github.com/repos/PastVu/pastvu
|
closed
|
Arrows to ease a choise for direction / Стрелки для облегчения выбора направления
|
UX/Design Map good first issue Improvement
|
Кроме того, выбор направления более удобен рядом с полем ввода координат
|
1.0
|
Arrows to ease a choise for direction / Стрелки для облегчения выбора направления - 
Кроме того, выбор направления более удобен рядом с полем ввода координат
|
design
|
arrows to ease a choise for direction стрелки для облегчения выбора направления кроме того выбор направления более удобен рядом с полем ввода координат
| 1
|
17,366
| 10,688,312,286
|
IssuesEvent
|
2019-10-22 17:58:01
|
PATRIC3/patric3_website
|
https://api.github.com/repos/PATRIC3/patric3_website
|
closed
|
support for interleaved FASTQ paired-end reads in RNA-seq
|
Bug Service: RNA-seq
|
@mshukla1 found this limit in the current services.
|
1.0
|
support for interleaved FASTQ paired-end reads in RNA-seq - @mshukla1 found this limit in the current services.
|
non_design
|
support for interleaved fastq paired end reads in rna seq found this limit in the current services
| 0
|
63,887
| 14,656,795,949
|
IssuesEvent
|
2020-12-28 14:13:05
|
fu1771695yongxie/yapi
|
https://api.github.com/repos/fu1771695yongxie/yapi
|
opened
|
WS-2018-0113 (High) detected in macaddress-0.2.8.tgz
|
security vulnerability
|
## WS-2018-0113 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>macaddress-0.2.8.tgz</b></p></summary>
<p>Get the MAC addresses (hardware addresses) of the hosts network interfaces.</p>
<p>Library home page: <a href="https://registry.npmjs.org/macaddress/-/macaddress-0.2.8.tgz">https://registry.npmjs.org/macaddress/-/macaddress-0.2.8.tgz</a></p>
<p>Path to dependency file: yapi/package.json</p>
<p>Path to vulnerable library: yapi/node_modules/macaddress/package.json</p>
<p>
Dependency Hierarchy:
- css-loader-0.28.10.tgz (Root Library)
- cssnano-3.10.0.tgz
- postcss-filter-plugins-2.0.2.tgz
- uniqid-4.1.1.tgz
- :x: **macaddress-0.2.8.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/yapi/commit/426884f4927afe9500db9cacc24729657b10526b">426884f4927afe9500db9cacc24729657b10526b</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>
All versions of macaddress are vulnerable to command injection. For this vulnerability to be exploited an attacker needs to control the iface argument to the one method.
<p>Publish Date: 2018-05-16
<p>URL: <a href=https://hackerone.com/reports/319467>WS-2018-0113</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>10.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://nodesecurity.io/advisories/654">https://nodesecurity.io/advisories/654</a></p>
<p>Release Date: 2018-05-16</p>
<p>Fix Resolution: No fix is currently available for this vulnerability. It is our recommendation to not install or use this module until a fix is provided.</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
WS-2018-0113 (High) detected in macaddress-0.2.8.tgz - ## WS-2018-0113 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>macaddress-0.2.8.tgz</b></p></summary>
<p>Get the MAC addresses (hardware addresses) of the hosts network interfaces.</p>
<p>Library home page: <a href="https://registry.npmjs.org/macaddress/-/macaddress-0.2.8.tgz">https://registry.npmjs.org/macaddress/-/macaddress-0.2.8.tgz</a></p>
<p>Path to dependency file: yapi/package.json</p>
<p>Path to vulnerable library: yapi/node_modules/macaddress/package.json</p>
<p>
Dependency Hierarchy:
- css-loader-0.28.10.tgz (Root Library)
- cssnano-3.10.0.tgz
- postcss-filter-plugins-2.0.2.tgz
- uniqid-4.1.1.tgz
- :x: **macaddress-0.2.8.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/yapi/commit/426884f4927afe9500db9cacc24729657b10526b">426884f4927afe9500db9cacc24729657b10526b</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>
All versions of macaddress are vulnerable to command injection. For this vulnerability to be exploited an attacker needs to control the iface argument to the one method.
<p>Publish Date: 2018-05-16
<p>URL: <a href=https://hackerone.com/reports/319467>WS-2018-0113</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>10.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://nodesecurity.io/advisories/654">https://nodesecurity.io/advisories/654</a></p>
<p>Release Date: 2018-05-16</p>
<p>Fix Resolution: No fix is currently available for this vulnerability. It is our recommendation to not install or use this module until a fix is provided.</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_design
|
ws high detected in macaddress tgz ws high severity vulnerability vulnerable library macaddress tgz get the mac addresses hardware addresses of the hosts network interfaces library home page a href path to dependency file yapi package json path to vulnerable library yapi node modules macaddress package json dependency hierarchy css loader tgz root library cssnano tgz postcss filter plugins tgz uniqid tgz x macaddress tgz vulnerable library found in head commit a href found in base branch master vulnerability details all versions of macaddress are vulnerable to command injection for this vulnerability to be exploited an attacker needs to control the iface argument to the one method 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 no fix is currently available for this vulnerability it is our recommendation to not install or use this module until a fix is provided step up your open source security game with whitesource
| 0
|
56,350
| 6,975,641,787
|
IssuesEvent
|
2017-12-12 08:05:34
|
otavanopisto/muikku
|
https://api.github.com/repos/otavanopisto/muikku
|
closed
|
Relocate announcement's workspace name
|
ANNOUNCER enhancement in progress REDESIGN2017
|
Workspace name should be relocated to the same position in announcements as labels are in communicator messages.
|
1.0
|
Relocate announcement's workspace name - Workspace name should be relocated to the same position in announcements as labels are in communicator messages.
|
design
|
relocate announcement s workspace name workspace name should be relocated to the same position in announcements as labels are in communicator messages
| 1
|
170,132
| 26,906,543,278
|
IssuesEvent
|
2023-02-06 19:34:22
|
department-of-veterans-affairs/va.gov-team
|
https://api.github.com/repos/department-of-veterans-affairs/va.gov-team
|
closed
|
[EPIC] MHV to VA.gov:MR: Lab and Tests: Low-fi design & refinement
|
Epic design my-health my-health-MR-CORE MHV-to-VA.gov-PI9
|
### Low-fi designs for Labs and Tests
At this time, we plan to combine the following domains that are currently treated as distinct entities in the legacy application (subject to be adjusted based on usability testing results):
#### VA Lab Results
- Chemistry/Hematology
- Microbiology
#### VA Pathology Reports
- Surgical Pathology
- Cytology
- Electron Microscopy
#### VA Medical Images and Reports
- VA Radiology Reports
- VA Medical Images
#### VA Electrocardiogram (EKG) Reports
- EKG Reports - note - these are no longer updated in VistA, but historical records are available.
The [domain brief ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/digital-health-modernization/mhv-to-va.gov/medical-records/data-domains/labs-and-tests/labs-and-tests-brief.md)with further details and examples is on GitHub
|
1.0
|
[EPIC] MHV to VA.gov:MR: Lab and Tests: Low-fi design & refinement - ### Low-fi designs for Labs and Tests
At this time, we plan to combine the following domains that are currently treated as distinct entities in the legacy application (subject to be adjusted based on usability testing results):
#### VA Lab Results
- Chemistry/Hematology
- Microbiology
#### VA Pathology Reports
- Surgical Pathology
- Cytology
- Electron Microscopy
#### VA Medical Images and Reports
- VA Radiology Reports
- VA Medical Images
#### VA Electrocardiogram (EKG) Reports
- EKG Reports - note - these are no longer updated in VistA, but historical records are available.
The [domain brief ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/digital-health-modernization/mhv-to-va.gov/medical-records/data-domains/labs-and-tests/labs-and-tests-brief.md)with further details and examples is on GitHub
|
design
|
mhv to va gov mr lab and tests low fi design refinement low fi designs for labs and tests at this time we plan to combine the following domains that are currently treated as distinct entities in the legacy application subject to be adjusted based on usability testing results va lab results chemistry hematology microbiology va pathology reports surgical pathology cytology electron microscopy va medical images and reports va radiology reports va medical images va electrocardiogram ekg reports ekg reports note these are no longer updated in vista but historical records are available the further details and examples is on github
| 1
|
143,275
| 21,993,445,502
|
IssuesEvent
|
2022-05-26 02:06:11
|
RecordReplay/devtools
|
https://api.github.com/repos/RecordReplay/devtools
|
closed
|
zypsyfy our pause line
|
design-complete
|
Not sure if these colors are perfect, but the old colors are still the firefox blue as opposed to our zypsy blue... I also looked at our fuschia, but it was too close to an error pause line...
### old
<img width="562" alt="Screen Shot 2022-05-19 at 10 01 51 PM" src="https://user-images.githubusercontent.com/254562/169454017-8803c00b-bfaf-4b94-9e3a-ac3d2317c53d.png">
### new
<img width="576" alt="Screen Shot 2022-05-19 at 10 01 41 PM" src="https://user-images.githubusercontent.com/254562/169453988-2ec8c67b-b876-43b6-8752-df318ccfacfe.png">
|
1.0
|
zypsyfy our pause line - Not sure if these colors are perfect, but the old colors are still the firefox blue as opposed to our zypsy blue... I also looked at our fuschia, but it was too close to an error pause line...
### old
<img width="562" alt="Screen Shot 2022-05-19 at 10 01 51 PM" src="https://user-images.githubusercontent.com/254562/169454017-8803c00b-bfaf-4b94-9e3a-ac3d2317c53d.png">
### new
<img width="576" alt="Screen Shot 2022-05-19 at 10 01 41 PM" src="https://user-images.githubusercontent.com/254562/169453988-2ec8c67b-b876-43b6-8752-df318ccfacfe.png">
|
design
|
zypsyfy our pause line not sure if these colors are perfect but the old colors are still the firefox blue as opposed to our zypsy blue i also looked at our fuschia but it was too close to an error pause line old img width alt screen shot at pm src new img width alt screen shot at pm src
| 1
|
297,754
| 22,391,035,571
|
IssuesEvent
|
2022-06-17 07:43:08
|
ca-knowledgebase/ca-knowledgebase.github.io
|
https://api.github.com/repos/ca-knowledgebase/ca-knowledgebase.github.io
|
closed
|
Edit Tutorial Template
|
documentation tutorial
|
For contributing on also make sure there is consistency across tutorials, some boiler plate that covers
- What you are expected to know
- next / prep
- rough structure / narrative
|
1.0
|
Edit Tutorial Template - For contributing on also make sure there is consistency across tutorials, some boiler plate that covers
- What you are expected to know
- next / prep
- rough structure / narrative
|
non_design
|
edit tutorial template for contributing on also make sure there is consistency across tutorials some boiler plate that covers what you are expected to know next prep rough structure narrative
| 0
|
12,815
| 3,292,267,304
|
IssuesEvent
|
2015-10-30 13:56:39
|
Allsteel/hni-textiles-webcomponents
|
https://api.github.com/repos/Allsteel/hni-textiles-webcomponents
|
closed
|
Colorway Misnamed - Pivot > Chocolate Mint
|
data issue ready to ReTest
|
The colorway for Pivot > Chocolate Mint is named incorrectly. It is currently named Pivot > Chocolate Milk. Please rename and point to correct image asset.
|
1.0
|
Colorway Misnamed - Pivot > Chocolate Mint - The colorway for Pivot > Chocolate Mint is named incorrectly. It is currently named Pivot > Chocolate Milk. Please rename and point to correct image asset.
|
non_design
|
colorway misnamed pivot chocolate mint the colorway for pivot chocolate mint is named incorrectly it is currently named pivot chocolate milk please rename and point to correct image asset
| 0
|
162,489
| 20,194,675,904
|
IssuesEvent
|
2022-02-11 09:34:02
|
TIBCOSoftware/TCSTK-Angular
|
https://api.github.com/repos/TIBCOSoftware/TCSTK-Angular
|
closed
|
WS-2022-0008 (Medium) detected in node-forge-0.10.0.tgz
|
security vulnerability
|
## WS-2022-0008 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-forge-0.10.0.tgz</b></p></summary>
<p>JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-forge/-/node-forge-0.10.0.tgz">https://registry.npmjs.org/node-forge/-/node-forge-0.10.0.tgz</a></p>
<p>
Dependency Hierarchy:
- build-angular-12.2.16.tgz (Root Library)
- webpack-dev-server-3.11.3.tgz
- selfsigned-1.10.14.tgz
- :x: **node-forge-0.10.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The forge.debug API had a potential prototype pollution issue if called with untrusted input. The API was only used for internal debug purposes in a safe way and never documented or advertised. It is suspected that uses of this API, if any exist, would likely not have used untrusted inputs in a vulnerable way.
<p>Publish Date: 2022-01-08
<p>URL: <a href=https://github.com/digitalbazaar/forge/commit/51228083550dde97701ac8e06c629a5184117562>WS-2022-0008</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.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-5rrq-pxf6-6jx5">https://github.com/advisories/GHSA-5rrq-pxf6-6jx5</a></p>
<p>Release Date: 2022-01-08</p>
<p>Fix Resolution (node-forge): 1.2.1</p>
<p>Direct dependency fix Resolution (@angular-devkit/build-angular): 13.2.0-next.2</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"@angular-devkit/build-angular","packageVersion":"12.2.16","packageFilePaths":[null],"isTransitiveDependency":false,"dependencyTree":"@angular-devkit/build-angular:12.2.16","isMinimumFixVersionAvailable":true,"minimumFixVersion":"13.2.0-next.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2022-0008","vulnerabilityDetails":"The forge.debug API had a potential prototype pollution issue if called with untrusted input. The API was only used for internal debug purposes in a safe way and never documented or advertised. It is suspected that uses of this API, if any exist, would likely not have used untrusted inputs in a vulnerable way.","vulnerabilityUrl":"https://github.com/digitalbazaar/forge/commit/51228083550dde97701ac8e06c629a5184117562","cvss3Severity":"medium","cvss3Score":"6.6","cvss3Metrics":{"A":"High","AC":"High","PR":"High","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
|
True
|
WS-2022-0008 (Medium) detected in node-forge-0.10.0.tgz - ## WS-2022-0008 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-forge-0.10.0.tgz</b></p></summary>
<p>JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-forge/-/node-forge-0.10.0.tgz">https://registry.npmjs.org/node-forge/-/node-forge-0.10.0.tgz</a></p>
<p>
Dependency Hierarchy:
- build-angular-12.2.16.tgz (Root Library)
- webpack-dev-server-3.11.3.tgz
- selfsigned-1.10.14.tgz
- :x: **node-forge-0.10.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The forge.debug API had a potential prototype pollution issue if called with untrusted input. The API was only used for internal debug purposes in a safe way and never documented or advertised. It is suspected that uses of this API, if any exist, would likely not have used untrusted inputs in a vulnerable way.
<p>Publish Date: 2022-01-08
<p>URL: <a href=https://github.com/digitalbazaar/forge/commit/51228083550dde97701ac8e06c629a5184117562>WS-2022-0008</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.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-5rrq-pxf6-6jx5">https://github.com/advisories/GHSA-5rrq-pxf6-6jx5</a></p>
<p>Release Date: 2022-01-08</p>
<p>Fix Resolution (node-forge): 1.2.1</p>
<p>Direct dependency fix Resolution (@angular-devkit/build-angular): 13.2.0-next.2</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"@angular-devkit/build-angular","packageVersion":"12.2.16","packageFilePaths":[null],"isTransitiveDependency":false,"dependencyTree":"@angular-devkit/build-angular:12.2.16","isMinimumFixVersionAvailable":true,"minimumFixVersion":"13.2.0-next.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2022-0008","vulnerabilityDetails":"The forge.debug API had a potential prototype pollution issue if called with untrusted input. The API was only used for internal debug purposes in a safe way and never documented or advertised. It is suspected that uses of this API, if any exist, would likely not have used untrusted inputs in a vulnerable way.","vulnerabilityUrl":"https://github.com/digitalbazaar/forge/commit/51228083550dde97701ac8e06c629a5184117562","cvss3Severity":"medium","cvss3Score":"6.6","cvss3Metrics":{"A":"High","AC":"High","PR":"High","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
|
non_design
|
ws medium detected in node forge tgz ws medium severity vulnerability vulnerable library node forge tgz javascript implementations of network transports cryptography ciphers pki message digests and various utilities library home page a href dependency hierarchy build angular tgz root library webpack dev server tgz selfsigned tgz x node forge tgz vulnerable library found in base branch master vulnerability details the forge debug api had a potential prototype pollution issue if called with untrusted input the api was only used for internal debug purposes in a safe way and never documented or advertised it is suspected that uses of this api if any exist would likely not have used untrusted inputs in a vulnerable way publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required high user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution node forge direct dependency fix resolution angular devkit build angular next check this box to open an automated fix pr isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree angular devkit build angular isminimumfixversionavailable true minimumfixversion next isbinary false basebranches vulnerabilityidentifier ws vulnerabilitydetails the forge debug api had a potential prototype pollution issue if called with untrusted input the api was only used for internal debug purposes in a safe way and never documented or advertised it is suspected that uses of this api if any exist would likely not have used untrusted inputs in a vulnerable way vulnerabilityurl
| 0
|
9,454
| 3,285,930,736
|
IssuesEvent
|
2015-10-28 22:53:01
|
hadley/dplyr
|
https://api.github.com/repos/hadley/dplyr
|
closed
|
Describe tbl_df behaviour in data frames vignette
|
documentation
|
* Default printing, and how to control it
* Why `[` behaves differently
|
1.0
|
Describe tbl_df behaviour in data frames vignette - * Default printing, and how to control it
* Why `[` behaves differently
|
non_design
|
describe tbl df behaviour in data frames vignette default printing and how to control it why behaves differently
| 0
|
45,614
| 9,792,700,381
|
IssuesEvent
|
2019-06-10 18:04:21
|
SAP/fundamental-ngx
|
https://api.github.com/repos/SAP/fundamental-ngx
|
opened
|
Simplify actionbar API
|
code refactoring enhancement
|
#### Is this a bug, enhancement, or feature request?
Enhancement
#### Briefly describe your proposal.
The API for actionbar is overly complicated with a lot of components. We could instead have directives which apply classes with hostbinding.
|
1.0
|
Simplify actionbar API - #### Is this a bug, enhancement, or feature request?
Enhancement
#### Briefly describe your proposal.
The API for actionbar is overly complicated with a lot of components. We could instead have directives which apply classes with hostbinding.
|
non_design
|
simplify actionbar api is this a bug enhancement or feature request enhancement briefly describe your proposal the api for actionbar is overly complicated with a lot of components we could instead have directives which apply classes with hostbinding
| 0
|
2,586
| 3,777,219,612
|
IssuesEvent
|
2016-03-17 19:15:00
|
twosigma/beaker-notebook
|
https://api.github.com/repos/twosigma/beaker-notebook
|
opened
|
sometimes all tests fail
|
Bug Infrastructure
|
eg http://ec2-54-175-192-115.compute-1.amazonaws.com:8080/job/Beaker%20PR/624/consoleFull
```
[firefox #1-1] beaker landing load
[firefox #1-1] ✗ can load
[firefox #1-1] - Failed: Angular could not be found on the page http://localhost:8801/ : retries looking for angular exceeded
```
|
1.0
|
sometimes all tests fail - eg http://ec2-54-175-192-115.compute-1.amazonaws.com:8080/job/Beaker%20PR/624/consoleFull
```
[firefox #1-1] beaker landing load
[firefox #1-1] ✗ can load
[firefox #1-1] - Failed: Angular could not be found on the page http://localhost:8801/ : retries looking for angular exceeded
```
|
non_design
|
sometimes all tests fail eg beaker landing load ✗ can load failed angular could not be found on the page retries looking for angular exceeded
| 0
|
142,720
| 21,875,452,797
|
IssuesEvent
|
2022-05-19 09:43:08
|
digirati-co-uk/delft-static-site-generator
|
https://api.github.com/repos/digirati-co-uk/delft-static-site-generator
|
opened
|
Improvement of collection overview
|
enhancement design
|
The current collection page only shows two objects side by side.
Proposed improvement:
- More efficient layout that can be adjusted
|
1.0
|
Improvement of collection overview - The current collection page only shows two objects side by side.
Proposed improvement:
- More efficient layout that can be adjusted
|
design
|
improvement of collection overview the current collection page only shows two objects side by side proposed improvement more efficient layout that can be adjusted
| 1
|
448,927
| 31,818,477,410
|
IssuesEvent
|
2023-09-13 22:54:23
|
TechVisionn/tech-parent
|
https://api.github.com/repos/TechVisionn/tech-parent
|
closed
|
Reunião de Administração do projeto - 13/09/2023
|
documentation
|
Data Estimada: 13/09/2023
Descrição: Ata de reunião da Equipe TechVision
- Master: Carlos Fernando.
- P.O. : Bryan Ribeiro.
Verificação do andamento dos processos e tarefas da equipe, dificuldades, avaliação até o presente momento da Sprint 1.
- Nesta Reunião, foi confirmada a subdivisão da equipe em 3 frentes:
- Front End - Camila, Orlando;
- Back End - José Maria, Zaion;
- Banco de Dados/Migrações - Andrew, Gabriel, Kauã.
|
1.0
|
Reunião de Administração do projeto - 13/09/2023 - Data Estimada: 13/09/2023
Descrição: Ata de reunião da Equipe TechVision
- Master: Carlos Fernando.
- P.O. : Bryan Ribeiro.
Verificação do andamento dos processos e tarefas da equipe, dificuldades, avaliação até o presente momento da Sprint 1.
- Nesta Reunião, foi confirmada a subdivisão da equipe em 3 frentes:
- Front End - Camila, Orlando;
- Back End - José Maria, Zaion;
- Banco de Dados/Migrações - Andrew, Gabriel, Kauã.
|
non_design
|
reunião de administração do projeto data estimada descrição ata de reunião da equipe techvision master carlos fernando p o bryan ribeiro verificação do andamento dos processos e tarefas da equipe dificuldades avaliação até o presente momento da sprint nesta reunião foi confirmada a subdivisão da equipe em frentes front end camila orlando back end josé maria zaion banco de dados migrações andrew gabriel kauã
| 0
|
169,770
| 26,858,614,353
|
IssuesEvent
|
2023-02-03 16:28:22
|
sboxgame/issues
|
https://api.github.com/repos/sboxgame/issues
|
opened
|
Impossible to type client components
|
api design
|
### What it is?
ever since Client became IClient it's impossible to create client EntityComponent
### What should it be?
Honestly, no idea. I don't know why Client was replaced by IClient in the first place.
|
1.0
|
Impossible to type client components - ### What it is?
ever since Client became IClient it's impossible to create client EntityComponent
### What should it be?
Honestly, no idea. I don't know why Client was replaced by IClient in the first place.
|
design
|
impossible to type client components what it is ever since client became iclient it s impossible to create client entitycomponent what should it be honestly no idea i don t know why client was replaced by iclient in the first place
| 1
|
65,160
| 7,859,053,379
|
IssuesEvent
|
2018-06-21 15:29:40
|
revelrylabs/harmonium
|
https://api.github.com/repos/revelrylabs/harmonium
|
closed
|
Add component for breadcrumbs
|
Draft designy in review
|
- Breadcrumbs are listed out as a list with a class on the `<ul>`: `rev-Breadcrumbs`
- All List items get the class `rev-Breadcrumbs-item`
- All list items will have a link where the path can be added EXCEPT for the active/selected page
- Active/Selected page item will not have a link inside and instead will have a span with the class `rev-Breadcrumbs-item--selected`
- Disabled breadcrumbs get a class `rev-Breadcrumbs-item--disabled`
Style Vars:
- [x] Var for active/selected page color
- [x] Var for disabled page color
- [x] Var for pages that are links
- [x] Var for separator color
- [x] Var for breadcrumbs margin
- [x] Var for breadcrumbs font size
- [x] Var for breadcrumb item margin
- [x] Var for breadcrumb separator (Content: ' / ';)
------------
- [ ] Add description/ help text on the examples page
|
1.0
|
Add component for breadcrumbs - - Breadcrumbs are listed out as a list with a class on the `<ul>`: `rev-Breadcrumbs`
- All List items get the class `rev-Breadcrumbs-item`
- All list items will have a link where the path can be added EXCEPT for the active/selected page
- Active/Selected page item will not have a link inside and instead will have a span with the class `rev-Breadcrumbs-item--selected`
- Disabled breadcrumbs get a class `rev-Breadcrumbs-item--disabled`
Style Vars:
- [x] Var for active/selected page color
- [x] Var for disabled page color
- [x] Var for pages that are links
- [x] Var for separator color
- [x] Var for breadcrumbs margin
- [x] Var for breadcrumbs font size
- [x] Var for breadcrumb item margin
- [x] Var for breadcrumb separator (Content: ' / ';)
------------
- [ ] Add description/ help text on the examples page
|
design
|
add component for breadcrumbs breadcrumbs are listed out as a list with a class on the rev breadcrumbs all list items get the class rev breadcrumbs item all list items will have a link where the path can be added except for the active selected page active selected page item will not have a link inside and instead will have a span with the class rev breadcrumbs item selected disabled breadcrumbs get a class rev breadcrumbs item disabled style vars var for active selected page color var for disabled page color var for pages that are links var for separator color var for breadcrumbs margin var for breadcrumbs font size var for breadcrumb item margin var for breadcrumb separator content add description help text on the examples page
| 1
|
156,258
| 24,589,567,145
|
IssuesEvent
|
2022-10-13 23:58:03
|
mapbox/mapbox-navigation-ios
|
https://api.github.com/repos/mapbox/mapbox-navigation-ios
|
closed
|
Route preview view controller
|
topic: design feature UI drop-in jira-sync-complete
|
This library should vend a view controller that displays a preview of a route (and potentially any alternative routes). There would be controls for beginning the route (pushing NavigationViewController onto the stack), as well as an option to view a static list of steps along the route.
RoutePreviewViewController would serve as an additional, optional entry point to the existing NavigationViewController. The user normally expects to be able to see the route visualized or summarized somehow before committing to it by beginning turn-by-turn navigation. In a navigation-focused application, the main view controller may already contain a NavigationMapView that can display the route, so it RoutePreviewViewController may not be strictly necessary. However, in a non-navigation-focused application, such a UI may not already be present, so RoutePreviewViewController will make it easier for developers to complete that part of the user experience.
/cc @mapbox/navigation-ios
|
1.0
|
Route preview view controller - This library should vend a view controller that displays a preview of a route (and potentially any alternative routes). There would be controls for beginning the route (pushing NavigationViewController onto the stack), as well as an option to view a static list of steps along the route.
RoutePreviewViewController would serve as an additional, optional entry point to the existing NavigationViewController. The user normally expects to be able to see the route visualized or summarized somehow before committing to it by beginning turn-by-turn navigation. In a navigation-focused application, the main view controller may already contain a NavigationMapView that can display the route, so it RoutePreviewViewController may not be strictly necessary. However, in a non-navigation-focused application, such a UI may not already be present, so RoutePreviewViewController will make it easier for developers to complete that part of the user experience.
/cc @mapbox/navigation-ios
|
design
|
route preview view controller this library should vend a view controller that displays a preview of a route and potentially any alternative routes there would be controls for beginning the route pushing navigationviewcontroller onto the stack as well as an option to view a static list of steps along the route routepreviewviewcontroller would serve as an additional optional entry point to the existing navigationviewcontroller the user normally expects to be able to see the route visualized or summarized somehow before committing to it by beginning turn by turn navigation in a navigation focused application the main view controller may already contain a navigationmapview that can display the route so it routepreviewviewcontroller may not be strictly necessary however in a non navigation focused application such a ui may not already be present so routepreviewviewcontroller will make it easier for developers to complete that part of the user experience cc mapbox navigation ios
| 1
|
38,581
| 4,972,041,931
|
IssuesEvent
|
2016-12-05 20:24:21
|
elegantthemes/Divi-Beta
|
https://api.github.com/repos/elegantthemes/Divi-Beta
|
closed
|
WP 4.7 :: FB :: Inconsistent User-specific localisation on Visual Builder
|
BUG DESIGN SIGNOFF QUALITY ASSURED READY FOR REVIEW
|
### Problem:
WordPress 3.7 introduces user specific language setting (site can be set to a particular language and user has different language setting that the site's language. See this post for What's coming on WP 3.7: http://www.wpbeginner.com/news/whats-coming-in-wordpress-4-7-features-and-screenshots/). When site and user has different language setting, the output on visual builder looks inconsistent. This is what happens when the following setting is used:
- Site language: Hebrew
- User language: French
Expected output: Visual builder, admin bar, etc uses French.
Current output:
- Modal's field label are in French
- Admin bar and the rest of the page are still in Hebrew
- BB properly uses French
### Steps To Reproduce:
1. Update WordPress to WP 3.7 RC 1
2. Set Builder post on VB Hebrew
3. Set current user's language to French
4. Open any Divi Builder post on VB
### Additional Information:
**Device**:
Macbook Pro Retina 15"
**Operating System**:
OSX El Capitan
**Browser**:
Latest Chrome
**Screen Resolution**:
2560x1440 + 1440 x 900 (dual monitor)
|
1.0
|
WP 4.7 :: FB :: Inconsistent User-specific localisation on Visual Builder - ### Problem:
WordPress 3.7 introduces user specific language setting (site can be set to a particular language and user has different language setting that the site's language. See this post for What's coming on WP 3.7: http://www.wpbeginner.com/news/whats-coming-in-wordpress-4-7-features-and-screenshots/). When site and user has different language setting, the output on visual builder looks inconsistent. This is what happens when the following setting is used:
- Site language: Hebrew
- User language: French
Expected output: Visual builder, admin bar, etc uses French.
Current output:
- Modal's field label are in French
- Admin bar and the rest of the page are still in Hebrew
- BB properly uses French
### Steps To Reproduce:
1. Update WordPress to WP 3.7 RC 1
2. Set Builder post on VB Hebrew
3. Set current user's language to French
4. Open any Divi Builder post on VB
### Additional Information:
**Device**:
Macbook Pro Retina 15"
**Operating System**:
OSX El Capitan
**Browser**:
Latest Chrome
**Screen Resolution**:
2560x1440 + 1440 x 900 (dual monitor)
|
design
|
wp fb inconsistent user specific localisation on visual builder problem wordpress introduces user specific language setting site can be set to a particular language and user has different language setting that the site s language see this post for what s coming on wp when site and user has different language setting the output on visual builder looks inconsistent this is what happens when the following setting is used site language hebrew user language french expected output visual builder admin bar etc uses french current output modal s field label are in french admin bar and the rest of the page are still in hebrew bb properly uses french steps to reproduce update wordpress to wp rc set builder post on vb hebrew set current user s language to french open any divi builder post on vb additional information device macbook pro retina operating system osx el capitan browser latest chrome screen resolution x dual monitor
| 1
|
22,911
| 3,800,432,245
|
IssuesEvent
|
2016-03-23 19:03:59
|
Forcir/design
|
https://api.github.com/repos/Forcir/design
|
closed
|
DOM Body Contrast
|
design: planning enhancement: discussion status: not started
|
Add a body-contrast option (class).
```SCSS
.body {
&.contrast {
background-color: #eceeef;
}
}
```
Would be useful for easily creating off-white pages
|
1.0
|
DOM Body Contrast - Add a body-contrast option (class).
```SCSS
.body {
&.contrast {
background-color: #eceeef;
}
}
```
Would be useful for easily creating off-white pages
|
design
|
dom body contrast add a body contrast option class scss body contrast background color eceeef would be useful for easily creating off white pages
| 1
|
272,889
| 29,795,118,235
|
IssuesEvent
|
2023-06-16 01:12:29
|
billmcchesney1/pacbot
|
https://api.github.com/repos/billmcchesney1/pacbot
|
closed
|
CVE-2021-25122 (High) detected in tomcat-embed-core-8.5.32.jar - autoclosed
|
Mend: dependency security vulnerability
|
## CVE-2021-25122 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-8.5.32.jar</b></p></summary>
<p>Core Tomcat implementation</p>
<p>Library home page: <a href="http://tomcat.apache.org/">http://tomcat.apache.org/</a></p>
<p>Path to dependency file: /api/pacman-api-admin/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.0.4.RELEASE.jar (Root Library)
- spring-boot-starter-tomcat-2.0.4.RELEASE.jar
- :x: **tomcat-embed-core-8.5.32.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/billmcchesney1/pacbot/commit/acf9a0620c1a37cee4f2896d71e1c3731c5c7b06">acf9a0620c1a37cee4f2896d71e1c3731c5c7b06</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>
When responding to new h2c connection requests, Apache Tomcat versions 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41 and 8.5.0 to 8.5.61 could duplicate request headers and a limited amount of request body from one request to another meaning user A and user B could both see the results of user A's request.
<p>Publish Date: 2021-03-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-25122>CVE-2021-25122</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://lists.apache.org/thread.html/r7b95bc248603360501f18c8eb03bb6001ec0ee3296205b34b07105b7%40%3Cannounce.tomcat.apache.org%3E">https://lists.apache.org/thread.html/r7b95bc248603360501f18c8eb03bb6001ec0ee3296205b34b07105b7%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2021-03-01</p>
<p>Fix Resolution: org.apache.tomcat.embed:tomcat-embed-core:8.5.62,9.0.42,10.0.2;org.apache.tomcat:tomcat-coyote:8.5.62,9.0.42,10.0.2</p>
</p>
</details>
<p></p>
|
True
|
CVE-2021-25122 (High) detected in tomcat-embed-core-8.5.32.jar - autoclosed - ## CVE-2021-25122 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-8.5.32.jar</b></p></summary>
<p>Core Tomcat implementation</p>
<p>Library home page: <a href="http://tomcat.apache.org/">http://tomcat.apache.org/</a></p>
<p>Path to dependency file: /api/pacman-api-admin/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.0.4.RELEASE.jar (Root Library)
- spring-boot-starter-tomcat-2.0.4.RELEASE.jar
- :x: **tomcat-embed-core-8.5.32.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/billmcchesney1/pacbot/commit/acf9a0620c1a37cee4f2896d71e1c3731c5c7b06">acf9a0620c1a37cee4f2896d71e1c3731c5c7b06</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>
When responding to new h2c connection requests, Apache Tomcat versions 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41 and 8.5.0 to 8.5.61 could duplicate request headers and a limited amount of request body from one request to another meaning user A and user B could both see the results of user A's request.
<p>Publish Date: 2021-03-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-25122>CVE-2021-25122</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://lists.apache.org/thread.html/r7b95bc248603360501f18c8eb03bb6001ec0ee3296205b34b07105b7%40%3Cannounce.tomcat.apache.org%3E">https://lists.apache.org/thread.html/r7b95bc248603360501f18c8eb03bb6001ec0ee3296205b34b07105b7%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2021-03-01</p>
<p>Fix Resolution: org.apache.tomcat.embed:tomcat-embed-core:8.5.62,9.0.42,10.0.2;org.apache.tomcat:tomcat-coyote:8.5.62,9.0.42,10.0.2</p>
</p>
</details>
<p></p>
|
non_design
|
cve high detected in tomcat embed core jar autoclosed cve high severity vulnerability vulnerable library tomcat embed core jar core tomcat implementation library home page a href path to dependency file api pacman api admin pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring boot starter web release jar root library spring boot starter tomcat release jar x tomcat embed core jar vulnerable library found in head commit a href found in base branch master vulnerability details when responding to new connection requests apache tomcat versions to to and to could duplicate request headers and a limited amount of request body from one request to another meaning user a and user b could both see the results of user a s request publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache tomcat embed tomcat embed core org apache tomcat tomcat coyote
| 0
|
157,833
| 24,733,325,456
|
IssuesEvent
|
2022-10-20 19:35:29
|
pulumi/pulumi
|
https://api.github.com/repos/pulumi/pulumi
|
closed
|
403 HTTP error fetching AWS resource plugin even though it's installed
|
kind/bug impact/usability resolution/by-design area/import
|
### What happened?
I started a new Pulumi project in Python today using `pulumi new aws-python` to test the `pulumi import` command on some AWS resources.
Creating the new Pulumi project worked, however when I run `pulumi import AWS::SNS::Topic x-dev-drip-welcome-sns xdevdripwelcomesnsE0E1B83B` I get the error:
```
Previewing import (dev)
View Live: https://app.pulumi.com/iulspop/another-one/dev/previews/cea9f31c-9dbf-412d-b12a-59de485a3121
Type Name Plan Info
+ pulumi:pulumi:Stack another-one-dev create 1 error
Diagnostics:
pulumi:pulumi:Stack (another-one-dev):
error: preview failed: failed to validate provider config: Could not automatically download and install resource plugin 'pulumi-resource-AWS'at version v5.18.0, install the plugin using `pulumi plugin install resource AWS v5.18.0`.
Underlying error: error downloading plugin AWS to file: failed to download plugin: AWS-5.18.0: 403 HTTP error fetching plugin from https://get.pulumi.com/releases/plugins/pulumi-resource-AWS-v5.18.0-darwin-arm64.tar.gz
```
However if I run `pulumi plugin install resource AWS v5.18.0` it seems to run successfully and the AWS plugin is listed as installed when I run `pulumi about`.
### Steps to reproduce
I don't know if this bug might be reproduced. Have a M1 MacBook Pro, install Pulumi using the official homebrew tap, start a new project usign`pulumi new`, attempt to import an AWS ressource.
### Expected Behavior
I expect the `pulumi import` command to run succesfully.
### Actual Behavior
The `pulumi import` command fails with this error:
```
Diagnostics:
pulumi:pulumi:Stack (another-one-dev):
error: preview failed: failed to validate provider config: Could not automatically download and install resource plugin 'pulumi-resource-AWS'at version v5.18.0, install the plugin using `pulumi plugin install resource AWS v5.18.0`.
Underlying error: error downloading plugin AWS to file: failed to download plugin: AWS-5.18.0: 403 HTTP error fetching plugin from https://get.pulumi.com/releases/plugins/pulumi-resource-AWS-v5.18.0-darwin-arm64.tar.gz
```
### Output of `pulumi about`
```
CLI
Version 3.43.1
Go Version go1.19.2
Go Compiler gc
Plugins
NAME VERSION
aws 5.18.0
python unknown
Host
OS darwin
Version 12.6
Arch arm64
This project is written in python: executable='/Library/Frameworks/Python.framework/Versions/3.10/bin/python3' version='3.10.8
'
Backend
Name pulumi.com
URL https://app.pulumi.com/iulspop
User iulspop
Organizations iulspop
Dependencies:
NAME VERSION
pip 22.3.0
pulumi-aws 5.18.0
setuptools 65.5.0
wheel 0.37.1
```
### Additional context
I found the troubleshooting [403 error fetching plugin](https://www.pulumi.com/docs/support/troubleshooting/#403-error-fetching-plugin) page and I followed the steps, but they didn't help. In this case, I just started the project so the provider version is already at the latest. In fact, the plugin is listed as installed at the correct version when I run `pulumi about` and version `5.18.0` of the `aws` plugin supports arm64. So I think this must be some other sort of problem.
I tried uninstalling Pulumi, deleting my projects, deleting the `.pulumi` folder and starting again. This time I ran `pulumi up` after I started the template project and it worked in both Python and Typescript. However when I ran `pulumi import` again I got the same error as above.
### Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
|
1.0
|
403 HTTP error fetching AWS resource plugin even though it's installed - ### What happened?
I started a new Pulumi project in Python today using `pulumi new aws-python` to test the `pulumi import` command on some AWS resources.
Creating the new Pulumi project worked, however when I run `pulumi import AWS::SNS::Topic x-dev-drip-welcome-sns xdevdripwelcomesnsE0E1B83B` I get the error:
```
Previewing import (dev)
View Live: https://app.pulumi.com/iulspop/another-one/dev/previews/cea9f31c-9dbf-412d-b12a-59de485a3121
Type Name Plan Info
+ pulumi:pulumi:Stack another-one-dev create 1 error
Diagnostics:
pulumi:pulumi:Stack (another-one-dev):
error: preview failed: failed to validate provider config: Could not automatically download and install resource plugin 'pulumi-resource-AWS'at version v5.18.0, install the plugin using `pulumi plugin install resource AWS v5.18.0`.
Underlying error: error downloading plugin AWS to file: failed to download plugin: AWS-5.18.0: 403 HTTP error fetching plugin from https://get.pulumi.com/releases/plugins/pulumi-resource-AWS-v5.18.0-darwin-arm64.tar.gz
```
However if I run `pulumi plugin install resource AWS v5.18.0` it seems to run successfully and the AWS plugin is listed as installed when I run `pulumi about`.
### Steps to reproduce
I don't know if this bug might be reproduced. Have a M1 MacBook Pro, install Pulumi using the official homebrew tap, start a new project usign`pulumi new`, attempt to import an AWS ressource.
### Expected Behavior
I expect the `pulumi import` command to run succesfully.
### Actual Behavior
The `pulumi import` command fails with this error:
```
Diagnostics:
pulumi:pulumi:Stack (another-one-dev):
error: preview failed: failed to validate provider config: Could not automatically download and install resource plugin 'pulumi-resource-AWS'at version v5.18.0, install the plugin using `pulumi plugin install resource AWS v5.18.0`.
Underlying error: error downloading plugin AWS to file: failed to download plugin: AWS-5.18.0: 403 HTTP error fetching plugin from https://get.pulumi.com/releases/plugins/pulumi-resource-AWS-v5.18.0-darwin-arm64.tar.gz
```
### Output of `pulumi about`
```
CLI
Version 3.43.1
Go Version go1.19.2
Go Compiler gc
Plugins
NAME VERSION
aws 5.18.0
python unknown
Host
OS darwin
Version 12.6
Arch arm64
This project is written in python: executable='/Library/Frameworks/Python.framework/Versions/3.10/bin/python3' version='3.10.8
'
Backend
Name pulumi.com
URL https://app.pulumi.com/iulspop
User iulspop
Organizations iulspop
Dependencies:
NAME VERSION
pip 22.3.0
pulumi-aws 5.18.0
setuptools 65.5.0
wheel 0.37.1
```
### Additional context
I found the troubleshooting [403 error fetching plugin](https://www.pulumi.com/docs/support/troubleshooting/#403-error-fetching-plugin) page and I followed the steps, but they didn't help. In this case, I just started the project so the provider version is already at the latest. In fact, the plugin is listed as installed at the correct version when I run `pulumi about` and version `5.18.0` of the `aws` plugin supports arm64. So I think this must be some other sort of problem.
I tried uninstalling Pulumi, deleting my projects, deleting the `.pulumi` folder and starting again. This time I ran `pulumi up` after I started the template project and it worked in both Python and Typescript. However when I ran `pulumi import` again I got the same error as above.
### Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
|
design
|
http error fetching aws resource plugin even though it s installed what happened i started a new pulumi project in python today using pulumi new aws python to test the pulumi import command on some aws resources creating the new pulumi project worked however when i run pulumi import aws sns topic x dev drip welcome sns i get the error previewing import dev view live type name plan info pulumi pulumi stack another one dev create error diagnostics pulumi pulumi stack another one dev error preview failed failed to validate provider config could not automatically download and install resource plugin pulumi resource aws at version install the plugin using pulumi plugin install resource aws underlying error error downloading plugin aws to file failed to download plugin aws http error fetching plugin from however if i run pulumi plugin install resource aws it seems to run successfully and the aws plugin is listed as installed when i run pulumi about steps to reproduce i don t know if this bug might be reproduced have a macbook pro install pulumi using the official homebrew tap start a new project usign pulumi new attempt to import an aws ressource expected behavior i expect the pulumi import command to run succesfully actual behavior the pulumi import command fails with this error diagnostics pulumi pulumi stack another one dev error preview failed failed to validate provider config could not automatically download and install resource plugin pulumi resource aws at version install the plugin using pulumi plugin install resource aws underlying error error downloading plugin aws to file failed to download plugin aws http error fetching plugin from output of pulumi about cli version go version go compiler gc plugins name version aws python unknown host os darwin version arch this project is written in python executable library frameworks python framework versions bin version backend name pulumi com url user iulspop organizations iulspop dependencies name version pip pulumi aws setuptools wheel additional context i found the troubleshooting page and i followed the steps but they didn t help in this case i just started the project so the provider version is already at the latest in fact the plugin is listed as installed at the correct version when i run pulumi about and version of the aws plugin supports so i think this must be some other sort of problem i tried uninstalling pulumi deleting my projects deleting the pulumi folder and starting again this time i ran pulumi up after i started the template project and it worked in both python and typescript however when i ran pulumi import again i got the same error as above contributing vote on this issue by adding a 👍 reaction to contribute a fix for this issue leave a comment and link to your pull request if you ve opened one already
| 1
|
1,329
| 2,603,785,611
|
IssuesEvent
|
2015-02-24 17:55:01
|
chrsmith/nishazi6
|
https://api.github.com/repos/chrsmith/nishazi6
|
opened
|
沈阳治疗乳头瘤病毒
|
auto-migrated Priority-Medium Type-Defect
|
```
沈阳治疗乳头瘤病毒〓沈陽軍區政治部醫院性病〓TEL：024-3102
3308〓成立于1946年，68年專注于性傳播疾病的研究和治療。位�
��沈陽市沈河區二緯路32號。是一所與新中國同建立共輝煌的�
��史悠久、設備精良、技術權威、專家云集，是預防、保健、
醫療、科研康復為一體的綜合性醫院。是國家首批公立甲等��
�隊醫院、全國首批醫療規范定點單位，是第四軍醫大學、東�
��大學等知名高等院校的教學醫院。曾被中國人民解放軍空軍
后勤部衛生部評為衛生工作先進單位，先后兩次榮立集體二��
�功。
```
-----
Original issue reported on code.google.com by `q964105...@gmail.com` on 4 Jun 2014 at 8:25
|
1.0
|
沈阳治疗乳头瘤病毒 - ```
沈阳治疗乳头瘤病毒〓沈陽軍區政治部醫院性病〓TEL：024-3102
3308〓成立于1946年，68年專注于性傳播疾病的研究和治療。位�
��沈陽市沈河區二緯路32號。是一所與新中國同建立共輝煌的�
��史悠久、設備精良、技術權威、專家云集，是預防、保健、
醫療、科研康復為一體的綜合性醫院。是國家首批公立甲等��
�隊醫院、全國首批醫療規范定點單位，是第四軍醫大學、東�
��大學等知名高等院校的教學醫院。曾被中國人民解放軍空軍
后勤部衛生部評為衛生工作先進單位，先后兩次榮立集體二��
�功。
```
-----
Original issue reported on code.google.com by `q964105...@gmail.com` on 4 Jun 2014 at 8:25
|
non_design
|
沈阳治疗乳头瘤病毒 沈阳治疗乳头瘤病毒〓沈陽軍區政治部醫院性病〓tel： 〓 ， 。位� �� 。是一所與新中國同建立共輝煌的� ��史悠久、設備精良、技術權威、專家云集，是預防、保健、 醫療、科研康復為一體的綜合性醫院。是國家首批公立甲等�� �隊醫院、全國首批醫療規范定點單位，是第四軍醫大學、東� ��大學等知名高等院校的教學醫院。曾被中國人民解放軍空軍 后勤部衛生部評為衛生工作先進單位，先后兩次榮立集體二�� �功。 original issue reported on code google com by gmail com on jun at
| 0
|
220,403
| 17,193,099,530
|
IssuesEvent
|
2021-07-16 13:46:00
|
nodejs/node-addon-api
|
https://api.github.com/repos/nodejs/node-addon-api
|
closed
|
[Tests] Add test Coverage for Symbol class
|
test
|
| class | methods |
|-------------------------|----------------------------------------------------------------------------------------------------------------------------------|
|Covered #972 | static Symbol New(napi_env env, const std::string& description) |
| Covered #972 | static Symbol New(napi_env env, napi_value description) |
| Covered #972 | Symbol() |
| Covered #972 | Symbol(napi_env env, napi_value description) |
| Covered #972 |Symbol(napi_env env, Napi::String description) |
| Covered #972 |Symbol(napi_env env, const std::string& description) |
| Covered #972 |Symbol(napi_env env , const char* description) |
| Covered #972 |Symbol::Wellknown(napi_env env, const std::string& name) |
|
1.0
|
[Tests] Add test Coverage for Symbol class - | class | methods |
|-------------------------|----------------------------------------------------------------------------------------------------------------------------------|
|Covered #972 | static Symbol New(napi_env env, const std::string& description) |
| Covered #972 | static Symbol New(napi_env env, napi_value description) |
| Covered #972 | Symbol() |
| Covered #972 | Symbol(napi_env env, napi_value description) |
| Covered #972 |Symbol(napi_env env, Napi::String description) |
| Covered #972 |Symbol(napi_env env, const std::string& description) |
| Covered #972 |Symbol(napi_env env , const char* description) |
| Covered #972 |Symbol::Wellknown(napi_env env, const std::string& name) |
|
non_design
|
add test coverage for symbol class class methods covered static symbol new napi env env const std string description covered static symbol new napi env env napi value description covered symbol covered symbol napi env env napi value description covered symbol napi env env napi string description covered symbol napi env env const std string description covered symbol napi env env const char description covered symbol wellknown napi env env const std string name
| 0
|
193,595
| 15,381,051,584
|
IssuesEvent
|
2021-03-02 22:02:12
|
golang/go
|
https://api.github.com/repos/golang/go
|
closed
|
x/website: various mistakes in documentation on modules
|
Documentation NeedsFix
|
I read the new documentation on modules (which is great, btw) and took notes of mistakes I encountered.
https://golang.org/doc/modules/gomod-ref
1. Contradiction: The description for 'replacement-path' says:
"[...] If this is a module path, you must specify a \_replacement-version\_ value. [...]"
But the following example shows the replacement of a module path without a replacement version value:
"`replace example.com/othermodule => example.com/myfork/othermodule`"
2. Section 'exclude', description of 'module-version":
"If this version number is omitted, all versions of the module are replaced with the content on the right side of the arrow."
But an 'exclude' directive doesn't have an arrow. This sentence seems to be copy&pasted from the 'replace' directive and wrong.
3. Contradiction:
"These directives are ignored in modules that depend on the current module."
vs. later
"These directives are ignored in modules that are dependencies of the current module."
Which one is it?
4. Formatting: In the first example one line is not correctly indented.
5. Formatting: "\_replacement-version\_", "\_replacement-path\_". The underscores are probably not intended, but unsupported Markdown syntax.
https://golang.org/doc/tutorial/create-module
6. "This tutorial's sequence includes six brief topics [...]"
Followed by a numbered list of seven topics. s/six/seven/
https://golang.org/doc/tutorial/call-module-code
7. Broken link: "Here, the replace directive [...]"
8. Broken tutorial: "In the hello directory, run go build to make Go locate the module and add it as a dependency to the go.mod file."
Starting with Go 1.16 'go build' doesn't add dependencies anymore, which breaks this tutorial (similar to #43672).
https://golang.org/doc/tutorial/getting-started
9. Outdated description: "3. On the Doc tab, under Index, [...]"
The former Doc tab is a menu item named 'Documentation' on the left side now.
https://golang.org/doc/modules/managing-dependencies
10. Broken link: "See package discovery."
11. Typo: "One you've discovered" s/One/Once/
https://golang.org/doc/modules/version-numbers
12. Typo: "For more, see Managingdependencies." (missing space)
https://golang.org/doc/modules/publishing
13. Typo: "6. [...] with 1nformation about [...]"
s/1nformation/information/
14. Broken links: "go get command" (twice)
here: "[ ... ] and run the go get command [...]",
and here: "They can run the go get command [...]
https://golang.org/doc/modules/major-version
15. Invalid syntax:
"Old import statement: `import example.com/mymodule/package1`
New import statement: `import example.com/mymodule/v2/package1`"
Package paths must be in quotes.
General
16. The anchors on most pages under doc/modules have temporary names: #tmp_0, #tmp_1, etc.
|
1.0
|
x/website: various mistakes in documentation on modules - I read the new documentation on modules (which is great, btw) and took notes of mistakes I encountered.
https://golang.org/doc/modules/gomod-ref
1. Contradiction: The description for 'replacement-path' says:
"[...] If this is a module path, you must specify a \_replacement-version\_ value. [...]"
But the following example shows the replacement of a module path without a replacement version value:
"`replace example.com/othermodule => example.com/myfork/othermodule`"
2. Section 'exclude', description of 'module-version":
"If this version number is omitted, all versions of the module are replaced with the content on the right side of the arrow."
But an 'exclude' directive doesn't have an arrow. This sentence seems to be copy&pasted from the 'replace' directive and wrong.
3. Contradiction:
"These directives are ignored in modules that depend on the current module."
vs. later
"These directives are ignored in modules that are dependencies of the current module."
Which one is it?
4. Formatting: In the first example one line is not correctly indented.
5. Formatting: "\_replacement-version\_", "\_replacement-path\_". The underscores are probably not intended, but unsupported Markdown syntax.
https://golang.org/doc/tutorial/create-module
6. "This tutorial's sequence includes six brief topics [...]"
Followed by a numbered list of seven topics. s/six/seven/
https://golang.org/doc/tutorial/call-module-code
7. Broken link: "Here, the replace directive [...]"
8. Broken tutorial: "In the hello directory, run go build to make Go locate the module and add it as a dependency to the go.mod file."
Starting with Go 1.16 'go build' doesn't add dependencies anymore, which breaks this tutorial (similar to #43672).
https://golang.org/doc/tutorial/getting-started
9. Outdated description: "3. On the Doc tab, under Index, [...]"
The former Doc tab is a menu item named 'Documentation' on the left side now.
https://golang.org/doc/modules/managing-dependencies
10. Broken link: "See package discovery."
11. Typo: "One you've discovered" s/One/Once/
https://golang.org/doc/modules/version-numbers
12. Typo: "For more, see Managingdependencies." (missing space)
https://golang.org/doc/modules/publishing
13. Typo: "6. [...] with 1nformation about [...]"
s/1nformation/information/
14. Broken links: "go get command" (twice)
here: "[ ... ] and run the go get command [...]",
and here: "They can run the go get command [...]
https://golang.org/doc/modules/major-version
15. Invalid syntax:
"Old import statement: `import example.com/mymodule/package1`
New import statement: `import example.com/mymodule/v2/package1`"
Package paths must be in quotes.
General
16. The anchors on most pages under doc/modules have temporary names: #tmp_0, #tmp_1, etc.
|
non_design
|
x website various mistakes in documentation on modules i read the new documentation on modules which is great btw and took notes of mistakes i encountered contradiction the description for replacement path says if this is a module path you must specify a replacement version value but the following example shows the replacement of a module path without a replacement version value replace example com othermodule example com myfork othermodule section exclude description of module version if this version number is omitted all versions of the module are replaced with the content on the right side of the arrow but an exclude directive doesn t have an arrow this sentence seems to be copy pasted from the replace directive and wrong contradiction these directives are ignored in modules that depend on the current module vs later these directives are ignored in modules that are dependencies of the current module which one is it formatting in the first example one line is not correctly indented formatting replacement version replacement path the underscores are probably not intended but unsupported markdown syntax this tutorial s sequence includes six brief topics followed by a numbered list of seven topics s six seven broken link here the replace directive broken tutorial in the hello directory run go build to make go locate the module and add it as a dependency to the go mod file starting with go go build doesn t add dependencies anymore which breaks this tutorial similar to outdated description on the doc tab under index the former doc tab is a menu item named documentation on the left side now broken link see package discovery typo one you ve discovered s one once typo for more see managingdependencies missing space typo with about s information broken links go get command twice here and run the go get command and here they can run the go get command invalid syntax old import statement import example com mymodule new import statement import example com mymodule package paths must be in quotes general the anchors on most pages under doc modules have temporary names tmp tmp etc
| 0
|
293,713
| 9,007,842,365
|
IssuesEvent
|
2019-02-05 00:43:52
|
Polymer/lit-element
|
https://api.github.com/repos/Polymer/lit-element
|
closed
|
[docs] Best practices for adding event listeners to a host element
|
Area: docs Priority: High Status: Accepted Type: Maintenance
|
There are three ways to add event listeners to a host element
1. In the constructor
2. In `ready`
3. In `connectedCallback` (requires removal in `disconnectedCallback`)
Which is the best way? Are there any memory leak issues for (1) and (2)?
I hope there would be some documentation on this topic.
|
1.0
|
[docs] Best practices for adding event listeners to a host element - There are three ways to add event listeners to a host element
1. In the constructor
2. In `ready`
3. In `connectedCallback` (requires removal in `disconnectedCallback`)
Which is the best way? Are there any memory leak issues for (1) and (2)?
I hope there would be some documentation on this topic.
|
non_design
|
best practices for adding event listeners to a host element there are three ways to add event listeners to a host element in the constructor in ready in connectedcallback requires removal in disconnectedcallback which is the best way are there any memory leak issues for and i hope there would be some documentation on this topic
| 0
|
153,526
| 24,141,067,102
|
IssuesEvent
|
2022-09-21 14:52:23
|
nymtech/team-product
|
https://api.github.com/repos/nymtech/team-product
|
closed
|
Wallet: create delegation screen first step & NE: table toolbar ui update
|
wallet network explorer design
|
This ticket require changes on the Network Explorer and the Wallet.
First step delegation screen - before any delegation user should see this screen with link to NYM explorer and explanation why they should use filters
_**Network Explorer:**_
Explorer filters currently are not visible enough
so let's change link to button in explorer and add copy to delegation screen that user for optimal search results should use advanced filters
mobile
_**Wallet:**_
Create this first step when users doesn't have delegations
Figma file location:
@benedettadavico I've been having a look with Marcin on the ui tickets done to fix Figma differences and he found one missing thing, that wasn't included on any of our tickets, and I'm going to use this one to include the change. Is the mnemonic on the signup, below screenshot is how it's looking currently on develop.
|
1.0
|
Wallet: create delegation screen first step & NE: table toolbar ui update - This ticket require changes on the Network Explorer and the Wallet.
First step delegation screen - before any delegation user should see this screen with link to NYM explorer and explanation why they should use filters
_**Network Explorer:**_
Explorer filters currently are not visible enough
so let's change link to button in explorer and add copy to delegation screen that user for optimal search results should use advanced filters
mobile
_**Wallet:**_
Create this first step when users doesn't have delegations
Figma file location:
@benedettadavico I've been having a look with Marcin on the ui tickets done to fix Figma differences and he found one missing thing, that wasn't included on any of our tickets, and I'm going to use this one to include the change. Is the mnemonic on the signup, below screenshot is how it's looking currently on develop.
|
design
|
wallet create delegation screen first step ne table toolbar ui update this ticket require changes on the network explorer and the wallet first step delegation screen before any delegation user should see this screen with link to nym explorer and explanation why they should use filters network explorer explorer filters currently are not visible enough so let s change link to button in explorer and add copy to delegation screen that user for optimal search results should use advanced filters mobile wallet create this first step when users doesn t have delegations figma file location benedettadavico i ve been having a look with marcin on the ui tickets done to fix figma differences and he found one missing thing that wasn t included on any of our tickets and i m going to use this one to include the change is the mnemonic on the signup below screenshot is how it s looking currently on develop
| 1
|
7,795
| 2,610,636,996
|
IssuesEvent
|
2015-02-26 21:33:43
|
alistairreilly/open-ig
|
https://api.github.com/repos/alistairreilly/open-ig
|
closed
|
UI hangok finomhangolása&elmaradt hangok pótlása
|
auto-migrated Milestone-0.93.500 Priority-Low Sound-Effects Type-Defect
|
```
Belső menü:
Nem megfelelő hangok:
-Hangok-->Gombhangok
-Játékmenet-->Épületek automatikus javítása.
Ennél a kettőnél click_low_1.wav helyett click_medium_2.wav-ot kellene
bejátszani.
```
Original issue reported on code.google.com by `Jozsef.T...@gmail.com` on 25 Aug 2011 at 6:18
|
1.0
|
UI hangok finomhangolása&elmaradt hangok pótlása - ```
Belső menü:
Nem megfelelő hangok:
-Hangok-->Gombhangok
-Játékmenet-->Épületek automatikus javítása.
Ennél a kettőnél click_low_1.wav helyett click_medium_2.wav-ot kellene
bejátszani.
```
Original issue reported on code.google.com by `Jozsef.T...@gmail.com` on 25 Aug 2011 at 6:18
|
non_design
|
ui hangok finomhangolása elmaradt hangok pótlása belső menü nem megfelelő hangok hangok gombhangok játékmenet épületek automatikus javítása ennél a kettőnél click low wav helyett click medium wav ot kellene bejátszani original issue reported on code google com by jozsef t gmail com on aug at
| 0
|
74,157
| 8,982,336,475
|
IssuesEvent
|
2019-01-31 01:36:17
|
quicwg/base-drafts
|
https://api.github.com/repos/quicwg/base-drafts
|
closed
|
ACK Frames should be in Increasing Packet Number Order
|
-transport design parked
|
The ACK frame consists of blocks in decreasing packet number order and, now that they use variable-length integers, processing these ACK blocks in reverse order is no longer feasible.
Generally, I feel that ACK blocks should be processed in increasing packet number order (start with smallest packet number), for a couple of reasons:
1. Assuming your list of Outstanding Sent Packets is ordered by increasing packet number (oldest packet at the front), for any ACK block you process, you'd expect the smallest packet number in the block to be at or near the front of the Sent Packets list.
2. If the smallest packet number isn't at the front of the Sent Packets list, then it's likely FACK/RACK could kick in, causing the front of the list to be removed immediately, further optimizing the search for the next smallest packet number that was acknowledged.
I can't see any reason for processing ACKs in the current order the frame contains them. Can anyone shed some light on why this order was originally chosen?
|
1.0
|
ACK Frames should be in Increasing Packet Number Order - The ACK frame consists of blocks in decreasing packet number order and, now that they use variable-length integers, processing these ACK blocks in reverse order is no longer feasible.
Generally, I feel that ACK blocks should be processed in increasing packet number order (start with smallest packet number), for a couple of reasons:
1. Assuming your list of Outstanding Sent Packets is ordered by increasing packet number (oldest packet at the front), for any ACK block you process, you'd expect the smallest packet number in the block to be at or near the front of the Sent Packets list.
2. If the smallest packet number isn't at the front of the Sent Packets list, then it's likely FACK/RACK could kick in, causing the front of the list to be removed immediately, further optimizing the search for the next smallest packet number that was acknowledged.
I can't see any reason for processing ACKs in the current order the frame contains them. Can anyone shed some light on why this order was originally chosen?
|
design
|
ack frames should be in increasing packet number order the ack frame consists of blocks in decreasing packet number order and now that they use variable length integers processing these ack blocks in reverse order is no longer feasible generally i feel that ack blocks should be processed in increasing packet number order start with smallest packet number for a couple of reasons assuming your list of outstanding sent packets is ordered by increasing packet number oldest packet at the front for any ack block you process you d expect the smallest packet number in the block to be at or near the front of the sent packets list if the smallest packet number isn t at the front of the sent packets list then it s likely fack rack could kick in causing the front of the list to be removed immediately further optimizing the search for the next smallest packet number that was acknowledged i can t see any reason for processing acks in the current order the frame contains them can anyone shed some light on why this order was originally chosen
| 1
|
92,701
| 11,700,841,589
|
IssuesEvent
|
2020-03-06 18:21:58
|
EnCiv/undebate
|
https://api.github.com/repos/EnCiv/undebate
|
opened
|
One on One UI Design
|
UI Design
|
When one has answered the questions, we want a special view for the "interview" style that candidates can send out to their constituents.
This is related to #3.
|
1.0
|
One on One UI Design - When one has answered the questions, we want a special view for the "interview" style that candidates can send out to their constituents.
This is related to #3.
|
design
|
one on one ui design when one has answered the questions we want a special view for the interview style that candidates can send out to their constituents this is related to
| 1
|
161,708
| 25,384,938,808
|
IssuesEvent
|
2022-11-21 21:00:06
|
NCIOCPL/cgov-digital-platform
|
https://api.github.com/repos/NCIOCPL/cgov-digital-platform
|
closed
|
Section Nav API is broken under certain circumstances.
|
bug Drupal - Redesign
|
### Issue description
> **ESTIMATE** TBD
The error below occurs because `$term_storage = $this->entityTypeManager->getStorage('taxonomy_term');` should be `$term_storage = $this->entityTypeManager()->getStorage('taxonomy_term');` as entityTypeManager on the ControllerBase is not a property but a method. The bigger issue here is that this code did not trip in testing. @kate-mashkina we need to make a regression use case for this issue. It occurs for `/taxonomy/term/11482/section-nav`.
```
The website encountered an unexpected error. Please try again later.
Error: Call to a member function getStorage() on null in Drupal\cgov_site_section\Controller\CgovNavTreeController->getParentTerm() (line 473 of profiles/custom/cgov_site/modules/custom/cgov_site_section/src/Controller/CgovNavTreeController.php).
Drupal\cgov_site_section\Controller\CgovNavTreeController->getParentTerm() (Line: 385)
Drupal\cgov_site_section\Controller\CgovNavTreeController->getNextBranch() (Line: 209)
Drupal\cgov_site_section\Controller\CgovNavTreeController->getParentNavInfo() (Line: 64)
Drupal\cgov_site_section\Controller\CgovNavTreeController->getSectionNav()
call_user_func_array() (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 564)
Drupal\Core\Render\Renderer->executeInRenderContext() (Line: 124)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext() (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 159)
Symfony\Component\HttpKernel\HttpKernel->handleRaw() (Line: 81)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 58)
Drupal\Core\StackMiddleware\Session->handle() (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass() (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle() (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() (Line: 23)
Stack\StackedHttpKernel->handle() (Line: 709)
Drupal\Core\DrupalKernel->handle() (Line: 19)
```
|
1.0
|
Section Nav API is broken under certain circumstances. - ### Issue description
> **ESTIMATE** TBD
The error below occurs because `$term_storage = $this->entityTypeManager->getStorage('taxonomy_term');` should be `$term_storage = $this->entityTypeManager()->getStorage('taxonomy_term');` as entityTypeManager on the ControllerBase is not a property but a method. The bigger issue here is that this code did not trip in testing. @kate-mashkina we need to make a regression use case for this issue. It occurs for `/taxonomy/term/11482/section-nav`.
```
The website encountered an unexpected error. Please try again later.
Error: Call to a member function getStorage() on null in Drupal\cgov_site_section\Controller\CgovNavTreeController->getParentTerm() (line 473 of profiles/custom/cgov_site/modules/custom/cgov_site_section/src/Controller/CgovNavTreeController.php).
Drupal\cgov_site_section\Controller\CgovNavTreeController->getParentTerm() (Line: 385)
Drupal\cgov_site_section\Controller\CgovNavTreeController->getNextBranch() (Line: 209)
Drupal\cgov_site_section\Controller\CgovNavTreeController->getParentNavInfo() (Line: 64)
Drupal\cgov_site_section\Controller\CgovNavTreeController->getSectionNav()
call_user_func_array() (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 564)
Drupal\Core\Render\Renderer->executeInRenderContext() (Line: 124)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext() (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 159)
Symfony\Component\HttpKernel\HttpKernel->handleRaw() (Line: 81)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 58)
Drupal\Core\StackMiddleware\Session->handle() (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass() (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle() (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() (Line: 23)
Stack\StackedHttpKernel->handle() (Line: 709)
Drupal\Core\DrupalKernel->handle() (Line: 19)
```
|
design
|
section nav api is broken under certain circumstances issue description estimate tbd the error below occurs because term storage this entitytypemanager getstorage taxonomy term should be term storage this entitytypemanager getstorage taxonomy term as entitytypemanager on the controllerbase is not a property but a method the bigger issue here is that this code did not trip in testing kate mashkina we need to make a regression use case for this issue it occurs for taxonomy term section nav the website encountered an unexpected error please try again later error call to a member function getstorage on null in drupal cgov site section controller cgovnavtreecontroller getparentterm line of profiles custom cgov site modules custom cgov site section src controller cgovnavtreecontroller php drupal cgov site section controller cgovnavtreecontroller getparentterm line drupal cgov site section controller cgovnavtreecontroller getnextbranch line drupal cgov site section controller cgovnavtreecontroller getparentnavinfo line drupal cgov site section controller cgovnavtreecontroller getsectionnav call user func array line drupal core eventsubscriber earlyrenderingcontrollerwrappersubscriber drupal core eventsubscriber closure line drupal core render renderer executeinrendercontext line drupal core eventsubscriber earlyrenderingcontrollerwrappersubscriber wrapcontrollerexecutioninrendercontext line drupal core eventsubscriber earlyrenderingcontrollerwrappersubscriber drupal core eventsubscriber closure line symfony component httpkernel httpkernel handleraw line symfony component httpkernel httpkernel handle line drupal core stackmiddleware session handle line drupal core stackmiddleware kernelprehandle handle line drupal page cache stackmiddleware pagecache pass line drupal page cache stackmiddleware pagecache handle line drupal core stackmiddleware reverseproxymiddleware handle line drupal core stackmiddleware negotiationmiddleware handle line stack stackedhttpkernel handle line drupal core drupalkernel handle line
| 1
|
172,245
| 27,250,056,731
|
IssuesEvent
|
2023-02-22 07:14:30
|
Mapsui/Mapsui
|
https://api.github.com/repos/Mapsui/Mapsui
|
closed
|
Add a MAUI MapControl sample
|
enhancement design/roadmap
|
**Is your feature request related to a problem? Please describe.**
Mapsui supports MapControl on all platforms and Mapview only on Xamarin.Forms, and in the future probably on Xamarin.Maui. My intention is to further improve MapControl and to make it the primary option. Right now Xamarin.Forms (the platform that is used the most) has no sample of how the MapControl should be used, so most of our users start out with Mapview, not aware of MapControl.
**Describe the solution you'd like**
Rename the existing one to Mapsui.Samples.Maui.Mapview and add a new MapControl sample named Mapsui.Samples.Maui.
**Describe alternatives you've considered**
- Do the same for Xamarin.Forms.
- Introduce Mapsui.Samples.Maui.MapControl and keep Mapview the same. Disadvantages: The naming of the Mapview sample will have the same format as the other MapControl samples which is confusing.
|
1.0
|
Add a MAUI MapControl sample - **Is your feature request related to a problem? Please describe.**
Mapsui supports MapControl on all platforms and Mapview only on Xamarin.Forms, and in the future probably on Xamarin.Maui. My intention is to further improve MapControl and to make it the primary option. Right now Xamarin.Forms (the platform that is used the most) has no sample of how the MapControl should be used, so most of our users start out with Mapview, not aware of MapControl.
**Describe the solution you'd like**
Rename the existing one to Mapsui.Samples.Maui.Mapview and add a new MapControl sample named Mapsui.Samples.Maui.
**Describe alternatives you've considered**
- Do the same for Xamarin.Forms.
- Introduce Mapsui.Samples.Maui.MapControl and keep Mapview the same. Disadvantages: The naming of the Mapview sample will have the same format as the other MapControl samples which is confusing.
|
design
|
add a maui mapcontrol sample is your feature request related to a problem please describe mapsui supports mapcontrol on all platforms and mapview only on xamarin forms and in the future probably on xamarin maui my intention is to further improve mapcontrol and to make it the primary option right now xamarin forms the platform that is used the most has no sample of how the mapcontrol should be used so most of our users start out with mapview not aware of mapcontrol describe the solution you d like rename the existing one to mapsui samples maui mapview and add a new mapcontrol sample named mapsui samples maui describe alternatives you ve considered do the same for xamarin forms introduce mapsui samples maui mapcontrol and keep mapview the same disadvantages the naming of the mapview sample will have the same format as the other mapcontrol samples which is confusing
| 1
|
88,896
| 11,167,158,111
|
IssuesEvent
|
2019-12-27 16:02:23
|
alpheios-project/components
|
https://api.github.com/repos/alpheios-project/components
|
reopened
|
browse grammars should offer top level choice of language to browse
|
design waiting_verification
|
to be consistent with Browse Inflections.
Can wait until after the release.
|
1.0
|
browse grammars should offer top level choice of language to browse - to be consistent with Browse Inflections.
Can wait until after the release.
|
design
|
browse grammars should offer top level choice of language to browse to be consistent with browse inflections can wait until after the release
| 1
|
45,333
| 5,922,435,555
|
IssuesEvent
|
2017-05-23 03:34:42
|
SCILHS/i2p-transform
|
https://api.github.com/repos/SCILHS/i2p-transform
|
closed
|
PCORnet V3 table names
|
design issue
|
I figured that 3 of the PCORnet tables are named different from the name used in the PCORnet v3 data model. The 3 tables are:
current name data model name
labresults_cm --> lab_result_cm
death_cause --> death_condition
procedure --> procedures
Please change these names to the data model name.
|
1.0
|
PCORnet V3 table names - I figured that 3 of the PCORnet tables are named different from the name used in the PCORnet v3 data model. The 3 tables are:
current name data model name
labresults_cm --> lab_result_cm
death_cause --> death_condition
procedure --> procedures
Please change these names to the data model name.
|
design
|
pcornet table names i figured that of the pcornet tables are named different from the name used in the pcornet data model the tables are current name data model name labresults cm lab result cm death cause death condition procedure procedures please change these names to the data model name
| 1
|
142,035
| 21,658,414,636
|
IssuesEvent
|
2022-05-06 16:22:07
|
BCDevOps/developer-experience
|
https://api.github.com/repos/BCDevOps/developer-experience
|
opened
|
Component Backlog (rewrite)
|
documentation service-design
|
Rewrite the following pages:
Component Backlog https://developer.gov.bc.ca/Design-System/Component-Backlog
**Definition of done**
- [ ] First draft
- [ ] SME review
- [ ] Approval
|
1.0
|
Component Backlog (rewrite) - Rewrite the following pages:
Component Backlog https://developer.gov.bc.ca/Design-System/Component-Backlog
**Definition of done**
- [ ] First draft
- [ ] SME review
- [ ] Approval
|
design
|
component backlog rewrite rewrite the following pages component backlog definition of done first draft sme review approval
| 1
|
157,741
| 13,721,937,664
|
IssuesEvent
|
2020-10-03 00:57:46
|
rodgeraraujo/minus.css
|
https://api.github.com/repos/rodgeraraujo/minus.css
|
opened
|
New ideas or improvement of the existing ones
|
documentation enhancement good first issue hacktoberfest help wanted
|
If you have any new ideas or suggestions for improvement feel free to fork and contribute
But remember, this is a `small and minimalistic css framework`.
|
1.0
|
New ideas or improvement of the existing ones - If you have any new ideas or suggestions for improvement feel free to fork and contribute
But remember, this is a `small and minimalistic css framework`.
|
non_design
|
new ideas or improvement of the existing ones if you have any new ideas or suggestions for improvement feel free to fork and contribute but remember this is a small and minimalistic css framework
| 0
|
201,551
| 15,803,090,779
|
IssuesEvent
|
2021-04-03 12:50:12
|
yuri-norwood/dotfiles
|
https://api.github.com/repos/yuri-norwood/dotfiles
|
closed
|
[HUB]: Standardise all Workflows
|
actions documentation github labeler sponsor
|
I've developed some good standardisations and simplifications in my go projects, and I've ended up using those as my base for new repos instead of this dotfiles repo, which is exactly what it is supposed to be for. Remedy this.
|
1.0
|
[HUB]: Standardise all Workflows - I've developed some good standardisations and simplifications in my go projects, and I've ended up using those as my base for new repos instead of this dotfiles repo, which is exactly what it is supposed to be for. Remedy this.
|
non_design
|
standardise all workflows i ve developed some good standardisations and simplifications in my go projects and i ve ended up using those as my base for new repos instead of this dotfiles repo which is exactly what it is supposed to be for remedy this
| 0
|
40,734
| 8,831,785,013
|
IssuesEvent
|
2019-01-04 00:45:52
|
kosyachniy/dev
|
https://api.github.com/repos/kosyachniy/dev
|
opened
|
Добавить Arduino код для всех модулей
|
code maintain
|
- [ ] Wi-Fi
- [ ] Bluetooth
- [ ] mSD
### Идея
Расписать принцип работы с каждым модулем для микроконтроллера Arduino (Uno, Nano)
### Описание
Добавить принципиальные схемы, источники, аргументацию именно такого выбора, способы совмещения и вариации
### Для чего
1. Сбор готовых решений на базе модульной структуры
2. Прийти к единному концепту сборки, проверенному опытом
### Необходимо для реализации
1.
### Ресурсы
[]()
|
1.0
|
Добавить Arduino код для всех модулей - - [ ] Wi-Fi
- [ ] Bluetooth
- [ ] mSD
### Идея
Расписать принцип работы с каждым модулем для микроконтроллера Arduino (Uno, Nano)
### Описание
Добавить принципиальные схемы, источники, аргументацию именно такого выбора, способы совмещения и вариации
### Для чего
1. Сбор готовых решений на базе модульной структуры
2. Прийти к единному концепту сборки, проверенному опытом
### Необходимо для реализации
1.
### Ресурсы
[]()
|
non_design
|
добавить arduino код для всех модулей wi fi bluetooth msd идея расписать принцип работы с каждым модулем для микроконтроллера arduino uno nano описание добавить принципиальные схемы источники аргументацию именно такого выбора способы совмещения и вариации для чего сбор готовых решений на базе модульной структуры прийти к единному концепту сборки проверенному опытом необходимо для реализации ресурсы
| 0
|
62,957
| 7,659,893,996
|
IssuesEvent
|
2018-05-11 08:32:44
|
intelligentpos/setting
|
https://api.github.com/repos/intelligentpos/setting
|
opened
|
Change the behaviour of ProviderFiller to not error on optional fields
|
Technical Design
|
The provider filler should not error if the field is optional, and there is no value for it, it should not error. As the definer of the struct has instructed that they do not consider the missing key to be an error state.
|
1.0
|
Change the behaviour of ProviderFiller to not error on optional fields - The provider filler should not error if the field is optional, and there is no value for it, it should not error. As the definer of the struct has instructed that they do not consider the missing key to be an error state.
|
design
|
change the behaviour of providerfiller to not error on optional fields the provider filler should not error if the field is optional and there is no value for it it should not error as the definer of the struct has instructed that they do not consider the missing key to be an error state
| 1
|
217,968
| 24,351,704,985
|
IssuesEvent
|
2022-10-03 01:11:33
|
kzonix/firecall-flex-apio
|
https://api.github.com/repos/kzonix/firecall-flex-apio
|
opened
|
CVE-2022-42004 (Medium) detected in jackson-databind-2.10.1.jar
|
security vulnerability
|
## CVE-2022-42004 - 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.10.1.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: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.10.1/18eee15ffc662d27538d5b6ee84e4c92c0a9d03e/jackson-databind-2.10.1.jar</p>
<p>
Dependency Hierarchy:
- cyclops-jackson-integration-10.4.0.jar (Root Library)
- :x: **jackson-databind-2.10.1.jar** (Vulnerable Library)
<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 FasterXML jackson-databind before 2.13.4, resource exhaustion can occur because of a lack of a check in BeanDeserializer._deserializeFromArray to prevent use of deeply nested arrays. An application is vulnerable only with certain customized choices for deserialization.
<p>Publish Date: 2022-10-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-42004>CVE-2022-42004</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-02</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.13.4</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-42004 (Medium) detected in jackson-databind-2.10.1.jar - ## CVE-2022-42004 - 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.10.1.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: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.10.1/18eee15ffc662d27538d5b6ee84e4c92c0a9d03e/jackson-databind-2.10.1.jar</p>
<p>
Dependency Hierarchy:
- cyclops-jackson-integration-10.4.0.jar (Root Library)
- :x: **jackson-databind-2.10.1.jar** (Vulnerable Library)
<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 FasterXML jackson-databind before 2.13.4, resource exhaustion can occur because of a lack of a check in BeanDeserializer._deserializeFromArray to prevent use of deeply nested arrays. An application is vulnerable only with certain customized choices for deserialization.
<p>Publish Date: 2022-10-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-42004>CVE-2022-42004</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-02</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.13.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_design
|
cve medium detected in 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 build gradle path to vulnerable library home wss scanner gradle caches modules files com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy cyclops jackson integration jar root library x jackson databind jar vulnerable library found in base branch master vulnerability details in fasterxml jackson databind before resource exhaustion can occur because of a lack of a check in beandeserializer deserializefromarray to prevent use of deeply nested arrays an application is vulnerable only with certain customized choices for deserialization publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution com fasterxml jackson core jackson databind step up your open source security game with mend
| 0
|
130,639
| 18,101,166,676
|
IssuesEvent
|
2021-09-22 14:21:15
|
practice-uffs/programa
|
https://api.github.com/repos/practice-uffs/programa
|
opened
|
Criação de uma mapa ilustrado
|
equipe:con-design serviço:cartaz
|
Foi solicitada a criação de um mapa ilustrado do Campus Chapecó. O mesmo será realizado no [figma.](https://www.figma.com/file/asNxUUlF41tcmttYyPoOrR/Excepcionais?node-id=401%3A2)
> Estamos elaborando um Guia do Estudante e gostaríamos de verificar a possibilidade da construção de um mapa do campus Chapecó, como o mapa que consta no Guia do Estudante do campus Erechim (disponível no site da UFFS).
Solicitante: ROZILENE BELLAVER
[Mural](https://mural.practice.uffs.cc/servico/1327)
|
1.0
|
Criação de uma mapa ilustrado - Foi solicitada a criação de um mapa ilustrado do Campus Chapecó. O mesmo será realizado no [figma.](https://www.figma.com/file/asNxUUlF41tcmttYyPoOrR/Excepcionais?node-id=401%3A2)
> Estamos elaborando um Guia do Estudante e gostaríamos de verificar a possibilidade da construção de um mapa do campus Chapecó, como o mapa que consta no Guia do Estudante do campus Erechim (disponível no site da UFFS).
Solicitante: ROZILENE BELLAVER
[Mural](https://mural.practice.uffs.cc/servico/1327)
|
design
|
criação de uma mapa ilustrado foi solicitada a criação de um mapa ilustrado do campus chapecó o mesmo será realizado no estamos elaborando um guia do estudante e gostaríamos de verificar a possibilidade da construção de um mapa do campus chapecó como o mapa que consta no guia do estudante do campus erechim disponível no site da uffs solicitante rozilene bellaver
| 1
|
1,619
| 10,454,255,563
|
IssuesEvent
|
2019-09-19 18:27:01
|
exercism/exercism
|
https://api.github.com/repos/exercism/exercism
|
closed
|
Check if tests pass before submitting
|
area/automation type/feature-request
|
I just saw a submission empty (I can give you the link if you want). I don't know why the user has submitted an empty solution, but it is now in my list of feedback to give and it makes no sense to leave a comment on it. I think this can be an improvement for the cli.
The cli should check whether the tests pass or not before pushing the code to exercism. If the tests don't pass, it fails displaying a console message like _"sorry, you have to pass all the tests before submitting your solution"_.
What do you think?.
|
1.0
|
Check if tests pass before submitting - I just saw a submission empty (I can give you the link if you want). I don't know why the user has submitted an empty solution, but it is now in my list of feedback to give and it makes no sense to leave a comment on it. I think this can be an improvement for the cli.
The cli should check whether the tests pass or not before pushing the code to exercism. If the tests don't pass, it fails displaying a console message like _"sorry, you have to pass all the tests before submitting your solution"_.
What do you think?.
|
non_design
|
check if tests pass before submitting i just saw a submission empty i can give you the link if you want i don t know why the user has submitted an empty solution but it is now in my list of feedback to give and it makes no sense to leave a comment on it i think this can be an improvement for the cli the cli should check whether the tests pass or not before pushing the code to exercism if the tests don t pass it fails displaying a console message like sorry you have to pass all the tests before submitting your solution what do you think
| 0
|
18,988
| 3,411,036,553
|
IssuesEvent
|
2015-12-04 23:13:41
|
mozilla/teach.mozilla.org
|
https://api.github.com/repos/mozilla/teach.mozilla.org
|
opened
|
Lock the sidebar
|
design dev
|
Suggestion from @kristinashu :
We should lock the sidebar so it's fixed in position.
|
1.0
|
Lock the sidebar - Suggestion from @kristinashu :
We should lock the sidebar so it's fixed in position.
|
design
|
lock the sidebar suggestion from kristinashu we should lock the sidebar so it s fixed in position
| 1
|
17,562
| 5,436,444,171
|
IssuesEvent
|
2017-03-06 01:02:57
|
joshuawhite929/spmia_feedback
|
https://api.github.com/repos/joshuawhite929/spmia_feedback
|
opened
|
README.md
|
chapter2_code
|
John,
Is the README.md file for chapter 2 out of date? Is it still necessary to use:
`docker-machine ip`
If not, can we update the text and perhaps change the address used to call the service to localhost?
Also, the directions for running the application are wrong. Unless you align the directory structure of chapters 1 & 2 to be like the rest of the book, the command should be:
`docker-compose -f docker-compose/common/docker-compose.yml up`
**Note:** For every other chapter, the command would be:
`docker-compose -f docker/common/docker-compose.yml`
|
1.0
|
README.md - John,
Is the README.md file for chapter 2 out of date? Is it still necessary to use:
`docker-machine ip`
If not, can we update the text and perhaps change the address used to call the service to localhost?
Also, the directions for running the application are wrong. Unless you align the directory structure of chapters 1 & 2 to be like the rest of the book, the command should be:
`docker-compose -f docker-compose/common/docker-compose.yml up`
**Note:** For every other chapter, the command would be:
`docker-compose -f docker/common/docker-compose.yml`
|
non_design
|
readme md john is the readme md file for chapter out of date is it still necessary to use docker machine ip if not can we update the text and perhaps change the address used to call the service to localhost also the directions for running the application are wrong unless you align the directory structure of chapters to be like the rest of the book the command should be docker compose f docker compose common docker compose yml up note for every other chapter the command would be docker compose f docker common docker compose yml
| 0
|
174,216
| 27,595,059,141
|
IssuesEvent
|
2023-03-09 05:20:50
|
codestates-seb/seb42_main_013
|
https://api.github.com/repos/codestates-seb/seb42_main_013
|
opened
|
[FE] Data create page design
|
FE design
|
### 만들고자 하는 기능
- 데이터 생성
### 해당 기능을 구현하기 위해 할 일
- [ ] 인풋
- [ ] 버튼
- [ ] 헤더
### 작업 완료 예상 날짜
2023-03-09
### 기타 사항(선택)
- 추가로 작성할 내용 있으면 작성
|
1.0
|
[FE] Data create page design - ### 만들고자 하는 기능
- 데이터 생성
### 해당 기능을 구현하기 위해 할 일
- [ ] 인풋
- [ ] 버튼
- [ ] 헤더
### 작업 완료 예상 날짜
2023-03-09
### 기타 사항(선택)
- 추가로 작성할 내용 있으면 작성
|
design
|
data create page design 만들고자 하는 기능 데이터 생성 해당 기능을 구현하기 위해 할 일 인풋 버튼 헤더 작업 완료 예상 날짜 기타 사항 선택 추가로 작성할 내용 있으면 작성
| 1
|
119,056
| 25,458,450,304
|
IssuesEvent
|
2022-11-24 16:07:43
|
SAP/fundamental-ngx
|
https://api.github.com/repos/SAP/fundamental-ngx
|
closed
|
fix(platform): table p13n dialog typos
|
code refactoring platform ariba table
|
#### Is this a bug, enhancement, or feature request?
Bug, Enhancement.
#### Briefly describe your proposal.
In the p13n dialog of the table component we have implemented some various dialog classes, like:
* `TableP13FilterComponent`, selector `fdp-table-p13-filter`
* `TableP13GroupComponent`, selector `fdp-table-p13-group` and so on...
Actually, they are never used, but instead of them used non existing components like:
* `fdp-table-p13n-sort`,
* `fdp-table-p13n-filter` and so on...
And even as both of them actually don't do any work component classes should be renamed to contain `n` after `13` in selectors.
#### Which versions of Angular and Fundamental Library for Angular are affected? (If this is a feature request, use current version.)
0.30.0-rc.140
#### If this is a bug, please provide steps for reproducing it.
.
#### Please provide relevant source code if applicable.
.
#### Is there anything else we should know?
.
|
1.0
|
fix(platform): table p13n dialog typos - #### Is this a bug, enhancement, or feature request?
Bug, Enhancement.
#### Briefly describe your proposal.
In the p13n dialog of the table component we have implemented some various dialog classes, like:
* `TableP13FilterComponent`, selector `fdp-table-p13-filter`
* `TableP13GroupComponent`, selector `fdp-table-p13-group` and so on...
Actually, they are never used, but instead of them used non existing components like:
* `fdp-table-p13n-sort`,
* `fdp-table-p13n-filter` and so on...
And even as both of them actually don't do any work component classes should be renamed to contain `n` after `13` in selectors.
#### Which versions of Angular and Fundamental Library for Angular are affected? (If this is a feature request, use current version.)
0.30.0-rc.140
#### If this is a bug, please provide steps for reproducing it.
.
#### Please provide relevant source code if applicable.
.
#### Is there anything else we should know?
.
|
non_design
|
fix platform table dialog typos is this a bug enhancement or feature request bug enhancement briefly describe your proposal in the dialog of the table component we have implemented some various dialog classes like selector fdp table filter selector fdp table group and so on actually they are never used but instead of them used non existing components like fdp table sort fdp table filter and so on and even as both of them actually don t do any work component classes should be renamed to contain n after in selectors which versions of angular and fundamental library for angular are affected if this is a feature request use current version rc if this is a bug please provide steps for reproducing it please provide relevant source code if applicable is there anything else we should know
| 0
|
128,368
| 17,501,496,241
|
IssuesEvent
|
2021-08-10 09:57:49
|
haproxy/haproxy
|
https://api.github.com/repos/haproxy/haproxy
|
closed
|
'option httpchk' : hiding headers or body at the end of the version string is deprecated.
|
status: works as designed
|
### Detailed Description of the Problem
[WARNING] (2961) : parsing [/usr/local/haproxy/conf/haproxy.cfg:92]: 'option httpchk' : hiding headers or body at the end of the version string is deprecated. Please, consider to use 'http-check send' directive instead.
[WARNING] (2961) : parsing [/usr/local/haproxy/conf/haproxy.cfg:108]: 'option httpchk' : hiding headers or body at the end of the version string is deprecated. Please, consider to use 'http-check send' directive instead.
Warnings were found.
### Expected Behavior
The service and monitoring page can run normally, but the status reports the following warning .
### Steps to Reproduce the Behavior
haproxy -c -f /usr/local/haproxy/conf/haproxy.cfg
### Do you have any idea what may have caused this?
_No response_
### Do you have an idea how to solve the issue?
_No response_
### What is your configuration?
```haproxy
global
# to have these messages end up in /var/log/haproxy.log you will
# need to:
#
# 1) configure syslog to accept network log events. This is done
# by adding the '-r' option to the SYSLOGD_OPTIONS in
# /etc/sysconfig/syslog
#
# 2) configure local2 events to go to the /var/log/haproxy.log
# file. A line like the following can be added to
# /etc/sysconfig/syslog
#
# local2.* /var/log/haproxy.log
#
log 127.0.0.1 local2
chroot /usr/local/haproxy
pidfile /usr/local/haproxy/socket/haproxy.pid
maxconn 4000
user haproxy
group haproxy
daemon
# turn on stats unix socket
stats socket /usr/local/haproxy/stats
#---------------------------------------------------------------------
# common defaults that all the 'listen' and 'backend' sections will
# use if not designated in their block
#---------------------------------------------------------------------
defaults
log global
option dontlognull
option redispatch
retries 3
timeout http-request 10s
timeout queue 1m
timeout connect 10s
timeout client 1m
timeout server 1m
timeout http-keep-alive 10s
timeout check 10s
maxconn 3000
listen stats
bind *:8080
mode http
stats enable
stats uri /haproxy
stats refresh 5s
stats realm haproxy-status
stats auth admin:HLLhll@123
listen jms-web
bind *:80
mode http
# redirect scheme https if !{ ssl_fc }
# bind *:443 ssl crt /opt/ssl.pem
option httplog
option httpclose
option forwardfor
option httpchk GET /api/health/
cookie SERVERID insert indirect
hash-type consistent
fullconn 500
balance leastconn
server 192.168.198.142 192.168.198.142:80 weight 1 cookie web01 check inter 2000 rise 2 fall 5
server 192.168.198.143 192.168.198.143:80 weight 1 cookie web02 check inter 2000 rise 2 fall 5
listen jms-ssh
bind *:2222
mode tcp
option tcplog
option tcp-check
fullconn 500
balance leastconn
server 192.168.198.142 192.168.198.142:2222 weight 1 check inter 2000 rise 2 fall 5 send-proxy
server 192.168.198.143 192.168.198.143:2222 weight 1 check inter 2000 rise 2 fall 5 send-proxy
listen jms-koko
bind *:80
mode http
option httplog
option httpclose
option forwardfor
option httpchk GET /koko/health/ HTTP/1.1\r\nHost:\ 192.168.198.140
cookie SERVERID insert indirect
hash-type consistent
fullconn 500
balance leastconn
server 192.168.198.142 192.168.198.142:80 weight 1 cookie web01 check inter 2000 rise 2 fall 5
server 192.168.198.143 192.168.198.143:80 weight 1 cookie web02 check inter 2000 rise 2 fall 5
listen jms-lion
bind *:80
mode http
option httplog
option httpclose
option forwardfor
option httpchk GET /lion/health/ HTTP/1.1\r\nHost:\ 192.168.198.140
cookie SERVERID insert indirect
hash-type consistent
fullconn 500
balance leastconn
server 192.168.198.142 192.168.198.142:80 weight 1 cookie web01 check inter 2000 rise 2 fall 5
server 192.168.198.143 192.168.198.143:80 weight 1 cookie web02 check inter 2000 rise 2 fall 5
#---------------------------------------------------------------------
#---------------------------------------------------------------------
# listen redis
# bind *:6379
# mode tcp
# timeout connect 3s
# timeout server 6s
# timeout client 6s
# option tcplog
# option tcp-check
# tcp-check connect
# tcp-check send AUTH\ KXOeyNgDeTdpeu9q\r\n
# tcp-check send PING\r\n
# tcp-check expect string +PONG
# tcp-check send info\ replication\r\n
# tcp-check expect string role: master
# tcp-check send QUIT\r\n
# tcp-check expect string +OK
# server redis01 192.168.100.11:6379 check inter 3s
# server redis02 192.168.100.12:6379 check inter 3s
# server redis03 192.168.100.13:6379 check inter 3s
```
### Output of `haproxy -vv`
```plain
HAProxy version 2.4.2-553dee3 2021/07/07 - https://haproxy.org/
Status: long-term supported branch - will stop receiving fixes around Q2 2026.
Known bugs: http://www.haproxy.org/bugs/bugs-2.4.2.html
Running on: Linux 3.10.0-1160.el7.x86_64 #1 SMP Mon Oct 19 16:18:59 UTC 2020 x86_64
Build options :
TARGET = linux-glibc
CPU = generic
CC = cc
CFLAGS = -m64 -march=x86-64 -O2 -g -Wall -Wextra -Wdeclaration-after-statement -fwrapv -Wno-unused-label -Wno-sign-compare -Wno-unused-parameter -Wno-clobbered -Wno-missing-field-initializers -Wtype-limits
OPTIONS = USE_PCRE=1 USE_OPENSSL=1 USE_LUA=1 USE_ZLIB=1 USE_SYSTEMD=1
DEBUG =
Feature list : +EPOLL -KQUEUE +NETFILTER +PCRE -PCRE_JIT -PCRE2 -PCRE2_JIT +POLL -PRIVATE_CACHE +THREAD -PTHREAD_PSHARED +BACKTRACE -STATIC_PCRE -STATIC_PCRE2 +TPROXY +LINUX_TPROXY +LINUX_SPLICE +LIBCRYPT +CRYPT_H +GETADDRINFO +OPENSSL +LUA +FUTEX +ACCEPT4 -CLOSEFROM +ZLIB -SLZ +CPU_AFFINITY +TFO +NS +DL +RT -DEVICEATLAS -51DEGREES -WURFL +SYSTEMD -OBSOLETE_LINKER +PRCTL +THREAD_DUMP -EVPORTS -OT -QUIC -PROMEX -MEMORY_PROFILING
Default settings :
bufsize = 16384, maxrewrite = 1024, maxpollevents = 200
Built with multi-threading support (MAX_THREADS=64, default=2).
Built with OpenSSL version : OpenSSL 1.0.2k-fips 26 Jan 2017
Running on OpenSSL version : OpenSSL 1.0.2k-fips 26 Jan 2017
OpenSSL library supports TLS extensions : yes
OpenSSL library supports SNI : yes
OpenSSL library supports : SSLv3 TLSv1.0 TLSv1.1 TLSv1.2
Built with Lua version : Lua 5.4.3
Built with network namespace support.
Built with zlib version : 1.2.7
Running on zlib version : 1.2.7
Compression algorithms supported : identity("identity"), deflate("deflate"), raw-deflate("deflate"), gzip("gzip")
Built with transparent proxy support using: IP_TRANSPARENT IPV6_TRANSPARENT IP_FREEBIND
Built with PCRE version : 8.32 2012-11-30
Running on PCRE version : 8.32 2012-11-30
PCRE library supports JIT : no (USE_PCRE_JIT not set)
Encrypted password support via crypt(3): yes
Built with gcc compiler version 4.8.5 20150623 (Red Hat 4.8.5-44)
Available polling systems :
epoll : pref=300, test result OK
poll : pref=200, test result OK
select : pref=150, test result OK
Total: 3 (3 usable), will use epoll.
Available multiplexer protocols :
(protocols marked as <default> cannot be specified using 'proto' keyword)
h2 : mode=HTTP side=FE|BE mux=H2 flags=HTX|CLEAN_ABRT|HOL_RISK|NO_UPG
fcgi : mode=HTTP side=BE mux=FCGI flags=HTX|HOL_RISK|NO_UPG
<default> : mode=HTTP side=FE|BE mux=H1 flags=HTX
h1 : mode=HTTP side=FE|BE mux=H1 flags=HTX|NO_UPG
<default> : mode=TCP side=FE|BE mux=PASS flags=
none : mode=TCP side=FE|BE mux=PASS flags=NO_UPG
Available services : none
Available filters :
[SPOE] spoe
[CACHE] cache
[FCGI] fcgi-app
[COMP] compression
[TRACE] trace
```
### Last Outputs and Backtraces
_No response_
### Additional Information
_No response_
|
1.0
|
'option httpchk' : hiding headers or body at the end of the version string is deprecated. - ### Detailed Description of the Problem
[WARNING] (2961) : parsing [/usr/local/haproxy/conf/haproxy.cfg:92]: 'option httpchk' : hiding headers or body at the end of the version string is deprecated. Please, consider to use 'http-check send' directive instead.
[WARNING] (2961) : parsing [/usr/local/haproxy/conf/haproxy.cfg:108]: 'option httpchk' : hiding headers or body at the end of the version string is deprecated. Please, consider to use 'http-check send' directive instead.
Warnings were found.
### Expected Behavior
The service and monitoring page can run normally, but the status reports the following warning .
### Steps to Reproduce the Behavior
haproxy -c -f /usr/local/haproxy/conf/haproxy.cfg
### Do you have any idea what may have caused this?
_No response_
### Do you have an idea how to solve the issue?
_No response_
### What is your configuration?
```haproxy
global
# to have these messages end up in /var/log/haproxy.log you will
# need to:
#
# 1) configure syslog to accept network log events. This is done
# by adding the '-r' option to the SYSLOGD_OPTIONS in
# /etc/sysconfig/syslog
#
# 2) configure local2 events to go to the /var/log/haproxy.log
# file. A line like the following can be added to
# /etc/sysconfig/syslog
#
# local2.* /var/log/haproxy.log
#
log 127.0.0.1 local2
chroot /usr/local/haproxy
pidfile /usr/local/haproxy/socket/haproxy.pid
maxconn 4000
user haproxy
group haproxy
daemon
# turn on stats unix socket
stats socket /usr/local/haproxy/stats
#---------------------------------------------------------------------
# common defaults that all the 'listen' and 'backend' sections will
# use if not designated in their block
#---------------------------------------------------------------------
defaults
log global
option dontlognull
option redispatch
retries 3
timeout http-request 10s
timeout queue 1m
timeout connect 10s
timeout client 1m
timeout server 1m
timeout http-keep-alive 10s
timeout check 10s
maxconn 3000
listen stats
bind *:8080
mode http
stats enable
stats uri /haproxy
stats refresh 5s
stats realm haproxy-status
stats auth admin:HLLhll@123
listen jms-web
bind *:80
mode http
# redirect scheme https if !{ ssl_fc }
# bind *:443 ssl crt /opt/ssl.pem
option httplog
option httpclose
option forwardfor
option httpchk GET /api/health/
cookie SERVERID insert indirect
hash-type consistent
fullconn 500
balance leastconn
server 192.168.198.142 192.168.198.142:80 weight 1 cookie web01 check inter 2000 rise 2 fall 5
server 192.168.198.143 192.168.198.143:80 weight 1 cookie web02 check inter 2000 rise 2 fall 5
listen jms-ssh
bind *:2222
mode tcp
option tcplog
option tcp-check
fullconn 500
balance leastconn
server 192.168.198.142 192.168.198.142:2222 weight 1 check inter 2000 rise 2 fall 5 send-proxy
server 192.168.198.143 192.168.198.143:2222 weight 1 check inter 2000 rise 2 fall 5 send-proxy
listen jms-koko
bind *:80
mode http
option httplog
option httpclose
option forwardfor
option httpchk GET /koko/health/ HTTP/1.1\r\nHost:\ 192.168.198.140
cookie SERVERID insert indirect
hash-type consistent
fullconn 500
balance leastconn
server 192.168.198.142 192.168.198.142:80 weight 1 cookie web01 check inter 2000 rise 2 fall 5
server 192.168.198.143 192.168.198.143:80 weight 1 cookie web02 check inter 2000 rise 2 fall 5
listen jms-lion
bind *:80
mode http
option httplog
option httpclose
option forwardfor
option httpchk GET /lion/health/ HTTP/1.1\r\nHost:\ 192.168.198.140
cookie SERVERID insert indirect
hash-type consistent
fullconn 500
balance leastconn
server 192.168.198.142 192.168.198.142:80 weight 1 cookie web01 check inter 2000 rise 2 fall 5
server 192.168.198.143 192.168.198.143:80 weight 1 cookie web02 check inter 2000 rise 2 fall 5
#---------------------------------------------------------------------
#---------------------------------------------------------------------
# listen redis
# bind *:6379
# mode tcp
# timeout connect 3s
# timeout server 6s
# timeout client 6s
# option tcplog
# option tcp-check
# tcp-check connect
# tcp-check send AUTH\ KXOeyNgDeTdpeu9q\r\n
# tcp-check send PING\r\n
# tcp-check expect string +PONG
# tcp-check send info\ replication\r\n
# tcp-check expect string role: master
# tcp-check send QUIT\r\n
# tcp-check expect string +OK
# server redis01 192.168.100.11:6379 check inter 3s
# server redis02 192.168.100.12:6379 check inter 3s
# server redis03 192.168.100.13:6379 check inter 3s
```
### Output of `haproxy -vv`
```plain
HAProxy version 2.4.2-553dee3 2021/07/07 - https://haproxy.org/
Status: long-term supported branch - will stop receiving fixes around Q2 2026.
Known bugs: http://www.haproxy.org/bugs/bugs-2.4.2.html
Running on: Linux 3.10.0-1160.el7.x86_64 #1 SMP Mon Oct 19 16:18:59 UTC 2020 x86_64
Build options :
TARGET = linux-glibc
CPU = generic
CC = cc
CFLAGS = -m64 -march=x86-64 -O2 -g -Wall -Wextra -Wdeclaration-after-statement -fwrapv -Wno-unused-label -Wno-sign-compare -Wno-unused-parameter -Wno-clobbered -Wno-missing-field-initializers -Wtype-limits
OPTIONS = USE_PCRE=1 USE_OPENSSL=1 USE_LUA=1 USE_ZLIB=1 USE_SYSTEMD=1
DEBUG =
Feature list : +EPOLL -KQUEUE +NETFILTER +PCRE -PCRE_JIT -PCRE2 -PCRE2_JIT +POLL -PRIVATE_CACHE +THREAD -PTHREAD_PSHARED +BACKTRACE -STATIC_PCRE -STATIC_PCRE2 +TPROXY +LINUX_TPROXY +LINUX_SPLICE +LIBCRYPT +CRYPT_H +GETADDRINFO +OPENSSL +LUA +FUTEX +ACCEPT4 -CLOSEFROM +ZLIB -SLZ +CPU_AFFINITY +TFO +NS +DL +RT -DEVICEATLAS -51DEGREES -WURFL +SYSTEMD -OBSOLETE_LINKER +PRCTL +THREAD_DUMP -EVPORTS -OT -QUIC -PROMEX -MEMORY_PROFILING
Default settings :
bufsize = 16384, maxrewrite = 1024, maxpollevents = 200
Built with multi-threading support (MAX_THREADS=64, default=2).
Built with OpenSSL version : OpenSSL 1.0.2k-fips 26 Jan 2017
Running on OpenSSL version : OpenSSL 1.0.2k-fips 26 Jan 2017
OpenSSL library supports TLS extensions : yes
OpenSSL library supports SNI : yes
OpenSSL library supports : SSLv3 TLSv1.0 TLSv1.1 TLSv1.2
Built with Lua version : Lua 5.4.3
Built with network namespace support.
Built with zlib version : 1.2.7
Running on zlib version : 1.2.7
Compression algorithms supported : identity("identity"), deflate("deflate"), raw-deflate("deflate"), gzip("gzip")
Built with transparent proxy support using: IP_TRANSPARENT IPV6_TRANSPARENT IP_FREEBIND
Built with PCRE version : 8.32 2012-11-30
Running on PCRE version : 8.32 2012-11-30
PCRE library supports JIT : no (USE_PCRE_JIT not set)
Encrypted password support via crypt(3): yes
Built with gcc compiler version 4.8.5 20150623 (Red Hat 4.8.5-44)
Available polling systems :
epoll : pref=300, test result OK
poll : pref=200, test result OK
select : pref=150, test result OK
Total: 3 (3 usable), will use epoll.
Available multiplexer protocols :
(protocols marked as <default> cannot be specified using 'proto' keyword)
h2 : mode=HTTP side=FE|BE mux=H2 flags=HTX|CLEAN_ABRT|HOL_RISK|NO_UPG
fcgi : mode=HTTP side=BE mux=FCGI flags=HTX|HOL_RISK|NO_UPG
<default> : mode=HTTP side=FE|BE mux=H1 flags=HTX
h1 : mode=HTTP side=FE|BE mux=H1 flags=HTX|NO_UPG
<default> : mode=TCP side=FE|BE mux=PASS flags=
none : mode=TCP side=FE|BE mux=PASS flags=NO_UPG
Available services : none
Available filters :
[SPOE] spoe
[CACHE] cache
[FCGI] fcgi-app
[COMP] compression
[TRACE] trace
```
### Last Outputs and Backtraces
_No response_
### Additional Information
_No response_
|
design
|
option httpchk hiding headers or body at the end of the version string is deprecated detailed description of the problem parsing option httpchk hiding headers or body at the end of the version string is deprecated please consider to use http check send directive instead parsing option httpchk hiding headers or body at the end of the version string is deprecated please consider to use http check send directive instead warnings were found expected behavior the service and monitoring page can run normally but the status reports the following warning steps to reproduce the behavior haproxy c f usr local haproxy conf haproxy cfg do you have any idea what may have caused this no response do you have an idea how to solve the issue no response what is your configuration haproxy global to have these messages end up in var log haproxy log you will need to configure syslog to accept network log events this is done by adding the r option to the syslogd options in etc sysconfig syslog configure events to go to the var log haproxy log file a line like the following can be added to etc sysconfig syslog var log haproxy log log chroot usr local haproxy pidfile usr local haproxy socket haproxy pid maxconn user haproxy group haproxy daemon turn on stats unix socket stats socket usr local haproxy stats common defaults that all the listen and backend sections will use if not designated in their block defaults log global option dontlognull option redispatch retries timeout http request timeout queue timeout connect timeout client timeout server timeout http keep alive timeout check maxconn listen stats bind mode http stats enable stats uri haproxy stats refresh stats realm haproxy status stats auth admin hllhll listen jms web bind mode http redirect scheme https if ssl fc bind ssl crt opt ssl pem option httplog option httpclose option forwardfor option httpchk get api health cookie serverid insert indirect hash type consistent fullconn balance leastconn server weight cookie check inter rise fall server weight cookie check inter rise fall listen jms ssh bind mode tcp option tcplog option tcp check fullconn balance leastconn server weight check inter rise fall send proxy server weight check inter rise fall send proxy listen jms koko bind mode http option httplog option httpclose option forwardfor option httpchk get koko health http r nhost cookie serverid insert indirect hash type consistent fullconn balance leastconn server weight cookie check inter rise fall server weight cookie check inter rise fall listen jms lion bind mode http option httplog option httpclose option forwardfor option httpchk get lion health http r nhost cookie serverid insert indirect hash type consistent fullconn balance leastconn server weight cookie check inter rise fall server weight cookie check inter rise fall listen redis bind mode tcp timeout connect timeout server timeout client option tcplog option tcp check tcp check connect tcp check send auth r n tcp check send ping r n tcp check expect string pong tcp check send info replication r n tcp check expect string role master tcp check send quit r n tcp check expect string ok server check inter server check inter server check inter output of haproxy vv plain haproxy version status long term supported branch will stop receiving fixes around known bugs running on linux smp mon oct utc build options target linux glibc cpu generic cc cc cflags march g wall wextra wdeclaration after statement fwrapv wno unused label wno sign compare wno unused parameter wno clobbered wno missing field initializers wtype limits options use pcre use openssl use lua use zlib use systemd debug feature list epoll kqueue netfilter pcre pcre jit jit poll private cache thread pthread pshared backtrace static pcre static tproxy linux tproxy linux splice libcrypt crypt h getaddrinfo openssl lua futex closefrom zlib slz cpu affinity tfo ns dl rt deviceatlas wurfl systemd obsolete linker prctl thread dump evports ot quic promex memory profiling default settings bufsize maxrewrite maxpollevents built with multi threading support max threads default built with openssl version openssl fips jan running on openssl version openssl fips jan openssl library supports tls extensions yes openssl library supports sni yes openssl library supports built with lua version lua built with network namespace support built with zlib version running on zlib version compression algorithms supported identity identity deflate deflate raw deflate deflate gzip gzip built with transparent proxy support using ip transparent transparent ip freebind built with pcre version running on pcre version pcre library supports jit no use pcre jit not set encrypted password support via crypt yes built with gcc compiler version red hat available polling systems epoll pref test result ok poll pref test result ok select pref test result ok total usable will use epoll available multiplexer protocols protocols marked as cannot be specified using proto keyword mode http side fe be mux flags htx clean abrt hol risk no upg fcgi mode http side be mux fcgi flags htx hol risk no upg mode http side fe be mux flags htx mode http side fe be mux flags htx no upg mode tcp side fe be mux pass flags none mode tcp side fe be mux pass flags no upg available services none available filters spoe cache fcgi app compression trace last outputs and backtraces no response additional information no response
| 1
|
135,483
| 5,252,935,641
|
IssuesEvent
|
2017-02-02 07:31:51
|
pmem/issues
|
https://api.github.com/repos/pmem/issues
|
closed
|
unit tests: unify order of running tests for Windows and Linux
|
OS: Linux OS: Windows Priority: 3 medium Type: Feature
|
On Linux for single test from directory there is set of configurations running. On the other hand on Windows at first configuration is chosen and than every test from given directory runs within that configuration. It would be nice to unify the output for both OSes.
|
1.0
|
unit tests: unify order of running tests for Windows and Linux - On Linux for single test from directory there is set of configurations running. On the other hand on Windows at first configuration is chosen and than every test from given directory runs within that configuration. It would be nice to unify the output for both OSes.
|
non_design
|
unit tests unify order of running tests for windows and linux on linux for single test from directory there is set of configurations running on the other hand on windows at first configuration is chosen and than every test from given directory runs within that configuration it would be nice to unify the output for both oses
| 0
|
144,746
| 22,514,003,093
|
IssuesEvent
|
2022-06-24 00:17:56
|
aws/aws-cdk
|
https://api.github.com/repos/aws/aws-cdk
|
closed
|
📊Tracking: AWS MediaStore
|
management/tracking needs-design @aws-cdk/aws-mediastore closed-for-staleness
|
Add your +1 👍 to help us prioritize high-level constructs for this service
---
### Overview:
<!--
Summary of the service (leverage the service’s product page for the text) and a link to the relevant AWS Docs.
This should be the same text that we put at the top of the package’s README.md. Also include a link to the
service’s CDK Construct Library API reference page.
-->
AWS Elemental MediaStore is a video origination and storage service that offers the high performance and immediate consistency required for live origination. With MediaStore, you can manage video assets as objects in containers to build dependable, cloud-based media workflows.
[AWS Docs](https://docs.aws.amazon.com/mediastore/latest/ug/what-is.html) <!-- replace `url` with link to the relevant AWS Docs -->
### Maturity: CloudFormation Resources Only
<!--
The valid maturity states are: CloudFormation Resources Only, Experimental, Developer Preview, Stable
-->
See the [AWS Construct Library Module Lifecycle doc](https://github.com/aws/aws-cdk-rfcs/blob/master/text/0107-construct-library-module-lifecycle.md) for more information about maturity levels.
### Implementation:
<!--
Checklist of use cases, constructs, features (such as grant methods) that will ship in this package
(not required until the issue is added to the public roadmap)
- [ ]
- [ ]
-->
See the [CDK API Reference](https://docs.aws.amazon.com/cdk/api/latest/docs/aws-mediastore-readme.html) for more implementation details.<!-- replace `url` with link to the service's CDK API reference -->
### Issue list:
<!--
e.g. checklist of links to feature requests, bugs, and PRs that are in scope for GA release of this module
(not required until the issues is added to the public roadmap)
- [ ]
- [ ]
-->
<!--
Labels to add:
- package/[name] (create new labels if they don’t already exist)
- needs-design (if cfn-only)
- management/roadmap (when added to the roadmap)
- in-progress (when added to “working on it” column of the roadmap)
-->
---
This is a 📊Tracking Issue
|
1.0
|
📊Tracking: AWS MediaStore - Add your +1 👍 to help us prioritize high-level constructs for this service
---
### Overview:
<!--
Summary of the service (leverage the service’s product page for the text) and a link to the relevant AWS Docs.
This should be the same text that we put at the top of the package’s README.md. Also include a link to the
service’s CDK Construct Library API reference page.
-->
AWS Elemental MediaStore is a video origination and storage service that offers the high performance and immediate consistency required for live origination. With MediaStore, you can manage video assets as objects in containers to build dependable, cloud-based media workflows.
[AWS Docs](https://docs.aws.amazon.com/mediastore/latest/ug/what-is.html) <!-- replace `url` with link to the relevant AWS Docs -->
### Maturity: CloudFormation Resources Only
<!--
The valid maturity states are: CloudFormation Resources Only, Experimental, Developer Preview, Stable
-->
See the [AWS Construct Library Module Lifecycle doc](https://github.com/aws/aws-cdk-rfcs/blob/master/text/0107-construct-library-module-lifecycle.md) for more information about maturity levels.
### Implementation:
<!--
Checklist of use cases, constructs, features (such as grant methods) that will ship in this package
(not required until the issue is added to the public roadmap)
- [ ]
- [ ]
-->
See the [CDK API Reference](https://docs.aws.amazon.com/cdk/api/latest/docs/aws-mediastore-readme.html) for more implementation details.<!-- replace `url` with link to the service's CDK API reference -->
### Issue list:
<!--
e.g. checklist of links to feature requests, bugs, and PRs that are in scope for GA release of this module
(not required until the issues is added to the public roadmap)
- [ ]
- [ ]
-->
<!--
Labels to add:
- package/[name] (create new labels if they don’t already exist)
- needs-design (if cfn-only)
- management/roadmap (when added to the roadmap)
- in-progress (when added to “working on it” column of the roadmap)
-->
---
This is a 📊Tracking Issue
|
design
|
📊tracking aws mediastore add your 👍 to help us prioritize high level constructs for this service overview summary of the service leverage the service’s product page for the text and a link to the relevant aws docs this should be the same text that we put at the top of the package’s readme md also include a link to the service’s cdk construct library api reference page aws elemental mediastore is a video origination and storage service that offers the high performance and immediate consistency required for live origination with mediastore you can manage video assets as objects in containers to build dependable cloud based media workflows maturity cloudformation resources only the valid maturity states are cloudformation resources only experimental developer preview stable see the for more information about maturity levels implementation checklist of use cases constructs features such as grant methods that will ship in this package not required until the issue is added to the public roadmap see the for more implementation details issue list e g checklist of links to feature requests bugs and prs that are in scope for ga release of this module not required until the issues is added to the public roadmap labels to add package create new labels if they don’t already exist needs design if cfn only management roadmap when added to the roadmap in progress when added to “working on it” column of the roadmap this is a 📊tracking issue
| 1
|
100,916
| 12,600,531,922
|
IssuesEvent
|
2020-06-11 08:19:14
|
otavanopisto/muikku
|
https://api.github.com/repos/otavanopisto/muikku
|
closed
|
Kansikuvan rajaus
|
NEEDS REVIEW REDESIGN WORKSPACES
|
Kansikuvan rajaustoiminto toimii vähän holtittomasti.
Esimerkiksi jos rajaa näin:
|
1.0
|
Kansikuvan rajaus - Kansikuvan rajaustoiminto toimii vähän holtittomasti.
Esimerkiksi jos rajaa näin:
|
design
|
kansikuvan rajaus kansikuvan rajaustoiminto toimii vähän holtittomasti esimerkiksi jos rajaa näin
| 1
|
298,230
| 22,470,855,873
|
IssuesEvent
|
2022-06-22 07:59:55
|
buerokratt/CentOps
|
https://api.github.com/repos/buerokratt/CentOps
|
closed
|
CentOps: Technical design
|
documentation
|
AS A Developer
I WANT TO produce a technical design which describes the technical choices we're making as a team to implement the goals outlines in the Architectural Design
SO THAT we can be sure that the technical approach is sound and that we can begin implementing it.
- [x] Produce a draft technical design
- [x] Share the technical design with the team and get feedback
|
1.0
|
CentOps: Technical design - AS A Developer
I WANT TO produce a technical design which describes the technical choices we're making as a team to implement the goals outlines in the Architectural Design
SO THAT we can be sure that the technical approach is sound and that we can begin implementing it.
- [x] Produce a draft technical design
- [x] Share the technical design with the team and get feedback
|
non_design
|
centops technical design as a developer i want to produce a technical design which describes the technical choices we re making as a team to implement the goals outlines in the architectural design so that we can be sure that the technical approach is sound and that we can begin implementing it produce a draft technical design share the technical design with the team and get feedback
| 0
|
812,787
| 30,352,175,479
|
IssuesEvent
|
2023-07-11 19:53:48
|
thePlebDev/Clicker
|
https://api.github.com/repos/thePlebDev/Clicker
|
closed
|
Better loading UI
|
enhancement priority 1 priority 2
|
# Proposed change
- Create a better loading UiIfor the user when is waiting for the access token
# Why is this important
- This will give the user more feedback when they are waiting for the access token
# Additional context
- n/a
|
2.0
|
Better loading UI - # Proposed change
- Create a better loading UiIfor the user when is waiting for the access token
# Why is this important
- This will give the user more feedback when they are waiting for the access token
# Additional context
- n/a
|
non_design
|
better loading ui proposed change create a better loading uiifor the user when is waiting for the access token why is this important this will give the user more feedback when they are waiting for the access token additional context n a
| 0
|
8,849
| 2,891,233,030
|
IssuesEvent
|
2015-06-15 02:13:07
|
openhealthcare/elcid
|
https://api.github.com/repos/openhealthcare/elcid
|
closed
|
Allergies - Clinical Safety edition
|
Clinical Governance Design discussion elCID Live elCID Microbiology elCID OPAT enhancement
|
Two possible features discussed today, feedback requested from all:
### Display in antimicrobials
Would it be helpful to display allergy information in the antimicrobials modal - to the right of the form.
This is the clinically relevant time that you really need the information?
### Confirm conflicting allergy/antimicrobial
Allergies and antimicrobials come from the same lookup list - e.g. we have good understanding of equivalence.
It would then be possible to answer the question
> Is this user allergic to this antimicrobial according to elCID
when a user saved an antimicrobial.
If the answer is yes, you can inform the user.
Pings:
@michaeledwardmarks @GabPoll @drcjar @ollyharvey @7575colli @jonnylambourne
<!---
@huboard:{"order":131.9609375,"custom_state":""}
-->
|
1.0
|
Allergies - Clinical Safety edition - Two possible features discussed today, feedback requested from all:
### Display in antimicrobials
Would it be helpful to display allergy information in the antimicrobials modal - to the right of the form.
This is the clinically relevant time that you really need the information?
### Confirm conflicting allergy/antimicrobial
Allergies and antimicrobials come from the same lookup list - e.g. we have good understanding of equivalence.
It would then be possible to answer the question
> Is this user allergic to this antimicrobial according to elCID
when a user saved an antimicrobial.
If the answer is yes, you can inform the user.
Pings:
@michaeledwardmarks @GabPoll @drcjar @ollyharvey @7575colli @jonnylambourne
<!---
@huboard:{"order":131.9609375,"custom_state":""}
-->
|
design
|
allergies clinical safety edition two possible features discussed today feedback requested from all display in antimicrobials would it be helpful to display allergy information in the antimicrobials modal to the right of the form this is the clinically relevant time that you really need the information confirm conflicting allergy antimicrobial allergies and antimicrobials come from the same lookup list e g we have good understanding of equivalence it would then be possible to answer the question is this user allergic to this antimicrobial according to elcid when a user saved an antimicrobial if the answer is yes you can inform the user pings michaeledwardmarks gabpoll drcjar ollyharvey jonnylambourne huboard order custom state
| 1
|
78,023
| 9,653,157,537
|
IssuesEvent
|
2019-05-19 00:46:30
|
panelinhadees/client
|
https://api.github.com/repos/panelinhadees/client
|
closed
|
Choose Font
|
design discussion
|
**Describe the solution you'd like**
A font that combines with developer and programmer things.
**Describe alternatives you've considered**
1. https://www.marksimonson.com/fonts/view/anonymous-pro
2. https://fonts.google.com/specimen/Roboto+Mono
3. https://artisanthemes.io/best-google-fonts-combinations-modern-agency-website/
|
1.0
|
Choose Font - **Describe the solution you'd like**
A font that combines with developer and programmer things.
**Describe alternatives you've considered**
1. https://www.marksimonson.com/fonts/view/anonymous-pro
2. https://fonts.google.com/specimen/Roboto+Mono
3. https://artisanthemes.io/best-google-fonts-combinations-modern-agency-website/
|
design
|
choose font describe the solution you d like a font that combines with developer and programmer things describe alternatives you ve considered
| 1
|
78,418
| 9,725,449,686
|
IssuesEvent
|
2019-05-30 08:44:33
|
mozilla-mobile/fenix
|
https://api.github.com/repos/mozilla-mobile/fenix
|
closed
|
[Bookmarks] Edit bookmark URL is covered by "clear" icon
|
Feature:Bookmarks P1 QA needed UX implementation review visual design 🐞 bug
|
The text should be faded out before the "x" icon.
|
1.0
|
[Bookmarks] Edit bookmark URL is covered by "clear" icon - The text should be faded out before the "x" icon.
|
design
|
edit bookmark url is covered by clear icon the text should be faded out before the x icon
| 1
|
7,006
| 5,806,646,087
|
IssuesEvent
|
2017-05-04 03:56:58
|
CleverRaven/Cataclysm-DDA
|
https://api.github.com/repos/CleverRaven/Cataclysm-DDA
|
closed
|
Triffid queens create a lot of wood.
|
Balance Performance
|
See this : http://prntscr.com/bno5z6 (I was standing on the roof, and had the queen run around a bit (it also trashed a car).
This was only one triffid queen. Normally several of them spawn, so they all create a lot of junk wood in your reality bubble. Perhaps this should be toned down. Or just make the queens special attack not create wood when it breaks trees. Otherwise queens will negatively affect game performance. (pressing V already lags in that location)
|
True
|
Triffid queens create a lot of wood. - See this : http://prntscr.com/bno5z6 (I was standing on the roof, and had the queen run around a bit (it also trashed a car).
This was only one triffid queen. Normally several of them spawn, so they all create a lot of junk wood in your reality bubble. Perhaps this should be toned down. Or just make the queens special attack not create wood when it breaks trees. Otherwise queens will negatively affect game performance. (pressing V already lags in that location)
|
non_design
|
triffid queens create a lot of wood see this i was standing on the roof and had the queen run around a bit it also trashed a car this was only one triffid queen normally several of them spawn so they all create a lot of junk wood in your reality bubble perhaps this should be toned down or just make the queens special attack not create wood when it breaks trees otherwise queens will negatively affect game performance pressing v already lags in that location
| 0
|
4,642
| 17,086,047,300
|
IssuesEvent
|
2021-07-08 12:00:10
|
gchq/Gaffer
|
https://api.github.com/repos/gchq/Gaffer
|
opened
|
CI sometimes ran unnecessarily
|
automation
|
Running the entire CI pipeline on a commit that changes a README is wasteful. We should add some checks to the CI action like the following:
```yaml
on:
pull_request:
paths-ignore:
- 'README.md'
```
We will have to think about which paths are reasonable to skip. See syntax [here](https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet).
|
1.0
|
CI sometimes ran unnecessarily - Running the entire CI pipeline on a commit that changes a README is wasteful. We should add some checks to the CI action like the following:
```yaml
on:
pull_request:
paths-ignore:
- 'README.md'
```
We will have to think about which paths are reasonable to skip. See syntax [here](https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet).
|
non_design
|
ci sometimes ran unnecessarily running the entire ci pipeline on a commit that changes a readme is wasteful we should add some checks to the ci action like the following yaml on pull request paths ignore readme md we will have to think about which paths are reasonable to skip see syntax
| 0
|
135,460
| 19,579,129,116
|
IssuesEvent
|
2022-01-04 18:48:41
|
stellar/stellar-design-system
|
https://api.github.com/repos/stellar/stellar-design-system
|
opened
|
Add new components
|
design-system
|
Add new components from AMM Reference UI.
- [ ] Avatar
- [ ] Card
- [ ] Tooltip
- [ ] Header
- [ ] Sortable table
- [ ] Pagination
- [ ] Chart
|
1.0
|
Add new components - Add new components from AMM Reference UI.
- [ ] Avatar
- [ ] Card
- [ ] Tooltip
- [ ] Header
- [ ] Sortable table
- [ ] Pagination
- [ ] Chart
|
design
|
add new components add new components from amm reference ui avatar card tooltip header sortable table pagination chart
| 1
|
95,964
| 12,067,163,110
|
IssuesEvent
|
2020-04-16 12:59:10
|
brave/brave-browser
|
https://api.github.com/repos/brave/brave-browser
|
opened
|
Fiat value text is not properly visible
|
QA/Yes design feature/crypto-wallets feature/crypto-widgets
|
<!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
<!--Provide a brief description of the issue-->
Fiat value text is not properly visible
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. Connect Binance widget
2. Switch to balance view to show
3. Fiat value is not properly visible
## Actual result:
<!--Please add screenshots if needed-->
## Expected result:
Clearly visible text colour
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
Easy
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Brave | 1.9.24 Chromium: 81.0.4044.92 (Official Build) nightly (64-bit)
-- | --
Revision | 32921c79b6f01a0fb2deef0e1d45b42f96581051-refs/branch-heads/4044@{#883}
OS | Linux
## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->
- Can you reproduce this issue with the current release? NA
- Can you reproduce this issue with the beta channel? NA
- Can you reproduce this issue with the dev channel? NA
- Can you reproduce this issue with the nightly channel? Yes
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? NA
- Does the issue resolve itself when disabling Brave Rewards? NA
- Is the issue reproducible on the latest version of Chrome? NA
## Miscellaneous Information:
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
should use the same colour text as used to fix #9236
|
1.0
|
Fiat value text is not properly visible - <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
<!--Provide a brief description of the issue-->
Fiat value text is not properly visible
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. Connect Binance widget
2. Switch to balance view to show
3. Fiat value is not properly visible
## Actual result:
<!--Please add screenshots if needed-->
## Expected result:
Clearly visible text colour
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
Easy
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Brave | 1.9.24 Chromium: 81.0.4044.92 (Official Build) nightly (64-bit)
-- | --
Revision | 32921c79b6f01a0fb2deef0e1d45b42f96581051-refs/branch-heads/4044@{#883}
OS | Linux
## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->
- Can you reproduce this issue with the current release? NA
- Can you reproduce this issue with the beta channel? NA
- Can you reproduce this issue with the dev channel? NA
- Can you reproduce this issue with the nightly channel? Yes
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? NA
- Does the issue resolve itself when disabling Brave Rewards? NA
- Is the issue reproducible on the latest version of Chrome? NA
## Miscellaneous Information:
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
should use the same colour text as used to fix #9236
|
design
|
fiat value text is not properly visible have you searched for similar issues before submitting this issue please check the open issues and add a note before logging a new issue please use the template below to provide information about the issue insufficient info will get the issue closed it will only be reopened after sufficient info is provided description fiat value text is not properly visible steps to reproduce connect binance widget switch to balance view to show fiat value is not properly visible actual result expected result clearly visible text colour reproduces how often easy brave version brave version info brave chromium official build nightly bit revision refs branch heads os linux version channel information can you reproduce this issue with the current release na can you reproduce this issue with the beta channel na can you reproduce this issue with the dev channel na can you reproduce this issue with the nightly channel yes other additional information does the issue resolve itself when disabling brave shields na does the issue resolve itself when disabling brave rewards na is the issue reproducible on the latest version of chrome na miscellaneous information should use the same colour text as used to fix
| 1
|
31,448
| 4,263,427,262
|
IssuesEvent
|
2016-07-12 00:37:56
|
18F/web-design-standards
|
https://api.github.com/repos/18F/web-design-standards
|
closed
|
[Website] Make mobile side nav open on the right
|
[Category] Front end [Category] User Experience [Category] Visual Design [Priority] Minor [Status] In progress [Type] Enhancement [Type] Website
|
## Description
This is a sub-issue in reference to #1227 website design update. Based off of the research done by the core team, it was determined that the side navigation should open to the right of the screen for smaller screen sizes. Below are the mock-ups to build the page from.
|
1.0
|
[Website] Make mobile side nav open on the right - ## Description
This is a sub-issue in reference to #1227 website design update. Based off of the research done by the core team, it was determined that the side navigation should open to the right of the screen for smaller screen sizes. Below are the mock-ups to build the page from.
|
design
|
make mobile side nav open on the right description this is a sub issue in reference to website design update based off of the research done by the core team it was determined that the side navigation should open to the right of the screen for smaller screen sizes below are the mock ups to build the page from
| 1
|
145,989
| 22,840,091,657
|
IssuesEvent
|
2022-07-12 20:48:48
|
GSA-TTS/FAC
|
https://api.github.com/repos/GSA-TTS/FAC
|
closed
|
design "Create New Audit: 1. Criteria Check" page for implementation based on sprint 6 research insights
|
design
|
Breakout issue of #274
**Background**
[Sprint 6 research - observations/refinements by page](https://docs.google.com/document/d/1Y8g7HEd6eysBQjg3x_-K3nzk9M9xBCp5w8eZXql_8xQ/edit#heading=h.ycduc4d91ltn)
**Observation(s)**
- While the questions themselves were easy for folks to answer, the purpose of these Qs wasn’t always clear to folks, but this didn’t bar them from continuing.
- A few users asked whether the $500K threshold regarding the OMB circular A-133 is still relevant, and this tripped them up.
- A few users wondered what would happen if you selected “No” for either of the second and third questions.
- Several users indicated confusion over the “unknown” field in the first question.
**MVP recommendation(s)**
- We should remove the “$500,000 or more during its audit period in accordance with OMB circular A-133” portion of the second question if possible (do we need clarification if there are reasons why this is here?).
**Future improvements**
- Consider adding content that better explains the purpose of these questions as checking that they need to submit a single audit and barring them from doing so if their entity doesn’t need to submit a single audit.
- Determine if or why the Yes/No questions are necessary.
**Tasks**
- [x] Review sprint 6 research analysis
- [x] Create checklists for refinement needed to each page
- [x] Update #274 with the checklist of refinements needed
- [x] Make refinements
- [x] Peer review
**Definition of done**
**Acceptance Criteria (We'll know we're done when...)**
- [x] Screens in Figma are ready to be handed off to front end
- [x] All text has a contrast ratio of 4.5:1 with the background
- [x] Interaction are documented if they deviate from USWDS components
- [ ] The needs of someone navigating the site with the use of a screenreader or keyboard has been considered and documented
- [ ] There is an option for multilingual support
- [ ] There is supporting documentation for alt text, labels for links (anchor + target), error text in forms, and what assistive technologies should announce (if applicable)
|
1.0
|
design "Create New Audit: 1. Criteria Check" page for implementation based on sprint 6 research insights - Breakout issue of #274
**Background**
[Sprint 6 research - observations/refinements by page](https://docs.google.com/document/d/1Y8g7HEd6eysBQjg3x_-K3nzk9M9xBCp5w8eZXql_8xQ/edit#heading=h.ycduc4d91ltn)
**Observation(s)**
- While the questions themselves were easy for folks to answer, the purpose of these Qs wasn’t always clear to folks, but this didn’t bar them from continuing.
- A few users asked whether the $500K threshold regarding the OMB circular A-133 is still relevant, and this tripped them up.
- A few users wondered what would happen if you selected “No” for either of the second and third questions.
- Several users indicated confusion over the “unknown” field in the first question.
**MVP recommendation(s)**
- We should remove the “$500,000 or more during its audit period in accordance with OMB circular A-133” portion of the second question if possible (do we need clarification if there are reasons why this is here?).
**Future improvements**
- Consider adding content that better explains the purpose of these questions as checking that they need to submit a single audit and barring them from doing so if their entity doesn’t need to submit a single audit.
- Determine if or why the Yes/No questions are necessary.
**Tasks**
- [x] Review sprint 6 research analysis
- [x] Create checklists for refinement needed to each page
- [x] Update #274 with the checklist of refinements needed
- [x] Make refinements
- [x] Peer review
**Definition of done**
**Acceptance Criteria (We'll know we're done when...)**
- [x] Screens in Figma are ready to be handed off to front end
- [x] All text has a contrast ratio of 4.5:1 with the background
- [x] Interaction are documented if they deviate from USWDS components
- [ ] The needs of someone navigating the site with the use of a screenreader or keyboard has been considered and documented
- [ ] There is an option for multilingual support
- [ ] There is supporting documentation for alt text, labels for links (anchor + target), error text in forms, and what assistive technologies should announce (if applicable)
|
design
|
design create new audit criteria check page for implementation based on sprint research insights breakout issue of background observation s while the questions themselves were easy for folks to answer the purpose of these qs wasn’t always clear to folks but this didn’t bar them from continuing a few users asked whether the threshold regarding the omb circular a is still relevant and this tripped them up a few users wondered what would happen if you selected “no” for either of the second and third questions several users indicated confusion over the “unknown” field in the first question mvp recommendation s we should remove the “ or more during its audit period in accordance with omb circular a ” portion of the second question if possible do we need clarification if there are reasons why this is here future improvements consider adding content that better explains the purpose of these questions as checking that they need to submit a single audit and barring them from doing so if their entity doesn’t need to submit a single audit determine if or why the yes no questions are necessary tasks review sprint research analysis create checklists for refinement needed to each page update with the checklist of refinements needed make refinements peer review definition of done acceptance criteria we ll know we re done when screens in figma are ready to be handed off to front end all text has a contrast ratio of with the background interaction are documented if they deviate from uswds components the needs of someone navigating the site with the use of a screenreader or keyboard has been considered and documented there is an option for multilingual support there is supporting documentation for alt text labels for links anchor target error text in forms and what assistive technologies should announce if applicable
| 1
|
128,299
| 17,475,657,810
|
IssuesEvent
|
2021-08-08 04:17:01
|
thedodd/trunk
|
https://api.github.com/repos/thedodd/trunk
|
closed
|
WASM Plugin / extension system
|
discussion needs design
|
### Abstract
Given that there will always be new features that folks want to add to Trunk, but adding too much to Trunk core would cause a fair amount of bloat, we will eventually want to expose a plugin system. The following is a non-exhaustive list of what we would like to see from the plugin system (**please comment below if you would like to add or remove items**):
- Ability for users to create their own plugins which will be loaded by the Trunk CLI and will be called as part of the standard Trunk build pipeline.
- Ability for plugins to declare the asset types which they will operate on.
- In the source HTML, this should be declared as something like `<link data-trunk data-plugin rel="my-plugin-type" any-other-attrs="will be passed to plugin"/>` (this needs further discussion).
- Trunk should see that the link is a plugin, and then will call any registered plugin which matches the `rel="my-plugin-type"`.
The Trunk team should build and maintain a `trunk-plugin` library which exposes common types used by Trunk itself, and which plugins should use to facilitate communication between Trunk and the plugin. Big shoutout to @lukechu10 for pointing out that WASM is perfect for this.
- This library will expose types needed to declare the Trunk ABI version which the plugin is using. This will allow us to safely evolve the plugin ABI without breaking old plugins.
- Which runtime should we use? Personally I like wasmer a lot. I've used it a bit and it is pretty solid. A lot of other folks in the WASM community outside of the Rust context are using it as well.
- What should the ABI look like which the WASM plugin modules need to expose?
- What are the ABI capabilities which Trunk should expose to plugins? This is gonna be a big item for discussion.
We need to gather some feedback.
- What do folks want to do with these plugins? This is nothing new. Many of the build/bundle tools in the JS ecosystem have plugin systems.
- What sort of data will the plugins need?
- What should our algorithm be for plugin discovery?
We will also want to discuss what Trunk itself should do in order to aid plugin authors in compiling, optimizing and publishing their WASM-plugins.
There is a lot to discuss here.
|
1.0
|
WASM Plugin / extension system - ### Abstract
Given that there will always be new features that folks want to add to Trunk, but adding too much to Trunk core would cause a fair amount of bloat, we will eventually want to expose a plugin system. The following is a non-exhaustive list of what we would like to see from the plugin system (**please comment below if you would like to add or remove items**):
- Ability for users to create their own plugins which will be loaded by the Trunk CLI and will be called as part of the standard Trunk build pipeline.
- Ability for plugins to declare the asset types which they will operate on.
- In the source HTML, this should be declared as something like `<link data-trunk data-plugin rel="my-plugin-type" any-other-attrs="will be passed to plugin"/>` (this needs further discussion).
- Trunk should see that the link is a plugin, and then will call any registered plugin which matches the `rel="my-plugin-type"`.
The Trunk team should build and maintain a `trunk-plugin` library which exposes common types used by Trunk itself, and which plugins should use to facilitate communication between Trunk and the plugin. Big shoutout to @lukechu10 for pointing out that WASM is perfect for this.
- This library will expose types needed to declare the Trunk ABI version which the plugin is using. This will allow us to safely evolve the plugin ABI without breaking old plugins.
- Which runtime should we use? Personally I like wasmer a lot. I've used it a bit and it is pretty solid. A lot of other folks in the WASM community outside of the Rust context are using it as well.
- What should the ABI look like which the WASM plugin modules need to expose?
- What are the ABI capabilities which Trunk should expose to plugins? This is gonna be a big item for discussion.
We need to gather some feedback.
- What do folks want to do with these plugins? This is nothing new. Many of the build/bundle tools in the JS ecosystem have plugin systems.
- What sort of data will the plugins need?
- What should our algorithm be for plugin discovery?
We will also want to discuss what Trunk itself should do in order to aid plugin authors in compiling, optimizing and publishing their WASM-plugins.
There is a lot to discuss here.
|
design
|
wasm plugin extension system abstract given that there will always be new features that folks want to add to trunk but adding too much to trunk core would cause a fair amount of bloat we will eventually want to expose a plugin system the following is a non exhaustive list of what we would like to see from the plugin system please comment below if you would like to add or remove items ability for users to create their own plugins which will be loaded by the trunk cli and will be called as part of the standard trunk build pipeline ability for plugins to declare the asset types which they will operate on in the source html this should be declared as something like this needs further discussion trunk should see that the link is a plugin and then will call any registered plugin which matches the rel my plugin type the trunk team should build and maintain a trunk plugin library which exposes common types used by trunk itself and which plugins should use to facilitate communication between trunk and the plugin big shoutout to for pointing out that wasm is perfect for this this library will expose types needed to declare the trunk abi version which the plugin is using this will allow us to safely evolve the plugin abi without breaking old plugins which runtime should we use personally i like wasmer a lot i ve used it a bit and it is pretty solid a lot of other folks in the wasm community outside of the rust context are using it as well what should the abi look like which the wasm plugin modules need to expose what are the abi capabilities which trunk should expose to plugins this is gonna be a big item for discussion we need to gather some feedback what do folks want to do with these plugins this is nothing new many of the build bundle tools in the js ecosystem have plugin systems what sort of data will the plugins need what should our algorithm be for plugin discovery we will also want to discuss what trunk itself should do in order to aid plugin authors in compiling optimizing and publishing their wasm plugins there is a lot to discuss here
| 1
|
419,350
| 28,143,139,801
|
IssuesEvent
|
2023-04-02 06:49:25
|
MarkBind/markbind
|
https://api.github.com/repos/MarkBind/markbind
|
opened
|
UG: tweak tip about div vs span
|
a-Documentation 📝
|
This indicates div is always preferred over span. I thought the choice between the two depends on whether the element is an inline element or a block element, and the hydration problem happens when authors use span where div should be used? I don't think we can ask authors to use div for inline elements as that can mess up the layout of the page (right?).
Also, not sure we should talk about hydration in the UG which is meant for authors, not developers.
|
1.0
|
UG: tweak tip about div vs span - 
This indicates div is always preferred over span. I thought the choice between the two depends on whether the element is an inline element or a block element, and the hydration problem happens when authors use span where div should be used? I don't think we can ask authors to use div for inline elements as that can mess up the layout of the page (right?).
Also, not sure we should talk about hydration in the UG which is meant for authors, not developers.
|
non_design
|
ug tweak tip about div vs span this indicates div is always preferred over span i thought the choice between the two depends on whether the element is an inline element or a block element and the hydration problem happens when authors use span where div should be used i don t think we can ask authors to use div for inline elements as that can mess up the layout of the page right also not sure we should talk about hydration in the ug which is meant for authors not developers
| 0
|
44,421
| 5,823,453,430
|
IssuesEvent
|
2017-05-07 01:26:24
|
brianwernick/ExoMedia
|
https://api.github.com/repos/brianwernick/ExoMedia
|
closed
|
onMediaPlaybackEnded() called repeatedly, even after resetting and preparing ExoAudioPlayer
|
Question Working as Designed
|
- [x] I have verified there are no duplicate active or recent bugs, questions, or requests
###### Include the following:
- ExoMedia version: `4.0.0`
- Device OS version: `6.0.1`
- Devide Manufacturer: `Google`
- Device Name: `Nexus 5`
###### Reproduction Steps
0. Initialize an ExoAudioPlayer
1. Prepare the ExoAudioPlayer for playback (reset(), setDataSource(), prepareAsync())
2. Wait for the ExoAudioPlayer to prepare. Then in the onPrepared() callback of ListenerMux.Notifier, call ExoAudioPlayer.start().
3. Wait for media playback to finish.
4. In the onMediaPlaybackEnded() callback of ListenerMux.Notifier, repeat step 1 above to prepare another media item for playback
###### Expected Result
The onPrepared() callback of ListenerMux.Notifier should be called when the second media item is prepared.
###### Actual Result
onMediaPlaybackEnded() is called again right after attempting to prepare the second item for playback, causing an infinite loop.
|
1.0
|
onMediaPlaybackEnded() called repeatedly, even after resetting and preparing ExoAudioPlayer - - [x] I have verified there are no duplicate active or recent bugs, questions, or requests
###### Include the following:
- ExoMedia version: `4.0.0`
- Device OS version: `6.0.1`
- Devide Manufacturer: `Google`
- Device Name: `Nexus 5`
###### Reproduction Steps
0. Initialize an ExoAudioPlayer
1. Prepare the ExoAudioPlayer for playback (reset(), setDataSource(), prepareAsync())
2. Wait for the ExoAudioPlayer to prepare. Then in the onPrepared() callback of ListenerMux.Notifier, call ExoAudioPlayer.start().
3. Wait for media playback to finish.
4. In the onMediaPlaybackEnded() callback of ListenerMux.Notifier, repeat step 1 above to prepare another media item for playback
###### Expected Result
The onPrepared() callback of ListenerMux.Notifier should be called when the second media item is prepared.
###### Actual Result
onMediaPlaybackEnded() is called again right after attempting to prepare the second item for playback, causing an infinite loop.
|
design
|
onmediaplaybackended called repeatedly even after resetting and preparing exoaudioplayer i have verified there are no duplicate active or recent bugs questions or requests include the following exomedia version device os version devide manufacturer google device name nexus reproduction steps initialize an exoaudioplayer prepare the exoaudioplayer for playback reset setdatasource prepareasync wait for the exoaudioplayer to prepare then in the onprepared callback of listenermux notifier call exoaudioplayer start wait for media playback to finish in the onmediaplaybackended callback of listenermux notifier repeat step above to prepare another media item for playback expected result the onprepared callback of listenermux notifier should be called when the second media item is prepared actual result onmediaplaybackended is called again right after attempting to prepare the second item for playback causing an infinite loop
| 1
|
117,764
| 15,171,133,656
|
IssuesEvent
|
2021-02-13 01:37:49
|
psf/black
|
https://api.github.com/repos/psf/black
|
opened
|
Mathematical expression become unreadable
|
design
|
**Request: minimal support for reasonable formatting of mathematical expressions**
Readability of mathematical expressions is critical for numerical code, and this is vitally dependent on reasonable code formatting. `Black` appears to have no sense of this issue, and produces code formatting that makes mathematical expressions not just obscure, but unreadable. I (developer of `scqubits`) love the idea of uniform code formatting. I also love the idea of enforcing uniformity by not providing options for formatting variations. The latter, however, can only work if the choices `black` makes fulfill minimal requirements of readability. If there is any interest within the `black` development team to address this issue, I would be happy to contribute and advise on reasonable formatting of mathematical expressions.
**Evidence of the above**
```python
def spectral_density(omega):
therm_ratio = calc_therm_ratio(omega, T)
s = (
2
* self.EL
/ q_ind_fun(omega)
* (1 / np.tanh(0.5 * np.abs(therm_ratio)))
/ (1 + np.exp(-therm_ratio))
)
```
**Reasonable style**
```python
def spectral_density(omega):
therm_ratio = calc_therm_ratio(omega, T)
s = (
2 * 8 * self. EC / q_cap_fun(omega)
* (1 / np.tanh(0.5 * np.abs(therm_ratio))) / (1 + np.exp(-therm_ratio))
)
```
The latter fits into the default 88 character line width just fine.
|
1.0
|
Mathematical expression become unreadable - **Request: minimal support for reasonable formatting of mathematical expressions**
Readability of mathematical expressions is critical for numerical code, and this is vitally dependent on reasonable code formatting. `Black` appears to have no sense of this issue, and produces code formatting that makes mathematical expressions not just obscure, but unreadable. I (developer of `scqubits`) love the idea of uniform code formatting. I also love the idea of enforcing uniformity by not providing options for formatting variations. The latter, however, can only work if the choices `black` makes fulfill minimal requirements of readability. If there is any interest within the `black` development team to address this issue, I would be happy to contribute and advise on reasonable formatting of mathematical expressions.
**Evidence of the above**
```python
def spectral_density(omega):
therm_ratio = calc_therm_ratio(omega, T)
s = (
2
* self.EL
/ q_ind_fun(omega)
* (1 / np.tanh(0.5 * np.abs(therm_ratio)))
/ (1 + np.exp(-therm_ratio))
)
```
**Reasonable style**
```python
def spectral_density(omega):
therm_ratio = calc_therm_ratio(omega, T)
s = (
2 * 8 * self. EC / q_cap_fun(omega)
* (1 / np.tanh(0.5 * np.abs(therm_ratio))) / (1 + np.exp(-therm_ratio))
)
```
The latter fits into the default 88 character line width just fine.
|
design
|
mathematical expression become unreadable request minimal support for reasonable formatting of mathematical expressions readability of mathematical expressions is critical for numerical code and this is vitally dependent on reasonable code formatting black appears to have no sense of this issue and produces code formatting that makes mathematical expressions not just obscure but unreadable i developer of scqubits love the idea of uniform code formatting i also love the idea of enforcing uniformity by not providing options for formatting variations the latter however can only work if the choices black makes fulfill minimal requirements of readability if there is any interest within the black development team to address this issue i would be happy to contribute and advise on reasonable formatting of mathematical expressions evidence of the above python def spectral density omega therm ratio calc therm ratio omega t s self el q ind fun omega np tanh np abs therm ratio np exp therm ratio reasonable style python def spectral density omega therm ratio calc therm ratio omega t s self ec q cap fun omega np tanh np abs therm ratio np exp therm ratio the latter fits into the default character line width just fine
| 1
|
123,862
| 16,543,368,721
|
IssuesEvent
|
2021-05-27 19:57:02
|
department-of-veterans-affairs/va.gov-team
|
https://api.github.com/repos/department-of-veterans-affairs/va.gov-team
|
closed
|
526 Enhancement - Reserve Info Military History Page
|
526 design vsa vsa-claims-appeals
|
## Issue Description
After doing testing for 526 enhancements, it was clear that this page could be consolidated to provide a better user experience for veterans filing disability claims. This ticket captures the design changes we intend to make based upon testing.
---
## Tasks
- [x] Create mockups of the new military service history page that includes reserve information
## Acceptance Criteria
- [x] Have spoken with BE and FE teams to understand tech requirements
- [x] mockups have been created
---
## How to configure this issue
- [ ] **Attached to a Milestone** (when will this be completed?)
- [ ] **Attached to an Epic** (what body of work is this a part of?)
- [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`)
- [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`)
- [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)
|
1.0
|
526 Enhancement - Reserve Info Military History Page - ## Issue Description
After doing testing for 526 enhancements, it was clear that this page could be consolidated to provide a better user experience for veterans filing disability claims. This ticket captures the design changes we intend to make based upon testing.
---
## Tasks
- [x] Create mockups of the new military service history page that includes reserve information
## Acceptance Criteria
- [x] Have spoken with BE and FE teams to understand tech requirements
- [x] mockups have been created
---
## How to configure this issue
- [ ] **Attached to a Milestone** (when will this be completed?)
- [ ] **Attached to an Epic** (what body of work is this a part of?)
- [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`)
- [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`)
- [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)
|
design
|
enhancement reserve info military history page issue description after doing testing for enhancements it was clear that this page could be consolidated to provide a better user experience for veterans filing disability claims this ticket captures the design changes we intend to make based upon testing tasks create mockups of the new military service history page that includes reserve information acceptance criteria have spoken with be and fe teams to understand tech requirements mockups have been created how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc
| 1
|
552,263
| 16,236,192,877
|
IssuesEvent
|
2021-05-07 01:14:45
|
Sage-Bionetworks/research-benchmarking-technology
|
https://api.github.com/repos/Sage-Bionetworks/research-benchmarking-technology
|
closed
|
Update ROCC dependencies May 2021
|
Priority: High
|
### Repositories
- [x] https://github.com/Sage-Bionetworks/rocc
- [x] https://github.com/Sage-Bionetworks/rocc-schemas
- [x] https://github.com/Sage-Bionetworks/rocc-app
- [x] https://github.com/Sage-Bionetworks/rocc-client-angular
- [x] https://github.com/Sage-Bionetworks/rocc-client-python
- [x] https://github.com/Sage-Bionetworks/rocc-infra
### Additional actions
- Configure repos to require at least one review before merging PR
- Enable auto-merging PRs
- PRs created by dependabot should be notified to the GH team `Sage-Bionetworks/rocc-maitainers`
- ~Configure dependabot to use rbt labels~ (work in progress)
|
1.0
|
Update ROCC dependencies May 2021 - ### Repositories
- [x] https://github.com/Sage-Bionetworks/rocc
- [x] https://github.com/Sage-Bionetworks/rocc-schemas
- [x] https://github.com/Sage-Bionetworks/rocc-app
- [x] https://github.com/Sage-Bionetworks/rocc-client-angular
- [x] https://github.com/Sage-Bionetworks/rocc-client-python
- [x] https://github.com/Sage-Bionetworks/rocc-infra
### Additional actions
- Configure repos to require at least one review before merging PR
- Enable auto-merging PRs
- PRs created by dependabot should be notified to the GH team `Sage-Bionetworks/rocc-maitainers`
- ~Configure dependabot to use rbt labels~ (work in progress)
|
non_design
|
update rocc dependencies may repositories additional actions configure repos to require at least one review before merging pr enable auto merging prs prs created by dependabot should be notified to the gh team sage bionetworks rocc maitainers configure dependabot to use rbt labels work in progress
| 0
|
105,256
| 23,018,095,284
|
IssuesEvent
|
2022-07-22 00:13:22
|
fprime-community/fpp
|
https://api.github.com/repos/fprime-community/fpp
|
closed
|
Generate C++ code for types inside components
|
bug code generation
|
fpp-to-cpp isn't generating code for types declared inside components, e.g.,
```
passive component C { enum E { X } }
```
In this example, fpp-to-cpp should generate a C++ enum `C_E`, not enclosed in any namespace.
- [x] Add a Component visitor to CppWriter to handle this case
- [x] Add unit tests for enums, arrays, and structs
|
1.0
|
Generate C++ code for types inside components - fpp-to-cpp isn't generating code for types declared inside components, e.g.,
```
passive component C { enum E { X } }
```
In this example, fpp-to-cpp should generate a C++ enum `C_E`, not enclosed in any namespace.
- [x] Add a Component visitor to CppWriter to handle this case
- [x] Add unit tests for enums, arrays, and structs
|
non_design
|
generate c code for types inside components fpp to cpp isn t generating code for types declared inside components e g passive component c enum e x in this example fpp to cpp should generate a c enum c e not enclosed in any namespace add a component visitor to cppwriter to handle this case add unit tests for enums arrays and structs
| 0
|
650,576
| 21,409,673,332
|
IssuesEvent
|
2022-04-22 03:32:05
|
lima-vm/lima
|
https://api.github.com/repos/lima-vm/lima
|
closed
|
Reduce the memory to < 4 GiB, when QEMU >= 7.0 && macOS <= 12.3 && CPU == M1
|
priority/high platform/ARM
|
QEMU 7.0 beta is known to cause host kernel panic on M1 (Prox/Max only?) when the guest memory exceeds 4GiB limit, but the host kernel panic is reported to be fixed in macOS 12.4 beta
https://gitlab.com/qemu-project/qemu/-/issues/903#note_911000975
But not all people can upgrade macOS immediately, so probably we should reduce the default memory to 2GiB when QEMU >= 7.0 && macOS <= 12.3 && CPU == M1 .
|
1.0
|
Reduce the memory to < 4 GiB, when QEMU >= 7.0 && macOS <= 12.3 && CPU == M1 - QEMU 7.0 beta is known to cause host kernel panic on M1 (Prox/Max only?) when the guest memory exceeds 4GiB limit, but the host kernel panic is reported to be fixed in macOS 12.4 beta
https://gitlab.com/qemu-project/qemu/-/issues/903#note_911000975
But not all people can upgrade macOS immediately, so probably we should reduce the default memory to 2GiB when QEMU >= 7.0 && macOS <= 12.3 && CPU == M1 .
|
non_design
|
reduce the memory to macos cpu qemu beta is known to cause host kernel panic on prox max only when the guest memory exceeds limit but the host kernel panic is reported to be fixed in macos beta but not all people can upgrade macos immediately so probably we should reduce the default memory to when qemu macos cpu
| 0
|
111,825
| 14,147,981,076
|
IssuesEvent
|
2020-11-10 21:43:56
|
OceanShare/OceanShare-iOS
|
https://api.github.com/repos/OceanShare/OceanShare-iOS
|
closed
|
Gamification
|
Priority: Low Status: Not Assigned Type: Design Type: Production
|
* [ ] save miles in user's data
* [ ] save number of like user's event receive
* [ ] assign special "title" + "ornaments" to the users
|
1.0
|
Gamification - * [ ] save miles in user's data
* [ ] save number of like user's event receive
* [ ] assign special "title" + "ornaments" to the users
|
design
|
gamification save miles in user s data save number of like user s event receive assign special title ornaments to the users
| 1
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.