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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
340,869
| 30,550,422,583
|
IssuesEvent
|
2023-07-20 08:08:40
|
wazuh/wazuh-qa
|
https://api.github.com/repos/wazuh/wazuh-qa
|
closed
|
Vulnerability detector test: Vulnerability scan correlation feeds
|
team/qa test/integration feature/vuln-detector new-development
|
When a vulnerability scan is launched, it is used several sources to decide if a package/system is vulnerable or not. In this case, the NVD and provider feed are used.
The objective of this issue is to test the expected behavior when the provider and NVD feed contradict each other or contain different information.
It is requested to carry out a study on the possible combinations and to develop a testing module for checking the different combinations between provider and NVD feeds.
|
1.0
|
Vulnerability detector test: Vulnerability scan correlation feeds - When a vulnerability scan is launched, it is used several sources to decide if a package/system is vulnerable or not. In this case, the NVD and provider feed are used.
The objective of this issue is to test the expected behavior when the provider and NVD feed contradict each other or contain different information.
It is requested to carry out a study on the possible combinations and to develop a testing module for checking the different combinations between provider and NVD feeds.
|
non_design
|
vulnerability detector test vulnerability scan correlation feeds when a vulnerability scan is launched it is used several sources to decide if a package system is vulnerable or not in this case the nvd and provider feed are used the objective of this issue is to test the expected behavior when the provider and nvd feed contradict each other or contain different information it is requested to carry out a study on the possible combinations and to develop a testing module for checking the different combinations between provider and nvd feeds
| 0
|
98,013
| 12,281,396,211
|
IssuesEvent
|
2020-05-08 15:46:53
|
department-of-veterans-affairs/va.gov-cms
|
https://api.github.com/repos/department-of-veterans-affairs/va.gov-cms
|
opened
|
Show users with acccess on each section page
|
Content governance Design Drupal engineering Enhancement ⭐️ Content ops
|
## User Story or Problem Statement
As an editor of a section, i want to know who has access to a section.
## Acceptance Criteria
On /section/veterans-health-administration/vha-facilities/va-pittsburgh-health-care:
* a list of users assigned to that section is shown
* Links to the ancestor terms with counts for number of assigned users is shown, eg `VHA (10) > VHA Facilities (12) > VISN 4 (1)`
|
1.0
|
Show users with acccess on each section page - ## User Story or Problem Statement
As an editor of a section, i want to know who has access to a section.
## Acceptance Criteria
On /section/veterans-health-administration/vha-facilities/va-pittsburgh-health-care:
* a list of users assigned to that section is shown
* Links to the ancestor terms with counts for number of assigned users is shown, eg `VHA (10) > VHA Facilities (12) > VISN 4 (1)`
|
design
|
show users with acccess on each section page user story or problem statement as an editor of a section i want to know who has access to a section acceptance criteria on section veterans health administration vha facilities va pittsburgh health care a list of users assigned to that section is shown links to the ancestor terms with counts for number of assigned users is shown eg vha vha facilities visn
| 1
|
10,342
| 2,622,145,945
|
IssuesEvent
|
2015-03-04 00:04:07
|
byzhang/i7z
|
https://api.github.com/repos/byzhang/i7z
|
closed
|
>32 core support ?
|
auto-migrated Priority-Medium Type-Defect
|
```
What steps will reproduce the problem?
1.sudo ./i7z
What is the expected output? What do you see instead? If possible do paste
the output
i7z DEBUG: i7z version: svn-r50-(1-1-2011)
i7z DEBUG: Found Intel Processor
i7z DEBUG: Stepping 2
i7z DEBUG: Model f
i7z DEBUG: Family 6
i7z DEBUG: Processor Type 0
i7z DEBUG: Extended Model 2
i7z DEBUG: msr = Model Specific Register
i7z DEBUG: Detected a Xeon MP - 32nm (E7 series)
i7z DEBUG: msr device files exist /dev/cpu/*/msr
i7z DEBUG: You have write permissions to msr device files
i7z: helper_functions.c:669: construct_CPU_Heirarchy_info: Assertion
`it_processor_num < 32' failed.
What version of the product are you using (the download version or the svn
version and which one)? On what operating system?
BTW is it a 32-bit or a 64-bit OS/Kernel?
Current latest version, v 0.27.
64 bit ubuntu
Please provide any additional information below (helpful will be platform
information like number and types of cpus, motherboard and a copy of
/proc/cpuinfo)
Dell R910 poweredge server
4 socket
4 ten-cores processors
40 real cores/ 80 cores hyperthreaded
more /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 47
model name : Intel(R) Xeon(R) CPU E7- 4850 @ 2.00GHz
.....
processor : 79
vendor_id : GenuineIntel
cpu family : 6
model : 47
model name : Intel(R) Xeon(R) CPU E7- 4850 @ 2.00GHz
If the program crashes with a rdmsr or wrmsr error. can you also paste the
output of ls -lt /dev/cpu/*/msr
```
Original issue reported on code.google.com by `gees...@gmail.com` on 6 Oct 2011 at 12:45
|
1.0
|
>32 core support ? - ```
What steps will reproduce the problem?
1.sudo ./i7z
What is the expected output? What do you see instead? If possible do paste
the output
i7z DEBUG: i7z version: svn-r50-(1-1-2011)
i7z DEBUG: Found Intel Processor
i7z DEBUG: Stepping 2
i7z DEBUG: Model f
i7z DEBUG: Family 6
i7z DEBUG: Processor Type 0
i7z DEBUG: Extended Model 2
i7z DEBUG: msr = Model Specific Register
i7z DEBUG: Detected a Xeon MP - 32nm (E7 series)
i7z DEBUG: msr device files exist /dev/cpu/*/msr
i7z DEBUG: You have write permissions to msr device files
i7z: helper_functions.c:669: construct_CPU_Heirarchy_info: Assertion
`it_processor_num < 32' failed.
What version of the product are you using (the download version or the svn
version and which one)? On what operating system?
BTW is it a 32-bit or a 64-bit OS/Kernel?
Current latest version, v 0.27.
64 bit ubuntu
Please provide any additional information below (helpful will be platform
information like number and types of cpus, motherboard and a copy of
/proc/cpuinfo)
Dell R910 poweredge server
4 socket
4 ten-cores processors
40 real cores/ 80 cores hyperthreaded
more /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 47
model name : Intel(R) Xeon(R) CPU E7- 4850 @ 2.00GHz
.....
processor : 79
vendor_id : GenuineIntel
cpu family : 6
model : 47
model name : Intel(R) Xeon(R) CPU E7- 4850 @ 2.00GHz
If the program crashes with a rdmsr or wrmsr error. can you also paste the
output of ls -lt /dev/cpu/*/msr
```
Original issue reported on code.google.com by `gees...@gmail.com` on 6 Oct 2011 at 12:45
|
non_design
|
core support what steps will reproduce the problem sudo what is the expected output what do you see instead if possible do paste the output debug version svn debug found intel processor debug stepping debug model f debug family debug processor type debug extended model debug msr model specific register debug detected a xeon mp series debug msr device files exist dev cpu msr debug you have write permissions to msr device files helper functions c construct cpu heirarchy info assertion it processor num failed what version of the product are you using the download version or the svn version and which one on what operating system btw is it a bit or a bit os kernel current latest version v bit ubuntu please provide any additional information below helpful will be platform information like number and types of cpus motherboard and a copy of proc cpuinfo dell poweredge server socket ten cores processors real cores cores hyperthreaded more proc cpuinfo processor vendor id genuineintel cpu family model model name intel r xeon r cpu processor vendor id genuineintel cpu family model model name intel r xeon r cpu if the program crashes with a rdmsr or wrmsr error can you also paste the output of ls lt dev cpu msr original issue reported on code google com by gees gmail com on oct at
| 0
|
216,073
| 7,301,005,483
|
IssuesEvent
|
2018-02-27 02:35:49
|
medic/medic-webapp
|
https://api.github.com/repos/medic/medic-webapp
|
closed
|
Horticulturalist Web UI drops the upgrading throbber once api has done its part instead of waiting until a new ddoc is ready
|
Priority: 3 - Low Status: 5 - Ready Type: Improvement UI/UX horticulturalist
|
When clicking upgrade we show an upgrade message and a loading throbber, and fire a request off to api to stage the new release for horticulturalist to pick up.
Currently once api returns we drop the throbber and go back to the upgrade page, with no indication of what's going on. However, the upgrade isn't complete until horti picks it up, kills api / sentinel, deploys, and starts api / sentinel again. At which time, we'll automatically reconnect and get the "there is a new version of this software" model.
We should change the code so the message and throbber never get dropped, so that they will stick around until the new version modal appears.
|
1.0
|
Horticulturalist Web UI drops the upgrading throbber once api has done its part instead of waiting until a new ddoc is ready - When clicking upgrade we show an upgrade message and a loading throbber, and fire a request off to api to stage the new release for horticulturalist to pick up.
Currently once api returns we drop the throbber and go back to the upgrade page, with no indication of what's going on. However, the upgrade isn't complete until horti picks it up, kills api / sentinel, deploys, and starts api / sentinel again. At which time, we'll automatically reconnect and get the "there is a new version of this software" model.
We should change the code so the message and throbber never get dropped, so that they will stick around until the new version modal appears.
|
non_design
|
horticulturalist web ui drops the upgrading throbber once api has done its part instead of waiting until a new ddoc is ready when clicking upgrade we show an upgrade message and a loading throbber and fire a request off to api to stage the new release for horticulturalist to pick up currently once api returns we drop the throbber and go back to the upgrade page with no indication of what s going on however the upgrade isn t complete until horti picks it up kills api sentinel deploys and starts api sentinel again at which time we ll automatically reconnect and get the there is a new version of this software model we should change the code so the message and throbber never get dropped so that they will stick around until the new version modal appears
| 0
|
168,306
| 6,368,664,560
|
IssuesEvent
|
2017-08-01 09:47:43
|
daisy/pipeline
|
https://api.github.com/repos/daisy/pipeline
|
closed
|
the data directory of a volatile job is not always deleted if things went wrong
|
1 - Next bug Component-Framework imported Priority-Medium
|
_From [rdeltour@gmail.com](https://code.google.com/u/rdeltour@gmail.com/) on February 20, 2012 16:05:30_
When the job execution failed or the fwk crashed, the data directory of a job is sometimes left on the file system. It should be systematically cleaned after execution, no matter what happens.
_Original issue: http://code.google.com/p/daisy-pipeline/issues/detail?id=149_
|
1.0
|
the data directory of a volatile job is not always deleted if things went wrong - _From [rdeltour@gmail.com](https://code.google.com/u/rdeltour@gmail.com/) on February 20, 2012 16:05:30_
When the job execution failed or the fwk crashed, the data directory of a job is sometimes left on the file system. It should be systematically cleaned after execution, no matter what happens.
_Original issue: http://code.google.com/p/daisy-pipeline/issues/detail?id=149_
|
non_design
|
the data directory of a volatile job is not always deleted if things went wrong from on february when the job execution failed or the fwk crashed the data directory of a job is sometimes left on the file system it should be systematically cleaned after execution no matter what happens original issue
| 0
|
174,492
| 14,484,272,585
|
IssuesEvent
|
2020-12-10 16:08:25
|
fluid-cloudnative/fluid
|
https://api.github.com/repos/fluid-cloudnative/fluid
|
closed
|
[DOC]
|
documentation
|
**Provide a link to that doc page:**
https://github.com/fluid-cloudnative/fluid/blob/master/pkg/utils/kubeclient/exec.go
**What is the defect and your suggestions on improvement:**
类别： 方法注释规范化 位置： pkg/utils/kubeclient/exec.go 内容： 将func ExecCommandInPod上的注释规范化
|
1.0
|
[DOC] - **Provide a link to that doc page:**
https://github.com/fluid-cloudnative/fluid/blob/master/pkg/utils/kubeclient/exec.go
**What is the defect and your suggestions on improvement:**
类别： 方法注释规范化 位置： pkg/utils/kubeclient/exec.go 内容： 将func ExecCommandInPod上的注释规范化
|
non_design
|
provide a link to that doc page what is the defect and your suggestions on improvement 类别： 方法注释规范化 位置： pkg utils kubeclient exec go 内容： 将func execcommandinpod上的注释规范化
| 0
|
92,309
| 3,869,574,898
|
IssuesEvent
|
2016-04-10 17:44:42
|
Microsoft/RTVS
|
https://api.github.com/repos/Microsoft/RTVS
|
closed
|
Some rows in VE are taller than others
|
area:Variable Explorer priority:P1 type:bug
|
E.g. compare `fac` and `fac1` here:
Seems to be due to Excel icon being too tall, and stretching the rows it appears in vertically.
|
1.0
|
Some rows in VE are taller than others - E.g. compare `fac` and `fac1` here:
Seems to be due to Excel icon being too tall, and stretching the rows it appears in vertically.
|
non_design
|
some rows in ve are taller than others e g compare fac and here seems to be due to excel icon being too tall and stretching the rows it appears in vertically
| 0
|
1,377
| 2,741,751,337
|
IssuesEvent
|
2015-04-21 13:14:49
|
OpenFLUID/openfluid
|
https://api.github.com/repos/OpenFLUID/openfluid
|
closed
|
Limit dependencies to boost libraries
|
builder cli devstudio framework
|
Remove any dependencies from wares
Remove built libs dependencies from applications and framework
Limit other dependencies
List used boost classes (run from build dir):
```grep -roh 'boost::[a-z_\-\:]*' ../src/* | sort -n | uniq -c```
Recursively list headers included from a source file (run from _build dir):
```g++ -H ../src/openfluid/ware/PluggableSimulator.hpp -I ../src -I ./src```
|
1.0
|
Limit dependencies to boost libraries - Remove any dependencies from wares
Remove built libs dependencies from applications and framework
Limit other dependencies
List used boost classes (run from build dir):
```grep -roh 'boost::[a-z_\-\:]*' ../src/* | sort -n | uniq -c```
Recursively list headers included from a source file (run from _build dir):
```g++ -H ../src/openfluid/ware/PluggableSimulator.hpp -I ../src -I ./src```
|
non_design
|
limit dependencies to boost libraries remove any dependencies from wares remove built libs dependencies from applications and framework limit other dependencies list used boost classes run from build dir grep roh boost src sort n uniq c recursively list headers included from a source file run from build dir g h src openfluid ware pluggablesimulator hpp i src i src
| 0
|
100,634
| 12,542,001,623
|
IssuesEvent
|
2020-06-05 13:21:10
|
dinsic-pim/tchap-web
|
https://api.github.com/repos/dinsic-pim/tchap-web
|
closed
|
Global : Warn users about losing encryption keys
|
design done feature
|
If a user always log-out after a use, or if his browser is configured with session destroy, the user will lose all his encryption keys and will not be able to see his conversation history.
We want to add two modal and a top bar in order to inform users.
Post-login modal :
Pre-logout modal :
Top bar :
|
1.0
|
Global : Warn users about losing encryption keys - If a user always log-out after a use, or if his browser is configured with session destroy, the user will lose all his encryption keys and will not be able to see his conversation history.
We want to add two modal and a top bar in order to inform users.
Post-login modal :
Pre-logout modal :
Top bar :
|
design
|
global warn users about losing encryption keys if a user always log out after a use or if his browser is configured with session destroy the user will lose all his encryption keys and will not be able to see his conversation history we want to add two modal and a top bar in order to inform users post login modal pre logout modal top bar
| 1
|
96,533
| 12,137,019,058
|
IssuesEvent
|
2020-04-23 15:09:24
|
solex2006/SELIProject
|
https://api.github.com/repos/solex2006/SELIProject
|
opened
|
Changes of context are initiated only by user request
|
1 - Planning Feature Design Notes :notebook: discussion
|
This is a "not-end" requirement. What I want to mean is that this should be considered for any new page you create that Student can access. Also should correct the old pages.
I will use the label **Feature Design Notes** to this cases
***************
Changes of context are **initiated only by user request** or a mechanism is available to turn off such changes.
NOTE
It is possible for more than one change of context to occur simultaneously. For example, clicking on a link which automatically opens a new window is an example of two separate changes of context related to the change in content and to the change in the viewport (window). The change in the content in this case is initiated by user request when they click on the link, but unless the user can be aware that the link will open in a new window then that change of context cannot be regarded as user-initiated.
### Examples
- an "update now" button
Instead of automatically updating the content, the author provides an "Update now" button that requests a refresh of the content.
- An automatic redirection
A user is automatically redirected from an old page to a new page in such a way that he or she never realizes the redirect has occurred.
# Scenario: If the Web page allows automatic updates
- [ ] Providing a mechanism to request an update of the content instead of updating automatically
Examples
Example 1
In HTML, a developer can provide a button or link that allows the user to update the content. For example, on a page with news items located at http://www.example.com/news.jsp
<a href="news.jsp">Update this page</a>
Example 2
In a Web interface for e-mail (Webmail), a developer can provide a button or link to fetch new incoming mails instead of updating automatically.
# Scenario: If automatic redirects are possible
- [ ] Implementing automatic redirects on the server side instead of on the client side
- [ ] Using an instant client-side redirect
# Scenario: If the Web page uses pop-up windows
- [ ] Including pop-up windows using one of the following techniques:
- Using the target attribute to open a new window on user request and indicating this in link text
- Using progressive enhancement to open new windows on user request
# Scenario: If using an onchange event on a select element
- [ ] Using an onchange event on a select element without causing a change of context
# :beetle: Test Procedures
### Providing a mechanism to request an update of the content instead of updating automatically
1. Find mechanisms to update the content (if such a mechanism is present).
2. For each such mechanism, check if it allows the user to request an update.
3. For each such mechanism, check if it can cause an automatic update.
Expected Results: 2 and 3 are true
# :busts_in_silhouette: Benefits
- Individuals who are unable to detect changes of context or may not realize that the context has changed are less likely to become disoriented while navigating a site. For example:
- individuals who are blind or have low vision may have difficulty knowing when a visual context change has occurred, such as a new window popping up. In this case, warning users of context changes in advance minimizes confusion when the user discovers that the back button no longer behaves as expected.
- Some individuals with low vision, with reading and intellectual disabilities, and who have difficulty interpreting visual cues may benefit from additional cues in order to detect changes of context.
- People with certain cognitive limitations do not get confused if automatic redirects are performed by the Web server instead of the browser.
|
1.0
|
Changes of context are initiated only by user request - This is a "not-end" requirement. What I want to mean is that this should be considered for any new page you create that Student can access. Also should correct the old pages.
I will use the label **Feature Design Notes** to this cases
***************
Changes of context are **initiated only by user request** or a mechanism is available to turn off such changes.
NOTE
It is possible for more than one change of context to occur simultaneously. For example, clicking on a link which automatically opens a new window is an example of two separate changes of context related to the change in content and to the change in the viewport (window). The change in the content in this case is initiated by user request when they click on the link, but unless the user can be aware that the link will open in a new window then that change of context cannot be regarded as user-initiated.
### Examples
- an "update now" button
Instead of automatically updating the content, the author provides an "Update now" button that requests a refresh of the content.
- An automatic redirection
A user is automatically redirected from an old page to a new page in such a way that he or she never realizes the redirect has occurred.
# Scenario: If the Web page allows automatic updates
- [ ] Providing a mechanism to request an update of the content instead of updating automatically
Examples
Example 1
In HTML, a developer can provide a button or link that allows the user to update the content. For example, on a page with news items located at http://www.example.com/news.jsp
<a href="news.jsp">Update this page</a>
Example 2
In a Web interface for e-mail (Webmail), a developer can provide a button or link to fetch new incoming mails instead of updating automatically.
# Scenario: If automatic redirects are possible
- [ ] Implementing automatic redirects on the server side instead of on the client side
- [ ] Using an instant client-side redirect
# Scenario: If the Web page uses pop-up windows
- [ ] Including pop-up windows using one of the following techniques:
- Using the target attribute to open a new window on user request and indicating this in link text
- Using progressive enhancement to open new windows on user request
# Scenario: If using an onchange event on a select element
- [ ] Using an onchange event on a select element without causing a change of context
# :beetle: Test Procedures
### Providing a mechanism to request an update of the content instead of updating automatically
1. Find mechanisms to update the content (if such a mechanism is present).
2. For each such mechanism, check if it allows the user to request an update.
3. For each such mechanism, check if it can cause an automatic update.
Expected Results: 2 and 3 are true
# :busts_in_silhouette: Benefits
- Individuals who are unable to detect changes of context or may not realize that the context has changed are less likely to become disoriented while navigating a site. For example:
- individuals who are blind or have low vision may have difficulty knowing when a visual context change has occurred, such as a new window popping up. In this case, warning users of context changes in advance minimizes confusion when the user discovers that the back button no longer behaves as expected.
- Some individuals with low vision, with reading and intellectual disabilities, and who have difficulty interpreting visual cues may benefit from additional cues in order to detect changes of context.
- People with certain cognitive limitations do not get confused if automatic redirects are performed by the Web server instead of the browser.
|
design
|
changes of context are initiated only by user request this is a not end requirement what i want to mean is that this should be considered for any new page you create that student can access also should correct the old pages i will use the label feature design notes to this cases changes of context are initiated only by user request or a mechanism is available to turn off such changes note it is possible for more than one change of context to occur simultaneously for example clicking on a link which automatically opens a new window is an example of two separate changes of context related to the change in content and to the change in the viewport window the change in the content in this case is initiated by user request when they click on the link but unless the user can be aware that the link will open in a new window then that change of context cannot be regarded as user initiated examples an update now button instead of automatically updating the content the author provides an update now button that requests a refresh of the content an automatic redirection a user is automatically redirected from an old page to a new page in such a way that he or she never realizes the redirect has occurred scenario if the web page allows automatic updates providing a mechanism to request an update of the content instead of updating automatically examples example in html a developer can provide a button or link that allows the user to update the content for example on a page with news items located at update this page example in a web interface for e mail webmail a developer can provide a button or link to fetch new incoming mails instead of updating automatically scenario if automatic redirects are possible implementing automatic redirects on the server side instead of on the client side using an instant client side redirect scenario if the web page uses pop up windows including pop up windows using one of the following techniques using the target attribute to open a new window on user request and indicating this in link text using progressive enhancement to open new windows on user request scenario if using an onchange event on a select element using an onchange event on a select element without causing a change of context beetle test procedures providing a mechanism to request an update of the content instead of updating automatically find mechanisms to update the content if such a mechanism is present for each such mechanism check if it allows the user to request an update for each such mechanism check if it can cause an automatic update expected results and are true busts in silhouette benefits individuals who are unable to detect changes of context or may not realize that the context has changed are less likely to become disoriented while navigating a site for example individuals who are blind or have low vision may have difficulty knowing when a visual context change has occurred such as a new window popping up in this case warning users of context changes in advance minimizes confusion when the user discovers that the back button no longer behaves as expected some individuals with low vision with reading and intellectual disabilities and who have difficulty interpreting visual cues may benefit from additional cues in order to detect changes of context people with certain cognitive limitations do not get confused if automatic redirects are performed by the web server instead of the browser
| 1
|
88,718
| 11,138,719,403
|
IssuesEvent
|
2019-12-20 23:32:48
|
ParabolInc/action
|
https://api.github.com/repos/ParabolInc/action
|
opened
|
Lo-fi concepts for upgrading notes/comments to other objects
|
design
|
See the background [here](#3391) and [here](https://github.com/ParabolInc/action/issues/3394#issuecomment-566770853)
### Acceptance Criteria
Sketches, concepts showing:
- optional, clever, user-friendly ways to upgrade a note or comment to another thing (e.g. reflection, task, agenda item, etc.)
- we may constrain what type of upgrades can be made by the UX of any given thread (e.g. comments can only become tasks in a Retro discussion thread)
- ideas on how to validate
- consider how to reply to an object or thread on an object (e.g. start a thread on a task)
- note the efforts of #3334 (discussion threads) and #3344 (1:1 meetings)
### Estimated Effort
- 10.5 points ([see CONTRIBUTING.md](https://github.com/ParabolInc/action/blob/master/CONTRIBUTING.md#points-and-sizes))
|
1.0
|
Lo-fi concepts for upgrading notes/comments to other objects - See the background [here](#3391) and [here](https://github.com/ParabolInc/action/issues/3394#issuecomment-566770853)
### Acceptance Criteria
Sketches, concepts showing:
- optional, clever, user-friendly ways to upgrade a note or comment to another thing (e.g. reflection, task, agenda item, etc.)
- we may constrain what type of upgrades can be made by the UX of any given thread (e.g. comments can only become tasks in a Retro discussion thread)
- ideas on how to validate
- consider how to reply to an object or thread on an object (e.g. start a thread on a task)
- note the efforts of #3334 (discussion threads) and #3344 (1:1 meetings)
### Estimated Effort
- 10.5 points ([see CONTRIBUTING.md](https://github.com/ParabolInc/action/blob/master/CONTRIBUTING.md#points-and-sizes))
|
design
|
lo fi concepts for upgrading notes comments to other objects see the background and acceptance criteria sketches concepts showing optional clever user friendly ways to upgrade a note or comment to another thing e g reflection task agenda item etc we may constrain what type of upgrades can be made by the ux of any given thread e g comments can only become tasks in a retro discussion thread ideas on how to validate consider how to reply to an object or thread on an object e g start a thread on a task note the efforts of discussion threads and meetings estimated effort points
| 1
|
93,028
| 11,733,775,211
|
IssuesEvent
|
2020-03-11 07:58:16
|
Telenav/osrm-backend
|
https://api.github.com/repos/Telenav/osrm-backend
|
closed
|
Historical Speed RPC Protocol Design
|
Design InProgress
|
As mentioned in https://github.com/Telenav/osrm-backend/issues/150, we're going to support historical speed in `osrm-ranking`. This issue is the first sub task for https://github.com/Telenav/osrm-backend/issues/150.
Some comments/requirements for the design:
- Same with live traffic, historical speed could be provided by `traffic-proxy` via RPC also.
- Historical speed data will have two parts:
- pattern: `pattern_id, speed_1, speed_2, ..., speed_n`
- let's say if 15 minutes per speed, the `speed_1` will be the speed on clock `00:00`, `speed_2: 00:15`, etc. In which case `n` will be `96`.
- mapping from way to pattern: `way_id, sunday_pattern_id, monday_pattern_id, ..., saturday_pattern_id`
- `way_id > 0` means forward and `way_id < 0` means backward.
- When collect the speeds data for a week, normally the week should be local time week, so it might be better to say the clock `00:00`, `00:15`, etc are also local time clock. Then we have to know each `way`'s **timezone** and **daylight saving time** since most of time **we'll query the speeds by UTC clock**.
- A better approach will be also append **offset** of UTC which has calculated by timezone and daylight saving time already.
- E.g. new mapping from way to pattern: `way_id, sunday_pattern_id, monday_pattern_id, ..., saturday_pattern_id, offset, timezone, daylight_saving_time`
- The advantage of this approach is that whatever who want to query the speeds with a UTC clock, they'll get same value since `traffic-proxy` provides unified time conversion.
- The disadvantage of this approach is that the `traffic-proxy` have to access map data to get `timezone` and `daylight saving time`, which currently it doesn't.
- Another approach is that we setup another microservice to have a mapping `way_id, timezone, daylight_saving_time`, in contrast the `traffic-proxy` only provides the historical speed patterns and mappings from way to pattern.
- The advatange of this approach is that `traffic-proxy` will be simpler.
- The disadvantage of this approach is that uses have to combine them together and implements the time conversion to get correct speeds.
- With this historcal speed pattern definition, we possible to query historical speed for a `way_id` on forward/backward at a each clock in a week.
- size estimate
- let's say if 15 minutes per speed, and each speed stores by `uint8`, `pattern_id` stores by `uint32`, then each pattern will needs **4 + 96*1=100** bytes.
- each mapping from way to pattern will need `8` bytes for `wayid` and `7*4=28` bytes for `pattern_id`s, so each value will need **36** bytes.
- let's say if North America totally have 20 millions ways(both direction) have historical speed, and totally have 10 millions patterns, then we'll need totally **20,000,000 * 2 * 36 + 10,000,000 * 100 = 2.44 GB** to store them in memory, which is acceptable on cloud side.
- In practice, we still possible to compress the patterns because many of them are the same or very similar, which means the size will much smaller.
|
1.0
|
Historical Speed RPC Protocol Design - As mentioned in https://github.com/Telenav/osrm-backend/issues/150, we're going to support historical speed in `osrm-ranking`. This issue is the first sub task for https://github.com/Telenav/osrm-backend/issues/150.
Some comments/requirements for the design:
- Same with live traffic, historical speed could be provided by `traffic-proxy` via RPC also.
- Historical speed data will have two parts:
- pattern: `pattern_id, speed_1, speed_2, ..., speed_n`
- let's say if 15 minutes per speed, the `speed_1` will be the speed on clock `00:00`, `speed_2: 00:15`, etc. In which case `n` will be `96`.
- mapping from way to pattern: `way_id, sunday_pattern_id, monday_pattern_id, ..., saturday_pattern_id`
- `way_id > 0` means forward and `way_id < 0` means backward.
- When collect the speeds data for a week, normally the week should be local time week, so it might be better to say the clock `00:00`, `00:15`, etc are also local time clock. Then we have to know each `way`'s **timezone** and **daylight saving time** since most of time **we'll query the speeds by UTC clock**.
- A better approach will be also append **offset** of UTC which has calculated by timezone and daylight saving time already.
- E.g. new mapping from way to pattern: `way_id, sunday_pattern_id, monday_pattern_id, ..., saturday_pattern_id, offset, timezone, daylight_saving_time`
- The advantage of this approach is that whatever who want to query the speeds with a UTC clock, they'll get same value since `traffic-proxy` provides unified time conversion.
- The disadvantage of this approach is that the `traffic-proxy` have to access map data to get `timezone` and `daylight saving time`, which currently it doesn't.
- Another approach is that we setup another microservice to have a mapping `way_id, timezone, daylight_saving_time`, in contrast the `traffic-proxy` only provides the historical speed patterns and mappings from way to pattern.
- The advatange of this approach is that `traffic-proxy` will be simpler.
- The disadvantage of this approach is that uses have to combine them together and implements the time conversion to get correct speeds.
- With this historcal speed pattern definition, we possible to query historical speed for a `way_id` on forward/backward at a each clock in a week.
- size estimate
- let's say if 15 minutes per speed, and each speed stores by `uint8`, `pattern_id` stores by `uint32`, then each pattern will needs **4 + 96*1=100** bytes.
- each mapping from way to pattern will need `8` bytes for `wayid` and `7*4=28` bytes for `pattern_id`s, so each value will need **36** bytes.
- let's say if North America totally have 20 millions ways(both direction) have historical speed, and totally have 10 millions patterns, then we'll need totally **20,000,000 * 2 * 36 + 10,000,000 * 100 = 2.44 GB** to store them in memory, which is acceptable on cloud side.
- In practice, we still possible to compress the patterns because many of them are the same or very similar, which means the size will much smaller.
|
design
|
historical speed rpc protocol design as mentioned in we re going to support historical speed in osrm ranking this issue is the first sub task for some comments requirements for the design same with live traffic historical speed could be provided by traffic proxy via rpc also historical speed data will have two parts pattern pattern id speed speed speed n let s say if minutes per speed the speed will be the speed on clock speed etc in which case n will be mapping from way to pattern way id sunday pattern id monday pattern id saturday pattern id way id means forward and way id means backward when collect the speeds data for a week normally the week should be local time week so it might be better to say the clock etc are also local time clock then we have to know each way s timezone and daylight saving time since most of time we ll query the speeds by utc clock a better approach will be also append offset of utc which has calculated by timezone and daylight saving time already e g new mapping from way to pattern way id sunday pattern id monday pattern id saturday pattern id offset timezone daylight saving time the advantage of this approach is that whatever who want to query the speeds with a utc clock they ll get same value since traffic proxy provides unified time conversion the disadvantage of this approach is that the traffic proxy have to access map data to get timezone and daylight saving time which currently it doesn t another approach is that we setup another microservice to have a mapping way id timezone daylight saving time in contrast the traffic proxy only provides the historical speed patterns and mappings from way to pattern the advatange of this approach is that traffic proxy will be simpler the disadvantage of this approach is that uses have to combine them together and implements the time conversion to get correct speeds with this historcal speed pattern definition we possible to query historical speed for a way id on forward backward at a each clock in a week size estimate let s say if minutes per speed and each speed stores by pattern id stores by then each pattern will needs bytes each mapping from way to pattern will need bytes for wayid and bytes for pattern id s so each value will need bytes let s say if north america totally have millions ways both direction have historical speed and totally have millions patterns then we ll need totally gb to store them in memory which is acceptable on cloud side in practice we still possible to compress the patterns because many of them are the same or very similar which means the size will much smaller
| 1
|
70,779
| 8,579,716,373
|
IssuesEvent
|
2018-11-13 09:56:20
|
julimage/LausitzPropan
|
https://api.github.com/repos/julimage/LausitzPropan
|
opened
|
page: Flaschengas
|
content design
|
Bilder in Sidebar:
Typ A = 11kg Treibgas (als letzte Position anzeigen)
Typ B = entfernen
Typ C = 33 kg Propangas
Typ D = 5 kg Propangas
Noch dazu fügen: 11kg (Mitte des Fotos mit allen Flaschen) und 19 kg (oben links im Gesamtbild)
* Auch das Bild mit allen Flaschen anzeigen.
|
1.0
|
page: Flaschengas - Bilder in Sidebar:
Typ A = 11kg Treibgas (als letzte Position anzeigen)
Typ B = entfernen
Typ C = 33 kg Propangas
Typ D = 5 kg Propangas
Noch dazu fügen: 11kg (Mitte des Fotos mit allen Flaschen) und 19 kg (oben links im Gesamtbild)
* Auch das Bild mit allen Flaschen anzeigen.
|
design
|
page flaschengas bilder in sidebar typ a treibgas als letzte position anzeigen typ b entfernen typ c kg propangas typ d kg propangas noch dazu fügen mitte des fotos mit allen flaschen und kg oben links im gesamtbild auch das bild mit allen flaschen anzeigen
| 1
|
79,470
| 9,906,349,018
|
IssuesEvent
|
2019-06-27 13:41:30
|
unitsofmeasurement/indriya
|
https://api.github.com/repos/unitsofmeasurement/indriya
|
closed
|
Move AbstractConverter to function
|
design task
|
I know this is a slightly bigger step, but as a new redefined `MultiplyConverter` interface also got defined (in place of the earlier class) in the function package, and `AbstractUnitFormat` etc. are in the format package, it is consequent here.
|
1.0
|
Move AbstractConverter to function - I know this is a slightly bigger step, but as a new redefined `MultiplyConverter` interface also got defined (in place of the earlier class) in the function package, and `AbstractUnitFormat` etc. are in the format package, it is consequent here.
|
design
|
move abstractconverter to function i know this is a slightly bigger step but as a new redefined multiplyconverter interface also got defined in place of the earlier class in the function package and abstractunitformat etc are in the format package it is consequent here
| 1
|
63,568
| 7,725,874,543
|
IssuesEvent
|
2018-05-24 19:22:02
|
infor-design/design-system
|
https://api.github.com/repos/infor-design/design-system
|
closed
|
UI Audit
|
for: design
|
Collect UI of different product teams for examples research purposes
Note:
UI uplift audit until may release
Actual UI uplift post may-sept
Going to be working with HCM to implement
- [x] Write and present Charter to Nunz to get sign off
**Notes:** Show nunz how the design tokens work and quickly demonstrate how our UI can change
The UI uplift shouldn’t be drastically different from xi
**Given adoption problems we already have we suggest a soho iteration
Once adoption rate of design tokens is at 50%?? We can look at a more major UI uplift
change
- [x] Kayiu will reach out to Mallory asking for screens to look at navigation patterns
- [x] Kayiu reaching out to teams to gather screens
- [x] Compile visual examples of UI problems
- [x] Gather UI pain points and findings from survey
- [x] Kayiu to take screenshots from product teams and review common nav and UI patterns
- Kayiu to take what enablement has started with mongoose and the forms (how to put together a form in the right way--mike is working on something like that) -- Took this item off because there's a ticket around Form layouts: https://github.com/infor-design/design-system/issues/124
|
1.0
|
UI Audit - Collect UI of different product teams for examples research purposes
Note:
UI uplift audit until may release
Actual UI uplift post may-sept
Going to be working with HCM to implement
- [x] Write and present Charter to Nunz to get sign off
**Notes:** Show nunz how the design tokens work and quickly demonstrate how our UI can change
The UI uplift shouldn’t be drastically different from xi
**Given adoption problems we already have we suggest a soho iteration
Once adoption rate of design tokens is at 50%?? We can look at a more major UI uplift
change
- [x] Kayiu will reach out to Mallory asking for screens to look at navigation patterns
- [x] Kayiu reaching out to teams to gather screens
- [x] Compile visual examples of UI problems
- [x] Gather UI pain points and findings from survey
- [x] Kayiu to take screenshots from product teams and review common nav and UI patterns
- Kayiu to take what enablement has started with mongoose and the forms (how to put together a form in the right way--mike is working on something like that) -- Took this item off because there's a ticket around Form layouts: https://github.com/infor-design/design-system/issues/124
|
design
|
ui audit collect ui of different product teams for examples research purposes note ui uplift audit until may release actual ui uplift post may sept going to be working with hcm to implement write and present charter to nunz to get sign off notes show nunz how the design tokens work and quickly demonstrate how our ui can change the ui uplift shouldn’t be drastically different from xi given adoption problems we already have we suggest a soho iteration once adoption rate of design tokens is at we can look at a more major ui uplift change kayiu will reach out to mallory asking for screens to look at navigation patterns kayiu reaching out to teams to gather screens compile visual examples of ui problems gather ui pain points and findings from survey kayiu to take screenshots from product teams and review common nav and ui patterns kayiu to take what enablement has started with mongoose and the forms how to put together a form in the right way mike is working on something like that took this item off because there s a ticket around form layouts
| 1
|
139,697
| 31,760,332,413
|
IssuesEvent
|
2023-09-12 04:19:10
|
dotnet/runtime
|
https://api.github.com/repos/dotnet/runtime
|
closed
|
JIT: "Mismatch in align instruction" in superpmi-replay
|
area-CodeGen-coreclr blocking-clean-ci-optional in-pr
|
superpmi-replay seems to be failing with "Mismatch in align instruction" when run with JitStressRegs=3:
```scala
[00:26:08] Mismatch in align instruction.
[00:26:08] Containing IG: IG117
[00:26:08] loopHeadPredIG: IG117
[00:26:08] loopHeadIG: IG118
[00:26:08] igInLoop: IG121
[00:26:08] igInLoop->backEdge: IG119
[00:26:08] igInLoop has align instruction for : IG122
[00:26:08] Loop:
[00:26:08] IG118
[00:26:08] IG119
[00:26:08] IG120
[00:26:08] IG121
[00:26:08] IG122
[00:26:08] IG123
[00:26:08] IG124
[00:26:08] IG125
[00:26:08] IG126
[00:26:08] IG127
[00:26:08] IG128
[00:26:08] IG129
[00:26:08] IG130
[00:26:08] IG131
[00:26:08] IG132
[00:26:08] IG133
[00:26:08] IG134
[00:26:08] IG135
[00:26:08] IG136
[00:26:08] IG137
[00:26:08] IG138
[00:26:08] IG139
[00:26:08] IG140
[00:26:08] IG141
[00:26:08] IG142
[00:26:08] IG143
[00:26:08] IG144
[00:26:08] IG145
[00:26:08] IG146
[00:26:08] IG147
[00:26:08] IG148
[00:26:08] IG149
[00:26:08] IG150
[00:26:08] IG151
[00:26:08] IG152
[00:26:08] IG153
[00:26:08] IG154
[00:26:08] IG155
[00:26:08] IG156
[00:26:08] IG157
[00:26:08] IG158
[00:26:08] IG159
[00:26:08] IG160
[00:26:08] IG161
[00:26:08] IG162
[00:26:08] IG163
[00:26:08] IG164
[00:26:08] IG165
[00:26:08] IG166
[00:26:08] IG167
[00:26:08] IG168
[00:26:08] IG169
[00:26:08] IG170
[00:26:08] IG171
[00:26:08] IG172
[00:26:08] IG173
[00:26:08] IG174
[00:26:08] IG175
[00:26:08] IG176
[00:26:08] IG177
[00:26:08] IG178
[00:26:08] IG179
[00:26:08] IG180
[00:26:08] IG181
[00:26:08] IG182
[00:26:08] IG183
[00:26:08] IG184
[00:26:08] IG185
[00:26:08] IG186
[00:26:08] IG187
[00:26:08] IG188
[00:26:08] IG189
[00:26:08] IG190
[00:26:08] IG191
[00:26:08] IG192
[00:26:08] IG193
[00:26:08] IG194
[00:26:08] IG195
[00:26:08] IG196
[00:26:08] IG197
[00:26:08] IG198
[00:26:08] IG199
[00:26:08] IG200
[00:26:08] IG201
[00:26:08] IG202
[00:26:08] IG203
[00:26:08] IG204
[00:26:08] IG205
[00:26:08] IG206
[00:26:08] IG207
[00:26:08] IG208
[00:26:08] IG209
[00:26:08] IG210
[00:26:08] IG211
[00:26:08] IG212
[00:26:08] IG213
[00:26:08] IG214
[00:26:08] IG215
[00:26:08] IG216
[00:26:08] ISSUE: <ASSERT> #530064 D:\a\_work\1\s\src\coreclr\jit\emit.cpp (5883) - Assertion failed 'false' in 'System.Numerics.BigIntegerCalculator:PowCore(System.Span`1[uint],int,System.ReadOnlySpan`1[uint],System.ReadOnlySpan`1[uint],System.Span`1[uint],System.Span`1[uint])' during 'Generate code' (IL size 511; hash 0xd0657e4f; Tier1)
[00:26:08]
```
Console log: https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-91827-merge-6e8d1e4418334afa89/windows-x64-2/1/console.c2bbff16.log?helixlogtype=result
cc @kunalspathak
|
1.0
|
JIT: "Mismatch in align instruction" in superpmi-replay - superpmi-replay seems to be failing with "Mismatch in align instruction" when run with JitStressRegs=3:
```scala
[00:26:08] Mismatch in align instruction.
[00:26:08] Containing IG: IG117
[00:26:08] loopHeadPredIG: IG117
[00:26:08] loopHeadIG: IG118
[00:26:08] igInLoop: IG121
[00:26:08] igInLoop->backEdge: IG119
[00:26:08] igInLoop has align instruction for : IG122
[00:26:08] Loop:
[00:26:08] IG118
[00:26:08] IG119
[00:26:08] IG120
[00:26:08] IG121
[00:26:08] IG122
[00:26:08] IG123
[00:26:08] IG124
[00:26:08] IG125
[00:26:08] IG126
[00:26:08] IG127
[00:26:08] IG128
[00:26:08] IG129
[00:26:08] IG130
[00:26:08] IG131
[00:26:08] IG132
[00:26:08] IG133
[00:26:08] IG134
[00:26:08] IG135
[00:26:08] IG136
[00:26:08] IG137
[00:26:08] IG138
[00:26:08] IG139
[00:26:08] IG140
[00:26:08] IG141
[00:26:08] IG142
[00:26:08] IG143
[00:26:08] IG144
[00:26:08] IG145
[00:26:08] IG146
[00:26:08] IG147
[00:26:08] IG148
[00:26:08] IG149
[00:26:08] IG150
[00:26:08] IG151
[00:26:08] IG152
[00:26:08] IG153
[00:26:08] IG154
[00:26:08] IG155
[00:26:08] IG156
[00:26:08] IG157
[00:26:08] IG158
[00:26:08] IG159
[00:26:08] IG160
[00:26:08] IG161
[00:26:08] IG162
[00:26:08] IG163
[00:26:08] IG164
[00:26:08] IG165
[00:26:08] IG166
[00:26:08] IG167
[00:26:08] IG168
[00:26:08] IG169
[00:26:08] IG170
[00:26:08] IG171
[00:26:08] IG172
[00:26:08] IG173
[00:26:08] IG174
[00:26:08] IG175
[00:26:08] IG176
[00:26:08] IG177
[00:26:08] IG178
[00:26:08] IG179
[00:26:08] IG180
[00:26:08] IG181
[00:26:08] IG182
[00:26:08] IG183
[00:26:08] IG184
[00:26:08] IG185
[00:26:08] IG186
[00:26:08] IG187
[00:26:08] IG188
[00:26:08] IG189
[00:26:08] IG190
[00:26:08] IG191
[00:26:08] IG192
[00:26:08] IG193
[00:26:08] IG194
[00:26:08] IG195
[00:26:08] IG196
[00:26:08] IG197
[00:26:08] IG198
[00:26:08] IG199
[00:26:08] IG200
[00:26:08] IG201
[00:26:08] IG202
[00:26:08] IG203
[00:26:08] IG204
[00:26:08] IG205
[00:26:08] IG206
[00:26:08] IG207
[00:26:08] IG208
[00:26:08] IG209
[00:26:08] IG210
[00:26:08] IG211
[00:26:08] IG212
[00:26:08] IG213
[00:26:08] IG214
[00:26:08] IG215
[00:26:08] IG216
[00:26:08] ISSUE: <ASSERT> #530064 D:\a\_work\1\s\src\coreclr\jit\emit.cpp (5883) - Assertion failed 'false' in 'System.Numerics.BigIntegerCalculator:PowCore(System.Span`1[uint],int,System.ReadOnlySpan`1[uint],System.ReadOnlySpan`1[uint],System.Span`1[uint],System.Span`1[uint])' during 'Generate code' (IL size 511; hash 0xd0657e4f; Tier1)
[00:26:08]
```
Console log: https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-91827-merge-6e8d1e4418334afa89/windows-x64-2/1/console.c2bbff16.log?helixlogtype=result
cc @kunalspathak
|
non_design
|
jit mismatch in align instruction in superpmi replay superpmi replay seems to be failing with mismatch in align instruction when run with jitstressregs scala mismatch in align instruction containing ig loopheadpredig loopheadig iginloop iginloop backedge iginloop has align instruction for loop issue d a work s src coreclr jit emit cpp assertion failed false in system numerics bigintegercalculator powcore system span int system readonlyspan system readonlyspan system span system span during generate code il size hash console log cc kunalspathak
| 0
|
622,991
| 19,659,961,216
|
IssuesEvent
|
2022-01-10 16:04:59
|
PardeeCenterDU/IFs-Issues-Tracking
|
https://api.github.com/repos/PardeeCenterDU/IFs-Issues-Tracking
|
opened
|
Check if we have better data for CAIDSHARE
|
Priority 2 Modeling - Economic Module
|
DATAECON.bas
RedetermineEcoBase:
'jrs 2020/08/19 removed temporarily while we get better data
'Call RegAvgOneDim("CAIDSHARE", CGDP(), aidlp())
|
1.0
|
Check if we have better data for CAIDSHARE - DATAECON.bas
RedetermineEcoBase:
'jrs 2020/08/19 removed temporarily while we get better data
'Call RegAvgOneDim("CAIDSHARE", CGDP(), aidlp())
|
non_design
|
check if we have better data for caidshare dataecon bas redetermineecobase jrs removed temporarily while we get better data call regavgonedim caidshare cgdp aidlp
| 0
|
111,375
| 14,073,039,327
|
IssuesEvent
|
2020-11-04 03:34:40
|
hackforla/food-oasis
|
https://api.github.com/repos/hackforla/food-oasis
|
closed
|
Create Volunteer Information Page
|
design: copywriting design: ui/ux dev dev: front-end
|
### Overview
We need to have a volunteer information page that provides an overview of FOLA, how volunteers help the project, when volunteer sessions are, etc. The link to the page should live in the hamburger menu.
### Action Items
- [ ] Write copy for volunteer information - should include:
- Text for button in hamburger menu - e.g. "Get Involved", "About FOLA", etc.
- Overview of FOLA & what the platform aims to accomplish
- Overview of volunteer contributions
- Instructions on how to sign up to be a volunteer
- Information on training sessions / upcoming volunteer sessions
- [ ] Create design & wireframes for page
- [ ] Include "REGISTER" CTA on page
- [ ] Include "DONATE" CTA on page --> should link to existing [Hack for LA donation URL](https://donorbox.org/hackforla)
- [ ] Create link to page in hamburger menu
- [ ] Code site & publish
### Questions
- [ ] How specific do dates for volunteer sessions have to be?
- [ ] Is it possible for users to sign up for specific volunteer sessions?
- [ ] If we include specific dates for volunteer sessions, how can we update the dates?
### Resources
[Existing Zoom Registration Link](https://us02web.zoom.us/meeting/register/tZErcOGqrDwtHddOYFkVPcX0Qta9GmyuUbfA)
[Existing FOLA "About" Page](https://foodoasis.la/about/)
|
2.0
|
Create Volunteer Information Page - ### Overview
We need to have a volunteer information page that provides an overview of FOLA, how volunteers help the project, when volunteer sessions are, etc. The link to the page should live in the hamburger menu.
### Action Items
- [ ] Write copy for volunteer information - should include:
- Text for button in hamburger menu - e.g. "Get Involved", "About FOLA", etc.
- Overview of FOLA & what the platform aims to accomplish
- Overview of volunteer contributions
- Instructions on how to sign up to be a volunteer
- Information on training sessions / upcoming volunteer sessions
- [ ] Create design & wireframes for page
- [ ] Include "REGISTER" CTA on page
- [ ] Include "DONATE" CTA on page --> should link to existing [Hack for LA donation URL](https://donorbox.org/hackforla)
- [ ] Create link to page in hamburger menu
- [ ] Code site & publish
### Questions
- [ ] How specific do dates for volunteer sessions have to be?
- [ ] Is it possible for users to sign up for specific volunteer sessions?
- [ ] If we include specific dates for volunteer sessions, how can we update the dates?
### Resources
[Existing Zoom Registration Link](https://us02web.zoom.us/meeting/register/tZErcOGqrDwtHddOYFkVPcX0Qta9GmyuUbfA)
[Existing FOLA "About" Page](https://foodoasis.la/about/)
|
design
|
create volunteer information page overview we need to have a volunteer information page that provides an overview of fola how volunteers help the project when volunteer sessions are etc the link to the page should live in the hamburger menu action items write copy for volunteer information should include text for button in hamburger menu e g get involved about fola etc overview of fola what the platform aims to accomplish overview of volunteer contributions instructions on how to sign up to be a volunteer information on training sessions upcoming volunteer sessions create design wireframes for page include register cta on page include donate cta on page should link to existing create link to page in hamburger menu code site publish questions how specific do dates for volunteer sessions have to be is it possible for users to sign up for specific volunteer sessions if we include specific dates for volunteer sessions how can we update the dates resources
| 1
|
395,473
| 27,070,573,393
|
IssuesEvent
|
2023-02-14 06:22:04
|
rawsashimi1604/ICT2106_P2_Project
|
https://api.github.com/repos/rawsashimi1604/ICT2106_P2_Project
|
closed
|
2.2 Functional Requirements
|
documentation
|
Todo:
For the below 5 user features:
- The system should be able to generate various graphs based on energy usage/activity.
- Users can set energy usage/spending limits and threshold.
- The user can choose to filter between the types of devices for comparison.
- The system should be able to log device activity and energy usage.
- Users should be able to compare energy usage between the devices at daily or weekly level.
1) Explain the purpose of the feature
2) State processes involve
3) State affected part and modules that the user features is working on
Deadline: 11 Feb 2023, 12pm
|
1.0
|
2.2 Functional Requirements - Todo:
For the below 5 user features:
- The system should be able to generate various graphs based on energy usage/activity.
- Users can set energy usage/spending limits and threshold.
- The user can choose to filter between the types of devices for comparison.
- The system should be able to log device activity and energy usage.
- Users should be able to compare energy usage between the devices at daily or weekly level.
1) Explain the purpose of the feature
2) State processes involve
3) State affected part and modules that the user features is working on
Deadline: 11 Feb 2023, 12pm
|
non_design
|
functional requirements todo for the below user features the system should be able to generate various graphs based on energy usage activity users can set energy usage spending limits and threshold the user can choose to filter between the types of devices for comparison the system should be able to log device activity and energy usage users should be able to compare energy usage between the devices at daily or weekly level explain the purpose of the feature state processes involve state affected part and modules that the user features is working on deadline feb
| 0
|
200,183
| 22,739,484,765
|
IssuesEvent
|
2022-07-07 01:18:28
|
ConnectionMaster/upload-release-asset
|
https://api.github.com/repos/ConnectionMaster/upload-release-asset
|
opened
|
CVE-2021-44906 (Medium) detected in minimist-0.0.8.tgz, minimist-1.2.0.tgz
|
security vulnerability
|
## CVE-2021-44906 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>minimist-0.0.8.tgz</b>, <b>minimist-1.2.0.tgz</b></p></summary>
<p>
<details><summary><b>minimist-0.0.8.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- eslint-5.16.0.tgz (Root Library)
- mkdirp-0.5.1.tgz
- :x: **minimist-0.0.8.tgz** (Vulnerable Library)
</details>
<details><summary><b>minimist-1.2.0.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/@cnakazawa/watch/node_modules/minimist/package.json,/node_modules/sane/node_modules/minimist/package.json,/node_modules/json5/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- jest-24.9.0.tgz (Root Library)
- jest-cli-24.9.0.tgz
- jest-config-24.9.0.tgz
- core-7.6.2.tgz
- json5-2.1.0.tgz
- :x: **minimist-1.2.0.tgz** (Vulnerable Library)
</details>
<p>Found in base branch: <b>main</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>
Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
<p>Publish Date: 2022-03-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44906>CVE-2021-44906</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.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-03-17</p>
<p>Fix Resolution (minimist): 1.2.6</p>
<p>Direct dependency fix Resolution (eslint): 7.15.0</p><p>Fix Resolution (minimist): 1.2.6</p>
<p>Direct dependency fix Resolution (jest): 27.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2021-44906 (Medium) detected in minimist-0.0.8.tgz, minimist-1.2.0.tgz - ## CVE-2021-44906 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>minimist-0.0.8.tgz</b>, <b>minimist-1.2.0.tgz</b></p></summary>
<p>
<details><summary><b>minimist-0.0.8.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- eslint-5.16.0.tgz (Root Library)
- mkdirp-0.5.1.tgz
- :x: **minimist-0.0.8.tgz** (Vulnerable Library)
</details>
<details><summary><b>minimist-1.2.0.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/@cnakazawa/watch/node_modules/minimist/package.json,/node_modules/sane/node_modules/minimist/package.json,/node_modules/json5/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- jest-24.9.0.tgz (Root Library)
- jest-cli-24.9.0.tgz
- jest-config-24.9.0.tgz
- core-7.6.2.tgz
- json5-2.1.0.tgz
- :x: **minimist-1.2.0.tgz** (Vulnerable Library)
</details>
<p>Found in base branch: <b>main</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>
Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
<p>Publish Date: 2022-03-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44906>CVE-2021-44906</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.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-03-17</p>
<p>Fix Resolution (minimist): 1.2.6</p>
<p>Direct dependency fix Resolution (eslint): 7.15.0</p><p>Fix Resolution (minimist): 1.2.6</p>
<p>Direct dependency fix Resolution (jest): 27.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_design
|
cve medium detected in minimist tgz minimist tgz cve medium severity vulnerability vulnerable libraries minimist tgz minimist tgz minimist tgz parse argument options library home page a href path to dependency file package json path to vulnerable library node modules minimist package json dependency hierarchy eslint tgz root library mkdirp tgz x minimist tgz vulnerable library minimist tgz parse argument options library home page a href path to dependency file package json path to vulnerable library node modules cnakazawa watch node modules minimist package json node modules sane node modules minimist package json node modules node modules minimist package json dependency hierarchy jest tgz root library jest cli tgz jest config tgz core tgz tgz x minimist tgz vulnerable library found in base branch main vulnerability details minimist is vulnerable to prototype pollution via file index js function setkey lines publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version release date fix resolution minimist direct dependency fix resolution eslint fix resolution minimist direct dependency fix resolution jest step up your open source security game with mend
| 0
|
20,984
| 3,441,863,512
|
IssuesEvent
|
2015-12-14 20:12:14
|
wdg/blacktree-secrets
|
https://api.github.com/repos/wdg/blacktree-secrets
|
closed
|
can't "show full list"
|
auto-migrated Priority-Medium Type-Defect
|
```
What steps will reproduce the problem?
1. go to main page
2. click "show full list"
3. fail
What is the expected output? What do you see instead?
expected: show list
seen: Timeout: datastore timeout: operation took too long
What version of the product are you using? On what operating system?
latest, mac safari
Please provide any additional information below.
i *just* entered a new secret. kjams "Timeout: datastore timeout: operation
took too long". did
that break it? why?
```
Original issue reported on code.google.com by `anbaricf...@gmail.com` on 20 Jun 2008 at 7:45
|
1.0
|
can't "show full list" - ```
What steps will reproduce the problem?
1. go to main page
2. click "show full list"
3. fail
What is the expected output? What do you see instead?
expected: show list
seen: Timeout: datastore timeout: operation took too long
What version of the product are you using? On what operating system?
latest, mac safari
Please provide any additional information below.
i *just* entered a new secret. kjams "Timeout: datastore timeout: operation
took too long". did
that break it? why?
```
Original issue reported on code.google.com by `anbaricf...@gmail.com` on 20 Jun 2008 at 7:45
|
non_design
|
can t show full list what steps will reproduce the problem go to main page click show full list fail what is the expected output what do you see instead expected show list seen timeout datastore timeout operation took too long what version of the product are you using on what operating system latest mac safari please provide any additional information below i just entered a new secret kjams timeout datastore timeout operation took too long did that break it why original issue reported on code google com by anbaricf gmail com on jun at
| 0
|
157,954
| 24,759,346,161
|
IssuesEvent
|
2022-10-21 21:23:46
|
mozilla/foundation.mozilla.org
|
https://api.github.com/repos/mozilla/foundation.mozilla.org
|
closed
|
[PNI editorial updates] UI updates based on usertesting
|
design Buyer's Guide 🛍
|
Goals
- [x] Update designs based on feedback from usertesting
- [x] Get feedback from design
- [x] Get feedback from devs and Jen
- [x] Make sure comps are ready for design to dev handoff
- [x] Create tickets for devs (provide description of changes, links to comps and acceptance criteria)
|
1.0
|
[PNI editorial updates] UI updates based on usertesting - Goals
- [x] Update designs based on feedback from usertesting
- [x] Get feedback from design
- [x] Get feedback from devs and Jen
- [x] Make sure comps are ready for design to dev handoff
- [x] Create tickets for devs (provide description of changes, links to comps and acceptance criteria)
|
design
|
ui updates based on usertesting goals update designs based on feedback from usertesting get feedback from design get feedback from devs and jen make sure comps are ready for design to dev handoff create tickets for devs provide description of changes links to comps and acceptance criteria
| 1
|
21,985
| 3,768,932,357
|
IssuesEvent
|
2016-03-16 08:25:13
|
Roy2014Kimi/JI3U47XFP7X25PCEAD3LMVXQ
|
https://api.github.com/repos/Roy2014Kimi/JI3U47XFP7X25PCEAD3LMVXQ
|
closed
|
VsHYw0F6/TLh3B2LzBFmtJ3FZsNKoAgQnmcLgfqvKh+H9JcybjOh3qssPlTlnka/RXfBLgNmshz0sA4TrRXo27mX5UIhyT53wXD0m2qboxoo892x/L2aMDaGX2tdqf/9aOQj0Ts/xyDEujP2VbL+uSCdIFs32fiFCqpFy/COEGU=
|
design
|
Jf6tTRAF+qYwp0RY9enJ2J52xS8UUIGWK3oYjlHG1Vq1s2hZx6QqjegPER4MbQxzcc1leZWo7ouEHj1XIWq0McBnLeFgQsy3kbEjseWmK2fljkj7VUMk8DpRzSMkmw1G/+79isyP9qIlzQO43C4TCPd5Sia9vD7EMHIUXFA5gHNTsHk0tyI/zWZSqvjEPhMkDKfGUXzrNQJX4gFfmwguVDLDfdl02wo/hgmVxGcfq5POEvpksx6dI0Koi8Ow13safngyh5mUa//n21NidVpaf8jPcTxjpkOkHCKJakSpNCy51ufdyvdbUTj0AtIRoRM9Ou20FN0JZ77gvw+huUN774NM1Qs+WLN3O/qIp/JMzcQ3ZjEGmVHtsAFaRMCNiAjsSmQHUMmgJLpyXF/L5eCfXC2OLySIEB+RMxuTYXp+s4y3lYbGmBczpX8WnfiHV83Duag6OL+BTMYOV8l6iVMAfjmYLE1VI8o3b7sO20x520dgxSPdPkV//azkiVKk4m15fUYib7et5dSZTfcyAz6O9cYOqAtvBIQtGKJq50bgeIYMp8ZRfOs1AlfiAV+bCC5UMsN92XTbCj+GCZXEZx+rk84S+mSzHp0jQqiLw7DXexpGTGaoxv6ys+wZ/xSvL0W5isXNDkKreeqgwMT++BKhbbnW593K91tROPQC0hGhEz067bQU3QlnvuC/D6G5Q3vvg0zVCz5Ys3c7+oin8kzNxO9MwvLUKVzsUJZJFMNoZTBKZAdQyaAkunJcX8vl4J9cLY4vJIgQH5EzG5Nhen6zjLeVhsaYFzOlfxad+IdXzcMRZ17t8VVA1PthHkWIQxuAOZgsTVUjyjdvuw7bTHnbR2DFI90+RX/9rOSJUqTibXl9RiJvt63l1JlN9zIDPo71DG74hqp4fEnVx+D9jD6akAynxlF86zUCV+IBX5sILlQyw33ZdNsKP4YJlcRnH6uTzhL6ZLMenSNCqIvDsNd7GukMN15ugQ+/au5AKVSulEgEWavVWha79jzqG1nG2PEaudbn3cr3W1E49ALSEaETPTrttBTdCWe+4L8PoblDe++DTNULPlizdzv6iKfyTM3EdWk7rTJZ2dPDaN3hGfpalEpkB1DJoCS6clxfy+Xgn1wtji8kiBAfkTMbk2F6frOMt5WGxpgXM6V/Fp34h1fNw9s0gJK2rdIfen2ERWerf+k5mCxNVSPKN2+7DttMedtHYMUj3T5Ff/2s5IlSpOJteX1GIm+3reXUmU33MgM+jvVcNBz5PBpWrsWgLCrb6PHEDKfGUXzrNQJX4gFfmwguVDLDfdl02wo/hgmVxGcfq5POEvpksx6dI0Koi8Ow13sa6Qw3Xm6BD79q7kApVK6USHS2E7agzJ/uVoc+EuLgSjK51ufdyvdbUTj0AtIRoRM9Ou20FN0JZ77gvw+huUN77+WlUCXy/vaGNmeLN0v4EHzywZzxZgcC1bsfHHHzuojHSmQHUMmgJLpyXF/L5eCfXC2OLySIEB+RMxuTYXp+s4zhh5I3ctkTPpB+l7SC41SQcE6DKjL/f36CI47TzHfW5jmYLE1VI8o3b7sO20x520dgxSPdPkV//azkiVKk4m15fUYib7et5dSZTfcyAz6O9WPrRAOmqqtNAbhWEw22FCCJoBCEWgy2keN7WAvPMYANMsN92XTbCj+GCZXEZx+rk84S+mSzHp0jQqiLw7DXexqNq4x9I6fuOlSs/W/zeQqdMmGZrxrsN3yPFtuRdKPBjrnW593K91tROPQC0hGhEz067bQU3QlnvuC/D6G5Q3vv5aVQJfL+9oY2Z4s3S/gQfC1z9EN5Xu3+tohOcedW2WMJmVC8BuOvryCfSdD6w1mUDh9AYc+Ml05yBLRmQLkq910wgIv/oa3qj/oAmwyf1X4/5FEO4Jx/k+6tcutfzUDxi34SskcOModtQVQLuDNnkT97d8zQNyT3OjZaiDa5Ag/gLcHsNalOt6RC5JhG5q5IjauMfSOn7jpUrP1v83kKnZjII6MTcJyGd7ZmlpbBKKdqKT/nzgyeEy+xBMdt58FMmzossE7tr6nnTESZj4Qkqx6rP1j8hGFBtrV9tzFGqwWcw6mzoilgpr5OKQMm07BMcLwc9ECsmyKC+7HnLk5v/NGYqTvokp3NX0VyLpGCpZgqlWgevvCYSjOprbvVuco9mScPs8k9xp7Emh/guJfMHt8ZAQOdtNnVjARlFSmhtXI1tJUtVPdC4bDXEEHLjS6rwPGUT6f4j3ahKEAxQfrm+F758rhNnLlR2qIJuj1mH+mZNlxYb5Na7yvHKragNjbfmy/xlxyEc+ZMIOcloE4q99UPdbNXYFQILQhrDpjk5RTfIAckNn4+5bkj8O3TGePvA7+P5/RYneB+V7VXH8jHfVq4epRkD/ZxM/6fi4l40fNitOcpVXRgRbtizaoJdzR+uyd3sJO9sm0YZQ4rX1Rk+DyzGdH+BLkfntJSJb35lOdvvNvYIkWM9+24oUVy12MFOe8lXvxUYY94EqHPFWQyEl0s6NXERUQ3ZjYJYTj3hzPlpVAl8v72hjZnizdL+BB8hHHSYjJiLRlOyt9tY4nHECl/4J/B/nuRDnZdA/XGO6lfu8cciIyU2PT0rwFA3A3IXTCAi/+hreqP+gCbDJ/Vfqhh5CPc5Y1FRiTq40Ft7MeLfhKyRw4yh21BVAu4M2eRL/9DNGlcjnDhauOt1kkPOuAtwew1qU63pELkmEbmrkiNq4x9I6fuOlSs/W/zeQqdx/M77rkf4jVKi1oRWUiy44EEvnTYtswlzLu1h17wi8WbOiywTu2vqedMRJmPhCSrHqs/WPyEYUG2tX23MUarBaVNypvf10tiI45G2DMabKxwvBz0QKybIoL7secuTm/8GbsMkjIyqAnVJYWlKbK73SqVaB6+8JhKM6mtu9W5yj2ZJw+zyT3GnsSaH+C4l8we+YOrQB8QwaUZ//2f21y15MTeso0iLyyZmScS/Uckvc/A8ZRPp/iPdqEoQDFB+ub4XvnyuE2cuVHaogm6PWYf6RPRUU3xROY7cMrH8V4//k2MgE3FBKEod9ydVeYf1luc1Q91s1dgVAgtCGsOmOTlFN8gByQ2fj7luSPw7dMZ4+8V1fpWdul/E1KcCfLwUZBMWrh6lGQP9nEz/p+LiXjR84JbyvUno2lVdjMZiLULuEq7J3ewk72ybRhlDitfVGT4PLMZ0f4EuR+e0lIlvfmU57G6D3ciElae/+RVeVmc0k+ZsAev1s2i5n4c0/9jtz7tXSzo1cRFRDdmNglhOPeHM+WlUCXy/vaGNmeLN0v4EHyz3PQ+sAv/HKBvOIVEZVx2KX/gn8H+e5EOdl0D9cY7qXBL0r74O6HNX++0ts9QUw1dMICL/6Gt6o/6AJsMn9V+rLIeAf/AA1G1bnVr9a/Moot+ErJHDjKHbUFUC7gzZ5HC5m7D3C8e/xLUwrPOMDz/4C3B7DWpTrekQuSYRuauSI2rjH0jp+46VKz9b/N5Cp1QqTLd/QZUMZ4t0zo5Hp7DuWSC1b9wjeoB4U0jjmGXV5s6LLBO7a+p50xEmY+EJKseqz9Y/IRhQba1fbcxRqsFHsSqb/L1wsIPKw9XkqsuSXC8HPRArJsigvux5y5Ob/zsfXoMO5Li5MlDDDr4XNMkKpVoHr7wmEozqa271bnKPZJFiJO9cIvDVwwIaptHgHmUOlCqWuO09/bOrwhbBKpq6OYbBTE8EW0PynBACipXxcDxlE+n+I92oShAMUH65vhe+fK4TZy5UdqiCbo9Zh/p2gjhh7/thVvyPUFTKVaY+gQO14y/gGmItCQMKLHQf7nVD3WzV2BUCC0Iaw6Y5OUU3yAHJDZ+PuW5I/Dt0xnj71t9To33rxS+5XzubT93mnRauHqUZA/2cTP+n4uJeNHzu84Kli4QJTOPlTZApurtArsnd7CTvbJtGGUOK19UZPg8sxnR/gS5H57SUiW9+ZTndShYQmUSp8pZy8lNyf/6LghdSiZ6kxS8AWvf3xpND/NdLOjVxEVEN2Y2CWE494cz5aVQJfL+9oY2Z4s3S/gQfAjbucy8DyDAVrKlAtNsrbM1OMrPUXtW1fHHsjlDK3iiSnTxXpRFdBmIT7TWAOoXSV0wgIv/oa3qj/oAmwyf1X5pDGmL0CPt+6WQlxZSDniXi34SskcOModtQVQLuDNnkfyUAnBnJKpgnLRFvDmhftDgLcHsNalOt6RC5JhG5q5IjauMfSOn7jpUrP1v83kKnXCpOsjOQqXNw4Iu+IbAkdb0S66g6ryhl+b2T4Q0PI5YmzossE7tr6nnTESZj4Qkqx6rP1j8hGFBtrV9tzFGqwX+CGpsbFBYMrJgJuzelrH5cLwc9ECsmyKC+7HnLk5v/GsAnQ9SwBFU7MCV9DsgtZ4qlWgevvCYSjOprbvVuco9lIRgboq/9fvmu4NSlhnDtJEXz21YleMaxND4/3UFcIHjkEmd+K0HoXTcBLE6YCyBwPGUT6f4j3ahKEAxQfrm+F758rhNnLlR2qIJuj1mH+lN8LACsawHLgzlepuLC5Gel8P5S6JgmBMCe0d1z+zmvdUPdbNXYFQILQhrDpjk5RTfIAckNn4+5bkj8O3TGePvN5fbYvi51aRzk4JDrajeivZobXEhoAs7Ima5mg78wENgxSPdPkV//azkiVKk4m15fUYib7et5dSZTfcyAz6O9U8JWCR2KrD4MF4p7DX2MsSzgF/Pa/GblJvEbDcwRPdXTMaNzMe+E6mpqbKpm9Ncr1fJPUSfi93AO+UK5Cec1VBGzUK2uCBvrzWTlpEb1qUFUDhuwUJ4FmXwlM5X8rwPGfRGtg007ZfGJUvoGrg74lbuEZ5cHg2sBMsrUtqb8CeKXMDZLfMUaFknDTHZtbjg86qDU3u+iTAo/w0LO7LzzWzro9FBuhFqDgQIb6OLYXxMrINcCOCbmyF30HArYwLpOgnIuYj3htzG0E4b4/0MP3C8GT+4Lls+1qOy5GAyZnE9UzhBV5yV4VbtqAH8qFHCjDutg3htYG7geZkrBaLVIiMrrnGJbPIMYyZ78HqBe37dXvpMyraZxy1IMhK5W721Lz/M+1vNXUc0mizOLtJoIkbRgkThWo+T0FZ6eJ9+I4djoJKf4J+tpxHdxcvMaJSu9hBj2DL481Ql/yjhYqXBAIsod0YTm/kxe9pHaDVLDW2dfk9YvMh91T9SZ+vPSjwTxEe70hPnSa0n7F9Bkun8ig+tYA5RFQg/PmLLmy+nPle1qoNTe76JMCj/DQs7svPNbFGvEcjbPCng9eaIjZUnwCWsg1wI4JubIXfQcCtjAuk6Cci5iPeG3MbQThvj/Qw/cLwZP7guWz7Wo7LkYDJmcT2sUO80wrj0XtfdDuSr8mcJO62DeG1gbuB5mSsFotUiIyuucYls8gxjJnvweoF7ft1e+kzKtpnHLUgyErlbvbUvgCTIrT5MIhp0kTtPYCSbdosSh1BKVew9Edm5CvwloS/s0oH4oV/cKBIuRQn86Q9tUkVbDUqZwS6jcX3JhzK4nKoApNDiEiLNSqeqsUniqtslq+xew4aOVpOX1+RmIrVobCXjd+rXehEjzW643P6Fz+5YVvOSoKhM0LOIqqV5udscqERbPE5sOhhL+Sb2u9m5drZZ77Ted0ChYhZNRYPGh6kAWyW+UndcBpo72ZWW3+EYy+tkopeQagHcgDKrx5YxWfCFu5f9vccT2Er15gEJHdul5vmJp3dKuphbDUhAFZkw2MACS8JVgwMx4XghNqcyL8u3wptwjFUKOfXsa6I2vUbNQra4IG+vNZOWkRvWpQXmNx7p/d793QdjA7kbMJeYTUqYwP0X+GaJyoZteyQGspKm1g+QF+KeqQ5CKwSrJiFSRVsNSpnBLqNxfcmHMricEB9gqlTktFj3rGLenuIHFfsmqwhLLNNDPSnTuS+Evd3jjZ9ywJ+FbZ1ZupFnklyPrWAOURUIPz5iy5svpz5XtaqDU3u+iTAo/w0LO7LzzWx9fbbufSReybK1ZdLFklyCO0drQZpRuxFdOOQNOX2/n4rBVeUf6NgTDpyNbiLhWZtPCVgkdiqw+DBeKew19jLEFiQib1byjSc61oxHfzKbv0zGjczHvhOpqamyqZvTXK9XyT1En4vdwDvlCuQnnNVQRs1Ctrggb681k5aRG9alBfMBG9kfFhu5c82BJDpvHmWGK1GPJBfPOiKnW8M3qKaU7hGeXB4NrATLK1Lam/AnilzA2S3zFGhZJw0x2bW44POqg1N7vokwKP8NCzuy881swiJowxV6JfmDjemaJr2tXDtHa0GaUbsRXTjkDTl9v5+KwVXlH+jYEw6cjW4i4VmbTwlYJHYqsPgwXinsNfYyxB4+mCb78pdRR152U6iSvyKPvd1VyRX0EYa7rXKxkrgj0JBBhUJqLXA55DChEbIyfgJmd3HeEGWEtG33TE3iGEnP7RaPgNJzlDD2kynxPLQOtvQ9V5pTQoTYt4zsQXO2Yg==
|
1.0
|
VsHYw0F6/TLh3B2LzBFmtJ3FZsNKoAgQnmcLgfqvKh+H9JcybjOh3qssPlTlnka/RXfBLgNmshz0sA4TrRXo27mX5UIhyT53wXD0m2qboxoo892x/L2aMDaGX2tdqf/9aOQj0Ts/xyDEujP2VbL+uSCdIFs32fiFCqpFy/COEGU= - Jf6tTRAF+qYwp0RY9enJ2J52xS8UUIGWK3oYjlHG1Vq1s2hZx6QqjegPER4MbQxzcc1leZWo7ouEHj1XIWq0McBnLeFgQsy3kbEjseWmK2fljkj7VUMk8DpRzSMkmw1G/+79isyP9qIlzQO43C4TCPd5Sia9vD7EMHIUXFA5gHNTsHk0tyI/zWZSqvjEPhMkDKfGUXzrNQJX4gFfmwguVDLDfdl02wo/hgmVxGcfq5POEvpksx6dI0Koi8Ow13safngyh5mUa//n21NidVpaf8jPcTxjpkOkHCKJakSpNCy51ufdyvdbUTj0AtIRoRM9Ou20FN0JZ77gvw+huUN774NM1Qs+WLN3O/qIp/JMzcQ3ZjEGmVHtsAFaRMCNiAjsSmQHUMmgJLpyXF/L5eCfXC2OLySIEB+RMxuTYXp+s4y3lYbGmBczpX8WnfiHV83Duag6OL+BTMYOV8l6iVMAfjmYLE1VI8o3b7sO20x520dgxSPdPkV//azkiVKk4m15fUYib7et5dSZTfcyAz6O9cYOqAtvBIQtGKJq50bgeIYMp8ZRfOs1AlfiAV+bCC5UMsN92XTbCj+GCZXEZx+rk84S+mSzHp0jQqiLw7DXexpGTGaoxv6ys+wZ/xSvL0W5isXNDkKreeqgwMT++BKhbbnW593K91tROPQC0hGhEz067bQU3QlnvuC/D6G5Q3vvg0zVCz5Ys3c7+oin8kzNxO9MwvLUKVzsUJZJFMNoZTBKZAdQyaAkunJcX8vl4J9cLY4vJIgQH5EzG5Nhen6zjLeVhsaYFzOlfxad+IdXzcMRZ17t8VVA1PthHkWIQxuAOZgsTVUjyjdvuw7bTHnbR2DFI90+RX/9rOSJUqTibXl9RiJvt63l1JlN9zIDPo71DG74hqp4fEnVx+D9jD6akAynxlF86zUCV+IBX5sILlQyw33ZdNsKP4YJlcRnH6uTzhL6ZLMenSNCqIvDsNd7GukMN15ugQ+/au5AKVSulEgEWavVWha79jzqG1nG2PEaudbn3cr3W1E49ALSEaETPTrttBTdCWe+4L8PoblDe++DTNULPlizdzv6iKfyTM3EdWk7rTJZ2dPDaN3hGfpalEpkB1DJoCS6clxfy+Xgn1wtji8kiBAfkTMbk2F6frOMt5WGxpgXM6V/Fp34h1fNw9s0gJK2rdIfen2ERWerf+k5mCxNVSPKN2+7DttMedtHYMUj3T5Ff/2s5IlSpOJteX1GIm+3reXUmU33MgM+jvVcNBz5PBpWrsWgLCrb6PHEDKfGUXzrNQJX4gFfmwguVDLDfdl02wo/hgmVxGcfq5POEvpksx6dI0Koi8Ow13sa6Qw3Xm6BD79q7kApVK6USHS2E7agzJ/uVoc+EuLgSjK51ufdyvdbUTj0AtIRoRM9Ou20FN0JZ77gvw+huUN77+WlUCXy/vaGNmeLN0v4EHzywZzxZgcC1bsfHHHzuojHSmQHUMmgJLpyXF/L5eCfXC2OLySIEB+RMxuTYXp+s4zhh5I3ctkTPpB+l7SC41SQcE6DKjL/f36CI47TzHfW5jmYLE1VI8o3b7sO20x520dgxSPdPkV//azkiVKk4m15fUYib7et5dSZTfcyAz6O9WPrRAOmqqtNAbhWEw22FCCJoBCEWgy2keN7WAvPMYANMsN92XTbCj+GCZXEZx+rk84S+mSzHp0jQqiLw7DXexqNq4x9I6fuOlSs/W/zeQqdMmGZrxrsN3yPFtuRdKPBjrnW593K91tROPQC0hGhEz067bQU3QlnvuC/D6G5Q3vv5aVQJfL+9oY2Z4s3S/gQfC1z9EN5Xu3+tohOcedW2WMJmVC8BuOvryCfSdD6w1mUDh9AYc+Ml05yBLRmQLkq910wgIv/oa3qj/oAmwyf1X4/5FEO4Jx/k+6tcutfzUDxi34SskcOModtQVQLuDNnkT97d8zQNyT3OjZaiDa5Ag/gLcHsNalOt6RC5JhG5q5IjauMfSOn7jpUrP1v83kKnZjII6MTcJyGd7ZmlpbBKKdqKT/nzgyeEy+xBMdt58FMmzossE7tr6nnTESZj4Qkqx6rP1j8hGFBtrV9tzFGqwWcw6mzoilgpr5OKQMm07BMcLwc9ECsmyKC+7HnLk5v/NGYqTvokp3NX0VyLpGCpZgqlWgevvCYSjOprbvVuco9mScPs8k9xp7Emh/guJfMHt8ZAQOdtNnVjARlFSmhtXI1tJUtVPdC4bDXEEHLjS6rwPGUT6f4j3ahKEAxQfrm+F758rhNnLlR2qIJuj1mH+mZNlxYb5Na7yvHKragNjbfmy/xlxyEc+ZMIOcloE4q99UPdbNXYFQILQhrDpjk5RTfIAckNn4+5bkj8O3TGePvA7+P5/RYneB+V7VXH8jHfVq4epRkD/ZxM/6fi4l40fNitOcpVXRgRbtizaoJdzR+uyd3sJO9sm0YZQ4rX1Rk+DyzGdH+BLkfntJSJb35lOdvvNvYIkWM9+24oUVy12MFOe8lXvxUYY94EqHPFWQyEl0s6NXERUQ3ZjYJYTj3hzPlpVAl8v72hjZnizdL+BB8hHHSYjJiLRlOyt9tY4nHECl/4J/B/nuRDnZdA/XGO6lfu8cciIyU2PT0rwFA3A3IXTCAi/+hreqP+gCbDJ/Vfqhh5CPc5Y1FRiTq40Ft7MeLfhKyRw4yh21BVAu4M2eRL/9DNGlcjnDhauOt1kkPOuAtwew1qU63pELkmEbmrkiNq4x9I6fuOlSs/W/zeQqdx/M77rkf4jVKi1oRWUiy44EEvnTYtswlzLu1h17wi8WbOiywTu2vqedMRJmPhCSrHqs/WPyEYUG2tX23MUarBaVNypvf10tiI45G2DMabKxwvBz0QKybIoL7secuTm/8GbsMkjIyqAnVJYWlKbK73SqVaB6+8JhKM6mtu9W5yj2ZJw+zyT3GnsSaH+C4l8we+YOrQB8QwaUZ//2f21y15MTeso0iLyyZmScS/Uckvc/A8ZRPp/iPdqEoQDFB+ub4XvnyuE2cuVHaogm6PWYf6RPRUU3xROY7cMrH8V4//k2MgE3FBKEod9ydVeYf1luc1Q91s1dgVAgtCGsOmOTlFN8gByQ2fj7luSPw7dMZ4+8V1fpWdul/E1KcCfLwUZBMWrh6lGQP9nEz/p+LiXjR84JbyvUno2lVdjMZiLULuEq7J3ewk72ybRhlDitfVGT4PLMZ0f4EuR+e0lIlvfmU57G6D3ciElae/+RVeVmc0k+ZsAev1s2i5n4c0/9jtz7tXSzo1cRFRDdmNglhOPeHM+WlUCXy/vaGNmeLN0v4EHyz3PQ+sAv/HKBvOIVEZVx2KX/gn8H+e5EOdl0D9cY7qXBL0r74O6HNX++0ts9QUw1dMICL/6Gt6o/6AJsMn9V+rLIeAf/AA1G1bnVr9a/Moot+ErJHDjKHbUFUC7gzZ5HC5m7D3C8e/xLUwrPOMDz/4C3B7DWpTrekQuSYRuauSI2rjH0jp+46VKz9b/N5Cp1QqTLd/QZUMZ4t0zo5Hp7DuWSC1b9wjeoB4U0jjmGXV5s6LLBO7a+p50xEmY+EJKseqz9Y/IRhQba1fbcxRqsFHsSqb/L1wsIPKw9XkqsuSXC8HPRArJsigvux5y5Ob/zsfXoMO5Li5MlDDDr4XNMkKpVoHr7wmEozqa271bnKPZJFiJO9cIvDVwwIaptHgHmUOlCqWuO09/bOrwhbBKpq6OYbBTE8EW0PynBACipXxcDxlE+n+I92oShAMUH65vhe+fK4TZy5UdqiCbo9Zh/p2gjhh7/thVvyPUFTKVaY+gQO14y/gGmItCQMKLHQf7nVD3WzV2BUCC0Iaw6Y5OUU3yAHJDZ+PuW5I/Dt0xnj71t9To33rxS+5XzubT93mnRauHqUZA/2cTP+n4uJeNHzu84Kli4QJTOPlTZApurtArsnd7CTvbJtGGUOK19UZPg8sxnR/gS5H57SUiW9+ZTndShYQmUSp8pZy8lNyf/6LghdSiZ6kxS8AWvf3xpND/NdLOjVxEVEN2Y2CWE494cz5aVQJfL+9oY2Z4s3S/gQfAjbucy8DyDAVrKlAtNsrbM1OMrPUXtW1fHHsjlDK3iiSnTxXpRFdBmIT7TWAOoXSV0wgIv/oa3qj/oAmwyf1X5pDGmL0CPt+6WQlxZSDniXi34SskcOModtQVQLuDNnkfyUAnBnJKpgnLRFvDmhftDgLcHsNalOt6RC5JhG5q5IjauMfSOn7jpUrP1v83kKnXCpOsjOQqXNw4Iu+IbAkdb0S66g6ryhl+b2T4Q0PI5YmzossE7tr6nnTESZj4Qkqx6rP1j8hGFBtrV9tzFGqwX+CGpsbFBYMrJgJuzelrH5cLwc9ECsmyKC+7HnLk5v/GsAnQ9SwBFU7MCV9DsgtZ4qlWgevvCYSjOprbvVuco9lIRgboq/9fvmu4NSlhnDtJEXz21YleMaxND4/3UFcIHjkEmd+K0HoXTcBLE6YCyBwPGUT6f4j3ahKEAxQfrm+F758rhNnLlR2qIJuj1mH+lN8LACsawHLgzlepuLC5Gel8P5S6JgmBMCe0d1z+zmvdUPdbNXYFQILQhrDpjk5RTfIAckNn4+5bkj8O3TGePvN5fbYvi51aRzk4JDrajeivZobXEhoAs7Ima5mg78wENgxSPdPkV//azkiVKk4m15fUYib7et5dSZTfcyAz6O9U8JWCR2KrD4MF4p7DX2MsSzgF/Pa/GblJvEbDcwRPdXTMaNzMe+E6mpqbKpm9Ncr1fJPUSfi93AO+UK5Cec1VBGzUK2uCBvrzWTlpEb1qUFUDhuwUJ4FmXwlM5X8rwPGfRGtg007ZfGJUvoGrg74lbuEZ5cHg2sBMsrUtqb8CeKXMDZLfMUaFknDTHZtbjg86qDU3u+iTAo/w0LO7LzzWzro9FBuhFqDgQIb6OLYXxMrINcCOCbmyF30HArYwLpOgnIuYj3htzG0E4b4/0MP3C8GT+4Lls+1qOy5GAyZnE9UzhBV5yV4VbtqAH8qFHCjDutg3htYG7geZkrBaLVIiMrrnGJbPIMYyZ78HqBe37dXvpMyraZxy1IMhK5W721Lz/M+1vNXUc0mizOLtJoIkbRgkThWo+T0FZ6eJ9+I4djoJKf4J+tpxHdxcvMaJSu9hBj2DL481Ql/yjhYqXBAIsod0YTm/kxe9pHaDVLDW2dfk9YvMh91T9SZ+vPSjwTxEe70hPnSa0n7F9Bkun8ig+tYA5RFQg/PmLLmy+nPle1qoNTe76JMCj/DQs7svPNbFGvEcjbPCng9eaIjZUnwCWsg1wI4JubIXfQcCtjAuk6Cci5iPeG3MbQThvj/Qw/cLwZP7guWz7Wo7LkYDJmcT2sUO80wrj0XtfdDuSr8mcJO62DeG1gbuB5mSsFotUiIyuucYls8gxjJnvweoF7ft1e+kzKtpnHLUgyErlbvbUvgCTIrT5MIhp0kTtPYCSbdosSh1BKVew9Edm5CvwloS/s0oH4oV/cKBIuRQn86Q9tUkVbDUqZwS6jcX3JhzK4nKoApNDiEiLNSqeqsUniqtslq+xew4aOVpOX1+RmIrVobCXjd+rXehEjzW643P6Fz+5YVvOSoKhM0LOIqqV5udscqERbPE5sOhhL+Sb2u9m5drZZ77Ted0ChYhZNRYPGh6kAWyW+UndcBpo72ZWW3+EYy+tkopeQagHcgDKrx5YxWfCFu5f9vccT2Er15gEJHdul5vmJp3dKuphbDUhAFZkw2MACS8JVgwMx4XghNqcyL8u3wptwjFUKOfXsa6I2vUbNQra4IG+vNZOWkRvWpQXmNx7p/d793QdjA7kbMJeYTUqYwP0X+GaJyoZteyQGspKm1g+QF+KeqQ5CKwSrJiFSRVsNSpnBLqNxfcmHMricEB9gqlTktFj3rGLenuIHFfsmqwhLLNNDPSnTuS+Evd3jjZ9ywJ+FbZ1ZupFnklyPrWAOURUIPz5iy5svpz5XtaqDU3u+iTAo/w0LO7LzzWx9fbbufSReybK1ZdLFklyCO0drQZpRuxFdOOQNOX2/n4rBVeUf6NgTDpyNbiLhWZtPCVgkdiqw+DBeKew19jLEFiQib1byjSc61oxHfzKbv0zGjczHvhOpqamyqZvTXK9XyT1En4vdwDvlCuQnnNVQRs1Ctrggb681k5aRG9alBfMBG9kfFhu5c82BJDpvHmWGK1GPJBfPOiKnW8M3qKaU7hGeXB4NrATLK1Lam/AnilzA2S3zFGhZJw0x2bW44POqg1N7vokwKP8NCzuy881swiJowxV6JfmDjemaJr2tXDtHa0GaUbsRXTjkDTl9v5+KwVXlH+jYEw6cjW4i4VmbTwlYJHYqsPgwXinsNfYyxB4+mCb78pdRR152U6iSvyKPvd1VyRX0EYa7rXKxkrgj0JBBhUJqLXA55DChEbIyfgJmd3HeEGWEtG33TE3iGEnP7RaPgNJzlDD2kynxPLQOtvQ9V5pTQoTYt4zsQXO2Yg==
|
design
|
coegu qip rmxutyxp gczxezx wz rx uvoc wlucxy rmxutyxp gczxezx w k nzgyeey xlxyec ryneb zxm dyzgdh b nurdnzda hreqp gcbdj w zeqqdx uckvc ipdqeoqdfb p wlucxy sav rlieaf moot xluwrpomdz n thvvypuftkvay pa gbljvebdcwrpdxtmanzme itao m pmllmy qw rmirvobcxjd eyy qf itao kwvxlh
| 1
|
48,947
| 6,137,299,313
|
IssuesEvent
|
2017-06-26 11:55:08
|
AnSyn/ansyn
|
https://api.github.com/repos/AnSyn/ansyn
|
reopened
|
pixel range imagery (images without geo-registration/ reference)
|
Ready for: Design
|
2 sub subjects:
1. how to indicate an un geo-registered image?
2. how to fix geo-registration?
|
1.0
|
pixel range imagery (images without geo-registration/ reference) - 2 sub subjects:
1. how to indicate an un geo-registered image?
2. how to fix geo-registration?
|
design
|
pixel range imagery images without geo registration reference sub subjects how to indicate an un geo registered image how to fix geo registration
| 1
|
21,370
| 29,202,227,103
|
IssuesEvent
|
2023-05-21 00:36:36
|
devssa/onde-codar-em-salvador
|
https://api.github.com/repos/devssa/onde-codar-em-salvador
|
closed
|
[Hibrido / Zona Norte de São Paulo - SP] C#/.Net Developer (Híbrido em Zona norte de SP) na Coodesh
|
SALVADOR BACK-END PJ SQL REQUISITOS PROCESSOS GITHUB SEGURANÇA UMA C QUALIDADE DESENVOLVIMENTO WEB ALOCADO Stale
|
## Descrição da vaga:
Esta é uma vaga de um parceiro da plataforma Coodesh, ao candidatar-se você terá acesso as informações completas sobre a empresa e benefícios.
Fique atento ao redirecionamento que vai te levar para uma url [https://coodesh.com](https://coodesh.com/vagas/cnet-developer-l-211038204?utm_source=github&utm_medium=devssa-onde-codar-em-salvador&modal=open) com o pop-up personalizado de candidatura. 👋
<p>A <strong>Beltis Tecnologia </strong>está em busca de <strong><ins>C#/.Net Developer</ins></strong> para compor seu time!</p>
<p>Buscamos um profissional para ser parte integrante do time de desenvolvimento, capaz de desenhar novas soluções e sustentar os sistemas existentes. Buscamos uma pessoa dinâmica com capacidade para se adaptar a diferentes cenários solicitados. Você irá atuar em uma empresa do segmento bancário/financeiro de grande porte.</p>
<p><strong>Responsabilidades:</strong></p>
<ul>
<li>Atuar no planejamento de novos produtos/serviços, atuando no desenvolvimento das interfaces para os usuários da plataforma;</li>
<li>Atuar no planejamento e desenvolvimento de novas aplicações e funcionalidades;</li>
<li>Fazer parte da sustentação e melhoria de projetos existentes;</li>
<li>Desenvolver soluções técnicas;</li>
<li>Testar as soluções desenvolvidas.</li>
</ul>
<p><strong>Motivos para fazer parte:</strong></p>
<ul>
<li>Projeto motivador em grande empresa do setor financeiro/bancário;</li>
<li>Empresa que investe constantemente em tecnologias e novas soluções para garantir a evolução contínua da qualidade e segurança de seus sistemas;</li>
<li>Ambiente colaborativo com grandes desafios;</li>
<li>Nosso cliente está entre uma das melhores empresas na área de soluções financeiras e tecnologia;</li>
<li>Parceria com plataforma de cursos online para aprimorar seus conhecimentos e habilidades.</li>
</ul>
## BELTIS TECNOLOGIA:
<p>Com mais de 20 anos de atuação no segmento de TI, adotamos uma política direcionada às pessoas. Com conhecimento de mercado, processos e tecnologia, oferecemos alta capacidade em Outsourcing de Profissionais.</p>
<p>Atuamos com diversos clientes a nível nacional, grandes players em seus segmentos que vão desde o financeiro, varejo, ensino e órgãos públicos.</p><a href='https://coodesh.com/empresas/beltis-tecnologia'>Veja mais no site</a>
## Habilidades:
- C#
- .NET Framework
- Microsoft SQL Server
## Local:
Zona Norte de São Paulo - SP
## Requisitos:
- Proficiente em desenvolvimento web;
- Experiência com .NET Framework e C#;
- Experiência com SQL Server;
- Devido a questões de segurança as atividades só podem ser in loco.
## Como se candidatar:
Candidatar-se exclusivamente através da plataforma Coodesh no link a seguir: [C#/.Net Developer (Híbrido em Zona norte de SP) na BELTIS TECNOLOGIA](https://coodesh.com/vagas/cnet-developer-l-211038204?utm_source=github&utm_medium=devssa-onde-codar-em-salvador&modal=open)
Após candidatar-se via plataforma Coodesh e validar o seu login, você poderá acompanhar e receber todas as interações do processo por lá. Utilize a opção **Pedir Feedback** entre uma etapa e outra na vaga que se candidatou. Isso fará com que a pessoa **Recruiter** responsável pelo processo na empresa receba a notificação.
## Labels
#### Alocação
Alocado
#### Regime
PJ
#### Categoria
Back-End
|
1.0
|
[Hibrido / Zona Norte de São Paulo - SP] C#/.Net Developer (Híbrido em Zona norte de SP) na Coodesh - ## Descrição da vaga:
Esta é uma vaga de um parceiro da plataforma Coodesh, ao candidatar-se você terá acesso as informações completas sobre a empresa e benefícios.
Fique atento ao redirecionamento que vai te levar para uma url [https://coodesh.com](https://coodesh.com/vagas/cnet-developer-l-211038204?utm_source=github&utm_medium=devssa-onde-codar-em-salvador&modal=open) com o pop-up personalizado de candidatura. 👋
<p>A <strong>Beltis Tecnologia </strong>está em busca de <strong><ins>C#/.Net Developer</ins></strong> para compor seu time!</p>
<p>Buscamos um profissional para ser parte integrante do time de desenvolvimento, capaz de desenhar novas soluções e sustentar os sistemas existentes. Buscamos uma pessoa dinâmica com capacidade para se adaptar a diferentes cenários solicitados. Você irá atuar em uma empresa do segmento bancário/financeiro de grande porte.</p>
<p><strong>Responsabilidades:</strong></p>
<ul>
<li>Atuar no planejamento de novos produtos/serviços, atuando no desenvolvimento das interfaces para os usuários da plataforma;</li>
<li>Atuar no planejamento e desenvolvimento de novas aplicações e funcionalidades;</li>
<li>Fazer parte da sustentação e melhoria de projetos existentes;</li>
<li>Desenvolver soluções técnicas;</li>
<li>Testar as soluções desenvolvidas.</li>
</ul>
<p><strong>Motivos para fazer parte:</strong></p>
<ul>
<li>Projeto motivador em grande empresa do setor financeiro/bancário;</li>
<li>Empresa que investe constantemente em tecnologias e novas soluções para garantir a evolução contínua da qualidade e segurança de seus sistemas;</li>
<li>Ambiente colaborativo com grandes desafios;</li>
<li>Nosso cliente está entre uma das melhores empresas na área de soluções financeiras e tecnologia;</li>
<li>Parceria com plataforma de cursos online para aprimorar seus conhecimentos e habilidades.</li>
</ul>
## BELTIS TECNOLOGIA:
<p>Com mais de 20 anos de atuação no segmento de TI, adotamos uma política direcionada às pessoas. Com conhecimento de mercado, processos e tecnologia, oferecemos alta capacidade em Outsourcing de Profissionais.</p>
<p>Atuamos com diversos clientes a nível nacional, grandes players em seus segmentos que vão desde o financeiro, varejo, ensino e órgãos públicos.</p><a href='https://coodesh.com/empresas/beltis-tecnologia'>Veja mais no site</a>
## Habilidades:
- C#
- .NET Framework
- Microsoft SQL Server
## Local:
Zona Norte de São Paulo - SP
## Requisitos:
- Proficiente em desenvolvimento web;
- Experiência com .NET Framework e C#;
- Experiência com SQL Server;
- Devido a questões de segurança as atividades só podem ser in loco.
## Como se candidatar:
Candidatar-se exclusivamente através da plataforma Coodesh no link a seguir: [C#/.Net Developer (Híbrido em Zona norte de SP) na BELTIS TECNOLOGIA](https://coodesh.com/vagas/cnet-developer-l-211038204?utm_source=github&utm_medium=devssa-onde-codar-em-salvador&modal=open)
Após candidatar-se via plataforma Coodesh e validar o seu login, você poderá acompanhar e receber todas as interações do processo por lá. Utilize a opção **Pedir Feedback** entre uma etapa e outra na vaga que se candidatou. Isso fará com que a pessoa **Recruiter** responsável pelo processo na empresa receba a notificação.
## Labels
#### Alocação
Alocado
#### Regime
PJ
#### Categoria
Back-End
|
non_design
|
c net developer híbrido em zona norte de sp na coodesh descrição da vaga esta é uma vaga de um parceiro da plataforma coodesh ao candidatar se você terá acesso as informações completas sobre a empresa e benefícios fique atento ao redirecionamento que vai te levar para uma url com o pop up personalizado de candidatura 👋 a beltis tecnologia está em busca de c net developer para compor seu time buscamos um profissional para ser parte integrante do time de desenvolvimento capaz de desenhar novas soluções e sustentar os sistemas existentes buscamos uma pessoa dinâmica com capacidade para se adaptar a diferentes cenários solicitados você irá atuar em uma empresa do segmento bancário financeiro de grande porte responsabilidades atuar no planejamento de novos produtos serviços atuando no desenvolvimento das interfaces para os usuários da plataforma atuar no planejamento e desenvolvimento de novas aplicações e funcionalidades fazer parte da sustentação e melhoria de projetos existentes desenvolver soluções técnicas testar as soluções desenvolvidas motivos para fazer parte projeto motivador em grande empresa do setor financeiro bancário empresa que investe constantemente em tecnologias e novas soluções para garantir a evolução contínua da qualidade e segurança de seus sistemas ambiente colaborativo com grandes desafios nosso cliente está entre uma das melhores empresas na área de soluções financeiras e tecnologia parceria com plataforma de cursos online para aprimorar seus conhecimentos e habilidades beltis tecnologia com mais de anos de atuação no segmento de ti adotamos uma política direcionada às pessoas com conhecimento de mercado processos e tecnologia oferecemos alta capacidade em outsourcing de profissionais atuamos com diversos clientes a nível nacional grandes players em seus segmentos que vão desde o financeiro varejo ensino e órgãos públicos habilidades c net framework microsoft sql server local zona norte de são paulo sp requisitos proficiente em desenvolvimento web experiência com net framework e c experiência com sql server devido a questões de segurança as atividades só podem ser in loco como se candidatar candidatar se exclusivamente através da plataforma coodesh no link a seguir após candidatar se via plataforma coodesh e validar o seu login você poderá acompanhar e receber todas as interações do processo por lá utilize a opção pedir feedback entre uma etapa e outra na vaga que se candidatou isso fará com que a pessoa recruiter responsável pelo processo na empresa receba a notificação labels alocação alocado regime pj categoria back end
| 0
|
137,823
| 18,766,154,553
|
IssuesEvent
|
2021-11-06 01:00:34
|
joshbnewton-prioritize-campaign/eslint-config-premisehealth
|
https://api.github.com/repos/joshbnewton-prioritize-campaign/eslint-config-premisehealth
|
opened
|
CVE-2021-3807 (High) detected in ansi-regex-3.0.0.tgz
|
security vulnerability
|
## CVE-2021-3807 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ansi-regex-3.0.0.tgz</b></p></summary>
<p>Regular expression for matching ANSI escape codes</p>
<p>Library home page: <a href="https://registry.npmjs.org/ansi-regex/-/ansi-regex-3.0.0.tgz">https://registry.npmjs.org/ansi-regex/-/ansi-regex-3.0.0.tgz</a></p>
<p>Path to dependency file: eslint-config-premisehealth/package.json</p>
<p>Path to vulnerable library: eslint-config-premisehealth/node_modules/ansi-regex/package.json</p>
<p>
Dependency Hierarchy:
- eslint-5.9.0.tgz (Root Library)
- strip-ansi-4.0.0.tgz
- :x: **ansi-regex-3.0.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
ansi-regex is vulnerable to Inefficient Regular Expression Complexity
<p>Publish Date: 2021-09-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3807>CVE-2021-3807</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994/">https://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994/</a></p>
<p>Release Date: 2021-09-17</p>
<p>Fix Resolution: ansi-regex - 5.0.1,6.0.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"ansi-regex","packageVersion":"3.0.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"eslint:5.9.0;strip-ansi:4.0.0;ansi-regex:3.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ansi-regex - 5.0.1,6.0.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-3807","vulnerabilityDetails":"ansi-regex is vulnerable to Inefficient Regular Expression Complexity","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3807","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2021-3807 (High) detected in ansi-regex-3.0.0.tgz - ## CVE-2021-3807 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ansi-regex-3.0.0.tgz</b></p></summary>
<p>Regular expression for matching ANSI escape codes</p>
<p>Library home page: <a href="https://registry.npmjs.org/ansi-regex/-/ansi-regex-3.0.0.tgz">https://registry.npmjs.org/ansi-regex/-/ansi-regex-3.0.0.tgz</a></p>
<p>Path to dependency file: eslint-config-premisehealth/package.json</p>
<p>Path to vulnerable library: eslint-config-premisehealth/node_modules/ansi-regex/package.json</p>
<p>
Dependency Hierarchy:
- eslint-5.9.0.tgz (Root Library)
- strip-ansi-4.0.0.tgz
- :x: **ansi-regex-3.0.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
ansi-regex is vulnerable to Inefficient Regular Expression Complexity
<p>Publish Date: 2021-09-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3807>CVE-2021-3807</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994/">https://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994/</a></p>
<p>Release Date: 2021-09-17</p>
<p>Fix Resolution: ansi-regex - 5.0.1,6.0.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"ansi-regex","packageVersion":"3.0.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"eslint:5.9.0;strip-ansi:4.0.0;ansi-regex:3.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ansi-regex - 5.0.1,6.0.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-3807","vulnerabilityDetails":"ansi-regex is vulnerable to Inefficient Regular Expression Complexity","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3807","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->
|
non_design
|
cve high detected in ansi regex tgz cve high severity vulnerability vulnerable library ansi regex tgz regular expression for matching ansi escape codes library home page a href path to dependency file eslint config premisehealth package json path to vulnerable library eslint config premisehealth node modules ansi regex package json dependency hierarchy eslint tgz root library strip ansi tgz x ansi regex tgz vulnerable library found in base branch master vulnerability details ansi regex is vulnerable to inefficient regular expression complexity publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution ansi regex isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree eslint strip ansi ansi regex isminimumfixversionavailable true minimumfixversion ansi regex basebranches vulnerabilityidentifier cve vulnerabilitydetails ansi regex is vulnerable to inefficient regular expression complexity vulnerabilityurl
| 0
|
90,708
| 11,426,404,761
|
IssuesEvent
|
2020-02-03 21:52:16
|
graphql-nexus/nexus-future
|
https://api.github.com/repos/graphql-nexus/nexus-future
|
opened
|
schema namespace and builders' names
|
scope/core scope/schema type/design-discussion
|
## Problem
- currently:
```ts
import { schema } from 'nexus-future'
schema.objectType
schema.enumType
schema.interfaceType
schema.inputObjectType
schema.idArg
schema.booleanArg
```
- `schema` is long
- `Type` suffix is long
- `schema` doesn't say graphql, but it is for graphql
- some users want to put their REST API into the framework as well, REST needs schema stuff too, like swagger or JSON Schema. We're currently squatting a concept/name that prohibits peaceful coexistence with other kinds of schema
- too much terminology: schema, graphql, type
## Maybe Solution(s)
### Namespace Naming
Also suggested here is the name convention of the module
#### `graphql`
```ts
// graphql.ts
// graphql/a.ts
import { graphql } from 'nexus-future'
graphql.queryType({
definition(t) {
t.field('hello', {
type: 'World',
arg: {
id: graphql.idArg({ ... })
}
resolve() {
...
},
})
},
})
graphql.objectType({
name: 'World',
definition(t) {
t.string('name')
},
})
```
#### `gql`
```ts
// gql.ts
// gql/a.ts
import { gql } from 'nexus-future'
gql.queryType({
definition(t) {
t.field('hello', {
type: 'World',
arg: {
id: gql.idArg({ ... })
}
resolve() {
...
},
})
},
})
gql.objectType({
name: 'World',
definition(t) {
t.string('name')
},
})
```
### Builder Naming
#### Drop `Type` suffix & `arg` namespace
```
gql.object
gql.enum
gql.interface
gql.input
gql.arg.id
gql.arg.bool
```
```ts
import { gql } from 'nexus-future'
gql.query({
definition(t) {
t.field('hello', {
type: 'World',
arg: {
id: gql.arg.id({ ... })
}
resolve() {
...
},
})
},
})
gql.object({
name: 'World',
definition(t) {
t.string('name')
},
})
```
_with `graphql` namespace_
```
graphql.object
graphql.enum
graphql.interface
graphql.input
graphql.arg.id
graphql.arg.bool
```
```ts
import { graphql } from 'nexus-future'
graphql.query({
definition(t) {
t.field('hello', {
type: 'World',
arg: {
id: graphql.arg.id({ ... })
}
resolve() {
...
},
})
},
})
graphql.object({
name: 'World',
definition(t) {
t.string('name')
},
})
```
#### Drop `Type` suffix & `arg` namespace & Pascal case
Because closer to SDL!
```
gql.Object
gql.Enum
gql.Interface
gql.Input
gql.arg.ID
gql.arg.Bool
```
```ts
import { gql } from 'nexus-future'
gql.Query({
definition(t) {
t.field('hello', {
type: 'World',
arg: {
id: gql.arg.ID({ ... })
}
resolve() {
...
},
})
},
})
gql.Object({
name: 'World',
definition(t) {
t.string('name')
},
})
```
_with `graphql` namespace_
```
graphql.Object
graphql.Enum
graphql.Interface
graphql.Input
graphql.arg.ID
graphql.arg.Bool
```
```ts
import { graphql } from 'nexus-future'
graphql.Query({
definition(t) {
t.field('hello', {
type: 'World',
arg: {
id: graphql.arg.ID({ ... })
}
resolve() {
...
},
})
},
})
graphql.Object({
name: 'World',
definition(t) {
t.string('name')
},
})
```
|
1.0
|
schema namespace and builders' names - ## Problem
- currently:
```ts
import { schema } from 'nexus-future'
schema.objectType
schema.enumType
schema.interfaceType
schema.inputObjectType
schema.idArg
schema.booleanArg
```
- `schema` is long
- `Type` suffix is long
- `schema` doesn't say graphql, but it is for graphql
- some users want to put their REST API into the framework as well, REST needs schema stuff too, like swagger or JSON Schema. We're currently squatting a concept/name that prohibits peaceful coexistence with other kinds of schema
- too much terminology: schema, graphql, type
## Maybe Solution(s)
### Namespace Naming
Also suggested here is the name convention of the module
#### `graphql`
```ts
// graphql.ts
// graphql/a.ts
import { graphql } from 'nexus-future'
graphql.queryType({
definition(t) {
t.field('hello', {
type: 'World',
arg: {
id: graphql.idArg({ ... })
}
resolve() {
...
},
})
},
})
graphql.objectType({
name: 'World',
definition(t) {
t.string('name')
},
})
```
#### `gql`
```ts
// gql.ts
// gql/a.ts
import { gql } from 'nexus-future'
gql.queryType({
definition(t) {
t.field('hello', {
type: 'World',
arg: {
id: gql.idArg({ ... })
}
resolve() {
...
},
})
},
})
gql.objectType({
name: 'World',
definition(t) {
t.string('name')
},
})
```
### Builder Naming
#### Drop `Type` suffix & `arg` namespace
```
gql.object
gql.enum
gql.interface
gql.input
gql.arg.id
gql.arg.bool
```
```ts
import { gql } from 'nexus-future'
gql.query({
definition(t) {
t.field('hello', {
type: 'World',
arg: {
id: gql.arg.id({ ... })
}
resolve() {
...
},
})
},
})
gql.object({
name: 'World',
definition(t) {
t.string('name')
},
})
```
_with `graphql` namespace_
```
graphql.object
graphql.enum
graphql.interface
graphql.input
graphql.arg.id
graphql.arg.bool
```
```ts
import { graphql } from 'nexus-future'
graphql.query({
definition(t) {
t.field('hello', {
type: 'World',
arg: {
id: graphql.arg.id({ ... })
}
resolve() {
...
},
})
},
})
graphql.object({
name: 'World',
definition(t) {
t.string('name')
},
})
```
#### Drop `Type` suffix & `arg` namespace & Pascal case
Because closer to SDL!
```
gql.Object
gql.Enum
gql.Interface
gql.Input
gql.arg.ID
gql.arg.Bool
```
```ts
import { gql } from 'nexus-future'
gql.Query({
definition(t) {
t.field('hello', {
type: 'World',
arg: {
id: gql.arg.ID({ ... })
}
resolve() {
...
},
})
},
})
gql.Object({
name: 'World',
definition(t) {
t.string('name')
},
})
```
_with `graphql` namespace_
```
graphql.Object
graphql.Enum
graphql.Interface
graphql.Input
graphql.arg.ID
graphql.arg.Bool
```
```ts
import { graphql } from 'nexus-future'
graphql.Query({
definition(t) {
t.field('hello', {
type: 'World',
arg: {
id: graphql.arg.ID({ ... })
}
resolve() {
...
},
})
},
})
graphql.Object({
name: 'World',
definition(t) {
t.string('name')
},
})
```
|
design
|
schema namespace and builders names problem currently ts import schema from nexus future schema objecttype schema enumtype schema interfacetype schema inputobjecttype schema idarg schema booleanarg schema is long type suffix is long schema doesn t say graphql but it is for graphql some users want to put their rest api into the framework as well rest needs schema stuff too like swagger or json schema we re currently squatting a concept name that prohibits peaceful coexistence with other kinds of schema too much terminology schema graphql type maybe solution s namespace naming also suggested here is the name convention of the module graphql ts graphql ts graphql a ts import graphql from nexus future graphql querytype definition t t field hello type world arg id graphql idarg resolve graphql objecttype name world definition t t string name gql ts gql ts gql a ts import gql from nexus future gql querytype definition t t field hello type world arg id gql idarg resolve gql objecttype name world definition t t string name builder naming drop type suffix arg namespace gql object gql enum gql interface gql input gql arg id gql arg bool ts import gql from nexus future gql query definition t t field hello type world arg id gql arg id resolve gql object name world definition t t string name with graphql namespace graphql object graphql enum graphql interface graphql input graphql arg id graphql arg bool ts import graphql from nexus future graphql query definition t t field hello type world arg id graphql arg id resolve graphql object name world definition t t string name drop type suffix arg namespace pascal case because closer to sdl gql object gql enum gql interface gql input gql arg id gql arg bool ts import gql from nexus future gql query definition t t field hello type world arg id gql arg id resolve gql object name world definition t t string name with graphql namespace graphql object graphql enum graphql interface graphql input graphql arg id graphql arg bool ts import graphql from nexus future graphql query definition t t field hello type world arg id graphql arg id resolve graphql object name world definition t t string name
| 1
|
124,488
| 26,467,271,369
|
IssuesEvent
|
2023-01-17 01:55:21
|
spring-projects/sts4
|
https://api.github.com/repos/spring-projects/sts4
|
closed
|
Unknown property error shown in application.yml when using java records
|
type: bug theme: property-editing-support for: eclipse for: vscode
|
**Describe the bug**
Given the following classes:
```java
@ConfigurationProperties("application.security")
public record SecurityProperties(List<UserProperties> users) {
}
```
```java
public record UserProperties(String name, String password, List<String> roles) {
}
```
and the following `application.yml`
```yaml
application:
security:
users:
- name: "user"
password: "password"
- name: "admin"
password: "secret"
roles: ["admin"]
```
The `application.yml` editor will show:
`Unknown property 'name' for type 'com.example.security.UserProperties'`
If java classes with `@ConstructorBinding` is used, no problems are identified.
**To Reproduce**
As described above.
**Sample**
https://github.com/philwebb/whats-new-in-spring-boot-3-0
|
1.0
|
Unknown property error shown in application.yml when using java records - **Describe the bug**
Given the following classes:
```java
@ConfigurationProperties("application.security")
public record SecurityProperties(List<UserProperties> users) {
}
```
```java
public record UserProperties(String name, String password, List<String> roles) {
}
```
and the following `application.yml`
```yaml
application:
security:
users:
- name: "user"
password: "password"
- name: "admin"
password: "secret"
roles: ["admin"]
```
The `application.yml` editor will show:
`Unknown property 'name' for type 'com.example.security.UserProperties'`
If java classes with `@ConstructorBinding` is used, no problems are identified.
**To Reproduce**
As described above.
**Sample**
https://github.com/philwebb/whats-new-in-spring-boot-3-0
|
non_design
|
unknown property error shown in application yml when using java records describe the bug given the following classes java configurationproperties application security public record securityproperties list users java public record userproperties string name string password list roles and the following application yml yaml application security users name user password password name admin password secret roles the application yml editor will show unknown property name for type com example security userproperties if java classes with constructorbinding is used no problems are identified to reproduce as described above sample
| 0
|
94,764
| 10,853,066,698
|
IssuesEvent
|
2019-11-13 14:03:23
|
cncf/cnf-testbed
|
https://api.github.com/repos/cncf/cnf-testbed
|
closed
|
Add NSM gw-routers example to CNF Testbed
|
documentation k8s nsm use case
|
Goal: Add [NSM gw-rotuers](https://github.com/networkservicemesh/examples/tree/master/examples/gw-routers) example to CNF Testbed as discussed on weekly meetings.
```
+---------+ +--------+ +--------+ +---------+
10.60.0.0/24 | | 10.60.1.0/24 | | 10.60.2.0/24 | | 10.60.3.0/24 | | 10.60.4.0/24
--------------+ Gateway +--------------> Router +--------------> Router +--------------> Gateway +--------------
| L | | L | | R | | R |
+---------+ +--------+ +--------+ +---------+
```
Tasks:
- [x] Create yaml description file(s) for example
- External endpoints (gateways) will likely need a some modification to run on CNF Testbed deployment
- Still relies on running privileged for NIC interfaces (using vfio-pci driver)
- [x] Test connectivity using ping
- [x] Add documentation
|
1.0
|
Add NSM gw-routers example to CNF Testbed - Goal: Add [NSM gw-rotuers](https://github.com/networkservicemesh/examples/tree/master/examples/gw-routers) example to CNF Testbed as discussed on weekly meetings.
```
+---------+ +--------+ +--------+ +---------+
10.60.0.0/24 | | 10.60.1.0/24 | | 10.60.2.0/24 | | 10.60.3.0/24 | | 10.60.4.0/24
--------------+ Gateway +--------------> Router +--------------> Router +--------------> Gateway +--------------
| L | | L | | R | | R |
+---------+ +--------+ +--------+ +---------+
```
Tasks:
- [x] Create yaml description file(s) for example
- External endpoints (gateways) will likely need a some modification to run on CNF Testbed deployment
- Still relies on running privileged for NIC interfaces (using vfio-pci driver)
- [x] Test connectivity using ping
- [x] Add documentation
|
non_design
|
add nsm gw routers example to cnf testbed goal add example to cnf testbed as discussed on weekly meetings gateway router router gateway l l r r tasks create yaml description file s for example external endpoints gateways will likely need a some modification to run on cnf testbed deployment still relies on running privileged for nic interfaces using vfio pci driver test connectivity using ping add documentation
| 0
|
5,622
| 8,477,035,089
|
IssuesEvent
|
2018-10-25 00:48:43
|
ncbo/bioportal-project
|
https://api.github.com/repos/ncbo/bioportal-project
|
closed
|
FASTO: Initial submission failed to parse
|
in progress ontology processing problem
|
User reached out to us on the support list to indicate that their initial upload of the [FASTO ontology](http://bioportal.bioontology.org/ontologies/FASTO) didn't parse.
There were two issues that I asked the user to address:
1). The ontology was submitted as a ZIP file, but didn't follow our required convention where the name of the ZIP file matches the name of the main ontology file. User fixed this issue and submitted a new ZIP file.
2). The parsing process then failed with the following error:
```
"Illegal Element Name (Element Is Not A QName): http://www.co-ode.org/ontologies/ont.owl#DDO:0000002”
```
There were 3 occurrences in the FASTO.owl source file of the above URI, where the colon character isn’t allowed in the end fragment (DDO:0000002). User fixed this issue and submitted a new version.
|
1.0
|
FASTO: Initial submission failed to parse - User reached out to us on the support list to indicate that their initial upload of the [FASTO ontology](http://bioportal.bioontology.org/ontologies/FASTO) didn't parse.
There were two issues that I asked the user to address:
1). The ontology was submitted as a ZIP file, but didn't follow our required convention where the name of the ZIP file matches the name of the main ontology file. User fixed this issue and submitted a new ZIP file.
2). The parsing process then failed with the following error:
```
"Illegal Element Name (Element Is Not A QName): http://www.co-ode.org/ontologies/ont.owl#DDO:0000002”
```
There were 3 occurrences in the FASTO.owl source file of the above URI, where the colon character isn’t allowed in the end fragment (DDO:0000002). User fixed this issue and submitted a new version.
|
non_design
|
fasto initial submission failed to parse user reached out to us on the support list to indicate that their initial upload of the didn t parse there were two issues that i asked the user to address the ontology was submitted as a zip file but didn t follow our required convention where the name of the zip file matches the name of the main ontology file user fixed this issue and submitted a new zip file the parsing process then failed with the following error illegal element name element is not a qname there were occurrences in the fasto owl source file of the above uri where the colon character isn’t allowed in the end fragment ddo user fixed this issue and submitted a new version
| 0
|
36,357
| 5,049,316,921
|
IssuesEvent
|
2016-12-20 15:35:30
|
leihs/leihs
|
https://api.github.com/repos/leihs/leihs
|
closed
|
Correct behaviour in regards to visibility of information in request and export
|
bug procurement test passed zhdk
|
How it should be for an existing request:
Admin can view everything but can not edit.
Inspector can always view everything but edit in his own categories.
**Approved quantity / Inspection comment:**
Requesting Phase / Inspection Phase:
- inspector in own categories: editable
- requester: label shown, value not shown
Budget Period has ended:
- requester and inspector: label shown, value shown (not editable)
**order amount / Inspector's Priority:**
Requesting Phase / Inspection Phase:
- inspector in own categories: editable
- requester: label not shown, value not shown
Budget Period has ended:
- inspector: label shown, value shown (not editable)
- requester: label not shown, value not shown
|
1.0
|
Correct behaviour in regards to visibility of information in request and export - How it should be for an existing request:
Admin can view everything but can not edit.
Inspector can always view everything but edit in his own categories.
**Approved quantity / Inspection comment:**
Requesting Phase / Inspection Phase:
- inspector in own categories: editable
- requester: label shown, value not shown
Budget Period has ended:
- requester and inspector: label shown, value shown (not editable)
**order amount / Inspector's Priority:**
Requesting Phase / Inspection Phase:
- inspector in own categories: editable
- requester: label not shown, value not shown
Budget Period has ended:
- inspector: label shown, value shown (not editable)
- requester: label not shown, value not shown
|
non_design
|
correct behaviour in regards to visibility of information in request and export how it should be for an existing request admin can view everything but can not edit inspector can always view everything but edit in his own categories approved quantity inspection comment requesting phase inspection phase inspector in own categories editable requester label shown value not shown budget period has ended requester and inspector label shown value shown not editable order amount inspector s priority requesting phase inspection phase inspector in own categories editable requester label not shown value not shown budget period has ended inspector label shown value shown not editable requester label not shown value not shown
| 0
|
103,398
| 12,893,076,793
|
IssuesEvent
|
2020-07-13 20:52:10
|
microsoft/vscode
|
https://api.github.com/repos/microsoft/vscode
|
closed
|
envFile support in launch.json not working with input variable reference
|
*as-designed
|
<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Describe the feature you'd like. -->
When I add `envFile` support to the launch.json, all works as expected. However, the environment variables are not available for use in variables. E.g.
```
{
"name": "Deploy",
"program": "${workspaceFolder}/dist/index.js",
"request": "launch",
"envFile": "${workspaceFolder}/.env",
"sourceMaps": true,
"console": "integratedTerminal",
"args": [
"deploy",
"${env:MODULE}",
"-v",
"${env:VERSION}"
],
"skipFiles": [
"<node_internals>/**"
],
"type": "node"
}
```
This looks like an ordering issue, the args are evaluated prior to the env file being loaded, as the command is always run with empty parameters. Once the program runs, all the variables are available.
We are using this to debug common command line runs, and would rather not hard code all the variations into the file. I'm aware of the "inputs" which works quite well, however due to running this 100s of times as we debug, we don't want to re-enter the arguments in the prompt continuously. Any other suggestions welcome, however in my view it would be much more intuitive if the envFile was loaded prior to evaluating the variables.
|
1.0
|
envFile support in launch.json not working with input variable reference - <!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Describe the feature you'd like. -->
When I add `envFile` support to the launch.json, all works as expected. However, the environment variables are not available for use in variables. E.g.
```
{
"name": "Deploy",
"program": "${workspaceFolder}/dist/index.js",
"request": "launch",
"envFile": "${workspaceFolder}/.env",
"sourceMaps": true,
"console": "integratedTerminal",
"args": [
"deploy",
"${env:MODULE}",
"-v",
"${env:VERSION}"
],
"skipFiles": [
"<node_internals>/**"
],
"type": "node"
}
```
This looks like an ordering issue, the args are evaluated prior to the env file being loaded, as the command is always run with empty parameters. Once the program runs, all the variables are available.
We are using this to debug common command line runs, and would rather not hard code all the variations into the file. I'm aware of the "inputs" which works quite well, however due to running this 100s of times as we debug, we don't want to re-enter the arguments in the prompt continuously. Any other suggestions welcome, however in my view it would be much more intuitive if the envFile was loaded prior to evaluating the variables.
|
design
|
envfile support in launch json not working with input variable reference when i add envfile support to the launch json all works as expected however the environment variables are not available for use in variables e g name deploy program workspacefolder dist index js request launch envfile workspacefolder env sourcemaps true console integratedterminal args deploy env module v env version skipfiles type node this looks like an ordering issue the args are evaluated prior to the env file being loaded as the command is always run with empty parameters once the program runs all the variables are available we are using this to debug common command line runs and would rather not hard code all the variations into the file i m aware of the inputs which works quite well however due to running this of times as we debug we don t want to re enter the arguments in the prompt continuously any other suggestions welcome however in my view it would be much more intuitive if the envfile was loaded prior to evaluating the variables
| 1
|
39,907
| 5,153,059,121
|
IssuesEvent
|
2017-01-14 07:05:40
|
metamaps/metamaps
|
https://api.github.com/repos/metamaps/metamaps
|
closed
|
Default name for new maps, and do they appear in the global list?
|
design needs discussion
|
I no longer think that we should add an incremental number to the default "untitled map"... (i.e. just leave it as such)
I do however think that all maps, even currently untitled ones, should show up in the global list so that others can be aware of them right away... and potentially choose to join in on the mapping.
|
1.0
|
Default name for new maps, and do they appear in the global list? - I no longer think that we should add an incremental number to the default "untitled map"... (i.e. just leave it as such)
I do however think that all maps, even currently untitled ones, should show up in the global list so that others can be aware of them right away... and potentially choose to join in on the mapping.
|
design
|
default name for new maps and do they appear in the global list i no longer think that we should add an incremental number to the default untitled map i e just leave it as such i do however think that all maps even currently untitled ones should show up in the global list so that others can be aware of them right away and potentially choose to join in on the mapping
| 1
|
19,429
| 10,354,376,311
|
IssuesEvent
|
2019-09-05 13:38:33
|
Accruent/robotframework-hub
|
https://api.github.com/repos/Accruent/robotframework-hub
|
opened
|
CVE-2019-11324 (High) detected in urllib3-1.24.1-py2.py3-none-any.whl
|
security vulnerability
|
## CVE-2019-11324 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>urllib3-1.24.1-py2.py3-none-any.whl</b></p></summary>
<p>HTTP library with thread-safe connection pooling, file post, and more.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/62/00/ee1d7de624db8ba7090d1226aebefab96a2c71cd5cfa7629d6ad3f61b79e/urllib3-1.24.1-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/62/00/ee1d7de624db8ba7090d1226aebefab96a2c71cd5cfa7629d6ad3f61b79e/urllib3-1.24.1-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /robotframework-hub/requirements.txt</p>
<p>Path to vulnerable library: /tmp/WhiteSource-ArchiveExtractor_e512a720-c4fd-4e08-9955-596c89fb9ab2/20190905133031_29498/20190905132950_depth_0/urllib3-1.24.1-py2.py3-none-any/urllib3,teSource-ArchiveExtractor_e512a720-c4fd-4e08-9955-596c89fb9ab2/20190905133031_29498/20190905132950_depth_0/urllib3-1.24.1-py2.py3-none-any/urllib3</p>
<p>
Dependency Hierarchy:
- :x: **urllib3-1.24.1-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Accruent/robotframework-hub/commit/971beb3d5aa8f2e98af662290c57bdfbea0dd5f2">971beb3d5aa8f2e98af662290c57bdfbea0dd5f2</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The urllib3 library before 1.24.2 for Python mishandles certain cases where the desired set of CA certificates is different from the OS store of CA certificates, which results in SSL connections succeeding in situations where a verification failure is the correct outcome. This is related to use of the ssl_context, ca_certs, or ca_certs_dir argument.
<p>Publish Date: 2019-04-18
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11324>CVE-2019-11324</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11324">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11324</a></p>
<p>Release Date: 2019-04-18</p>
<p>Fix Resolution: 1.24.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2019-11324 (High) detected in urllib3-1.24.1-py2.py3-none-any.whl - ## CVE-2019-11324 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>urllib3-1.24.1-py2.py3-none-any.whl</b></p></summary>
<p>HTTP library with thread-safe connection pooling, file post, and more.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/62/00/ee1d7de624db8ba7090d1226aebefab96a2c71cd5cfa7629d6ad3f61b79e/urllib3-1.24.1-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/62/00/ee1d7de624db8ba7090d1226aebefab96a2c71cd5cfa7629d6ad3f61b79e/urllib3-1.24.1-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /robotframework-hub/requirements.txt</p>
<p>Path to vulnerable library: /tmp/WhiteSource-ArchiveExtractor_e512a720-c4fd-4e08-9955-596c89fb9ab2/20190905133031_29498/20190905132950_depth_0/urllib3-1.24.1-py2.py3-none-any/urllib3,teSource-ArchiveExtractor_e512a720-c4fd-4e08-9955-596c89fb9ab2/20190905133031_29498/20190905132950_depth_0/urllib3-1.24.1-py2.py3-none-any/urllib3</p>
<p>
Dependency Hierarchy:
- :x: **urllib3-1.24.1-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Accruent/robotframework-hub/commit/971beb3d5aa8f2e98af662290c57bdfbea0dd5f2">971beb3d5aa8f2e98af662290c57bdfbea0dd5f2</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The urllib3 library before 1.24.2 for Python mishandles certain cases where the desired set of CA certificates is different from the OS store of CA certificates, which results in SSL connections succeeding in situations where a verification failure is the correct outcome. This is related to use of the ssl_context, ca_certs, or ca_certs_dir argument.
<p>Publish Date: 2019-04-18
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11324>CVE-2019-11324</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11324">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11324</a></p>
<p>Release Date: 2019-04-18</p>
<p>Fix Resolution: 1.24.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_design
|
cve high detected in none any whl cve high severity vulnerability vulnerable library none any whl http library with thread safe connection pooling file post and more library home page a href path to dependency file robotframework hub requirements txt path to vulnerable library tmp whitesource archiveextractor depth none any tesource archiveextractor depth none any dependency hierarchy x none any whl vulnerable library found in head commit a href vulnerability details the library before for python mishandles certain cases where the desired set of ca certificates is different from the os store of ca certificates which results in ssl connections succeeding in situations where a verification failure is the correct outcome this is related to use of the ssl context ca certs or ca certs dir argument publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
41,177
| 2,868,983,021
|
IssuesEvent
|
2015-06-05 22:22:05
|
dart-lang/pub
|
https://api.github.com/repos/dart-lang/pub
|
opened
|
add option to resolve -pre release and stable versions as same priority
|
enhancement Priority-Medium
|
<a href="https://github.com/sigmundch"><img src="https://avatars.githubusercontent.com/u/2049220?v=3" align="left" width="96" height="96"hspace="10"></img></a> **Issue by [sigmundch](https://github.com/sigmundch)**
_Originally opened as dart-lang/sdk#20529_
----
For example:
pub upgrade --give-me-the-latest-most-awesome-pre-release-features-I-can-get-my-hands-on-Thank-you
So if I have a dependency with a constraint ">= 1.0.0 < 2.0.0"
and both 1.1.0 and 1.2.0-alpha are available, I'd get 1.2.0-alpha.
|
1.0
|
add option to resolve -pre release and stable versions as same priority - <a href="https://github.com/sigmundch"><img src="https://avatars.githubusercontent.com/u/2049220?v=3" align="left" width="96" height="96"hspace="10"></img></a> **Issue by [sigmundch](https://github.com/sigmundch)**
_Originally opened as dart-lang/sdk#20529_
----
For example:
pub upgrade --give-me-the-latest-most-awesome-pre-release-features-I-can-get-my-hands-on-Thank-you
So if I have a dependency with a constraint ">= 1.0.0 < 2.0.0"
and both 1.1.0 and 1.2.0-alpha are available, I'd get 1.2.0-alpha.
|
non_design
|
add option to resolve pre release and stable versions as same priority issue by originally opened as dart lang sdk for example nbsp nbsp pub upgrade give me the latest most awesome pre release features i can get my hands on thank you so if i have a dependency with a constraint quot gt lt quot and both and alpha are available i d get alpha
| 0
|
179,153
| 30,175,111,842
|
IssuesEvent
|
2023-07-04 03:20:55
|
decidim/decidim
|
https://api.github.com/repos/decidim/decidim
|
closed
|
Redesign / Mobile: Cookie warning should appear on top of the nave menu
|
contract: redesign
|
Now it appears below:
<img width="971" alt="image" src="https://github.com/decidim/decidim/assets/24740/87270528-54a6-440e-8cf8-591dcd92e558">
|
1.0
|
Redesign / Mobile: Cookie warning should appear on top of the nave menu - Now it appears below:
<img width="971" alt="image" src="https://github.com/decidim/decidim/assets/24740/87270528-54a6-440e-8cf8-591dcd92e558">
|
design
|
redesign mobile cookie warning should appear on top of the nave menu now it appears below img width alt image src
| 1
|
148,526
| 23,357,126,476
|
IssuesEvent
|
2022-08-10 08:27:04
|
nymtech/team-product
|
https://api.github.com/repos/nymtech/team-product
|
closed
|
Wallet: Delegation - aligment, spacing, 3 dots menu and tooltips
|
desktop wallet design
|
Few things in this task
- Aligment of elements in table - different placement of texts and button in wallet
- Box title - (I will add this as a global change in another task) wrong size and thickness
- Size of delegate button
- Lack of tooltips for total delegations and rewards - they are prepared in NYM wallet page(delegation section)
- During undelegation, lack of position showing rewards, when you are undelegating you are also undelegating rewards not only stake
- DELEGATION 3 DOTS - R ICON for redeem and C ICON for Compound shoul be in bold not regular or semibold like now
- DELEGATION 3 DOTS - Icons should be alligned to top of text not centered:
- DELEGATION 3 DOTS - description for compound and reedem in smaller text and let's break it like in the design
- DELEGATION 3 DOTS - Delegate more, undelegate, redeem, compound, different thicness of font - should be bolder
Figma file:
https://www.figma.com/file/KiYKZnWeefSALAe0j2dAPI/Nym-Wallet?node-id=2086%3A34523
- [x] design
- [x] development
|
1.0
|
Wallet: Delegation - aligment, spacing, 3 dots menu and tooltips - Few things in this task
- Aligment of elements in table - different placement of texts and button in wallet
- Box title - (I will add this as a global change in another task) wrong size and thickness
- Size of delegate button
- Lack of tooltips for total delegations and rewards - they are prepared in NYM wallet page(delegation section)
- During undelegation, lack of position showing rewards, when you are undelegating you are also undelegating rewards not only stake
- DELEGATION 3 DOTS - R ICON for redeem and C ICON for Compound shoul be in bold not regular or semibold like now
- DELEGATION 3 DOTS - Icons should be alligned to top of text not centered:
- DELEGATION 3 DOTS - description for compound and reedem in smaller text and let's break it like in the design
- DELEGATION 3 DOTS - Delegate more, undelegate, redeem, compound, different thicness of font - should be bolder
Figma file:
https://www.figma.com/file/KiYKZnWeefSALAe0j2dAPI/Nym-Wallet?node-id=2086%3A34523
- [x] design
- [x] development
|
design
|
wallet delegation aligment spacing dots menu and tooltips few things in this task aligment of elements in table different placement of texts and button in wallet box title i will add this as a global change in another task wrong size and thickness size of delegate button lack of tooltips for total delegations and rewards they are prepared in nym wallet page delegation section during undelegation lack of position showing rewards when you are undelegating you are also undelegating rewards not only stake delegation dots r icon for redeem and c icon for compound shoul be in bold not regular or semibold like now delegation dots icons should be alligned to top of text not centered delegation dots description for compound and reedem in smaller text and let s break it like in the design delegation dots delegate more undelegate redeem compound different thicness of font should be bolder figma file design development
| 1
|
119,033
| 15,393,487,320
|
IssuesEvent
|
2021-03-03 16:46:39
|
liqd/a4-meinberlin
|
https://api.github.com/repos/liqd/a4-meinberlin
|
closed
|
long phase title for active phase
|
Prio: Low Type: UX/UI or design
|
**URL:** https://meinberlin-dev.liqd.net/projekte/testing-burgerhaushalt-2-phases/
**user:** any
**expected behaviour:**
**behaviour:**
**important screensize:**
**device & browser:**
**Comment/Question:** when phase title is long, should the "active" not rather be in the second line instead of a new extra and otherwise empty line? @mcastro-lqd what do you think?
Screenshot?
<img width="568" alt="Bildschirmfoto 2021-02-15 um 18 12 36" src="https://user-images.githubusercontent.com/35491681/107976350-b1f21f80-6fb9-11eb-8979-963268e0f0db.png">
<img width="568" alt="Bildschirmfoto 2021-02-15 um 18 13 06" src="https://user-images.githubusercontent.com/35491681/107976351-b3234c80-6fb9-11eb-8163-411dd2aa5d2d.png">
|
1.0
|
long phase title for active phase - **URL:** https://meinberlin-dev.liqd.net/projekte/testing-burgerhaushalt-2-phases/
**user:** any
**expected behaviour:**
**behaviour:**
**important screensize:**
**device & browser:**
**Comment/Question:** when phase title is long, should the "active" not rather be in the second line instead of a new extra and otherwise empty line? @mcastro-lqd what do you think?
Screenshot?
<img width="568" alt="Bildschirmfoto 2021-02-15 um 18 12 36" src="https://user-images.githubusercontent.com/35491681/107976350-b1f21f80-6fb9-11eb-8979-963268e0f0db.png">
<img width="568" alt="Bildschirmfoto 2021-02-15 um 18 13 06" src="https://user-images.githubusercontent.com/35491681/107976351-b3234c80-6fb9-11eb-8163-411dd2aa5d2d.png">
|
design
|
long phase title for active phase url user any expected behaviour behaviour important screensize device browser comment question when phase title is long should the active not rather be in the second line instead of a new extra and otherwise empty line mcastro lqd what do you think screenshot img width alt bildschirmfoto um src img width alt bildschirmfoto um src
| 1
|
51,852
| 6,552,402,698
|
IssuesEvent
|
2017-09-05 18:13:10
|
phetsims/equality-explorer
|
https://api.github.com/repos/phetsims/equality-explorer
|
closed
|
disabling the Organize button
|
design:general
|
This is the Organize button (herein "the button"), found on the scale:
I believe that we decided that the button should be disabled when (a) the scale is empty, or (b) the scale is already organized.
I’ve implemented the “scale is empty” requirement, which is very easy to detect. See for example [1.0.0-dev.9](http://www.colorado.edu/physics/phet/dev/html/equality-explorer/1.0.0-dev.9/equality-explorer_en.html).
Disabling the button when the scale becomes organized is a bit of a problem. Every time an item is added to (or removed from) the scale, we would need to compute whether the arrangement of items on the scale is organized. That’s going to be a relatively expensive algorithm. And since it's happening while the user is dragging something, it will impact responsiveness.
My recommendation is to disable the button when (a) the scale is empty, or (b) immediately after the button has been pressed. After pressing the button, it will be re-enabled as soon as an item is added to (or removed from) the scale, regardless of whether the arrangement of the items is “organized”.
This is obviously a compromise. Pressing the button may sometimes appear to do nothing. But (imo) that's preferable to impacting overall responsiveness of the sim.
@amanda-phet your thoughts?
|
1.0
|
disabling the Organize button - This is the Organize button (herein "the button"), found on the scale:
I believe that we decided that the button should be disabled when (a) the scale is empty, or (b) the scale is already organized.
I’ve implemented the “scale is empty” requirement, which is very easy to detect. See for example [1.0.0-dev.9](http://www.colorado.edu/physics/phet/dev/html/equality-explorer/1.0.0-dev.9/equality-explorer_en.html).
Disabling the button when the scale becomes organized is a bit of a problem. Every time an item is added to (or removed from) the scale, we would need to compute whether the arrangement of items on the scale is organized. That’s going to be a relatively expensive algorithm. And since it's happening while the user is dragging something, it will impact responsiveness.
My recommendation is to disable the button when (a) the scale is empty, or (b) immediately after the button has been pressed. After pressing the button, it will be re-enabled as soon as an item is added to (or removed from) the scale, regardless of whether the arrangement of the items is “organized”.
This is obviously a compromise. Pressing the button may sometimes appear to do nothing. But (imo) that's preferable to impacting overall responsiveness of the sim.
@amanda-phet your thoughts?
|
design
|
disabling the organize button this is the organize button herein the button found on the scale i believe that we decided that the button should be disabled when a the scale is empty or b the scale is already organized i’ve implemented the “scale is empty” requirement which is very easy to detect see for example disabling the button when the scale becomes organized is a bit of a problem every time an item is added to or removed from the scale we would need to compute whether the arrangement of items on the scale is organized that’s going to be a relatively expensive algorithm and since it s happening while the user is dragging something it will impact responsiveness my recommendation is to disable the button when a the scale is empty or b immediately after the button has been pressed after pressing the button it will be re enabled as soon as an item is added to or removed from the scale regardless of whether the arrangement of the items is “organized” this is obviously a compromise pressing the button may sometimes appear to do nothing but imo that s preferable to impacting overall responsiveness of the sim amanda phet your thoughts
| 1
|
2,766
| 2,714,006,774
|
IssuesEvent
|
2015-04-09 22:50:27
|
reidmorrison/semantic_logger
|
https://api.github.com/repos/reidmorrison/semantic_logger
|
closed
|
Tag logs with current Thread context information
|
Documentation
|
I would like to be able to tag logs with information retrieved from the context of the Thread that called the log method. Similar to how the `Thread.current_name` is appended but with custom information.
A use case for this would be tagging anything logged in a rack request context. For example, I use `Thread.current` to store a request's Id and it'd be useful to specify a configuration to ensure that request id gets tagged in all the logs.
Right now this is possible if we wrap the log calls in the `tagged` method block and specify the request id. However, this is not possible in all instances.
This is also not possible using custom formatters since these get run in the context of the appender Thread which wouldn't have the information we need.
|
1.0
|
Tag logs with current Thread context information - I would like to be able to tag logs with information retrieved from the context of the Thread that called the log method. Similar to how the `Thread.current_name` is appended but with custom information.
A use case for this would be tagging anything logged in a rack request context. For example, I use `Thread.current` to store a request's Id and it'd be useful to specify a configuration to ensure that request id gets tagged in all the logs.
Right now this is possible if we wrap the log calls in the `tagged` method block and specify the request id. However, this is not possible in all instances.
This is also not possible using custom formatters since these get run in the context of the appender Thread which wouldn't have the information we need.
|
non_design
|
tag logs with current thread context information i would like to be able to tag logs with information retrieved from the context of the thread that called the log method similar to how the thread current name is appended but with custom information a use case for this would be tagging anything logged in a rack request context for example i use thread current to store a request s id and it d be useful to specify a configuration to ensure that request id gets tagged in all the logs right now this is possible if we wrap the log calls in the tagged method block and specify the request id however this is not possible in all instances this is also not possible using custom formatters since these get run in the context of the appender thread which wouldn t have the information we need
| 0
|
100,627
| 11,200,705,466
|
IssuesEvent
|
2020-01-03 22:45:04
|
vuetifyjs/vuetify
|
https://api.github.com/repos/vuetifyjs/vuetify
|
closed
|
[Documentation] Use of Breakpoints (and the use of sass variables in general) in scss
|
T: documentation sass
|
### Problem to solve
There is a lack to none of documentation regarding breakpoints use in scss.
Is this the correct way to do it in vuetify (for now at least) ?
@import '~vuetify/src/styles/settings/_variables';
@media #{map-get($display-breakpoints, 'md-and-down')} {
.custom-class {
display: block;
}
}
### Proposed solution
A documentation and utility function addition like in bootstrap
https://getbootstrap.com/docs/4.3/layout/overview/#responsive-breakpoints
@include media-breakpoint-down(md) {
.custom-class {
display: block;
}
}
<!-- generated by vuetify-issue-helper. DO NOT REMOVE -->
|
1.0
|
[Documentation] Use of Breakpoints (and the use of sass variables in general) in scss - ### Problem to solve
There is a lack to none of documentation regarding breakpoints use in scss.
Is this the correct way to do it in vuetify (for now at least) ?
@import '~vuetify/src/styles/settings/_variables';
@media #{map-get($display-breakpoints, 'md-and-down')} {
.custom-class {
display: block;
}
}
### Proposed solution
A documentation and utility function addition like in bootstrap
https://getbootstrap.com/docs/4.3/layout/overview/#responsive-breakpoints
@include media-breakpoint-down(md) {
.custom-class {
display: block;
}
}
<!-- generated by vuetify-issue-helper. DO NOT REMOVE -->
|
non_design
|
use of breakpoints and the use of sass variables in general in scss problem to solve there is a lack to none of documentation regarding breakpoints use in scss is this the correct way to do it in vuetify for now at least import vuetify src styles settings variables media map get display breakpoints md and down custom class display block proposed solution a documentation and utility function addition like in bootstrap include media breakpoint down md custom class display block
| 0
|
148,899
| 23,394,832,356
|
IssuesEvent
|
2022-08-11 21:49:39
|
department-of-veterans-affairs/va.gov-team
|
https://api.github.com/repos/department-of-veterans-affairs/va.gov-team
|
closed
|
Staging Review: Design System Team: Memorable Date & Month/Year date web components
|
Epic vsp-design-system-team governance-team
|
This is a staging review request for two date web components.
**Memorable date**
Design.va.gov: https://design.va.gov/components/form/memorable-date
Storybook: https://design.va.gov/storybook/?path=/docs/components-va-memorable-date--default
**Month Year - Date web component variant**
Design.va.gov: https://design.va.gov/components/form/date-input
Storybook: https://design.va.gov/storybook/?path=/docs/components-va-date--month-year
Product Outline: Design System Product Outline https://vfs.atlassian.net/wiki/spaces/DST/pages/2133557283
|
1.0
|
Staging Review: Design System Team: Memorable Date & Month/Year date web components - This is a staging review request for two date web components.
**Memorable date**
Design.va.gov: https://design.va.gov/components/form/memorable-date
Storybook: https://design.va.gov/storybook/?path=/docs/components-va-memorable-date--default
**Month Year - Date web component variant**
Design.va.gov: https://design.va.gov/components/form/date-input
Storybook: https://design.va.gov/storybook/?path=/docs/components-va-date--month-year
Product Outline: Design System Product Outline https://vfs.atlassian.net/wiki/spaces/DST/pages/2133557283
|
design
|
staging review design system team memorable date month year date web components this is a staging review request for two date web components memorable date design va gov storybook month year date web component variant design va gov storybook product outline design system product outline
| 1
|
35,194
| 30,829,828,353
|
IssuesEvent
|
2023-08-02 00:08:18
|
KhronosGroup/glslang
|
https://api.github.com/repos/KhronosGroup/glslang
|
closed
|
Compile error: message.h file not found
|
question Infrastructure
|
SPIRV-Tools remove the 'message.h' file recently
https://github.com/KhronosGroup/SPIRV-Tools/pull/1838
So the compile failed with "SPIRV/GlslangToSpv.cpp:59:14: fatal error: message.h: No such file or directory"
|
1.0
|
Compile error: message.h file not found - SPIRV-Tools remove the 'message.h' file recently
https://github.com/KhronosGroup/SPIRV-Tools/pull/1838
So the compile failed with "SPIRV/GlslangToSpv.cpp:59:14: fatal error: message.h: No such file or directory"
|
non_design
|
compile error message h file not found spirv tools remove the message h file recently so the compile failed with spirv glslangtospv cpp fatal error message h no such file or directory
| 0
|
316,485
| 23,634,254,258
|
IssuesEvent
|
2022-08-25 12:02:58
|
starlite-api/starlite
|
https://api.github.com/repos/starlite-api/starlite
|
closed
|
Documentation: Reference docs WIP tracking issue
|
documentation enhancement help wanted good first issue
|
This issue is for tracking work still to be completed for rollout of the reference api docs.
|
1.0
|
Documentation: Reference docs WIP tracking issue - This issue is for tracking work still to be completed for rollout of the reference api docs.
|
non_design
|
documentation reference docs wip tracking issue this issue is for tracking work still to be completed for rollout of the reference api docs
| 0
|
131,857
| 18,255,464,003
|
IssuesEvent
|
2021-10-03 00:29:13
|
ghc-dev/Tiffany-Rosario
|
https://api.github.com/repos/ghc-dev/Tiffany-Rosario
|
opened
|
CVE-2020-14330 (Medium) detected in ansible-2.9.9.tar.gz
|
security vulnerability
|
## CVE-2020-14330 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p></summary>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: Tiffany-Rosario/requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Tiffany-Rosario/commit/6bab73dc317273f1f8902491428f5d94c7c0390b">6bab73dc317273f1f8902491428f5d94c7c0390b</a></p>
<p>Found in base branch: <b>feature_branch</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>
An Improper Output Neutralization for Logs flaw was found in Ansible when using the uri module, where sensitive data is exposed to content and json output. This flaw allows an attacker to access the logs or outputs of performed tasks to read keys used in playbooks from other users within the uri module. The highest threat from this vulnerability is to data confidentiality.
<p>Publish Date: 2020-09-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-14330>CVE-2020-14330</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-14330">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-14330</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: 2.10.0</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Python","packageName":"ansible","packageVersion":"2.9.9","packageFilePaths":["/requirements.txt"],"isTransitiveDependency":false,"dependencyTree":"ansible:2.9.9","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.10.0"}],"baseBranches":["feature_branch"],"vulnerabilityIdentifier":"CVE-2020-14330","vulnerabilityDetails":"An Improper Output Neutralization for Logs flaw was found in Ansible when using the uri module, where sensitive data is exposed to content and json output. This flaw allows an attacker to access the logs or outputs of performed tasks to read keys used in playbooks from other users within the uri module. The highest threat from this vulnerability is to data confidentiality.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-14330","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Local","I":"None"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2020-14330 (Medium) detected in ansible-2.9.9.tar.gz - ## CVE-2020-14330 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ansible-2.9.9.tar.gz</b></p></summary>
<p>Radically simple IT automation</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz">https://files.pythonhosted.org/packages/00/5d/e10b83e0e6056dbd5b4809b451a191395175a57e3175ce04e35d9c5fc2a0/ansible-2.9.9.tar.gz</a></p>
<p>Path to dependency file: Tiffany-Rosario/requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **ansible-2.9.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Tiffany-Rosario/commit/6bab73dc317273f1f8902491428f5d94c7c0390b">6bab73dc317273f1f8902491428f5d94c7c0390b</a></p>
<p>Found in base branch: <b>feature_branch</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>
An Improper Output Neutralization for Logs flaw was found in Ansible when using the uri module, where sensitive data is exposed to content and json output. This flaw allows an attacker to access the logs or outputs of performed tasks to read keys used in playbooks from other users within the uri module. The highest threat from this vulnerability is to data confidentiality.
<p>Publish Date: 2020-09-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-14330>CVE-2020-14330</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-14330">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-14330</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: 2.10.0</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Python","packageName":"ansible","packageVersion":"2.9.9","packageFilePaths":["/requirements.txt"],"isTransitiveDependency":false,"dependencyTree":"ansible:2.9.9","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.10.0"}],"baseBranches":["feature_branch"],"vulnerabilityIdentifier":"CVE-2020-14330","vulnerabilityDetails":"An Improper Output Neutralization for Logs flaw was found in Ansible when using the uri module, where sensitive data is exposed to content and json output. This flaw allows an attacker to access the logs or outputs of performed tasks to read keys used in playbooks from other users within the uri module. The highest threat from this vulnerability is to data confidentiality.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-14330","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Local","I":"None"},"extraData":{}}</REMEDIATE> -->
|
non_design
|
cve medium detected in ansible tar gz cve medium severity vulnerability vulnerable library ansible tar gz radically simple it automation library home page a href path to dependency file tiffany rosario requirements txt path to vulnerable library requirements txt dependency hierarchy x ansible tar gz vulnerable library found in head commit a href found in base branch feature branch vulnerability details an improper output neutralization for logs flaw was found in ansible when using the uri module where sensitive data is exposed to content and json output this flaw allows an attacker to access the logs or outputs of performed tasks to read keys used in playbooks from other users within the uri module the highest threat from this vulnerability is to data confidentiality publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact 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 rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree ansible isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier cve vulnerabilitydetails an improper output neutralization for logs flaw was found in ansible when using the uri module where sensitive data is exposed to content and json output this flaw allows an attacker to access the logs or outputs of performed tasks to read keys used in playbooks from other users within the uri module the highest threat from this vulnerability is to data confidentiality vulnerabilityurl
| 0
|
103,565
| 12,950,365,480
|
IssuesEvent
|
2020-07-19 12:55:55
|
DarthVanger/NeuralNotes
|
https://api.github.com/repos/DarthVanger/NeuralNotes
|
closed
|
Add top bar with logo and buttons (just design, no functionality)
|
html / design
|
<img width="706" alt="1-topbar" src="https://user-images.githubusercontent.com/6686679/82253153-1021a180-9959-11ea-9c69-5c098d6c8289.png">
|
1.0
|
Add top bar with logo and buttons (just design, no functionality) - <img width="706" alt="1-topbar" src="https://user-images.githubusercontent.com/6686679/82253153-1021a180-9959-11ea-9c69-5c098d6c8289.png">
|
design
|
add top bar with logo and buttons just design no functionality img width alt topbar src
| 1
|
2,309
| 2,675,944,359
|
IssuesEvent
|
2015-03-25 15:19:08
|
Atmosphere/atmosphere
|
https://api.github.com/repos/Atmosphere/atmosphere
|
opened
|
New JDK Lambda Friendly API, replacing AtmosphereHandler/AtmosphereResourceEvent. Based on AtmosphereResourceEventListener callback
|
3.0.0 Documentation Enhancement
|
Make it super simple!
|
1.0
|
New JDK Lambda Friendly API, replacing AtmosphereHandler/AtmosphereResourceEvent. Based on AtmosphereResourceEventListener callback - Make it super simple!
|
non_design
|
new jdk lambda friendly api replacing atmospherehandler atmosphereresourceevent based on atmosphereresourceeventlistener callback make it super simple
| 0
|
112,960
| 14,349,539,538
|
IssuesEvent
|
2020-11-29 17:01:17
|
l0vey0u/ToDo
|
https://api.github.com/repos/l0vey0u/ToDo
|
opened
|
세준이랑 ToDo 기획하기
|
1년내에 Design OpenSource web 경험쌓기 프로그래밍
|
내가 만든 내 프로그램 1탄
음..
언어 와 속도와 디자인과 그런거?
적어도 디자인 시안이라도 잡아서 시작하는게 좋을 것 같기도 하다
|
1.0
|
세준이랑 ToDo 기획하기 - 내가 만든 내 프로그램 1탄
음..
언어 와 속도와 디자인과 그런거?
적어도 디자인 시안이라도 잡아서 시작하는게 좋을 것 같기도 하다
|
design
|
세준이랑 todo 기획하기 내가 만든 내 프로그램 음 언어 와 속도와 디자인과 그런거 적어도 디자인 시안이라도 잡아서 시작하는게 좋을 것 같기도 하다
| 1
|
736,212
| 25,462,897,954
|
IssuesEvent
|
2022-11-24 22:17:03
|
MasterCruelty/robbot
|
https://api.github.com/repos/MasterCruelty/robbot
|
closed
|
[2.0] Trenitalia api
|
enhancement help wanted good first issue question low priority
|
A few commands to show timetable of the Italian train you look for.
- [x] A command to check information about a specific train(delay etc.etc.)
- [x] A command to fetch data and show the next trains coming in a station by giving departure and arrival station
- [x] Showing ticket price
- [x] Showing the last detection of a train
|
1.0
|
[2.0] Trenitalia api - A few commands to show timetable of the Italian train you look for.
- [x] A command to check information about a specific train(delay etc.etc.)
- [x] A command to fetch data and show the next trains coming in a station by giving departure and arrival station
- [x] Showing ticket price
- [x] Showing the last detection of a train
|
non_design
|
trenitalia api a few commands to show timetable of the italian train you look for a command to check information about a specific train delay etc etc a command to fetch data and show the next trains coming in a station by giving departure and arrival station showing ticket price showing the last detection of a train
| 0
|
224,689
| 24,783,434,724
|
IssuesEvent
|
2022-10-24 07:50:59
|
sast-automation-dev/verademo-43
|
https://api.github.com/repos/sast-automation-dev/verademo-43
|
opened
|
bootstrap-3.3.2.min.js: 6 vulnerabilities (highest severity is: 6.1)
|
security vulnerability
|
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bootstrap-3.3.2.min.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: /app/src/main/webapp/resources/js/bootstrap.min.js</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-43/commit/43ed031cdf1afccad0d95270a077576732f1bf80">43ed031cdf1afccad0d95270a077576732f1bf80</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (bootstrap version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2019-8331](https://www.mend.io/vulnerability-database/CVE-2019-8331) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.2.min.js | Direct | bootstrap - 3.4.1,4.3.1;bootstrap-sass - 3.4.1,4.3.1 | ❌ |
| [CVE-2018-14040](https://www.mend.io/vulnerability-database/CVE-2018-14040) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.2.min.js | Direct | org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0 | ❌ |
| [CVE-2018-20677](https://www.mend.io/vulnerability-database/CVE-2018-20677) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.2.min.js | Direct | Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0 | ❌ |
| [CVE-2018-20676](https://www.mend.io/vulnerability-database/CVE-2018-20676) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.2.min.js | Direct | bootstrap - 3.4.0 | ❌ |
| [CVE-2018-14042](https://www.mend.io/vulnerability-database/CVE-2018-14042) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.2.min.js | Direct | org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0 | ❌ |
| [CVE-2016-10735](https://www.mend.io/vulnerability-database/CVE-2016-10735) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.2.min.js | Direct | 3.4.0 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-8331</summary>
### Vulnerable Library - <b>bootstrap-3.3.2.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: /app/src/main/webapp/resources/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-43/commit/43ed031cdf1afccad0d95270a077576732f1bf80">43ed031cdf1afccad0d95270a077576732f1bf80</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.1 and 4.3.x before 4.3.1, XSS is possible in the tooltip or popover data-template attribute.
<p>Publish Date: Feb 20, 2019 4:29:00 PM
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-8331>CVE-2019-8331</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: Feb 20, 2019 4:29:00 PM</p>
<p>Fix Resolution: bootstrap - 3.4.1,4.3.1;bootstrap-sass - 3.4.1,4.3.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-14040</summary>
### Vulnerable Library - <b>bootstrap-3.3.2.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: /app/src/main/webapp/resources/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-43/commit/43ed031cdf1afccad0d95270a077576732f1bf80">43ed031cdf1afccad0d95270a077576732f1bf80</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute.
<p>Publish Date: Jul 13, 2018 2:29:00 PM
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14040>CVE-2018-14040</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: Jul 13, 2018 2:29:00 PM</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-20677</summary>
### Vulnerable Library - <b>bootstrap-3.3.2.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: /app/src/main/webapp/resources/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-43/commit/43ed031cdf1afccad0d95270a077576732f1bf80">43ed031cdf1afccad0d95270a077576732f1bf80</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.
<p>Publish Date: Jan 9, 2019 5:29:00 AM
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-20677>CVE-2018-20677</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677</a></p>
<p>Release Date: Jan 9, 2019 5:29:00 AM</p>
<p>Fix Resolution: Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-20676</summary>
### Vulnerable Library - <b>bootstrap-3.3.2.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: /app/src/main/webapp/resources/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-43/commit/43ed031cdf1afccad0d95270a077576732f1bf80">43ed031cdf1afccad0d95270a077576732f1bf80</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.
<p>Publish Date: Jan 9, 2019 5:29:00 AM
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-20676>CVE-2018-20676</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676</a></p>
<p>Release Date: Jan 9, 2019 5:29:00 AM</p>
<p>Fix Resolution: bootstrap - 3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-14042</summary>
### Vulnerable Library - <b>bootstrap-3.3.2.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: /app/src/main/webapp/resources/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-43/commit/43ed031cdf1afccad0d95270a077576732f1bf80">43ed031cdf1afccad0d95270a077576732f1bf80</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.
<p>Publish Date: Jul 13, 2018 2:29:00 PM
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14042>CVE-2018-14042</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: Jul 13, 2018 2:29:00 PM</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2016-10735</summary>
### Vulnerable Library - <b>bootstrap-3.3.2.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: /app/src/main/webapp/resources/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-43/commit/43ed031cdf1afccad0d95270a077576732f1bf80">43ed031cdf1afccad0d95270a077576732f1bf80</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target attribute, a different vulnerability than CVE-2018-14041.
<p>Publish Date: Jan 9, 2019 5:29:00 AM
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-10735>CVE-2016-10735</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: Jan 9, 2019 5:29:00 AM</p>
<p>Fix Resolution: 3.4.0</p>
</p>
<p></p>
</details>
|
True
|
bootstrap-3.3.2.min.js: 6 vulnerabilities (highest severity is: 6.1) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bootstrap-3.3.2.min.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: /app/src/main/webapp/resources/js/bootstrap.min.js</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-43/commit/43ed031cdf1afccad0d95270a077576732f1bf80">43ed031cdf1afccad0d95270a077576732f1bf80</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (bootstrap version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2019-8331](https://www.mend.io/vulnerability-database/CVE-2019-8331) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.2.min.js | Direct | bootstrap - 3.4.1,4.3.1;bootstrap-sass - 3.4.1,4.3.1 | ❌ |
| [CVE-2018-14040](https://www.mend.io/vulnerability-database/CVE-2018-14040) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.2.min.js | Direct | org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0 | ❌ |
| [CVE-2018-20677](https://www.mend.io/vulnerability-database/CVE-2018-20677) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.2.min.js | Direct | Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0 | ❌ |
| [CVE-2018-20676](https://www.mend.io/vulnerability-database/CVE-2018-20676) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.2.min.js | Direct | bootstrap - 3.4.0 | ❌ |
| [CVE-2018-14042](https://www.mend.io/vulnerability-database/CVE-2018-14042) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.2.min.js | Direct | org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0 | ❌ |
| [CVE-2016-10735](https://www.mend.io/vulnerability-database/CVE-2016-10735) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.3.2.min.js | Direct | 3.4.0 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-8331</summary>
### Vulnerable Library - <b>bootstrap-3.3.2.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: /app/src/main/webapp/resources/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-43/commit/43ed031cdf1afccad0d95270a077576732f1bf80">43ed031cdf1afccad0d95270a077576732f1bf80</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.1 and 4.3.x before 4.3.1, XSS is possible in the tooltip or popover data-template attribute.
<p>Publish Date: Feb 20, 2019 4:29:00 PM
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-8331>CVE-2019-8331</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: Feb 20, 2019 4:29:00 PM</p>
<p>Fix Resolution: bootstrap - 3.4.1,4.3.1;bootstrap-sass - 3.4.1,4.3.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-14040</summary>
### Vulnerable Library - <b>bootstrap-3.3.2.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: /app/src/main/webapp/resources/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-43/commit/43ed031cdf1afccad0d95270a077576732f1bf80">43ed031cdf1afccad0d95270a077576732f1bf80</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute.
<p>Publish Date: Jul 13, 2018 2:29:00 PM
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14040>CVE-2018-14040</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: Jul 13, 2018 2:29:00 PM</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-20677</summary>
### Vulnerable Library - <b>bootstrap-3.3.2.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: /app/src/main/webapp/resources/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-43/commit/43ed031cdf1afccad0d95270a077576732f1bf80">43ed031cdf1afccad0d95270a077576732f1bf80</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.
<p>Publish Date: Jan 9, 2019 5:29:00 AM
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-20677>CVE-2018-20677</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677</a></p>
<p>Release Date: Jan 9, 2019 5:29:00 AM</p>
<p>Fix Resolution: Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-20676</summary>
### Vulnerable Library - <b>bootstrap-3.3.2.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: /app/src/main/webapp/resources/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-43/commit/43ed031cdf1afccad0d95270a077576732f1bf80">43ed031cdf1afccad0d95270a077576732f1bf80</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.
<p>Publish Date: Jan 9, 2019 5:29:00 AM
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-20676>CVE-2018-20676</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676</a></p>
<p>Release Date: Jan 9, 2019 5:29:00 AM</p>
<p>Fix Resolution: bootstrap - 3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-14042</summary>
### Vulnerable Library - <b>bootstrap-3.3.2.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: /app/src/main/webapp/resources/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-43/commit/43ed031cdf1afccad0d95270a077576732f1bf80">43ed031cdf1afccad0d95270a077576732f1bf80</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.
<p>Publish Date: Jul 13, 2018 2:29:00 PM
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14042>CVE-2018-14042</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: Jul 13, 2018 2:29:00 PM</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2016-10735</summary>
### Vulnerable Library - <b>bootstrap-3.3.2.min.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.2/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: /app/src/main/webapp/resources/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/verademo-43/commit/43ed031cdf1afccad0d95270a077576732f1bf80">43ed031cdf1afccad0d95270a077576732f1bf80</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target attribute, a different vulnerability than CVE-2018-14041.
<p>Publish Date: Jan 9, 2019 5:29:00 AM
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-10735>CVE-2016-10735</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: Jan 9, 2019 5:29:00 AM</p>
<p>Fix Resolution: 3.4.0</p>
</p>
<p></p>
</details>
|
non_design
|
bootstrap min js vulnerabilities highest severity is vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library app src main webapp resources js bootstrap min js found in head commit a href vulnerabilities cve severity cvss dependency type fixed in bootstrap version remediation available medium bootstrap min js direct bootstrap bootstrap sass medium bootstrap min js direct org webjars npm bootstrap org webjars bootstrap medium bootstrap min js direct bootstrap nordron angulartemplate dynamic net express projecttemplates dotnetng template znxtapp core module theme beta jmeter medium bootstrap min js direct bootstrap medium bootstrap min js direct org webjars npm bootstrap org webjars bootstrap medium bootstrap min js direct details cve vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library app src main webapp resources js bootstrap min js dependency hierarchy x bootstrap min js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap before and x before xss is possible in the tooltip or popover data template attribute publish date feb pm url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version release date feb pm fix resolution bootstrap bootstrap sass cve vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library app src main webapp resources js bootstrap min js dependency hierarchy x bootstrap min js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap before xss is possible in the collapse data parent attribute publish date jul pm url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version release date jul pm fix resolution org webjars npm bootstrap org webjars bootstrap cve vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library app src main webapp resources js bootstrap min js dependency hierarchy x bootstrap min js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap before xss is possible in the affix configuration target property publish date jan am url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date jan am fix resolution bootstrap nordron angulartemplate dynamic net express projecttemplates dotnetng template znxtapp core module theme beta jmeter cve vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library app src main webapp resources js bootstrap min js dependency hierarchy x bootstrap min js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap before xss is possible in the tooltip data viewport attribute publish date jan am url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date jan am fix resolution bootstrap cve vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library app src main webapp resources js bootstrap min js dependency hierarchy x bootstrap min js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap before xss is possible in the data container property of tooltip publish date jul pm url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version release date jul pm fix resolution org webjars npm bootstrap org webjars bootstrap cve vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library app src main webapp resources js bootstrap min js dependency hierarchy x bootstrap min js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap x before and x beta before beta xss is possible in the data target attribute a different vulnerability than cve publish date jan am url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version release date jan am fix resolution
| 0
|
88,363
| 11,088,471,108
|
IssuesEvent
|
2019-12-14 11:22:12
|
neo-project/neo-vm
|
https://api.github.com/repos/neo-project/neo-vm
|
closed
|
Slot opcodes
|
design
|
In NEO2, we have alt stack and several opcodes such as `TOALTSTACK` and `FROMALTSTACK` to support parameters, local variables, and static fields. But since we are not going to be compatible with NEO2, we can remove the alt stack.
By adding some new opcodes, we can make access to parameters, local variables, and static fields easier:
```
INITSLOT //Initialize the argument slot and the local variable list for the current execution context.
INITSSLOT //Initialize the static field list for the current execution context.
LDARG //Loads the argument at a specified index onto the evaluation stack.
STARG //Stores the value on top of the evaluation stack in the argument slot at a specified index.
LDLOC //Loads the local variable at a specified index onto the evaluation stack.
STLOC //Stores the value on top of the evaluation stack in the local variable list at a specified index.
LDSFLD //Loads the static field at a specified index onto the evaluation stack.
STSFLD //Stores the value on top of the evaluation stack in the static field list at a specified index.
```
The argument slot and local variable list will be automatically cleaned up when `RET` is executed. The static field list will be automatically cleaned up when the last execution context belonging to the current contract is unloaded.
This way, we can completely remove alt stack and related opcodes. The implementation of the compiler will also be more convenient.
|
1.0
|
Slot opcodes - In NEO2, we have alt stack and several opcodes such as `TOALTSTACK` and `FROMALTSTACK` to support parameters, local variables, and static fields. But since we are not going to be compatible with NEO2, we can remove the alt stack.
By adding some new opcodes, we can make access to parameters, local variables, and static fields easier:
```
INITSLOT //Initialize the argument slot and the local variable list for the current execution context.
INITSSLOT //Initialize the static field list for the current execution context.
LDARG //Loads the argument at a specified index onto the evaluation stack.
STARG //Stores the value on top of the evaluation stack in the argument slot at a specified index.
LDLOC //Loads the local variable at a specified index onto the evaluation stack.
STLOC //Stores the value on top of the evaluation stack in the local variable list at a specified index.
LDSFLD //Loads the static field at a specified index onto the evaluation stack.
STSFLD //Stores the value on top of the evaluation stack in the static field list at a specified index.
```
The argument slot and local variable list will be automatically cleaned up when `RET` is executed. The static field list will be automatically cleaned up when the last execution context belonging to the current contract is unloaded.
This way, we can completely remove alt stack and related opcodes. The implementation of the compiler will also be more convenient.
|
design
|
slot opcodes in we have alt stack and several opcodes such as toaltstack and fromaltstack to support parameters local variables and static fields but since we are not going to be compatible with we can remove the alt stack by adding some new opcodes we can make access to parameters local variables and static fields easier initslot initialize the argument slot and the local variable list for the current execution context initsslot initialize the static field list for the current execution context ldarg loads the argument at a specified index onto the evaluation stack starg stores the value on top of the evaluation stack in the argument slot at a specified index ldloc loads the local variable at a specified index onto the evaluation stack stloc stores the value on top of the evaluation stack in the local variable list at a specified index ldsfld loads the static field at a specified index onto the evaluation stack stsfld stores the value on top of the evaluation stack in the static field list at a specified index the argument slot and local variable list will be automatically cleaned up when ret is executed the static field list will be automatically cleaned up when the last execution context belonging to the current contract is unloaded this way we can completely remove alt stack and related opcodes the implementation of the compiler will also be more convenient
| 1
|
109,808
| 13,837,912,534
|
IssuesEvent
|
2020-10-14 04:59:45
|
Vuologist/bumpie
|
https://api.github.com/repos/Vuologist/bumpie
|
closed
|
Design - display and edit name in setting page
|
design
|
Figure out where to display name in settings page
Figure out where to put option to change name
need to break down into subtasks
|
1.0
|
Design - display and edit name in setting page - Figure out where to display name in settings page
Figure out where to put option to change name
need to break down into subtasks
|
design
|
design display and edit name in setting page figure out where to display name in settings page figure out where to put option to change name need to break down into subtasks
| 1
|
28,440
| 4,105,625,521
|
IssuesEvent
|
2016-06-06 02:55:12
|
brave/browser-laptop
|
https://api.github.com/repos/brave/browser-laptop
|
closed
|
Bookmarks Toolbar Spacing
|
design suggestion
|
In my Bookmarks Toolbar, I have folders (on the left) as well as individual bookmarks......the way it is now, the Folder names are being squeezed down to as little as ONE letter.......I believe the folders should have priority and always show their full name. Is this possible? Thanks!
|
1.0
|
Bookmarks Toolbar Spacing - In my Bookmarks Toolbar, I have folders (on the left) as well as individual bookmarks......the way it is now, the Folder names are being squeezed down to as little as ONE letter.......I believe the folders should have priority and always show their full name. Is this possible? Thanks!
|
design
|
bookmarks toolbar spacing in my bookmarks toolbar i have folders on the left as well as individual bookmarks the way it is now the folder names are being squeezed down to as little as one letter i believe the folders should have priority and always show their full name is this possible thanks
| 1
|
75,803
| 9,329,449,139
|
IssuesEvent
|
2019-03-28 02:26:06
|
Vidvox/isf.video
|
https://api.github.com/repos/Vidvox/isf.video
|
closed
|
New W I D E graphic for homepage
|
design
|
We're currently just using the one from the HAP site…
|
1.0
|
New W I D E graphic for homepage - We're currently just using the one from the HAP site…
|
design
|
new w i d e graphic for homepage we re currently just using the one from the hap site…
| 1
|
176,434
| 28,095,155,623
|
IssuesEvent
|
2023-03-30 15:19:27
|
department-of-veterans-affairs/vets-design-system-documentation
|
https://api.github.com/repos/department-of-veterans-affairs/vets-design-system-documentation
|
opened
|
Create new Icon for VA Icons that do not have a USWDS Replacement (Icons Audit follow up 3/3)
|
vsp-design-system-team
|
## Description
Follow up to the [Icons Audit](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/1476). This is 3 out of 3 categories for what to do with the VA icons that do not have a USWDS equivalent.
## Details
(Icons that do not have a USWDS replacements)
Road
Handshake
Dot Circle*
Play Circle*
Clipboard Check
Prescription Bottle
## Tasks
- [ ] Create new icon for each one of the icons listed above
## Acceptance Criteria
- [ ] Sketch file has been updated
- [ ] Icons have been approved by PO
|
1.0
|
Create new Icon for VA Icons that do not have a USWDS Replacement (Icons Audit follow up 3/3) - ## Description
Follow up to the [Icons Audit](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/1476). This is 3 out of 3 categories for what to do with the VA icons that do not have a USWDS equivalent.
## Details
(Icons that do not have a USWDS replacements)
Road
Handshake
Dot Circle*
Play Circle*
Clipboard Check
Prescription Bottle
## Tasks
- [ ] Create new icon for each one of the icons listed above
## Acceptance Criteria
- [ ] Sketch file has been updated
- [ ] Icons have been approved by PO
|
design
|
create new icon for va icons that do not have a uswds replacement icons audit follow up description follow up to the this is out of categories for what to do with the va icons that do not have a uswds equivalent details icons that do not have a uswds replacements road handshake dot circle play circle clipboard check prescription bottle tasks create new icon for each one of the icons listed above acceptance criteria sketch file has been updated icons have been approved by po
| 1
|
15,681
| 3,331,458,591
|
IssuesEvent
|
2015-11-11 15:56:41
|
owncloud/core
|
https://api.github.com/repos/owncloud/core
|
closed
|
Accessibility - possibly remove `tabindex=-1` on first link to index.php
|
design enhancement
|
I don't know why the `tabindex` attribute is set to `-1` on the logo index link in layout.user.php?
It makes this pretty important link inaccessible to keyboard usage (especially in Screen Readers).
I'd suggest removing it. In case it got in there for visual reasons, like not having a dotted outline around, there are accessible ways to deal with that. For example, by including an explicit `#owncloud:focus {}` rule.
|
1.0
|
Accessibility - possibly remove `tabindex=-1` on first link to index.php - I don't know why the `tabindex` attribute is set to `-1` on the logo index link in layout.user.php?
It makes this pretty important link inaccessible to keyboard usage (especially in Screen Readers).
I'd suggest removing it. In case it got in there for visual reasons, like not having a dotted outline around, there are accessible ways to deal with that. For example, by including an explicit `#owncloud:focus {}` rule.
|
design
|
accessibility possibly remove tabindex on first link to index php i don t know why the tabindex attribute is set to on the logo index link in layout user php it makes this pretty important link inaccessible to keyboard usage especially in screen readers i d suggest removing it in case it got in there for visual reasons like not having a dotted outline around there are accessible ways to deal with that for example by including an explicit owncloud focus rule
| 1
|
69,499
| 8,410,919,761
|
IssuesEvent
|
2018-10-12 12:19:59
|
pandas-dev/pandas
|
https://api.github.com/repos/pandas-dev/pandas
|
closed
|
Reductions for ExtensionArray
|
API Design Groupby Numeric
|
Creeping up to this in https://github.com/pandas-dev/pandas/pull/22345
A few questions
1. What should this look like for EA authors? What helpers can / should we provide?
2. How does this affect users? Specifically, assuming IntegerArray implements reductions, what's the dtype here?
```python
In [11]: df = pd.DataFrame({"A": ['a', 'b', 'a'], "B": pd.core.arrays.IntegerArray([1, 2, 3])})
In [12]: df.groupby("A").B.min().dtype
```
Is it `int64`, or should we preserve `Int64`?
We can also discuss transforms ( cumulative operations like cumsum, maybe things like `.shift`).
|
1.0
|
Reductions for ExtensionArray - Creeping up to this in https://github.com/pandas-dev/pandas/pull/22345
A few questions
1. What should this look like for EA authors? What helpers can / should we provide?
2. How does this affect users? Specifically, assuming IntegerArray implements reductions, what's the dtype here?
```python
In [11]: df = pd.DataFrame({"A": ['a', 'b', 'a'], "B": pd.core.arrays.IntegerArray([1, 2, 3])})
In [12]: df.groupby("A").B.min().dtype
```
Is it `int64`, or should we preserve `Int64`?
We can also discuss transforms ( cumulative operations like cumsum, maybe things like `.shift`).
|
design
|
reductions for extensionarray creeping up to this in a few questions what should this look like for ea authors what helpers can should we provide how does this affect users specifically assuming integerarray implements reductions what s the dtype here python in df pd dataframe a b pd core arrays integerarray in df groupby a b min dtype is it or should we preserve we can also discuss transforms cumulative operations like cumsum maybe things like shift
| 1
|
43,760
| 11,302,686,838
|
IssuesEvent
|
2020-01-17 18:16:31
|
wagerr/wagerr
|
https://api.github.com/repos/wagerr/wagerr
|
closed
|
Snap does not work on Raspbian
|
Bug Build system Linux/Unix Scripts and tools
|
While building snaps and automating install from new, have found that the current snap does not run on Raspbian 10 buster.
This may be down to configure flags in snapcraft.yaml...have editied it to use gitian-build configure flags and am building and testing on snapcraft store
|
1.0
|
Snap does not work on Raspbian - While building snaps and automating install from new, have found that the current snap does not run on Raspbian 10 buster.
This may be down to configure flags in snapcraft.yaml...have editied it to use gitian-build configure flags and am building and testing on snapcraft store
|
non_design
|
snap does not work on raspbian while building snaps and automating install from new have found that the current snap does not run on raspbian buster this may be down to configure flags in snapcraft yaml have editied it to use gitian build configure flags and am building and testing on snapcraft store
| 0
|
37,133
| 4,779,389,516
|
IssuesEvent
|
2016-10-27 22:18:54
|
CRUDParaSempre/DOCES
|
https://api.github.com/repos/CRUDParaSempre/DOCES
|
opened
|
Tela de Jogo - Sprites de Novos Cenários
|
Design Média Pendente Sub-tarefa ∞
|
Sub-tarefa de #22
Criar sprites de novos cenários para a lojinha
|
1.0
|
Tela de Jogo - Sprites de Novos Cenários - Sub-tarefa de #22
Criar sprites de novos cenários para a lojinha
|
design
|
tela de jogo sprites de novos cenários sub tarefa de criar sprites de novos cenários para a lojinha
| 1
|
181,621
| 21,664,406,851
|
IssuesEvent
|
2022-05-07 01:15:15
|
TERMINALSERVERORDERLY/dev
|
https://api.github.com/repos/TERMINALSERVERORDERLY/dev
|
closed
|
WS-2019-0333 (High) detected in handlebars-4.1.2.tgz - autoclosed
|
security vulnerability
|
## WS-2019-0333 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.1.2.tgz</b></p></summary>
<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-4.1.2.tgz">https://registry.npmjs.org/handlebars/-/handlebars-4.1.2.tgz</a></p>
<p>Path to dependency file: /dev/packages/dev/package.json</p>
<p>Path to vulnerable library: dev/packages/dev/node_modules/handlebars/package.json,dev/packages/dev/node_modules/handlebars/package.json</p>
<p>
Dependency Hierarchy:
- dev-0.24.6.tgz (Root Library)
- gitbook-plugin-include-codeblock-3.2.2.tgz
- :x: **handlebars-4.1.2.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In handlebars, versions prior to v4.5.3 are vulnerable to prototype pollution. Using a malicious template it's possbile to add or modify properties to the Object prototype. This can also lead to DOS and RCE in certain conditions.
<p>Publish Date: 2019-11-18
<p>URL: <a href=https://github.com/wycats/handlebars.js/commit/f7f05d7558e674856686b62a00cde5758f3b7a08>WS-2019-0333</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>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1325">https://www.npmjs.com/advisories/1325</a></p>
<p>Release Date: 2019-12-05</p>
<p>Fix Resolution: handlebars - 4.5.3</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-2019-0333 (High) detected in handlebars-4.1.2.tgz - autoclosed - ## WS-2019-0333 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.1.2.tgz</b></p></summary>
<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-4.1.2.tgz">https://registry.npmjs.org/handlebars/-/handlebars-4.1.2.tgz</a></p>
<p>Path to dependency file: /dev/packages/dev/package.json</p>
<p>Path to vulnerable library: dev/packages/dev/node_modules/handlebars/package.json,dev/packages/dev/node_modules/handlebars/package.json</p>
<p>
Dependency Hierarchy:
- dev-0.24.6.tgz (Root Library)
- gitbook-plugin-include-codeblock-3.2.2.tgz
- :x: **handlebars-4.1.2.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In handlebars, versions prior to v4.5.3 are vulnerable to prototype pollution. Using a malicious template it's possbile to add or modify properties to the Object prototype. This can also lead to DOS and RCE in certain conditions.
<p>Publish Date: 2019-11-18
<p>URL: <a href=https://github.com/wycats/handlebars.js/commit/f7f05d7558e674856686b62a00cde5758f3b7a08>WS-2019-0333</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>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1325">https://www.npmjs.com/advisories/1325</a></p>
<p>Release Date: 2019-12-05</p>
<p>Fix Resolution: handlebars - 4.5.3</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 handlebars tgz autoclosed ws high severity vulnerability vulnerable library handlebars tgz handlebars provides the power necessary to let you build semantic templates effectively with no frustration library home page a href path to dependency file dev packages dev package json path to vulnerable library dev packages dev node modules handlebars package json dev packages dev node modules handlebars package json dependency hierarchy dev tgz root library gitbook plugin include codeblock tgz x handlebars tgz vulnerable library vulnerability details in handlebars versions prior to are vulnerable to prototype pollution using a malicious template it s possbile to add or modify properties to the object prototype this can also lead to dos and rce in certain conditions publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution handlebars step up your open source security game with whitesource
| 0
|
111,159
| 14,012,413,788
|
IssuesEvent
|
2020-10-29 09:00:17
|
cyberark/conjur
|
https://api.github.com/repos/cyberark/conjur
|
closed
|
Refactoring authenticators code - Low level design for ValidateResourceRestrictions
|
kind/design
|
As part of developing GCP authenticator we have noticed that the `ValidateResourceRestrictions` component can be redesign to serve most of our authenticators: K8S, Azure, and GCP
Write a LLD which explains the change
**DoD**
- [ ] We have an LLD reviewed by the TEAM
|
1.0
|
Refactoring authenticators code - Low level design for ValidateResourceRestrictions - As part of developing GCP authenticator we have noticed that the `ValidateResourceRestrictions` component can be redesign to serve most of our authenticators: K8S, Azure, and GCP
Write a LLD which explains the change
**DoD**
- [ ] We have an LLD reviewed by the TEAM
|
design
|
refactoring authenticators code low level design for validateresourcerestrictions as part of developing gcp authenticator we have noticed that the validateresourcerestrictions component can be redesign to serve most of our authenticators azure and gcp write a lld which explains the change dod we have an lld reviewed by the team
| 1
|
74,338
| 9,015,342,990
|
IssuesEvent
|
2019-02-06 02:18:52
|
samtecspg/articulate
|
https://api.github.com/repos/samtecspg/articulate
|
opened
|
Implement search on review page
|
api needs design nice to have ui
|
This is ES based and maybe will be easier? Ideally though we'd have powerful filtering like category score < 80% etc.
|
1.0
|
Implement search on review page - This is ES based and maybe will be easier? Ideally though we'd have powerful filtering like category score < 80% etc.
|
design
|
implement search on review page this is es based and maybe will be easier ideally though we d have powerful filtering like category score etc
| 1
|
1,726
| 10,605,197,733
|
IssuesEvent
|
2019-10-10 19:54:42
|
ritsec/cluster-duck
|
https://api.github.com/repos/ritsec/cluster-duck
|
opened
|
Organize Existing Automation
|
automation
|
Organize Existing Automation
==============
Our current Ansible and Terraform should be reorganized more coherently.
A single central Ansible repository would be created to store host_vars, group_vars, the inventory file(s), and the overall playbook or playbooks. Then, each role would be split out into its own separate repository and pushed to Ansible Galaxy. The central Ansible repository would then reference the roles pushed in Ansible Galaxy. We could also use other roles, such as those created by geerlingguy, that are deemed of sufficient quality to use. _Please note that this repository would be separate from our openstack-ansible repository_.
Our Terraform should be split into two repositories: an internal and external repository. The external repository would contain all Terraform for our AWS environment, and could also include anything used for any other public clouds we choose to use. The internal repository would contain all Terraform for our internal OpenStack environment.
The goal should be that these repositories could be used to completely re-deploy our entire club infrastructure with the proper variables set. The only required dependencies should be AWS and OpenStack accounts with the proper permissions. Yes, that does mean that we would need to have OpenStack set up.
Tasks
-----
All of the following tasks must be complete before this issue can be closed. Be sure to reference this issue in the relevant issues/PRs in other repositories.
- [ ] Create internal Terraform repository
- [ ] Create external Terraform repository
- [ ] Update existing Ansible repository to match the goals outlined in this issue
- [ ] Merge existing Terraform and Ansible into the repositories as described above
- [ ] Document how to run our Terraform and Ansible and explain what it is used for
|
1.0
|
Organize Existing Automation - Organize Existing Automation
==============
Our current Ansible and Terraform should be reorganized more coherently.
A single central Ansible repository would be created to store host_vars, group_vars, the inventory file(s), and the overall playbook or playbooks. Then, each role would be split out into its own separate repository and pushed to Ansible Galaxy. The central Ansible repository would then reference the roles pushed in Ansible Galaxy. We could also use other roles, such as those created by geerlingguy, that are deemed of sufficient quality to use. _Please note that this repository would be separate from our openstack-ansible repository_.
Our Terraform should be split into two repositories: an internal and external repository. The external repository would contain all Terraform for our AWS environment, and could also include anything used for any other public clouds we choose to use. The internal repository would contain all Terraform for our internal OpenStack environment.
The goal should be that these repositories could be used to completely re-deploy our entire club infrastructure with the proper variables set. The only required dependencies should be AWS and OpenStack accounts with the proper permissions. Yes, that does mean that we would need to have OpenStack set up.
Tasks
-----
All of the following tasks must be complete before this issue can be closed. Be sure to reference this issue in the relevant issues/PRs in other repositories.
- [ ] Create internal Terraform repository
- [ ] Create external Terraform repository
- [ ] Update existing Ansible repository to match the goals outlined in this issue
- [ ] Merge existing Terraform and Ansible into the repositories as described above
- [ ] Document how to run our Terraform and Ansible and explain what it is used for
|
non_design
|
organize existing automation organize existing automation our current ansible and terraform should be reorganized more coherently a single central ansible repository would be created to store host vars group vars the inventory file s and the overall playbook or playbooks then each role would be split out into its own separate repository and pushed to ansible galaxy the central ansible repository would then reference the roles pushed in ansible galaxy we could also use other roles such as those created by geerlingguy that are deemed of sufficient quality to use please note that this repository would be separate from our openstack ansible repository our terraform should be split into two repositories an internal and external repository the external repository would contain all terraform for our aws environment and could also include anything used for any other public clouds we choose to use the internal repository would contain all terraform for our internal openstack environment the goal should be that these repositories could be used to completely re deploy our entire club infrastructure with the proper variables set the only required dependencies should be aws and openstack accounts with the proper permissions yes that does mean that we would need to have openstack set up tasks all of the following tasks must be complete before this issue can be closed be sure to reference this issue in the relevant issues prs in other repositories create internal terraform repository create external terraform repository update existing ansible repository to match the goals outlined in this issue merge existing terraform and ansible into the repositories as described above document how to run our terraform and ansible and explain what it is used for
| 0
|
16,033
| 10,425,738,818
|
IssuesEvent
|
2019-09-16 16:00:18
|
cityofaustin/atd-data-tech
|
https://api.github.com/repos/cityofaustin/atd-data-tech
|
closed
|
Data dump of 1k CRIS crash records from other agencies
|
Project: Vision Zero Crash Data System Service: Dev Workgroup: VZ
|
@johnclary would like to be able to follow up on missing lat/long in APD data — (Austin is the only one in TX missing lat/long).
|
1.0
|
Data dump of 1k CRIS crash records from other agencies - @johnclary would like to be able to follow up on missing lat/long in APD data — (Austin is the only one in TX missing lat/long).
|
non_design
|
data dump of cris crash records from other agencies johnclary would like to be able to follow up on missing lat long in apd data — austin is the only one in tx missing lat long
| 0
|
116,229
| 14,937,435,151
|
IssuesEvent
|
2021-01-25 14:38:10
|
dotnet/docs
|
https://api.github.com/repos/dotnet/docs
|
closed
|
Clarify 2-letter special guideline for "Id"
|
:book: guide - Framework Design Guidelines :books: Area - .NET Guide Pri2 doc-enhancement dotnet/prod won't fix
|
This is a very commonly asked question because perhaps legacy conventions recommended `ID` and would be helpful to clarify, even just adding an example in the Pascal/Camel/Not table.
From the current documentation, `id` & `Id` are recommended, but it is not clear when used as only part of an identifier, as was done with the `IOStream` example.
Please add a similar example how `Id` differs from `IO`. I believe this has to do with one is an abbreviation and the other an acronym, but it would be nice to confirm for the community.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 0eba6b11-5703-355f-0e85-08ee7451120d
* Version Independent ID: 4691fbb3-7b6d-8c02-e372-315ca302e48e
* Content: [Capitalization Conventions](https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/capitalization-conventions)
* Content Source: [docs/standard/design-guidelines/capitalization-conventions.md](https://github.com/dotnet/docs/blob/master/docs/standard/design-guidelines/capitalization-conventions.md)
* Product: **dotnet**
* GitHub Login: @rpetrusha
* Microsoft Alias: **ronpet**
|
1.0
|
Clarify 2-letter special guideline for "Id" - This is a very commonly asked question because perhaps legacy conventions recommended `ID` and would be helpful to clarify, even just adding an example in the Pascal/Camel/Not table.
From the current documentation, `id` & `Id` are recommended, but it is not clear when used as only part of an identifier, as was done with the `IOStream` example.
Please add a similar example how `Id` differs from `IO`. I believe this has to do with one is an abbreviation and the other an acronym, but it would be nice to confirm for the community.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 0eba6b11-5703-355f-0e85-08ee7451120d
* Version Independent ID: 4691fbb3-7b6d-8c02-e372-315ca302e48e
* Content: [Capitalization Conventions](https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/capitalization-conventions)
* Content Source: [docs/standard/design-guidelines/capitalization-conventions.md](https://github.com/dotnet/docs/blob/master/docs/standard/design-guidelines/capitalization-conventions.md)
* Product: **dotnet**
* GitHub Login: @rpetrusha
* Microsoft Alias: **ronpet**
|
design
|
clarify letter special guideline for id this is a very commonly asked question because perhaps legacy conventions recommended id and would be helpful to clarify even just adding an example in the pascal camel not table from the current documentation id id are recommended but it is not clear when used as only part of an identifier as was done with the iostream example please add a similar example how id differs from io i believe this has to do with one is an abbreviation and the other an acronym but it would be nice to confirm for the community 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 dotnet github login rpetrusha microsoft alias ronpet
| 1
|
38,164
| 8,432,106,785
|
IssuesEvent
|
2018-10-17 00:10:12
|
dotnet/coreclr
|
https://api.github.com/repos/dotnet/coreclr
|
closed
|
[arm32] Test failures in finalizearraysleep, finalizearray
|
arch-arm32 area-CodeGen
|
With JitStress=1
https://ci.dot.net/job/dotnet_coreclr/job/master/view/arm/job/jitstress/job/arm_cross_checked_windows_nt_jitstress1_tst/36/artifact/bin/tests/Windows_NT.arm.Checked/Smarty.run.0/Smarty.0.fail.smrt/*view*/
```
TEST_CMD_LINE: GC\Features\Finalizer\finalizeother\finalizearraysleep> C:\Users\robox\j\workspace\arm_cross_che---722ff6b5\bin\tests\Windows_NT.arm.Checked\GC\Features\Finalizer\finalizeother\finalizearraysleep\finalizearraysleep.cmd
BEGIN EXECUTION
"C:\Users\robox\j\workspace\arm_cross_che---722ff6b5\bin\tests\Windows_NT.arm.Checked\Tests\Core_Root\corerun.exe" finalizearraysleep.exe
Test for Finalize() for array of objects failed!
Expected: 100
Actual: 0
END EXECUTION - FAILED
FAILED
```
```
TEST_CMD_LINE: GC\Features\Finalizer\finalizeother\finalizearray> C:\Users\robox\j\workspace\arm_cross_che---722ff6b5\bin\tests\Windows_NT.arm.Checked\GC\Features\Finalizer\finalizeother\finalizearray\finalizearray.cmd
BEGIN EXECUTION
"C:\Users\robox\j\workspace\arm_cross_che---722ff6b5\bin\tests\Windows_NT.arm.Checked\Tests\Core_Root\corerun.exe" finalizearray.exe
Test for Finalize() for array of objects failed!
Expected: 100
Actual: 1
END EXECUTION - FAILED
FAILED
```
@dotnet/arm32-contrib
|
1.0
|
[arm32] Test failures in finalizearraysleep, finalizearray - With JitStress=1
https://ci.dot.net/job/dotnet_coreclr/job/master/view/arm/job/jitstress/job/arm_cross_checked_windows_nt_jitstress1_tst/36/artifact/bin/tests/Windows_NT.arm.Checked/Smarty.run.0/Smarty.0.fail.smrt/*view*/
```
TEST_CMD_LINE: GC\Features\Finalizer\finalizeother\finalizearraysleep> C:\Users\robox\j\workspace\arm_cross_che---722ff6b5\bin\tests\Windows_NT.arm.Checked\GC\Features\Finalizer\finalizeother\finalizearraysleep\finalizearraysleep.cmd
BEGIN EXECUTION
"C:\Users\robox\j\workspace\arm_cross_che---722ff6b5\bin\tests\Windows_NT.arm.Checked\Tests\Core_Root\corerun.exe" finalizearraysleep.exe
Test for Finalize() for array of objects failed!
Expected: 100
Actual: 0
END EXECUTION - FAILED
FAILED
```
```
TEST_CMD_LINE: GC\Features\Finalizer\finalizeother\finalizearray> C:\Users\robox\j\workspace\arm_cross_che---722ff6b5\bin\tests\Windows_NT.arm.Checked\GC\Features\Finalizer\finalizeother\finalizearray\finalizearray.cmd
BEGIN EXECUTION
"C:\Users\robox\j\workspace\arm_cross_che---722ff6b5\bin\tests\Windows_NT.arm.Checked\Tests\Core_Root\corerun.exe" finalizearray.exe
Test for Finalize() for array of objects failed!
Expected: 100
Actual: 1
END EXECUTION - FAILED
FAILED
```
@dotnet/arm32-contrib
|
non_design
|
test failures in finalizearraysleep finalizearray with jitstress test cmd line gc features finalizer finalizeother finalizearraysleep c users robox j workspace arm cross che bin tests windows nt arm checked gc features finalizer finalizeother finalizearraysleep finalizearraysleep cmd begin execution c users robox j workspace arm cross che bin tests windows nt arm checked tests core root corerun exe finalizearraysleep exe test for finalize for array of objects failed expected actual end execution failed failed test cmd line gc features finalizer finalizeother finalizearray c users robox j workspace arm cross che bin tests windows nt arm checked gc features finalizer finalizeother finalizearray finalizearray cmd begin execution c users robox j workspace arm cross che bin tests windows nt arm checked tests core root corerun exe finalizearray exe test for finalize for array of objects failed expected actual end execution failed failed dotnet contrib
| 0
|
120,437
| 15,766,254,705
|
IssuesEvent
|
2021-03-31 14:53:54
|
NixOS/nixos-homepage
|
https://api.github.com/repos/NixOS/nixos-homepage
|
opened
|
[DOCUMENTATION] Add paged support for project documentation
|
design
|
**Describe the glitch**
The Nix documentation pages are near-enough impossible to navigate properly for 2 reasons:
1. The site loads as slow as molasses, owing to it's massive size
2. The only available versions of the Nix manuals are single page, and in places don't provide enough access to nested subsections (especially the Nix Language reference).
**Screenshots**
See any of the documentation pages, it should be immediately obvious
**Additional context**
I have found this particularly annoying when trying to build a project on top of the Nix expression language, as the reference has no table of contents that goes deep enough to find anything quickly.
|
1.0
|
[DOCUMENTATION] Add paged support for project documentation - **Describe the glitch**
The Nix documentation pages are near-enough impossible to navigate properly for 2 reasons:
1. The site loads as slow as molasses, owing to it's massive size
2. The only available versions of the Nix manuals are single page, and in places don't provide enough access to nested subsections (especially the Nix Language reference).
**Screenshots**
See any of the documentation pages, it should be immediately obvious
**Additional context**
I have found this particularly annoying when trying to build a project on top of the Nix expression language, as the reference has no table of contents that goes deep enough to find anything quickly.
|
design
|
add paged support for project documentation describe the glitch the nix documentation pages are near enough impossible to navigate properly for reasons the site loads as slow as molasses owing to it s massive size the only available versions of the nix manuals are single page and in places don t provide enough access to nested subsections especially the nix language reference screenshots see any of the documentation pages it should be immediately obvious additional context i have found this particularly annoying when trying to build a project on top of the nix expression language as the reference has no table of contents that goes deep enough to find anything quickly
| 1
|
30,624
| 24,947,051,598
|
IssuesEvent
|
2022-11-01 01:47:35
|
move2-it/infrastructure
|
https://api.github.com/repos/move2-it/infrastructure
|
closed
|
Create Kubernetes deployment for: Prometheus
|
Infrastructure
|
- deployment is carried out using Terraform and Helm charts
- Prometheus is configured to send metrics to Prometheus in Grafana Cloud
|
1.0
|
Create Kubernetes deployment for: Prometheus - - deployment is carried out using Terraform and Helm charts
- Prometheus is configured to send metrics to Prometheus in Grafana Cloud
|
non_design
|
create kubernetes deployment for prometheus deployment is carried out using terraform and helm charts prometheus is configured to send metrics to prometheus in grafana cloud
| 0
|
435,046
| 12,530,850,453
|
IssuesEvent
|
2020-06-04 13:42:30
|
webcompat/web-bugs
|
https://api.github.com/repos/webcompat/web-bugs
|
closed
|
m.facebook.com - design is broken
|
browser-firefox-mobile engine-gecko priority-critical
|
<!-- @browser: Firefox Mobile 77.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:77.0) Gecko/77.0 Firefox/77.0 -->
<!-- @reported_with: -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/53712 -->
**URL**: https://m.facebook.com/
**Browser / Version**: Firefox Mobile 77.0
**Operating System**: Android
**Tested Another Browser**: Yes Chrome
**Problem type**: Design is broken
**Description**: Items not fully visible
**Steps to Reproduce**:
Facebook shows low resolution images in firefox mobile.but in Chrome it shows normal images.
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
Submitted in the name of `@mohan123`
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
1.0
|
m.facebook.com - design is broken - <!-- @browser: Firefox Mobile 77.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:77.0) Gecko/77.0 Firefox/77.0 -->
<!-- @reported_with: -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/53712 -->
**URL**: https://m.facebook.com/
**Browser / Version**: Firefox Mobile 77.0
**Operating System**: Android
**Tested Another Browser**: Yes Chrome
**Problem type**: Design is broken
**Description**: Items not fully visible
**Steps to Reproduce**:
Facebook shows low resolution images in firefox mobile.but in Chrome it shows normal images.
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
Submitted in the name of `@mohan123`
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
non_design
|
m facebook com design is broken url browser version firefox mobile operating system android tested another browser yes chrome problem type design is broken description items not fully visible steps to reproduce facebook shows low resolution images in firefox mobile but in chrome it shows normal images browser configuration none submitted in the name of from with ❤️
| 0
|
176,943
| 13,671,500,246
|
IssuesEvent
|
2020-09-29 07:05:53
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
opened
|
roachtest: drop/tpcc/w=100,nodes=9 failed
|
C-test-failure O-roachtest O-robot branch-release-20.1 release-blocker
|
[(roachtest).drop/tpcc/w=100,nodes=9 failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2328549&tab=buildLog) on [release-20.1@5a4e41010f8faa095c88e2e5b142e0b6880c9f44](https://github.com/cockroachdb/cockroach/commits/5a4e41010f8faa095c88e2e5b142e0b6880c9f44):
```
| I200929 07:05:26.467503 72 ccl/workloadccl/fixture.go:583 Restoring from gs://cockroach-fixtures/workload/tpcc/version=2.2.0,deprecated-fk-indexes=false,fks=true,interleaved=false,seed=1,warehouses=100/customer
| I200929 07:05:26.467139 75 ccl/workloadccl/fixture.go:583 Restoring from gs://cockroach-fixtures/workload/tpcc/version=2.2.0,deprecated-fk-indexes=false,fks=true,interleaved=false,seed=1,warehouses=100/new_order
| I200929 07:05:26.467092 73 ccl/workloadccl/fixture.go:583 Restoring from gs://cockroach-fixtures/workload/tpcc/version=2.2.0,deprecated-fk-indexes=false,fks=true,interleaved=false,seed=1,warehouses=100/history
| I200929 07:05:26.467202 77 ccl/workloadccl/fixture.go:583 Restoring from gs://cockroach-fixtures/workload/tpcc/version=2.2.0,deprecated-fk-indexes=false,fks=true,interleaved=false,seed=1,warehouses=100/stock
| I200929 07:05:26.468309 78 ccl/workloadccl/fixture.go:583 Restoring from gs://cockroach-fixtures/workload/tpcc/version=2.2.0,deprecated-fk-indexes=false,fks=true,interleaved=false,seed=1,warehouses=100/order_line
| Error: restoring fixture: backup: gs://cockroach-fixtures/workload/tpcc/version=2.2.0,deprecated-fk-indexes=false,fks=true,interleaved=false,seed=1,warehouses=100/district: pq: storage: object doesn't exist
| Error: COMMAND_PROBLEM: exit status 1
| (1) COMMAND_PROBLEM
| Wraps: (2) Node 1. Command with error:
| | ```
| | ./workload fixtures load tpcc --warehouses=100 --db tpcc {pgurl:1}
| | ```
| Wraps: (3) exit status 1
| Error types: (1) errors.Cmd (2) *hintdetail.withDetail (3) *exec.ExitError
|
| stdout:
Wraps: (4) exit status 20
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *main.withCommandDetails (4) *exec.ExitError
cluster.go:2651,drop.go:158,drop.go:183,test_runner.go:755: monitor failure: monitor task failed: t.Fatal() was called
(1) attached stack trace
-- stack trace:
| main.(*monitor).WaitE
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2639
| main.(*monitor).Wait
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2647
| main.registerDrop.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/drop.go:158
| main.registerDrop.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/drop.go:183
| main.(*testRunner).runTest.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/test_runner.go:755
Wraps: (2) monitor failure
Wraps: (3) attached stack trace
-- stack trace:
| main.(*monitor).wait.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2695
Wraps: (4) monitor task failed
Wraps: (5) attached stack trace
-- stack trace:
| main.init
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2609
| runtime.doInit
| /usr/local/go/src/runtime/proc.go:5228
| runtime.main
| /usr/local/go/src/runtime/proc.go:190
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1357
Wraps: (6) t.Fatal() was called
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *withstack.withStack (6) *errutil.leafError
```
<details><summary>More</summary><p>
Artifacts: [/drop/tpcc/w=100,nodes=9](https://teamcity.cockroachdb.com/viewLog.html?buildId=2328549&tab=artifacts#/drop/tpcc/w=100,nodes=9)
Related:
- #54836 roachtest: drop/tpcc/w=100,nodes=9 failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-release-20.2](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-release-20.2)
- #54834 roachtest: drop/tpcc/w=100,nodes=9 failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-master](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-master) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Adrop%2Ftpcc%2Fw%3D100%2Cnodes%3D9.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
|
2.0
|
roachtest: drop/tpcc/w=100,nodes=9 failed - [(roachtest).drop/tpcc/w=100,nodes=9 failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2328549&tab=buildLog) on [release-20.1@5a4e41010f8faa095c88e2e5b142e0b6880c9f44](https://github.com/cockroachdb/cockroach/commits/5a4e41010f8faa095c88e2e5b142e0b6880c9f44):
```
| I200929 07:05:26.467503 72 ccl/workloadccl/fixture.go:583 Restoring from gs://cockroach-fixtures/workload/tpcc/version=2.2.0,deprecated-fk-indexes=false,fks=true,interleaved=false,seed=1,warehouses=100/customer
| I200929 07:05:26.467139 75 ccl/workloadccl/fixture.go:583 Restoring from gs://cockroach-fixtures/workload/tpcc/version=2.2.0,deprecated-fk-indexes=false,fks=true,interleaved=false,seed=1,warehouses=100/new_order
| I200929 07:05:26.467092 73 ccl/workloadccl/fixture.go:583 Restoring from gs://cockroach-fixtures/workload/tpcc/version=2.2.0,deprecated-fk-indexes=false,fks=true,interleaved=false,seed=1,warehouses=100/history
| I200929 07:05:26.467202 77 ccl/workloadccl/fixture.go:583 Restoring from gs://cockroach-fixtures/workload/tpcc/version=2.2.0,deprecated-fk-indexes=false,fks=true,interleaved=false,seed=1,warehouses=100/stock
| I200929 07:05:26.468309 78 ccl/workloadccl/fixture.go:583 Restoring from gs://cockroach-fixtures/workload/tpcc/version=2.2.0,deprecated-fk-indexes=false,fks=true,interleaved=false,seed=1,warehouses=100/order_line
| Error: restoring fixture: backup: gs://cockroach-fixtures/workload/tpcc/version=2.2.0,deprecated-fk-indexes=false,fks=true,interleaved=false,seed=1,warehouses=100/district: pq: storage: object doesn't exist
| Error: COMMAND_PROBLEM: exit status 1
| (1) COMMAND_PROBLEM
| Wraps: (2) Node 1. Command with error:
| | ```
| | ./workload fixtures load tpcc --warehouses=100 --db tpcc {pgurl:1}
| | ```
| Wraps: (3) exit status 1
| Error types: (1) errors.Cmd (2) *hintdetail.withDetail (3) *exec.ExitError
|
| stdout:
Wraps: (4) exit status 20
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *main.withCommandDetails (4) *exec.ExitError
cluster.go:2651,drop.go:158,drop.go:183,test_runner.go:755: monitor failure: monitor task failed: t.Fatal() was called
(1) attached stack trace
-- stack trace:
| main.(*monitor).WaitE
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2639
| main.(*monitor).Wait
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2647
| main.registerDrop.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/drop.go:158
| main.registerDrop.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/drop.go:183
| main.(*testRunner).runTest.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/test_runner.go:755
Wraps: (2) monitor failure
Wraps: (3) attached stack trace
-- stack trace:
| main.(*monitor).wait.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2695
Wraps: (4) monitor task failed
Wraps: (5) attached stack trace
-- stack trace:
| main.init
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2609
| runtime.doInit
| /usr/local/go/src/runtime/proc.go:5228
| runtime.main
| /usr/local/go/src/runtime/proc.go:190
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1357
Wraps: (6) t.Fatal() was called
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *withstack.withStack (6) *errutil.leafError
```
<details><summary>More</summary><p>
Artifacts: [/drop/tpcc/w=100,nodes=9](https://teamcity.cockroachdb.com/viewLog.html?buildId=2328549&tab=artifacts#/drop/tpcc/w=100,nodes=9)
Related:
- #54836 roachtest: drop/tpcc/w=100,nodes=9 failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-release-20.2](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-release-20.2)
- #54834 roachtest: drop/tpcc/w=100,nodes=9 failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-master](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-master) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Adrop%2Ftpcc%2Fw%3D100%2Cnodes%3D9.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
|
non_design
|
roachtest drop tpcc w nodes failed on ccl workloadccl fixture go restoring from gs cockroach fixtures workload tpcc version deprecated fk indexes false fks true interleaved false seed warehouses customer ccl workloadccl fixture go restoring from gs cockroach fixtures workload tpcc version deprecated fk indexes false fks true interleaved false seed warehouses new order ccl workloadccl fixture go restoring from gs cockroach fixtures workload tpcc version deprecated fk indexes false fks true interleaved false seed warehouses history ccl workloadccl fixture go restoring from gs cockroach fixtures workload tpcc version deprecated fk indexes false fks true interleaved false seed warehouses stock ccl workloadccl fixture go restoring from gs cockroach fixtures workload tpcc version deprecated fk indexes false fks true interleaved false seed warehouses order line error restoring fixture backup gs cockroach fixtures workload tpcc version deprecated fk indexes false fks true interleaved false seed warehouses district pq storage object doesn t exist error command problem exit status command problem wraps node command with error workload fixtures load tpcc warehouses db tpcc pgurl wraps exit status error types errors cmd hintdetail withdetail exec exiterror stdout wraps exit status error types withstack withstack errutil withprefix main withcommanddetails exec exiterror cluster go drop go drop go test runner go monitor failure monitor task failed t fatal was called attached stack trace stack trace main monitor waite home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go main monitor wait home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go main registerdrop home agent work go src github com cockroachdb cockroach pkg cmd roachtest drop go main registerdrop home agent work go src github com cockroachdb cockroach pkg cmd roachtest drop go main testrunner runtest home agent work go src github com cockroachdb cockroach pkg cmd roachtest test runner go wraps monitor failure wraps attached stack trace stack trace main monitor wait home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go wraps monitor task failed wraps attached stack trace stack trace main init home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go runtime doinit usr local go src runtime proc go runtime main usr local go src runtime proc go runtime goexit usr local go src runtime asm s wraps t fatal was called error types withstack withstack errutil withprefix withstack withstack errutil withprefix withstack withstack errutil leaferror more artifacts related roachtest drop tpcc w nodes failed roachtest drop tpcc w nodes failed powered by
| 0
|
102,806
| 12,824,606,536
|
IssuesEvent
|
2020-07-06 13:44:46
|
vector-im/riot-web
|
https://api.github.com/repos/vector-im/riot-web
|
closed
|
Allow picking a recovery key file upon login / other places where you need the SSSS key
|
feature:e2e-cross-signing needs-design story:deprio-phrases:45 suggestion ui/ux
|
When logging in and verifying yourself via SSSS or other places when you need the SSSS key you have to manually enter your passphrase or your key. It might be nice to be to have some kind of "Chose keyfile" dialog to be able to upload/use a keyfile you previously downloaded/created when setting up cross-signing etc. Else you would have to manually open said keyfile and paste its contents....that seems sub-ideal
|
1.0
|
Allow picking a recovery key file upon login / other places where you need the SSSS key - 
When logging in and verifying yourself via SSSS or other places when you need the SSSS key you have to manually enter your passphrase or your key. It might be nice to be to have some kind of "Chose keyfile" dialog to be able to upload/use a keyfile you previously downloaded/created when setting up cross-signing etc. Else you would have to manually open said keyfile and paste its contents....that seems sub-ideal
|
design
|
allow picking a recovery key file upon login other places where you need the ssss key when logging in and verifying yourself via ssss or other places when you need the ssss key you have to manually enter your passphrase or your key it might be nice to be to have some kind of chose keyfile dialog to be able to upload use a keyfile you previously downloaded created when setting up cross signing etc else you would have to manually open said keyfile and paste its contents that seems sub ideal
| 1
|
21,599
| 4,727,557,539
|
IssuesEvent
|
2016-10-18 13:50:11
|
NIVeriStandAdd-Ons/Modbus-Custom-Device-v2
|
https://api.github.com/repos/NIVeriStandAdd-Ons/Modbus-Custom-Device-v2
|
opened
|
Add description to the diagnostics channels
|
documentation
|
(what do they do?), or add this to the main page/top level page.
|
1.0
|
Add description to the diagnostics channels - (what do they do?), or add this to the main page/top level page.
|
non_design
|
add description to the diagnostics channels what do they do or add this to the main page top level page
| 0
|
19,234
| 5,827,853,234
|
IssuesEvent
|
2017-05-08 10:12:41
|
jOOQ/jOOQ
|
https://api.github.com/repos/jOOQ/jOOQ
|
closed
|
JPADatabase doesn't correctly generate tables for multi-schema entities
|
C: Code Generation P: Medium R: Fixed T: Defect
|
When entities are annotated with schema information, then the `JPADatabase` currently doesn't correctly generate the tables. For example:
```java
@Entity
@Table(schema = "schema1", name = "t_actor")
public class JPAActor {
@Id
int id;
@Column(name = "first_name")
String firstName;
@Column(name = "last_name")
String lastName;
@ManyToMany
@JoinTable(
schema = "schema2",
name = "t_film_actor",
joinColumns = @JoinColumn(name = "actor_id", referencedColumnName = "id"),
inverseJoinColumns = @JoinColumn(name = "film_id", referencedColumnName = "id")
)
Set<JPAFilm> films;
}
@Entity
@Table(schema = "schema2", name = "t_film")
public class JPAFilm {
@Id
public int id;
@Column(name = "title")
public String title;
@ManyToMany
@JoinTable(
schema = "schema2",
name = "t_film_actor",
joinColumns = @JoinColumn(name = "film_id", referencedColumnName = "id"),
inverseJoinColumns = @JoinColumn(name = "actor_id", referencedColumnName = "id")
)
public Set<JPAActor> actors;
}
```
This is probably due to some Hibernate misconfiguration (or bug), as Hibernate's `SchemaExport`, which is used behind the scenes by `JPADatabase` doesn't generate any non-public tables (nor the schemata) in the H2 in-memory database.
|
1.0
|
JPADatabase doesn't correctly generate tables for multi-schema entities - When entities are annotated with schema information, then the `JPADatabase` currently doesn't correctly generate the tables. For example:
```java
@Entity
@Table(schema = "schema1", name = "t_actor")
public class JPAActor {
@Id
int id;
@Column(name = "first_name")
String firstName;
@Column(name = "last_name")
String lastName;
@ManyToMany
@JoinTable(
schema = "schema2",
name = "t_film_actor",
joinColumns = @JoinColumn(name = "actor_id", referencedColumnName = "id"),
inverseJoinColumns = @JoinColumn(name = "film_id", referencedColumnName = "id")
)
Set<JPAFilm> films;
}
@Entity
@Table(schema = "schema2", name = "t_film")
public class JPAFilm {
@Id
public int id;
@Column(name = "title")
public String title;
@ManyToMany
@JoinTable(
schema = "schema2",
name = "t_film_actor",
joinColumns = @JoinColumn(name = "film_id", referencedColumnName = "id"),
inverseJoinColumns = @JoinColumn(name = "actor_id", referencedColumnName = "id")
)
public Set<JPAActor> actors;
}
```
This is probably due to some Hibernate misconfiguration (or bug), as Hibernate's `SchemaExport`, which is used behind the scenes by `JPADatabase` doesn't generate any non-public tables (nor the schemata) in the H2 in-memory database.
|
non_design
|
jpadatabase doesn t correctly generate tables for multi schema entities when entities are annotated with schema information then the jpadatabase currently doesn t correctly generate the tables for example java entity table schema name t actor public class jpaactor id int id column name first name string firstname column name last name string lastname manytomany jointable schema name t film actor joincolumns joincolumn name actor id referencedcolumnname id inversejoincolumns joincolumn name film id referencedcolumnname id set films entity table schema name t film public class jpafilm id public int id column name title public string title manytomany jointable schema name t film actor joincolumns joincolumn name film id referencedcolumnname id inversejoincolumns joincolumn name actor id referencedcolumnname id public set actors this is probably due to some hibernate misconfiguration or bug as hibernate s schemaexport which is used behind the scenes by jpadatabase doesn t generate any non public tables nor the schemata in the in memory database
| 0
|
133,722
| 29,507,101,009
|
IssuesEvent
|
2023-06-03 12:56:05
|
EddieHubCommunity/LinkFree
|
https://api.github.com/repos/EddieHubCommunity/LinkFree
|
closed
|
[OTHER] Remove single use mode
|
💻 aspect: code 🏁 status: ready for dev 🔢 points: 3
|
### What would you like to share?
This feature is not used and we are keen for people to connect on the hosted platform
REMOVE
- layout
- config
- docs
anything else?
### Additional information
_No response_
|
1.0
|
[OTHER] Remove single use mode - ### What would you like to share?
This feature is not used and we are keen for people to connect on the hosted platform
REMOVE
- layout
- config
- docs
anything else?
### Additional information
_No response_
|
non_design
|
remove single use mode what would you like to share this feature is not used and we are keen for people to connect on the hosted platform remove layout config docs anything else additional information no response
| 0
|
275,830
| 8,581,233,337
|
IssuesEvent
|
2018-11-13 14:13:00
|
spinnaker/spinnaker
|
https://api.github.com/repos/spinnaker/spinnaker
|
closed
|
Halyard: Publish metric dashboards
|
component/halyard enhancement priority/2 stale to-be-closed
|
_Migrated from https://github.com/spinnaker/halyard_
__Opened by__: @lwander _(2017-04-10 17:52:15)_ This involves taking the dashboards in the `spinnaker-monitoring-third-party` debian and publishing them for the user of Halyard.
|
1.0
|
Halyard: Publish metric dashboards - _Migrated from https://github.com/spinnaker/halyard_
__Opened by__: @lwander _(2017-04-10 17:52:15)_ This involves taking the dashboards in the `spinnaker-monitoring-third-party` debian and publishing them for the user of Halyard.
|
non_design
|
halyard publish metric dashboards migrated from opened by lwander this involves taking the dashboards in the spinnaker monitoring third party debian and publishing them for the user of halyard
| 0
|
524,825
| 15,223,981,285
|
IssuesEvent
|
2021-02-18 04:03:15
|
DimensionDev/Maskbook
|
https://api.github.com/repos/DimensionDev/Maskbook
|
closed
|
[Bug] After switching the swap provider the Swap token should remain the same
|
Priority: P1 (Now) Type: Bug
|
## Bug Report
<img width="1371" alt="Screen Shot 2021-02-14 at 00 52 31" src="https://user-images.githubusercontent.com/6687437/107858043-f8863380-6e6c-11eb-85e7-25857edaf74c.png">
<img width="1371" alt="Screen Shot 2021-02-14 at 00 52 03" src="https://user-images.githubusercontent.com/6687437/107858050-0340c880-6e6d-11eb-84eb-f6d3e914468d.png">
How to reproduce:
Try search $uni and swap dai -> uni on uniV2;
then switch provider to 0x/sushi others. the $dai will be $eth but the amount number stay the same. which is not ideal situation.
## Environment
### System
- [ ] Windows
- OS Version:
- [ ] Mac OS X
- OS Version:
- [ ] Linux
- Linux Distribution:
- OS Version:
### Platform/Browser
- [x] Chrome
- Mask Version:
- Browser Version:
- [x] Firefox
- Mask Version:
- Browser Version:
- [ ] Android
- Mask Version:
- Android Version:
- [ ] iOS
- Mask Version:
- iOS Version:
### Build Variant
- Where do you get Mask?
- [ ] Store
- [ ] ZIP
- [ ] Self-Compiled
- Build Commit: /_Optionally attach a Commit ID, if it is from an pre-release branch head_/
## Bug Info
### Actual Behavior
/_What happened?_/
|
1.0
|
[Bug] After switching the swap provider the Swap token should remain the same - ## Bug Report
<img width="1371" alt="Screen Shot 2021-02-14 at 00 52 31" src="https://user-images.githubusercontent.com/6687437/107858043-f8863380-6e6c-11eb-85e7-25857edaf74c.png">
<img width="1371" alt="Screen Shot 2021-02-14 at 00 52 03" src="https://user-images.githubusercontent.com/6687437/107858050-0340c880-6e6d-11eb-84eb-f6d3e914468d.png">
How to reproduce:
Try search $uni and swap dai -> uni on uniV2;
then switch provider to 0x/sushi others. the $dai will be $eth but the amount number stay the same. which is not ideal situation.
## Environment
### System
- [ ] Windows
- OS Version:
- [ ] Mac OS X
- OS Version:
- [ ] Linux
- Linux Distribution:
- OS Version:
### Platform/Browser
- [x] Chrome
- Mask Version:
- Browser Version:
- [x] Firefox
- Mask Version:
- Browser Version:
- [ ] Android
- Mask Version:
- Android Version:
- [ ] iOS
- Mask Version:
- iOS Version:
### Build Variant
- Where do you get Mask?
- [ ] Store
- [ ] ZIP
- [ ] Self-Compiled
- Build Commit: /_Optionally attach a Commit ID, if it is from an pre-release branch head_/
## Bug Info
### Actual Behavior
/_What happened?_/
|
non_design
|
after switching the swap provider the swap token should remain the same bug report img width alt screen shot at src img width alt screen shot at src how to reproduce try search uni and swap dai uni on then switch provider to sushi others the dai will be eth but the amount number stay the same which is not ideal situation environment system windows os version mac os x os version linux linux distribution os version platform browser chrome mask version browser version firefox mask version browser version android mask version android version ios mask version ios version build variant where do you get mask store zip self compiled build commit optionally attach a commit id if it is from an pre release branch head bug info actual behavior what happened
| 0
|
63,067
| 7,688,029,447
|
IssuesEvent
|
2018-05-17 08:11:05
|
codebuddies/codebuddies
|
https://api.github.com/repos/codebuddies/codebuddies
|
opened
|
Redesign: Home Page V3
|
design
|
Requirements on home page (order of sections not determined yet):
**1. Mission statement/goals**
**2. BuyMeACoffee links for hangout organizers** #844
**3. Global Silent Hangout**
**4. CodeBuddies Connect**
**5. Gamification**
|
1.0
|
Redesign: Home Page V3 - Requirements on home page (order of sections not determined yet):
**1. Mission statement/goals**
**2. BuyMeACoffee links for hangout organizers** #844
**3. Global Silent Hangout**
**4. CodeBuddies Connect**
**5. Gamification**
|
design
|
redesign home page requirements on home page order of sections not determined yet mission statement goals buymeacoffee links for hangout organizers global silent hangout codebuddies connect gamification
| 1
|
171,095
| 27,060,814,414
|
IssuesEvent
|
2023-02-13 19:36:46
|
Shopify/polaris
|
https://api.github.com/repos/Shopify/polaris
|
closed
|
Connect GitHub discussions
|
Design #gsd:30559
|
### Tasks
Design
- [x] Create Github discussions
- [x] Create a simple discussion template and update all threads (Selene)
Eng
- [x] Add links to respective page on the doc site (Johan)
- [x] Add new pattern index link to (Johan)
### GitHub discussion links
| Added | Topic | Link |
|--------|--------|--------|
| ✅ | Polaris Patterns general | `https://github.com/Shopify/polaris/discussions/categories/pattern-documentation` |
| ✅ | Date picking | `https://github.com/Shopify/polaris/discussions/7853` |
| ✅ | Resource index layout | `https://github.com/Shopify/polaris/discussions/8215` |
| ✅ | Resource details layout | `https://github.com/Shopify/polaris/discussions/8216` |
| ✅ | App settings layout | `https://github.com/Shopify/polaris/discussions/8217` |
|
1.0
|
Connect GitHub discussions - ### Tasks
Design
- [x] Create Github discussions
- [x] Create a simple discussion template and update all threads (Selene)
Eng
- [x] Add links to respective page on the doc site (Johan)
- [x] Add new pattern index link to (Johan)
### GitHub discussion links
| Added | Topic | Link |
|--------|--------|--------|
| ✅ | Polaris Patterns general | `https://github.com/Shopify/polaris/discussions/categories/pattern-documentation` |
| ✅ | Date picking | `https://github.com/Shopify/polaris/discussions/7853` |
| ✅ | Resource index layout | `https://github.com/Shopify/polaris/discussions/8215` |
| ✅ | Resource details layout | `https://github.com/Shopify/polaris/discussions/8216` |
| ✅ | App settings layout | `https://github.com/Shopify/polaris/discussions/8217` |
|
design
|
connect github discussions tasks design create github discussions create a simple discussion template and update all threads selene eng add links to respective page on the doc site johan add new pattern index link to johan github discussion links added topic link ✅ polaris patterns general ✅ date picking ✅ resource index layout ✅ resource details layout ✅ app settings layout
| 1
|
116,654
| 14,987,642,187
|
IssuesEvent
|
2021-01-28 23:21:03
|
kantord/LibreLingo
|
https://api.github.com/repos/kantord/LibreLingo
|
closed
|
Translate what you hear challenge
|
design difficulty:hard django feature_request wontfix
|
**Is your feature request related to a problem? Please describe.**
In this kind of exercice, we ask the user to translate a word or sentence in his mother tongue.
**Describe the solution you'd like**
<img width="1792" alt="Screen Shot 2020-08-16 at 13 39 37" src="https://user-images.githubusercontent.com/442722/90328364-0d6d3180-dfc6-11ea-9600-5b5f4568eda8.png">
**Describe alternatives you've considered**
Maybe using a variant of the ShortInputChallenge? But then we need to change the wording a bit and hide the virtual keyboard.
It's different from the ChipsChallenge because it requires keyboard typing.
|
1.0
|
Translate what you hear challenge - **Is your feature request related to a problem? Please describe.**
In this kind of exercice, we ask the user to translate a word or sentence in his mother tongue.
**Describe the solution you'd like**
<img width="1792" alt="Screen Shot 2020-08-16 at 13 39 37" src="https://user-images.githubusercontent.com/442722/90328364-0d6d3180-dfc6-11ea-9600-5b5f4568eda8.png">
**Describe alternatives you've considered**
Maybe using a variant of the ShortInputChallenge? But then we need to change the wording a bit and hide the virtual keyboard.
It's different from the ChipsChallenge because it requires keyboard typing.
|
design
|
translate what you hear challenge is your feature request related to a problem please describe in this kind of exercice we ask the user to translate a word or sentence in his mother tongue describe the solution you d like img width alt screen shot at src describe alternatives you ve considered maybe using a variant of the shortinputchallenge but then we need to change the wording a bit and hide the virtual keyboard it s different from the chipschallenge because it requires keyboard typing
| 1
|
96,352
| 19,989,240,375
|
IssuesEvent
|
2022-01-31 02:51:17
|
microsoft/AL
|
https://api.github.com/repos/microsoft/AL
|
closed
|
Many methods/property accessors on RecordRef do not autocomplete with, or warn about, parentheses
|
bug static-code-analysis CodeCop stale
|
Shouldn't all methods require parentheses, and thus (a) include them when auto-completing from Intellisense and (b) warn about them if omitted (e.g. from manually written or migrated code)?
Many of them on `RecordRef` type do not; the below is not necessarily exhaustive, as I got bored, but illustrates my point well.
|
2.0
|
Many methods/property accessors on RecordRef do not autocomplete with, or warn about, parentheses - Shouldn't all methods require parentheses, and thus (a) include them when auto-completing from Intellisense and (b) warn about them if omitted (e.g. from manually written or migrated code)?
Many of them on `RecordRef` type do not; the below is not necessarily exhaustive, as I got bored, but illustrates my point well.
|
non_design
|
many methods property accessors on recordref do not autocomplete with or warn about parentheses shouldn t all methods require parentheses and thus a include them when auto completing from intellisense and b warn about them if omitted e g from manually written or migrated code many of them on recordref type do not the below is not necessarily exhaustive as i got bored but illustrates my point well
| 0
|
318,935
| 27,333,308,929
|
IssuesEvent
|
2023-02-25 22:33:27
|
PalisadoesFoundation/talawa-admin
|
https://api.github.com/repos/PalisadoesFoundation/talawa-admin
|
closed
|
incorrect and incomplete instructions in INSTALLATION.md
|
bug unapproved test feature request
|
**Describe the bug**
A clear and concise description of what the bug is.
1. There are some minor but important missing details in [INSTALLATION.md](https://github.com/PalisadoesFoundation/talawa-api/blob/develop/INSTALLATION.md). The mongodb url do not talks about passing a default db in connection string. If not given the app don't throw a error during `npm run dev` but the connection is not made and the development data base is not created. This is troubling for users new to mongodb. Discussed [here on slack](https://thepalisadoes-dyb6419.slack.com/archives/CSWGQ70UQ/p1677241781770239?thread_ts=1677171179.688719&cid=CSWGQ70UQ)
2. Before [this](https://github.com/PalisadoesFoundation/talawa-api/blob/develop/INSTALLATION.md#i-mongodb-compass) step we have to trigger the creation of user object from register panel. Then only the user object in db will appear. This step is not talked about.
3. [Here](https://github.com/PalisadoesFoundation/talawa-api/blob/develop/CONTRIBUTING.md#contributing-code)
> The [organizations.spec.js](https://github.com/PalisadoesFoundation/talawa-api/blob/develop/tests/resolvers/organization_query/organizations.spec.js) test file is a well documented example of what to do for resolver tests.
organizations.spec.js is misplaced I need to fix the path
Files to be changed :
[INSTALLATION.md](https://github.com/PalisadoesFoundation/talawa-api/blob/develop/INSTALLATION.md)
[CONTRIBUTING.md](https://github.com/PalisadoesFoundation/talawa-api/blob/develop/CONTRIBUTING.md)
**To Reproduce**
Steps to reproduce the behavior:
1.
2.
3.
4.
**Expected behavior**
A clear and concise description of what you expected to happen.
**Actual behavior**
A clear and concise description of how the code performed w.r.t expectations.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Additional details**
Add any other context or screenshots about the feature request here.
**Potential internship candidates**
Please read this if you are planning to apply for a Palisadoes Foundation internship https://github.com/PalisadoesFoundation/talawa/issues/359
|
1.0
|
incorrect and incomplete instructions in INSTALLATION.md - **Describe the bug**
A clear and concise description of what the bug is.
1. There are some minor but important missing details in [INSTALLATION.md](https://github.com/PalisadoesFoundation/talawa-api/blob/develop/INSTALLATION.md). The mongodb url do not talks about passing a default db in connection string. If not given the app don't throw a error during `npm run dev` but the connection is not made and the development data base is not created. This is troubling for users new to mongodb. Discussed [here on slack](https://thepalisadoes-dyb6419.slack.com/archives/CSWGQ70UQ/p1677241781770239?thread_ts=1677171179.688719&cid=CSWGQ70UQ)
2. Before [this](https://github.com/PalisadoesFoundation/talawa-api/blob/develop/INSTALLATION.md#i-mongodb-compass) step we have to trigger the creation of user object from register panel. Then only the user object in db will appear. This step is not talked about.
3. [Here](https://github.com/PalisadoesFoundation/talawa-api/blob/develop/CONTRIBUTING.md#contributing-code)
> The [organizations.spec.js](https://github.com/PalisadoesFoundation/talawa-api/blob/develop/tests/resolvers/organization_query/organizations.spec.js) test file is a well documented example of what to do for resolver tests.
organizations.spec.js is misplaced I need to fix the path
Files to be changed :
[INSTALLATION.md](https://github.com/PalisadoesFoundation/talawa-api/blob/develop/INSTALLATION.md)
[CONTRIBUTING.md](https://github.com/PalisadoesFoundation/talawa-api/blob/develop/CONTRIBUTING.md)
**To Reproduce**
Steps to reproduce the behavior:
1.
2.
3.
4.
**Expected behavior**
A clear and concise description of what you expected to happen.
**Actual behavior**
A clear and concise description of how the code performed w.r.t expectations.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Additional details**
Add any other context or screenshots about the feature request here.
**Potential internship candidates**
Please read this if you are planning to apply for a Palisadoes Foundation internship https://github.com/PalisadoesFoundation/talawa/issues/359
|
non_design
|
incorrect and incomplete instructions in installation md describe the bug a clear and concise description of what the bug is there are some minor but important missing details in the mongodb url do not talks about passing a default db in connection string if not given the app don t throw a error during npm run dev but the connection is not made and the development data base is not created this is troubling for users new to mongodb discussed before step we have to trigger the creation of user object from register panel then only the user object in db will appear this step is not talked about the test file is a well documented example of what to do for resolver tests organizations spec js is misplaced i need to fix the path files to be changed to reproduce steps to reproduce the behavior expected behavior a clear and concise description of what you expected to happen actual behavior a clear and concise description of how the code performed w r t expectations screenshots if applicable add screenshots to help explain your problem additional details add any other context or screenshots about the feature request here potential internship candidates please read this if you are planning to apply for a palisadoes foundation internship
| 0
|
64,488
| 7,807,922,209
|
IssuesEvent
|
2018-06-11 18:28:15
|
PressStartHetic/press-start-project
|
https://api.github.com/repos/PressStartHetic/press-start-project
|
opened
|
Concevoir le wireframe de la page de Création de tags
|
Design
|
Ajout, vue, modification, suppression de tags
|
1.0
|
Concevoir le wireframe de la page de Création de tags - Ajout, vue, modification, suppression de tags
|
design
|
concevoir le wireframe de la page de création de tags ajout vue modification suppression de tags
| 1
|
172,070
| 27,230,411,127
|
IssuesEvent
|
2023-02-21 12:50:56
|
momocus/sakazuki
|
https://api.github.com/repos/momocus/sakazuki
|
closed
|
検索をしているときはページタイトルに検索ワードを入れたい
|
design
|
ブラウザの戻るページ一覧とかで、ただのトップページと検索中のトップページが区別できない。
できると、好きな検索に戻れて便利。
複数の去年の酒を検索してから複製新規作成するときにほしい。
|
1.0
|
検索をしているときはページタイトルに検索ワードを入れたい - ブラウザの戻るページ一覧とかで、ただのトップページと検索中のトップページが区別できない。
できると、好きな検索に戻れて便利。
複数の去年の酒を検索してから複製新規作成するときにほしい。
|
design
|
検索をしているときはページタイトルに検索ワードを入れたい ブラウザの戻るページ一覧とかで、ただのトップページと検索中のトップページが区別できない。 できると、好きな検索に戻れて便利。 複数の去年の酒を検索してから複製新規作成するときにほしい。
| 1
|
30,169
| 4,566,080,841
|
IssuesEvent
|
2016-09-15 04:44:52
|
Microsoft/vsts-tasks
|
https://api.github.com/repos/Microsoft/vsts-tasks
|
closed
|
A parameter cannot be found that matches parameter name 'vstestLocationMethod'
|
Area: Test bug
|
I'm suddenly getting this exeception when trying to run tests.
2016-09-13T08:11:22.1094992Z Executing the powershell script: C:\BuildAgent\tasks\VSTest\1.0.50\VSTest.ps1
2016-09-13T08:11:22.1876285Z ##[error]System.Management.Automation.ParameterBindingException: A parameter cannot be found that matches parameter name 'vstestLocationMethod'.
2016-09-13T08:11:22.1876285Z ##[error] at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
2016-09-13T08:11:22.1876285Z ##[error] at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
2016-09-13T08:11:22.1876285Z ##[error] at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync)
2016-09-13T08:11:22.2032386Z ##[error] at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
2016-09-13T08:11:22.2032386Z ##[error] at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
2016-09-13T08:11:22.2032386Z ##[error] at Microsoft.TeamFoundation.DistributedTask.Handlers.PowerShellHandler.Execute(ITaskContext context, CancellationToken cancellationToken, Int32 timeoutInMinutes)
2016-09-13T08:11:22.2032386Z ##[error] at Microsoft.TeamFoundation.DistributedTask.Worker.JobRunner.RunTask(ITaskContext context, TaskWrapper task, CancellationTokenSource tokenSource)
|
1.0
|
A parameter cannot be found that matches parameter name 'vstestLocationMethod' - I'm suddenly getting this exeception when trying to run tests.
2016-09-13T08:11:22.1094992Z Executing the powershell script: C:\BuildAgent\tasks\VSTest\1.0.50\VSTest.ps1
2016-09-13T08:11:22.1876285Z ##[error]System.Management.Automation.ParameterBindingException: A parameter cannot be found that matches parameter name 'vstestLocationMethod'.
2016-09-13T08:11:22.1876285Z ##[error] at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
2016-09-13T08:11:22.1876285Z ##[error] at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
2016-09-13T08:11:22.1876285Z ##[error] at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync)
2016-09-13T08:11:22.2032386Z ##[error] at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
2016-09-13T08:11:22.2032386Z ##[error] at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
2016-09-13T08:11:22.2032386Z ##[error] at Microsoft.TeamFoundation.DistributedTask.Handlers.PowerShellHandler.Execute(ITaskContext context, CancellationToken cancellationToken, Int32 timeoutInMinutes)
2016-09-13T08:11:22.2032386Z ##[error] at Microsoft.TeamFoundation.DistributedTask.Worker.JobRunner.RunTask(ITaskContext context, TaskWrapper task, CancellationTokenSource tokenSource)
|
non_design
|
a parameter cannot be found that matches parameter name vstestlocationmethod i m suddenly getting this exeception when trying to run tests executing the powershell script c buildagent tasks vstest vstest system management automation parameterbindingexception a parameter cannot be found that matches parameter name vstestlocationmethod at system management automation runspaces pipelinebase invoke ienumerable input at system management automation powershell worker constructpipelineanddowork runspace rs boolean performsyncinvoke at system management automation powershell worker createrunspaceifneededanddowork runspace rstouse boolean issync at system management automation powershell coreinvokehelper psdatacollection input psdatacollection output psinvocationsettings settings at system management automation powershell coreinvoke psdatacollection input psdatacollection output psinvocationsettings settings at microsoft teamfoundation distributedtask handlers powershellhandler execute itaskcontext context cancellationtoken cancellationtoken timeoutinminutes at microsoft teamfoundation distributedtask worker jobrunner runtask itaskcontext context taskwrapper task cancellationtokensource tokensource
| 0
|
37,106
| 4,778,318,498
|
IssuesEvent
|
2016-10-27 18:55:52
|
aspnet/IISIntegration
|
https://api.github.com/repos/aspnet/IISIntegration
|
closed
|
IIS custom error pages do not work with ANCM
|
0 - Backlog AspNetCoreModule needs design
|
The IIS custom error page feature allows IIS to provide/replace the response body for specific status codes. By default it will do this for 401,403,404,405,406,412,500,501,502. However, this does not work with ANCM/Kestrel, all configured error pages are bypassed and the original body from the application is returned to the client.
Questions:
- Do we want to support IIS custom error pages with Asp.Net Core? We have a replacement feature in Diagnostics called StatusCodePages. We also have multiple 500 pages.
- If yes, should it be opt-in or opt-out? If it were opt out you would be unable to see any of the Asp.Net diagnostics pages by default.
@DamianEdwards @shirhatti @pan-wang @davidfowl
|
1.0
|
IIS custom error pages do not work with ANCM - The IIS custom error page feature allows IIS to provide/replace the response body for specific status codes. By default it will do this for 401,403,404,405,406,412,500,501,502. However, this does not work with ANCM/Kestrel, all configured error pages are bypassed and the original body from the application is returned to the client.
Questions:
- Do we want to support IIS custom error pages with Asp.Net Core? We have a replacement feature in Diagnostics called StatusCodePages. We also have multiple 500 pages.
- If yes, should it be opt-in or opt-out? If it were opt out you would be unable to see any of the Asp.Net diagnostics pages by default.
@DamianEdwards @shirhatti @pan-wang @davidfowl
|
design
|
iis custom error pages do not work with ancm the iis custom error page feature allows iis to provide replace the response body for specific status codes by default it will do this for however this does not work with ancm kestrel all configured error pages are bypassed and the original body from the application is returned to the client questions do we want to support iis custom error pages with asp net core we have a replacement feature in diagnostics called statuscodepages we also have multiple pages if yes should it be opt in or opt out if it were opt out you would be unable to see any of the asp net diagnostics pages by default damianedwards shirhatti pan wang davidfowl
| 1
|
23,428
| 3,851,790,090
|
IssuesEvent
|
2016-04-06 04:49:52
|
ysdn-2016/ysdn-2016.github.io
|
https://api.github.com/repos/ysdn-2016/ysdn-2016.github.io
|
opened
|
(mobile) Sponsors page shapes
|
design
|
Can we separate the shapes that appear on the header on Sponsors page (mobile) 🙊
... and we should also bring the header up slightly so it matches the rest of the pages.
|
1.0
|
(mobile) Sponsors page shapes - Can we separate the shapes that appear on the header on Sponsors page (mobile) 🙊
... and we should also bring the header up slightly so it matches the rest of the pages.
|
design
|
mobile sponsors page shapes can we separate the shapes that appear on the header on sponsors page mobile 🙊 and we should also bring the header up slightly so it matches the rest of the pages
| 1
|
31,720
| 26,040,360,996
|
IssuesEvent
|
2022-12-22 09:53:20
|
TurtleEngr/gitproj
|
https://api.github.com/repos/TurtleEngr/gitproj
|
opened
|
Cleanup: Remove "internal" function tests
|
infrastructure
|
For good TDD, the tests should only test at the topmost interface or function inputs and outputs.
Tests for internal functions should be moved to a different test area. I.e. they are optional; they are only used when the functions are first created. Refactoring could remove or change internal functions. The important part is testing the interface inputs and the expected outputs, not how the internal functions work.
|
1.0
|
Cleanup: Remove "internal" function tests - For good TDD, the tests should only test at the topmost interface or function inputs and outputs.
Tests for internal functions should be moved to a different test area. I.e. they are optional; they are only used when the functions are first created. Refactoring could remove or change internal functions. The important part is testing the interface inputs and the expected outputs, not how the internal functions work.
|
non_design
|
cleanup remove internal function tests for good tdd the tests should only test at the topmost interface or function inputs and outputs tests for internal functions should be moved to a different test area i e they are optional they are only used when the functions are first created refactoring could remove or change internal functions the important part is testing the interface inputs and the expected outputs not how the internal functions work
| 0
|
60,687
| 7,373,762,869
|
IssuesEvent
|
2018-03-13 18:11:51
|
ParabolInc/action
|
https://api.github.com/repos/ParabolInc/action
|
closed
|
Date assignment and styling (aka The Passing of Time)
|
design discussion enhancement
|
## Issue - Enhancement
As a preliminary step to "floating boats", and as a step closer to "omniscient social automation":
1. (This should be an optional feature, not required)
2. ICON - create a simple calendar icon on the upper left - allow user to click & drag-select a Due Date.
3. COLORING - 4 densities of color: DARK=1wk out, MED=2wks out, LIGHT=3wks out, FAINT=4wks+; the color of the card is determined by what date the user selects
4. PROGRESS - Color progression from Faint > Light > Med > Dark is fully automated (and can be reset by the user at any time
5. LOCATION - column placement of the card is automated for first placement: Faint & Light = Future column; Med & Dark = Active column (automatically reset if user changes Due Date)
|
1.0
|
Date assignment and styling (aka The Passing of Time) - ## Issue - Enhancement
As a preliminary step to "floating boats", and as a step closer to "omniscient social automation":
1. (This should be an optional feature, not required)
2. ICON - create a simple calendar icon on the upper left - allow user to click & drag-select a Due Date.
3. COLORING - 4 densities of color: DARK=1wk out, MED=2wks out, LIGHT=3wks out, FAINT=4wks+; the color of the card is determined by what date the user selects
4. PROGRESS - Color progression from Faint > Light > Med > Dark is fully automated (and can be reset by the user at any time
5. LOCATION - column placement of the card is automated for first placement: Faint & Light = Future column; Med & Dark = Active column (automatically reset if user changes Due Date)
|
design
|
date assignment and styling aka the passing of time issue enhancement as a preliminary step to floating boats and as a step closer to omniscient social automation this should be an optional feature not required icon create a simple calendar icon on the upper left allow user to click drag select a due date coloring densities of color dark out med out light out faint the color of the card is determined by what date the user selects progress color progression from faint light med dark is fully automated and can be reset by the user at any time location column placement of the card is automated for first placement faint light future column med dark active column automatically reset if user changes due date
| 1
|
202,760
| 7,054,467,977
|
IssuesEvent
|
2018-01-04 00:57:02
|
Navarra/game
|
https://api.github.com/repos/Navarra/game
|
opened
|
Add a game-loop and start using requestAnimationFrame
|
canvas core engine enhancement hard high priority
|
At the moment, in its nubile infancy, Navarra does not have a game-loop and this needs to change. Yes, it's `<canvas>` game that is also lacking in bits for graphics, but I think it would be imperative to add a game loop not only for the graphics (which would more than handle it) but also for the readability and logistics of it.
I propose we start using: [requestAnimationFrame](https://developer.mozilla.org/en-US/docs/Web/API/window/requestAnimationFrame).
> The **window.requestAnimationFrame()** method tells the browser that you wish to perform an animation and requests that the browser call a specified function to update an animation before the next repaint. The method takes a callback as an argument to be invoked before the repaint.
The `<canvas>` will be refreshed and all will be well. The monsters will be in their places, the items dropped will be there and of course, eventually, other connected players.
This means that the `game.js` file will slowly be migrated over to `engine.js` and that's where the game will kick off in a more apt manner.
Let me know if any of you have any objections. I think this is a step in the right direction.
|
1.0
|
Add a game-loop and start using requestAnimationFrame - At the moment, in its nubile infancy, Navarra does not have a game-loop and this needs to change. Yes, it's `<canvas>` game that is also lacking in bits for graphics, but I think it would be imperative to add a game loop not only for the graphics (which would more than handle it) but also for the readability and logistics of it.
I propose we start using: [requestAnimationFrame](https://developer.mozilla.org/en-US/docs/Web/API/window/requestAnimationFrame).
> The **window.requestAnimationFrame()** method tells the browser that you wish to perform an animation and requests that the browser call a specified function to update an animation before the next repaint. The method takes a callback as an argument to be invoked before the repaint.
The `<canvas>` will be refreshed and all will be well. The monsters will be in their places, the items dropped will be there and of course, eventually, other connected players.
This means that the `game.js` file will slowly be migrated over to `engine.js` and that's where the game will kick off in a more apt manner.
Let me know if any of you have any objections. I think this is a step in the right direction.
|
non_design
|
add a game loop and start using requestanimationframe at the moment in its nubile infancy navarra does not have a game loop and this needs to change yes it s game that is also lacking in bits for graphics but i think it would be imperative to add a game loop not only for the graphics which would more than handle it but also for the readability and logistics of it i propose we start using the window requestanimationframe method tells the browser that you wish to perform an animation and requests that the browser call a specified function to update an animation before the next repaint the method takes a callback as an argument to be invoked before the repaint the will be refreshed and all will be well the monsters will be in their places the items dropped will be there and of course eventually other connected players this means that the game js file will slowly be migrated over to engine js and that s where the game will kick off in a more apt manner let me know if any of you have any objections i think this is a step in the right direction
| 0
|
63,806
| 7,744,941,059
|
IssuesEvent
|
2018-05-29 16:45:00
|
DrewSimtech/optimizer
|
https://api.github.com/repos/DrewSimtech/optimizer
|
opened
|
Research best iterative method for restarts
|
Designer Testing and Research
|
As a designer I would like to better understand methods for propagating initial searches. Initial impressions lead me to believe that random restart with Gaussian distribution would work best.
|
1.0
|
Research best iterative method for restarts - As a designer I would like to better understand methods for propagating initial searches. Initial impressions lead me to believe that random restart with Gaussian distribution would work best.
|
design
|
research best iterative method for restarts as a designer i would like to better understand methods for propagating initial searches initial impressions lead me to believe that random restart with gaussian distribution would work best
| 1
|
76,136
| 26,258,724,247
|
IssuesEvent
|
2023-01-06 04:52:22
|
vector-im/element-web
|
https://api.github.com/repos/vector-im/element-web
|
closed
|
Problem with SSL unable to use the chat app - https://matrix-client.matrix.org/
|
T-Defect
|
### Steps to reproduce
Unable to send message due to expired home server
https://matrix-client.matrix.org/
### Outcome
#### What did you expect?
#### What happened instead?
### Operating system
All versions
### Application version
Latest Version
### How did you install the app?
From the website
### Homeserver
https://matrix-client.matrix.org/
### Will you send logs?
No
|
1.0
|
Problem with SSL unable to use the chat app - https://matrix-client.matrix.org/ - ### Steps to reproduce
Unable to send message due to expired home server
https://matrix-client.matrix.org/
### Outcome
#### What did you expect?
#### What happened instead?
### Operating system
All versions
### Application version
Latest Version
### How did you install the app?
From the website
### Homeserver
https://matrix-client.matrix.org/
### Will you send logs?
No
|
non_design
|
problem with ssl unable to use the chat app steps to reproduce unable to send message due to expired home server outcome what did you expect what happened instead operating system all versions application version latest version how did you install the app from the website homeserver will you send logs no
| 0
|
75,841
| 21,009,283,984
|
IssuesEvent
|
2022-03-30 03:49:59
|
google/mediapipe
|
https://api.github.com/repos/google/mediapipe
|
opened
|
Error in android_sdk_repository: Cannot redefine repository after any load statement in the WORKSPACE file (for repository 'androidsdk')
|
type:build/install
|
ERROR: Traceback (most recent call last):
File "/home/alg/ai/mediapipe/WORKSPACE", line 418, column 23, in <toplevel>
android_sdk_repository(name = "androidsdk", path = "/root/Android/Sdk")
Error in android_sdk_repository: Cannot redefine repository after any load statement in the WORKSPACE file (for repository 'androidsdk')
ERROR: error loading package 'external': Package 'external' contains errors
INFO: Elapsed time: 0.945s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
|
1.0
|
Error in android_sdk_repository: Cannot redefine repository after any load statement in the WORKSPACE file (for repository 'androidsdk') - ERROR: Traceback (most recent call last):
File "/home/alg/ai/mediapipe/WORKSPACE", line 418, column 23, in <toplevel>
android_sdk_repository(name = "androidsdk", path = "/root/Android/Sdk")
Error in android_sdk_repository: Cannot redefine repository after any load statement in the WORKSPACE file (for repository 'androidsdk')
ERROR: error loading package 'external': Package 'external' contains errors
INFO: Elapsed time: 0.945s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
|
non_design
|
error in android sdk repository cannot redefine repository after any load statement in the workspace file for repository androidsdk error traceback most recent call last file home alg ai mediapipe workspace line column in android sdk repository name androidsdk path root android sdk error in android sdk repository cannot redefine repository after any load statement in the workspace file for repository androidsdk error error loading package external package external contains errors info elapsed time info processes failed build did not complete successfully packages loaded
| 0
|
26,307
| 4,676,673,238
|
IssuesEvent
|
2016-10-07 12:47:50
|
phingofficial/phing-issues-test
|
https://api.github.com/repos/phingofficial/phing-issues-test
|
opened
|
Add API documentation (Trac #7)
|
defect documentation Incomplete Migration Migrated from Trac
|
Migrated from https://www.phing.info/trac/ticket/7
```json
{
"status": "closed",
"changetime": "2009-08-22T09:00:48",
"description": "both API docs (current and 2.2.0) down :&\n\nsee http://phing.info/trac/wiki/Users/Documentation/API",
"reporter": "bmuskalla",
"cc": "",
"resolution": "invalid",
"_ts": "1250931648000000",
"component": "documentation",
"summary": "Add API documentation",
"priority": "minor",
"keywords": "api docs",
"version": "",
"time": "2006-03-01T23:54:23",
"milestone": "Icebox",
"owner": "",
"type": "defect"
}
```
|
1.0
|
Add API documentation (Trac #7) - Migrated from https://www.phing.info/trac/ticket/7
```json
{
"status": "closed",
"changetime": "2009-08-22T09:00:48",
"description": "both API docs (current and 2.2.0) down :&\n\nsee http://phing.info/trac/wiki/Users/Documentation/API",
"reporter": "bmuskalla",
"cc": "",
"resolution": "invalid",
"_ts": "1250931648000000",
"component": "documentation",
"summary": "Add API documentation",
"priority": "minor",
"keywords": "api docs",
"version": "",
"time": "2006-03-01T23:54:23",
"milestone": "Icebox",
"owner": "",
"type": "defect"
}
```
|
non_design
|
add api documentation trac migrated from json status closed changetime description both api docs current and down n nsee reporter bmuskalla cc resolution invalid ts component documentation summary add api documentation priority minor keywords api docs version time milestone icebox owner type defect
| 0
|
91,510
| 10,722,231,690
|
IssuesEvent
|
2019-10-27 10:22:35
|
Cockatrice/Cockatrice
|
https://api.github.com/repos/Cockatrice/Cockatrice
|
closed
|
Wiki Updates
|
Documentation
|
Re-add wiki support for MSVC140/etc files. Seems to be coming up again a lot.
https://github.com/Cockatrice/Cockatrice/wiki/Troubleshooting/_compare/6b42344a31514136c7d8682619ec061faa619fa9...5b9b6f19ea2f5444dc5fa0ddd1be33dc3d762391
cc: @tooomm
|
1.0
|
Wiki Updates - Re-add wiki support for MSVC140/etc files. Seems to be coming up again a lot.
https://github.com/Cockatrice/Cockatrice/wiki/Troubleshooting/_compare/6b42344a31514136c7d8682619ec061faa619fa9...5b9b6f19ea2f5444dc5fa0ddd1be33dc3d762391
cc: @tooomm
|
non_design
|
wiki updates re add wiki support for etc files seems to be coming up again a lot cc tooomm
| 0
|
259,302
| 27,621,800,726
|
IssuesEvent
|
2023-03-10 01:12:36
|
nidhi7598/linux-3.0.35
|
https://api.github.com/repos/nidhi7598/linux-3.0.35
|
closed
|
CVE-2018-5995 (Medium) detected in linuxlinux-3.0.40 - autoclosed
|
Mend: dependency security vulnerability
|
## CVE-2018-5995 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-3.0.40</b></p></summary>
<p>
<p>Apache Software Foundation (ASF)</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v3.0/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v3.0/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/nidhi7598/linux-3.0.35/commit/4cc6d4a22f88b8effe1090492c1a242ce587b492">4cc6d4a22f88b8effe1090492c1a242ce587b492</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/lib/vsprintf.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The pcpu_embed_first_chunk function in mm/percpu.c in the Linux kernel through 4.14.14 allows local users to obtain sensitive address information by reading dmesg data from a "pages/cpu" printk call.
<p>Publish Date: 2018-08-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-5995>CVE-2018-5995</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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-2018-5995">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5995</a></p>
<p>Release Date: 2018-08-07</p>
<p>Fix Resolution: v4.15-rc2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2018-5995 (Medium) detected in linuxlinux-3.0.40 - autoclosed - ## CVE-2018-5995 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-3.0.40</b></p></summary>
<p>
<p>Apache Software Foundation (ASF)</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v3.0/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v3.0/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/nidhi7598/linux-3.0.35/commit/4cc6d4a22f88b8effe1090492c1a242ce587b492">4cc6d4a22f88b8effe1090492c1a242ce587b492</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/lib/vsprintf.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The pcpu_embed_first_chunk function in mm/percpu.c in the Linux kernel through 4.14.14 allows local users to obtain sensitive address information by reading dmesg data from a "pages/cpu" printk call.
<p>Publish Date: 2018-08-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-5995>CVE-2018-5995</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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-2018-5995">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5995</a></p>
<p>Release Date: 2018-08-07</p>
<p>Fix Resolution: v4.15-rc2</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 linuxlinux autoclosed cve medium severity vulnerability vulnerable library linuxlinux apache software foundation asf library home page a href found in head commit a href found in base branch master vulnerable source files lib vsprintf c vulnerability details the pcpu embed first chunk function in mm percpu c in the linux kernel through allows local users to obtain sensitive address information by reading dmesg data from a pages cpu printk call publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend
| 0
|
36,378
| 9,798,395,784
|
IssuesEvent
|
2019-06-11 12:18:40
|
GetTerminus/tslint-config-frontend
|
https://api.github.com/repos/GetTerminus/tslint-config-frontend
|
closed
|
Address fstream dependency security issue
|
Focus: build Type: chore
|
- [ ] Update dependencies as needed to resolve security issues
|
1.0
|
Address fstream dependency security issue - 
- [ ] Update dependencies as needed to resolve security issues
|
non_design
|
address fstream dependency security issue update dependencies as needed to resolve security issues
| 0
|
456,496
| 13,150,826,412
|
IssuesEvent
|
2020-08-09 13:43:29
|
chrisjsewell/docutils
|
https://api.github.com/repos/chrisjsewell/docutils
|
closed
|
Trouble Using Images with rst2pdf.py [SF:bugs:81]
|
bugs closed-fixed priority-5
|
author: jrush
created: 2007-04-04 09:51:24
assigned: grubert
SF_url: https://sourceforge.net/p/docutils/bugs/81
Using rst2pdf.py to convert a small document with an embedded image fails, with a few LaTeX error messages:
Package typearea, 2004/09/16 v2.9t LaTeX2e KOMA package
Copyright \(C\) Frank Neukam, 1992-1994
Copyright \(C\) Markus Kohm, 1994-2002
Package typearea Warning: Bad DIV-value\!
\(typearea\) You should decrease DIV, increase fontsize or
\(typearea\) change papersize.
A few of these:
\! Illegal unit of measure \(pt inserted\).
<use storage-proxy.png>
Overfull \hbox \(34.36905pt too wide\) in paragraph at lines 166--167
It seems LaTeX does not degrade gracefully when things don't fit, unlike HTML which always finds a way.
---
commenter: jrush
posted: 2007-04-04 09:51:24
title: #81 Trouble Using Images with rst2pdf.py
attachments:
- https://sourceforge.net/p/docutils/bugs/_discuss/thread/91301145/1b6b/attachment/pdfimages.tgz
rst document, run log, two images used
---
commenter: grubert
posted: 2007-04-04 10:21:27
title: #81 Trouble Using Images with rst2pdf.py
- **assigned_to**: nobody --> grubert
---
commenter: grubert
posted: 2007-04-04 10:21:27
title: #81 Trouble Using Images with rst2pdf.py
Logged In: YES
user\_id=147070
Originator: NO
> \! Illegal unit of measure \(pt inserted\).
this is an error, the typearea Warning is a warning.
> <use storage-proxy.png>
> Overfull \hbox \(34.36905pt too wide\) in paragraph at lines 166--167
this means it is too wide
> It seems LaTeX does not degrade gracefully when things don't fit, unlike
> HTML which always finds a way.\!
sideway scrolling is harder on printouts ?
could you publish a short sample somewhere, so i can have a closer look ?
---
commenter: jrush
posted: 2007-04-04 17:43:15
title: #81 Trouble Using Images with rst2pdf.py
Logged In: YES
user\_id=56840
Originator: YES
There is an attachment to the bug report containing the rst document in question, along with the two images it includes and a sample run log. If you need more, just let me know.
---
commenter: grubert
posted: 2007-04-05 19:37:15
title: #81 Trouble Using Images with rst2pdf.py
Logged In: YES
user\_id=147070
Originator: NO
problemlist
1\. you want the image right aligned with text flowing around
align=right does not tell this, it just happens to work
so in html ?
2\. width=965,height=458 without units does not define much.
i guess graphicx in pdfmode then uses pt. not that
bad. 1pt=1/72in correct ? is this what you want
the first one is 485 wide \(measured in gv\) this is
965\*0.5
3\. for printing eps or pdf files would be necessary, so i
assume you want screenreadpdf ?
---
commenter: milde
posted: 2009-09-07 07:54:25
title: #81 Trouble Using Images with rst2pdf.py
This is fixed in the SVN \(upcoming 0.6 release\)
---
commenter: milde
posted: 2009-09-07 07:54:28
title: #81 Trouble Using Images with rst2pdf.py
- **status**: open --> open-fixed
---
commenter: milde
posted: 2009-09-07 09:14:41
title: #81 Trouble Using Images with rst2pdf.py
- **status**: open-fixed --> closed-fixed
|
1.0
|
Trouble Using Images with rst2pdf.py [SF:bugs:81] -
author: jrush
created: 2007-04-04 09:51:24
assigned: grubert
SF_url: https://sourceforge.net/p/docutils/bugs/81
Using rst2pdf.py to convert a small document with an embedded image fails, with a few LaTeX error messages:
Package typearea, 2004/09/16 v2.9t LaTeX2e KOMA package
Copyright \(C\) Frank Neukam, 1992-1994
Copyright \(C\) Markus Kohm, 1994-2002
Package typearea Warning: Bad DIV-value\!
\(typearea\) You should decrease DIV, increase fontsize or
\(typearea\) change papersize.
A few of these:
\! Illegal unit of measure \(pt inserted\).
<use storage-proxy.png>
Overfull \hbox \(34.36905pt too wide\) in paragraph at lines 166--167
It seems LaTeX does not degrade gracefully when things don't fit, unlike HTML which always finds a way.
---
commenter: jrush
posted: 2007-04-04 09:51:24
title: #81 Trouble Using Images with rst2pdf.py
attachments:
- https://sourceforge.net/p/docutils/bugs/_discuss/thread/91301145/1b6b/attachment/pdfimages.tgz
rst document, run log, two images used
---
commenter: grubert
posted: 2007-04-04 10:21:27
title: #81 Trouble Using Images with rst2pdf.py
- **assigned_to**: nobody --> grubert
---
commenter: grubert
posted: 2007-04-04 10:21:27
title: #81 Trouble Using Images with rst2pdf.py
Logged In: YES
user\_id=147070
Originator: NO
> \! Illegal unit of measure \(pt inserted\).
this is an error, the typearea Warning is a warning.
> <use storage-proxy.png>
> Overfull \hbox \(34.36905pt too wide\) in paragraph at lines 166--167
this means it is too wide
> It seems LaTeX does not degrade gracefully when things don't fit, unlike
> HTML which always finds a way.\!
sideway scrolling is harder on printouts ?
could you publish a short sample somewhere, so i can have a closer look ?
---
commenter: jrush
posted: 2007-04-04 17:43:15
title: #81 Trouble Using Images with rst2pdf.py
Logged In: YES
user\_id=56840
Originator: YES
There is an attachment to the bug report containing the rst document in question, along with the two images it includes and a sample run log. If you need more, just let me know.
---
commenter: grubert
posted: 2007-04-05 19:37:15
title: #81 Trouble Using Images with rst2pdf.py
Logged In: YES
user\_id=147070
Originator: NO
problemlist
1\. you want the image right aligned with text flowing around
align=right does not tell this, it just happens to work
so in html ?
2\. width=965,height=458 without units does not define much.
i guess graphicx in pdfmode then uses pt. not that
bad. 1pt=1/72in correct ? is this what you want
the first one is 485 wide \(measured in gv\) this is
965\*0.5
3\. for printing eps or pdf files would be necessary, so i
assume you want screenreadpdf ?
---
commenter: milde
posted: 2009-09-07 07:54:25
title: #81 Trouble Using Images with rst2pdf.py
This is fixed in the SVN \(upcoming 0.6 release\)
---
commenter: milde
posted: 2009-09-07 07:54:28
title: #81 Trouble Using Images with rst2pdf.py
- **status**: open --> open-fixed
---
commenter: milde
posted: 2009-09-07 09:14:41
title: #81 Trouble Using Images with rst2pdf.py
- **status**: open-fixed --> closed-fixed
|
non_design
|
trouble using images with py author jrush created assigned grubert sf url using py to convert a small document with an embedded image fails with a few latex error messages package typearea koma package copyright c frank neukam copyright c markus kohm package typearea warning bad div value typearea you should decrease div increase fontsize or typearea change papersize a few of these illegal unit of measure pt inserted overfull hbox too wide in paragraph at lines it seems latex does not degrade gracefully when things don t fit unlike html which always finds a way commenter jrush posted title trouble using images with py attachments rst document run log two images used commenter grubert posted title trouble using images with py assigned to nobody grubert commenter grubert posted title trouble using images with py logged in yes user id originator no illegal unit of measure pt inserted this is an error the typearea warning is a warning overfull hbox too wide in paragraph at lines this means it is too wide it seems latex does not degrade gracefully when things don t fit unlike html which always finds a way sideway scrolling is harder on printouts could you publish a short sample somewhere so i can have a closer look commenter jrush posted title trouble using images with py logged in yes user id originator yes there is an attachment to the bug report containing the rst document in question along with the two images it includes and a sample run log if you need more just let me know commenter grubert posted title trouble using images with py logged in yes user id originator no problemlist you want the image right aligned with text flowing around align right does not tell this it just happens to work so in html width height without units does not define much i guess graphicx in pdfmode then uses pt not that bad correct is this what you want the first one is wide measured in gv this is for printing eps or pdf files would be necessary so i assume you want screenreadpdf commenter milde posted title trouble using images with py this is fixed in the svn upcoming release commenter milde posted title trouble using images with py status open open fixed commenter milde posted title trouble using images with py status open fixed closed fixed
| 0
|
116,039
| 17,358,317,177
|
IssuesEvent
|
2021-07-29 16:56:30
|
Tim-sandbox/webgoat-trng
|
https://api.github.com/repos/Tim-sandbox/webgoat-trng
|
opened
|
CVE-2019-10747 (High) detected in set-value-2.0.0.tgz, set-value-0.4.3.tgz
|
security vulnerability
|
## CVE-2019-10747 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>set-value-2.0.0.tgz</b>, <b>set-value-0.4.3.tgz</b></p></summary>
<p>
<details><summary><b>set-value-2.0.0.tgz</b></p></summary>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-2.0.0.tgz">https://registry.npmjs.org/set-value/-/set-value-2.0.0.tgz</a></p>
<p>Path to dependency file: webgoat-trng/docs/package.json</p>
<p>Path to vulnerable library: webgoat-trng/docs/node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- browser-sync-2.26.3.tgz (Root Library)
- chokidar-2.0.4.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- :x: **set-value-2.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>set-value-0.4.3.tgz</b></p></summary>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-0.4.3.tgz">https://registry.npmjs.org/set-value/-/set-value-0.4.3.tgz</a></p>
<p>Path to dependency file: webgoat-trng/docs/package.json</p>
<p>Path to vulnerable library: webgoat-trng/docs/node_modules/union-value/node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- browser-sync-2.26.3.tgz (Root Library)
- chokidar-2.0.4.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- union-value-1.0.0.tgz
- :x: **set-value-0.4.3.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Tim-sandbox/webgoat-trng/commit/35c20cdfd5acad60536ca6b0402f619e18097690">35c20cdfd5acad60536ca6b0402f619e18097690</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
set-value is vulnerable to Prototype Pollution in versions lower than 3.0.1. The function mixin-deep could be tricked into adding or modifying properties of Object.prototype using any of the constructor, prototype and _proto_ payloads.
<p>Publish Date: 2019-08-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10747>CVE-2019-10747</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/jonschlinkert/set-value/commit/95e9d9923f8a8b4a01da1ea138fcc39ec7b6b15f">https://github.com/jonschlinkert/set-value/commit/95e9d9923f8a8b4a01da1ea138fcc39ec7b6b15f</a></p>
<p>Release Date: 2019-07-24</p>
<p>Fix Resolution: 2.0.1,3.0.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"set-value","packageVersion":"2.0.0","packageFilePaths":["/docs/package.json"],"isTransitiveDependency":true,"dependencyTree":"browser-sync:2.26.3;chokidar:2.0.4;braces:2.3.2;snapdragon:0.8.2;base:0.11.2;cache-base:1.0.1;set-value:2.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.0.1,3.0.1"},{"packageType":"javascript/Node.js","packageName":"set-value","packageVersion":"0.4.3","packageFilePaths":["/docs/package.json"],"isTransitiveDependency":true,"dependencyTree":"browser-sync:2.26.3;chokidar:2.0.4;braces:2.3.2;snapdragon:0.8.2;base:0.11.2;cache-base:1.0.1;union-value:1.0.0;set-value:0.4.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.0.1,3.0.1"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2019-10747","vulnerabilityDetails":"set-value is vulnerable to Prototype Pollution in versions lower than 3.0.1. The function mixin-deep could be tricked into adding or modifying properties of Object.prototype using any of the constructor, prototype and _proto_ payloads.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10747","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2019-10747 (High) detected in set-value-2.0.0.tgz, set-value-0.4.3.tgz - ## CVE-2019-10747 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>set-value-2.0.0.tgz</b>, <b>set-value-0.4.3.tgz</b></p></summary>
<p>
<details><summary><b>set-value-2.0.0.tgz</b></p></summary>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-2.0.0.tgz">https://registry.npmjs.org/set-value/-/set-value-2.0.0.tgz</a></p>
<p>Path to dependency file: webgoat-trng/docs/package.json</p>
<p>Path to vulnerable library: webgoat-trng/docs/node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- browser-sync-2.26.3.tgz (Root Library)
- chokidar-2.0.4.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- :x: **set-value-2.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>set-value-0.4.3.tgz</b></p></summary>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-0.4.3.tgz">https://registry.npmjs.org/set-value/-/set-value-0.4.3.tgz</a></p>
<p>Path to dependency file: webgoat-trng/docs/package.json</p>
<p>Path to vulnerable library: webgoat-trng/docs/node_modules/union-value/node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- browser-sync-2.26.3.tgz (Root Library)
- chokidar-2.0.4.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- union-value-1.0.0.tgz
- :x: **set-value-0.4.3.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Tim-sandbox/webgoat-trng/commit/35c20cdfd5acad60536ca6b0402f619e18097690">35c20cdfd5acad60536ca6b0402f619e18097690</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
set-value is vulnerable to Prototype Pollution in versions lower than 3.0.1. The function mixin-deep could be tricked into adding or modifying properties of Object.prototype using any of the constructor, prototype and _proto_ payloads.
<p>Publish Date: 2019-08-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10747>CVE-2019-10747</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/jonschlinkert/set-value/commit/95e9d9923f8a8b4a01da1ea138fcc39ec7b6b15f">https://github.com/jonschlinkert/set-value/commit/95e9d9923f8a8b4a01da1ea138fcc39ec7b6b15f</a></p>
<p>Release Date: 2019-07-24</p>
<p>Fix Resolution: 2.0.1,3.0.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"set-value","packageVersion":"2.0.0","packageFilePaths":["/docs/package.json"],"isTransitiveDependency":true,"dependencyTree":"browser-sync:2.26.3;chokidar:2.0.4;braces:2.3.2;snapdragon:0.8.2;base:0.11.2;cache-base:1.0.1;set-value:2.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.0.1,3.0.1"},{"packageType":"javascript/Node.js","packageName":"set-value","packageVersion":"0.4.3","packageFilePaths":["/docs/package.json"],"isTransitiveDependency":true,"dependencyTree":"browser-sync:2.26.3;chokidar:2.0.4;braces:2.3.2;snapdragon:0.8.2;base:0.11.2;cache-base:1.0.1;union-value:1.0.0;set-value:0.4.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.0.1,3.0.1"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2019-10747","vulnerabilityDetails":"set-value is vulnerable to Prototype Pollution in versions lower than 3.0.1. The function mixin-deep could be tricked into adding or modifying properties of Object.prototype using any of the constructor, prototype and _proto_ payloads.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10747","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
|
non_design
|
cve high detected in set value tgz set value tgz cve high severity vulnerability vulnerable libraries set value tgz set value tgz set value tgz create nested values and any intermediaries using dot notation a b c paths library home page a href path to dependency file webgoat trng docs package json path to vulnerable library webgoat trng docs node modules set value package json dependency hierarchy browser sync tgz root library chokidar tgz braces tgz snapdragon tgz base tgz cache base tgz x set value tgz vulnerable library set value tgz create nested values and any intermediaries using dot notation a b c paths library home page a href path to dependency file webgoat trng docs package json path to vulnerable library webgoat trng docs node modules union value node modules set value package json dependency hierarchy browser sync tgz root library chokidar tgz braces tgz snapdragon tgz base tgz cache base tgz union value tgz x set value tgz vulnerable library found in head commit a href found in base branch main vulnerability details set value is vulnerable to prototype pollution in versions lower than the function mixin deep could be tricked into adding or modifying properties of object prototype using any of the constructor prototype and proto payloads publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree browser sync chokidar braces snapdragon base cache base set value isminimumfixversionavailable true minimumfixversion packagetype javascript node js packagename set value packageversion packagefilepaths istransitivedependency true dependencytree browser sync chokidar braces snapdragon base cache base union value set value isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier cve vulnerabilitydetails set value is vulnerable to prototype pollution in versions lower than the function mixin deep could be tricked into adding or modifying properties of object prototype using any of the constructor prototype and proto payloads vulnerabilityurl
| 0
|
98,822
| 12,370,639,809
|
IssuesEvent
|
2020-05-18 17:08:27
|
cloudfour/cloudfour.com-patterns
|
https://api.github.com/repos/cloudfour/cloudfour.com-patterns
|
closed
|
Update icons
|
size:10 🎨 design
|
I like our current icon set, but there are a few small updates they would benefit from in the short term.
## Current Source File Location
In our shared project file location, the Illustrator files for icons are in Icons ▸ Glyphs.
## Retire some icons
There are a few icons we are never using or will likely stop using that we can remove:
- [x] **dot**: Was used by the radio pattern, which no longer exists since we never used it.
- [x] **lanyrd**: This site has been broken [since 2019](https://en.wikipedia.org/wiki/Lanyrd).
- [x] **notification:** It's unclear what this icon was meant to do that wasn't covered by **notifications**. It isn't used in any templates.
## Organization
Currently our icons sit in one folder, but I think these might benefit from some reorganization:
- [x] Original icons should sit at the root of the icons directory. These include glyphs like arrows, link, notifications, etc.
- [x] Icons representing third-party brands should be moved to a "brands" subdirectory. These include icons for publications (A List Apart, Smashing, etc.), social media websites, etc.
- [x] Our logo should be moved _out_ of icons, possibly one level up.
This organization should also be reflected in our source files, with separate files for each type of asset.
Why? I'll get to that next…
## Sizing
The biggest design opportunity with our icons is to reconcile differences in perceived visual size.
Some icons look proportionate to one another. Notice how the smaller caret (used for dropdowns) is smaller in proportion to the check mark, the same way that the ▾ character is typically rendered compared to ✔️:
<img width="322" alt="Screen Shot 2020-04-24 at 4 30 08 PM" src="https://user-images.githubusercontent.com/69633/80264394-e2428900-8648-11ea-82e5-69ae7a800998.png">
But this is not true of all icons. Notice how small the notification bell 🔔 feels in comparison to ➕ :
<img width="307" alt="Screen Shot 2020-04-24 at 4 31 37 PM" src="https://user-images.githubusercontent.com/69633/80264469-19189f00-8649-11ea-8549-43fc42e4b35e.png">
The [Material Icon Design Principles](https://material.io/design/iconography/system-icons.html#grid-and-keyline-shapes) page does a good job of illustrating some of the concepts between icon sizing and composition to promote consistency and prevent these issues.
This is also why I feel it's important to organize our icons better. By sizing them relative to each other, maybe the Lanyrd (RIP) icon (which extends dramatically into the top-left corner) wouldn't be threatening to devour the GitHub icon (which is confined to a circle):
<img width="116" alt="Screen Shot 2020-04-24 at 4 32 20 PM" src="https://user-images.githubusercontent.com/69633/80264513-436a5c80-8649-11ea-8017-75df3632c8e1.png">
Finally, the logo is used primarily as a _branding_ element (not an icon). Arbitrarily squashing it into our 24×24 grid raises three issues:
- We have to scale the element up for its primary use case, which is silly.
- Its coordinates will have more decimal points, which increases the size of the markup required to define the shape.
- Decimal points may be rounded for performance, which could result in quality loss.
So to summarize the goals here:
- [x] Resize icons as a family so they will read as _visually_ consistent, rather than simply filling the `viewBox`.
- [x] Treat logo asset as separate and don't squash it down like an icon.
## Simplify stroke colors
In our preview icon pattern, any patterns that used a stroke color instead of a fill color had to specify `stroke="currentColor"`. This is no longer the case, so it can be left off those patterns entirely.
- [x] Remove unnecessary `stroke` attributes.
## Not in scope…
- Sweeping revisions to our icon styles. We should certainly tweak things like `stroke-width` to account for the resizing, but we should stick with our current angles, our chunky hearts and envelopes, etc.
- It feels a little clunky in 2020 to be pointing people to a shared directory so they can open Illustrator and manually export SVGs. But while I'd love to explore a GitHub-style [Figma integration](https://github.blog/2018-04-12-driving-changes-from-designs/) for this, I think that's turning a modest task into a gargantuan one.
|
1.0
|
Update icons - I like our current icon set, but there are a few small updates they would benefit from in the short term.
## Current Source File Location
In our shared project file location, the Illustrator files for icons are in Icons ▸ Glyphs.
## Retire some icons
There are a few icons we are never using or will likely stop using that we can remove:
- [x] **dot**: Was used by the radio pattern, which no longer exists since we never used it.
- [x] **lanyrd**: This site has been broken [since 2019](https://en.wikipedia.org/wiki/Lanyrd).
- [x] **notification:** It's unclear what this icon was meant to do that wasn't covered by **notifications**. It isn't used in any templates.
## Organization
Currently our icons sit in one folder, but I think these might benefit from some reorganization:
- [x] Original icons should sit at the root of the icons directory. These include glyphs like arrows, link, notifications, etc.
- [x] Icons representing third-party brands should be moved to a "brands" subdirectory. These include icons for publications (A List Apart, Smashing, etc.), social media websites, etc.
- [x] Our logo should be moved _out_ of icons, possibly one level up.
This organization should also be reflected in our source files, with separate files for each type of asset.
Why? I'll get to that next…
## Sizing
The biggest design opportunity with our icons is to reconcile differences in perceived visual size.
Some icons look proportionate to one another. Notice how the smaller caret (used for dropdowns) is smaller in proportion to the check mark, the same way that the ▾ character is typically rendered compared to ✔️:
<img width="322" alt="Screen Shot 2020-04-24 at 4 30 08 PM" src="https://user-images.githubusercontent.com/69633/80264394-e2428900-8648-11ea-82e5-69ae7a800998.png">
But this is not true of all icons. Notice how small the notification bell 🔔 feels in comparison to ➕ :
<img width="307" alt="Screen Shot 2020-04-24 at 4 31 37 PM" src="https://user-images.githubusercontent.com/69633/80264469-19189f00-8649-11ea-8549-43fc42e4b35e.png">
The [Material Icon Design Principles](https://material.io/design/iconography/system-icons.html#grid-and-keyline-shapes) page does a good job of illustrating some of the concepts between icon sizing and composition to promote consistency and prevent these issues.
This is also why I feel it's important to organize our icons better. By sizing them relative to each other, maybe the Lanyrd (RIP) icon (which extends dramatically into the top-left corner) wouldn't be threatening to devour the GitHub icon (which is confined to a circle):
<img width="116" alt="Screen Shot 2020-04-24 at 4 32 20 PM" src="https://user-images.githubusercontent.com/69633/80264513-436a5c80-8649-11ea-8017-75df3632c8e1.png">
Finally, the logo is used primarily as a _branding_ element (not an icon). Arbitrarily squashing it into our 24×24 grid raises three issues:
- We have to scale the element up for its primary use case, which is silly.
- Its coordinates will have more decimal points, which increases the size of the markup required to define the shape.
- Decimal points may be rounded for performance, which could result in quality loss.
So to summarize the goals here:
- [x] Resize icons as a family so they will read as _visually_ consistent, rather than simply filling the `viewBox`.
- [x] Treat logo asset as separate and don't squash it down like an icon.
## Simplify stroke colors
In our preview icon pattern, any patterns that used a stroke color instead of a fill color had to specify `stroke="currentColor"`. This is no longer the case, so it can be left off those patterns entirely.
- [x] Remove unnecessary `stroke` attributes.
## Not in scope…
- Sweeping revisions to our icon styles. We should certainly tweak things like `stroke-width` to account for the resizing, but we should stick with our current angles, our chunky hearts and envelopes, etc.
- It feels a little clunky in 2020 to be pointing people to a shared directory so they can open Illustrator and manually export SVGs. But while I'd love to explore a GitHub-style [Figma integration](https://github.blog/2018-04-12-driving-changes-from-designs/) for this, I think that's turning a modest task into a gargantuan one.
|
design
|
update icons i like our current icon set but there are a few small updates they would benefit from in the short term current source file location in our shared project file location the illustrator files for icons are in icons ▸ glyphs retire some icons there are a few icons we are never using or will likely stop using that we can remove dot was used by the radio pattern which no longer exists since we never used it lanyrd this site has been broken notification it s unclear what this icon was meant to do that wasn t covered by notifications it isn t used in any templates organization currently our icons sit in one folder but i think these might benefit from some reorganization original icons should sit at the root of the icons directory these include glyphs like arrows link notifications etc icons representing third party brands should be moved to a brands subdirectory these include icons for publications a list apart smashing etc social media websites etc our logo should be moved out of icons possibly one level up this organization should also be reflected in our source files with separate files for each type of asset why i ll get to that next… sizing the biggest design opportunity with our icons is to reconcile differences in perceived visual size some icons look proportionate to one another notice how the smaller caret used for dropdowns is smaller in proportion to the check mark the same way that the ▾ character is typically rendered compared to ✔️ img width alt screen shot at pm src but this is not true of all icons notice how small the notification bell 🔔 feels in comparison to ➕ img width alt screen shot at pm src the page does a good job of illustrating some of the concepts between icon sizing and composition to promote consistency and prevent these issues this is also why i feel it s important to organize our icons better by sizing them relative to each other maybe the lanyrd rip icon which extends dramatically into the top left corner wouldn t be threatening to devour the github icon which is confined to a circle img width alt screen shot at pm src finally the logo is used primarily as a branding element not an icon arbitrarily squashing it into our × grid raises three issues we have to scale the element up for its primary use case which is silly its coordinates will have more decimal points which increases the size of the markup required to define the shape decimal points may be rounded for performance which could result in quality loss so to summarize the goals here resize icons as a family so they will read as visually consistent rather than simply filling the viewbox treat logo asset as separate and don t squash it down like an icon simplify stroke colors in our preview icon pattern any patterns that used a stroke color instead of a fill color had to specify stroke currentcolor this is no longer the case so it can be left off those patterns entirely remove unnecessary stroke attributes not in scope… sweeping revisions to our icon styles we should certainly tweak things like stroke width to account for the resizing but we should stick with our current angles our chunky hearts and envelopes etc it feels a little clunky in to be pointing people to a shared directory so they can open illustrator and manually export svgs but while i d love to explore a github style for this i think that s turning a modest task into a gargantuan one
| 1
|
161,282
| 25,315,422,235
|
IssuesEvent
|
2022-11-17 21:09:53
|
carbon-design-system/carbon-design-kit
|
https://api.github.com/repos/carbon-design-system/carbon-design-kit
|
closed
|
[Figma] Add "Fluid-input: ComboBox"
|
kit: figma role: design :pencil2:
|
Fluid inputs: Provide design tooling updates for TextInput to `v11` Figma kit
- [x] Add to branch for all Fluid input work in each theme file (do not merge until all fluid inputs have been completed)
- [x] White theme
- [x] Gray 10 theme
- [x] Gray 90 theme
- [x] Gray 100 theme
## Spec
[Sketch file](https://ibm.box.com/s/x5dlvehz661vhqa75gwr6yqhfz0odoj5) | [Figma file](https://www.figma.com/file/9oQamCzUmVPw2jTiFkJ3Qw/Fluid-inputs_v11?node-id=243%3A1914)
|
1.0
|
[Figma] Add "Fluid-input: ComboBox" - Fluid inputs: Provide design tooling updates for TextInput to `v11` Figma kit
- [x] Add to branch for all Fluid input work in each theme file (do not merge until all fluid inputs have been completed)
- [x] White theme
- [x] Gray 10 theme
- [x] Gray 90 theme
- [x] Gray 100 theme
## Spec
[Sketch file](https://ibm.box.com/s/x5dlvehz661vhqa75gwr6yqhfz0odoj5) | [Figma file](https://www.figma.com/file/9oQamCzUmVPw2jTiFkJ3Qw/Fluid-inputs_v11?node-id=243%3A1914)
|
design
|
add fluid input combobox fluid inputs provide design tooling updates for textinput to figma kit add to branch for all fluid input work in each theme file do not merge until all fluid inputs have been completed white theme gray theme gray theme gray theme spec
| 1
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.